insmod insertion error: -1 Device or resource busy

[bob 295]

On Friday 19 June 2009 10:06 am, Lennart Sorensen wrote:
> On Thu, Jun 18, 2009 at 08:16:34PM -0400, bob 295 wrote:
> > Looked through the source code for the module and found only one instance
> > of EBUSY in around some ioctl stuff.    However,  it is preceded by a
> > printk which I'm not seeing.
> >
> > The init_module function contains the following block with no surrounding
> > printk:
> >
> > 	rc = register_chrdev(dscud_major, "dscud", &dscud_fops);
> > 	if ( rc < 0 )
> > 		return rc;
> >
> > Could this generate the insmod insertion error I'm seeing?   Next
> > opportunity I'll add a printk for rc.    I'm guessing this might give me
> > EBUSY.    If so what could be the source of such an EBUSY response from
> > register_chrdev()?
> >
> > Thanks in advance again.
>
> Wall whatever dscud_major is, if another driver is already using that
> major number, then you will probably get that error.
>
> So look up what that major should be, and check /proc/devices to see if
> anything is using that major.

BINGO.   Thanks.   Onward and upward to try and make the A-D card dance 
now ...

bob
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists