ums fails to initialise correctly
I wasn't sure whether this question was better asked on this list or the freebsd-usb one; but since I'm already subscribed here, I figured it was a good place to start. I'm having a lot of problems getting the ums (USB mouse) driver to initialise the mouse correctly. The only time it'll do so is if I physically unplug the mouse and reattach it; otherwise, it seems there's no way of getting it to initialise correctly. The mouse in question is a Logitech MX Revolution wireless model, though I'm not sure how relevant that is. Confusingly, the kernel messages are identical when it comes to seeing the mouse initially and reattaching it; perhaps significantly, if I plug it into my KVM switch (as opposed to one of the computer's own ports), it still fails to initialise if I switch it away from the FreeBSD system and back again: I have to do the physical detach/reattach process to get it to reinitialise. One possible lead is that once the mouse is working, it's fine when it's switched between the two FreeBSD systems, but switching to Windows and back renders it unusable again until I physically reattach it. I had wondered if it might be some hardware weirdness, but Windows (XP and 7) and Linux (on the same computer as FreeBSD) have no problems with it. The symptoms are just a lack of any data; otherwise everything seems identical between it working and not: the messages are the same, the /dev entry is being created correctly, devd starts up the moused process for me, but there's nothing. It's not a moused problem either, cat -v /dev/ums1 also reveals no data. I've tried pretty much every BIOS configuration I can think of, I've tried FreeBSD with both the ehci and ohci drivers, both compiled into the kernel and as modules; I've used usbconfig to see if there's any difference in configuration between the mouse working and not working, but nothing at all; variously loading and unloading ums, attempting to reset it or do a software power off and back on with usbconfig also won't bring it back to life. Meanwhile, the USB keyboard just works, whatever I do. I spent much of the past couple of days Googling for suggestions and discovered it wasn't an uncommon problem, but could find no definite solution (other than suggestions to disable legacy support if it was enabled and vice versa - which didn't work). I did find similar queries going back to 2003, which makes me wonder if it's a problem without any obvious solution, but I thought I'd ask anyway. I'm using -current in its amd64 form on an old-ish dual-core AMD with an Asus motherboard, if that gives anybody any clues. But I figure I should get back to whether or not this is the right place to ask before I start posting reams of configuration and debugging information! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ums fails to initialise correctly
On Monday 22 February 2010 14:41:18 Chris Hedley wrote: I wasn't sure whether this question was better asked on this list or the freebsd-usb one; but since I'm already subscribed here, I figured it was a good place to start. I'm having a lot of problems getting the ums (USB mouse) driver to initialise the mouse correctly. The only time it'll do so is if I physically unplug the mouse and reattach it; otherwise, it seems there's no way of getting it to initialise correctly. The mouse in question is a Logitech MX Revolution wireless model, though I'm not sure how relevant that is. Confusingly, the kernel messages are identical when it comes to seeing the mouse initially and reattaching it; perhaps significantly, if I plug it into my KVM switch (as opposed to one of the computer's own ports), it still fails to initialise if I switch it away from the FreeBSD system and back again: I have to do the physical detach/reattach process to get it to reinitialise. One possible lead is that once the mouse is working, it's fine when it's switched between the two FreeBSD systems, but switching to Windows and back renders it unusable again until I physically reattach it. I had wondered if it might be some hardware weirdness, but Windows (XP and 7) and Linux (on the same computer as FreeBSD) have no problems with it. The symptoms are just a lack of any data; otherwise everything seems identical between it working and not: the messages are the same, the /dev entry is being created correctly, devd starts up the moused process for me, but there's nothing. It's not a moused problem either, cat -v /dev/ums1 also reveals no data. I've tried pretty much every BIOS configuration I can think of, I've tried FreeBSD with both the ehci and ohci drivers, both compiled into the kernel and as modules; I've used usbconfig to see if there's any difference in configuration between the mouse working and not working, but nothing at all; variously loading and unloading ums, attempting to reset it or do a software power off and back on with usbconfig also won't bring it back to life. Meanwhile, the USB keyboard just works, whatever I do. I spent much of the past couple of days Googling for suggestions and discovered it wasn't an uncommon problem, but could find no definite solution (other than suggestions to disable legacy support if it was enabled and vice versa - which didn't work). I did find similar queries going back to 2003, which makes me wonder if it's a problem without any obvious solution, but I thought I'd ask anyway. I'm using -current in its amd64 form on an old-ish dual-core AMD with an Asus motherboard, if that gives anybody any clues. But I figure I should get back to whether or not this is the right place to ask before I start posting reams of configuration and debugging information! Hi, What is printed to dmesg when you enable debugging? sysctl hw.usb.ums.debug=15 --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Can't use USB keyboard during boot menu
I've already had this problem in the past and seems it's back now. I use a Sun Type 7 USB keyboard. When my box is booting, and FreeBSD menu shows up, I cannot press any key to go for a single boot for example. ugen1.1: UHCI root HUB VIA at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.1: UHCI root HUB VIA at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: UHCI root HUB VIA at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: UHCI root HUB VIA at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: EHCI root HUB VIA at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: product 0x100e vendor 0x0430 at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.3: USB Mouse vendor 0x0566 at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: Sun USB Keyboard vendor 0x0430 at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Please let me know if you need more data. Thanks -- Renato Botelho ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ums fails to initialise correctly
On Mon, 22 Feb 2010, Hans Petter Selasky wrote: Hi, What is printed to dmesg when you enable debugging? sysctl hw.usb.ums.debug=15 Is the attached information okay? I tried it twice, first after a switch using the KVM (where the mouse didn't work) and second when unplugging the receiver and plugging it back in. Both traces are identical except for the sc=0xf... etc bit. Do you want me to get the boot-time messages too, or is this okay for now?ugen0.4: Logitech at usbus0 ums_probe: ums_probe: ums_attach: sc=0xff0001619800 ums1: Logitech USB Receiver, class 0/0, rev 2.00/2.00, addr 4 on usbus0 ums1: 16 buttons and [XYZ] coordinates ID=0 ums_attach: sc=0xff0001619800, index=0 ums_attach: X 16/16 id=0 ums_attach: Y 32/16 id=0 ums_attach: Z 48/8 id=0 ums_attach: T 0/0 id=0 ums_attach: W 0/0 id=0 ums_attach: B1 0/1 id=0 ums_attach: B2 1/1 id=0 ums_attach: B3 2/1 id=0 ums_attach: B4 3/1 id=0 ums_attach: B5 4/1 id=0 ums_attach: B6 5/1 id=0 ums_attach: B7 6/1 id=0 ums_attach: B8 7/1 id=0 ums_attach: B9 8/1 id=0 ums_attach: B10 9/1 id=0 ums_attach: B11 10/1 id=0 ums_attach: B12 11/1 id=0 ums_attach: B13 12/1 id=0 ums_attach: B14 13/1 id=0 ums_attach: B15 14/1 id=0 ums_attach: B16 15/1 id=0 ums_attach: sc=0xff0001619800, index=1 ums_attach: X 0/0 id=0 ums_attach: Y 0/0 id=0 ums_attach: Z 0/0 id=0 ums_attach: T 0/0 id=0 ums_attach: W 0/0 id=0 ums_attach: size=8, id=0 ums_probe: ums_probe: ums_open: ums_open: ums_ioctl: ums_ioctl: ums_ioctl: ums_ioctl: ums_ioctl: ugen0.4: Logitech at usbus0 (disconnected) ums1: at uhub1, port 3, addr 4 (disconnected) ums_detach: sc=0xff0001619800 ugen0.4: Logitech at usbus0 ums_probe: ums_probe: ums_attach: sc=0xff00015ae800 ums1: Logitech USB Receiver, class 0/0, rev 2.00/2.00, addr 4 on usbus0 ums1: 16 buttons and [XYZ] coordinates ID=0 ums_attach: sc=0xff00015ae800, index=0 ums_attach: X 16/16 id=0 ums_attach: Y 32/16 id=0 ums_attach: Z 48/8 id=0 ums_attach: T 0/0 id=0 ums_attach: W 0/0 id=0 ums_attach: B1 0/1 id=0 ums_attach: B2 1/1 id=0 ums_attach: B3 2/1 id=0 ums_attach: B4 3/1 id=0 ums_attach: B5 4/1 id=0 ums_attach: B6 5/1 id=0 ums_attach: B7 6/1 id=0 ums_attach: B8 7/1 id=0 ums_attach: B9 8/1 id=0 ums_attach: B10 9/1 id=0 ums_attach: B11 10/1 id=0 ums_attach: B12 11/1 id=0 ums_attach: B13 12/1 id=0 ums_attach: B14 13/1 id=0 ums_attach: B15 14/1 id=0 ums_attach: B16 15/1 id=0 ums_attach: sc=0xff00015ae800, index=1 ums_attach: X 0/0 id=0 ums_attach: Y 0/0 id=0 ums_attach: Z 0/0 id=0 ums_attach: T 0/0 id=0 ums_attach: W 0/0 id=0 ums_attach: size=8, id=0 ums_probe: ums_probe: ums_open: ums_open: ums_ioctl: ums_ioctl: ums_ioctl: ums_ioctl: ums_ioctl: ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [PATCH] SASL problems with spnego on 8.0-BETA4
On 07/10/2009 07:38, John Marshall wrote: access with gssapi auth from a client succeeded. Perhaps George Mamalakis could test the _spnego case? Guys, I am terribly sorry to tell you that I just now saw this conversation(!?!! 4 months later !!!). This is due to the fact that at that time I was mainly tracking the fbsd-stable list (my first email started in fbsd-stable list), and since I use filters in thunderbird, I never got to see your emails in my inbox...truly sorry once more!!! I don't know if Alexander's patch is still valid but from what I realize -since I have built many systems based on fbsd-stable (with latest sources) and I had to hack krb5-config in order to achieve correct behavior of cyrus/gssapi/spnego/openldap- it hasn't yet been commited to fbsd8-stable sources. If so, I will apply it on my machines and rerun my applications. Sorry again for the delay! -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ums fails to initialise correctly
On Monday 22 February 2010 17:52:25 Chris Hedley wrote: On Mon, 22 Feb 2010, Hans Petter Selasky wrote: Hi, What is printed to dmesg when you enable debugging? sysctl hw.usb.ums.debug=15 Is the attached information okay? I tried it twice, first after a switch using the KVM (where the mouse didn't work) and second when unplugging the receiver and plugging it back in. Both traces are identical except for the sc=0xf... etc bit. Do you want me to get the boot-time messages too, or is this okay for now? What is printed when you move the mouse? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ums fails to initialise correctly
On Mon, 22 Feb 2010, Hans Petter Selasky wrote: On Monday 22 February 2010 17:52:25 Chris Hedley wrote: On Mon, 22 Feb 2010, Hans Petter Selasky wrote: Hi, What is printed to dmesg when you enable debugging? sysctl hw.usb.ums.debug=15 Is the attached information okay? I tried it twice, first after a switch using the KVM (where the mouse didn't work) and second when unplugging the receiver and plugging it back in. Both traces are identical except for the sc=0xf... etc bit. Do you want me to get the boot-time messages too, or is this okay for now? What is printed when you move the mouse? When I disconnect reconnect it, I get lots of stuff like this as the pointer moves about the screen: ums_intr_callback: sc=0xff00015ae800 actlen=8 ums_intr_callback: data = 00 00 00 00 ff ff 00 00 ums_intr_callback: x:0 y:1 z:0 t:0 w:0 buttons:0x ums_intr_callback: sc=0xff00015ae800 actlen=8 ums_intr_callback: data = 00 00 00 00 fc ff 00 00 ums_intr_callback: x:0 y:4 z:0 t:0 w:0 buttons:0x ums_intr_callback: sc=0xff00015ae800 actlen=8 ums_intr_callback: data = 00 00 ec ff d5 ff 00 00 ums_intr_callback: x:-20 y:43 z:0 t:0 w:0 buttons:0x But nothing at all when it hasn't initialised properly. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ums fails to initialise correctly
On Monday 22 February 2010 18:45:04 Chris Hedley wrote: On Mon, 22 Feb 2010, Hans Petter Selasky wrote: On Monday 22 February 2010 17:52:25 Chris Hedley wrote: On Mon, 22 Feb 2010, Hans Petter Selasky wrote: Hi, What is printed to dmesg when you enable debugging? sysctl hw.usb.ums.debug=15 Is the attached information okay? I tried it twice, first after a switch using the KVM (where the mouse didn't work) and second when unplugging the receiver and plugging it back in. Both traces are identical except for the sc=0xf... etc bit. Do you want me to get the boot-time messages too, or is this okay for now? What is printed when you move the mouse? When I disconnect reconnect it, I get lots of stuff like this as the pointer moves about the screen: ums_intr_callback: sc=0xff00015ae800 actlen=8 ums_intr_callback: data = 00 00 00 00 ff ff 00 00 ums_intr_callback: x:0 y:1 z:0 t:0 w:0 buttons:0x ums_intr_callback: sc=0xff00015ae800 actlen=8 ums_intr_callback: data = 00 00 00 00 fc ff 00 00 ums_intr_callback: x:0 y:4 z:0 t:0 w:0 buttons:0x ums_intr_callback: sc=0xff00015ae800 actlen=8 ums_intr_callback: data = 00 00 ec ff d5 ff 00 00 ums_intr_callback: x:-20 y:43 z:0 t:0 w:0 buttons:0x But nothing at all when it hasn't initialised properly. Hi, If you get no ums_intr_callback() printouts at all in the failing case, and you are running 9-current, I guess that your KWM switch has some special requirements on the USB programming which I am not aware about. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ums fails to initialise correctly
Hi Chris, Instead of re-plugging the mouse, you can run: usbconfig -u X -a Y reset To manually re-enumerate the USB device at ugenX.Y. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ums fails to initialise correctly
On Mon, 22 Feb 2010, Hans Petter Selasky wrote: But nothing at all when it hasn't initialised properly. Hi, If you get no ums_intr_callback() printouts at all in the failing case, and you are running 9-current, I guess that your KWM switch has some special requirements on the USB programming which I am not aware about. It is all a bit confusing: I tried the other day to boot with the mouse receiver plugged directly into the computer so I could remove the KVM from the equation, and that didn't work either, until I unplugged it and plugged it back in after it had booted. But today it was fine. Then again, I had problems getting the ehci driver to see it when plugging it into the computer after it had booted, though the ohci driver was more accommodating. It does have the hallmarks of one of those pesky intermittent problems... I tried the usbconfig ... reset command, but other than producing convincing-looking messages, that didn't do the trick: it looked like it was there, but absolutely nothing when moving it about. I even tried the power_off/power_on combo in the hope that would be enough, but that didn't work either. It's being extremely stubborn. One possibly significant element is that usbconfig lists the mouse as being full speed (12 MB/s) and the KVM as being low speed (1.5 MB/s) which I understand could potentially cause timing problems or some such; though that doesn't explain why it seems happy enough once I've physically detached and reattached the mouse receiver, since the two devices still show the same respective speeds afterwards. If this really is unworkable, I've been toying with the idea of running my workstation purely in legacy mode (assuming I can get it working...) but I'm not sure if that's really the best way ahead, either for me or the FreeBSD project! But as long as you or anybody else is happy to help look into this odd little problem I've dug up, I'll provide whatever information I can. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
em0 on S3420 chipset (was Re: em0 on H55 chipset problems)
Hi Jack, Any chance on MFC'ing this version of the em driver ? I have another MB that does not work with RELENG_8, only HEAD. Its an Intel branded server motherboard with two onboard NICs. S3420GPC. One of the em nics shows up on RELENG_8, but not both. em1 shows up on RELENG_8, but em0 does not attach on RELENG_8. dmesg below from a snapshot of HEAD from this morning. I guess the onboard NICs are two different types of em nics? BTW, Is one better than the other ? e...@pci0:0:25:0:class=0x02 card=0x34ec8086 chip=0x10ef8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 13[e0] = PCI Advanced Features: FLR TP e...@pci0:3:0:0: class=0x02 card=0x34ec8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled FreeBSD 9.0-CURRENT #3: Fri Feb 5 11:43:38 EST 2010 mdtan...@ich10.sentex.ca:/usr/HEAD/obj/usr/HEAD/src/sys/alix i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (2666.65-MHz 686-class CPU) Origin = GenuineIntel Id = 0x106e5 Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x98e3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT AMD Features=0x2810NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 2582040576 (2462 MB) ACPI APIC Table: INTEL S3420GPC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard acpi0: INTEL S3420GPC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 5.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x2000-0x20ff mem 0xb000-0xbfff,0xc1a0-0xc1a0 irq 16 at device 0.0 on pci1 pci1: multimedia, HDA at device 0.1 (no driver attached) pci0: base peripheral at device 8.0 (no driver attached) pci0: base peripheral at device 8.1 (no driver attached) pci0: base peripheral at device 8.2 (no driver attached) pci0: base peripheral at device 8.3 (no driver attached) pci0: base peripheral at device 16.0 (no driver attached) pci0: base peripheral at device 16.1 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x3040-0x305f mem 0xc1b0-0xc1b1,0xc1b25000-0xc1b25fff irq 20 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:c8:4b:99 ehci0: Intel PCH USB 2.0 controller USB-B mem 0xc1b22000-0xc1b223ff irq 21 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: Intel PCH USB 2.0 controller USB-B on ehci0 pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3: ACPI PCI bus on pcib3 em1: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x1000-0x101f mem 0xc190-0xc191,0xc192-0xc1923fff irq 16 at device 0.0 on pci3 em1: Using MSIX interrupts em1: [ITHREAD] em1: [ITHREAD] em1: [ITHREAD] em1: Ethernet address: 00:15:17:c8:4b:98 pcib4: ACPI PCI-PCI bridge irq 18 at device 28.6 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 19 at device 28.7 on pci0 pci5: ACPI PCI bus on pcib5 ehci1: Intel PCH USB 2.0 controller USB-A mem 0xc1b21000-0xc1b213ff irq 23 at device 29.0 on pci0 ehci1: [ITHREAD] usbus1: EHCI version 1.0 usbus1: Intel PCH USB 2.0 controller USB-A on ehci1 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel AHCI controller port 0x3068-0x306f,0x3074-0x3077,0x3060-0x3067,0x3070-0x3073,0x3020-0x303f mem 0xc1b2-0xc1b207ff irq 18 at device 31.2 on pci0 atapci0: [ITHREAD] atapci0: AHCI v1.30 controller with 6 3Gbps ports, PM not supported ata2: ATA channel 0 on
Re: Can't use USB keyboard during boot menu
On Mon, 22 Feb 2010, Renato Botelho wrote: I've already had this problem in the past and seems it's back now. I use a Sun Type 7 USB keyboard. When my box is booting, and FreeBSD menu shows up, I cannot press any key to go for a single boot for example. ugen1.1: UHCI root HUB VIA at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.1: UHCI root HUB VIA at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: UHCI root HUB VIA at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: UHCI root HUB VIA at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: EHCI root HUB VIA at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: product 0x100e vendor 0x0430 at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.3: USB Mouse vendor 0x0566 at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: Sun USB Keyboard vendor 0x0430 at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Please let me know if you need more data. Do you have USB legacy support enabled in your BIOS? I'm not sure if there's an option for the loader to use USB devices natively, but the BIOS's legacy option where it provides AT/PS2 emulation is probably the easiest way to get the keyboard working. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: em0 on S3420 chipset (was Re: em0 on H55 chipset problems)
Yes, I need to get the code MFC'd anyway, sorry, I just am constantly fighting fires lately it seems :( I'll try to get on it. Jack On Mon, Feb 22, 2010 at 11:46 AM, Mike Tancsa m...@sentex.net wrote: Hi Jack, Any chance on MFC'ing this version of the em driver ? I have another MB that does not work with RELENG_8, only HEAD. Its an Intel branded server motherboard with two onboard NICs. S3420GPC. One of the em nics shows up on RELENG_8, but not both. em1 shows up on RELENG_8, but em0 does not attach on RELENG_8. dmesg below from a snapshot of HEAD from this morning. I guess the onboard NICs are two different types of em nics? BTW, Is one better than the other ? e...@pci0:0:25:0:class=0x02 card=0x34ec8086 chip=0x10ef8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 13[e0] = PCI Advanced Features: FLR TP e...@pci0:3:0:0: class=0x02 card=0x34ec8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled FreeBSD 9.0-CURRENT #3: Fri Feb 5 11:43:38 EST 2010 mdtan...@ich10.sentex.ca:/usr/HEAD/obj/usr/HEAD/src/sys/alix i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (2666.65-MHz 686-class CPU) Origin = GenuineIntel Id = 0x106e5 Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x98e3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT AMD Features=0x2810NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 2582040576 (2462 MB) ACPI APIC Table: INTEL S3420GPC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard acpi0: INTEL S3420GPC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 5.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x2000-0x20ff mem 0xb000-0xbfff,0xc1a0-0xc1a0 irq 16 at device 0.0 on pci1 pci1: multimedia, HDA at device 0.1 (no driver attached) pci0: base peripheral at device 8.0 (no driver attached) pci0: base peripheral at device 8.1 (no driver attached) pci0: base peripheral at device 8.2 (no driver attached) pci0: base peripheral at device 8.3 (no driver attached) pci0: base peripheral at device 16.0 (no driver attached) pci0: base peripheral at device 16.1 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x3040-0x305f mem 0xc1b0-0xc1b1,0xc1b25000-0xc1b25fff irq 20 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:c8:4b:99 ehci0: Intel PCH USB 2.0 controller USB-B mem 0xc1b22000-0xc1b223ff irq 21 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: Intel PCH USB 2.0 controller USB-B on ehci0 pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3: ACPI PCI bus on pcib3 em1: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x1000-0x101f mem 0xc190-0xc191,0xc192-0xc1923fff irq 16 at device 0.0 on pci3 em1: Using MSIX interrupts em1: [ITHREAD] em1: [ITHREAD] em1: [ITHREAD] em1: Ethernet address: 00:15:17:c8:4b:98 pcib4: ACPI PCI-PCI bridge irq 18 at device 28.6 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 19 at device 28.7 on pci0 pci5: ACPI PCI bus on pcib5 ehci1: Intel PCH USB 2.0 controller USB-A mem 0xc1b21000-0xc1b213ff irq 23 at device 29.0 on pci0 ehci1: [ITHREAD] usbus1: EHCI version 1.0 usbus1: Intel PCH USB 2.0 controller USB-A on ehci1 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0
