Adding another hard drive
I'm trying to add another hard drive into my system, a 250GB Western Digital 7200RPM SATA drive, and when I have it plugged into the motherboard the system hangs when it gets to: Timecounter TSC frequency 1803775604 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDRW LITE-ON COMBO SOHC-4836K/SPJ2 at ata1-master UDMA33 ad4: 114473MB Seagate ST3120213AS 3.AHH at ata2-master SATA150 Normally, I see the following line right after that: Trying to mount root from ufs:/dev/ad4s1a and then the mount messages, the daemon starting messages, and the login prompt. When I have the new hard drive plugged into a free SATA port on the motherboard, it hangs the system hard, I have to unplug the box from the wall to shut it down. The BIOS sees that drive just fine. If I unplug it from the SATA port on the motherboard, the system starts up just fine again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding another hard drive
John Nielsen wrote: Quoting Rich Demanowski [EMAIL PROTECTED]: I'm trying to add another hard drive into my system, a 250GB Western Digital 7200RPM SATA drive, and when I have it plugged into the motherboard the system hangs when it gets to: Timecounter TSC frequency 1803775604 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDRW LITE-ON COMBO SOHC-4836K/SPJ2 at ata1-master UDMA33 ad4: 114473MB Seagate ST3120213AS 3.AHH at ata2-master SATA150 I had a similar problem using a new SATA-II drive with my SATA150 controller. Once I closed the jumper to force the drive down to SATA150 operation the problem went away. This isn't necessary on most drive/controller combinations (the fallback is supposed to happen automatically), but it was for me and sounds like it may be for you. I had to do a bit of searching around to confirm the jumper function since it's more or less undocumented for my drive (a Seagate). Good luck, JN Oddly enough, the answer is even more simplistic than that ... I simply tried plugging it into a different open SATA connector on the motherboard. If I plug it into number 2 (number 1 is connected to the original SATA hard drive that came with the system, a 120GB Seagate), it locks the system up like I described earlier. If I plug it into number 3 ... everything works fine. Curious. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enabling sound?
Dylan Cochran wrote: I don't get the pcm0 lines that section 7.2.2 in the manual talks about. cat /dev/sndstat returns: FreeBSD Audio Driver (newpcm) Installed devices: and nothing else. The driver isn't attached to the device, either because the pci id's don't match or the card isn't using an emu10k* chip. Please type pciconf -l -v and reply with the portion that matches the card. [EMAIL PROTECTED]:10:0: class=0x040100 card=0x10061102 chip=0x00071102 rev=0x00 hdr=0x00 vendor = 'Creative Labs' device = 'CA0106-DAT Audigy LS' class= multimedia subclass = audio So, at the very least, FreeBSD knows there's *something* there, it just doesn't grok what it is that's there. I hope this helps, if you understand C and how pci works I grok some C, but I've never dealt with PCI peripherals before. I've only ever coded at the application level. you can use the pci id output that pciconf provides and modify the #define EMU10K1_PCI_ID0x00021102 line in /usr/src/sys/dev/sound/pci/emu10k1.c to match it, this will force the driver to try to bind to the card. That would be the chip=0x00071102 piece? This may not work, it's not supported, and definately DON'T link the driver to the kernel (ie, don't add a device snd_emu10k1 line to the kernel config) in the off chance it causes a strange hard lock problem. Good luck :) Thanks, I'll give it a go and see what happens. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enabling sound?
Dylan Cochran wrote: the pci id output that pciconf provides and modify the #define EMU10K1_PCI_ID0x00021102 line in /usr/src/sys/dev/sound/pci/emu10k1.c Well, at least I got a new response in dmesg out of that one: pcm0: Creative EMU10K1 port 0xcf00-0xcf1f irq 18 at device 10.0 on pci3 pcm0: AC97 reset timed out. pcm0: ac97 codec invalid or not present (id == 0) device_attach: pcm0 attach returned 6 I took the device sound and device snd_emu10k1 lines out of the kernel config, changed the line in emu10k1.c to EMU10K1_PCI_ID 0x00071102, recompiled, and added snd_emu10k1_load=YES to /boot/loader.conf Now it seems I need to tweak the AC97 stuff, too? Or, since pciconf shows this as an Audigy, should I instead tweak one of the EMU10K2 or K3 lines? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enabling sound?
Dylan Cochran wrote: I don't get the pcm0 lines that section 7.2.2 in the manual talks about. cat /dev/sndstat returns: FreeBSD Audio Driver (newpcm) Installed devices: and nothing else. The driver isn't attached to the device, either because the pci id's don't match or the card isn't using an emu10k* chip. Please type pciconf -l -v and reply with the portion that matches the card. Well, I'm still not getting any further. I pulled the SB Live! card out and enabled the on-board sound in the BIOS, to see if doing a kldload snd_driver would recognize *that*. It doesn't. The on-board sound shows up like this in pciconf -l -v: [EMAIL PROTECTED]:16:1: class=0x040300 card=0x2a3e103c chip=0x026c10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class= multimedia kldload snd_driver followed by cat /dev/sndstat yields: FreeBSD Audio Driver (newpcm) Installed devices: just like before. :( --- Information I can glean from looking at the SoundBlaster card: On the board: Sound Blaster Live! 24-bit Model: SB0410 On the chips: Creative CA0106-DAT LF (c) Creative Tech '02 C0524 KD692 Cirrus Logic CS4382-KQZ WAEXAR0452 WM WM8775SEDS 4AAADOG Everything else on there seems to be simple resistors, caps, and maybe a mosfet or three. Changing emu10k1.c so that the definition of EMU10K1_PCI_ID matches what pciconf -l -v found gets the module to recognize that there's a card there, and then it pukes on the ac97 stuff (which confuses me since this card claims to be ac97 compliant and the Cirrus chips is there ...) pcm0: Creative EMU10K1 port 0xcf00-0xcf1f irq 18 at device 10.0 on pci3 pcm0: AC97 reset timed out. pcm0: ac97 codec invalid or not present (id == 0) device_attach: pcm0 attach returned 6 Looking through sound/pcm/ac97.c I can see that the reset() function is failing, and the id = line in the ac97_initmixer() function isn't recognizing the chip on the board. I got a SoundBlaster Live! because it was listed as a known working piece of hardware. Apparently this is a newer version of the board that isn't supported yet. Getting it to work is becoming a PITA beyond what I have the time and willpower to put in right now. Is there a piece of sound hardware I can just run down to CompUSA and buy, that I can drop in here and get this thing working with *today*? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Enabling sound?
I just dropped a SoundBlaster Live! card into my box, and have followed the directions in the handbook and the man pages. The following lines are in the compiled kernel: device sound device snd_emu10k1 I don't get the pcm0 lines that section 7.2.2 in the manual talks about. cat /dev/sndstat returns: FreeBSD Audio Driver (newpcm) Installed devices: and nothing else. kldload snd_emu10k1 yields no output whatsoever. When followed by cat /dev/sndstat it produces the same outputs as above. kld_load snd_driver yields: ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0x20 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled I recompiled with the sound and emu10k1 drivers commented out, and the kldload and cat /dev/sndstat commands still yield the same. I need to get sound enabled on this box, so I can do some online training provided through streaming video. Please, please, please tell me I don't have to break down and install wankers on this thing ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enabling sound?
Derrick Ryalls wrote: On 7/21/06, Rich Demanowski [EMAIL PROTECTED] wrote: I just dropped a SoundBlaster Live! card into my box, and have followed the directions in the handbook and the man pages. The following lines are in the compiled kernel: device sound device snd_emu10k1 I don't get the pcm0 lines that section 7.2.2 in the manual talks about. cat /dev/sndstat returns: FreeBSD Audio Driver (newpcm) Installed devices: and nothing else. kldload snd_emu10k1 yields no output whatsoever. When followed by cat /dev/sndstat it produces the same outputs as above. kld_load snd_driver yields: ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0x20 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled I recompiled with the sound and emu10k1 drivers commented out, and the kldload and cat /dev/sndstat commands still yield the same. I need to get sound enabled on this box, so I can do some online training provided through streaming video. Please, please, please tell me I don't have to break down and install wankers on this thing ... I would try this: kldload snd_driver then cat /dev/sndstat to see if perhaps a different driver is needed. I tried that. That's what got me all the ppc0 and sio1 errors. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enabling sound?
Derrick Ryalls wrote: On 7/21/06, Rich Demanowski [EMAIL PROTECTED] wrote: I just dropped a SoundBlaster Live! card into my box, and have followed the directions in the handbook and the man pages. The following lines are in the compiled kernel: device sound device snd_emu10k1 I don't get the pcm0 lines that section 7.2.2 in the manual talks about. cat /dev/sndstat returns: FreeBSD Audio Driver (newpcm) Installed devices: and nothing else. kldload snd_emu10k1 yields no output whatsoever. When followed by cat /dev/sndstat it produces the same outputs as above. kld_load snd_driver yields: ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0x20 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled I recompiled with the sound and emu10k1 drivers commented out, and the kldload and cat /dev/sndstat commands still yield the same. I need to get sound enabled on this box, so I can do some online training provided through streaming video. Please, please, please tell me I don't have to break down and install wankers on this thing ... I would try this: kldload snd_driver then cat /dev/sndstat to see if perhaps a different driver is needed. Also, you shouldn't need to recompile, just add the driver line to /boot/loader.conf as described in the handbook. Could this be (part of?) the problem? -- in dmesg: . . . isab0: PCI-ISA bridge at device 10.0 on pci0 . . . pci3: multimedia, audio at device 10.0 (no driver attached) I've re-compiled my kernel yet again to remove the sio device, since this thing has no 8250 or 16[45]50 serial ports on it, which got rid of the error messages in dmesg I was seeing about the port not being enabled and the IRQ not mapping. It also has no parallel port on it -- can I remove the ppc, ppbus, lpt, plip, and ppi devices without breaking anything else? The only peripheral ports this thing has on it are USB2. I'm pretty much stuck with a custom kernel on this machine, since the wireless network I'm on requires WEP, and the wlan_wep module would need to be loaded by hand if I went with the generic kernel and module loading ... which would also mean hand-starting dhcpclient and ifconfig, since both will fail at boot-time without wlan_wep. All the wireless stuff works just fine with ath, ath_hal, ath_rate_sample, wlan, and wlan_wep compiled into the kernel. The only thing I can't seem to get working is this blasted sound card. I wouldn't even worry about it if I didn't have to do this stupid flash based video training crap (why can't they just send me TFM so I can R it?!?). *sigh* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB and 6.1-RELEASE
Micah wrote: Rich Demanowski wrote: scbus, da, pass, ohci, uhci, ehci, usb, udbp, ugen, uhid, ukbd, ulpt, umass, ums, ural, urio and uscanner are all enabled in the running kernel's /usr/src/sys/i386/conf config file. usbd is not running. When I try to start usbd I get the following: No USB host controllers found. There are no usb* devices listed in /dev. in dmesg I get the following with regard to ohci0 and ehci0: ohci0: OHCI (generic) USB controller mem 0xfe02f000-0xfe02 at device 11.0 on pci0 pcib0: unable to route slot 11 INTA ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xfe02e000-0xfe02e0ff at device 1 1.1 on pci0 pcib0: unable to route slot 11 INTB ehci0: Could not allocate irq device_attach: ehci0 attach returned 6 When I plug the drive into any of the USB ports on the system, nothing happens in dmesg or /var/log/messages. camcontrol devlist lists no devices. I'm a bit confused as to why my USB keyboard and mouse function, but my thumb drive will not. It's likely that your BIOS has legacy support enabled in which case, as far as FreeBSD is concerned, you actually have a regular keyboard and mouse. That would explain why the mouse and keyboard work while other USB items do not. From the messages you gave, it's clear that FreeBSB is unable to connect to the USB controller. Disabling legacy support in the BIOS may help. Otherwise check your BIOS for other USB related settings and try changing those. Indeed, legacy support is enabled (actually auto was the setting in the BIOS). When I disable it, the keyboard and mouse cease functioning, as well. That was the only setting I could find in the BIOS related to USB. I suppose that means the on-board USB controller is one not supported by existing drivers? Or at least ones not listed in the GENERIC config on which I based my kernel (all I added was the ath drivers for my wireless)? I don't know which chipset it is, but my guess is, since the on-board video and LAN is an nVidia chipset, that the USB controller probably is, as well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB and 6.1-RELEASE
Micah wrote: Rich Demanowski wrote: Micah wrote: Rich Demanowski wrote: scbus, da, pass, ohci, uhci, ehci, usb, udbp, ugen, uhid, ukbd, ulpt, umass, ums, ural, urio and uscanner are all enabled in the running kernel's /usr/src/sys/i386/conf config file. usbd is not running. When I try to start usbd I get the following: No USB host controllers found. There are no usb* devices listed in /dev. in dmesg I get the following with regard to ohci0 and ehci0: ohci0: OHCI (generic) USB controller mem 0xfe02f000-0xfe02 at device 11.0 on pci0 pcib0: unable to route slot 11 INTA ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xfe02e000-0xfe02e0ff at device 1 1.1 on pci0 pcib0: unable to route slot 11 INTB ehci0: Could not allocate irq device_attach: ehci0 attach returned 6 When I plug the drive into any of the USB ports on the system, nothing happens in dmesg or /var/log/messages. camcontrol devlist lists no devices. I'm a bit confused as to why my USB keyboard and mouse function, but my thumb drive will not. It's likely that your BIOS has legacy support enabled in which case, as far as FreeBSD is concerned, you actually have a regular keyboard and mouse. That would explain why the mouse and keyboard work while other USB items do not. From the messages you gave, it's clear that FreeBSB is unable to connect to the USB controller. Disabling legacy support in the BIOS may help. Otherwise check your BIOS for other USB related settings and try changing those. Indeed, legacy support is enabled (actually auto was the setting in the BIOS). When I disable it, the keyboard and mouse cease functioning, as well. That was the only setting I could find in the BIOS related to USB. I suppose that means the on-board USB controller is one not supported by existing drivers? Or at least ones not listed in the GENERIC config on which I based my kernel (all I added was the ath drivers for my wireless)? I don't know which chipset it is, but my guess is, since the on-board video and LAN is an nVidia chipset, that the USB controller probably is, as well. Based on the error messages I think it's still worth trying some different settings. FeeeBSD seems to recognize the controller but it is unable to allocate the right resources to it. Check your BIOS for a PnP OS setting and toggle it. Also, try booting with ACPI disabled (or enabled) from the FreeBSD boot menu. IIRC, ACPI can have a hand in routing resources. HTH, Micah ACPI is turned off. The install disc wouldn't even boot at all with it turned on. I'll try the Plug-and-play OS setting. It's currently on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB and 6.1-RELEASE
Micah wrote: Rich Demanowski wrote: Micah wrote: Rich Demanowski wrote: Micah wrote: Rich Demanowski wrote: scbus, da, pass, ohci, uhci, ehci, usb, udbp, ugen, uhid, ukbd, ulpt, umass, ums, ural, urio and uscanner are all enabled in the running kernel's /usr/src/sys/i386/conf config file. usbd is not running. When I try to start usbd I get the following: No USB host controllers found. There are no usb* devices listed in /dev. in dmesg I get the following with regard to ohci0 and ehci0: ohci0: OHCI (generic) USB controller mem 0xfe02f000-0xfe02 at device 11.0 on pci0 pcib0: unable to route slot 11 INTA ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xfe02e000-0xfe02e0ff at device 1 1.1 on pci0 pcib0: unable to route slot 11 INTB ehci0: Could not allocate irq device_attach: ehci0 attach returned 6 When I plug the drive into any of the USB ports on the system, nothing happens in dmesg or /var/log/messages. camcontrol devlist lists no devices. I'm a bit confused as to why my USB keyboard and mouse function, but my thumb drive will not. It's likely that your BIOS has legacy support enabled in which case, as far as FreeBSD is concerned, you actually have a regular keyboard and mouse. That would explain why the mouse and keyboard work while other USB items do not. From the messages you gave, it's clear that FreeBSB is unable to connect to the USB controller. Disabling legacy support in the BIOS may help. Otherwise check your BIOS for other USB related settings and try changing those. Indeed, legacy support is enabled (actually auto was the setting in the BIOS). When I disable it, the keyboard and mouse cease functioning, as well. That was the only setting I could find in the BIOS related to USB. I suppose that means the on-board USB controller is one not supported by existing drivers? Or at least ones not listed in the GENERIC config on which I based my kernel (all I added was the ath drivers for my wireless)? I don't know which chipset it is, but my guess is, since the on-board video and LAN is an nVidia chipset, that the USB controller probably is, as well. Based on the error messages I think it's still worth trying some different settings. FeeeBSD seems to recognize the controller but it is unable to allocate the right resources to it. Check your BIOS for a PnP OS setting and toggle it. Also, try booting with ACPI disabled (or enabled) from the FreeBSD boot menu. IIRC, ACPI can have a hand in routing resources. HTH, Micah OK, disabling Plug-n-Play OS *and* USB legacy support now has the system recognizing the USB controllers. It also seems to have fixed the odd CAPSLOCK character duplication I was getting, and my mouse scroll wheel now works. Now I'm on to another issue. When I plug in the thumb drive, which is a 512MB USB 2.0 Mobile Swingdrive, containing an MS-DOS filesystem, I get the following: umass0: vendor 0x0930 USB Flash Memory, rev 2.00/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: USB Flash Memory 1.04 Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 489MB (1001472 512 byte sectors: 64H 32S/T 489C) umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Phase Error, residue = 0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 mount /dev/da0 /thumb yields the error: mount: /dev/da0 on /thumb: incorrect super block
USB and 6.1-RELEASE
I've searched through and browsed the archives, and can't find anything that helps me with this. I've recently gotten my Compaq SR1910NX up and running on FreeBSD 6.1, but am having trouble getting it to recognize my SwingDrive umass device (USB 2.0, 512MB). The only thing that's different from this machine's from-the-factory configuration is the addition of a Linksys WMP55AG wireless card, which is working just fine thanks to the ath driver. I know the USB controller is working because both my USB keyboard and my USB mouse function (though the keyboard (a Happy Hacking Lite 2) is a little quirky ... when I hold down the shift key to type a word in all caps, it doubles up the letters LIKEKE THTHIISS sometimes, and I still haven't gotten Xorg to recognize the scroll wheel on the mouse). scbus, da, pass, ohci, uhci, ehci, usb, udbp, ugen, uhid, ukbd, ulpt, umass, ums, ural, urio and uscanner are all enabled in the running kernel's /usr/src/sys/i386/conf config file. usbd is not running. When I try to start usbd I get the following: No USB host controllers found. There are no usb* devices listed in /dev. in dmesg I get the following with regard to ohci0 and ehci0: ohci0: OHCI (generic) USB controller mem 0xfe02f000-0xfe02 at device 11.0 on pci0 pcib0: unable to route slot 11 INTA ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xfe02e000-0xfe02e0ff at device 1 1.1 on pci0 pcib0: unable to route slot 11 INTB ehci0: Could not allocate irq device_attach: ehci0 attach returned 6 When I plug the drive into any of the USB ports on the system, nothing happens in dmesg or /var/log/messages. camcontrol devlist lists no devices. I'm a bit confused as to why my USB keyboard and mouse function, but my thumb drive will not. Any ideas? Did I miss something in the kernel config? Do I need to enable something in rc.conf? According to what's in the FreeBSD handbook, this should be working ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
