Hello, I have a strange problem with a PS/2 keyboard attached through USB adapter to USB port (machine doesn't have PS/2 ports). The keyboard behaves fine during POST and first boot stages (I'm not sure if that's the first stage, but I'm referring to the stage where I can select single-user mode). Then, after kernel is loaded, and enters single-user mode, and further on, if proceeded to multi-user mode, the keyboard input is not recognized. Strangely enough, when I load Xorg (I do that manually, not as a tty), the keyboard is recognized again, also in consoles. If I detach and attach the keyboard when it's input is not recognized, it finally gets recognized after several detach-attach cycles; on each, I get kernel messages about USB device being attached and detached. I would like to ask for advice, - if there's anything I can try? I can't grok the kernel sources related to the cause (I tried), so I need help about what else can I try - enable debug, put some hacks in kernel to see what's going on etc. Thank you! Here's exceprt from dmesg: FreeBSD 6.3-STABLE #0: Mon Jan 28 11:34:18 CET 2008 kbd1 at kbdmux0 uhci0: <UHCI (generic) USB controller> port 0xff20-0xff3f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] usb0: <UHCI (generic) USB controller> on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: <UHCI (generic) USB controller> port 0xff00-0xff1f irq 17 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] usb1: <UHCI (generic) USB controller> on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdfdfbc00-0xdfdfbfff irq 22 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: <EHCI (generic) USB 2.0 controller> on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered uhci2: <UHCI (generic) USB controller> port 0xff80-0xff9f irq 23 at device 29.0 on pci0 uhci2: [GIANT-LOCKED] usb3: <UHCI (generic) USB controller> on uhci2 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered uhci3: <UHCI (generic) USB controller> port 0xff60-0xff7f irq 17 at device 29.1 on pci0 uhci3: [GIANT-LOCKED] usb4: <UHCI (generic) USB controller> on uhci3 usb4: USB revision 1.0 uhub4: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub4: 2 ports with 2 removable, self powered uhci4: <UHCI (generic) USB controller> port 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci4: [GIANT-LOCKED] usb5: <UHCI (generic) USB controller> on uhci4 usb5: USB revision 1.0 uhub5: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub5: 2 ports with 2 removable, self powered ehci1: <EHCI (generic) USB 2.0 controller> mem 0xff980800-0xff980bff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: <EHCI (generic) USB 2.0 controller> on ehci1 usb6: USB revision 2.0 uhub6: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub6: 6 ports with 6 removable, self powered ukbd0: vendor 0x0d3d USBPS2, rev 1.10/0.01, addr 2, iclass 3/1 kbd2 at ukbd0 ums1: vendor 0x0d3d USBPS2, rev 1.10/0.01, addr 2, iclass 3/1 ums1: 5 buttons and Z dir. usb1: host controller halted usb0: host controller halted And by this time the system is booted, but the keyboard is not recognized. So I take another wireless USB keyboard and plug it in, to login: uhub7: vendor 0x0424 product 0x2504, class 9/0, rev 2.00/0.01, addr 2 uhub7: multiple transaction translators uhub7: 4 ports with 4 removable, self powered ukbd1: Logitech USB Receiver, rev 1.10/38.10, addr 3, iclass 3/1 kbd3 at ukbd1 ums2: Logitech USB Receiver, rev 1.10/38.10, addr 3, iclass 3/1 ums2: 8 buttons and Z dir. The first keyboard is still not recognized; but by the time xorg is loaded it is, without any extra kernel messages. -- Sincerely, Dmitry Karasik