Logitech G510 doesn't work while booting

[timothy-s-dev]

I recently set up Linux Mint to dual-boot along side Windows 7, and nearly everything is working smoothly (barring some issues with Skype). However, the keyboard doesn't seem to work between the time I power on the computer, and an OS reaches it's login screen, be it Windows 7 or Linux Mint. It's a USB keyboard (Logitech G510), but my older USB Acer keyboard works just fine. Legacy USB support was already on in the BIOS when I went to check it after some searching. I think this is likely because the keyboard uses a special driver to manage the LCD screen, but I don't recall needing the other keyboard to reach the boot menu to launch Mint from CD, though my memory may just be failing me.

Any input or suggestions for other places to look would be most appreciated,
Timothy Sassone

[/Zoran\]

I also encountered on some computers that USB keyboards don't work up until login screen. It's most probably because of the keyboard itself, like you said. That's why it wise to have a PS/2 keyboard and mouse lying around to use in cases such as this.
cheers

[timothy-s-dev]

I used my USB Acer keyboard instead to manage GRUB and other boot-time input. It's not that it's USB input, there's some difference between the Logitech G510 and the older USB Acer keyboard.

[richyrich]

Something you might want to take a look at ? . . I don't know if your model is related to Logitech's G15, but a search for logitech in Synaptic's Package Manager will show you some interesting applications, including apps and plugins for the keyboard lcd.

[timothy-s-dev]

I'm having to work from Windows for the evening, until I can get some of this fixed, but thanks for the heads up, sounds interesting. That said, unless one of them starts when the BIOS does instead of when Linux Mint does, it's not going to solve the problem.

Thanks,
Timothy S.

[richyrich]

Take a stroll through the Log File Viewer, notably through the dmesg, xorg, and messages logs. They have time code along the left, and the most recent boot of the day is appended to the bottom of the file.
If you do find something unusual, or an error message, you can copy/paste the log file back here (or your other post). It's easier reading, and takes less space if you paste it inside a Code box in your reply.
Posting your complete dmesg log right after a fresh boot may show what is happening with your usb detection and hardware drivers.

[Yuritau]

I'm having the same problem with my Razer Lycosa keyboard. It works just fine before the boot loader (accessing BIOS), and after boot loader. It's only during the 10 seconds it gives me to choose which OS to load that the keyboard is unresponsive.

EDIT: Well that was a silly and easy fix, for me anyways. My BIOS (MSI K7N2 Delta) had "USB Keyboard Support" set to disabled. Don't know how I didn't run into that sooner.

[timothy-s-dev]

Code: Select all

[   64.361826] udev[556]: starting version 163
[   64.368731] lp: driver loaded but no devices found
[   64.382097] xhci_hcd 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   64.382135] xhci_hcd 0000:02:00.0: setting latency timer to 64
[   64.382137] xhci_hcd 0000:02:00.0: xHCI Host Controller
[   64.382212] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 8
[   64.382743] xhci_hcd 0000:02:00.0: irq 17, io mem 0xfd6fe000
[   64.392045] usb usb8: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
[   64.392133] xHCI xhci_add_endpoint called for root hub
[   64.392135] xHCI xhci_check_bandwidth called for root hub
[   64.392322] hub 8-0:1.0: USB hub found
[   64.392322] hub 8-0:1.0: 4 ports detected
[   64.410812] EDAC MC: Ver: 2.1.0 Sep 19 2010
[   64.418169] ACPI: resource piix4_smbus [io  0x0b00-0x0b07] conflicts with ACPI region SOR1 [mem 0x00000b00-0x00000b0f window]
[   64.418169] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   64.428458] Adding 15361020k swap on /dev/sdb3.  Priority:-1 extents:1 across:15361020k
[   64.431484] EDAC amd64_edac:  Ver: 3.3.0 Sep 19 2010
[   64.433441] EDAC amd64: This node reports that Memory ECC is currently disabled, set F3x44[22] (0000:00:18.3).
[   64.433441] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
[   64.433441]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
[   64.433441]  (Note that use of the override may cause unknown side effects.)
[   64.433441] amd64_edac: probe of 0000:00:18.2 failed with error -22
[   64.458230] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   64.556175] hda_codec: ALC892: BIOS auto-probing.
[   64.562256] Too many connections
[   64.564483] HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[   64.564485] hda_intel: Disable MSI for Nvidia chipset
[   64.564561] HDA Intel 0000:01:00.1: setting latency timer to 64
[   64.712015] usb 8-3: new high speed USB device using xhci_hcd and address 0
[   64.734853] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   64.735507] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   64.735659] usb 8-3: ep 0x81 - rounding interval to 2048 microframes
[   64.736391] hub 8-3:1.0: USB hub found
[   64.736835] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   64.736965] hub 8-3:1.0: 4 ports detected
[   64.801721] EXT4-fs (sdb2): re-mounted. Opts: errors=remount-ro
[   64.861374] usb 8-4: new full speed USB device using xhci_hcd and address 0
[   64.893170] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
[   64.895163] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
[   64.897163] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
[   64.944165] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   64.953173] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   64.959164] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   64.980282] input: Logitech G510 Gaming Keyboard as /devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb8/8-4/8-4:1.0/input/input5
[   64.980315] generic-usb 0003:046D:C22E.0004: input,hidraw3: USB HID v1.11 Keyboard [Logitech G510 Gaming Keyboard] on usb-0000:02:00.0-4/input0
[   65.011170] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.019169] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.023057] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.029118] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.035119] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.040104] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.044172] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.048170] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.052107] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.088121] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.098273] input: Logitech G510 Gaming Keyboard as /devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb8/8-4/8-4:1.1/input/input6
[   65.098366] generic-usb 0003:046D:C22E.0005: input,hiddev96,hidraw4: USB HID v1.11 Device [Logitech G510 Gaming Keyboard] on usb-0000:02:00.0-4/input1
[   65.112175] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.118202] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.123216] 3:4:1: endpoint lacks sample rate attribute bit, cannot set.
[   65.135891] r8169 0000:03:00.0: eth0: link up
[   65.135895] r8169 0000:03:00.0: eth0: link up
[   65.168125] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
[   65.170119] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
[   65.182489] usb 8-3.3: new high speed USB device using xhci_hcd and address 0
[   65.341112] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.344284] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep
[   65.345366] usb 8-3.3: ep 0x87 - rounding interval to 128 microframes
[   65.351973] Linux video capture interface: v2.00
[   65.353644] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0824)
[   65.370120] input: UVC Camera (046d:0824) as /devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb8/8-3/8-3.3/8-3.3:1.0/input/input7
[   65.370152] usbcore: registered new interface driver uvcvideo
[   65.370153] USB Video Class driver (v0.1.0)

To be entirely honest, I'm not really sure what I'm looking for, although there are a surprising number of warning here.... I tried formatting and starting over with no luck. When I try to install the updates it looks like it's trying to run (the window shows up on the toolbar) but it eventually just stops and disappears, leaving me with a mouse that doesn't click at all (after the earlier focus issues I was having, perhaps it's giving focus to the window that never opens?) At the moment, I'm having to post with just the keyboard, so my appologies if more of the log was posted than necessary.

Let me know if there's anything else you'd need to know, I'm honestly not sure what it is I'm looking for, and I'm not having any luck just messing with it Dx

Timothy S.

[timothy-s-dev]

I'm getting the "Cannot grab your mouse" errors. But after a fresh install nothing has changed. I immediately lose the ability to click if I try to lauch the update center, and generally lose it anyways eventually. Any ideas? The inability to use basic input devices here is making things somewhat tricky

Tim

[bugmenotprettyplz]

Same issue here on the Logitech G510. My second generation Logitech G15 works fine on the same system (and USB port).

Bear in mind the G510 has the LCD screen and inbuilt sound card. That will probably have an effect.

[Darkthefox]

I had this problem too, I got around it but unplugging my headset from the keyboard. I had this problem after switching boards which makes me think it is a bios related issue.