Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
Hi, On Saturday 23 June 2012 15:08:53 Thomas Mueller wrote: I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. I have here 2 hard disks and 2 flash drives with USB 2.0. Three of them work on FreeBSD on an USB 3.0 port. One hard disk only works on a USB 3.0 port. One hard drive with USB 3.0 does not work on USB 3.0 but only on 2.0. Irony is that the PCBSD installer installed PCBSD on the USB 3.0 disk but it did not boot afterward. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. Let me check this out. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Same as in my case. USB is more a lottery than real computing for me. Erich I suppose I could say NetBSD is more a lottery than real computing, especially on the new computer. But some of the bugs are consistent. My USB 3.0 hard drive is not bootable (motherboard issue?), also does not show on Grub2 Super Grub Disk on the System Rescue CD menu sysresccd.org Maybe the latter could be fixed by building Grub2 from source under either Linux or FreeBSD Ports. I think I'd also like to build the gdisk port, both on main hard drive and on a bootable FreeBSD USB stick. One USB stick (PNY 1 GB) is no longer readable/mountable from FreeBSD though it is from Linux. I thought that might be corruption. Since I have all that data now on an Ativa 4 GB USB stick, I could install the latest System Rescue CD to the PNY 1 GB USB stick (runs Linux on FAT32), see if there are any problems. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On 06/22/12 08:22, Hans Petter Selasky wrote: On Friday 22 June 2012 08:01:38 O. Hartmann wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted Hi, After plugging the device, try: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) --HPS I tried the USB drive this morning with the recommended quirk shown above on FreeBSD 10.0-CURRENT #1 r237462: Sat Jun 23 01:00:35 CEST 2012 without success. I get the same error message as shown above. With or without quirk. I then started Windows 7 on the same box. The USB drive is seen as expected and reflects what I experienced on every other non-FreeBSD box and hardware in the lab on last week. I reformatted the USB drive with extFAT and standard block size on Windows 7. The USB drive is now seen again on FreeBSD and recognized as a drive. Seen in my sloppy terminology means: recognized as a disk. The hardware is recognized, but it is not recognized as a drive. The fact, that the very first time after I bought that USB drive, I was able to put several GB on it, use it on both FreeBSD 9-STABLE and 10-CURRENT, and then it broke, drives me nuts. Using the very same pen drive on other OSes even on the same hardware without issues makes me believe FreeBSD does have an issue, not the USB drive. I will fill the USB drive with data and try to use it very often on FreeBSD. Last time the error occured, it was read by a Suse Linux box. If I wouldn't know better I would say Linux tries to kill the USB drive ... But Linux did see it all the time. A usual customer would see it the same way, I guess. I will test and report next week when I have access to the other boxes and OSes again. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
and hardware in the lab on last week. I reformatted the USB drive with extFAT and standard block size on Windows 7. The USB drive is now seen again on FreeBSD and recognized as this points that the pendrive's controller is not just flaky but horrid. The communiation with OS, and how/whether it is configured properly should not depend on what data is written to it - in your case exFAT metadata. It seems that controller manufacturer just did something to run on windows and linux instead of something that conform to USB mass storage interface standard :( Sorry but it may be hopeless case. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
My elder colleague often told me that it is the easiest and well-working way to check whether the one is certified to work for Mac OS X to get USB mass storage devices which work with *BSD :) Just my 5 yen, -|-__ YAMAMOTO, Taku | __ t...@tackymt.homeip.net What if a USB mass storage device works with some BSDs but not all? I had Kingston Data Travelers, 2 GB, from one lot that were good with Linux and FreeBSD but not NetBSD. Other USB sticks, including Kingston Data Tavelers, worked with Linux, FreeBSD and NetBSD. I even installed FreeDOS 1.1 prerelease on one of those NetBSD-averse Kingstom Data Travelers. But I think either Mac OS X, Linux or FreeBSD is much more production-ready than NetBSD. There are 3 drivers, one for 3.0, 2.0 and 1.0, and they are associated to corresponding devices at boot. I'll play around with it this weekend and see how to switch, i've also noticed issue connecting 2.0 device to 3.0 port. Waitman Gobble San Jose California USA I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. My Western Digital My Book Essential 3.0 TB USB 3.0 drive works even on the old computer whose motherboard's USB is 1.1. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
What if a USB mass storage device works with some BSDs but not all? well the only thing i never experiences with USB pendrives is a one that works everytime properly. Everything else is possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On 21 June 2012 23:22, Hans Petter Selasky hsela...@c2i.net wrote: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) Question - if that's the case, then why are we even doing that by default? Adrian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
Hi, On Saturday 23 June 2012 15:08:53 Thomas Mueller wrote: I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. I have here 2 hard disks and 2 flash drives with USB 2.0. Three of them work on FreeBSD on an USB 3.0 port. One hard disk only works on a USB 3.0 port. One hard drive with USB 3.0 does not work on USB 3.0 but only on 2.0. Irony is that the PCBSD installer installed PCBSD on the USB 3.0 disk but it did not boot afterward. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. Let me check this out. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Same as in my case. USB is more a lottery than real computing for me. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Saturday 23 June 2012 11:52:53 Adrian Chadd wrote: On 21 June 2012 23:22, Hans Petter Selasky hsela...@c2i.net wrote: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) Question - if that's the case, then why are we even doing that by default? Hi, Do you want a blacklist or do you want a whitelist? Please explain the pros and cons. I believe that those that program wrong shall be held responsible for that and given a chance to clean up, and not the opposite way around. As a senior programmer I can only testify that many people care equally little about what their computer is made of and what they eat. We probably need a control body to certify USB devices that is cheaper than USB.org, simply put. I think it is a bad idea to cripple all USB SCSI devices because what looks like the majority do not obey the rules of the specifications they are supposed to support. Else we need to make a new USB SCSI class for devices that are certified and one for devices that are not certified. Non-certified devices can have a limited SCSI command set, which should be implemented in the CAM layer like some kind of flag. If we could join heads on the Linux guys on this, we might be able to do something! Like having a pop-up every time a USB device fails certain tests. From the history we can predict what people will do when they do not know what they are doing. They will nail the guy doing it right and let the guy doing it wrong go free. And it seems like this happened before too ;-) I have a personal FreeBSD-native USB test utilty that runs mass storage devices through a series of tests. Most USB mass storage devices I've tested so far have obvious bugs, which either means their firmware can be hacked or made to crash. Also worth noting, that many USB device are not certified at all. It might be clever to look for the USB logo from USB.org next time you want to transfer X GB of personal data from location X to Y. --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Sat, 23 Jun 2012 15:50:05 +0700 Erich Dollansky articulated: USB is more a lottery than real computing for me. That is really sad. I am sort of forced to use USB devices on a daily basis, Luckily, very few of them involve FreeBSD, which is why I do not exhibit such a negative attitude, except of course when I do attempt to plug one in a FreeBSD machine with negative results. I do not know what is more pathetic; the fact that so many devices fail to operate correctly -- if at all --, or the willingness of the FreeBSD community to accept it as the norm. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
Hi, On Saturday 23 June 2012 18:18:58 Jerry wrote: On Sat, 23 Jun 2012 15:50:05 +0700 Erich Dollansky articulated: USB is more a lottery than real computing for me. That is really sad. I am sort of forced to use USB devices on a daily basis, Luckily, very few of them involve FreeBSD, which is why I do not exhibit such a negative attitude, except of course when I do attempt to plug one in a FreeBSD machine with negative results. I do not know what is more pathetic; the fact that so many devices fail to operate correctly -- if at all --, or the willingness of the FreeBSD community to accept it as the norm. I see it a bit different. There are standards. I hope that FreeBSD follows them as close as possible. There are also some grey areas in every standard. The grey areas can only be filled with manpower. This is the point where FreeBSD hits a wall. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Sat, Jun 23, 2012 at 1:08 AM, Thomas Mueller muelle...@insightbb.comwrote: My elder colleague often told me that it is the easiest and well-working way to check whether the one is certified to work for Mac OS X to get USB mass storage devices which work with *BSD :) Just my 5 yen, -|-__ YAMAMOTO, Taku | __ t...@tackymt.homeip.net What if a USB mass storage device works with some BSDs but not all? I had Kingston Data Travelers, 2 GB, from one lot that were good with Linux and FreeBSD but not NetBSD. Other USB sticks, including Kingston Data Tavelers, worked with Linux, FreeBSD and NetBSD. I even installed FreeDOS 1.1 prerelease on one of those NetBSD-averse Kingstom Data Travelers. But I think either Mac OS X, Linux or FreeBSD is much more production-ready than NetBSD. There are 3 drivers, one for 3.0, 2.0 and 1.0, and they are associated to corresponding devices at boot. I'll play around with it this weekend and see how to switch, i've also noticed issue connecting 2.0 device to 3.0 port. Waitman Gobble San Jose California USA I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. My Western Digital My Book Essential 3.0 TB USB 3.0 drive works even on the old computer whose motherboard's USB is 1.1. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org One possible 'caveat'.. I've noticed occasionally it will take 75 seconds or so for a USB 3.0 drive to 'connect'.. at first I thought the drive was not being 'recognized'. Someone has posted here that they believe it could be b/c a USB 3.0 uses 2x the power of 2.0 (i've not confirmed that) and it could be due to some kind of power management on the computer.. I've not yet taken the time to sort that out. anyhow this issue initially led me to believe there was some problem with the driver, but it seems likely not the case. Waitman Gobble San Jose California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
ports. Same as in my case. USB is more a lottery than real computing for me. but this is not USB standard fault, but USB device manufacturers that cannot really read standard specifications. It works (under windoze, under linux) is enough. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
daily basis, Luckily, very few of them involve FreeBSD, which is why I do not exhibit such a negative attitude, except of course when I do attempt to plug one in a FreeBSD machine with negative results. I do not know what is more pathetic; the fact that so many devices fail to operate correctly -- if at all --, or the willingness of the FreeBSD community to accept it as the norm. usb_quirks.c is already quite large as you may see... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Sat, 23 Jun 2012 15:00:29 +0200 (CEST) Wojciech Puchar articulated: ports. Same as in my case. USB is more a lottery than real computing for me. but this is not USB standard fault, but USB device manufacturers that cannot really read standard specifications. It works (under windoze, under linux) is enough. If the ROI does not exceed the expenditure to meet a specification that only applies to a niche segment of the potential market, then it is in all probability not going to happen. Furthermore, I have seen no documented proof that the problem actually exists with the device and not with the FreeBSD implementation of the specification nor with its supplied drivers. FreeBSD has not exactly been a leader in the implementation of USB. Apparently, it doesn't fully support all variants of USB http://wiki.freebsd.org/USB although that might have recently changed. In any case, as a wise man once stated, it is better to light a candle than curse the darkness. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
windoze, under linux) is enough. If the ROI does not exceed the expenditure to meet a specification that only applies to a niche segment of the potential market, then it is in all probability not going to happen. Right. Fine. There is not written on them conforms to USB Mass Storage standard ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted signature.asc Description: OpenPGP digital signature
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Thu, Jun 21, 2012 at 11:01 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? I don't personally have any relevant experience with this device, but having the exact revisions of code where this was working and where it was failing would be helpful, in order to perform a binary search to determine whether or not this is a regression. Thanks, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Friday 22 June 2012 08:01:38 O. Hartmann wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted Hi, After plugging the device, try: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
incapable of handling the 64GB drive. I do not have issues with USB it's not about capacity. But seems some quirks for that pendrive (which have buggy firmware) has to be added, as it doesn't respond for inquiry command. sorry i am not USB expert. umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Fri, Jun 22, 2012 at 1:01 AM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted I see similar behavior and output on my Dell M6500 notebook running CURRENT, but only on two ports which are some type of hybrid USB 2.0/3.0 (configurable via BIOS setting). If I use either of these ports with a USB 2.0 device while running the ports in USB 3.0 mode (using xhci(4)), I can't reliably get a device to properly attach. I say reliably, because every once in a while, I can plug a device in and it works fine, even multiple times and after reboots. If I configure these ports to run in USB 2.0 mode (using ehci(4)), all of my USB 2.0 devices seem to work without fail. However, USB 3.0 devices do not attach on these ports when they are configured as USB 2.0 ports. So, at least on my notebook, these ports must be configured at either 2.0 or 3.0, depending on which device I plan on using :( I have one other port on this same system that is USB 2.0-only, and it works all of the time :) I'll have to try and add a hub into the mix to see if perhaps it is a power issue (although with a recent Linux kernel and Windows 7, all is well no matter what configuration I provide). It may be that FreeBSD's USB subsystem lacks some extra bit of code required to configure the ports properly in regard to power. -Brandon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Jun 22, 2012 10:45 AM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Fri, Jun 22, 2012 at 1:01 AM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted I see similar behavior and output on my Dell M6500 notebook running CURRENT, but only on two ports which are some type of hybrid USB 2.0/3.0 (configurable via BIOS setting). If I use either of these ports with a USB 2.0 device while running the ports in USB 3.0 mode (using xhci(4)), I can't reliably get a device to properly attach. I say reliably, because every once in a while, I can plug a device in and it works fine, even multiple times and after reboots. If I configure these ports to run in USB 2.0 mode (using ehci(4)), all of my USB 2.0 devices seem to work without fail. However, USB 3.0 devices do not attach on these ports when they are configured as USB 2.0 ports. So, at least on my notebook, these ports must be configured at either 2.0 or 3.0, depending on which device I plan on using :( I have one other port on this same system that is USB 2.0-only, and it works all of the time :) I'll have to try and add a hub into the mix to see if perhaps it is a power issue (although with a recent Linux kernel and Windows 7, all is well no matter what configuration I provide). It may be that FreeBSD's USB subsystem lacks some extra bit of code required to configure the ports properly in regard to power. -Brandon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org There are 3 drivers, one for 3.0, 2.0 and 1.0, and they are associated to corresponding devices at boot. I'll play around with it this weekend and see how to switch, i've also noticed issue connecting 2.0 device to 3.0 port. Waitman Gobble San Jose California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to
