This is a discussion on USB 1.x or 2.0? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> hi folks, how do i get know what's my current USB device version? is it a USB-1.x or USB-2.0? ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| |||
| Steven Woody wrote: > hi folks, > > how do i get know what's my current USB device version? is it a > USB-1.x or USB-2.0? and how much speed difference between this two > specification? > > thanks. > > - > woody > You can look at /proc/bus/usb but the information that appear here are not very clear to me (there is also lsusb but I do not see this information). An alternative is to install lshw (http://ezix.org/project/wiki/HardwareLiSter). This tool provide a very comprehensive and clear view of your hardware (It will tell you amoung other the protocol and speed supported by your various USB devices) Olive |
| |||
| On Sat, 14 Apr 2007 09:22:20 +0200, Olive wrote: > Steven Woody wrote: >> hi folks, >> >> how do i get know what's my current USB device version? is it a USB-1.x >> or USB-2.0? and how much speed difference between this two >> specification? >> >> thanks. >> >> - >> woody >> >> > You can look at /proc/bus/usb but the information that appear here are > not very clear to me What's not "very clear" ? The parms labeled Spd: and Ver: for resp. 'speed' and 'version' are quite plain aren't they ?-) > (there is also lsusb but I do not see this > information). Use 'lsusb -v' and open the sleepy eye, you'll see the light ;D) |
| |||
| On Apr 14, 4:43 pm, loki harfagr <l...@DarkDesign.free.fr> wrote: > On Sat, 14 Apr 2007 09:22:20 +0200, Olive wrote: > > Steven Woody wrote: > >> hi folks, > > >> how do i get know what's my current USB device version? is it a USB-1.x > >> or USB-2.0? and how much speed difference between this two > >> specification? > > >> thanks. > > >> - > >> woody > > > You can look at /proc/bus/usb but the information that appear here are > > not very clear to me > > What's not "very clear" ? The parms labeled Spd: and Ver: > for resp. 'speed' and 'version' are quite plain aren't they ?-) > > > (there is also lsusb but I do not see this > > information). > > Use 'lsusb -v' and open the sleepy eye, you'll see the light ;D) sorry, i runed the lsusb, but still have not found what's the field indicating the version number? - woody |
| |||
| On Sat, 14 Apr 2007 20:04:27 -0700, Steven Woody wrote: > sorry, i runed the lsusb, but still have not found what's the field > indicating the version number? Look for a line like this: iProduct 2 UHCI Host Controller If you see "UHCI" that means USB 1.x If you see "EHCI" that means USB 2.x You may also see these terms (uhci/ehci) with the "lsmod" command, which would indicate which module was loaded, which would tell you what version of USB you have... -- "Ubuntu" -- an African word, meaning "Slackware is too hard for me". |
| |||
| Dan C <youmustbejoking@lan.invalid> wrote: > > You may also see these terms (uhci/ehci) with the "lsmod" command, which > would indicate which module was loaded, which would tell you what version > of USB you have... This would explain why the new USB flash reader I recently bought doesn't work while my somewhat older one does. I guess the new one isn't backwards compatible. - Kurt |
| |||
| ~kurt <actinouranium@earthlink.net>: > This would explain why the new USB flash reader I recently bought doesn't > work while my somewhat older one does. I guess the new one isn't > backwards compatible. Maybe it helps, to query the partition table by something like `fdisk -l /dev/sda` before mounting? This is, just to give the driver layers a chance, 'to see' the device somehow, before accessing it 'for real'. I have a flash reader here, which won't work otherwise. But this way it works reliably as expected. |
| |||
| On Sat, 14 Apr 2007 20:04:27 -0700, Steven Woody wrote: > On Apr 14, 4:43 pm, loki harfagr <l...@DarkDesign.free.fr> wrote: >> On Sat, 14 Apr 2007 09:22:20 +0200, Olive wrote: >> > Steven Woody wrote: >> >> hi folks, >> >> >> how do i get know what's my current USB device version? is it a >> >> USB-1.x or USB-2.0? and how much speed difference between this two >> >> specification? >> >> >> thanks. >> >> >> - >> >> woody >> >> > You can look at /proc/bus/usb but the information that appear here >> > are not very clear to me >> >> What's not "very clear" ? The parms labeled Spd: and Ver: >> for resp. 'speed' and 'version' are quite plain aren't they ?-) >> >> > (there is also lsusb but I do not see this information). >> >> Use 'lsusb -v' and open the sleepy eye, you'll see the light ;D) > > > sorry, i runed the lsusb, but still have not found what's the field > indicating the version number? That's the bcdUSB field that, for now, can take theses 3 values : 0x0100 (USB 1.0) 0x0110 (USB 1.1) 0x0200 (USB 2.0) The xHCI value is related to speed capabilities of the controller : There are three specs regarding host controllers, each one will support only a subset of USB 2.0 device speeds, the USB Enhanced Host Controller (EHCI) id for Hi-Speed USB Universal Host Controller (UHCI) and/or USB Open Host Controller (OHCI) are for "Full speed" and "low speed" These speed are determined by ceilings : Low speed, up to 1.5 Mbps Full speed, up to 12 Mbps Hi-Speed, up to 480 Mbps So, you need ehci and ohci (or uhci) modules to be loaded if you want/need different speeds, for instance I here have : # lsmod | grep '[oue]hci' ohci_hcd 19204 0 ehci_hcd 29580 0 Now, back to this nap attack ;-) |
| |||
| ~kurt wrote: > Dan C <youmustbejoking@lan.invalid> wrote: >> You may also see these terms (uhci/ehci) with the "lsmod" command, which >> would indicate which module was loaded, which would tell you what version >> of USB you have... > > This would explain why the new USB flash reader I recently bought doesn't work > while my somewhat older one does. I guess the new one isn't backwards > compatible. I had a USB device that took too long to initialize or something... To make it work, I had to - plug it in - wait for the device entry to appear - unmount the device - mount the device again Hope that helps, Daniel |