GPU2 used to be reported correctly as Intel I-GPU

GPU2 used to be reported correctly as Intel I-GPU (i-915 driver). Now, it does not. Is that normal? Or, is it an issue?

Note: I am running 2-display monitors with the internal I-GPU configured in the BIOS to be active and supporting Multi-Display mode.

1 Like

This does not look normal, llvmpipe usually means there is no GPU in use but everything is being rendered on the CPU in software.

2 Likes

I do know why it can to be like that.
Here are some Graphics info:

inxi -xxxG                                                                                                                                                                                                                            ──(Sat,May24)─┘
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel arch: Gen-6 ports: active: HDMI-A-1
    empty: DP-1, DP-2, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0122
    class-ID: 0380
  Device-2: Advanced Micro Devices [AMD/ATI] Vega 20 [Radeon VII]
    driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports:
    active: DP-5 empty: DP-3,DP-4,HDMI-A-3 bus-ID: 03:00.0 chip-ID: 1002:66af
    class-ID: 0300
  Device-3: SunplusIT Depstech webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-4.2:4
    chip-ID: 1bdf:5060 class-ID: 0102 serial: J20230111V0
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: amdgpu,modesetting
    alternate: fbdev,intel,vesa dri: radeonsi,crocus gpu: amdgpu,i915
    d-rect: 5360x2640 display-ID: 0
  Monitor-1: DP-5 pos: bottom-l model: Samsung C34J79x serial: HNTW400793
    res: mode: 3440x1440 hz: 100 scale: 100% (1) dpi: 110
    size: 797x333mm (31.38x13.11") diag: 864mm (34") modes: max: 3440x1440
    min: 720x400
  Monitor-2: HDMI-A-1 pos: top-right model: Dell U2412M serial: M2GCR161050L
    res: mode: 1920x1200 hz: 60 scale: 160% (1.6) to: 1200x1920 dpi: 94
    size: 518x324mm (20.39x12.76") diag: 611mm (24.1") modes: max: 1920x1200
    min: 720x400
  API: EGL v: 1.5 hw: drv: intel crocus drv: amd radeonsi platforms:
    device: 0 drv: radeonsi device: 1 drv: crocus device: 2 drv: swrast gbm:
    drv: kms_swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 3.3 vendor: amd mesa v: 25.2.0-devel
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon VII (radeonsi vega20 ACO
    DRM 3.61 6.14.8-x64v2-xanmod1) device-ID: 1002:66af display-ID: :0.0
  API: Vulkan v: 1.4.313 layers: 9 surfaces: N/A device: 0
    type: discrete-gpu hw: amd driver: mesa radv device-ID: 1002:66af device: 1
    type: cpu driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top,lact wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

That means that the Vulkan API is using the software render instead of the i915/crocus driver for the intel integrated i-GPU of the 2600K processor.

Is this a bug or feature?

I am not sure if it is a bug or not. This is why I posted.

My guess would be a bug as my Intel iGPU is reported as Intel® Graphics.
Or maybe a misconfiguration as I found the stuff the Arch wiki told me about Intel GPUs quite complicated, (too many variants and options) and still not sure I have done all correctly myself.

Slightly newer iGPU but also i915, the dGPU is Nvidia and Arch Kernel 6.14.7-arch2-1 though.

Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics vendor: CLEVO/KAPOK driver: i915
    v: kernel arch: Xe ports: active: eDP-1 empty: DP-1, DP-2, DP-3, HDMI-A-1,
    HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:a788 class-ID: 0300
  Device-2: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile]
    vendor: CLEVO/KAPOK driver: nvidia v: 570.153.02 arch: Lovelace pcie:
    speed: 2.5 GT/s lanes: 8 ports: active: none off: DP-4,HDMI-A-4
    empty: eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2860 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: intel,nvidia
    unloaded: modesetting alternate: fbdev,nouveau,nv,vesa dri: i965
    gpu: i915,nvidia,nvidia-nvswitch d-rect: 5120x4320 display-ID: 0
  Monitor-1: DP-4 pos: middle-l model: BenQ EX2710Q serial: S4P01819065 res:
    mode: 2560x1440 hz: 120 scale: 125% (1.25) to: 2048x1152 dpi: 109
    size: 597x336mm (23.5x13.23") diag: 685mm (27") modes: max: 2560x1440
    min: 640x480
  Monitor-2: HDMI-A-4 pos: primary,top-left model: VG27AQL1A
    serial: M2LMQS030248 res: mode: 2560x1440 hz: 60 scale: 125% (1.25)
    to: 2048x1152 dpi: 109 size: 596x336mm (23.46x13.23") diag: 685mm (27")
    modes: max: 2560x1440 min: 640x480
  Monitor-3: eDP-1 pos: bottom-r model: BOE Display 0x09f9 res:
    mode: 2560x1440 hz: 240 scale: 150% (1.5) to: 1707x960 dpi: 171
    size: 381x214mm (15x8.43") diag: 437mm (17.2") modes: 2560x1440
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau drv: nvidia
    platforms: device: 0 drv: nvidia device: 1 drv: nouveau device: 2 drv: iris
    device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.1.1-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
    device-ID: 8086:a788 display-ID: :0.0
  API: Vulkan v: 1.4.313 layers: 8 surfaces: N/A device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2860 device: 1
    type: integrated-gpu driver: mesa intel device-ID: 8086:a788
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr

It is a bug in mesa 25.2 dev. I switch the mesa to stable version 25.1, and we are back to normal and both i-GPU and the discrete video card are both detected normally.

1 Like