Hello,
I just installed ubuntu 26.04 and because it has very recent hardware and I had one difficult passage, I am making this post.
Ubuntu 26.04 Installation and MSI Vector 17 HX AI Setup — Conversation
Export
This file contains the conversation content and key command/output
exchanges from the Ubuntu installation/setup thread, including Windows
resizing, Intel VMD troubleshooting, Ubuntu dual boot, GRUB boot order,
Secure Boot/MOK enrollment, and NVIDIA RTX 5090 driver setup.
NOTE: This is a reconstructed text export from the conversation context
available to the assistant.
PART 1 — DISK PREPARATION / WINDOWS
USER: If you do this your files wonty be protectes “Turn Off”,
Decryption in progress
USER: Can we already just look at the partitions ?
USER: 300MB EFI System, Windows C 1875.61 GB 900MB Recovery 30.82GB
Recovery partition
USER: What I usually do is having a linux system particition and a data
partition. On the data partition I alos put my docker images, LLM files,
etc. So I can easily do a fresh reinstall (In never upgrade my system
because I want to get rid of unneccessary files). Can you advice a
partition for this ?
USER: Windows is only used occationally, so 400GB is ok
USER: Device encryption says off
USER: It asks for the amount of space to shrink in MB, or shoud be use
Mb ? What would be your computed value ?
USER: That number is 1920624
USER: I made a mistake:
total size before shrink in MB 1920624
Size of available shrink space in MB 1821326
USER: Total size after shrink in MB 409600
USER: It is done, I have a bootable ubuntu-26.04.1-desktop-amd64.iso usb
stick
USER: I am now in “Try Ubuntu” and my wifi is connected
PART 2 — LIVE UBUNTU HARDWARE CHECKS
Detected PCI hardware:
00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel
Graphics] (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation
GB203M / GN22 [GeForce RTX 5090 Max-Q / Mobile] (rev a1) 01:00.1 Audio
device: NVIDIA Corporation GB203 High Definition Audio Controller (rev
a1) 80:14.5 Non-VGA unclassified device: Intel Corporation Device 7f2f
(rev 10) 80:1f.3 Multimedia audio controller: Intel Corporation 800
Series ACE (Audio Context Engine) (rev 10) 84:00.0 Network controller:
Intel Corporation Wi-Fi 7(802.11be) AX1775/AX1790/BE20/BE401/BE1750 2x2
(rev 1a)
Kernel:
7.0.0-30-generic
NVIDIA PCI information showed: - RTX 5090 Mobile [10de:2c18] - MSI
subsystem [1462:149c] - Live-session driver: nouveau
Wi-Fi: - Intel Wi-Fi 7 [8086:272b] - driver: iwlwifi
Display topology: - Intel graphics drove the internal eDP panel in
MSHybrid mode. - NVIDIA exposed external DP/HDMI connectors and an
alternate eDP path. - Internal display: 3840x2400 at approximately 240
Hz.
Other checks: - Suspend/resume worked. - Battery reporting worked. -
Keyboard backlight worked. - Microphone worked. - Bluetooth scanning
worked. - Realtek RTL8125 2.5GbE detected.
PART 3 — INTEL VMD / SSD NOT VISIBLE
During Ubuntu manual partitioning, only the USB drive was visible.
lsblk showed approximately:
sda 57.8G disk iso9660 HEMA_64GB ├─sda1 6G iso9660 ├─sda2 5M vfat ├─sda3
300K └─sda4 51.7G ext4
The internal NVMe was missing.
PCI showed:
00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management
Device NVMe RAID Controller Intel Corporation [8086:ad0b] DeviceName:
Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI]
Device [1462:149c] Kernel modules: vmd
80:1d.0 System peripheral [0880]: Intel Corporation RST VMD Managed
Controller [8086:09ab]
The VMD module could be loaded with:
sudo modprobe vmd
but the VMD device did not bind. dmesg contained:
vmd 0000:00:0e.0: Unknown Bus Offset Setting (3)
The conclusion was that the Ubuntu 26.04 live kernel did not support the
VMD configuration used by this new Intel/MSI platform, preventing the
NVMe disk from appearing.
PART 4 — PREPARING WINDOWS TO DISABLE VMD
Windows Device Encryption / BitLocker was already OFF.
In an Administrator Command Prompt:
bcdedit /set {current} safeboot minimal
Output:
The operation completed successfully.
This configured Windows to enter Safe Mode on its next boot, preparing
Windows for the storage-controller topology change.
The BIOS was entered via Windows recovery / UEFI Firmware Settings.
The normal MSI BIOS did not expose VMD.
The hidden Advanced BIOS settings were opened, and the VMD menu was
found at:
Advanced BIOS Settings → System Agent (SA) Configuration → VMD Setup
Menu
The menu contained:
Enable vmd controller [Enabled] Enable vmd global mapping [Disabled] Map
RP BDF 128/29/0 Under VMD [Enabled] RAID0 [Enabled] RAID1 [Enabled]
RAID5 [Disabled] RAID10 [Disabled] ZPODD [Disabled]
Only this setting was changed:
Enable VMD controller Enabled → Disabled
The other VMD/RAID settings were left untouched.
Windows then successfully booted into Safe Mode with VMD disabled.
The temporary Safe Mode configuration was removed using:
bcdedit /deletevalue {current} safeboot
Windows was then able to boot normally with VMD disabled.
PART 5 — UBUNTU INSTALLATION
After disabling VMD, the Ubuntu installer could see the internal SSD.
Manual partitioning showed:
nvme0n1 ~2.05 TB nvme0n1p1 VFAT 314.57 MB nvme0n1p2 134.22 MB nvme0n1p3
NTFS 429.50 GB free space 1.58 TB nvme0n1p4 NTFS 943.72 MB nvme0n1p5
NTFS 33.09 GB
The existing partitions were preserved: - EFI System partition -
Microsoft Reserved partition - Windows partition - Windows recovery
partition - MSI/OEM recovery partition
The free space was used for Ubuntu/Linux according to the planned Linux
system/data separation.
Ubuntu 26.04 was installed successfully.
PART 6 — GRUB / WINDOWS BOOT ORDER
After installation, the machine initially booted directly into Windows.
Pressing F11 at the MSI logo opened the one-time boot menu. Ubuntu was
present there and booted successfully into GRUB/Ubuntu.
In Ubuntu:
efibootmgr
Output:
BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0000,0002 Boot0000*
Windows Boot Manager
HD(1,GPT,809326d4-57eb-44b8-b7a4-e01d3abffc70,0x800,0x96000)/.efi…
Boot0002* Ubuntu
HD(1,GPT,809326d4-57eb-44b8-b7a4-e01d3abffc70,0x800,0x96000)/64.efi
The EFI boot order was changed:
sudo efibootmgr -o 0002,0000
Although BootOrder became correct, MSI still booted Windows.
The MSI BIOS had an additional boot priority under:
UEFI Hard Disk Drive BBS Priorities
Ubuntu was moved ahead of Windows Boot Manager there.
After saving the BIOS configuration, normal startup correctly entered
GRUB.
Final boot flow:
Power on → GRUB → Ubuntu → Windows Boot Manager
PART 7 — NVIDIA RTX 5090 DRIVER
On the installed Ubuntu system:
ubuntu-drivers devices
Output:
== /sys/devices/pci0000:00/0000:00:06.0/0000:01:00.0 == modalias :
pci:v000010DEd00002C18sv00001462sd0000149Cbc03sc00i00 vendor : NVIDIA
Corporation model : GB203M / GN22 [GeForce RTX 5090 Max-Q / Mobile]
driver : nvidia-driver-595 - distro non-free driver :
nvidia-driver-580 - distro non-free driver : nvidia-driver-595-open -
distro non-free recommended driver : nvidia-driver-580-server - distro
non-free driver : nvidia-driver-595-server-open - distro non-free driver
: nvidia-driver-610-open - distro non-free driver : nvidia-driver-610 -
distro non-free driver : nvidia-driver-580-open - distro non-free driver
: nvidia-driver-580-server-open - distro non-free driver :
nvidia-driver-595-server - distro non-free driver :
xserver-xorg-video-nouveau - distro free builtin
Ubuntu explicitly recommended:
nvidia-driver-595-open
System update:
sudo apt update sudo apt full-upgrade
Four packages were deferred due to Ubuntu phased updates. They were left
deferred.
NVIDIA driver installation:
sudo apt install nvidia-driver-595-open
PART 8 — SECURE BOOT / MOK
During NVIDIA installation, Ubuntu detected that UEFI Secure Boot was
enabled.
Ubuntu requested creation of a temporary Machine Owner Key (MOK)
enrollment password.
On reboot, the blue MOK Manager appeared.
The enrollment sequence was:
Enroll MOK → Continue → Yes → enter the temporary password → Reboot
The password is only needed for enrollment; it is not required on every
boot.
This enrolled a trusted signing key so that the NVIDIA kernel module can
load while UEFI Secure Boot remains enabled.
PART 9 — NVIDIA VERIFICATION
nvidia-smi successfully detected the RTX 5090.
PCI check:
lspci | grep -i nvidia
Output:
01:00.0 VGA compatible controller: NVIDIA Corporation GB203M / GN22
[GeForce RTX 5090 Max-Q / Mobile] (rev a1) 01:00.1 Audio device: NVIDIA
Corporation GB203 High Definition Audio Controller (rev a1)
The first attempt at the detailed PCI command used a typo:
lspci -nnk -s 01.00.0
which produced:
lspci: -s: Invalid slot/function number
The correct PCI syntax uses a colon:
lspci -nnk -s 01:00.0
Output:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GB203M /
GN22 [GeForce RTX 5090 Max-Q / Mobile] [10de:2c18] (rev a1) Subsystem:
Micro-Star International Co., Ltd. [MSI] Device [1462:149c] Kernel
driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm,
nvidia
The authoritative result is:
Kernel driver in use: nvidia
This confirms that the RTX 5090 is running with the NVIDIA driver rather
than Nouveau.
FINAL STATE
Laptop: - MSI Vector 17 HX AI A2XWJG family - Intel Arrow Lake
platform - NVIDIA GeForce RTX 5090 Laptop GPU, 24 GB - 2 TB NVMe -
3840x2400 ~240 Hz internal display - Intel Wi-Fi 7
Storage: - Intel VMD disabled - Windows boots successfully using direct
NVMe access - Windows and MSI recovery partitions retained - Ubuntu
installed alongside Windows - Linux system/data separation used
Boot: - MSI UEFI recognizes both Windows and Ubuntu - Ubuntu is first in
UEFI Hard Disk Drive BBS Priorities - Normal boot enters GRUB - GRUB
provides Ubuntu and Windows choices
Ubuntu: - Ubuntu 26.04 - Secure Boot enabled - NVIDIA signing key
enrolled via MOK - nvidia-driver-595-open installed - RTX 5090 visible
via nvidia-smi - Kernel driver in use: nvidia
Next planned setup: - Configure persistent Linux data storage for
projects, LLM models, Docker data, and datasets - Docker - NVIDIA
Container Toolkit - Python/PyTorch AI development environment - CUDA
toolkit only if/when actually required