Re: lspci output variations for Display Controller

2026-01-30 Thread Michael Cronenworth 

On 1/30/26 11:58 AM, Lukas Ruzicka wrote:


Class: Display controller
Vendor: Advanced Micro Devices, Inc. [AMD/ATI]
Device: Strix Halo [Radeon Graphics / Radeon 8050S Graphics / Radeon 
8060S Graphics]

SVendor: Framework Computer Inc.



Maybe this is too off-topic but I'll only reply once. I have relatively 
new display hardware and both still report "VGA compat. controller". A 
Radeon 9070 XT and a Lunar Lake (Intel) Arc 140v. I wouldn't think 
either would still show up as "VGA" but they do.


--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: lspci output variations for Display Controller

2026-01-30 Thread Lukas Ruzicka 
```
Slot: c2:00.0
Class: Display controller
Vendor: Advanced Micro Devices, Inc. [AMD/ATI]
Device: Strix Halo [Radeon Graphics / Radeon 8050S Graphics / Radeon 8060S
Graphics]
SVendor: Framework Computer Inc.
SDevice: Device 000a
Rev: c4
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 18
```

On Thu, Jan 29, 2026 at 10:05 AM Petr Sklenar  wrote:

> Hello all,
> I’m updating QA [test case] and noticed that on newer systems,
> graphics hardware is often reported as 'Display controller'
> rather than 'VGA' in lspci.
>
> To better understand how common this is across different setups,
> I'd appreciate any samples people are willing to share.
> I plan to update the test case based on the outputs provided.
>
> If you have a moment, could you run this and send the output
> off-list to me so we don't clutter the mail thread?
>
> $ lspci -kvmm
>
> No rush, just send whenever you’re already in a terminal.
> I am mainly looking to see how varied the
> Class: and VGA: fields
>
> [test case]
> https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver
>
> Thanks,
> Petr
>
> --
> ___
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam, report it:
> https://forge.fedoraproject.org/infra/tickets/issues/new
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

[email protected]
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: lspci output variations for Display Controller

2026-01-29 Thread Gerd Hoffmann 
On Thu, Jan 29, 2026 at 10:04:11AM +0100, Petr Sklenar wrote:
> Hello all,
> I’m updating QA [test case] and noticed that on newer systems,
> graphics hardware is often reported as 'Display controller'
> rather than 'VGA' in lspci.

That essentially means the GPU is not VGA compatible.  I expect that
becoming increasingly common with hardware vendors dropping BIOS
compatibility and moving to UEFI-only setups.  They can simply ship a
UEFI firmware driver for the GPU hardware then and VGA compatibility is
not needed any more to have a working display during boot.

> To better understand how common this is across different setups,
> I'd appreciate any samples people are willing to share.
> I plan to update the test case based on the outputs provided.

If you wanna try this in a virtual machine:  qemu has two virtio-cpu
variants, one with vga compatibility (-device virtio-vga), one without
(-device virtio-gpu-pci).  The former is reported as class 'VGA'
(0x0300), the latter as class 'Display Controller / Other' (0x0380).

With OVMF you'll get a working display on both devices, seabios works
only with virtio-vga.

Libvirt does not support explicitly picking the one or the other, if you
ask for a virtio display device you'll get virtio-vga on x86 and
virtio-gpu-pci otherwise (arm, riscv, ...).

HTH,
  Gerd

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new