bugGNU GRUB - Bugs: bug #47636, usb_keyboard does not like...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #47636: usb_keyboard does not like Logitech gaming keyboard

Submitter:  Ben Klein <man_in_shack>
Submitted:  Thu 07 Apr 2016 07:00:14 AM UTC
   
 
Category:  Booting Severity:  Major
Priority:  5 - Normal Item Group:  Hardware-specific
Status:  None Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Open Release:  Git master
Release:  Reproducibility:  Every Time
Planned Release:  2.03+

Thu 07 Apr 2016 08:07:47 AM UTC, comment #1: 

So I think the problem is that Grub expects the keyboard to be a USB 1.x device when it needs to be USB 2.0. I tried:

> insmod ahci
> set prefix=(ahci3,msdos1)/grub

# note I forgot the /grub in original submission but you get the idea

> insmod ehci
> insmod usb_keyboard


Neither the G510 or my generic USB keyboard functioned at this point (presumably because usb_keyboard doesn't talk to the ehci module), but no booting issues occurred either. lsmod showed Grub auto loaded usbms with ehci.

I also spotted Linux registering the G510 as a "full speed USB device" after loading ohci in Grub.

Ben Klein <man_in_shack>
Thu 07 Apr 2016 07:00:14 AM UTC, original submission:  

commit f4d35d49e32c29183b3492da18ea480d91716efe

Using nativedisk or loading ohci for USB keyboard support when my Logitech G510 gaming keyboard is plugged in causes some problem with the USB subsystem.

Steps to reproduce, while G510 is plugged in:

> nativedisk

OR

> insmod ahci
> set prefix=(ahci3,msdos1)
> insmod ohci


The symptoms are that the G510 is not fully initialised (should display the G510 logo on the built-in screen), the Grub does not accept input from the keyboard, and Linux hangs on USB device discovery with repeated message:
usb 4-3: device descriptor read/64, error -110

My generic USB keyboard does function correctly after loading nativedisk or ohci.

Boot eventually continues once the USB subsystem gives up on trying to identify and enumerate the keyboard.

After rebooting, either warm or cold, BIOS POST also runs slowly. The only remedy is to unplug the G510 or power off the PSU.

If Linux is booted using biosdisk (without loading ohci), or the keyboard is unplugged on boot and plugged in after the kernel loads, then the G510 keyboard works correctly.

It may be worth noting that lsusb -v shows the G510 is a USB2.0 device, not USB1.x as most keyboards are.

Ben Klein <man_in_shack>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by phcoder (Updated the item)
  • -email is unavailable- added by man_in_shack (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-03-05 phcoder Planned ReleaseNone 2.03+

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code