I am using a ArchLinux distribution. `uname -a` gives me:
Linux torre 5.4.87-1-lts #1 SMP Wed, 06 Jan 2021 14:56:05 + x86_64
GNU/Linux
So, some months ago, my USB Keyboard stopped being detected at
boot. I mean, eventually got detected, after the 9 seconds timeout and
this is a bit
Hi Benjamin, Nestor,
On Tue, 2018-03-06 at 00:31 +0100, Florent Flament wrote:
> On Mon, 2018-03-05 at 18:26 +0100, Benjamin Tissoires wrote:
> > Hi Florent,
>
> Hi Benjamin,
>
> >
> > On Mon, Mar 5, 2018 at 10:31 AM, Nestor Lopez Casado
> > wrote:
> > > Hello
Hi Benjamin, Nestor,
On Tue, 2018-03-06 at 00:31 +0100, Florent Flament wrote:
> On Mon, 2018-03-05 at 18:26 +0100, Benjamin Tissoires wrote:
> > Hi Florent,
>
> Hi Benjamin,
>
> >
> > On Mon, Mar 5, 2018 at 10:31 AM, Nestor Lopez Casado
> > wrote:
> > > Hello Florent,
> > >
> > > In my
On Mon, 2018-03-05 at 18:26 +0100, Benjamin Tissoires wrote:
> Hi Florent,
Hi Benjamin,
>
> On Mon, Mar 5, 2018 at 10:31 AM, Nestor Lopez Casado
> wrote:
> > Hello Florent,
> >
> > In my view, this driver may not be a good idea. The default
> > behaviour
> > of K290
On Mon, 2018-03-05 at 18:26 +0100, Benjamin Tissoires wrote:
> Hi Florent,
Hi Benjamin,
>
> On Mon, Mar 5, 2018 at 10:31 AM, Nestor Lopez Casado
> wrote:
> > Hello Florent,
> >
> > In my view, this driver may not be a good idea. The default
> > behaviour
> > of K290 is 'send multimedia
On Mon, 2018-03-05 at 10:31 +0100, Nestor Lopez Casado wrote:
> Hello Florent,
Hi Nestor,
> In my view, this driver may not be a good idea. The default behaviour
> of K290 is 'send multimedia keycodes' with the user given the choice
> to change that behaviour via vendor commands. Putting a
On Mon, 2018-03-05 at 10:31 +0100, Nestor Lopez Casado wrote:
> Hello Florent,
Hi Nestor,
> In my view, this driver may not be a good idea. The default behaviour
> of K290 is 'send multimedia keycodes' with the user given the choice
> to change that behaviour via vendor commands. Putting a
/commits/Florent-Flament/Logitech-K290-Add-driver-for-the-Logitech-K290-USB-keyboard/20180305-153311
base: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next
config: tile-allyesconfig (attached as .config)
compiler: tilegx-linux-gcc (GCC) 7.2.0
reproduce:
wget
https
/commits/Florent-Flament/Logitech-K290-Add-driver-for-the-Logitech-K290-USB-keyboard/20180305-153311
base: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next
config: tile-allyesconfig (attached as .config)
compiler: tilegx-linux-gcc (GCC) 7.2.0
reproduce:
wget
https
Hi Florent,
On Mon, Mar 5, 2018 at 10:31 AM, Nestor Lopez Casado
wrote:
> Hello Florent,
>
> In my view, this driver may not be a good idea. The default behaviour
> of K290 is 'send multimedia keycodes' with the user given the choice
> to change that behaviour via
Hi Florent,
On Mon, Mar 5, 2018 at 10:31 AM, Nestor Lopez Casado
wrote:
> Hello Florent,
>
> In my view, this driver may not be a good idea. The default behaviour
> of K290 is 'send multimedia keycodes' with the user given the choice
> to change that behaviour via vendor commands. Putting a
-ci/linux/commits/Florent-Flament/Logitech-K290-Add-driver-for-the-Logitech-K290-USB-keyboard/20180305-153311
base: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF
-ci/linux/commits/Florent-Flament/Logitech-K290-Add-driver-for-the-Logitech-K290-USB-keyboard/20180305-153311
base: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF
Hello Florent,
In my view, this driver may not be a good idea. The default behaviour
of K290 is 'send multimedia keycodes' with the user given the choice
to change that behaviour via vendor commands. Putting a driver that
will unconditionally change that behaviour without the user's consent
might
Hello Florent,
In my view, this driver may not be a good idea. The default behaviour
of K290 is 'send multimedia keycodes' with the user given the choice
to change that behaviour via vendor commands. Putting a driver that
will unconditionally change that behaviour without the user's consent
might
K290: Add driver for the Logitech K290 USB keyboard
drivers/hid/Kconfig | 18
drivers/hid/Makefile| 1 +
drivers/hid/hid-ids.h | 1 +
drivers/hid/hid-logitech-k290.c | 100
4 files changed, 120 insertions
K290: Add driver for the Logitech K290 USB keyboard
drivers/hid/Kconfig | 18
drivers/hid/Makefile| 1 +
drivers/hid/hid-ids.h | 1 +
drivers/hid/hid-logitech-k290.c | 100
4 files changed, 120 insertions
With the generic HID driver, K290 keyboards' F1 to F12 keys send
multimedia events by default, and standard keycodes when the function
key is pressed. This driver allows to configure K290 keyboards, so
that F1 to F12 have a standard behavior and send multimedia events
when the function key is
With the generic HID driver, K290 keyboards' F1 to F12 keys send
multimedia events by default, and standard keycodes when the function
key is pressed. This driver allows to configure K290 keyboards, so
that F1 to F12 have a standard behavior and send multimedia events
when the function key is
With the generic HID driver, K290 keyboards' F1 to F12 keys send
multimedia events by default, and standard keycodes when the function
key is pressed. This driver allows to configure K290 keyboards, so
that F1 to F12 have a standard behavior and send multimedia events
when the function key is
With the generic HID driver, K290 keyboards' F1 to F12 keys send
multimedia events by default, and standard keycodes when the function
key is pressed. This driver allows to configure K290 keyboards, so
that F1 to F12 have a standard behavior and send multimedia events
when the function key is
On Sat, 2018-03-03 at 18:08 +0200, Andy Shevchenko wrote:
> On Sat, Mar 3, 2018 at 12:04 AM, Florent Flament
> wrote:
> > With the generic HID driver, K290 keyboards' F1 to F12 keys send
> > multimedia events by default, and standard keycodes when the
> > function
> >
On Sat, 2018-03-03 at 18:08 +0200, Andy Shevchenko wrote:
> On Sat, Mar 3, 2018 at 12:04 AM, Florent Flament
> wrote:
> > With the generic HID driver, K290 keyboards' F1 to F12 keys send
> > multimedia events by default, and standard keycodes when the
> > function
> > key is pressed. This driver
On Sat, Mar 3, 2018 at 12:04 AM, Florent Flament
wrote:
> With the generic HID driver, K290 keyboards' F1 to F12 keys send
> multimedia events by default, and standard keycodes when the function
> key is pressed. This driver allows to configure K290 keyboards, so
>
On Sat, Mar 3, 2018 at 12:04 AM, Florent Flament
wrote:
> With the generic HID driver, K290 keyboards' F1 to F12 keys send
> multimedia events by default, and standard keycodes when the function
> key is pressed. This driver allows to configure K290 keyboards, so
> that F1 to F12 have a standard
With the generic HID driver, K290 keyboards' F1 to F12 keys send
multimedia events by default, and standard keycodes when the function
key is pressed. This driver allows to configure K290 keyboards, so
that F1 to F12 have a standard behavior and send multimedia events
when the function key is
With the generic HID driver, K290 keyboards' F1 to F12 keys send
multimedia events by default, and standard keycodes when the function
key is pressed. This driver allows to configure K290 keyboards, so
that F1 to F12 have a standard behavior and send multimedia events
when the function key is
On Sun, Oct 22, 2017 at 08:04:49PM +0200, Damien Wyart wrote:
> >>> - is evdev driver in your kernel compiled as a module?
>
> >> Yes, it is.
>
> > OK, so this must be module loading issue that I missed. Just to
> > confirm, if you "modprobe evdev" it all starts to work?
>
> Yes, I confirm
On Sun, Oct 22, 2017 at 08:04:49PM +0200, Damien Wyart wrote:
> >>> - is evdev driver in your kernel compiled as a module?
>
> >> Yes, it is.
>
> > OK, so this must be module loading issue that I missed. Just to
> > confirm, if you "modprobe evdev" it all starts to work?
>
> Yes, I confirm
>>> - is evdev driver in your kernel compiled as a module?
>> Yes, it is.
> OK, so this must be module loading issue that I missed. Just to
> confirm, if you "modprobe evdev" it all starts to work?
Yes, I confirm loading the module by hand makes everything work ok.
Thanks for your replies!
>>> - is evdev driver in your kernel compiled as a module?
>> Yes, it is.
> OK, so this must be module loading issue that I missed. Just to
> confirm, if you "modprobe evdev" it all starts to work?
Yes, I confirm loading the module by hand makes everything work ok.
Thanks for your replies!
On Sun, Oct 22, 2017 at 10:27 AM, Damien Wyart wrote:
>>> Should that commit be reverted for now? Maybe other people will be
>>> able to reproduce it?
>
> On Sun, Oct 22, 2017 at 6:37 PM, Dmitry Torokhov
> wrote:
>> Hm, that is not good. A few
On Sun, Oct 22, 2017 at 10:27 AM, Damien Wyart wrote:
>>> Should that commit be reverted for now? Maybe other people will be
>>> able to reproduce it?
>
> On Sun, Oct 22, 2017 at 6:37 PM, Dmitry Torokhov
> wrote:
>> Hm, that is not good. A few question before we decide to revert:
>
>> - do your
>> Should that commit be reverted for now? Maybe other people will be
>> able to reproduce it?
On Sun, Oct 22, 2017 at 6:37 PM, Dmitry Torokhov
wrote:
> Hm, that is not good. A few question before we decide to revert:
> - do your devices work on text console?
Yes,
>> Should that commit be reverted for now? Maybe other people will be
>> able to reproduce it?
On Sun, Oct 22, 2017 at 6:37 PM, Dmitry Torokhov
wrote:
> Hm, that is not good. A few question before we decide to revert:
> - do your devices work on text console?
Yes, they do.
> - can you post
On Sun, Oct 22, 2017 at 8:46 AM, Damien Wyart wrote:
> Hi,
>
> Having compiled a kernel today (bfc1168de949c in Linus' tree), I
> noticed keyboard and mouse were not working at all (stuck at X DM
> level).
>
> After digging a bit, I realized only one change in the recent
On Sun, Oct 22, 2017 at 8:46 AM, Damien Wyart wrote:
> Hi,
>
> Having compiled a kernel today (bfc1168de949c in Linus' tree), I
> noticed keyboard and mouse were not working at all (stuck at X DM
> level).
>
> After digging a bit, I realized only one change in the recent input
> commits was quite
Hi,
Having compiled a kernel today (bfc1168de949c in Linus' tree), I
noticed keyboard and mouse were not working at all (stuck at X DM
level).
After digging a bit, I realized only one change in the recent input
commits was quite general, and bingo, reverting "allow matching device
IDs on
Hi,
Having compiled a kernel today (bfc1168de949c in Linus' tree), I
noticed keyboard and mouse were not working at all (stuck at X DM
level).
After digging a bit, I realized only one change in the recent input
commits was quite general, and bingo, reverting "allow matching device
IDs on
On Wed, 23 Jul 2014 23:30:48 +0100
Jamie Lentin wrote:
> Add support for both ThinkPad Compact Bluetooth Keyboard with
> TrackPoint and ThinkPad Compact USB Keyboard with TrackPoint.
>
> Signed-off-by: Jamie Lentin
I think this version is OK, thanks.
Reviewed-by: An
On Wed, 23 Jul 2014 23:30:48 +0100
Jamie Lentin j...@lentin.co.uk wrote:
Add support for both ThinkPad Compact Bluetooth Keyboard with
TrackPoint and ThinkPad Compact USB Keyboard with TrackPoint.
Signed-off-by: Jamie Lentin j...@lentin.co.uk
I think this version is OK, thanks.
Reviewed
Add support for both ThinkPad Compact Bluetooth Keyboard with
TrackPoint and ThinkPad Compact USB Keyboard with TrackPoint.
Signed-off-by: Jamie Lentin
---
Documentation/ABI/testing/sysfs-driver-hid-lenovo | 12 ++
drivers/hid/Kconfig | 2 +
drivers/hid/hid
Add support for both ThinkPad Compact Bluetooth Keyboard with
TrackPoint and ThinkPad Compact USB Keyboard with TrackPoint.
Signed-off-by: Jamie Lentin j...@lentin.co.uk
---
Documentation/ABI/testing/sysfs-driver-hid-lenovo | 12 ++
drivers/hid/Kconfig | 2
tact:linux-in...@vger.kernel.org
> Description: This controls if mouse clicks should be generated if the
> trackpoint is quickly pressed. How fast this press has to be
> is being controlled by press_speed.
> Values are 0 or 1.
> +
Description: This controls if mouse clicks should be generated if the
trackpoint is quickly pressed. How fast this press has to be
is being controlled by press_speed.
Values are 0 or 1.
+ Applies to Thinkpad USB Keyboard with TrackPoint.
What
to be
is being controlled by press_speed.
Values are 0 or 1.
+ Applies to Thinkpad USB Keyboard with TrackPoint.
What: /sys/bus/usb/devices/-:./::./dragging
Date: July 2011
Contact: linux-in...@vger.kernel.org
Description
this press has to be
is being controlled by press_speed.
Values are 0 or 1.
+ Applies to Thinkpad USB Keyboard with TrackPoint.
What: /sys/bus/usb/devices/busnum-devnum:config num.interface
num/hid-bus:vendor-id:product-id.num/dragging
Date
> --- a/drivers/hid/Kconfig
> +++ b/drivers/hid/Kconfig
> @@ -334,6 +334,8 @@ config HID_LENOVO
> Thinkpad standalone keyboards, e.g:
> - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and
> trackpoint
> configuration)
> + - ThinkPad
--- a/drivers/hid/Kconfig
+++ b/drivers/hid/Kconfig
@@ -334,6 +334,8 @@ config HID_LENOVO
Thinkpad standalone keyboards, e.g:
- ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and
trackpoint
configuration)
+ - ThinkPad Compact Bluetooth Keyboard with TrackPoint
a/drivers/hid/Kconfig b/drivers/hid/Kconfig
index dd07d59..48b4777 100644
--- a/drivers/hid/Kconfig
+++ b/drivers/hid/Kconfig
@@ -334,6 +334,8 @@ config HID_LENOVO
Thinkpad standalone keyboards, e.g:
- ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and
trackpoint
(+)
diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
index dd07d59..48b4777 100644
--- a/drivers/hid/Kconfig
+++ b/drivers/hid/Kconfig
@@ -334,6 +334,8 @@ config HID_LENOVO
Thinkpad standalone keyboards, e.g:
- ThinkPad USB Keyboard with TrackPoint (supports extra LEDs
On Fri, 13 Jun 2014, Antonio Ospite wrote:
> > Previously the tpkbd driver had various functions marked "_tp" to indicate
> > that it's for the "mouse" half of the keyboard as the kernel sees it,
> > however it does nothing special with the keyboard half. I was intending
> > (somewhat
ctkbd ? :)
> ...and lenovo_input_mapping switches between them
>
> The latter seems a bit too invasive, but I'm not sure how obvious with the
> former that it'd be that the "Compact USB keyboard" is in-fact a
> compactkbd not a usbkbd. The former is probably what I'll go for unless
>
be that the Compact USB keyboard is in-fact a
compactkbd not a usbkbd. The former is probably what I'll go for unless
you have any thoughts.
[...]
Ciao,
Antonio
--
Antonio Ospite
http://ao2.it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki
On Fri, 13 Jun 2014, Antonio Ospite wrote:
Previously the tpkbd driver had various functions marked _tp to indicate
that it's for the mouse half of the keyboard as the kernel sees it,
however it does nothing special with the keyboard half. I was intending
(somewhat sloppily) to
3bec9f5..1671e7a 100644
--- a/drivers/hid/hid-lenovo-tpkbd.c
+++ b/drivers/hid/hid-lenovo-tpkbd.c
@@ -1,8 +1,11 @@
/*
* HID driver for Lenovo:-
* * ThinkPad USB Keyboard with TrackPoint
+ * * ThinkPad Compact Bluetooth Keyboard with TrackPoint
+ * * ThinkPad Compact USB Keyboard
/drivers/hid/hid-lenovo-tpkbd.c
index 3bec9f5..1671e7a 100644
--- a/drivers/hid/hid-lenovo-tpkbd.c
+++ b/drivers/hid/hid-lenovo-tpkbd.c
@@ -1,8 +1,11 @@
/*
* HID driver for Lenovo:-
* * ThinkPad USB Keyboard with TrackPoint
+ * * ThinkPad Compact Bluetooth Keyboard with TrackPoint
+ * * ThinkPad
s/hid/hid-lenovo-tpkbd.c b/drivers/hid/hid-lenovo-tpkbd.c
> index 3bec9f5..1671e7a 100644
> --- a/drivers/hid/hid-lenovo-tpkbd.c
> +++ b/drivers/hid/hid-lenovo-tpkbd.c
> @@ -1,8 +1,11 @@
> /*
> * HID driver for Lenovo:-
> * * ThinkPad USB Keyboard with TrackP
/drivers/hid/hid-lenovo-tpkbd.c
@@ -1,8 +1,11 @@
/*
* HID driver for Lenovo:-
* * ThinkPad USB Keyboard with TrackPoint
+ * * ThinkPad Compact Bluetooth Keyboard with TrackPoint
+ * * ThinkPad Compact USB Keyboard with TrackPoint
Use - as the bullet.
*
* Copyright (c) 2012
0x0064
diff --git a/drivers/hid/hid-lenovo-tpkbd.c b/drivers/hid/hid-lenovo-tpkbd.c
index 3bec9f5..1671e7a 100644
--- a/drivers/hid/hid-lenovo-tpkbd.c
+++ b/drivers/hid/hid-lenovo-tpkbd.c
@@ -1,8 +1,11 @@
/*
* HID driver for Lenovo:-
* * ThinkPad USB Keyboard with TrackPoint
+ * * ThinkPad
USB_DEVICE_ID_LG_MULTITOUCH0x0064
diff --git a/drivers/hid/hid-lenovo-tpkbd.c b/drivers/hid/hid-lenovo-tpkbd.c
index 3bec9f5..1671e7a 100644
--- a/drivers/hid/hid-lenovo-tpkbd.c
+++ b/drivers/hid/hid-lenovo-tpkbd.c
@@ -1,8 +1,11 @@
/*
* HID driver for Lenovo:-
* * ThinkPad USB Keyboard with TrackPoint
On Mon, 2014-02-17 at 21:23 +0800, Daniel J Blueman wrote:
> Across 5+ years of kernels, I've been seeing occasional (1-2 times per
> day) key-stuck issues where eg a fn+delete combo repeats delete until
> I press delete again. I've seen this happen with fn+ctrl+left, leaving
> left held and
On Mon, 2014-02-17 at 21:23 +0800, Daniel J Blueman wrote:
Across 5+ years of kernels, I've been seeing occasional (1-2 times per
day) key-stuck issues where eg a fn+delete combo repeats delete until
I press delete again. I've seen this happen with fn+ctrl+left, leaving
left held and likewise
some USB
> HID instrumentation to locate this issue over time. Without apriori
> knowledge of the linux USB input stack, what is a good initial
> approach?
I've seen some similar behavior on servers connected to a KVM switch
(USB keyboard/mouse) where without apparent reason the ENTER key b
Across 5+ years of kernels, I've been seeing occasional (1-2 times per
day) key-stuck issues where eg a fn+delete combo repeats delete until
I press delete again. I've seen this happen with fn+ctrl+left, leaving
left held and likewise with right.
This has occurred on Apple laptops, external USB
Across 5+ years of kernels, I've been seeing occasional (1-2 times per
day) key-stuck issues where eg a fn+delete combo repeats delete until
I press delete again. I've seen this happen with fn+ctrl+left, leaving
left held and likewise with right.
This has occurred on Apple laptops, external USB
to locate this issue over time. Without apriori
knowledge of the linux USB input stack, what is a good initial
approach?
I've seen some similar behavior on servers connected to a KVM switch
(USB keyboard/mouse) where without apparent reason the ENTER key became
pressed and did continuously send
I do have a ThinkPad T420 with external VGA monitor + USB keyboard.
Till 3.9.4 I just can press the enter button at the external keyboard to
wake up a system. With 3.10.rcX however this won#t work any more.
However short) open and close the LID works.
Known issue ? (Because bisecting this can't
I do have a ThinkPad T420 with external VGA monitor + USB keyboard.
Till 3.9.4 I just can press the enter button at the external keyboard to
wake up a system. With 3.10.rcX however this won#t work any more.
However short) open and close the LID works.
Known issue ? (Because bisecting this can't
On Thu, 18 Oct 2012, Martin Vysny wrote:
> Good day,
>thank you for your response, please see the answers below.
>
>
> On 10/17/2012 08:05 PM, Alan Stern wrote:
> > On Wed, 17 Oct 2012, Martin Vysny wrote:
> >
> >> Good day,
> >> thank you for your mail. I was finally able to reproduce
Good day,
thank you for your response, please see the answers below.
On 10/17/2012 08:05 PM, Alan Stern wrote:
On Wed, 17 Oct 2012, Martin Vysny wrote:
Good day,
thank you for your mail. I was finally able to reproduce the issue. I
am attaching a dmesg output of a correct boot (please
Good day,
thank you for your response, please see the answers below.
On 10/17/2012 08:05 PM, Alan Stern wrote:
On Wed, 17 Oct 2012, Martin Vysny wrote:
Good day,
thank you for your mail. I was finally able to reproduce the issue. I
am attaching a dmesg output of a correct boot (please
On Thu, 18 Oct 2012, Martin Vysny wrote:
Good day,
thank you for your response, please see the answers below.
On 10/17/2012 08:05 PM, Alan Stern wrote:
On Wed, 17 Oct 2012, Martin Vysny wrote:
Good day,
thank you for your mail. I was finally able to reproduce the issue. I
On Wed, 17 Oct 2012, Martin Vysny wrote:
> Good day,
>thank you for your mail. I was finally able to reproduce the issue. I
> am attaching a dmesg output of a correct boot (please note that there
> still are several unwanted IRQs), and a dmesg output of a reproduced error.
Did you boot
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
, 2012 at 11:20 AM, Dave Jones wrote:
>>>>> Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
>>>>> Logitech USB keyboard doesn't light up until he hits a key, and then
>>>>> it immediately powers back off, defeating the purpose of having a
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
ry (CC'd) reported a bug to us that since 3.6.1, his illuminated
> > > > Logitech USB keyboard doesn't light up until he hits a key, and then
> > > > it immediately powers back off, defeating the purpose of having an
> > > > illumated keyboard.
> > >
to us that since 3.6.1, his illuminated
Logitech USB keyboard doesn't light up until he hits a key, and then
it immediately powers back off, defeating the purpose of having an
illumated keyboard.
Looking over the 3.6.1 changelog, I see this change, which sounds
like it might
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,
...@redhat.com wrote:
Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
Logitech USB keyboard doesn't light up until he hits a key, and then
it immediately powers back off, defeating the purpose of having an
illumated keyboard.
Looking over the 3.6.1 changelog, I see this change, which
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
On Wed, 17 Oct 2012, Martin Vysny wrote:
Good day,
thank you for your mail. I was finally able to reproduce the issue. I
am attaching a dmesg output of a correct boot (please note that there
still are several unwanted IRQs), and a dmesg output of a reproduced error.
Did you boot with
On Tue, Oct 16, 2012 at 09:54:36AM -0700, Greg Kroah-Hartman wrote:
> On Tue, Oct 16, 2012 at 12:45:56PM -0400, Michael Spang wrote:
> > On Tue, Oct 16, 2012 at 11:20 AM, Dave Jones wrote:
> > > Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
> >
On Tue, Oct 16, 2012 at 11:20:23AM -0400, Dave Jones wrote:
> Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
> Logitech USB keyboard doesn't light up until he hits a key, and then
> it immediately powers back off, defeating the purpose of having an
> illumated key
On Tue, Oct 16, 2012 at 12:45:56PM -0400, Michael Spang wrote:
> On Tue, Oct 16, 2012 at 11:20 AM, Dave Jones wrote:
> > Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
> > Logitech USB keyboard doesn't light up until he hits a key, and then
> > it immedi
On Tue, Oct 16, 2012 at 11:20 AM, Dave Jones wrote:
> Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
> Logitech USB keyboard doesn't light up until he hits a key, and then
> it immediately powers back off, defeating the purpose of having an
> illumated keyboard.
Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
Logitech USB keyboard doesn't light up until he hits a key, and then
it immediately powers back off, defeating the purpose of having an
illumated keyboard.
Looking over the 3.6.1 changelog, I see this change, which sounds
like
Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
Logitech USB keyboard doesn't light up until he hits a key, and then
it immediately powers back off, defeating the purpose of having an
illumated keyboard.
Looking over the 3.6.1 changelog, I see this change, which sounds
like
On Tue, Oct 16, 2012 at 11:20 AM, Dave Jones da...@redhat.com wrote:
Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
Logitech USB keyboard doesn't light up until he hits a key, and then
it immediately powers back off, defeating the purpose of having an
illumated keyboard
On Tue, Oct 16, 2012 at 12:45:56PM -0400, Michael Spang wrote:
On Tue, Oct 16, 2012 at 11:20 AM, Dave Jones da...@redhat.com wrote:
Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
Logitech USB keyboard doesn't light up until he hits a key, and then
it immediately powers
On Tue, Oct 16, 2012 at 11:20:23AM -0400, Dave Jones wrote:
Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
Logitech USB keyboard doesn't light up until he hits a key, and then
it immediately powers back off, defeating the purpose of having an
illumated keyboard.
Does he
On Tue, Oct 16, 2012 at 09:54:36AM -0700, Greg Kroah-Hartman wrote:
On Tue, Oct 16, 2012 at 12:45:56PM -0400, Michael Spang wrote:
On Tue, Oct 16, 2012 at 11:20 AM, Dave Jones da...@redhat.com wrote:
Gerry (CC'd) reported a bug to us that since 3.6.1, his illuminated
Logitech USB keyboard
On Fri, Sep 14, 2012 at 12:49:45PM +0300, Marti Raudsepp wrote:
> After installing an old 100Mbit PCI Ethernet card to my machine, it has
> complained a few times about spurious interrupts ("nobody cared") at a
> random time of the day. After the oops is reported, my USB keyboa
Hi lists,
After installing an old 100Mbit PCI Ethernet card to my machine, it has
complained a few times about spurious interrupts ("nobody cared") at a
random time of the day. After the oops is reported, my USB keyboard (HP
smart card keyboard) stops working properly -- it has lot
Hi lists,
After installing an old 100Mbit PCI Ethernet card to my machine, it has
complained a few times about spurious interrupts (nobody cared) at a
random time of the day. After the oops is reported, my USB keyboard (HP
smart card keyboard) stops working properly -- it has lots of delay
On Fri, Sep 14, 2012 at 12:49:45PM +0300, Marti Raudsepp wrote:
After installing an old 100Mbit PCI Ethernet card to my machine, it has
complained a few times about spurious interrupts (nobody cared) at a
random time of the day. After the oops is reported, my USB keyboard (HP
smart card
On Friday, September 07, 2012 05:12:18 PM Jiri Kosina wrote:
> On Thu, 30 Aug 2012, Andres Freund wrote:
> > > With a quick grep I just discovered that a new driver for this (or
> > > similar?) keyboards has been added. I have *not* compiled this in
> > > though: +# CONFIG_HID_LENOVO_TPKBD is not
On Thu, 30 Aug 2012, Andres Freund wrote:
> > With a quick grep I just discovered that a new driver for this (or
> > similar?) keyboards has been added. I have *not* compiled this in though:
> > +# CONFIG_HID_LENOVO_TPKBD is not set
> >
> > Is the new, unconditional, entry in the
On Thu, 30 Aug 2012, Andres Freund wrote:
With a quick grep I just discovered that a new driver for this (or
similar?) keyboards has been added. I have *not* compiled this in though:
+# CONFIG_HID_LENOVO_TPKBD is not set
Is the new, unconditional, entry in the hid_have_special_driver
1 - 100 of 231 matches
Mail list logo