ProArt X870E bios: Integrated Graphics menu entry missing (disable/enable/auto)

Motherboard: ProArt X870E-CREATOR WIFI

Mobo bios version 1001/1003

Bios menu entry to enable/disable integrated (cpu) graphics is missing. There is no way to manually enable or disable integrated graphics in the bios, or set it to auto.

A week ago on bios 1001, I’ve installed Windows, w/o using a discrete graphics card in the freshly built system, using the integrated graphics (cpu) instead with a 1920x1080 monitor. All good. Installed apps, made an image.

Mounted a RTX2080 Super (awaiting RTX5080), hooked up to my ultra widescreen 5120x1440 monitor. All good. Dual screens.

RTX2080: 5120x1440 main monitor

CPU iGPU: 1920x0180 secondary monitor

Use case: While still on the RTX2080 for now, I’d like to use the CPU’s iGPU for my 2nd monitor, since the outdated RTX2080 is the system’s bottleneck. So I do not want to load that up more than I have to.

Now, at one point, upon loading bios defaults later and performing a “Save Changes & Reset”: There was a listing of all the variables which were going to be reset, including “Integrated Graphics”.

Updated the bios from 1001 to 1003, was looking to turn the iGPU back on. Could not find it anywhere in the sub menus.

Also, when one performs a (F9) search for “Integrated Graphics” in the bios, nothing.
I can’t enable the CPU’s iGPU. Is this a thing on current AM5 platforms? Working as intended, or a design fault?

(My last build was a Z97-Deluxe with i7-4790K, back in 2014. That one allowed iGPU enabling/disabling from the bios.)

Other components:

CPU: AMD 9800X3D

RAM: Kingston KF560C32RSK2-96

1 Like

Check the manual, should be in Advanced → NB Configurations

The whole NB Configuration sub menu is apparently missing. (Can’t find it elsewhere either.)

Try the search mode (I think it’s under F8)? Otherwise go back to the previous bios and wait until it’s resolved?

Is the default not AUTO, which I believe is enabled, at least if a screen is connected to the iGPU? Talking from my experience with the X670E ProArt…

I’ve already tried search (F8), as mentioned in the initial post. Nothing.

The previous 1001 bios doesn’t have the menu entry either from what I remember, since I looked thoroughly for it in that version too. The default should be AUTO, as that’s what it reverted to, when I did the initial load bios defaults under 1001. So in the background, something is happening.

In order to enable the iGPU, I have to take the discrete graphics card out. However, when I put it back in, the iGPU is disabled again.

My best guess is the bios triggers for a 9800X3D are currently not properly done.

Tried clearing CMOS, either with button on the back or by removing battery?
When you get to the Windows, is the iGPU listed in the Device Manager and just doesn’t have video output?

While still on the RTX2080 for now, I’d like to use the CPU’s iGPU for my 2nd monitor, since the outdated RTX2080 is the system’s bottleneck

IMO, handling three monitors (dual QHD and one FullHD) isn’t a problem for such card. Rendering and outputting system GUI isn’t gonna hit your FPS, if that’s what you care about

So, clearing CMOS did provide me with a NB Configuration menu entry, allowing me to change iGPU settings. I apparently missed that earlier. Thanks for that!

Considering the iGPU use case, that’s just a personal thing. It’s available, I’d like to use it, for now.

Now I did discover that enabling CSM (Boot\CSM (Compatibility Support Module)) apparently disables the iGPU and the NB Configuration menu.

Re-Size BAR info states CSM interaction (disabling).
CSM info however does not state Re-Size bar and/or iGPU interaction (disabling).

I use CSM to be able to boot a (SATA) SSD with a Linux distro (using the bios boot manager), which does not have GRUB nested into the Windows Boot Loader of the primary boot (NVMe) SSD.
With CSM disabled, that Linux drive and all other drives except the primary Windows one, are not listed in the boot manager.

I also noted that the bios sometimes does wonky stuff when changing, saving and loading settings. Be it from a settings file or just by changing variables. It apparently doesn’t like it when changing many settings at once for instance (possibly due to dependencies, who knows).

(

I could go in various tangents here about other bios functionality, not related to the main topic, however related to the above:

  1. Why can’t I disable individual M.2 NVMe slots/drives?
    Sometimes when installing a second or third OS (on other drives), one could want the OS to not see specific drives at all, since an OS install might do things to drives you don’t want it to. It happens.
    It’s perfectly possible with SATA ports to individually disable them (ironically when it’s actually easy to unplug those drives in most cases). Physically removing NVMe’s to get the same result is a PITA. It can easily be argued M.2 slots need that functionality more than SATA ports. The option for M.2 drives is not there. Why?
    Use case: Prevent certain Linux distros grub managers to mess with the Windows boot manager, despite telling them during install not to do so. (Checking out Ubuntu/Linux Mint as an example.) (Glad I had an image of the Windows boot manager to restore its state.)

  2. Why isn’t there a bios option to show the bios boot manager on every boot? Rather than having to press F8 to bring it up.

Quite the tangent, but yeah, /endofrant

)

Right, that also stated in the manual. I just didn’t even think someone would willingly run CSM on a new computer in 2025.

I use CSM to be able to boot a (SATA) SSD with a Linux distro (using the bios boot manager), which does not have GRUB nested into the Windows Boot Loader of the primary boot (NVMe) SSD.
With CSM disabled, that Linux drive and all other drives except the primary Windows one, are not listed in the boot manager.

You probably just moved all you drives from the 2014 build as is, right? Are they still MBR, without GPT tables and EFI System partitions? If so, then I don’t know, dump the data somewhere and just reinstall from scratch.

Prevent certain Linux distros grub managers to mess with the Windows boot manager

I don’t remember the time when this was a thing. One drive - one OS and you’ll be fine.

  1. Why isn’t there a bios option to show the bios boot manager on every boot? Rather than having to press F8 to bring it up.

Because there are probably very few people on the planet who would want that. Why?

You probably just moved all you drives from the 2014 build as is, right? Are they still MBR, without GPT tables and EFI System partitions? If so, then I don’t know, dump the data somewhere and just reinstall from scratch.

No, they’re freshly defined, formatted and installed. Deffo not MBR from the dark ages, haha :).

Windows drive:

1

Linux drive:

2

I don’t remember the time when this was a thing. One drive - one OS and you’ll be fine.

Again, use case, personal. Windows as primary OS. Linux desktop as secondary OS to mess around with. No need to debate the use case, or the choice to prevent OS specific boot managers to mangle each other. That’s where the bios boot manager would be/is nice.

Something is off here. From what I see here - there should be no reason to resort to CSM. Maybe Asus’s UEFI behaves differently, but on all motherboards I had since 2015 (asrock, gigabyte) - if OS is installed with efi support - the bios boot manager is automatically able to detect those (without CSM). Maybe you have FastBoot enabled?
AFAIK, this is how it should work. UEFI during early boot scans all storage devices for a presence of GPT partition table. For the drives with it (even USB removables) - it then reads the GPT table for the presence of FAT32 formatted EFI System Partition (partition ID in the spec). And last - if there is a file /EFI/Boot/bootx64.efi on that partition - then UEFI boot manager automatically adds a record to the boot menu.

I do remember though, one MSI board back then (~2016), where this auto detection didn’t fully work. Meaning it was only able to detect a windows bootloader, but for linux - I had to manually add a record using efibootmgr, and it was annoying, because every time I’ve clear CMOS - those records were wiped and I had to boot from live ISO to bring it back (maybe happened once a year).

Disabling Fast Boot did not change the behavior.

However, something was definitely off. That comment got me thinking in another direction.

After having previously messed with grub, repairing/redefining it as well (after it had altered the Windows boot loader, which I fixed using an image restore), I figured the grub repair could be the culprit.
I could boot that Linux install with either CSM enabled, or triggering it from a Systemrescue Linux USB stick (basically a live ISO).

Decided to perform a Linux reinstall.

So I booted Systemrescue Linux from an USB stick, wiped the Linux disk using GParted. I also used GParted to temporarily remove the boot flag from the Windows boot partition, so grub would not detect the Windows boot loader and mess with it during the Linux install.

Installed Linux. It indeed did not see the Windows boot loader this time. Perfect. Used GParted to re-enable the boot flag on the Windows boot partition.

Now the Linux disk has a proper boot entry. Grub and the Windows boot loader have not messed with each other. No CSM required to (manually) boot into it anymore.

iGPU working.
Booting either OS working, without them knowing of each other’s existence.
CSM disabled.

All done. Cheers for thinking along and the suggestions!

1 Like