Date: Fri, 21 Jun 2019 00:46:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238729] head -r347549 on aorus gaming 7 F12e BIOS (Threadripper 1950X): boot attempts hang (but boots for fedora/Windows 10 Pro) Message-ID: <bug-238729-227-rys07lhWiY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238729-227@https.bugs.freebsd.org/bugzilla/> References: <bug-238729-227@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=3D238729 --- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Conrad Meyer from comment #3) I'm unsure just what comment 3 is indicating. The FreeBSD acpidump either uses /dev/mem or uses a dsdt input file (via -f). Quoting: Since only the DSDT is stored in the file, the -t flag may not be used with this option. /dev/mem is not available because of lack of booting. That left me with only dsdt as an option via that tool. (Running under Hyper-V does not have a matching acpi context in its /dev/mem and so is not useful. As stands I'm unable to native-boot using FreeBSD.) So all I got from FreeBSD's acpidump was dsdt decoding from the dsdt.dat that I manged to get from fedora. I've not yet figured out what all I can get from fedora's tools. acpidump is definitely not the same as FreeBSD's and there is a acpixtract as well. --=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-238729-227-rys07lhWiY>