From: Burkhard K. <bu...@bu...> - 2001-03-07 22:14:39
|
Mika, I've have forwarded your mail to David. At the moment I don't understand your problem - it looks like the devices stops talking to your host after successfully starting to scan. Are you running an SMP kernel? In that case you might want to try a uniprocessor kernel first - espially if you happen to have just one processor in your box. (Many distributitions) come with SMP kernels which is not always the best choice. Without seeing the debug output from ieee12844pp.o I it's impossible to determine exactly what happens. Please load the modules with Parameter "debug=2". This produces a huge amount of messages in /var/log/messages and some might even get lost because of the high rate at which debug messages are created. Therefore it might be necessary to uncomment the linebuf define in line 73 of ieee12844pp.c. Send the debug output directly to me, not to the list. Mika Saari > Hello, > > Sorry again I should read the documentation better the usenibble=1 was > mentioned there. I added the parameter to ieee12844pp module and the scanner > started the scanning (which it didn't do earlier) but after first part of > scanning it stopped and gave this error message (everything like it come to the > screen) > > ---------------------------------------- > [root@unicorn /root]# insmod parport > Using /lib/modules/2.4.2/kernel/drivers/parport/parport.o > [root@unicorn /root]# insmod parport_pc > Using /lib/modules/2.4.2/kernel/drivers/parport/parport_pc.o > [root@unicorn /root]# insmod /usr/local/lib/ieee12844.o > IEEE1284.4 protocol layer for Linux installed > [root@unicorn /root]# insmod /usr/local/lib/ieee12844pp.o usenibble=1 > ieee12844pp: IEEE1284.4 device found on parport0: > HEWLETT-PACKARD OFFICEJET PRO 1150C; > device registered to IEEE1284.4 protocol layer as link mlcpp0 > > [root@unicorn /root]# scanimage --test &> debug.txt > PAR_WAIT_SET_CLEAR(l=d9991abc,set=0x0000,clear=0x0040): timed out waiting for > event=9! > mlcpp0: mlcpp_intr ERROR -110 > state=5 event=9 reset=7 recv=3 rcv=0 send=2 > mlc: mlcpp0: link error -110 > [root@unicorn /root]# PAR_WAIT_SET_CLEAR(l=d9991abc,set=0x0098,clear=0x0040): > timed out waiting for event=23! > ---------------------------------------- > > I also enclose the debug.txt with this mail, hope it helps. > Burkhard -- Burkhard Kohl bu...@bu... |
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2001-03-08 00:52:21
|
Hi, Mika and Burkhard. If nothing works unless you use the "usenibble=1" option, then the parallel port may not be configured for bidirectional ("BPP" or "PS/2") or ECP. If it's set to unidirectional ("SPP") or EPP, then try changing it in the BIOS setup to see if that fixes the problem. My changes to ieee12844pp.c in 0.7 were partially to address the event 9 (if I remember correctly) problem you're seeing here, but the tradeoff is that the parallel port needs to be bidirectional or ECP. David > -----Original Message----- > From: Burkhard Kohl [mailto:bu...@bu...] > Sent: Wednesday, March 07, 2001 2:11 PM > To: Mika Saari > Cc: hpo...@li... > Subject: Re: [hpoj-devel] Kernel 2.4.1 module: PATCH > > > Mika, I've have forwarded your mail to David. > > At the moment I don't understand your problem - it looks > like the devices stops talking to your host after successfully > starting to scan. > > Are you running an SMP kernel? In that case you might want to > try a uniprocessor kernel first - espially if you happen to > have just one processor in your box. (Many distributitions) > come with SMP kernels which is not always the best choice. > > Without seeing the debug output from ieee12844pp.o I it's > impossible to determine exactly what happens. > Please load the modules with Parameter "debug=2". > > This produces a huge amount of messages in /var/log/messages > and some might even get lost because of the high rate at > which debug messages are created. Therefore it might be > necessary to uncomment the linebuf define in line 73 of > ieee12844pp.c. > > Send the debug output directly to me, not to the list. > > Mika Saari > > Hello, > > > > Sorry again I should read the documentation better the > usenibble=1 was > > mentioned there. I added the parameter to ieee12844pp > module and the scanner > > started the scanning (which it didn't do earlier) but after > first part of > > scanning it stopped and gave this error message (everything > like it come to the > > screen) > > > > ---------------------------------------- > > [root@unicorn /root]# insmod parport > > Using /lib/modules/2.4.2/kernel/drivers/parport/parport.o > > [root@unicorn /root]# insmod parport_pc > > Using /lib/modules/2.4.2/kernel/drivers/parport/parport_pc.o > > [root@unicorn /root]# insmod /usr/local/lib/ieee12844.o > > IEEE1284.4 protocol layer for Linux installed > > [root@unicorn /root]# insmod /usr/local/lib/ieee12844pp.o > usenibble=1 > > ieee12844pp: IEEE1284.4 device found on parport0: > > HEWLETT-PACKARD OFFICEJET PRO 1150C; > > device registered to IEEE1284.4 protocol layer as link mlcpp0 > > > > [root@unicorn /root]# scanimage --test &> debug.txt > > PAR_WAIT_SET_CLEAR(l=d9991abc,set=0x0000,clear=0x0040): > timed out waiting for > > event=9! > > mlcpp0: mlcpp_intr ERROR -110 > > state=5 event=9 reset=7 recv=3 rcv=0 send=2 > > mlc: mlcpp0: link error -110 > > [root@unicorn /root]# > PAR_WAIT_SET_CLEAR(l=d9991abc,set=0x0098,clear=0x0040): > > timed out waiting for event=23! > > ---------------------------------------- > > > > I also enclose the debug.txt with this mail, hope it helps. > > > > Burkhard > -- > Burkhard Kohl bu...@bu... > > _______________________________________________ > hpoj-devel mailing list > hpo...@li... > http://lists.sourceforge.net/lists/listinfo/hpoj-devel > |