Re: PS/2 barcode scanner shows no output, kernel 2.6 (atkbd.c)
Am Mittwoch, 27. Juli 2005 12:00 schrieben Sie:
> On Tue, Jul 26, 2005 at 09:46:15AM +0200, Martin Rasp wrote:
> > Hi.
> >
> > I tried to use a barcode scanner (Labau LS300 PS/2) under Debian 3.1 but
> > it failed. When using Debian's kernel 2.6.8 (2.6.8-2-686-smp) I don't get
> > any useful output of the scanner except of the following messages
> > in /var/log/kern.log.
> >
> > Jul 25 08:13:45 debian kernel: atkbd.c: Keyboard on isa0060/serio0
> > reports too many keys pressed.
> > Jul 25 08:13:46 debian kernel: input: AT Translated Set 2 keyboard on
> > isa0060/serio0
> > Jul 25 08:14:08 debian kernel: input: AT Translated Set 2 keyboard on
> > isa0060/serio0
> > Jul 25 08:14:37 debian last message repeated 2 times
> >
> > A compiled Kernel 2.6.12.3 doesn't work either.
> > But after booting Debian's kernel 2.4.27 (2.4.27-2-686-smp) the
> > appropriate scan values are printed to the screen as expected.
>
> As this seems to be still present upstream, I have CCed the
> linux-input in the hope of some help.
>
> > When scanning barcodes while Linux keylogger (lkl) is running
> > each value is saved successfully in lkl's logfile.
>
> Which kernel is this with?
That was tested with Kernel 2.6.8-2-686-smp, but I noticed today that lkl
doesn't recognize the characters very well (maybe it's a lkl problem?).
I scanned the barcode '4 100060 004645' several times and got the following
output:
debian:/tmp# lkl -l -k /usr/share/lkl/keymaps/us_km -o log.file
Started to log port 0x60. Keymap is /usr/share/lkl/keymaps/us_km. The logfile
is log.file.
4100060004645
4100060004645
debian:/tmp# tail -f log.file
<Ret>
00060004645<Ret>
4100060004645<Ret>
<ScrlLck>41046<Ret>
41004645F606004645<Ret>
4100060004645<Ret>
<Ctrl>0004645<Ret>
0645F1<Ctrl>400<Ctrl>106000645<Ret>
debian:/tmp# tail -f /var/log/kern.log
Jul 27 12:35:20 debian kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Jul 27 12:35:50 debian last message repeated 4 times
Jul 27 12:36:21 debian last message repeated 7 times
Jul 27 12:37:14 debian last message repeated 5 times
The program showkey only displayed the error messages "AT Translated Set 2
keyboard on isa0060/serio0". So lkl seems to be the right tool to test with.
> > If DEBUG_ATKBD is set in "/usr/src/linux/drivers/input/keyboard/atkbd.c"
> > and I scan a barcode I get some more output in /var/log/kern.log but
> > nothing useful (for me).
> >
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received aa flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received fe flags 03
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received b8 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received e0 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 05 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 85 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 02 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 82 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 07 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 87 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 05 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 85 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 07 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 87 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 05 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 85 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 06 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 86 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 1c flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 9c flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received aa flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received b6 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received b8 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received e0 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received b8 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received e0 flags 00
> > Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00
> >
> > Seems to be a problem of kernel 2.6 in general because it works with
> > kernel 2.4. Is there a workaround or kernel option to allow the use of
> > ps/2 barcode scanners with kernel 2.6?
> >
> > Martin
> >
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmaster@lists.debian.org
>
> --
> Horms
Martin
Reply to: