On 24 Mar 1999, Soulier, Frederic wrote:
> (1) Yesterday, I recompiled my 2.2.1 kernel with support (modules) for:
> o parallel ide device support.
> o parallel port ide disk (pd driver)
> o shuttle epat/epez support (epat protocol)
> I ran the mkd script and then this is what I got:
>
> #insmod paride
> paride: version 1.04 installed
>
> #insmod epat
> paride: epat registered as protocol 0
>
> #insmod pd
> pd: pd version 1.05, major 45, cluster 64, nice 0
> pda: autoprobe failed
> pd: no valid drive found
>
> /lib/modules/2.2.1/misc/pd.0: init_module: Device or resource busy
>
>
> (2) Then I decided to recompile my kernel for some other reasons
> and now 'insmod paride' gives me a few lines of errors
> (unfortunately I cannot access my linux box now and give you the
> exact error msgs but they seemed to relate to parport_)
>
> #modprobe paride (seems to be fine)
> #modprobe epat (seems to be fine)
> #modprobe pd
> /lib/modules/2.2.1/misc/pd.o: init_module: Device or resource busy
> paride: Device or resource busy
Hmmm.... "I get a Device or resource busy" for pd if the module is
already activated.
For me, modprobe pd just simpy works.
You could try checking the linux-parport mailing list archive. It's at:
http://www.torque.net/parport/archive
On that same page... there are instructions if you would like to join
their mailing list.
regards,
= ====== Andre M. Varon Lasaltech Incorporated
= = == Technical Head Fax-Tel: (034)435-0836
= === =
= = = E-mail : [EMAIL PROTECTED]
===== = WebPage : http://andre.lasaltech.com
