On Sat, Jan 03, 2026 at 11:20:04AM +0000, requiem. wrote:
> I managed to find and re-flash the stock F.16 BIOS version from HP
> (usually don't trust those 3rd party "driver installer" sites but it
> came through this time). The whitelist is back (yay, I guess), but with
> the wi-fi card removed I've managed to run some more tests. As I opened
> up the case I also installed a new CMOS battery, just to be safe.
>
> On Wed, 31 Dec 2025 10:28:07 +0000 Crystal
> Kolipe <[email protected]> wrote:
>
> > > [     1.023181] wmihp0 at acpiwmi0: HP WMI mappings
> > > [     1.023181] wmihp0: autoconfiguration error: failed to get data
> > > for event 0x80: AE_BAD_DATA
>
> This seems to be the case also with the stock BIOS. dmesg.boot on
> NetBSD still has the same error after flashing the stock F.16 BIOS.
>
> > > Just brwowsing through the dmesg I notice the CMOS clock is way off.
> > > Possibly a dead battery. Would that cause issues?
> >
> > Probably not the cause of this specific problem, but in general a
> > faulty CMOS battery can potentially cause all sorts of non-obvious
> > and difficult to identify issues, so if you can replace it that would
> > probably be a good idea.
>
> I did, well, didn't seem to make a difference. Clock keeps time at
> least.
>
> > For testing purposes only and to try to gather more information, can
> > you try booting the OpenBSD installer and disabling the acpi driver
> > in the bootloader?
> >
> Dropping to config with `boot -c` and then calling `disable acpi` gets
> me a working installer. Attaching a dmesg for this one too.
>

Sorry, I'm lost here.

To summarize:

1. you had a configuration that worked before.

2. you changed a bunch of devices and flashed some hacked/sketchy bios

3. things broke

I don't understand the dmesg pastes above, they don't look like openbsd.

I would recommend you start undoing the changes you made one at a time, and
tell us which change breaks things. And if it's the hacked/sketchy bios then
you might be SOL. It's too hard to diagnose "I changed a bunch of things
and now nothing works, please help".

PS at this point I don't even grok from the mail above if reverting the BIOS
change fixed anything. It seems like you're replying to multiple threads.

-ml

Reply via email to