USB Keyboard not working

[F5inet]

When trying to install using an USB Keyboard or a USB to PS/2 mouse&keyboard combo the splash screen don't recognize the keyboard, making impossible to 'press enter' to install ubuntu or type anything.

if you plug a PS/2 keyboard, all is working fine, and once is installed, you can plug again your USB keyboard and is working fine, too...

[Colin Watson (cjwatson)]

I suspect you need to fiddle with your BIOS; it may need a flash upgrade to handle USB keyboards properly.

[F5inet (f5inet)]

i don't think so, the bios is detecting and working with USB Dongle &
keyboard (USB Keyboard Support is enabled in BIOS setup). DOS is working
properly if I install it. i can navigate in the BIOS setup with USB
keyboard...

seems to be an error in grub/lilo keyboard management...

¿maybe a bug in grub?

i can do an usb dump, so you can view the info. anyway, i currently run
ubuntu breezy. after install, the keyboard is working properly...

2006/3/19, Colin Watson <email address hidden>:
>
> Public bug report changed:
> https://launchpad.net/malone/bugs/35530
>
> Task: ubuntu base-installer
> Sourcepackagename: base-installer => gfxboot
> Binarypackagename: base-installer => None
>
> Comment:
> I suspect you need to fiddle with your BIOS; it may need a flash upgrade
> to handle USB keyboards properly.
>

--
Una delgada linea nos separa, yo la llamo... 'Talento'

[Colin Watson (cjwatson)]

On Sun, Mar 19, 2006 at 05:03:05PM -0000, F5inet wrote:
> i don't think so, the bios is detecting and working with USB Dongle &
> keyboard (USB Keyboard Support is enabled in BIOS setup). DOS is working
> properly if I install it. i can navigate in the BIOS setup with USB
> keyboard...

OK. Unfortunately I have no USB keyboard hardware so I don't know if
this is a fundamental limitation in syslinux/gfxboot or not.

> seems to be an error in grub/lilo keyboard management...

That's kind of impossible since grub is not used when booting from the
CD. This is why I reassigned the bug to gfxboot, although it could be
syslinux instead.

[Tollef Fog Heen (tfheen)]

I have a problem which somewhat resembles this. When doing a fresh boot, grub or syslinux refuses keyboard input, but only if the shutdown at the previous boot was unexpected, such as pressing the reset button.

Does my experience match yours, original submitter?

[F5inet (f5inet)]

no. my USB keyboard don't work on grub/install menu. i can do a LSUSB, and
you can view it...

this is the relevant line:
Bus 001 Device 002: ID 04b4:8081 Cypress Semiconductor Corp.

a USB Mouse/keyboard combo in a USB 1.1 controler. this work VERY GOOD in
MSWindows, inside linux (i am typing now with this in ubuntu breezy) and in
MSDOS (yeah, in DOS too). but don't work in grub/install menu of ANY
GRAPHICAL INSTALLATION (a diskette direct boot and install debian works
well)

sorry for the spam...
----------------> LSUSB <-------------------------------

Bus 005 Device 001: ID 0000:0000
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 1 Single TT
  bMaxPacketSize0 8
  idVendor 0x0000
  idProduct 0x0000
  bcdDevice 2.06
  iManufacturer 3 Linux 2.6.12-10-686 ehci_hcd
  iProduct 2 VIA Technologies, Inc. USB 2.0
  iSerial 1 0000:00:0c.2
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 9 Hub
      bInterfaceSubClass 0 Unused
      bInterfaceProtocol 0
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0002 1x 2 bytes
        bInterval 12
Hub Descriptor:
  bLength 9
  bDescriptorType 41
  nNbrPorts 4
  wHubCharacteristic 0x000a
    No power switching (usb 1.0)
    Per-port overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood 10 * 2 milli seconds
  bHubContrCurrent 0 milli Ampere
  DeviceRemovable 0x48
  PortPwrCtrlMask 0x80
 Hub Port Status:
   Port 1: 0000.0100 power
   Port 2: 0000.0100 power
   Port 3: 0000.0100 power
   Port 4: 0000.0100 power

Bus 004 Device 001: ID 0000:0000
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x0000
  idProduct 0x0000
  bcdDevice 2.06
  iManufacturer 3 Linux 2.6.12-10-686 uhci_hcd
  iProduct 2 VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1Controller (#4)
  iSerial 1 0000:00:0c.1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength ...

[Simon Wong (wongy)]

Same problem for me with the new Dapper graphical boot menu.

USB keyboard works in BIOS configuration so boot USB support is working.

When the graphical boot menu with installation/memory test etc options comes up the USB keyboard does not work.

I plugged in a PS/2 keyboard and it worked fine.

Once the text based installer was running the USB keyboard worked OK.

I do not have the PC details on me but will append when I get them (PIII 800MHz, Intel motherboard, USB mouse/keyboard combo with Belkin USB KVM switch - works with several other machines with Ubuntu no probs).

[Laurens Simonis (laurens.s)]

I have this bug too on a Dell Precision WorkStation 220, tried with Flight 7. Exactly the same thing.

[Carthik Sharma (carthik)]

Confirmed by another user.

[GreySim (greysim)]

Confirmed by another user using a "macally" USB keyboard on a Dell tower using a Dapper CD from Shipit. Works in BIOS, works post-install, doesn't work in the menu for the LiveCD. This unfortunately makes the LiveCD *near-useless* for me, as it's impossible to get a persistant session if the keyboard isn't working to pass the proper options for it. :(

[F5inet (f5inet)]

confirmed from me in dapper from shipit. USB keyboard doesn't work in
graphical menu install.

i upgraded from breezy to dapper. run flawlessly inside dapper.

2006/7/27, GreySim <email address hidden>:
>
> Confirmed by another user using a "macally" USB keyboard on a Dell tower
> using a Dapper CD from Shipit. Works in BIOS, works post-install,
> doesn't work in the menu for the LiveCD. This unfortunately makes the
> LiveCD *near-useless* for me, as it's impossible to get a persistant
> session if the keyboard isn't working to pass the proper options for it.
> :(
>
> --
> USB Keyboard not working
> https://launchpad.net/bugs/35530
>

--
Una delgada linea nos separa, yo la llamo... 'Talento'

[foster (ichhaisse)]

The problem is still unsolved in Version 7.04.

I have to wait the count-down out as the usb keyboard won't work during the choice of CD boot menu.

[F5inet (f5inet)]

ubuntu feisty solves this bug for me. graphical menu is working now.

to everybody that have this problem: do a 'lsusb' and paste here.

2007/6/11, foster <email address hidden>:
>
> The problem is still unsolved in Version 7.04.
>
> I have to wait the count-down out as the usb keyboard won't work during
> the choice of CD boot menu.
>
> --
> USB Keyboard not working
> https://bugs.launchpad.net/bugs/35530
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Una delgada linea nos separa, yo la llamo... 'Talento'

[SilverWave (silverwave)]

Work Around: Changing BIOS setting :
Pheonix Awardbios > integrated peripherals > on-chip PCI device > USB keyboard support vis > set this to BIOS from the OS default.

Saitek2 usb keyboard.

[kmurray (kwmbak)]

Me too. I tried out the Tribe 4 and Tribe 5 releases, and the keyboard is non-responsive at the boot menu; as described above. The same CDs boot just fine on other machines.

Hardware is a Dell XPS410N (Ubuntu pre-installed), with BIOS revision 2.4.2. Someday soon I'll work up the courage to flash the BIOS to the latest rev (2.5.1), which I expect will effect a cure. What's strange is that the standard 7.04 CD works as expected, as does Knoppix 5.something. Perhaps something in SYSLINUX has changed?

For the time being, holding down the shift key while booting is an effective workaround.

(see also Mandriva bug 31360)

[kmurray (kwmbak)]

gah!

I meant mandriva bug 31630

http://qa.mandriva.com/show_bug.cgi?id=31630

[Loe Spee (lgespee)]

I have the same problem with a new Dell PC, it has no PS/2 ports, so there is no way for me to work around it like that.

The keyboard works fine in the BIOS itself and during boot, but in the menu that appears when booting a LiveCD it doesn't work.
(I have this behavior on Ubuntu 7.10 RC.)
However the Ubuntu 7.04 LiveCD works fine, and does recognize the keyboard.

I hope this will be fixed before the final release in two days. It is a real show stopper, since it's impossible to install Ubuntu now with the nice LiveCD.

[taim1 (maztaim-deactivatedaccount)]

Same problem here with 7.10 install CD, JEOS install CD, Server CD, Alternative CD. This only seems to be a problem when attempting to start initially from CD. Once you wait on the countdown (on those images that HAVE countdowns), it loads fine and USB keyboard works fine. I have fiddled with what settings I can in BIOS to no avail. I have the latest BIOS from Dell for a Dimension E510.

[xoc (xoctor)]

Same problem here with 7.04 and 7.10 live or alternative CDs on a Dell Dimension E520. Unplugging and reinserting the keyboard USB plug does not help. Older versions of Ubuntu work, strangely enough.

[Tim Bosse (timbosse)]

Although not a solution to the ACTUAL bug, you can work around this by holding down the <shift> key on your keyboard at the POST screens until you are prompted "Load boot graphics (y/n)? y". Select "n" for no. From there you will have to create the boot command manually. I recommend using a combination of "F1" to list the help index and "F3" to list the different boot methods.

This is a known issue with isolinux and the GUI boot menu. There needs to be an upstream patch to actually correct this issue.

[Tim Bosse (timbosse)]

The work-around was tested successfully on a Dell Dimension E510 which was experiencing the same issue as mentioned with my old account above from taim1.

[Frank Wegner (ftwegner)]

BTW, the USB keyboard is also not working with 7.10 when you try to recover a lost root password by adding "rw init=/bin/bash" to the kernel boot line. The root shell boots up but you cannot type.

[Frank Wegner (ftwegner)]

Some more info regarding my previous post: I managed to get the keyboard working by holding the shift key while booting. With "rw init=/bin/bash" as described above I got a root prompt. I typed in "passwd" and hit RETURN. From this point on the keyboard driver was messed up. Hitting a SPACE key worked like a RETURN, no further characters would show up, Ctrl-Alt-Del was still working though. Actually, I could reset the root password to SPACE in the end. Attached is the "lsusb -v" output for the DELL keyboard.

[Retromingent (ray-rwalk2730)]

I have the same problem. The USB keyboard worked fine with Ubuntu 7.10 but now fails after the 8.04 upgrade. My keyboard is a Logitech Elite.

[candtalan (aeclist)]

I also have found this on a friends machine Dell Dimension E520 when trying to test ubuntu 7.10 and also 8.04 live CD. 7.04 was already installed (by me) and I do not recall any problems like this.

I upgraded the friends version from 7.04 to 7.10 and then immediately on to 8.04. A bit tedious I think but at least I did not want to take a risk that a clean reinstall would go wrong if something was odd about the hardware compatibility. I had lost confidence in the live cd for that hardware.
(had not seen this bug entry at that time)

For both 7.10 and 8.04, neither usb mouse nor usb keyboard worked at initial stage of CD booting, (which was disconcerting) so I had to allow the timeout to run. Once the CD was running live k/ubuntu os then both mouse and keyboard were ok.

[Marchbanks (curmudgn)]

The problem's come back with Hardy Heron. Like Loe Spee, my Dell OptiPlex GX620 (Vortex, Neo chassis) has NO PS/2 ports (in 2005 Dell converted PS/2 ports to an upsell add-on in the OptiPlex and Dimension lines of business) so the PS/2 port workaround is a non-starter. I'm *completely* unable to use any of the Heron alternate install CDs, which is a pain and a half since I'm trying to set up a dual-boot box without having to wipe the drive. The only way I can install Heron at all is to allow the regular install CD to count down, as foster did. So when is SOMEone gonna come up with an actual FIX rather than workaround suggestions (kmurray's <Shf> key suggestion fails to work with my hardware) or "sucks to be you" responses? (I don't even OWN a PS/2 keyboard any longer, and bedamn if I'm gonna go to Goodwill and buy one.)

[Eyal (eyal-cs)]

Same problem with Ubuntu 8.04 LTS Server, and similarly, there is no PS/2 port on my Dell Machine.

[Eyal (eyal-cs)]

Also, the BIOS has no reference to USB keyboard/mouse, so none of the workarounds above works.

[Marchbanks (curmudgn)]

I solved the problem in the OptiPlex GX620. What was wanted is a rollback to the A10 revision of the BIOS. Up through A10 the keyboard works fine during installation, but with the A11 the keyboard goes on strike.

[Tommy Trussell (tommy-trussell)]

Confirming this bug in Ubuntu 8.04.1 on a Dell Dimension E510 (which has no PS/2-style keyboard ports). I tried the Desktop, Alternate and Server disks with the same result. I'm using a USB to PS/2 adapter, but it did the same with a "native" USB keyboard.

DELL BIOS version: A07 (01/08/07)

To get to the text installer, I held a Shift key as soon as the Dell's Setup/Boot menu disappeared, and answered "no" to the "Load Boot Graphics" prompt. From there the text install went fine, and the keyboard and mouse work fine.

[rivode (bugs-launchpad-net-rivode)]

Just a comment about a similar problem I'm having...

I have a PS/2 mouse/keyboard to USB adapter (USB ID 13ba:0017). The PS/2 keyboard works fine in the Grub menu (presumably this is the BIOS emulation working here) but once the kernel starts it doesn't work at all. This is for typing in a LUKS passphrase (this happens in the initrd), once the system has started (ie. press ctrl+shift+f1 on the laptop keyboard, the other one doesn't work) nor does it work in gdm. However, the PS/2 mouse attached to it works fine (this mouse does USB also via an adapter).

I also have a docking station with PS/2 ports on it, and that works fine with a PS/2 keyboard provided I attach the laptop before I turn it on. (I don't know how this docking station works, but it might have USB ID 0930:0403 or it might send the PS/2 signals straight to the docking connector.)

[Tommy Trussell (tommy-trussell)]

I just tried the Dimension E510 again with an Intrepid desktop 8.10 amd64 beta disk. The first attempt, I couldn't even use the Shift key workaround, but after a power down and restart, the desktop disk worked fine with my USB keyboard adapter.

[Christian Damsgaard (chr-damsgaard)]

My USB keyboard dosn't work after GRUB in Kubuntu 8.10. Funnily it worked with Kubuntu 8.10 rc Live disk, the two times I booted it. In 8.04 the bug was intermittent, the keyboard was recognised about half the time. Now in 8.10 it hasn't worked from start of the kernel yet. The workaround, plugging the keyboard out & in, still works.

[Gene Cumm (gene-cumm)]

I personally can confirm the issue. I first noticed it with another Linux distro (a rescue distro) that loaded menu.c32 by default. From syslinux 3.53 to 3.61, the bug existed. The last patch (to the syslinux core/) before 3.62 resolved the issue. 3.62 and later work without any known issues with respect to this. Certain older versions also do not have this issue.

I've only noticed it with the Dell OptiPlex GX620 and BIOS A11. A10 and below do not have this issue. If menu.c32/vesamenu.c32 was not loaded, the USB keyboard worked without any troubles (using the vanilla syslinux).

I can provide binaries and/or the commit SHA1 name if needed.

[Retromingent (ray-rwalk2730)]

I found that this is not necessarily a Linux error per se, but seems to be a BIOS/boot loader compatibility problem (yet, oddly, it worked with Ubuntu 7.10 and whatever Grub version came with the 7.10). The BIOS is old, 2004, when I turned over the box to be used with Vista it too had the same issue on it's boot loader: only a PS/2 connected keyboard would work on the loader, the USB did not. In both cases, Linux and Vista, once the OS loaded it was fine.

I suspect it is a compatibility issue with new boot loaders and the old BIOS.

[reis (aytekin-sahin)]

same with ubuntu 9.04 / install within windows

i guess the bootmanager is grub but i'm not sure since it looks more like the windows boot manager and has 30 secs to select - but i cant selecet since the usb keyboard is not recognized. so i think it's maybe not a grub problem...

so i uninstalled it from within windows
but the REALLY UGLY thing is that it wont uninstall the boot menu, so now i have to wait 30 seconds until the countdown has finished and windows boots ... GREAT!

now need to get rid of the boot menu somehow...

i may come with an update if get rid of the boot manager

by the way it's also not possible to select the 'install' option when booting from the CD - USB keyboard does not work here as well. so i'm pretty sure if i install after starting from the CD that grub will not work. i'll try now...

[Janusz (yorashtan2)]

same with ubuntu 9.10....

workaround: turn on "legacy usb support" in your bios

[Gene Cumm (gene-cumm)]

1) I'd classify the need to have legacy USB support as a BIOS bug. Any relatively modern full OS will have USB HID support by default. DOS (by default) and Syslinux have no USB HID support. Grub2 has optional USB HID support when set by the configuration.

2) With regards to the Syslinux version-specific issues:

Gutsy-7.10 contains Syslinux-3.36. Hardy-8.04 contains Syslinux-3.53. Intrpid-8.10 contain Syslinux-3.63.

Only Hardy will be affected by this Syslinux version-specific bug that only affects select machines.

Based on this, I would classify this as "Won't Fix" or "Fix Released" with a note in a wiki page about common issues.