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

[mlh%goathill.org@localhost (MLH)]

The following reply was made to PR port-amd64/56987; it has been noted by GNATS.

From: mlh%goathill.org@localhost (MLH)
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
 netbsd-bugs%netbsd.org@localhost, mlh%goathill.org@localhost
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
 -current)
Date: Wed, 9 Aug 2023 17:47:03 -0400 (EDT)

 MLH wrote:
 > The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
 > 
 > From: mlh%goathill.org@localhost (MLH)
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
 >  netbsd-bugs%netbsd.org@localhost, mlh%goathill.org@localhost
 > Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
 >  -current)
 > Date: Wed, 9 Aug 2023 16:12:48 -0400 (EDT)
 > 
 >  Taylor R Campbell wrote:
 >  > The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
 >  > 
 >  >  > Same filename, new file
 >  >  > http://synthetictransport.com/log/sdbstat
 >  >  
 >  >  Thanks, can you do the same with one of the working kernels so we can
 >  >  compare side by side?
 >  
 >  After days and days of trying to create a bootable (and easily
 >  recoverable back to my std setup), I need help.
 >  
 >  I lost access to my std setup for several days when I installed a
 >  debug kernel to test the above with to my root disk. I managed to
 >  finally recover it using an sdcard with an ietf NetBSD installer
 >  on it. Since that time, all but my std setup now stops with Read-only
 >  file system init failures. I can't get it to breakout to a shell
 >  to do anything.
 >  
 >  I have put the installer on several cf cards, both using dd and
 >  manually building and installing many times. Nothing works.
 >  
 >  If I could find out how to specify what the path name for ietf
 >  booting a specific kernel filename, I wouldn't need to try to use
 >  the sdcard path. As it is, I can only boot using 'boot -a' and
 >  selecting the root dk(x) needed where 'netbsd' is located. I can't
 >  specify the filename though and I don't want to risk changing
 >  'netbsd' to something else that won't boot (which is what happened
 >  the last time).
 
 Ha. ietf -> uefi. frustration mistake