It is an parallel port Hard Drive. It appears as though parport is finding
it at 0x378.
> parport0: PC-style at 0x378 [SPP,PS2,EPP]
> parport0: no IEEE-1284 device present.
I load paride and it installs correctly
> paride: version 1.04 installed
I then load the fit3 module which is the driver for transdisk and it loads
correctly
i don't think it requires the epat protocol, but I loaded it anyway, to no
avail
> paride: fit3 registered as protocol 0
But as soon as I try to load any devs, ie pf, pcd, etc I get the same
message
> Using /lib/modules/2.2.14-3/misc/pf.o
> /lib/modules/2.2.14-3/misc/pf.o: init_module: Device or resource busy
or
> Using /lib/modules/2.2.14-3/misc/pt.o
> /lib/modules/2.2.14-3/misc/pt.o: init_module: Device or resource busy
or
> Using /lib/modules/2.2.14-3/misc/pg.o
> /lib/modules/2.2.14-3/misc/pg.o: init_module: Device or resource busy
I have even tried to specify the drive and protocol, but I still get the
Device
or resource busy message
> insmod pf drive0=0x378,0
I did also read the paride.c and the pf.c files and try to specfy all the
parameters,
but nothing seems to work. if the device is busy by what???
Any help or guidance would be appreciative.
Thanks,
Scott
----- Original Message -----
From: "Penndragon" <pdragon@internettv.net.au>
To: "Scapester" <scapester2000@hotmail.com>
Sent: Friday, January 26, 2001 10:51 PM
Subject: Re: [PARPORT] Transdisk failure
> MM Scapester
>
> Now I can read your post :)
> From what I can gather you haven't loaded the epat module, is that a fair
> assumption? Does the device you're trying to connect need it? Are you
trying
> to set up a Parallel Floppy such as an ls-120 or something akin to it? If
> so, I'd suggest the following order to insert the modules
>
> paride
> epat
> pf
>
> James
> ----- Original Message -----
> From: Scapester
> To: linux-parport@torque.net
> Sent: Saturday, January 27, 2001 2:23 PM
> Subject: [PARPORT] Transdisk failure
>
>
> I am hoping someone can help with a problem I am having. When I try to
> insmod the pf driver I get this error message:
>
> insmod pf
> Using /lib/modules/2.2.14-3/misc/pf.o
> /lib/modules/2.2.14-3/misc/pf.o: init_module: Device or resource busy
>
> I have unloaded and reloaded the parport, paride and fit3 modules. I get
> this message when I try to insert any drivers, pf, pcd, etc. I am running
> turbolinux 6.0 server lite. My lsmod shows :
>
> Module Size Used by
> parport_probe 3164 0 (autoclean)
> parport_pc 7232 0 (autoclean)
> soundcore 2336 0 (autoclean) (unused)
> fit3 3876 0
> msdos 5300 0 (autoclean) (unused)
> paride 3408 1 [fit3]
> parport 6724 0 [parport_probe
> parport_pc paride]
> nfs 27012 2 (autoclean)
> nfsd 141328 1 (autoclean)
> lockd 29260 1 (autoclean) [nfs nfsd]
> sunrpc 48492 1 (autoclean) [nfs nfsd
> lockd]
> tulip 32552 1 (autoclean)
> pci-scan 2640 0 (autoclean) [tulip]
> vfat 9188 0 (unused)
> fat 29220 0 [msdos vfat]
>
> Dmesg show:
>
> paride: version 1.04 installed
>
> paride: fit3 registered as protocol 0
>
> parport0: PC-style at 0x378 [SPP,PS2,EPP]
> parport0: no IEEE-1284 device present.
> pf0: Autoprobe failed
> pf: No ATAPI disk detected
>
> I have tried: insmod pf drive0=0x378,0 - insmod pf drive1=0x378,0, and
all
> combination of drive, protocol numbers etc. Any help would be greatly
> apperciated. Thanks,
> Scapester
>
>
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Sat Jan 27 2001 - 13:38:07 EST