Question Interesting BIOS Issue on Asus P6X58D-E motherboard ?

MajorPager

Prominent
Aug 8, 2023
307
40
710
Hello all, it's currently late into the night and my tired self is trying to correct a mess-up that occurred when I reinstalled Windows 10 around a week or 2 ago and have ran into a few peculiar things.

I didn't know that there was two options for AHCI and IDE so BIOS was set to AHCI but my 1TB WD HDD was set to IDE. Now since IDE is as old as dirt now and AHCI is great, I wanted to change it along with the VT parameters, which I did.

Then of course the system wouldn't boot, not even from my plan B USB installer, till I disabled VT-D only, then it worked. Device manager shows SCSI now, and for some reason an unknown device listed as "Marvell 91XX Config" which is the model of the sata controller on this board, but it also says its working properly.

Despite knowing I should've reinstalled in the first place I shall just wait till the system corrupts then do so.

Now what I really want to know is:
1. Why is there "Marvell 91XX Config" in DM, what is it for, and why is it shown as "Unknown Device"?
2. Why doesn't VT-D work at all?

I honestly don't know much rn since I woke up like 3 hrs ago after a long day and am still trying to wrap my head around this.

EDIT: Also lost the ability to set hard drive priority in BIOS after the switch, why? Its beyond me.
 
Last edited:
Hello!
You've experienced issues with a heavy InDesign file due to many images and pages. It's now not opening, likely because of its size. Try saving the file as an IDML (InDesign Markup Language) file to choice advantages login reduce its size and make it more manageable. Also, consider linking images instead of embedding them to keep the file size down. Good luck!
 
Last edited:
  • Like
Reactions: MajorPager
Hello!
You've experienced issues with a heavy InDesign file due to many images and pages. It's now not opening, likely because of its size. Try saving the file as an IDML (InDesign Markup Language) file to reduce its size and make it more manageable. Also, consider linking images instead of embedding them to keep the file size down. Good luck!
How would I go about that if there's no OS installed? Because I tried reinstalling Windows from a USB with the HDD disabled and it wouldn't boot from it with VT-D enabled.

Also could I ask as to why this system specifically after power loss and restore, turns on / shows windows boot screen / then doesn't actually go into the OS? Then after a quick restart boots perfectly fine? This is a fresher install as well.
 
1. Why is there "Marvell 91XX Config" in DM, what is it for, and why is it shown as "Unknown Device"?
2. Why doesn't VT-D work at all?
Its because its missing the ASUS drivers. AHCI controller is using a generic driver for the motherboard. So it segments it this way since AHCI turns on the hardware hooks for the software raid (if you were going to install it from the extra boot menu that was enabled) . In bios, the AHCI section is turned on and this sub menu is where you would set the boot device and timeout.

VT-d will only work with AHCI if the drivers are correct. Since its not the driver it is looking for it will halt the system at OS boot
 
Hello!
You've experienced issues with a heavy InDesign file due to many images and pages. It's now not opening, likely because of its size. Try saving the file as an IDML (InDesign Markup Language) file to reduce its size and make it more manageable. Also, consider linking images instead of embedding them to keep the file size down. Good luck!
???

What does Adobe InDesign have to do with this?

Let's fix the actual problem.
 
What does Adobe InDesign have to do with this?
Wow, I was and still am apparently very tired, I thought that was just some random file within windows and not an actual app, very bizarre I'm just realizing that now.

UPDATE: Also installed the ASUS drivers for the storage controllers which worked flawlessly, and tried to find drivers for the system devices but didn't get far with those.
 
I see now, although how would I narrow it down to the problematic driver? And also how does it stop the USB installer from booting when there's nothing present?
Because you didn't you didn't install the native 16 bit drive controllers when you installed the drive. Which was a floppy disk in older systems to install the raid and native achi controller. That is why VT-d doesn't work. It requires this driver present and the drive formatted with its little space reserved for it in the 1st 1M of the drive. VT-d passes 13h interrupt to activate the ACHI/raid controller instead of to the hardware receiving the interrupt. Then the AHCI driver initialises the drives instead.