[Bug 1313497] Re: USB keyboard unresponsive on fresh install
I am trying to clean up the bug reports I am assigned to. This one sounds like it got resolved by changing the preseed in order to get the correct set of modules installed. Closing it invalid which may sound a bit harsh but it did not seem to be a bug in the kernel package after all. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] Re: USB keyboard unresponsive on fresh install
** Description changed: - Hi, - I just did a fresh install of Ubuntu 14.04 LTS onto a machine here. During the installation (which is pre-seeded) and in the BIOS, my - keyboard works flawlessly. - - However, the moment I boot the machine up, I note the keyboard is not - operational. Naturally, I discover this *after* buggering up my - networking settings. + keyboard works flawlessly. However, the moment I boot the machine up, I + note the keyboard is not operational. Naturally, I discover this + *after* buggering up my networking settings. The offending package is linux-image-3.13.0-24-generic version 3.13.0-24.46. At one point I noticed an irq 16: nobody cared error message. Due to there being no network connectivity, I was unable to capture the message displayed. The output from `dmesg` (see attachment dmesg.txt) suggests it does see USB and the keyboard, but plugging the keyboard into any of the available ports and pressing keys has no effect on the console. The machine is a rack-mounted server, intended to run headless. The motherboard is an Intel DQ77MK. No peripheral cards are installed. - root@host:~# cat /proc/version_signature - Ubuntu 3.13.0-24.46-generic 3.13.9 - root@host:~# lspci -vnvn - 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) - Subsystem: Intel Corporation Device [8086:2035] - Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- - Latency: 0 - Capabilities: [e0] Vendor Specific Information: Len=0c ? - - 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) - Subsystem: Intel Corporation Device [8086:2035] - Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- - Latency: 0 - Interrupt: pin A routed to IRQ 11 - Region 0: Memory at f780 (64-bit, non-prefetchable) [size=4M] - Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] - Region 4: I/O ports at f000 [size=64] - Expansion ROM at unassigned [disabled] - Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- - Address: Data: - Capabilities: [d0] Power Management version 2 - Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) - Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- - Capabilities: [a4] PCI Advanced Features - AFCap: TP+ FLR+ - AFCtrl: FLR- - AFStatus: TP- - - 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) - Subsystem: Intel Corporation Device [8086:2035] - Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ - Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- - Latency: 0 - Interrupt: pin A routed to IRQ 40 - Region 0: Memory at f7e2 (64-bit, non-prefetchable) [size=64K] - Capabilities: [70] Power Management version 2 - Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+) - Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- - Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ - Address: fee0a00c Data: 4181 - Kernel driver in use: xhci_hcd - - 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) - Subsystem: Intel Corporation Device [8086:2035] - Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- - Latency: 0 - Interrupt: pin A routed to IRQ 11 - Region 0: Memory at f7e3c000 (64-bit, non-prefetchable) [size=16] - Capabilities: [50] Power Management version 3 - Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) - Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- - Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+ - Address: Data: - - 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller
Re: [Bug 1313497] Re: USB keyboard unresponsive on fresh install
Hi Stuart, On 29.04.2014 05:23, Stuart Longland wrote: Did the linux-3.13.0-24-generic package miss out a few files or are they in a separate package the installer forgot to install? That could be and depends on you seed. For bare-metal you should have seleced linux-server for d-i base-installer/kernel/image. In general the linux-image should not be picked directly as we indeed split up the modules into the minimum for virtual machines and a rest. linux-server, linux-generic, and linux-virtual are all meta-package which will install the right set of packages and also make sure you see kernel updates. server and generic nowadays is actually the same. So you could have installed without those and now miss the linux-image-extra package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313497] Re: USB keyboard unresponsive on fresh install
On 29/04/14 18:35, Stefan Bader wrote: Hi Stuart, On 29.04.2014 05:23, Stuart Longland wrote: Did the linux-3.13.0-24-generic package miss out a few files or are they in a separate package the installer forgot to install? That could be and depends on you seed. For bare-metal you should have seleced linux-server for d-i base-installer/kernel/image. In general the linux-image should not be picked directly as we indeed split up the modules into the minimum for virtual machines and a rest. linux-server, linux-generic, and linux-virtual are all meta-package which will install the right set of packages and also make sure you see kernel updates. server and generic nowadays is actually the same. So you could have installed without those and now miss the linux-image-extra package. Ahh, I have in my preseed: # The kernel image (meta) package to be installed; none can be used if no # is to be installed. d-i base-installer/kernel/image string linux-image-virtual Perhaps I mis-interpreted the intent of virtual. Is there a document that describes the image options in detail that one could refer to? Perhaps mention of it should be made in the preseed examples? It's easy to miss the bit about it being for virtual instances in the dpkg -l output, which is how I installed the image: root@host:~# dpkg -l linux-image-virtual Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===--- ii linux-image-virtual 3.13.0.24.29 amd64This package will always depend on the latest minima I shall amend my preseed scripts and perhaps we can work on the documentation (which either is lacking or I missed seeing it). Regards, -- Stuart Longland Systems Engineer _ ___ \ /|_) | T: +61 7 3535 9619 \/ | \ | 38b Douglas StreetF: +61 7 3535 9699 SYSTEMSMilton QLD 4064 http://www.vrt.com.au -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313497] Re: USB keyboard unresponsive on fresh install
Hi Stefan, On 29/04/14 01:23, Stefan Bader wrote: Question is maybe whether this is the usb keyboard or maybe some failure to start a local tty or framebuffer mode. If there is a login prompt, framebuffer and tty are most likely ok. If you can ssh into the server from somewhere close to it (to be able to press keys on the keybord at the same time) you could try to install input-utils. sudo lsinput should have an entry for the keyboard since it is detected. Well, I had a look, and oddly enough the keyboard is *not* detected. root@host:~# lsinput /dev/input/event0 bustype : BUS_HOST vendor : 0x0 product : 0x1 version : 0 name: Power Button phys: PNP0C0C/button/input0 bits ev : EV_SYN EV_KEY /dev/input/event1 bustype : BUS_HOST vendor : 0x0 product : 0x1 version : 0 name: Power Button phys: LNXPWRBN/button/input0 bits ev : EV_SYN EV_KEY There's no entry for the keyboard. I had a poke around but couldn't see any kernel modules missing. Even after re-plugging the keyboard, it doesn't appear. Digging around, I see the USB HID support is a module: root@host:~# grep USB_HID /boot/config-3.13.0-24-generic CONFIG_USB_HID=m CONFIG_USB_HIDDEV=y Yet, the list of modules on the system seems incomplete: root@host:~# find /lib/modules -type f -name \*.ko /lib/modules/3.13.0-24-generic/kernel/net/ieee802154/ieee802154.ko /lib/modules/3.13.0-24-generic/kernel/net/ieee802154/af_802154.ko /lib/modules/3.13.0-24-generic/kernel/net/ieee802154/6lowpan.ko /lib/modules/3.13.0-24-generic/kernel/net/netrom/netrom.ko /lib/modules/3.13.0-24-generic/kernel/net/x25/x25.ko /lib/modules/3.13.0-24-generic/kernel/net/can/can-raw.ko /lib/modules/3.13.0-24-generic/kernel/net/can/can.ko /lib/modules/3.13.0-24-generic/kernel/net/can/can-bcm.ko /lib/modules/3.13.0-24-generic/kernel/net/can/can-gw.ko /lib/modules/3.13.0-24-generic/kernel/net/ceph/libceph.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_mirred.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_codel.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/em_meta.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_red.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_multiq.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_simple.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_dsmark.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_cbq.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_fw.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_bpf.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_cgroup.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/em_nbyte.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_hfsc.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_tcindex.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_choke.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_police.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_atm.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_qfq.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_plug.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_fq.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_csum.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_gact.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_flow.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/em_u32.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_route.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/em_cmp.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_netem.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_mqprio.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_ingress.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_rsvp.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_fq_codel.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_rsvp6.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_nat.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/em_canid.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_sfb.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/em_text.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_prio.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_gred.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_sfq.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_u32.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_drr.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/cls_basic.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_ipt.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_teql.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_pedit.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_htb.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/sch_tbf.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/act_skbedit.ko /lib/modules/3.13.0-24-generic/kernel/net/sched/em_ipset.ko
[Bug 1313497] Re: USB keyboard unresponsive on fresh install
Question is maybe whether this is the usb keyboard or maybe some failure to start a local tty or framebuffer mode. If there is a login prompt, framebuffer and tty are most likely ok. If you can ssh into the server from somewhere close to it (to be able to press keys on the keybord at the same time) you could try to install input-utils. sudo lsinput should have an entry for the keyboard since it is detected. Then you could sudo input-events # where number is the number from the /dev line from lsinput. Look I would have two input lines for my Logitech keyboard here, if that is the case try both. At least one of them should work... ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Stefan Bader (smb) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] Re: USB keyboard unresponsive on fresh install
apport information ** Tags added: apport-collected ** Description changed: Hi, I just did a fresh install of Ubuntu 14.04 LTS onto a machine here. During the installation (which is pre-seeded) and in the BIOS, my keyboard works flawlessly. However, the moment I boot the machine up, I note the keyboard is not operational. Naturally, I discover this *after* buggering up my networking settings. The offending package is linux-image-3.13.0-24-generic version 3.13.0-24.46. At one point I noticed an irq 16: nobody cared error message. Due to there being no network connectivity, I was unable to capture the message displayed. The output from `dmesg` (see attachment dmesg.txt) suggests it does see USB and the keyboard, but plugging the keyboard into any of the available ports and pressing keys has no effect on the console. The machine is a rack-mounted server, intended to run headless. The motherboard is an Intel DQ77MK. No peripheral cards are installed. root@host:~# cat /proc/version_signature Ubuntu 3.13.0-24.46-generic 3.13.9 root@host:~# lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) Subsystem: Intel Corporation Device [8086:2035] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c ? 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2035] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f780 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Intel Corporation Device [8086:2035] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 40 Region 0: Memory at f7e2 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Address: fee0a00c Data: 4181 Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Intel Corporation Device [8086:2035] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f7e3c000 (64-bit, non-prefetchable) [size=16] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller [8086:1e3d] (rev 04) (prog-if 02 [16550]) Subsystem: Intel Corporation Device [8086:2035] Control: I/O+ Mem+ BusMaster+
