Quote:
Originally Posted by Blinker
Hi, me again
|
Welcome back!
Quote:
After the kernel messages have scrolled past nothing happens.
|
Just like four years ago, you have a boot problem. But it's a different problem this time.
Quote:
The last line reads
Code:
root on rd0a swap on rd0b dump on rd0b
and then just sits there.
|
I don't think a
verbose boot will help, because this is the last kernel message expected during boot. After issuing that message, the kernel should pass control to init(8). You could always try a verbose boot, because like chicken soup, it wouldn't hurt. But I doubt it will help.
If you were to report this problem to the misc@ or bugs@ mailing list, someone would ask if you could capture the preceding dmesg in its entirety, which is only going to be possible if you have a serial port, a null-modem cable, and a second computer. Your working, 5.7 dmesg would probably be even more useful to developers to understand what's unique about your hardware.
If I recall correctly, the ddb(4) debugger is not included in these RAMDISK kernels, due to space. You might be able to boot a 5.8 (or -current) GENERIC kernel, and see if it fails the same way. If so, a backtrace from ddb(4) may provide insights to developers. Though if you do this, I'd recommend booting the kernel in single-user mode (boot
-s), to avoid causing any data issues with userland daemons that might otherwise be started.
The crash(8) man page provides guidance on using both ddb(4) and gdb(1), and may be helpful.