systemic@mciworld.com
Mon, 20 Dec 1999 20:43:39 -0800
On Sun, Dec 19, 1999 at 08:15:22PM +0000, Tim Waugh so eloquently wrote:
<snip>
Hey again,
As a refresher, you suggested that I upgrade to the 2.3 series of
kernels to better assist me in getting my 5100c to work correctly. I've
upgraded to 2.3.33 and gotten it to patch. I haven't been able to
successfully patch for 2.3.34 yet, but I'm not too concerned about that
now. I've gotten everything to good state with the new kernel and now
have a couple of different problems with the ppscsi stuff.
First though, the details:
(1) Kernel 2.3.33 (clean source)
(2) Bios set to EPP
(3) In Bios - setting for Plug-and-Pray OS set to NO (I tried this the
other way and my printer couldn't be found)
(4) Parallel Support, SCSI Generic compiled into kernel
(5) ppscsi, and epst built as modules
When I go to "insmod ppscsi" I have success. When I do a "insmod epst"
I get the following:
<snip>----------
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.
<snip»----------
The system just freezes here. Can't even kill -9 the process. I can
print during this time successfully, and then I get some more output:
<snip>----------
bad magic c40f92e0 (should be d08241a4, creator 0), wq bug, forcing
oops.
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c0112792
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c0112792>]
EFLAGS: 00010092
eax: 00000016 ebx: d0824110 ecx: cfa54000 edx: cfa55f84
esi: 00000246 edi: d082419c ebp: ce579f38 esp: ce579f1c
ds: 0018 es: 0018 ss: 0018
Process cat (pid: 747, stackpage=ce579000)
Stack: 00000246 00000000 00000000 ce578000 00001000 00000286 00000003
00000000
d081e4d8 cf523720 c1448260 c14572c0 c01affb5 d0824110 00000000
00001000
ce578000 c01a92b4 c14572c0 00000000 c01a97df 00000000 ced2a380
ffffffea
Call Trace: [<d081e4d8>] [<c01affb5>] [<d0824110>] [<c01a92b4>]
[<c01a97df>] [<c012b06a>] [<c010ae74>]
Code: c7 05 00 00 00 00 00 00 00 00 83 c4 04 90 83 3f 00 74 06 83
<snip>------------
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:
<snip>------------
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
parport0: Found 4 daisy-chained devices
parport0: only read 126 of 1000 ID bytes
parport0: faking semi-colon
parport0 (addr 0): Legacy device
parport0: faking semi-colon
parport0 (addr 1): Printer, Hewlett-Packard HP LaserJet 1100
parport0: faking semi-colon
parport0 (addr 2): Printer, Hewlett-Packard HP LaserJet 1100
parport0: faking semi-colon
parport0 (addr 3): Printer, Hewlett-Packard HP LaserJet 1100
parport0: faking semi-colon
parport0: Printer, Hewlett-Packard HP LaserJet 1100
lp0: using parport0 (polling).
<snip>-----------
Any advice for me here? Anyone? (Beg mode on... please I wanna use my
scannnnnnner). I'm better now, really.
Thanks in advance,
Systemic
-- ----------------------------------------------------------------- "Just because you're paranoid, doesn't mean that they really aren't out to get you." ------------------------------------------------------------------- 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 Wed 22 Dec 1999 - 17:25:35 EST