Hi. On Saturday 07 July 2007 01:04:51 Stefan Seyfried wrote: > On Thu, Jul 05, 2007 at 09:04:27PM +1000, Nigel Cunningham wrote: > > > > > > If confusion persist after 4 seconds hard power down... then you h ve > > > hw/BIOS problem. Complain to whoever is manufacturing that beast. > > > > Adding i8042.reset=1 to the commandline fixed it. > > Wasn't there a quirk list where workarounds for i8042 on known bad machines > are stored? Maybe it would be a good idea to get your machine into it ;-) Unless I'm missing something, it looks like there's no such thing in the i8042 driver. That's okay. I can cope with adding i8042.reset=1 to my commandline :) Nigel -- Nigel Cunningham Christian Reformed Church of Cobden 103 Curdie Street, Cobden 3266, Victoria, Australia Ph. +61 3 5595 1185 / +61 417 100 574 Communal Worship: 11 am Sunday.
Attachment:
pgpu1tY0MXzpM.pgp
Description: PGP signature
- Follow-Ups:
- Re: Failure to properly reinit i8042 post suspend-to-ram
- From: Stefan Seyfried <[email protected]>
- Re: Failure to properly reinit i8042 post suspend-to-ram
- References:
- Re: Failure to properly reinit i8042 post suspend-to-ram
- From: Nigel Cunningham <[email protected]>
- Re: Failure to properly reinit i8042 post suspend-to-ram
- From: Stefan Seyfried <[email protected]>
- Re: Failure to properly reinit i8042 post suspend-to-ram
- Prev by Date: [PATCH] do not limit locked memory when RLIMIT_MEMLOCK is RLIM_INFINITY
- Next by Date: Re: [RFC] fsblock
- Previous by thread: Re: Failure to properly reinit i8042 post suspend-to-ram
- Next by thread: Re: Failure to properly reinit i8042 post suspend-to-ram
- Index(es):
 |