linux-kernel - Re: [PATCH][RFC] input: remove bios I8042_CTR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091029032633.GA7959@core.coreip.homeip.net>
Date:	Wed, 28 Oct 2009 20:26:33 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Dave Young <hidave.darkstar@...il.com>
Cc:	Vojtech Pavlik <vojtech@...e.cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH][RFC] input: remove bios I8042_CTR_XLATE check to make
	keyboard usable

On Thu, Oct 29, 2009 at 08:33:26AM +0800, Dave Young wrote:
> On Wed, Oct 28, 2009 at 06:42:12PM +0800, Dave Young wrote:
> > On Wed, Oct 28, 2009 at 11:03:18AM +0100, Vojtech Pavlik wrote:
> > > On Tue, Oct 27, 2009 at 10:43:10PM -0700, Dmitry Torokhov wrote:
> > > > Hi Dave,
> > > > 
> > > > On Tue, Oct 27, 2009 at 01:34:04PM +0800, Dave Young wrote:
> > > > > 
> > > > > Pressing somekey at early booting phase cause keyboard to be not usable
> > > > > (The hardware is DELL latitude e5400):
> > > 
> > > Does early booting mean while the BIOS is coming up? Does the keyboard
> > > work in GRUB then? Or is it during the early init of the Linux kernel?
> > 
> > Keyboard work under lilo.
> > For the early booting I means the early init of the linux kernel
> > 
> > >  
> > > > > atkbd.c: Unknown key pressed (raw set 2, code 0xd3 on isa0060/serio0).
> > > > > atkbd.c: Use 'setkeycodes e053 <keycode>' to make it known.
> > > > > atkbd.c: Unknown key pressed (raw set 2, code 0x1d3 on isa0060/serio0).
> > > > > atkbd.c: Use 'setkeycodes e053 <keycode>' to make it known.
> > > > > 
> > > > > i8042.c set i8042_direct to true when the controller init. But the result
> > > > > is keyboard not usable, The only option is press the power button to shutdown. 
> > > > > 
> > > > > So here remove the bios check to fix it.
> > > 
> > > My question would be: Why this happens? Could it be that the probe is
> > > confused by the keypress and reads the CTR incorrectly? Or is it just
> > > that the keyboard controller is in fact in translating mode, yet the CTR
> > > indicates otherwise?
> > > 
> > > A i8042.debug=1 log of the bad init would be good.
> > 
> > Here it is (retrieve from syslog):
> 
> Syslog redirect the debug info to another log file, sorry, post again:
> 

Any chance of reconfiguring syslog so debug is captured in the same
file? It is easier to see what is happening with the rest of context
present...

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/