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] [day] [month] [year] [list]
Message-id: <507EB764.2040105@verizon.net>
Date:	Wed, 17 Oct 2012 09:49:24 -0400
From:	Gerry Reno <greno@...izon.net>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Michael Spang <spang@...gle.com>, linux-usb@...r.kernel.org,
	Dave Jones <davej@...hat.com>,
	Michael Spang <spang@...omium.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Fedora Kernel Team <kernel-team@...oraproject.org>
Subject: Re: USB keyboard backlight powering down.

On 10/17/2012 09:31 AM, Josh Boyer wrote:
> On Wed, Oct 17, 2012 at 09:09:56AM -0400, Gerry Reno wrote:
>>>> This was the udev bug I was referring to, which I think is causing the
>>>> keyboard to have auto-suspend enabled:
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=825284
>>>>
>>>> udev shouldn't be enabling auto-suspend of USB hids by default, since
>>>> many of them don't send a wakeup to come out of suspend when they
>>>> should.  For example, most USB mice only send a wakeup even when they
>>>> are clicked, not when they are moved.  That causes the user to sit
>>>> there, frustrated, as they move their mouse and wonder why their screen
>>>> doesn't unblank.  Other keyboards also lose keystrokes, which means if
>>>> you pause to compose your thoughts, the first couple letters you type
>>>> gets dropped.
>>> I know we fixed that bug for F17, F18, and rawhide.  I did it myself.
>>> I don't think this is udev related, but we'll double check the version.
>>>
>>> Gerry, are you using udev-182-3.fc17 or newer on your F17 install?
>>>
>>> josh
>>>
>>
>>
>> Installed Packages
>> udev.x86_64                                                182-1.fc17                                               
>> @anaconda-0
>>
>> There is an update available to 182-3 but I haven't installed it.  Didn't know what it might impact.
> Well, it would certainly be good to update to it and see if this bug is
> fixed for you.  You will probably need to rebuild your initramfs with
> the updated udev.
>
> josh
>


I updated udev to 182-3 then rebooted and my illuminated keyboard is now functioning properly.  Didn't need to rebuild
initramfs.  Everything appears to be working fine.

Gerry


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ