usb pen drive not detecting



hi

I cant get bsd to detect any usb pen drives on my system. I have a generic
kernel with a few extra options that i cant see causing any issues.
I do get a few kernel messages when I plug the drive in (see below). The pen
drives are plugged directly into the usb headers on the back of the
motherboard ie not the kvm (which works)
I'm happy to supply any extra debug information


usbd_req_re_enumerate:1539: addr=4, set address failed! (USB_ERR_TIMEOUT,
ignored)
Root mount waiting for: usbus4
usbd_req_re_enumerate:1553: getting device descriptor at addr 4 failed,
USB_ERR_TIMEOUT!
ugen4.4: <(null)> at usbus4 (disconnected)
uhub_reattach_port:435: could not allocate new device!

$ usbconfig
ugen2.1: <UHCI root HUB Intel> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON
ugen3.1: <UHCI root HUB Intel> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON
ugen4.1: <EHCI root HUB Intel> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=ON
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON
ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON
ugen4.2: <product 0x6560 vendor 0x04b4> at usbus4, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE
ugen4.3: <USB KVM vendor 0x0d3d> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps)
pwr=ON

$ uname -a
FreeBSD X 8.0-BETA2 FreeBSD 8.0-BETA2 #2: Sat Jul 18 23:29:28 BST 2009
root@x:/usr/obj/usr/src/sys/me amd64


$ cat /sys/amd64/conf/me
include GENERIC


options KDTRACE_FRAME # Ensure frames are compiled in
options KDTRACE_HOOKS # Kernel DTrace hooks


options ALTQ
options ALTQ_CBQ
options ALTQ_RED
options ALTQ_RIO
options ALTQ_HFSC
options ALTQ_CDNR
options ALTQ_PRIQ
options ALTQ_NOPCC

device carp
options COM_MULTIPORT
device puc


_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • [PATCH 18-rc2] Fix typos in /Documentation : N-P
    ... Again, if you're not gonna do synchronization with disk drives (dang, ... -the kernel. ... There are two options specific to PSX driver portion. ... The driver uses the settings from the EEPROM set in the SCSI BIOS ...
    (Linux-Kernel)
  • Re: disk speed regression kernel 2.6.29 and after
    ... When I installed kernel 2.6.30, ... I currently have 3 hard drives hooked up. ... ACPI: ... CPU: L2 Cache: 512K ...
    (Linux-Kernel)
  • Major SATA / EXT3 Issue?
    ... I am curious if anyone else has had major problems with SATA drives on ... basis for my kernel build and test processes. ... Because I focused on hardware as the reason for the failure I ... # AX.25 network device drivers ...
    (Linux-Kernel)
  • athlon-xp + fakeraid regression
    ... The build completes fine, the kernel boots fine, the machine will seem to be fine as long as it remains quiescent. ... At the beginning, just after hitting enter on the make command, one of the ad4 disk light goes on solid for several seconds. ... There is a well known thing where these cheap pata fakeraid cards will try to do ata133 if the drive says it can, when really, even if he drives are new ata133 drives and the cables are new and short and shielded, you still shouldn't try to do ata133 since the spec is too tight and you'll just get bit errors or other failures. ... The fix is use ata100 somehow, either by disabling dma entirely in loader.conf (since you have no more selective option there, and the raid card bios never has an option for controlling pio/dma mode like motherboard bios's have) and then use atacontrol in rc.early to set udma5, or by using disks that can only do ata100 and only advertise ata100 to the controller. ...
    (freebsd-current)
  • Re: Where did you get them there devices ?
    ... point me to the mechanism or kernel ... controller, and the address of the controller. ... SCSI controllers, the order of the controllers depended on how the ... Drives on a SCSI controller have an address, ...
    (Fedora)
Loading