Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #274509 > unrolled thread

Re: why this new stick fail to boot

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: why this new stick fail to boot Dan Ritter <dsr@randomstring.org> - 2024-11-13 00:30 +0100
    Re: why this new stick fail to boot <tomas@tuxteam.de> - 2024-11-13 06:40 +0100
    Re: why this new stick fail to boot <tomas@tuxteam.de> - 2024-11-13 20:30 +0100

#274509 — Re: why this new stick fail to boot

hlyg wrote: 
> 
> easiest way to identify usb3 is look at color, both connector and connectee
> shall be blue

As it turns out, that's not a requirement.

USB A ports can be white, black, blue, red, yellow, green, teal
or purple... or pretty much any other color in the future.

It's normal for a manufacturer to make all the ports of a given
generation on a single device the same color, but even that is
not mandatory.

(There are some websites that claim a mandatory assignation of 
color to speed. Note that they don't cite sources.)


-dsr-

[toc] | [next] | [standalone]

#274510

[Multipart message — attachments visible in raw view] — view raw

On Tue, Nov 12, 2024 at 06:07:48PM -0500, Dan Ritter wrote:
> hlyg wrote: 
> > 
> > easiest way to identify usb3 is look at color, both connector and connectee
> > shall be blue
> 
> As it turns out, that's not a requirement.

Just a recommendation:

  "USB 3.0 Type-A and B connectors are usually blue, to distinguish
   them from USB 2.0 connectors, as recommended by the specification"
   [1]
> 
> USB A ports can be white, black, blue, red, yellow, green, teal
> or purple... or pretty much any other color in the future.
> 
> It's normal for a manufacturer to make all the ports of a given
> generation on a single device the same color, but even that is
> not mandatory.
> 
> (There are some websites that claim a mandatory assignation of 
> color to speed. Note that they don't cite sources.)

The ref [1] has a source for that.

But yes, it's "just" a recommendation, and USB2 doesn't recommend
*not* to use blue, so...

You can try to peek into the connector and try to spot those extra
five pins. But then, the nasty manufacturer might have left them
unconnected...

Cheers

[1] https://en.wikipedia.org/wiki/USB-3
-- 
t

[toc] | [prev] | [next] | [standalone]

#274516

[Multipart message — attachments visible in raw view] — view raw

On Thu, Nov 14, 2024 at 02:31:42AM +0800, hlyg wrote:
> Thank tomas! actually i am amateur on this subject

You are welcome :-)

We all are amateurs (amateur is French and means you love something,
so... :)

> but at my local market, usb devices aren't as colorful as Ritter describe,
> blue indicates usb3

Most of the time it is true. But you don't know until you try :-)

For example, my laptop's ports are black, but they are USB3 capable.

If I stick an old, 2.0 stick, "lsusb -v" (needs sudo) says:

  Bus 001 Device 006: ID 0781:5567 SanDisk Corp. Cruzer Blade
  Device Descriptor:
    bLength                18
    bDescriptorType         1
    bcdUSB               2.00
    bDeviceClass            0 
    bDeviceSubClass         0 
    bDeviceProtocol         0 
    bMaxPacketSize0        64
    idVendor           0x0781 SanDisk Corp.
    idProduct          0x5567 Cruzer Blade
    bcdDevice            1.03
    iManufacturer           1 SanDisk
    iProduct                2 Cruzer Blade
    iSerial                 3 200443243302BCC0F8A8
    bNumConfigurations      1

See the "bcdUSB" there? It's 2.0. Whereas a more modern stick, which
I bought two weeks ago for a local Linux install party says:

  Bus 002 Device 003: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Kyson
  Device Descriptor:
    bLength                18
    bDescriptorType         1
    bcdUSB               3.20
    bDeviceClass            0 
    bDeviceSubClass         0 
    bDeviceProtocol         0 
    bMaxPacketSize0         9
    idVendor           0x0951 Kingston Technology
    idProduct          0x1666 DataTraveler 100 G3/G4/SE9 G2/50 Kyson
    bcdDevice            1.10
    iManufacturer           2 Kingston
    iProduct                3 DataTraveler 3.0
    iSerial                 4 4CEDFB74A3A417C1791703BA
    bNumConfigurations      1

Now bcdUSB says 3.2

Cheers
-- 
t

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web