From: Matt Causey <matt.causey@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: serio / atkbd / PS/2 Strangeness with Serial port adapter
Date: Mon, 24 Aug 2009 17:09:20 -0700 [thread overview]
Message-ID: <ac71f2bb0908241709i1afa2cedy62c3dc13982f4fb7@mail.gmail.com> (raw)
In-Reply-To: <20090810090508.69E02526EC9@mailhub.coreip.homeip.net>
On Mon, Aug 10, 2009 at 1:34 AM, Dmitry
Torokhov<dmitry.torokhov@gmail.com> wrote:
>> [ 459.004227] drivers/input/serio/i8042.c: fe <- i8042 (interrupt, 1,
>> 12, timeout) [445118]
>> [20171.684870] drivers/input/serio/i8042.c: 0b <- i8042 (interrupt, 0,
>> 1) [20162195]
>>
>> However - the atkbd driver does not pick the device up at all.
>>
>
> Your device is steadely refusing to say that it is a keyboard - and so
> atkbd driver does not bind to it.
>
>> So, I did find a workaround (which is NOT acceptable for this
>> deployment). Remember the PS/2 'wedge' I mentioned? Well, it has an
>> extra PS/2 port for your keyboard. If I connect a PS/2 keyboard to
>> that thing, suddenly my scanner starts working.
>>
>> We see some chatter from the controller driver, then one of these:
>>
>> [23811.805578] input: AT Translated Set 2 keyboard as
>> /devices/platform/i8042/serio0/input/input6
>>
>
> That happened because apparently the 'wedge' passes the inquirys to
> the real keyboard and it answers propery.
>
> I think the "i8042.dumbkbd" kernel parameter will solve your issue.
>
> --
> Dmitry
>
That's great. I think it's the only option that I did not try. ;-)
Works great!
In case it matters:
blah blah/ # dmesg | grep i8042
[ 0.000000] Kernel command line: initrd=ramdisk.gz
video="vesafb:mtrr,ywrap,1024x768-32@85" i8042.dumbkbd
BOOT_IMAGE=bzImage auto
[ 14.046511] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 14.046578] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 15.804210] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input2
blah blah/ #
Looks like it just decides that there must be a keyboard there,
whether or not there really is one.
Are there any downsides to using this kernel parameter?
Thanks!
--
Matt
next prev parent reply other threads:[~2009-08-25 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 20:15 Matt Causey
2009-08-06 21:04 ` Gustavo Guillermo Perez
2009-08-06 21:40 ` Matt Causey
2009-08-10 8:34 ` Dmitry Torokhov
2009-08-25 0:09 ` Matt Causey [this message]
2009-08-25 0:22 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac71f2bb0908241709i1afa2cedy62c3dc13982f4fb7@mail.gmail.com \
--to=matt.causey@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®