Tim Waugh (email@example.com)
Thu, 23 Dec 1999 10:22:34 +0000 (GMT)
On Mon, 20 Dec 1999 firstname.lastname@example.org wrote:
> When I go to "insmod ppscsi" I have success. When I do a "insmod epst"
> I get the following:
> epst.1: epst 0.91 (0.91), Shuttle EPST at 0x378 mode 2 (PS/2) dly 1 nice
> 0 sg 16scsi1 : epst
> scsi : 2 hosts.
This is a problem with the SCSI layer in 2.3 -- I just saw a patch posted
to linux-scsi. Hopefully the fix will find its way into 2.3.35 or 2.3.36.
> Any ideas what this could mean? It looks like I'm getting my devices
> recognized at bootup (somewhat... I don't have the ppscsi stuff compiled
> into the kernel, rather as modules). As evidence I offer the following
> output from dmesg:
> parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
> parport0: Found 4 daisy-chained devices
Huh? I gather you don't really have four daisy-chained devices plus
another on the end? Especially if they're all printers.. ;-)
What exactly do you have plugged into the port?
> parport0: only read 126 of 1000 ID bytes
> parport0: faking semi-colon
HP ought to read the specs..
> parport0 (addr 0): Legacy device
Eek. That might be a bug actually. There's obviously no way that an IEEE
1284.3 compliant device isn't IEEE 1284.3 compliant, which I think is that
that's trying to say.
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Thu 23 Dec 1999 - 05:24:21 EST