From: Andrew Haninger <ahaning@gmail.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org,
suspend2-users <suspend2-users@lists.suspend2.net>
Subject: Re: PS/2 Keyboard is dead after resume.
Date: Sat, 16 Jul 2005 11:06:22 -0400 [thread overview]
Message-ID: <105c793f05071608065ceb5b8b@mail.gmail.com> (raw)
In-Reply-To: <200507160135.39220.dtor_core@ameritech.net>
On 7/16/05, Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> Ok, so you start with IRQ 12 disabled.. You don't have a PS/2 mouse,
> do you?
Nope :).
> > serio: i8042 AUX port at 0x60,0x64 irq 12
> > serio: i8042 KBD port at 0x60,0x64 irq 1
>
> You did not select PNP support (but as far as keyboard controller settings
> go we don't trust it anyway on i386).
I've never ever found it to work, so I usually disable it.
> And here you have a bunch of hardware gets assigned to IRQ 12...
> Hmm, I tought ACPI would try not use 12 unless it is absolutely
> necessary. What appens if you use "pci=routeirq" boot option?
The keyboard was still dead after resume.
> You can try working around this with "i8042.noaux" kernel boot option,
> but we should probably teach i8042 driver to not touch AUX port on resume
> if it was disabled.
This worked. Strangely enough, after googling for i8042 and suspend
last night, I found the 2.6.12 kernel boot options file. I tried
i8042.nomux, i8042.direct, and some others, but nothing worked. Just
for fun, I tried booting without any kernel boot options (just the
suspend2 option) and with a PS/2 mouse plugged in. On suspend, the
keyboard worked.
Maybe this could/should be added to the suspend2 code as well?
Whatever. It works for now. If you'd like any more information, just
let me know. Thanks!
-Andy
prev parent reply other threads:[~2005-07-16 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 2:35 PS/2 Keyboard is dead after resume Andrew Haninger
2005-07-15 5:24 ` Dmitry Torokhov
2005-07-15 11:43 ` Andrew Haninger
2005-07-16 6:35 ` Dmitry Torokhov
2005-07-16 15:06 ` Andrew Haninger [this message]
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=105c793f05071608065ceb5b8b@mail.gmail.com \
--to=ahaning@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=suspend2-users@lists.suspend2.net \
/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