Alder Lake (12500) PCI devices not being recognized.

[Chriscla]

Hi, first thank you for all your hard work on Proxmox.

I'm trying to setup a Proxmox 7.2 system with a i5-12500 running on an AsRock B660 motherboard. It doesn't appear that PCI devices (including the internal GPU) are being recognized correctly. Doing lspci, I would expect the devices to say "Alder Lake" in the Intel Devices. I did a live-ISO boot of an Ubuntu 22.04 system and lspci correctly showed the devices labeled as Alder Lake. The reason I'm looking into this is that I'm trying to get stable transcoding working.

root@starbase:~# lspci
00:00.0 Host bridge: Intel Corporation Device 4650 (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 4690 (rev 0c)
00:06.0 PCI bridge: Intel Corporation Device 464d (rev 05)
00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 7acc (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7abd (rev 11)
00:1c.6 PCI bridge: Intel Corporation Device 7abe (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a86 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
01:00.0 Non-Volatile memory controller: SK hynix Device 174a
02:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)

I have updated the kernel to the newest Proxmox 5.15 kernel. I also tried one of Fabien's 5.18 kernels.

root@starbase:~# uname -a
Linux starbase 5.15.39-3-pve #2 SMP PVE 5.15.39-3 (Wed, 27 Jul 2022 13:45:39 +0200) x86_64 GNU/Linux

I have removed all "fancy" kernel options:

root@starbase:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.39-3-pve root=UUID=88ab3211-4b4b-4888-8633-5647a8a26677 ro quiet

Any ideas why the devices are not being properly recognized and named as their full Intel Alder Lake variants? Or am I chasing a Red Herring?

Thank you!

 

[shrdlicka]

I'm not sure what you mean with properly recognized

$ lscpi -v

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7) (prog-if 00 [VGA controller])
    Subsystem: ASRock Incorporation Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X]
    Flags: bus master, fast devsel, latency 0, IRQ 145, IOMMU group 1
    Memory at 4080000000 (64-bit, prefetchable) [size=2G]
    Memory at 4040000000 (64-bit, prefetchable) [size=2M]
    I/O ports at 3000 [size=256]
    Memory at a2100000 (32-bit, non-prefetchable) [size=256K]
    Expansion ROM at 000c0000 [disabled] [size=128K]
    Capabilities: <access denied>
    Kernel driver in use: amdgpu     <==================
    Kernel modules: amdgpu            <==================

I hope the -v option is telling you some kernel module is loaded for each of the devices.

Take a look at man lspci

...
FILES
       /usr/share/misc/pci.ids
              A list of all known PCI ID's (vendors, devices, classes and sub‐
              classes). Maintained at https://pci-ids.ucw.cz/, use the update-
              pciids utility to download the most recent version.

       /usr/share/misc/pci.ids.gz
              If  lspci is compiled with support for compression, this file is
              tried before pci.ids.

       ~/.pciids-cache
              All ID's found in the DNS query mode are cached in this file.

It has a translation table for PCI IDs to device names. You can update it with update-pciids. I think this is your only problem .

 

[Chriscla]

Yep, updating the id's made the device names show correctly. Another reminder to RTFM. Thank you! I was hoping that this was why I was having stability issues but this isn't it. I was so confused why it was showing the driver being loaded but the name wasn't correct.