nother data point:
I removed all parport modules and then started a print job to see if the autoloader could figure it out.
It loaded parport and parport_probe, but then hung with the previously noted repeating error message:
-- Feb 19 16:12:08 cx408397-a modprobe: can't locate module parport_lowlevel Feb 19 16:12:08 cx408397-a kernel: lp: no devices found Feb 19 16:12:08 cx408397-a insmod: /lib/modules/2.2.18/misc/lp.o: init_module: Device or resource busy --until I manually loaded parport_pc: -- insmod parport_pc io=0x3bc,0x378,0x278 irq=none,7,auto --
which then allowed lp.o to load: -- Feb 19 16:12:23 cx408397-a kernel: 0x3bc: CTR: wrote 0x0c, read 0xff Feb 19 16:12:23 cx408397-a kernel: 0x3bc: DATA: wrote 0xaa, read 0xff Feb 19 16:12:23 cx408397-a kernel: parport0: PC-style at 0x3bc [SPP,PS2] Feb 19 16:12:23 cx408397-a kernel: parport_probe: failed Feb 19 16:12:23 cx408397-a kernel: parport0: no IEEE-1284 device present. Feb 19 16:12:23 cx408397-a kernel: parport1: PC-style at 0x378, irq 7 [SPP] Feb 19 16:12:23 cx408397-a kernel: parport_probe: succeeded Feb 19 16:12:23 cx408397-a kernel: parport1: Printer, Hewlett-Packard HP LaserJet 6MP Feb 19 16:12:23 cx408397-a kernel: 0x278: CTR: wrote 0x0c, read 0xff Feb 19 16:12:23 cx408397-a kernel: 0x278: DATA: wrote 0xaa, read 0xff Feb 19 16:12:23 cx408397-a kernel: parport2: PC-style at 0x278 [SPP,PS2] Feb 19 16:12:23 cx408397-a kernel: parport_probe: failed Feb 19 16:12:23 cx408397-a kernel: parport2: no IEEE-1284 device present. Feb 19 16:12:40 cx408397-a kernel: lp0: using parport0 (polling). Feb 19 16:12:40 cx408397-a kernel: lp1: using parport1 (interrupt-driven). Feb 19 16:12:40 cx408397-a kernel: lp2: using parport2 (polling). --
and the std almost blank piece of paper to to eject.
was this of any use?
hjm
Tim Waugh wrote: > > On Mon, Feb 19, 2001 at 01:51:31PM -0800, Harry Mangalam wrote: > > > This sounds a bit like the problem that Eythan Weg had last year, but > > in his case it looked like his cable was just buggered. I have > > tested my cable on other machines and it's communicating on this > > machine as well (and was printing fine under 2.2.14).. > > Is installing 2.2.14 and quickly testing to see if that does indeed > make the problem go away an option? If so, I would suggestion trying > to find out exactly which kernel revision it stops working at. > > Tim. > */ > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > Part 1.2Type: application/pgp-signature
-- Cheers, Harry
Harry J Mangalam -- (949) 856 2847 (v&f) -- hjm@ncgr.org || mangalam@home.com
-- 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 : Mon Feb 19 2001 - 19:21:17 EST