From: Gerry Reno <greno@verizon.net>
To: Josh Boyer <jwboyer@redhat.com>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Spang <spang@google.com>,
linux-usb@vger.kernel.org, Dave Jones <davej@redhat.com>,
Michael Spang <spang@chromium.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Fedora Kernel Team <kernel-team@fedoraproject.org>
Subject: Re: USB keyboard backlight powering down.
Date: Wed, 17 Oct 2012 09:49:24 -0400 [thread overview]
Message-ID: <507EB764.2040105@verizon.net> (raw)
In-Reply-To: <20121017133151.GB2934@hansolo.jdub.homelinux.org>
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
next prev parent reply other threads:[~2012-10-17 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 15:20 USB keyboard backlight powering down Dave Jones
2012-10-16 16:45 ` Michael Spang
2012-10-16 16:54 ` Greg Kroah-Hartman
2012-10-16 17:35 ` Sarah Sharp
2012-10-17 12:55 ` Josh Boyer
2012-10-17 13:09 ` Gerry Reno
2012-10-17 13:31 ` Josh Boyer
2012-10-17 13:49 ` Gerry Reno [this message]
2012-10-16 17:29 ` Sarah Sharp
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=507EB764.2040105@verizon.net \
--to=greno@verizon.net \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=spang@chromium.org \
--cc=spang@google.com \
/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