On Sun, Mar 5, 2023 at 6:36 PM Zack Newman <z...@philomathiclife.com> wrote: > > > I am pretty sure it's a display/video driver issue and would like to > > just disable anything I could to that effect since this will be a > > headless system. Any suggestions on what I can do to troubleshoot > > this further? > > Have you tried booting bsd in single-user mode? Have you tried booting a > different OS (e.g., Arch Linux) just to check if _something_ works? > Since you want this to be headless, why not configure your system to > use the serial console? Your motherboard comes equipped with four > serial ports, so use one. This does not address the bug-if in fact > there is one-but it should at least allow you to work around it. > Thanks for the suggestions. The only way I can boot is through bsd.rd. Boot -s made no difference as it hangs before this would make a difference. boot -c and boot -d specifically brought me to their respective prompts, but unresponsive. I also tried changing the console to serial, and no luck.
As for other OS's, Ubuntu and Opensuse worked just fine right out of the box. However, OPNSense did not. I can't remember the exact error message there, but it did clue me into the fact that it saw com ports 0-3 even though I disabled 2/3. That got me thinking. I also got other tips outside the email list, and this got me going down a rabbit hole within the BIOS. After clearing nvram, and resetting to defaults, somehow this got it to boot up just fine. I'm part relieved that it works, and part concerned that I have no idea why, so I've spent the weekend slowly going through all change permutations in bios to find what's not working. It turns out that disabling com2 specifically (out of 0-3) , breaks... something... on BSD-like systems at least. I'm trying to narrow it down and I'll share in the bug I opened once I have useful info, even if it's naughty hardware. > I very recently ran into a similar issue with a new system I built. I > was able to boot bsd.rd as well as bsd in single-user mode; however > when booting bsd normally, it would hang after fsck(8) ran. This > happened with the most recent snapshot as well. I was able to > successfully boot Arch Linux without an issue though. Finally, I was > about to send a bug report following https://www.openbsd.org/ddb.html > where it recommends using the serial console to capture output. Once I > bought the necessary equipment to do so, I re-enabled the serial console > on my motherboard that I disabled before thinking I wouldn't use it. It > turned out that the problem was disabling the serial console. Once I > enabled it and installed OpenBSD with com0 as the default console, > everything worked fine. I am happy this happened though because I would > rather use the serial port anyway. > On Sun, Mar 5, 2023 at 6:36 PM Zack Newman <z...@philomathiclife.com> wrote: > > > I am pretty sure it's a display/video driver issue and would like to > > just disable anything I could to that effect since this will be a > > headless system. Any suggestions on what I can do to troubleshoot > > this further? > > Have you tried booting bsd in single-user mode? Have you tried booting a > different OS (e.g., Arch Linux) just to check if _something_ works? > Since you want this to be headless, why not configure your system to > use the serial console? Your motherboard comes equipped with four > serial ports, so use one. This does not address the bug-if in fact > there is one-but it should at least allow you to work around it. > > I very recently ran into a similar issue with a new system I built. I > was able to boot bsd.rd as well as bsd in single-user mode; however > when booting bsd normally, it would hang after fsck(8) ran. This > happened with the most recent snapshot as well. I was able to > successfully boot Arch Linux without an issue though. Finally, I was > about to send a bug report following https://www.openbsd.org/ddb.html > where it recommends using the serial console to capture output. Once I > bought the necessary equipment to do so, I re-enabled the serial console > on my motherboard that I disabled before thinking I wouldn't use it. It > turned out that the problem was disabling the serial console. Once I > enabled it and installed OpenBSD with com0 as the default console, > everything worked fine. I am happy this happened though because I would > rather use the serial port anyway. >
