When not moving the cursor (touching the touch disk) during startup, the keyboard won't work (red bluetooth light on the keyboard). Either the cursor is moved during the startup process or the bluetooth usb receiver for the keyboard is unplugged and plugged in again when in gdm will make the keyboard work. This is not so in Fedora 7. I noticed this behavior with the last three or four kernels from rawhide, don't know if this behavior also showed up before. It's also the same with the current xen-kernel. So I don't think it's a kernel problem. But it is strange and it is not very comfortable.
For information: I did not do a clean install, instead I upgraded a former Fedora 7 installation.
Mario.
DI Mario Bruckschwaiger wrote:
When not moving the cursor (touching the touch disk) during startup, the keyboard won't work (red bluetooth light on the keyboard). Either the cursor is moved during the startup process or the bluetooth usb receiver for the keyboard is unplugged and plugged in again when in gdm will make the keyboard work. This is not so in Fedora 7. I noticed this behavior with the last three or four kernels from rawhide, don't know if this behavior also showed up before. It's also the same with the current xen-kernel. So I don't think it's a kernel problem. But it is strange and it is not very comfortable.
For information: I did not do a clean install, instead I upgraded a former Fedora 7 installation.
Sounds like the new usb autosuspend code is biting you, the device gets suspended because it isn't used for a while, you could try doing: echo "on" > /sys/bus/usb/devices/1-1/power/level
From /etc/rc.d/rc.local replacing 1-1 with the actual place where your usb receiver is.
Regards,
Hans
On Fri, 2007-09-21 at 17:05 +0200, Hans de Goede wrote:
Sounds like the new usb autosuspend code is biting you, the device gets suspended because it isn't used for a while, you could try doing: echo "on" > /sys/bus/usb/devices/1-1/power/level
From /etc/rc.d/rc.local replacing 1-1 with the actual place where your usb receiver is.
No, did not work. Same behavior as before.
DI Mario Bruckschwaiger wrote:
When not moving the cursor (touching the touch disk) during startup, the keyboard won't work (red bluetooth light on the keyboard). Either the cursor is moved during the startup process or the bluetooth usb receiver for the keyboard is unplugged and plugged in again when in gdm will make the keyboard work. This is not so in Fedora 7. I noticed this behavior with the last three or four kernels from rawhide, don't know if this behavior also showed up before. It's also the same with the current xen-kernel. So I don't think it's a kernel problem. But it is strange and it is not very comfortable.
For information: I did not do a clean install, instead I upgraded a former Fedora 7 installation.
Mario.
Could you provide some HardWare details.. Other than the keyboard...
Best regards. Johann B.
On Fri, 2007-09-21 at 15:10 +0000, "Jóhann B. Guðmundsson" wrote:
Could you provide some HardWare details.. Other than the keyboard...
Of course,
the cpu (from /proc/cpuinfo of a Fedora 7 installation) is an Intel dual core
vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) D CPU 2.66GHz stepping : 7 cpu MHz : 2676.291 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monito r ds_cpl tm2 cid cx16 xtpr lahf_lm bogomips : 5355.71 clflush size : 64
and from /proc/bus/usb/devices (also from the Fedora 7 installation)
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 3 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=0b04 Rev=49.00 S: Manufacturer=Logitech S: Product=Logitech BT Mini-Receiver C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=02 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=c713 Rev=49.00 S: Manufacturer=Logitech S: Product=Logitech BT Mini-Receiver S: SerialNumber=00076172342B C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
T: Bus=02 Lev=02 Prnt=03 Port=02 Cnt=02 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=c714 Rev=49.00 S: Manufacturer=Logitech S: Product=Logitech BT Mini-Receiver S: SerialNumber=00076172342B C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=2ms
Hope this helps, I can give you more info if needed.
Mario.
DI Mario Bruckschwaiger wrote:
On Fri, 2007-09-21 at 15:10 +0000, "Jóhann B. Guðmundsson" wrote:
Could you provide some HardWare details.. Other than the keyboard...
Of course,
the cpu (from /proc/cpuinfo of a Fedora 7 installation) is an Intel dual core
vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) D CPU 2.66GHz stepping : 7 cpu MHz : 2676.291 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monito r ds_cpl tm2 cid cx16 xtpr lahf_lm bogomips : 5355.71 clflush size : 64
and from /proc/bus/usb/devices (also from the Fedora 7 installation)
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 3 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=0b04 Rev=49.00 S: Manufacturer=Logitech S: Product=Logitech BT Mini-Receiver C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=02 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=c713 Rev=49.00 S: Manufacturer=Logitech S: Product=Logitech BT Mini-Receiver S: SerialNumber=00076172342B C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
T: Bus=02 Lev=02 Prnt=03 Port=02 Cnt=02 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=c714 Rev=49.00 S: Manufacturer=Logitech S: Product=Logitech BT Mini-Receiver S: SerialNumber=00076172342B C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=2ms
Hope this helps, I can give you more info if needed.
Mario.
Did you try what Hans suggested...
Sounds like the new usb autosuspend code is biting you, the device gets suspended because it isn't used for a while, you could try doing: echo "on" > /sys/bus/usb/devices/1-1/power/level
From /etc/rc.d/rc.local replacing 1-1 with the actual place where your usb receiver is.
Regards,
Hans
Good to know what motherboard you running.
And report if what Hans suggestsed fixes things...
Best regards Johann B.
On Fri, 2007-09-21 at 16:58 +0200, DI Mario Bruckschwaiger wrote:
When not moving the cursor (touching the touch disk) during startup, the keyboard won't work (red bluetooth light on the keyboard). Either the cursor is moved during the startup process or the bluetooth usb receiver for the keyboard is unplugged and plugged in again when in gdm will make the keyboard work. This is not so in Fedora 7. I noticed this behavior with the last three or four kernels from rawhide, don't know if this behavior also showed up before. It's also the same with the current xen-kernel. So I don't think it's a kernel problem. But it is strange and it is not very comfortable.
For information: I did not do a clean install, instead I upgraded a former Fedora 7 installation.
Is the host-side part of this hardware actually operating in Bluetooth mode? Is hcid running? Is the input service running? Are there interesting messages in /var/log/messages? What does 'hcidump -VX' show when you start typing?
On Fri, 2007-09-21 at 17:40 +0100, David Woodhouse wrote:
Is the host-side part of this hardware actually operating in Bluetooth mode? Is hcid running? Is the input service running? Are there interesting messages in /var/log/messages? What does 'hcidump -VX' show when you start typing?
Ok, bluetooth service is started but says "hcid is dead". And in the /var/log/messages there is the following:
The first part is the normal recognition of the bluetooth receiver, the second part are the warnings, and the last part is my unplugging and plugging-in of the receiver.
Sep 21 19:09:29 rock kernel: usb 3-2.2: configuration #1 chosen from 1 choice Sep 21 19:09:29 rock kernel: input: Logitech Logitech BT Mini-Receiver as /class/input/input1 Sep 21 19:09:29 rock kernel: input: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.1-2.2 Sep 21 19:09:29 rock kernel: ata1.00: configured for UDMA/33 Sep 21 19:09:29 rock kernel: usb 3-2.3: new full speed USB device using uhci_hcd and address 4 Sep 21 19:09:29 rock kernel: ata1.01: configured for UDMA/33 Sep 21 19:09:29 rock kernel: usb 3-2.3: configuration #1 chosen from 1 choice Sep 21 19:09:29 rock kernel: input: Logitech Logitech BT Mini-Receiver as /class/input/input2 Sep 21 19:09:29 rock kernel: input,hiddev96: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.1-2.3 ..... Sep 21 19:09:29 rock kernel: Bluetooth: Core ver 2.11 Sep 21 19:09:29 rock kernel: NET: Registered protocol family 31 Sep 21 19:09:29 rock kernel: Bluetooth: HCI device and connection manager initialized Sep 21 19:09:29 rock kernel: Bluetooth: HCI socket layer initialized Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: WARNING: at drivers/hid/hid-core.c:784 implement() (Not tainted) Sep 21 19:09:29 rock kernel: [<c0406463>] show_trace_log_lvl+0x1a/0x2f Sep 21 19:09:29 rock kernel: [<c0406e59>] show_trace+0x12/0x14 Sep 21 19:09:29 rock kernel: [<c0406e71>] dump_stack+0x16/0x18 Sep 21 19:09:29 rock kernel: [<c05b7df1>] hid_output_report+0x22b/0x2c3 Sep 21 19:09:29 rock kernel: [<c05bc586>] hid_submit_ctrl+0x57/0x1cf Sep 21 19:09:29 rock kernel: [<c05bc843>] usbhid_submit_report +0x145/0x168 Sep 21 19:09:29 rock kernel: [<c05beabe>] hiddev_ioctl+0x360/0x8d6 Sep 21 19:09:29 rock kernel: [<c0493f41>] do_ioctl+0x51/0x68 Sep 21 19:09:29 rock kernel: [<c04941a1>] vfs_ioctl+0x249/0x25c Sep 21 19:09:29 rock kernel: [<c04941fd>] sys_ioctl+0x49/0x64 Sep 21 19:09:29 rock kernel: [<c040522e>] syscall_call+0x7/0xb Sep 21 19:09:29 rock kernel: ======================= Sep 21 19:09:29 rock kernel: Bluetooth: L2CAP ver 2.8 Sep 21 19:09:29 rock kernel: Bluetooth: L2CAP socket layer initialized Sep 21 19:09:29 rock kernel: Bluetooth: RFCOMM socket layer initialized Sep 21 19:09:29 rock kernel: Bluetooth: RFCOMM TTY layer initialized Sep 21 19:09:29 rock kernel: Bluetooth: RFCOMM ver 1.8 Sep 21 19:09:29 rock kernel: usb 3-2.1: new full speed USB device using uhci_hcd and address 5 Sep 21 19:09:29 rock kernel: usb 3-2.1: configuration #1 chosen from 1 choice Sep 21 19:09:29 rock kernel: Bluetooth: HCI USB driver ver 2.9 Sep 21 19:09:29 rock kernel: usbcore: registered new interface driver hci_usb ..... Sep 21 19:09:58 rock kernel: usb 3-2: USB disconnect, address 2 Sep 21 19:09:58 rock kernel: usb 3-2.1: USB disconnect, address 5 Sep 21 19:09:58 rock kernel: usb 3-2.2: USB disconnect, address 3 Sep 21 19:09:58 rock kernel: usb 3-2.3: USB disconnect, address 4 Sep 21 19:10:01 rock kernel: usb 3-2: new full speed USB device using uhci_hcd and address 6 Sep 21 19:10:01 rock kernel: usb 3-2: configuration #1 chosen from 1 choice Sep 21 19:10:01 rock kernel: hub 3-2:1.0: USB hub found Sep 21 19:10:01 rock kernel: hub 3-2:1.0: 3 ports detected Sep 21 19:10:01 rock kernel: usb 3-2.2: new full speed USB device using uhci_hcd and address 7 Sep 21 19:10:01 rock kernel: usb 3-2.2: configuration #1 chosen from 1 choice Sep 21 19:10:01 rock kernel: input: Logitech Logitech BT Mini-Receiver as /class/input/input5 Sep 21 19:10:01 rock kernel: input: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.1-2.2 Sep 21 19:10:02 rock kernel: usb 3-2.3: new full speed USB device using uhci_hcd and address 8 Sep 21 19:10:02 rock kernel: usb 3-2.3: configuration #1 chosen from 1 choice Sep 21 19:10:02 rock kernel: input: Logitech Logitech BT Mini-Receiver as /class/input/input6 Sep 21 19:10:02 rock kernel: input,hiddev96: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.1-2.3 Sep 21 19:10:08 rock gdm-binary[2729]: GLib-CRITICAL: g_key_file_get_string: assertion `key_file != NULL' failed Sep 21 19:10:08 rock gdm-binary[2729]: GLib-CRITICAL: g_key_file_get_string: assertion `key_file != NULL' failed Sep 21 19:10:08 rock gdm-binary[2729]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed