From: Matthew Harrell <lists-sender-14a37a@bittwiddlers.com>
To: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
Date: Fri, 14 Jan 2005 18:06:37 -0500 [thread overview]
Message-ID: <20050114230637.GA32061@bittwiddlers.com> (raw)
In-Reply-To: <200501122242.51686.dtor_core@ameritech.net>
:
: And what if you do not compile PS/2 mouse support in? Is keyboard still
: dead?
:
I also have an inresponsive keyboard and mouse on my laptop with later kernels.
To qualify that more, the same setup used to compile 2.6.10, 2.6.10-mm2,
2.6.10-mm3, 2.6.11-rc1 only gives me a working keyboard and mouse on the
2.6.10 kernel. I can plug in a USB keyboard and mouse and they work fine.
Not sure if it's the same problem as the original author. I just compiled
2.6.11-rc1 with the ps/2 mouse as a module (hoping that forcing it to load
later would help) but that didn't seem to make a difference even though it
looks like the mouse was loaded (by hotplug) after the keyboard should have
been setup. If you want I'll try another in a few minutes without the
mouse entirely. It looks like acpi does detect both keyboard and mouse
controllers. For those interested kernel bootup messages and kernel config
are available here
http://alecto.bittwiddlers.com/files/linux/boot-2.6.11rc1.log
http://alecto.bittwiddlers.com/files/linux/defconfig-2.6.11rc1
--
Matthew Harrell Failure is not an option. It comes
Bit Twiddlers, Inc. bundled with your Microsoft
mharrell@bittwiddlers.com product.
next prev parent reply other threads:[~2005-01-14 23:10 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 8:27 Roey Katz
2005-01-01 21:31 ` Dmitry Torokhov
2005-01-02 6:28 ` Roey Katz
2005-01-02 6:52 ` Dmitry Torokhov
2005-01-02 6:59 ` Roey Katz
2005-01-03 2:53 ` Roey Katz
2005-01-03 3:06 ` Dmitry Torokhov
2005-01-03 5:37 ` Roey Katz
2005-01-03 6:23 ` Dmitry Torokhov
2005-01-03 13:21 ` Roey Katz
2005-01-03 16:35 ` Dmitry Torokhov
2005-01-03 16:54 ` Roey Katz
2005-01-04 5:49 ` Roey Katz
2005-01-04 6:17 ` Dmitry Torokhov
2005-01-04 6:26 ` Roey Katz
2005-01-06 4:16 ` Dmitry Torokhov
2005-01-06 4:29 ` Roey Katz
2005-01-07 4:06 ` Roey Katz
2005-01-07 5:45 ` Dmitry Torokhov
2005-01-07 13:37 ` Roey Katz
2005-01-07 15:20 ` Dmitry Torokhov
2005-01-09 5:14 ` Roey Katz
2005-01-09 5:35 ` Dmitry Torokhov
2005-01-09 14:24 ` Roey Katz
2005-01-09 16:02 ` Dmitry Torokhov
2005-01-10 1:09 ` Roey Katz
2005-01-11 7:39 ` Dmitry Torokhov
2005-01-13 3:19 ` Roey Katz
2005-01-13 3:42 ` Dmitry Torokhov
2005-01-14 23:06 ` Matthew Harrell [this message]
2005-01-15 0:29 ` Matthew Harrell
2005-01-15 1:31 ` Dmitry Torokhov
2005-01-15 2:28 ` Matthew Harrell
2005-01-15 2:58 ` Matthew Harrell
2005-01-15 3:57 ` Dmitry Torokhov
2005-01-17 19:56 ` Vojtech Pavlik
2005-01-17 19:58 ` Matthew Harrell
2005-01-17 20:03 ` Vojtech Pavlik
2005-01-15 7:23 ` Roey Katz
2005-02-12 17:50 ` Roey Katz
2005-02-13 6:45 ` Dmitry Torokhov
2005-03-03 13:26 ` Roey Katz
2005-01-03 3:03 ` Roey Katz
2005-01-15 11:05 Marco Cipullo
2005-01-15 17:42 ` Dmitry Torokhov
2005-01-15 18:02 ` marco
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=20050114230637.GA32061@bittwiddlers.com \
--to=lists-sender-14a37a@bittwiddlers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrell-dated-1106175998.ed30bc@bittwiddlers.com \
/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
Powered by JetHome