11:24 a.m.
I have a system that functions as a PVR, and is re-booted daily. There have been no recent
updates. On yesterday's reboot (and subsequently) the kernel does not recognize A/N
keystrokes from the KBD. Mousepad motions and clicks work fine. Looking at the dmesg
output, there appears to be nothing amiss. When I move the USB transceiver to another
system, everything works as it should.
Suggestions? Thanks.
11:33 a.m.
New subject: USB keybord curiosity
On 09/30/2014 03:21:59 PM, Ed Greshko wrote:
On 10/01/14 05:44, Geoffrey Leach wrote:
> What follows is the log output from dmesg and Xorg.0.log. I think
this establishes that the keyboard is properly recognized by X and the
kernel. (But what do I know?) The question is: is there something
running that is grabbing keystrokes? Or, alternatively, some process
that should be passing keystrokes to X, but isn't? Keep in mind that
plugged into another system, the keyboard functions correctly.
When you move the transceiver to the failing system are you always
using the same USB port? If you have a desktop system with USB ports
on the front and back they are often on different USB hubs. Have you
tried moving to a different port and, if possible, hub?
Follow-up to my previous reply. Booted from a vendor-supplied test disk. Keyboard worked
fine in their Ubuntu disto. So, it would appear that there's an X-driver component
that's been trashed, no? And, if so, how would I find it, or am I looking at a full
re-load?
6:07 p.m.
New subject: USB keybord curiosity
On 09/30/2014 03:21:59 PM, Ed Greshko wrote:
On 10/01/14 05:44, Geoffrey Leach wrote:
> What follows is the log output from dmesg and Xorg.0.log. I think
this establishes that the keyboard is properly recognized by X and the
kernel. (But what do I know?) The question is: is there something
running that is grabbing keystrokes? Or, alternatively, some process
that should be passing keystrokes to X, but isn't? Keep in mind that
plugged into another system, the keyboard functions correctly.
When you move the transceiver to the failing system are you always
using the same USB port? If you have a desktop system with USB ports
on the front and back they are often on different USB hubs. Have you
tried moving to a different port and, if possible, hub?
On the failing system (Intel DH77DF) I have tried the transceiver on 3 USB-2.0 ports and 1
USB 3.0 port. Result always the same. I don't have a desktop. On the laptop the port
that yielded the 'correct' result was USB-2.0
5:21 p.m.
New subject: USB keybord curiosity
On 10/01/14 05:44, Geoffrey Leach wrote:
What follows is the log output from dmesg and Xorg.0.log. I think
this establishes that the keyboard is properly recognized by X and the kernel. (But what
do I know?) The question is: is there something running that is grabbing keystrokes? Or,
alternatively, some process that should be passing keystrokes to X, but isn't? Keep
in mind that plugged into another system, the keyboard functions correctly.
When you move the transceiver to the failing system are you always using the same USB
port? If you have a desktop system with USB ports on the front and back they are often on
different USB hubs. Have you tried moving to a different port and, if possible, hub?
--
If you can't laugh at yourself, others will gladly oblige.
4:44 p.m.
New subject: USB keybord curiosity
On 09/30/2014 02:21:34 PM, Geoffrey Leach wrote:
<snip> Reply found (properly) at !end
> On Tue, Sep 30, 2014 at 9:58 AM, Geoffrey Leach
<geoff(a)hughes.net>
> wrote:
>
> > Corrected subject.
> >
> > On 09/30/2014 09:24:31 AM, Geoffrey Leach wrote:
> > > I have a system that functions as a PVR, and is re-booted daily.
> There
> > > have been no recent updates. On yesterday's reboot (and
> subsequently)
> > > the kernel does not recognize A/N keystrokes from the KBD.
> Mousepad
> > > motions and clicks work fine. Looking at the dmesg output, there
> > > appears to be nothing amiss. When I move the USB transceiver to
> > > another system, everything works as it should.
> > >
> > > Suggestions? Thanks.
What follows is the log output from dmesg and Xorg.0.log. I think this establishes that
the keyboard is properly recognized by X and the kernel. (But what do I know?) The
question is: is there something running that is grabbing keystrokes? Or, alternatively,
some process that should be passing keystrokes to X, but isn't? Keep in mind that
plugged into another system, the keyboard functions correctly.
And I am truly sorry for cluttering the list with all this junk!
DMESG
[ 9854.519710] usb 1-1.4: USB disconnect, device number 3
[ 9877.550485] usb 1-1.3: new full-speed USB device number 4 using ehci_hcd
[ 9877.638854] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c52b
[ 9877.638858] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9877.638860] usb 1-1.3: Product: USB Receiver
[ 9877.638862] usb 1-1.3: Manufacturer: Logitech
[ 9877.645417] logitech-djreceiver 0003:046D:C52B.0007: hiddev0,hidraw0: USB HID v1.11
Device [Logitech USB Receiver] on usb-0000:00:1a.0-1.3/input2
[ 9877.647869] input: Logitech Unifying Device. Wireless PID:400e as
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/0003:046D:C52B.0007/input/input11
[ 9877.648126] logitech-djdevice 0003:046D:C52B.0008: input,hidraw1: USB HID v1.11
Keyboard [Logitech Unifying Device. Wireless PID:400e] on usb-0000:00:1a.0-1.3:1
Xorg.0.log
[ 31.147] (II) LoadModule: "evdev"
[ 31.147] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[ 31.148] (II) Module evdev: vendor="X.Org Foundation"
[ 31.148] compiled for 1.12.0, module version = 2.7.0
[ 31.148] Module class: X.Org XInput Driver
[ 31.148] ABI class: X.Org XInput driver, version 16.0
[ 31.148] (II) Using input driver 'evdev' for 'Power Button'
[ 31.148] Option "XkbRules" "evdev"
[ 31.148] Option "XkbModel" "pc105+inet"
[ 31.148] Option "XkbLayout" "us"
[ 31.148] Option "_source" "server/udev"
[ 31.148] Option "name" "Power Button"
[ 31.148] Option "path" "/dev/input/event1"
[ 31.148] Option "device" "/dev/input/event1"
[ 31.148] Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 31.148] Option "driver" "evdev"
[ 31.148] Option "XkbOptions" "terminate:ctrl_alt_bksp,"
[ 31.148] (**) Power Button: always reports core events
[ 31.148] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 31.148] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 31.148] (--) evdev: Power Button: Found keys
[ 31.148] (II) evdev: Power Button: Configuring as keyboard
[ 31.148] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 31.148] (II) XINPUT: Adding extended input device "Power Button" (type:
KEYBOARD, id 6)
[ 31.148] (**) Option "xkb_rules" "evdev"
[ 31.148] (**) Option "xkb_model" "pc105+inet"
[ 31.148] (**) Option "xkb_layout" "us"
[ 31.148] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[ 31.169] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[ 31.169] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 31.169] (**) Video Bus: Applying InputClass "system-setup-keyboard"
[ 31.169] (II) Using input driver 'evdev' for 'Video Bus'
[ 31.169] Option "XkbRules" "evdev"
[ 31.169] Option "XkbModel" "pc105+inet"
[ 31.169] Option "XkbLayout" "us"
[ 31.169] Option "_source" "server/udev"
[ 31.169] Option "name" "Video Bus"
[ 31.169] Option "path" "/dev/input/event3"
[ 31.169] Option "device" "/dev/input/event3"
[ 31.169] Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input3/event3"
[ 31.169] Option "driver" "evdev"
[ 31.169] Option "XkbOptions" "terminate:ctrl_alt_bksp,"
[ 31.169] (**) Video Bus: always reports core events
[ 31.169] (**) evdev: Video Bus: Device: "/dev/input/event3"
[ 31.169] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 31.169] (--) evdev: Video Bus: Found keys
[ 31.169] (II) evdev: Video Bus: Configuring as keyboard
[ 31.148] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 31.148] (II) XINPUT: Adding extended input device "Power Button" (type:
KEYBOARD, id 6)
[ 31.148] (**) Option "xkb_rules" "evdev"
[ 31.148] (**) Option "xkb_model" "pc105+inet"
[ 31.148] (**) Option "xkb_layout" "us"
[ 31.148] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[ 31.169] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[ 31.169] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 31.169] (**) Video Bus: Applying InputClass "system-setup-keyboard"
[ 31.169] (II) Using input driver 'evdev' for 'Video Bus'
[ 31.169] Option "XkbRules" "evdev"
[ 31.169] Option "XkbModel" "pc105+inet"
[ 31.169] Option "XkbLayout" "us"
[ 31.169] Option "_source" "server/udev"
[ 31.169] Option "name" "Video Bus"
[ 31.169] Option "path" "/dev/input/event3"
[ 31.169] Option "device" "/dev/input/event3"
[ 31.169] Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input3/event3"
[ 31.169] Option "driver" "evdev"
[ 31.169] Option "XkbOptions" "terminate:ctrl_alt_bksp,"
[ 31.169] (**) Video Bus: always reports core events
[ 31.169] (**) evdev: Video Bus: Device: "/dev/input/event3"
[ 31.169] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 31.169] (--) evdev: Video Bus: Found keys
[ 31.169] (II) evdev: Video Bus: Configuring as keyboard
[ 31.169] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input3/event3"
[ 31.169] (II) XINPUT: Adding extended input device "Video Bus" (type:
KEYBOARD, id 7)
[ 31.169] (**) Option "xkb_rules" "evdev"
[ 31.169] (**) Option "xkb_model" "pc105+inet"
[ 31.169] (**) Option "xkb_layout" "us"
[ 31.169] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[ 31.169] (II) XKB: Reusing cached keymap
[ 31.169] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 31.169] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 31.169] (**) Power Button: Applying InputClass "system-setup-keyboard"
[ 31.169] (II) Using input driver 'evdev' for 'Power Button'
[ 31.169] Option "XkbRules" "evdev"
[ 31.169] Option "XkbModel" "pc105+inet"
[ 31.169] Option "XkbLayout" "us"
[ 31.169] Option "_source" "server/udev"
[ 31.169] Option "name" "Power Button"
[ 31.169] Option "path" "/dev/input/event0"
[ 31.169] Option "device" "/dev/input/event0"
[ 31.169] Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 31.170] Option "driver" "evdev"
[ 31.170] Option "XkbOptions" "terminate:ctrl_alt_bksp,"
[ 31.170] (**) Power Button: always reports core events
[ 31.170] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 31.170] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 31.170] (--) evdev: Power Button: Found keys
[ 31.170] (II) evdev: Power Button: Configuring as keyboard
[ 31.170] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 31.170] (II) XINPUT: Adding extended input device "Power Button" (type:
KEYBOARD, id 8)
[ 31.170] (**) Option "xkb_rules" "evdev"
[ 31.170] (**) Option "xkb_model" "pc105+inet"
[ 31.170] (**) Option "xkb_layout" "us"
[ 31.170] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[ 31.170] (II) XKB: Reusing cached keymap
[ 31.170] (II) config/udev: Adding input device Logitech Unifying Device. Wireless
PID:400e (/dev/input/event2)
[ 31.170] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"evdev pointer catchall"
[ 31.170] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"evdev keyboard catchall"
[ 31.170] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"system-setup-keyboard"
[ 31.170] (II) Using input driver 'evdev' for 'Logitech Unifying Device.
Wireless PID:400e'
[ 31.170] Option "XkbRules" "evdev"
[ 31.170] Option "XkbModel" "pc105+inet"
[ 31.170] Option "XkbLayout" "us"
[ 31.170] Option "_source" "server/udev"
[ 31.170] Option "name" "Logitech Unifying Device. Wireless
PID:400e"
[ 31.170] Option "path" "/dev/input/event2"
[ 31.170] Option "device" "/dev/input/event2"
[ 31.170] Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/input/input2/event2"
[ 31.170] Option "driver" "evdev"
[ 31.170] Option "XkbOptions" "terminate:ctrl_alt_bksp,"
[ 31.170] (**) Logitech Unifying Device. Wireless PID:400e: always reports core events
[ 31.170] (**) evdev: Logitech Unifying Device. Wireless PID:400e: Device:
"/dev/input/event2"
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: absolute axis 0x20
[652..1]
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Vendor 0x46d Product
0xc52b
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found 20 mouse
buttons
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found scroll
wheel(s)
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found relative axes
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found x and y
relative axes
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found absolute axes
[ 31.171] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Forcing absolute x/y
axes to exist.
[ 31.171] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found keys
[ 31.171] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Configuring as
mouse
[ 31.171] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Configuring as
keyboard
[ 31.171] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Adding scrollwheel
support
[ 31.171] (**) evdev: Logitech Unifying Device. Wireless PID:400e: YAxisMapping:
buttons 4 and 5
[ 31.171] (**) evdev: Logitech Unifying Device. Wireless PID:400e: EmulateWheelButton:
4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 31.171] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/input/input2/event2"
[ 31.171] (II) XINPUT: Adding extended input device "Logitech Unifying Device.
Wireless PID:400e" (type: KEYBOARD, id 9)
[ 31.171] (**) Option "xkb_rules" "evdev"
[ 31.171] (**) Option "xkb_model" "pc105+inet"
[ 31.171] (**) Option "xkb_layout" "us"
[ 31.171] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[ 31.171] (II) XKB: Reusing cached keymap
[ 31.171] (II) evdev: Logitech Unifying Device. Wireless PID:400e: initialized for
relative axes.
[ 31.171] (WW) evdev: Logitech Unifying Device. Wireless PID:400e: ignoring absolute
axes.
[ 31.171] (**) Logitech Unifying Device. Wireless PID:400e: (accel) keeping
acceleration scheme 1
[ 31.171] (**) Logitech Unifying Device. Wireless PID:400e: (accel) acceleration
profile 0
[ 31.171] (**) Logitech Unifying Device. Wireless PID:400e: (accel) acceleration
factor: 2.000
[ 31.171] (**) Logitech Unifying Device. Wireless PID:400e: (accel) acceleration
threshold: 4
[ 31.172] (II) config/udev: Adding input device Logitech Unifying Device. Wireless
PID:400e (/dev/input/mouse0)
[ 31.172] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"system-setup-keyboard"
[ 31.172] (II) No input driver specified, ignoring this device.
[ 31.172] (II) This device may have been added with another device file.
[ 31.172] (II) config/udev: Adding input device HDA Intel PCH Line Out Front
(/dev/input/event10)
[ 31.172] (II) No input driver specified, ignoring this device.
[ 31.172] (II) This device may have been added with another device file.
[ 31.172] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7
(/dev/input/event4)
[ 31.172] (II) No input driver specified, ignoring this device.
[ 31.172] (II) This device may have been added with another device file.
[ 31.172] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3
(/dev/input/event5)
[ 31.172] (II) No input driver specified, ignoring this device.
[ 31.172] (II) This device may have been added with another device file.
[ 31.173] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
[ 31.173] (II) No input driver specified, ignoring this device.
[ 31.173] (II) This device may have been added with another device file.
[ 31.173] (II) config/udev: Adding input device HDA Intel PCH Rear Mic
(/dev/input/event7)
[ 31.173] (II) No input driver specified, ignoring this device.
[ 31.173] (II) This device may have been added with another device file.
[ 31.173] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE
(/dev/input/event8)
[ 31.173] (II) No input driver specified, ignoring this device.
[ 31.173] (II) This device may have been added with another device file.
[ 31.173] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround
(/dev/input/event9)
[ 31.173] (II) No input driver specified, ignoring this device.
[ 31.173] (II) This device may have been added with another device file.
[ 31.353] (II) intel(0): EDID vendor "SNY", prod id 12289
[ 31.353] (II) intel(0): Using EDID range info for horizontal sync
[ 31.353] (II) intel(0): Using EDID range info for vertical refresh
[ 31.353] (II) intel(0): Printing DDC gathered Modelines:
[ 31.353] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052
2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 31.353] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650
720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 31.353] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052
2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[ 31.353] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480
489 495 525 -hsync -vsync (31.5 kHz e)
[ 31.353] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602
1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[ 31.353] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056
600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 31.353] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480
490 492 525 -hsync -vsync (31.5 kHz e)
[ 31.353] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344
768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 31.353] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440
1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 31.353] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576
581 586 625 -hsync -vsync (31.2 kHz e)
[ 31.353] (II) intel(0): Modeline "1440x240"x0.0 27.00 1440 1478 1602 1716
240 244 247 262 -hsync -vsync (15.7 kHz e)
[ 31.353] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2448 2492
2640 1080 1084 1089 1125 +hsync +vsync (28.1 kHz e)
[ 32.339] (II) intel(0): EDID vendor "SNY", prod id 12289
[ 32.339] (II) intel(0): Using hsync ranges from config file
[ 32.339] (II) intel(0): Using vrefresh ranges from config file
[ 32.339] (II) intel(0): Printing DDC gathered Modelines:
[ 32.339] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052
2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 32.339] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650
720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 32.339] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052
2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[ 32.339] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480
489 495 525 -hsync -vsync (31.5 kHz e)
[ 32.339] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602
1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[ 32.339] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056
600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 32.339] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480
490 492 525 -hsync -vsync (31.5 kHz e)
[ 32.339] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344
768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 32.339] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440
1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 32.339] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576
581 586 625 -hsync -vsync (31.2 kHz e)
[ 32.339] (II) intel(0): Modeline "1440x240"x0.0 27.00 1440 1478 1602 1716
240 244 247 262 -hsync -vsync (15.7 kHz e)
[ 32.339] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2448 2492
2640 1080 1084 1089 1125 +hsync +vsync (28.1 kHz e)
[ 9856.974] (II) config/udev: removing device Logitech Unifying Device. Wireless
PID:400e
[ 9856.974] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Close
[ 9856.974] (II) UnloadModule: "evdev"
[ 9880.093] (II) config/udev: Adding input device Logitech Unifying Device. Wireless
PID:400e (/dev/input/mouse0)
[ 9880.093] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"system-setup-keyboard"
[ 9880.093] (II) No input driver specified, ignoring this device.
[ 9880.093] (II) This device may have been added with another device file.
[ 9880.093] (II) config/udev: Adding input device Logitech Unifying Device. Wireless
PID:400e (/dev/input/event2)
[ 9880.093] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"evdev pointer catchall"
[ 9880.093] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"evdev keyboard catchall"
[ 9880.093] (**) Logitech Unifying Device. Wireless PID:400e: Applying InputClass
"system-setup-keyboard"
[ 9880.093] (II) Using input driver 'evdev' for 'Logitech Unifying Device.
Wireless PID:400e'
[ 9880.093] Option "XkbRules" "evdev"
[ 9880.093] Option "XkbModel" "pc105+inet"
[ 9880.093] Option "XkbLayout" "us"
[ 9880.093] Option "_source" "server/udev"
[ 9880.093] Option "name" "Logitech Unifying Device. Wireless
PID:400e"
[ 9880.093] Option "path" "/dev/input/event2"
[ 9880.093] Option "device" "/dev/input/event2"
[ 9880.093] Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/0003:046D:C52B.0007/input/input11/event2"
[ 9880.093] Option "driver" "evdev"
[ 9880.093] Option "XkbOptions" "terminate:ctrl_alt_bksp,"
[ 9880.094] (**) Logitech Unifying Device. Wireless PID:400e: always reports core events
[ 9880.094] (**) evdev: Logitech Unifying Device. Wireless PID:400e: Device:
"/dev/input/event2"
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: absolute axis 0x20
[652..1]
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Vendor 0x46d Product
0xc52b
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found 20 mouse
buttons
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found scroll
wheel(s)
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found relative axes
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found x and y
relative axes
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found absolute axes
[ 9880.094] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Forcing absolute x/y
axes to exist.
[ 9880.094] (--) evdev: Logitech Unifying Device. Wireless PID:400e: Found keys
[ 9880.094] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Configuring as
mouse
[ 9880.094] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Configuring as
keyboard
[ 9880.094] (II) evdev: Logitech Unifying Device. Wireless PID:400e: Adding scrollwheel
support
[ 9880.094] (**) evdev: Logitech Unifying Device. Wireless PID:400e: YAxisMapping:
buttons 4 and 5
[ 9880.094] (**) evdev: Logitech Unifying Device. Wireless PID:400e: EmulateWheelButton:
4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 9880.094] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/0003:046D:C52B.0007/input/input11/event2"
[ 9880.094] (II) XINPUT: Adding extended input device "Logitech Unifying Device.
Wireless PID:400e" (type: KEYBOARD, id 9)
[ 9880.094] (**) Option "xkb_rules" "evdev"
[ 9880.094] (**) Option "xkb_model" "pc105+inet"
[ 9880.094] (**) Option "xkb_layout" "us"
[ 9880.094] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[ 9880.094] (II) XKB: Reusing cached keymap
[ 9880.094] (II) evdev: Logitech Unifying Device. Wireless PID:400e: initialized for
relative axes.
[ 9880.094] (WW) evdev: Logitech Unifying Device. Wireless PID:400e: ignoring absolute
axes.
[ 9880.094] (**) Logitech Unifying Device. Wireless PID:400e: (accel) keeping
acceleration scheme 1
[ 9880.094] (**) Logitech Unifying Device. Wireless PID:400e: (accel) acceleration
profile 0
[ 9880.094] (**) Logitech Unifying Device. Wireless PID:400e: (accel) acceleration
factor: 2.000
[ 9880.094] (**) Logitech Unifying Device. Wireless PID:400e: (accel) acceleration
threshold: 4
4:21 p.m.
New subject: USB keybord curiosity
Ah, yes. The old, "My lunch ate the computer issue!" Well, I would have denided
the possibility, but in this case I would have been supported by the evidence.
Shaking the keyboard upside-down and thoroughly dusting resulted in no change. As did
cleaning the USB dongle and the slot.
So, thanks for the suggestion. I'm still stumped!
On 09/30/2014 12:21:39 PM, Tod Merley wrote:
I tend to think HW rather than SW. If it were me I would remove the
key
board, shake it upside down and work the keys in that position while
puffing with dust off periodically from various angles.
Probably good to shoot some dust off into the USB connectors - perhaps
change the connector used in the computer, and consider using some
shaped
stiff card stock covered by a bit of old white T shirt slightly wet
and
then dry (or with some 99% (or at least 90% no lanolin) isopropyl
alcohol)
to clean the inside of the connector finishing with a dry rub and dust
off.
Might also be a good time to badblock the disk if appropriate (that is
- if
it is not SSD).
Virus root kit scan. Possible system re-load. If still no joy
consider
replacement.
On Tue, Sep 30, 2014 at 9:58 AM, Geoffrey Leach <geoff(a)hughes.net>
wrote:
> Corrected subject.
>
> On 09/30/2014 09:24:31 AM, Geoffrey Leach wrote:
> > I have a system that functions as a PVR, and is re-booted daily.
There
> > have been no recent updates. On yesterday's reboot (and
subsequently)
> > the kernel does not recognize A/N keystrokes from the KBD.
Mousepad
> > motions and clicks work fine. Looking at the dmesg output, there
> > appears to be nothing amiss. When I move the USB transceiver to
> > another system, everything works as it should.
> >
> > Suggestions? Thanks.
> > --
> > users mailing list
> > users(a)lists.fedoraproject.org
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
> >
>
>
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
------quoted attachment------
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
2:21 p.m.
New subject: USB keybord curiosity
I tend to think HW rather than SW. If it were me I would remove the key
board, shake it upside down and work the keys in that position while
puffing with dust off periodically from various angles.
Probably good to shoot some dust off into the USB connectors - perhaps
change the connector used in the computer, and consider using some shaped
stiff card stock covered by a bit of old white T shirt slightly wet and
then dry (or with some 99% (or at least 90% no lanolin) isopropyl alcohol)
to clean the inside of the connector finishing with a dry rub and dust off.
Might also be a good time to badblock the disk if appropriate (that is - if
it is not SSD).
Virus root kit scan. Possible system re-load. If still no joy consider
replacement.
On Tue, Sep 30, 2014 at 9:58 AM, Geoffrey Leach <geoff(a)hughes.net> wrote:
Corrected subject.
On 09/30/2014 09:24:31 AM, Geoffrey Leach wrote:
> I have a system that functions as a PVR, and is re-booted daily. There
> have been no recent updates. On yesterday's reboot (and subsequently)
> the kernel does not recognize A/N keystrokes from the KBD. Mousepad
> motions and clicks work fine. Looking at the dmesg output, there
> appears to be nothing amiss. When I move the USB transceiver to
> another system, everything works as it should.
>
> Suggestions? Thanks.
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
11:58 a.m.
New subject: USB keybord curiosity
Corrected subject.
On 09/30/2014 09:24:31 AM, Geoffrey Leach wrote:
I have a system that functions as a PVR, and is re-booted daily.
There
have been no recent updates. On yesterday's reboot (and subsequently)
the kernel does not recognize A/N keystrokes from the KBD. Mousepad
motions and clicks work fine. Looking at the dmesg output, there
appears to be nothing amiss. When I move the USB transceiver to
another system, everything works as it should.
Suggestions? Thanks.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
3488
days inactive
3489
days old
7 comments
3 participants
participants (3)
-
Ed Greshko -
Geoffrey Leach -
Tod Merley