[Bug 272507] SATA controller fails to initialize on some AMD X670E(xtreme) based motherboards
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 272507] SATA drives show in BIOS but won't show in /dev"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 27 Jul 2023 13:32:00 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507 --- Comment #11 from Justin Tocci <justin@tocci.org> --- Thank you for your suggestion. I just did a reboot with: verbose fast boot disabled SATA Port 1 Hot Plug enabled SATA Port 2,3,4 Hot Plug disabled (SATA ports 1 and 2 have disk drives attached) display priority external -> internal full screen logo disabled result was no joy. My research from Alexander Motin's post suggesting Plug and Play OS be turned off led me to believe this is sometimes listed as PnP/PCI Configuration. I found no reference to PnP or Plug and Play in the bios. Just now I did a thorough search of every screen and option and found no reference. I then searched the ASRock manual, website and then the internet for alternate names and came up with nothing. I welcome all suggestions. But I do have a PCI Configuration screen. That screen only has three options. Disabling "Above 4G Decoding" removes the menu items for "Re-Size Bar support" and "Above 4GB MMIO Limit". I had tried this already as reported on this page but adding it to the above changes gave me the same top thirty lines of dmesg and no additional hard drives. ls /dev/ acpi ctty hpet0 log mixer6 nvme0ns1 sequencer0 ttyv3 ugen0.1 uhid0 wmistat0 apm devctl input mdctl mlx5ctl nvme1 sndstat ttyv4 ugen1.1 uhid1 xpt0 apmctl devctl2 io mem music0 nvme1ns1 stderr ttyv5 ugen1.2 uhid2 zero audit devstat iov midistat netdump nvme2 stdin ttyv6 ugen1.3 uinput zfs auditpipe diskid kbd0 mixer0 netmap nvme2ns1 stdout ttyv7 ugen1.4 ukbd0 bpf efi kbd1 mixer1 null pci sysmouse ttyv8 ugen1.5 ukbd1 bpf0 fd kbd2 mixer2 nvd0 pfil tcp_log ttyv9 ugen2.1 ums0 console fido kbdmux0 mixer3 nvd1 pts ttyv0 ttyva ugen3.1 urandom consolectl full klog mixer4 nvd2 random ttyv1 ttyvb ugen4.1 usb crypto geom.ctl kmem mixer5 nvme0 reroot ttyv2 ufssuspend ugen4.2 usbctl dmesg, both trys: root(33)au:~ # dmesg tcp_log: tcp_log device crypto: <crypto core> kbd0 at kbdmux0 io: <I/O> mem: <memory> null: <full device, null device, zero device> [ath_hal] loaded efirtc0: <EFI Realtime Clock> efirtc0: registered as a time-of-day clock, resolution 1.000000s smbios0: <System Management BIOS> at iomem 0x794d8000-0x794d801e smbios0: Version: 3.4, BCD Revision: 3.4 crypto: assign cryptosoft0 driver id 0, flags 0x6000000 aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS,SHA1,SHA256> crypto: assign aesni0 driver id 1, flags 0xe000000 acpi0: <ALASKA A M I > Firmware Error (ACPI): Failure creating named object [\134_SB.PCI0.GPP0._PRW], AE_ALREADY_EXISTS (20201113/dswload2-480) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20201113/psobject-372) Firmware Error (ACPI): Failure creating named object [\134_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20201113/dswload2-480) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20201113/psobject-372) Firmware Error (ACPI): Failure creating named object [\134_GPE._L08], AE_ALREADY_EXISTS (20201113/dswload2-480) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20201113/psobject-372) ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014) ACPI: 15 ACPI AML tables successfully acquired and loaded PCIe: Memory Mapped configuration base @ 0xf0000000 -- You are receiving this mail because: You are the assignee for the bug.