From: Andrew Morton <akpm@osdl.org>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, caphrim007@gmail.com
Subject: Re: Lost keyboard on Inspiron 8200 at 2.6.13
Date: Fri, 16 Sep 2005 02:53:56 -0700 [thread overview]
Message-ID: <20050916025356.0d5189a6.akpm@osdl.org> (raw)
In-Reply-To: <200509152357.58921.dtor_core@ameritech.net>
Dmitry Torokhov <dtor_core@ameritech.net> wrote:
>
> On Thursday 15 September 2005 23:29, Tim Rupp wrote:
> > I just recently went to upgrade to 2.6.13 from 2.6.12.3 and after
> > re-compiling with a clean .config, I've hit a snag.
> >
> > I'm pretty sure I've got the config script down right, but upon reboot,
> > I no longer have a keyboard.
> >
> > I checked to see if this had crept up between 2.6.12.3 and 2.6.13.1. It
> > seems that >2.6.13 are the versions that do this.
> >
> > Attached are dmesgs from my 2.6.13.1 and 2.6.12.3 kernels. In the
> > 2.6.13.1 kernel I noticed this line.
> >
> > i8042.c: Can't read CTR while initializing i8042
> >
>
> The kernel failed to talk to your keyboard controller. Try booting with
> "usb-handoff" and also try "acpi=off"
>
This is of course not an acceptable solution. A machine which worked
without funky commandline parameters should continue to work in later
kernels.
How come it broke?
next prev parent reply other threads:[~2005-09-16 9:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 4:29 Lost keyboard on Inspiron 8200 at 2.6.13 Tim Rupp
2005-09-16 4:57 ` Dmitry Torokhov
2005-09-16 5:13 ` Tim Rupp
2005-09-16 9:53 ` Andrew Morton [this message]
2005-09-16 15:25 ` Dmitry Torokhov
2005-09-16 16:00 ` Alan Cox
2005-09-16 18:44 ` Greg KH
2005-09-16 19:00 ` [linux-usb-devel] " Alan Stern
2005-09-16 19:45 ` David Brownell
2005-09-16 22:24 ` [linux-usb-devel] " Pete Zaitcev
2005-09-16 22:32 ` Greg KH
2005-09-16 23:54 ` Alan Cox
2005-09-17 4:12 ` Alan Stern
2005-09-17 8:08 ` Alan Cox
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=20050916025356.0d5189a6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=caphrim007@gmail.com \
--cc=dtor_core@ameritech.net \
--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