From: Michael Krufky <mike@krufky.com>
To: mkrufky@m1k.net
Cc: vojtech@suse.cz, Frank Peters <frank.peters@comcast.net>,
linux-kernel@vger.kernel.org
Subject: Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems
Date: Mon, 27 Jun 2005 07:39:11 -0400 [thread overview]
Message-ID: <42BFE55F.4020905@krufky.com> (raw)
In-Reply-To: <42BC306A.1030904@m1k.net>
Michael Krufky wrote:
> Frank Peters <frank.peters@comcast.net> wrote:
>
>> After downloading and compiling the latest version 2.6.12, my
>> keyboard becomes unresponsive and dead following the boot process.
>> This doesn't occur all of the time, but only some of the time.
>> In particular, the follwing boot up message will be seen at
>> sporadic places among the other text output:
>>
>> input: AT Translated Set 2 keyboard on isa0060/serio0
>>
>> When this message does not occur anywhere in the boot messages,
>> the keyboard is not functional. When the message does occur, then
>> the keyboard will respond, but sometimes with an erratic key
>> repeat rate. After rebooting several times I can usually get
>> the system up and running smoothly, but with this current kernel
>> 2.6.12, there is no guarantee that it will boot properly at any
>> given time.
>>
>>
> ...
>
>> My system is an ASUS P4B533 motherboard with a Pentium 3.6 Ghz
>> Hyperthreaded processor and 1 GHz RAM. The kernel is the stock
>> linux kernel (compiled with gcc-2.95.3) and the rest of my software
>> is self-compiled (i.e. no distribution).
>>
>> If I disable ACPI, either by compiling a new 2.6.12 kernel or
>> through boot up parameters, the keyboard will respond normally
>> without any problems, but the kernel will not recognize my
>> hyperthreaded processor. Only one CPU will be initialized and
>> active.
>>
>> Thus, I can enjoy a problem-free 2.6.12 kernel if I choose to
>> sacrifice ACPI and hyperthreading.
>>
>>
> ...
>
>> If anyone has any suggestions or needs any more information,
>> please CC me at the address frank.peters@comcast.net as I am not
>> a subscriber to the list.
>>
>>
> I am having the same problem with my Shuttle FT61 motherboard,
> although I have not tried to disable ACPI... Until now I thought I
> just had a faulty keyboard, as my method to fix this was to unplug the
> keyboard and plug it back in after bootup. When this happens, I see
> this in dmesg as the last line:
>
> input: AT Translated Set 2 keyboard on isa0060/serio0
>
> I am also having problems with my AUX mouse, as seen in message
>
> Subject: 2.6.12-rc5-mm1 breaks serio: i8042 AUX port
>
> Frank, are you having problems with your ps/2 mouse port as well?
>
> I haven't spent enough time experimenting with this, as I thought it
> might have had something to to with my hardware / KVM switch. Seeing
> Frank's message is the reason why I've decided to chime back in on this.
>
> As a clarification, I have been having these keyboard problems
> intermittently, regardless of whether I'm using -mm or mainline
> kernel. I was NOT having this problem in 2.6.11 I wasn't having the
> psaux mouse problems in 2.6.11 either .... I unplugged my psaux mouse
> from that machine before 2.6.12-mainline was released, so I don't know
> if those symptoms are still present. (using USB mouse now instead).
> I am currently in my office, so I can't test this right now, and I
> will be away for this weekend. I'll be able to make these tests again
> come Sunday night/Monday. ...and I will try it this time WITHOUT the
> kvm switch.
>
I tested the above scenarios with 2.6.12-mm2 and everything is working
normally again. ...still having input problems with older -mm kernels,
but if -mm2 is working then I must assume that the problem, (at least MY
problem) has already been fixed.
Thank you!
next prev parent reply other threads:[~2005-06-27 11:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 15:34 Asus MB and 2.6.12 Problems Frank Peters
2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky
2005-06-24 16:59 ` Frank Peters
2005-06-24 17:12 ` Michael Krufky
[not found] ` <20050728222838.64517cc9.akpm@osdl.org>
2005-07-29 5:44 ` Michael Krufky
2005-07-29 5:54 ` Andrew Morton
2005-07-30 2:44 ` Zwane Mwaikambo
2005-07-30 3:48 ` Michael Krufky
2005-07-30 3:52 ` Michael Krufky
2005-07-30 4:18 ` Michael Krufky
2005-07-30 4:37 ` Andrew Morton
2005-07-30 5:57 ` Dmitry Torokhov
2005-07-30 6:34 ` Frank Peters
2005-07-31 18:45 ` Vojtech Pavlik
2005-07-31 19:24 ` Frank Peters
2005-07-31 20:42 ` Andrew Morton
2005-07-31 23:48 ` Frank Peters
2005-07-29 18:33 ` Frank Peters
[not found] ` <20050804162812.29a3f2b2.akpm@osdl.org>
2005-08-05 3:09 ` Frank Peters
2005-08-05 3:20 ` Dmitry Torokhov
2005-08-05 3:54 ` Andrew Morton
2005-08-05 4:07 ` Dmitry Torokhov
2005-08-05 10:40 ` Marc Ballarin
2005-08-05 4:07 ` Michael Krufky
2005-08-05 6:43 ` Vojtech Pavlik
2005-08-04 20:19 ` Andrew Morton
2005-06-27 11:39 ` Michael Krufky [this message]
[not found] ` <1119633158.3180.5.camel@home-lap>
2005-06-24 18:07 ` Frank Peters
2005-06-26 19:47 ` Alexey Dobriyan
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 8:33 isa0060/serio0 problems -WAS- " Andrey Borzenkov
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=42BFE55F.4020905@krufky.com \
--to=mike@krufky.com \
--cc=frank.peters@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@m1k.net \
--cc=vojtech@suse.cz \
/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