From: Andrew Morton <akpm@osdl.org>
To: mkrufky@m1k.net
Cc: frank.peters@comcast.net, linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems
Date: Thu, 4 Aug 2005 13:19:30 -0700 [thread overview]
Message-ID: <20050804131930.793156d4.akpm@osdl.org> (raw)
In-Reply-To: <42BC3EFE.5090302@m1k.net>
Michael Krufky <mkrufky@m1k.net> wrote:
>
> I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel
> maintainer.
>
> Vojtech, I figured these should be sent to you. If I am wrong, please
> redirect them to the correct person / list and let us know.
>
(Pleasee don't top-post. See what a mess you've made!)
I don't think we've fixed all the bugs which people were reporting in this
thread. Could people please retest 2.6.13-rc6 when it's out and generate
new reports for any remaining problems? Via bugzilla.kernel.org would be
preferred (by me. Otherwise tracking the status of these things is a
nightmare).
Thanks.
(And, unlike previous cycles, I'll be tracking these bugs into the 2.6.14
series, so nobody can hide!)
(As long as they're in bugzilla)
>
> Frank Peters wrote:
>
> >On Fri, 24 Jun 2005 12:10:18 -0400
> >Michael Krufky <mkrufky@m1k.net> wrote:
> >
> >
> >
> >>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 am so glad that you asked this.
> >
> >I have not been able to get my ps/2 mouse to function with any
> >2.6.x or 2.4.x kernel (same ASUS MB). The problem is already
> >so long standing that I have completely given up on it and use
> >a serial mouse exclusively and no longer bother with ps/2.
> >
> >(I also hate to report that since I dual boot with MS Windows,
> >the ps/2 mouse functions properly under the same conditions
> >with MS Windows 2K. The hardware cannot be at fault.)
> >
> >
> >
> >>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.
> >>
> >>
> >
> >Actually, my keyboard problems began with kernel-2.6.11, but were
> >quickly resolved when I used the following parameter in my lilo.conf
> >file:
> >
> >i8042.nomux
> >
> >When I use this parameter, or any other i8042 specific parameter,
> >with kernel-2.6.12, there is no effect. The keyboard still occasionally
> >comes up dead.
> >
> >Thanks for the information on unplugging and re-plugging the keyboard.
> >I'll give that a try soon.
> >
> >Frank Peters
> >
> >(Please CC to frank.peters@comcast.net as I am not a subscriber to this
> >list.)
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
> >
> >
>
>
> --
> Michael Krufky
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-08-04 20:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 15:34 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 [this message]
2005-06-27 11:39 ` Michael Krufky
[not found] ` <1119633158.3180.5.camel@home-lap>
2005-06-24 18:07 ` Frank Peters
2005-06-26 19:47 ` Alexey Dobriyan
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=20050804131930.793156d4.akpm@osdl.org \
--to=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®