Re: [PARPORT] Castlewood ORB


Bruce Savaglio (bsavagli1@home.com)
Sat, 12 Feb 2000 11:41:52 -0800


Without the 0x378 I get:
> pd: pd version 1.05, major 45, cluster 64, nice 0
> pda Atuoprobe faild
> pd: no valid drive found
> /lib/modules/2.2.12-20/misc/pd.o: init_module: Device or resource busy
Also, cat /proc/ioports doesn't contain a 0x378 although the bios is definitely set to that port for the paralell port.
Also, my pd driver must be build differently that yours because I have to include the insmod parport as the first line
or the pd errors out.I don't know what's using the 0x378 port, although I tried it with 0x376 and 0x278, still no luck.

Thanks much for you help. I now have a direction in which to look. Any further suggestions will be appreciated.

Jonas Linde wrote:

> And bsavagli1@home.com spoke unto the world. And said:
> > Still trying to successfully install an ORB on linux. I've seen the
> > archives from some who have said it was a walk-in-the-park. I seem to be
> > lost. If anyone spots what I'm doing wrong, please let me know
> <snip>
> > I have been trying to install the drivers for an ORB without any luck. I
> > I have an ECP/EPP paralell port with the EPP mode set to 1.9.
> > If I use
> > insmod pd drive0=0x378 verbose=1
> > I get:
> > pd: pd version 1.05, major 45, cluster 64, nice 0
> > pda: on26: port 0x378, mode 0, test=(255,255)
> > pda: on26: port 0x378, mode 1, test=(255,255)
> > pda: on26: port 0x378, mode 2, test=(255,255)
> > pda: on26: port 0x378, mode 3, test=(255,255)
> > pda: on26: port 0x378, mode 4, test=(255,255)
> > pda: Adapter not found
> > pd: no valid drive found
> > /lib/modules/2.2.12-20/misc/pd.o: init_module: Device or resource busy
>
> Well, for me it was the walk-in-the-park;
>
> insmod paride
> insmod on26
> insmod pd
>
> works like a sharm... The syslog then contains:
>
> Feb 12 17:19:19 master kernel: paride: version 1.04 installed
> Feb 12 17:19:23 master kernel: paride: on26 registered as protocol 0
> Feb 12 17:19:34 master kernel: pd: pd version 1.05, major 45, cluster 64, nice 0
> Feb 12 17:19:34 master kernel: pda: 0x378 is parport0
> Feb 12 17:19:34 master kernel: pda: on26: port 0x378, mode 0, test=(0,0)
> Feb 12 17:19:34 master kernel: pda: on26: port 0x378, mode 1, test=(0,0)
> Feb 12 17:19:34 master kernel: pda: on26: port 0x378, mode 2, test=(255,255)
> Feb 12 17:19:34 master kernel: pda: on26: port 0x378, mode 3, test=(255,255)
> Feb 12 17:19:34 master kernel: pda: on26: port 0x378, mode 4, test=(255,255)
> Feb 12 17:19:34 master kernel: pda: Sharing parport0 at 0x378
> Feb 12 17:19:34 master kernel: pda: on26 1.04, OnSpec 90c26 at 0x378, mode 1 (8-bit), delay 1
> Feb 12 17:19:34 master kernel: pda: CASTLEWOOD ORB, master, 4307184 blocks [2103M], (4273/16/63), removable media
> Feb 12 17:19:42 master kernel: pda: pda1
>
> Occasionally I get "lp0 out of paper" too, which I find kind of cute. ;-)
>
> I managed to reproduce your error messages by changing the port to
> 0x278. Are you shure your parallell port is at 0x378? What happens if
> you skip the drive0=0x378 bit? What output do you get from the command
>
> cat /proc/ioports
>
> There should be a "0378-037a : parport0" line in there.
>
> /J
> ________________________________________________________________________
> Jonas Linde init ab jonas@init.se www.init.se/~jonas/ +46-707-492496
>
> GE/IT$ d-() s++: a C++(++++)$ UBVL++(++++)$ P++ L+++>$ E++ W++(-) N+ o--
> K+ !w(+) O M@ V PS+ PE++(-) Y+ PGP+>++ t 5- X R- tv- b+>++ DI D++ G++(-)
> e+++ h---- r+++ y++++
>
> -- To unsubscribe, send mail to: linux-parport-request@torque.net --
> -- with the single word "unsubscribe" in the body of the message. --

-- 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 2.0b3 on Sat 12 Feb 2000 - 14:41:00 EST