Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
Update... It seems that the 'xhci-hcd' module was split into 'xhci-pci' and 'xhci-platform' since kernel version 3.18. Adding the 'xhci-pci' module to initramfs fixes the issue for me. It worked for me too... I should have read this thread till the last post... Sorry. -- Emmanuel Fleury A good compromise leaves everyone mad. -- Calvin Hobbes (Bill Waterson) signature.asc Description: OpenPGP digital signature
Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
Same problem as previously mentioned. I have an Apple MacBook with luks, my keyboard is recognized (I can navigate in the GRUB option menu), but typing the passphrase to access the disk and boot on my system has no effect. Moreover, I am compiling my own kernels for my distribution and the problem occurred at 3.18.x and higher (I just tried with 3.19.0 right now, the problem is still here). So, the problem comes from a modification of the kernel settings and not because of some tweaks from specific to linux-image-3.18.0-trunk-amd64. The new kernel series may need to tick a new box in the menuconfig phase, but I can tell which one. I am still looking for some clues that could lead to a resolution of the problem (if a least I could see where it fails it would be a starting point). So, any hint is welcome ! Regards -- Emmanuel Fleury Experience is one thing you can't get for nothing. -- Oscar Wilde signature.asc Description: OpenPGP digital signature
Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
It seems that the 'xhci-hcd' module was split into 'xhci-pci' and 'xhci-platform' since kernel version 3.18. Adding the 'xhci-pci' module to initramfs fixes the issue for me. Ilias signature.asc Description: Digital signature
Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
❦ 16 décembre 2014 09:22 +0900, Mike Hommey mh+report...@glandium.org : Preliminary note: this works fine with linux-image-3.16.0-4-amd64 and all versions before that. My setup involves a luks encrypted root file system, so I get a prompt during boot for the passphrase. When booting with the kernel from linux-image-3.18.0-trunk-amd64, I simply can't type that passphrase with a usb keyboard. Note that before linux-image-3.18.0-trunk-amd64, it did work, but not immediately: at the time the prompt showed up, it would not actually work, and it would take a few seconds for the keyboard to be recognized, but it would eventually be useable to type the passphrase. This, in turn, may be related to the fact that the keyboard doesn't work in grub either, probably because the old bios compatibility doesn't work. If it did, I guess there would actually be no problem with the cryptsetup prompt. I have the same problem but my keyboard works with Grub. I suppose that the appropriate HID driver or evdev doesn't get loaded in the initramfs but without a keyboard, that's a bit difficult to test. update-initramfs doesn't show evdev being used but hid stuff is here. -- Reader, suppose you were an idiot. And suppose you were a member of Congress. But I repeat myself. -- Mark Twain signature.asc Description: PGP signature
Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
Package: src:linux Version: 3.18-1~exp1 Severity: important Preliminary note: this works fine with linux-image-3.16.0-4-amd64 and all versions before that. My setup involves a luks encrypted root file system, so I get a prompt during boot for the passphrase. When booting with the kernel from linux-image-3.18.0-trunk-amd64, I simply can't type that passphrase with a usb keyboard. Note that before linux-image-3.18.0-trunk-amd64, it did work, but not immediately: at the time the prompt showed up, it would not actually work, and it would take a few seconds for the keyboard to be recognized, but it would eventually be useable to type the passphrase. This, in turn, may be related to the fact that the keyboard doesn't work in grub either, probably because the old bios compatibility doesn't work. If it did, I guess there would actually be no problem with the cryptsetup prompt. -- Package-specific info: ** Version: Linux version 3.18.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-4) ) #1 SMP Debian 3.18-1~exp1 (2014-12-11) ** Command line: BOOT_IMAGE=/vmlinuz-3.18.0-trunk-amd64 root=/dev/mapper/zenigata-root ro quiet ** Not tainted ** Kernel log: [ 19.479456] Bluetooth: SCO socket layer initialized [ 19.481502] usbcore: registered new interface driver btusb [ 19.483235] hidraw: raw HID events driver (C) Jiri Kosina [ 19.483523] media: Linux media interface: v0.10 [ 19.486736] Linux video capture interface: v2.00 [ 19.490747] uvcvideo: Found UVC 1.00 device Integrated Webcam (0bda:5716) [ 19.494883] Bluetooth: hci0: read Intel version: 370710018002030d37 [ 19.494886] Bluetooth: hci0: Intel device is already patched. patch num: 37 [ 19.497586] usbcore: registered new interface driver usbhid [ 19.497589] usbhid: USB HID core driver [ 19.498962] input: Integrated Webcam as /devices/pci:00/:00:14.0/usb2/2-5/2-5:1.0/input/input14 [ 19.499038] usbcore: registered new interface driver uvcvideo [ 19.499040] USB Video Class driver (1.1.1) [ 19.540150] usb 2-1.2.2: new low-speed USB device number 9 using xhci_hcd [ 19.634530] usb 2-1.2.2: New USB device found, idVendor=05ac, idProduct=0304 [ 19.634534] usb 2-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 19.634537] usb 2-1.2.2: Product: Apple Optical USB Mouse [ 19.634538] usb 2-1.2.2: Manufacturer: Mitsumi Electric [ 19.634747] usb 2-1.2.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 19.708413] usb 2-1.2.3: new high-speed USB device number 10 using xhci_hcd [ 19.805829] usb 2-1.2.3: New USB device found, idVendor=13fe, idProduct=1f00 [ 19.805833] usb 2-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 19.805836] usb 2-1.2.3: Product: Patriot Memory [ 19.805837] usb 2-1.2.3: Manufacturer: [ 19.805839] usb 2-1.2.3: SerialNumber: 078A1DB11609 [ 19.817557] input: HID 0566:3107 as /devices/pci:00/:00:14.0/usb2/2-1/2-1.2/2-1.2.1/2-1.2.1:1.0/0003:0566:3107.0001/input/input15 [ 19.817695] hid-generic 0003:0566:3107.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 0566:3107] on usb-:00:14.0-1.2.1/input0 [ 19.818858] input: HID 0566:3107 as /devices/pci:00/:00:14.0/usb2/2-1/2-1.2/2-1.2.1/2-1.2.1:1.1/0003:0566:3107.0002/input/input16 [ 19.819240] input: Mitsumi Electric Apple Optical USB Mouse as /devices/pci:00/:00:14.0/usb2/2-1/2-1.2/2-1.2.2/2-1.2.2:1.0/0003:05AC:0304.0004/input/input17 [ 19.820157] hid-generic 0003:0566:3107.0002: input,hidraw1: USB HID v1.10 Device [HID 0566:3107] on usb-:00:14.0-1.2.1/input1 [ 19.820658] apple 0003:05AC:0304.0004: input,hidraw2: USB HID v1.10 Mouse [Mitsumi Electric Apple Optical USB Mouse] on usb-:00:14.0-1.2.2/input0 [ 19.820685] usb-storage 2-1.2.3:1.0: USB Mass Storage device detected [ 19.821692] scsi host3: usb-storage 2-1.2.3:1.0 [ 19.821799] usbcore: registered new interface driver usb-storage [ 19.878557] systemd-journald[284]: Received request to flush runtime journal from PID 1 [ 19.989804] RPC: Registered named UNIX socket transport module. [ 19.989807] RPC: Registered udp transport module. [ 19.989808] RPC: Registered tcp transport module. [ 19.989808] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 19.992791] FS-Cache: Loaded [ 19.999896] FS-Cache: Netfs 'nfs' registered for caching [ 20.006610] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 20.122205] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.122208] Bluetooth: BNEP filters: protocol multicast [ 20.122215] Bluetooth: BNEP socket layer initialized [ 20.481233] iwlwifi :06:00.0: L1 Enabled - LTR Enabled [ 20.481841] iwlwifi :06:00.0: L1 Enabled - LTR Enabled [ 20.821977] scsi 3:0:0:0: Direct-Access Patriot Memory PMAP PQ: 0 ANSI: 0 CCS [ 20.822548] sd 3:0:0:0: [sdb] 15654912 512-byte logical blocks: (8.01 GB/7.46 GiB) [ 20.822636] sd 3:0:0:0: Attached scsi
Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
On Tue, Dec 16, 2014 at 09:22:42AM +0900, Mike Hommey wrote: Package: src:linux Version: 3.18-1~exp1 Severity: important Preliminary note: this works fine with linux-image-3.16.0-4-amd64 and all versions before that. My setup involves a luks encrypted root file system, so I get a prompt during boot for the passphrase. When booting with the kernel from linux-image-3.18.0-trunk-amd64, I simply can't type that passphrase with a usb keyboard. Note that before linux-image-3.18.0-trunk-amd64, it did work, but not immediately: at the time the prompt showed up, it would not actually work, and it would take a few seconds for the keyboard to be recognized, but it would eventually be useable to type the passphrase. This, in turn, may be related to the fact that the keyboard doesn't work in grub either, probably because the old bios compatibility doesn't work. If it did, I guess there would actually be no problem with the cryptsetup prompt. So it turns out that legacy support was disabled in the bios, and that made grub not recognize the keyboard... but that didn't solve the issue with the cryptsetup prompt. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
