Re: why this new stick fail to boot

[tomas]

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

signature.asc
Description: PGP signature