On 7/25/19 2:24 PM, Mark Kettenis wrote: >> Date: Thu, 25 Jul 2019 21:01:43 +0100 >> From: Stuart Henderson <[email protected]> >> >> Posting additional information back to the mailing list, I'm not >> sure what would be causing it to stop at this point .. > > That's where interrupts get turned on. If there is an interrupt storm > of some sorts that might stop the kernel from making progress. One > possible way of figuring out what is causing the problem is to boot > with the -c option and disable device drivers one by one.
Sounds kinda similar to the problem I'm having (7/24. "acpimadt(4) problem"). Quick starting point might be to try disabling acpimadt, and see if that helps. Nick. > >> On 2019/07/25 18:10, Per Gunnarsson wrote: >> > It's the same with the snapshot I got from the norwegian mirror. Console >> > messages ending with: >> > >> > root on rd0a swap on rd0b dump on rd0b >> > >> > (many devices are shown as not configured) >> > >> > after "root on rd0a ..." I don't get any options, the console logs my >> > usb mouse attaching and detatching, but no installation program starts. >> >> >> >> >> >> On 2019/07/25 10:55, Per Gunnarsson wrote: >> > Hello! >> > >> > I have been trying to install OpenBSD amd64 on a Lenovo 510-15ABR, and >> > the CD boots, I get a dmesg but the installer never starts. >> > When I think about it, I probably should have read the "supported >> > hardware" list first before complaining, but I will paste a dmesg and a >> > dmidecode from FreeBSD anyway in case you are interested.
