WD MyBook Essential problem
Dear Colleagues, I've just purchased this External 1,5 TB HD: http://www.wdc.com/en/products/products.aspx?id=240 All is fine except of one thing: it is not detected during the system boot - I can see it only when I physically reattach it after every reboot. To make it more complicated, I did tests with my older WD MyBook 750 GB and it is detected in exactly the same conditions (same system). I really hoped that yesterday upgrade from 8.1 to 8.2-RELESE could have helped, but it didn't change anything. This is what I get after reattaching during normal system usage: # dmesg . ugen4.2: Western Digital at usbus4 (disconnected) umass0: at uhub4, port 3, addr 2 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry uhid0: at uhub4, port 3, addr 2 (disconnected) ugen4.2: vendor 0x1058 at usbus4 umass0: vendor 0x1058 My Book 1130, class 0/0, rev 2.10/10.12, addr 2 on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: WD My Book 1130 1012 Fixed Direct Access SCSI-6 device da0: 40.000MB/s transfers da0: 1430767MB (2930210816 512 byte sectors: 255H 63S/T 182397C) ses0 at umass-sim0 bus 0 scbus0 target 0 lun 1 ses0: WD SES Device 1012 Fixed Enclosure Services SCSI-6 device ses0: 40.000MB/s transfers ses0: SCSI-3 SES Device # camcontrol devlist WD My Book 1130 1012 at scbus0 target 0 lun 0 (pass0,da0) WD SES Device 1012 at scbus0 target 0 lun 1 (pass1,ses0) //this is the same physical device # camcontrol rescan all Re-scan of bus 0 was successful # camcontrol reset all Reset of bus 0 returned error 0x3a ## And this is what I get after rebooting with the HD attached: # dmesg . Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Root mount waiting for: usbus4 Root mount waiting for: usbus4 usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) Root mount waiting for: usbus4 Root mount waiting for: usbus4 usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) Root mount waiting for: usbus4 ugen4.2: Unknown at usbus4 (disconnected) uhub_reattach_port: could not allocate new device . # camcontrol devlist //nothing here # camcontrol rescan all camcontrol: CAMIOCOMMAND ioctl failed: Invalid argument # camcontrol reset all camcontrol: CAMIOCOMMAND ioctl failed: Invalid argument So now I have to reach the server physically to reattach the HD to get the output presented first (and to have it work). I tried it with SCSI_DELAY=5000 (default kernel value) as well as with 15000 ms. I tried in /etc/rc.conf: usbd_enable=YES dbus_enable=YES hald_enable=YES but it didn't change anything, same as: ahci_load=YES uhci_load=YES ohci_load=YES ehci_load=YES usb_load=YES # USB subsystem ugen_load=YES # USB generic device, if all else fails ... uhid_load=YES # Human Interface Devices umass_load=YES # Mass Storage Devices in /boot/loader.conf Any idea what can be the reason? I purchased 2 such HDs for 2 separate FreeBSD systems, which doubles my problem ;) In Ubuntu there's no such issue - the HD works fine. I've spent dozens of hours on that, and still am in the same point... Thank you very much in advance for any clue. Jacek ___ 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
Serious bandwidth regression in if_axe (uether)
Hi all. I just stumbled across a problem with my network throughput that appears to be linked to recent changes. In [FreeBSD 8.1-STABLE #10 r214834: Fri Nov 5 18:20:58 CET 2010] my D-Link DUB-E100 Fast Ethernet USB 2.0 adapter, configured via if_axe (uether) delivers an expected 20 MBit throughput (downstream) via my provider (20MBit downstream is the maximum I get from provider). However starting with [FreeBSD 8.2-PRERELEASE #11 r217577: Wed Jan 19 16:50:07 CET 2011] the throughput is down to 5.62 MBit (tested with various reference hosts, 5.62MBit is the best I got). The latter is also true for 8.2-RELEASE. Is this already a known problem? Thanks in advance, Marcus -- Marcus Mueller . . . crack-admin/coder ;-) Mulle kybernetiK . http://www.mulle-kybernetik.com Current projects: http://www.mulle-kybernetik.com/znek/ ___ 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: failed to start webcamd
martinko wrote: Hans Petter Selasky wrote: On Monday 28 February 2011 19:35:38 martinko wrote: Hi, I've just installed webcamd port to try out my Logitech HD camera. However, when plugging the camera in I get root: /usr/local/etc/rc.d/webcamd: WARNING: failed to start webcamd message, then camera is disconnected, connected again and it all repeats (cycle about 1 second). Where should I start looking at please ? Hi, There is a new webcamd port coming soon. Can you give that a try first and see if the problem is still the same? --HPS Hi! I had a little difficulty applying the patch and later restarting devd (WARNING: failed to start devd) but the end result seems interesting: kernel: ugen3.2: vendor 0x046d at usbus3 kernel: uaudio0: vendor 0x046d product 0x0823, class 239/2, rev 2.00/0.10, addr 2 on usbus3 kernel: uaudio0: No playback! kernel: uaudio0: Record: 32000 Hz, 2 ch, 16-bit S-LE PCM format kernel: uaudio0: No midi sequencer kernel: pcm1: USB audio on uaudio0 So I do have audio but where is video ? And how should I test it ? :-) Cheers, Martin Hi, I've just updated to the latest webcamd port and restarted my system. Though I can see video0 node in /dev now, there is no message when attaching device. Actually, I get the following: Mar 2 16:14:56 kernel: ugen3.2: vendor 0x046d at usbus3 (disconnected) Mar 2 16:14:56 kernel: uaudio0: at uhub3, port 3, addr 2 (disconnected) Mar 2 16:14:56 kernel: pcm1: detached Mar 2 16:15:06 kernel: ugen3.2: vendor 0x046d at usbus3 Mar 2 16:15:06 kernel: uaudio0: vendor 0x046d product 0x0823, class 239/2, rev 2.00/0.10, addr 2 on usbus3 Mar 2 16:15:07 root: /usr/local/etc/rc.d/webcamd: WARNING: failed to start webcamd Mar 2 16:15:07 root: Unknown USB device: vendor 0x046d product 0x0823 bus uhub3 Mar 2 16:15:07 root: Unknown USB device: vendor 0x046d product 0x0823 bus uhub3 Mar 2 16:15:07 kernel: uaudio0: No playback! Mar 2 16:15:07 kernel: uaudio0: Record: 32000 Hz, 2 ch, 16-bit S-LE PCM format Mar 2 16:15:07 kernel: uaudio0: No midi sequencer Mar 2 16:15:07 kernel: pcm1: USB audio on uaudio0 Mar 2 16:15:07 root: Unknown USB device: vendor 0x046d product 0x0823 bus uhub3 Any ideas what might be going on please ? Cheers, Martin PS: The camera does support UVC -- http://www.logitech.com/en-us/for-business/products/webcams-headsets/devices/7364 -- and its siblings are listed in uvc(4) man page as supported. ___ 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
Add ID to USB drive for MS Excel
Hi Have 2 or more USB RFID reader pen drives which work ok and place the tag read into Excel. See:- http://www.rfidshop.com/lf-usb-pen-reader-uniqueem4102-1120-p.asp How can I get a prefix/suffix ID for each USB RFID device ? so that when placed into Excel there is an ID for each reader used and Excel can deal with that. Thanks Charlie -- View this message in context: http://old.nabble.com/Add-ID-to-USB-drive-for-MS-Excel-tp31055720p31055720.html Sent from the freebsd-usb mailing list archive at Nabble.com. ___ 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: why does ulpt depend on ucom?
On 2011-03-01 2:08 AM, Hans Petter Selasky wrote: On Tuesday 01 March 2011 11:03:54 Carl wrote: Hans, do I need to submit bug reports for any of these things or will you just be checking in all the necessary fixes? Send me a patch and I will fix it. I've attached a patch for the man pages distributed with 8.1-RELEASE. As an end user rather than FreeBSD developer, I wouldn't know how to go about moving ulpt.c to a more appropriate place in the source tree. --Carl diff -u 8.1-RELEASE/usr/src/share/man/man4/u3g.4 8.1-RELEASE-patched/usr/src/share/man/man4/u3g.4 --- 8.1-RELEASE/usr/src/share/man/man4/u3g.42011-03-01 13:44:50.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/u3g.42011-03-01 13:59:18.0 -0800 @@ -30,7 +30,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device u3g -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/uark.4 8.1-RELEASE-patched/usr/src/share/man/man4/uark.4 --- 8.1-RELEASE/usr/src/share/man/man4/uark.4 2011-03-01 13:44:58.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/uark.4 2011-03-01 13:59:18.0 -0800 @@ -28,7 +28,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device uark -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/ubsa.4 8.1-RELEASE-patched/usr/src/share/man/man4/ubsa.4 --- 8.1-RELEASE/usr/src/share/man/man4/ubsa.4 2011-03-01 13:45:27.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/ubsa.4 2011-03-01 13:59:18.0 -0800 @@ -47,7 +47,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device ubsa -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/uchcom.4 8.1-RELEASE-patched/usr/src/share/man/man4/uchcom.4 --- 8.1-RELEASE/usr/src/share/man/man4/uchcom.4 2011-03-01 13:45:23.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/uchcom.4 2011-03-01 13:59:18.0 -0800 @@ -41,7 +41,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device uchcom -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/ufoma.4 8.1-RELEASE-patched/usr/src/share/man/man4/ufoma.4 --- 8.1-RELEASE/usr/src/share/man/man4/ufoma.4 2011-03-01 13:45:38.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/ufoma.4 2011-03-01 13:59:18.0 -0800 @@ -39,7 +39,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device ufoma -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/uftdi.4 8.1-RELEASE-patched/usr/src/share/man/man4/uftdi.4 --- 8.1-RELEASE/usr/src/share/man/man4/uftdi.4 2011-03-01 13:45:45.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/uftdi.4 2011-03-01 13:59:18.0 -0800 @@ -48,7 +48,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device uftdi -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/uipaq.4 8.1-RELEASE-patched/usr/src/share/man/man4/uipaq.4 --- 8.1-RELEASE/usr/src/share/man/man4/uipaq.4 2011-03-01 13:45:55.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/uipaq.4 2011-03-01 13:59:18.0 -0800 @@ -42,7 +42,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device uipaq -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/umct.4 8.1-RELEASE-patched/usr/src/share/man/man4/umct.4 --- 8.1-RELEASE/usr/src/share/man/man4/umct.4 2011-03-01 13:46:07.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/umct.4 2011-03-01 13:59:18.0 -0800 @@ -37,7 +37,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device umct -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/umodem.4 8.1-RELEASE-patched/usr/src/share/man/man4/umodem.4 --- 8.1-RELEASE/usr/src/share/man/man4/umodem.4 2011-03-01 13:46:11.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/umodem.4 2011-03-01 13:59:18.0 -0800 @@ -48,7 +48,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device umodem -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/uplcom.4 8.1-RELEASE-patched/usr/src/share/man/man4/uplcom.4 --- 8.1-RELEASE/usr/src/share/man/man4/uplcom.4 2011-03-01 13:46:18.0 -0800 +++ 8.1-RELEASE-patched/usr/src/share/man/man4/uplcom.4 2011-03-01 13:59:18.0 -0800 @@ -48,7 +48,6 @@ kernel configuration file: .Bd -ragged -offset indent .Cd device uplcom -.Cd device ucom .Ed .Pp Alternatively, to load the driver as a diff -u 8.1-RELEASE/usr/src/share/man/man4/uslcom.4 8.1-RELEASE-patched/usr/src/share/man/man4/uslcom.4 ---
