Re: why this new stick fail to boot

2024-11-13 Thread 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 indicat

Re: why this new stick fail to boot

2024-11-13 Thread hlyg
Thank tomas! actually i am amateur on this subject but at my local market, usb devices aren't as colorful as Ritter describe, blue indicates usb3

Re: why this new stick fail to boot

2024-11-13 Thread Erwan David
Le 13/11/2024 à 00:07, Dan Ritter a écrit : 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 col

Re: why this new stick fail to boot

2024-11-12 Thread tomas
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 b

Re: why this new stick fail to boot

2024-11-12 Thread Dan Ritter
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 ma

Re: why this new stick fail to boot

2024-11-12 Thread hlyg
easiest way to identify usb3 is look at color, both connector and connectee shall be blue after i install freebsd and reboot, POST can't finish, i have to unplug power cord it's easy to explain why booting is bug-prone, it involves 2 parties, bios maker and OS developer at first i thoug

Re: why this new stick fail to boot

2024-11-12 Thread Richard Owlett
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.t

Re: why this new stick fail to boot

2024-11-12 Thread David Wright
On Tue 12 Nov 2024 at 22:52:09 (+0800), hlyg wrote: > > /var/log/installer/syslog might not be helpful, because everything > proceeds smoothly and normally during installation Agreed. The idea was to see the verbose context in which any Grub-install error and warning messages would be discovered.

Re: why this new stick fail to boot

2024-11-11 Thread hlyg
Thank Wright! /var/log/installer/syslog might not be helpful, because everything proceeds smoothly and normally during installation it is easy to reproduce my problem, pc with 2 hard disks, 2 free usb disks(one for installation disk, the other installation target), i don't use uefi actuall

Re: why this new stick fail to boot

2024-11-11 Thread David Wright
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 bo

Re: why this new stick fail to boot

2024-11-10 Thread hlyg
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?

Re: why this new stick fail to boot

2024-11-10 Thread Charles Curley
On Mon, 11 Nov 2024 06:57:23 +0800 hlyg 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