> doesn't imply it can be fixed or anybody gives some time for fixing it.
Does does mean that it can even be fixed. Even on linux it might just
have the "fixes" to turn off the acpipci because that I don't know.
I have a few choices. To turn off acpicpi on the amd64, switch to i386
OpenBSD or install a different operating system that does not have the
same issue. I could even change my hardware and OpenBSD might work
better depending on if that hardware does not have any other issues.
Right now I am thinking to keep it it with the acpipci off because it
does boot that way. Then put a bug report in but there might be no one
wanting to fix it because the hardware is not popular enough and its too
old. At this point its a 2008 core 2 duo laptop that at this point just
be upgraded to something newer (I do have newer computers I just wanted
to get OpenBSD on this laptop and I did with the option off.
On 6/29/25 9:44a, Mihai Popescu wrote:
... if anyone wants to see what is wrong with the acpi.
I doubt this will fix your setup: see what is wrong with acpi and even
find what is wrong doesn't imply it can be fixed or anybody gives some
time for fixing it.
I have run probably in the same problem with my hardware, the OpenBSD
didn't boot anymore after install. Instructed by some super helper
here on the list i did a bisect and found the offending snapshot.
There was no fix. I guess I have to change my hardware to something
newer. I suggest you do the same. Gone are the days when "little
hardware" was useful. Welcome to the hardware diversity mess. Add the
software.
