1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: why this new stick fail to boot

    From Charles Curley@21:1/5 to hlyg on Mon Nov 11 05:30:01 2024
    On Mon, 11 Nov 2024 06:57:23 +0800
    hlyg <hlyg2023@outlook.com> wrote:

    this usb stick has 2 interfaces: usb type A and C, for pc and cell
    phone

    i install bullseye on it, installation finish without error

    but booting fails, it is ignored, boot from hard disk, not usb disk

    freebsd has same problem

    Both bullseye and freeBSD failing suggests that the firmware is not set
    to boot to the USB stick. While you're at it, turn off secure boot.

    --
    Does anybody read signatures any more?

    https://charlescurley.com
    https://charlescurley.com/blog/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Wright@21:1/5 to hlyg on Tue Nov 12 05:10:01 2024
    On Mon 11 Nov 2024 at 13:29:07 (+0800), hlyg wrote:
    Thank Curley! i have found out on my own

    i install again on another pc with 1 hard disk, it succeeds

    problem is with pc with 2 hard disks, 1 usb disk for installation
    media, 1 target usb disk

    this situation is so special that both debian and freebsd fail to
    install boot loader properly?

    I don't see what's so special about the first PC's disk inventory,
    but if you feel that's the cause of the problem, that's fine.
    I would just point out that you can find a log of the installation
    process at /var/log/installer/syslog, though I assume that you've
    overwritten the first installation's log by installing a second time.
    Reading the second installation's log might help if you encounter
    this problem again in future.

    Cheers,
    David.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Owlett@21:1/5 to David Wright on Tue Nov 12 21:10:02 2024
    On 11/12/24 1:52 PM, David Wright wrote:
    [snip]

    I don't know how one tells USB2 and USB3 sticks apart,...


    https://html.duckduckgo.com/html?q=%22identify%22%20%22USB2%22%20%22USB3%22


    https://unix.stackexchange.com/questions/112143/which-usb-slot-is-2-0-or-3-0-how-do-i-know


    https://forums.tomshardware.com/threads/how-to-identify-usb2-and-usb3-external-hard-drives.1911432/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Ritter@21:1/5 to hlyg on Wed Nov 13 00:30:01 2024
    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-

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to Dan Ritter on Wed Nov 13 06:40:01 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZzQ5uQAKCRAFyCz1etHa RlBEAJ9bmjUgqcoUvBPtZ0eZSfOGPXRQBgCeJL1lVqrAo/4JAoF4Gp2ru+1wvM8=
    =UIAk
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to hlyg on Wed Nov 13 20:30:01 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iFwEABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZzT80QAKCRAFyCz1etHa RjKCAJiZ/p5W7X43SeVJiGMljd3zbsmjAJwK1eXOPEH4uWxuOPFYco93qs0WyA==
    =gjhw
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)