Re: ehci breaking Supermicro IPMI keyboard on uhci?
On 11/04/14 17:40, Steven Hartland wrote: On 04/11/2014 07:22, Hans Petter Selasky wrote: On 11/04/14 01:05, Steven Hartland wrote: Had the problem where the Supermicro IPMI keyboard wouldn't work on some machines for a while, tonight I finally had time to play with all the options to see if anything would make it work. Turns out adding the following to loader.conf does fixes the issue: hint.ehci.0.disabled=1 So the question is why would this help? Surely disabling one controller shouldn't make devices attached to another work? Hi, The USB device is failing to enumerate. Are you sure there is no XHCI controller on this device? I did try removing xhci from my kernel config, but that had no effect, only when I disabled the ehci controller did it correctly enumerate the devices attached to the uhci controller. Attached is the outuput from pciconf -l -v in case that helps. If there's anything else I can provide which will help just let me know. For reference I'm currently testing 10.1-RC4 on this box. Regards Steve Maybe you can check the PCI IDs with Linux EHCI driver, if your hardware requires some special quirks? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: ehci breaking Supermicro IPMI keyboard on uhci?
On 04/11/2014 07:22, Hans Petter Selasky wrote: On 11/04/14 01:05, Steven Hartland wrote: Had the problem where the Supermicro IPMI keyboard wouldn't work on some machines for a while, tonight I finally had time to play with all the options to see if anything would make it work. Turns out adding the following to loader.conf does fixes the issue: hint.ehci.0.disabled=1 So the question is why would this help? Surely disabling one controller shouldn't make devices attached to another work? Hi, The USB device is failing to enumerate. Are you sure there is no XHCI controller on this device? I did try removing xhci from my kernel config, but that had no effect, only when I disabled the ehci controller did it correctly enumerate the devices attached to the uhci controller. Attached is the outuput from pciconf -l -v in case that helps. If there's anything else I can provide which will help just let me know. For reference I'm currently testing 10.1-RC4 on this box. Regards Steve pciconf -l -v hostb0@pci0:0:0:0: class=0x06 card=0xa28015d9 chip=0x40038086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset Memory Controller Hub' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0xa28015d9 chip=0x40218086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 1' class = bridge subclass = PCI-PCI pcib2@pci0:0:3:0: class=0x060400 card=0xa28015d9 chip=0x40238086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 3' class = bridge subclass = PCI-PCI pcib3@pci0:0:5:0: class=0x060400 card=0xa28015d9 chip=0x40258086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 5' class = bridge subclass = PCI-PCI pcib4@pci0:0:7:0: class=0x060400 card=0xa28015d9 chip=0x40278086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 7' class = bridge subclass = PCI-PCI pcib10@pci0:0:9:0: class=0x060400 card=0xa28015d9 chip=0x40298086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 9' class = bridge subclass = PCI-PCI hostb1@pci0:0:16:0: class=0x06 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb2@pci0:0:16:1: class=0x06 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb3@pci0:0:16:2: class=0x06 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb4@pci0:0:16:3: class=0x06 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb5@pci0:0:16:4: class=0x06 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb6@pci0:0:17:0: class=0x06 card=0xa28015d9 chip=0x40318086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset CE/SF Registers' class = bridge subclass = HOST-PCI hostb7@pci0:0:21:0: class=0x06 card=0xa28015d9 chip=0x40358086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI hostb8@pci0:0:21:1: class=0x06 card=0xa28015d9 chip=0x40358086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI hostb9@pci0:0:22:0: class=0x06 card=0xa28015d9 chip=0x40368086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI hostb10@pci0:0:22:1:class=0x06 card=0xa28015d9 chip=0x40368086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI pcib11@pci0:0:28:0: class=0x060400 card=0xa28015d9 chip=0x26908086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset PCI Express Root Port 1' class = bridge subclass = PCI-PCI uhci0@pci0:0:29:0: class=0x0c0300 card=0xa28015d9 chip=0x26888086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation'
Re: ehci breaking Supermicro IPMI keyboard on uhci?
On 04/11/2014 16:45, Hans Petter Selasky wrote: On 11/04/14 17:40, Steven Hartland wrote: On 04/11/2014 07:22, Hans Petter Selasky wrote: On 11/04/14 01:05, Steven Hartland wrote: Had the problem where the Supermicro IPMI keyboard wouldn't work on some machines for a while, tonight I finally had time to play with all the options to see if anything would make it work. Turns out adding the following to loader.conf does fixes the issue: hint.ehci.0.disabled=1 So the question is why would this help? Surely disabling one controller shouldn't make devices attached to another work? Hi, The USB device is failing to enumerate. Are you sure there is no XHCI controller on this device? I did try removing xhci from my kernel config, but that had no effect, only when I disabled the ehci controller did it correctly enumerate the devices attached to the uhci controller. Attached is the outuput from pciconf -l -v in case that helps. If there's anything else I can provide which will help just let me know. For reference I'm currently testing 10.1-RC4 on this box. Regards Steve Maybe you can check the PCI IDs with Linux EHCI driver, if your hardware requires some special quirks? I cant find any mention of quirks for the Intel USB controller PCI IDs but I might be looking in the wrong place, do you have a link to what I should be searching though? I did however find the following which is for the exact device I'm having issues with and seems to indicate the HW might have an issue with HighSpeed mode. https://lkml.org/lkml/2012/4/19/224 http://lkml.iu.edu//hypermail/linux/kernel/1204.3/03115.html Which makes me wonder if hw.usb.ehci.no_hs=1 would also result in a working device. Regards Steve ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
