Date: Wed, 28 Apr 2021 00:43:39 +0000 From: bugzilla-noreply@freebsd.org To: acpi@FreeBSD.org Subject: [Bug 202069] FreeBSD 11-CURRENT r285794 on Dell Inspiron 13 7352: ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20150619/psargs-391) Message-ID: <bug-202069-16045-dur7ghWoxY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-202069-16045@https.bugs.freebsd.org/bugzilla/> References: <bug-202069-16045@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202069 --- Comment #15 from Neel Chauhan <nc@FreeBSD.org> --- (In reply to Exhaling from comment #14) The truth is, you can still use FreeBSD even with this error message. When installing, switch to another console and run bsdinstall from there. When installed, set "debug.acpi.disabled=3D1" in /boot/loader.conf as said earlier. I used FreeBSD 11.2 on the said Dell Inspiron 7352 by suppressing the error message back in 2018-2019. I no longer have the Inspiron, and my two HP Spectre x360s (along with one = work ThinkPads with an unlocked BIOS, other one is locked) don't suffer from the same issue with FreeBSD. Only a few ACPI errors on boot on the two Spectres, and we obviously know how well ThinkPads work with FBSD (though I don't wan= t a ThinkPad for myself, and hence why I got HP hardware). About Dell specifically, I believe most newer (or older) Dell hardware shouldn't have these "errors", but I can't confirm since I don't have newer Dell hardware with me. I haven't used Dell hardware newer than Intel Broadw= ell, sorry. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202069-16045-dur7ghWoxY>