Re: port-amd64/56987 (Certain usb devices can no longer be mounted on -current)

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

> Date: Thu, 5 Oct 2023 10:44:37 -0400 (EDT)
> From: mlh%goathill.org@localhost (MLH)
> 
> > >  > Same filename, new file
> > >  > http://synthetictransport.com/log/sdbstat

This URL now returns 404.  Can you provide the log at a stable
location, or just put it back up there for now so we can save a copy
of it?

> BTW, on Android these devices show as "FSL Semi USB drive" but I
> haven't seen what this is. Is there a reference to that before the
> USB stack was rewritten (which lost the capability to read these
> devices)?

That's probably just a name that the USB device reports for itself,
plus `USB drive' because it's a USB mass storage class of device
(`hard drive').

(We didn't rewrite the USB stack -- it's almost all the same code as
before.  We just made a lot of small changes to fix a lot of little
bugs; perhaps a bug crept into one of those small changes.  Many of
these changes in particular were deliberately broken down into
especially small, functionally separate commits -- with changes as
independent as possible -- so that it would be easy for bisection to
narrow down exactly which commit broke anything.)

> Also, has anyone come up with a way to determine boot file path
> names for uefi booting yet?

You can either use:

- esp:/EFI/NetBSD/boot.cfg, on the EFI system partition (esp); or
- /boot.cfg, on the root partition, which is installed by default on
  x86.

See boot.cfg(8) for details of the format, and x86/boot(8) for details
of the process.  The default x86 boot.cfg is this:

menu=Boot normally:rndseed /var/db/entropy-file;boot
menu=Boot single user:rndseed /var/db/entropy-file;boot -s
menu=Drop to boot prompt:prompt
default=1
timeout=5
clear=1

You can just add another menu entry like this to boot a kernel called
`netbsd.test', placed after the other `menu=...' lines in boot.cfg so
it's not taken as the default:

menu=Boot other kernel:rndseed /var/db/entropy-file;boot netbsd.test

Alternatively, instead of changing boot.cfg, you can move your working
kernel from /netbsd to /onetbsd.  It will continue to boot when you do
this: the bootloader will try /netbsd first, then /onetbsd.  Then you
can try another kernel at /netbsd, and if it doesn't work, drop to the
bootloader prompt to do `boot /onetbsd' instead.