Re: Excessivly cheap USB device issue
On Tue, 2009-09-29 at 23:16 +1300, Andrew Thompson wrote: > On Tue, Sep 29, 2009 at 05:11:24AM -0500, Robert Noland wrote: > > On Tue, 2009-09-29 at 14:35 +0930, Daniel O'Connor wrote: > > > On Mon, 28 Sep 2009, Mike Tancsa wrote: > > > > >I also have a similar device, which I've been messing with a bit the > > > > >last couple of days. In your case, it isn't seeing the media, just > > > > > the "drive". I've had to try various combinations of unplugging > > > > > the adapter from usb, inserting the media then plugging it back in. > > > > > It does seem to work fairly reliably if you boot with the media > > > > > already inserted, but it doesn't seem to detect media change at > > > > > all. > > > > > > > > I get around it (on my cheap reader) by always doing a > > > > cat /dev/null > /dev/da1 > > > > whever I change or insert new media into the reader > > > > > > > > That seems to work with the gear I have 99% of the time. > > > > > > Hmm OK, I sort of expected fdisk da1 to fail straightaway though (it > > > takes ~30 seconds to fail for me). > > > > > > I have unplugged it for now, it interacts annoyingly with SANE because > > > that scans the SCSI bus(es) looking for scanner and each umass takes > > > 30+ seconds to fail. > > > > FWIW, on yesterdays kernel, mine seems to be working properly and > > detecting media change. I'm not sure what change helped. Note that I > > am running -CURRENT. > > Was that after the sync to Hans's repo? There were around 20 commits so > if anyone can narrow it down to a single rev then it may be able to be > merged. Looks like I'm at r197575, now. robert. > > Andrew > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Excessivly cheap USB device issue
On Tue, Sep 29, 2009 at 05:11:24AM -0500, Robert Noland wrote: > On Tue, 2009-09-29 at 14:35 +0930, Daniel O'Connor wrote: > > On Mon, 28 Sep 2009, Mike Tancsa wrote: > > > >I also have a similar device, which I've been messing with a bit the > > > >last couple of days. In your case, it isn't seeing the media, just > > > > the "drive". I've had to try various combinations of unplugging > > > > the adapter from usb, inserting the media then plugging it back in. > > > > It does seem to work fairly reliably if you boot with the media > > > > already inserted, but it doesn't seem to detect media change at > > > > all. > > > > > > I get around it (on my cheap reader) by always doing a > > > cat /dev/null > /dev/da1 > > > whever I change or insert new media into the reader > > > > > > That seems to work with the gear I have 99% of the time. > > > > Hmm OK, I sort of expected fdisk da1 to fail straightaway though (it > > takes ~30 seconds to fail for me). > > > > I have unplugged it for now, it interacts annoyingly with SANE because > > that scans the SCSI bus(es) looking for scanner and each umass takes > > 30+ seconds to fail. > > FWIW, on yesterdays kernel, mine seems to be working properly and > detecting media change. I'm not sure what change helped. Note that I > am running -CURRENT. Was that after the sync to Hans's repo? There were around 20 commits so if anyone can narrow it down to a single rev then it may be able to be merged. Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Excessivly cheap USB device issue
On Tue, 2009-09-29 at 14:35 +0930, Daniel O'Connor wrote: > On Mon, 28 Sep 2009, Mike Tancsa wrote: > > >I also have a similar device, which I've been messing with a bit the > > >last couple of days. In your case, it isn't seeing the media, just > > > the "drive". I've had to try various combinations of unplugging > > > the adapter from usb, inserting the media then plugging it back in. > > > It does seem to work fairly reliably if you boot with the media > > > already inserted, but it doesn't seem to detect media change at > > > all. > > > > I get around it (on my cheap reader) by always doing a > > cat /dev/null > /dev/da1 > > whever I change or insert new media into the reader > > > > That seems to work with the gear I have 99% of the time. > > Hmm OK, I sort of expected fdisk da1 to fail straightaway though (it > takes ~30 seconds to fail for me). > > I have unplugged it for now, it interacts annoyingly with SANE because > that scans the SCSI bus(es) looking for scanner and each umass takes > 30+ seconds to fail. FWIW, on yesterdays kernel, mine seems to be working properly and detecting media change. I'm not sure what change helped. Note that I am running -CURRENT. robert. -- Robert Noland FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Excessivly cheap USB device issue
On Mon, 28 Sep 2009, Mike Tancsa wrote: > >I also have a similar device, which I've been messing with a bit the > >last couple of days. In your case, it isn't seeing the media, just > > the "drive". I've had to try various combinations of unplugging > > the adapter from usb, inserting the media then plugging it back in. > > It does seem to work fairly reliably if you boot with the media > > already inserted, but it doesn't seem to detect media change at > > all. > > I get around it (on my cheap reader) by always doing a > cat /dev/null > /dev/da1 > whever I change or insert new media into the reader > > That seems to work with the gear I have 99% of the time. Hmm OK, I sort of expected fdisk da1 to fail straightaway though (it takes ~30 seconds to fail for me). I have unplugged it for now, it interacts annoyingly with SANE because that scans the SCSI bus(es) looking for scanner and each umass takes 30+ seconds to fail. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: Excessivly cheap USB device issue
At 10:47 AM 9/27/2009, Robert Noland wrote: > Sep 27 14:29:18 midget kernel: da1: Attempt to query device size failed: NOT READY, Medium not present > > If I connect a CF card to da1 and run 'fdisk da1' I get.. > [midget 0:06] ~ >fdisk da1 > load: 0.29 cmd: fdisk 69630 [cgticb] 1.50r 0.00u 0.00s 0% 1160k > load: 0.19 cmd: fdisk 69630 [cbwait] 24.42r 0.00u 0.00s 0% 1160k > load: 0.19 cmd: fdisk 69630 [cbwait] 27.01r 0.00u 0.00s 0% 1160k > fdisk: unable to get correct path for da1: Input/output error > > [midget 0:05] ~ >sudo usbconfig -u 5 -a 2 dump_device_desc > ugen5.2: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x > bDeviceSubClass = 0x > bDeviceProtocol = 0x > bMaxPacketSize0 = 0x0040 > idVendor = 0x058f > idProduct = 0x6362 > bcdDevice = 0x0129 > load: 0.21 cmd: usbconfig 69643 [WCTRL] 1.73r 0.00u 0.00s 0% 1080k > iManufacturer = 0x0001 > load: 0.19 cmd: usbconfig 69643 [WCTRL] 8.56r 0.00u 0.00s 0% 1104k > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > Perhaps some quirk would help but I'm not sure which one :) I also have a similar device, which I've been messing with a bit the last couple of days. In your case, it isn't seeing the media, just the "drive". I've had to try various combinations of unplugging the adapter from usb, inserting the media then plugging it back in. It does seem to work fairly reliably if you boot with the media already inserted, but it doesn't seem to detect media change at all. I get around it (on my cheap reader) by always doing a cat /dev/null > /dev/da1 whever I change or insert new media into the reader That seems to work with the gear I have 99% of the time. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Excessivly cheap USB device issue
On Mon, 2009-09-28 at 00:09 +0930, Daniel O'Connor wrote: > I have a very cheap USB CF/SD/SM/MS connected to an 8.0-RC1 system and > it is detected, ie.. > Sep 27 14:29:18 midget kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Sep 27 14:29:18 midget kernel: da0: Removable > Direct Access SCSI-0 device > Sep 27 14:29:18 midget kernel: da0: 40.000MB/s transfers > Sep 27 14:29:18 midget kernel: da0: Attempt to query device size failed: NOT > READY, Medium not present > Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): TEST UNIT READY. > CDB: 0 20 0 0 0 0 > Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): CAM Status: SCSI > Status Error > Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): SCSI Status: Check > Condition > Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): NOT READY > csi:0,aa,55,40 asc:3a,0 > Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Medium not present > Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Unretryable error > Sep 27 14:29:18 midget kernel: da1 at umass-sim0 bus 0 target 0 lun 1 > Sep 27 14:29:18 midget kernel: da1: Removable > Direct Access SCSI-0 device > Sep 27 14:29:18 midget kernel: da1: 40.000MB/s transfers > Sep 27 14:29:18 midget kernel: da1: Attempt to query device size failed: NOT > READY, Medium not present > > If I connect a CF card to da1 and run 'fdisk da1' I get.. > [midget 0:06] ~ >fdisk da1 > load: 0.29 cmd: fdisk 69630 [cgticb] 1.50r 0.00u 0.00s 0% 1160k > load: 0.19 cmd: fdisk 69630 [cbwait] 24.42r 0.00u 0.00s 0% 1160k > load: 0.19 cmd: fdisk 69630 [cbwait] 27.01r 0.00u 0.00s 0% 1160k > fdisk: unable to get correct path for da1: Input/output error > > [midget 0:05] ~ >sudo usbconfig -u 5 -a 2 dump_device_desc > ugen5.2: at usbus5, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x > bDeviceSubClass = 0x > bDeviceProtocol = 0x > bMaxPacketSize0 = 0x0040 > idVendor = 0x058f > idProduct = 0x6362 > bcdDevice = 0x0129 > load: 0.21 cmd: usbconfig 69643 [WCTRL] 1.73r 0.00u 0.00s 0% 1080k > iManufacturer = 0x0001 > load: 0.19 cmd: usbconfig 69643 [WCTRL] 8.56r 0.00u 0.00s 0% 1104k > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > Perhaps some quirk would help but I'm not sure which one :) I also have a similar device, which I've been messing with a bit the last couple of days. In your case, it isn't seeing the media, just the "drive". I've had to try various combinations of unplugging the adapter from usb, inserting the media then plugging it back in. It does seem to work fairly reliably if you boot with the media already inserted, but it doesn't seem to detect media change at all. robert. -- Robert Noland FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
