intel card recognised but not used, llvmpipe used instead

Kernels & Hardware, configuring network, installing services

intel card recognised but not used, llvmpipe used instead

Postby Bernoot » 2020-10-31 12:22

Hello,

I have a Dell Latitude 5310 / with an Intel Core i5-10210U CPU @ 1.60GHz
I am under Debian GNU/Linux 10 (buster) / GNOME 3.30.2
There is no additional graphic card, so the intel chipset should be used, but it seems it is not, although propoerly detected.

I paste the results of some diagnostic commands (sorry for several output statements being in french, but should be easy to understand).
  • I can understand that errors are reported in /var/log/Xorg.0.log @ 3.455, but I am too noob to interpret them.
  • I also find puzzling that uname says the kernel is 5.8 while /var/log/Xorg.0.log says "Build Operating System: Linux 4.19.0-10-amd64 x86_64 Debian". Could this be related to the graphic card issue?

Thanks for any suggestion!

Bernoot

Code: Select all
$ uname -a
Linux ABI20 5.8.0-0.bpo.2-amd64 #1 SMP Debian 5.8.10-1~bpo10+1 (2020-09-26) x86_64 GNU/Linux

$ sudo apt list libdrm-intel* libgbm* firmware-linux-nonfree xserver-xorg-video-intel
firmware-linux-nonfree/stable,now 20190114-2 all  [installé]
libdrm-intel1/stable,now 2.4.97-1 amd64  [installé]
libgbm-dev/stable 18.3.6-2+deb10u1 amd64
libgbm1/stable,now 18.3.6-2+deb10u1 amd64  [installé]
xserver-xorg-video-intel/stable,now 2:2.99.917+git20180925-2 amd64  [installé]

$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c)
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9b41] (rev 02)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 0c)
00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911]
00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:02f9]
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:02ed]
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:02ef]
00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:02e8]
00:15.1 Serial bus controller [0c80]: Intel Corporation Device [8086:02e9]
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:02e0]
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:02b2] (rev f0)
00:1d.4 PCI bridge [0604]: Intel Corporation Device [8086:02b4] (rev f0)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:0284]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:02c8]
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3]
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:02a4]
00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:0d4f]
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
02:00.0 Non-Volatile memory controller [0108]: SK hynix Device [1c5c:1339]

$ lspci -vv
[...]
00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device 099f
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
   Latency: 0, Cache Line Size: 64 bytes
   Interrupt: pin A routed to IRQ 136
   Region 0: Memory at 90000000 (64-bit, non-prefetchable) [size=16M]
   Region 2: Memory at 80000000 (64-bit, prefetchable) [size=256M]
   Region 4: I/O ports at 3000 [size=64]
   [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
   Capabilities: <access denied>
   Kernel driver in use: i915
   Kernel modules: i915
[...]

$ sudo lshw -class display
  *-display                 
       description: VGA compatible controller
       produit: Intel Corporation
       fabriquant: Intel Corporation
       identifiant matériel: 2
       information bus: pci@0000:00:02.0
       version: 02
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       ressources: irq:136 mémoire:90000000-90ffffff mémoire:80000000-8fffffff portE/S:3000(taille=64) mémoire:c0000-dffff

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: VMware, Inc. (0xffffffff)
    Device: llvmpipe (LLVM 7.0, 256 bits) (0xffffffff)
    Version: 18.3.6
    Accelerated: no
    Video memory: 31842MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 7.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.3.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.1 Mesa 18.3.6
OpenGL shading language version string: 1.40
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.3.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

$ cat /var/log/Xorg.0.log
[     3.444] (--) Log file renamed from "/var/log/Xorg.pid-743.log" to "/var/log/Xorg.0.log"
[     3.445]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[     3.445] Build Operating System: Linux 4.19.0-10-amd64 x86_64 Debian
[     3.445] Current Operating System: Linux ABI20 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64
[     3.445] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-amd64 root=UUID=14670662-fa63-4e49-a473-79a5d2cacb87 ro quiet nomodeset
[     3.445] Build Date: 27 August 2020  08:51:48AM
[     3.445] xorg-server 2:1.20.4-1+deb10u1 (https://www.debian.org/support)
[     3.445] Current version of pixman: 0.36.0
[     3.445]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[     3.445] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     3.445] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 24 02:13:10 2020
[     3.446] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     3.447] (==) No Layout section.  Using the first Screen section.
[     3.447] (==) No screen section available. Using defaults.
[     3.447] (**) |-->Screen "Default Screen Section" (0)
[     3.447] (**) |   |-->Monitor "<default monitor>"
[     3.447] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[     3.447] (==) Automatically adding devices
[     3.447] (==) Automatically enabling devices
[     3.447] (==) Automatically adding GPU devices
[     3.447] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     3.448] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     3.448]    Entry deleted from font path.
[     3.449] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
[     3.449] (==) ModulePath set to "/usr/lib/xorg/modules"
[     3.449] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[     3.449] (II) Loader magic: 0x55d0a0362e20
[     3.449] (II) Module ABI versions:
[     3.449]    X.Org ANSI C Emulation: 0.4
[     3.449]    X.Org Video Driver: 24.0
[     3.449]    X.Org XInput driver : 24.1
[     3.449]    X.Org Server Extension : 10.0
[     3.449] (++) using VT number 1

[     3.450] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
[     3.451] (--) PCI:*(0@0:2:0) 8086:9b41:1028:099f rev 2, Mem @ 0x90000000/16777216, 0x80000000/268435456, I/O @ 0x00003000/64, BIOS @ 0x????????/131072
[     3.451] (II) LoadModule: "glx"
[     3.452] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     3.453] (II) Module glx: vendor="X.Org Foundation"
[     3.453]    compiled for 1.20.4, module version = 1.0.0
[     3.453]    ABI class: X.Org Server Extension, version 10.0
[     3.453] (==) Matched modesetting as autoconfigured driver 0
[     3.453] (==) Matched fbdev as autoconfigured driver 1
[     3.453] (==) Matched vesa as autoconfigured driver 2
[     3.453] (==) Assigned the driver to the xf86ConfigLayout
[     3.453] (II) LoadModule: "modesetting"
[     3.453] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     3.454] (II) Module modesetting: vendor="X.Org Foundation"
[     3.454]    compiled for 1.20.4, module version = 1.20.4
[     3.454]    Module class: X.Org Video Driver
[     3.454]    ABI class: X.Org Video Driver, version 24.0
[     3.454] (II) LoadModule: "fbdev"
[     3.454] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     3.454] (II) Module fbdev: vendor="X.Org Foundation"
[     3.454]    compiled for 1.20.0, module version = 0.5.0
[     3.454]    Module class: X.Org Video Driver
[     3.454]    ABI class: X.Org Video Driver, version 24.0
[     3.454] (II) LoadModule: "vesa"
[     3.454] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     3.454] (II) Module vesa: vendor="X.Org Foundation"
[     3.454]    compiled for 1.20.1, module version = 2.4.0
[     3.454]    Module class: X.Org Video Driver
[     3.454]    ABI class: X.Org Video Driver, version 24.0
[     3.454] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     3.454] (II) FBDEV: driver for framebuffer: fbdev
[     3.454] (II) VESA: driver for VESA chipsets: vesa
[     3.455] (EE) open /dev/dri/card0: No such file or directory
[     3.455] (WW) Falling back to old probe method for modesetting
[     3.455] (EE) open /dev/dri/card0: No such file or directory
[     3.455] (II) Loading sub module "fbdevhw"
[     3.455] (II) LoadModule: "fbdevhw"
[     3.455] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     3.455] (II) Module fbdevhw: vendor="X.Org Foundation"
[     3.455]    compiled for 1.20.4, module version = 0.0.2
[     3.455]    ABI class: X.Org Video Driver, version 24.0
[     3.455] (EE) Unable to find a valid framebuffer device
[     3.455] (WW) Falling back to old probe method for fbdev
[     3.455] (II) Loading sub module "fbdevhw"
[     3.455] (II) LoadModule: "fbdevhw"
[     3.455] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     3.455] (II) Module fbdevhw: vendor="X.Org Foundation"
[     3.455]    compiled for 1.20.4, module version = 0.0.2
[     3.455]    ABI class: X.Org Video Driver, version 24.0
[     3.455] (II) FBDEV(2): using default device
[     3.455] (EE) Screen 0 deleted because of no matching config section.
[     3.455] (II) UnloadModule: "modesetting"
[     3.455] (EE) Screen 0 deleted because of no matching config section.
[     3.455] (II) UnloadModule: "fbdev"
[     3.455] (II) UnloadSubModule: "fbdevhw"
[     3.455] (EE)
Fatal server error:
[     3.455] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[     3.455] (EE)
[     3.455] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[     3.455] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[     3.455] (EE)
[     3.458] (EE) Server terminated with error (1). Closing log file.

$ sudo fbset -i

mode "1920x1080"
    geometry 1920 1080 1920 1080 32
    timings 0 0 0 0 0 0 0
    accel true
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : i915drmfb
    Address     : 0
    Size        : 8294400
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 7680
    Accelerator : No

$ sudo journalctl -b | grep i915
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
oct. 30 13:19:21 ABI20 kernel: [drm] Initialized i915 1.6.0 20200515 for 0000:00:02.0 on minor 0
oct. 30 13:19:21 ABI20 kernel: fbcon: i915drmfb (fb0) is primary device
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
oct. 30 13:19:22 ABI20 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

$ cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  14670662-fa63-4e49-a473-79a5d2cacb87
else
  search --no-floppy --fs-uuid --set=root 14670662-fa63-4e49-a473-79a5d2cacb87
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  14670662-fa63-4e49-a473-79a5d2cacb87
else
  search --no-floppy --fs-uuid --set=root 14670662-fa63-4e49-a473-79a5d2cacb87
fi
insmod png
if background_image /usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
   set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-14670662-fa63-4e49-a473-79a5d2cacb87' {
   load_video
   insmod gzio
   if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
   insmod part_gpt
   insmod ext2
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root  14670662-fa63-4e49-a473-79a5d2cacb87
   else
     search --no-floppy --fs-uuid --set=root 14670662-fa63-4e49-a473-79a5d2cacb87
   fi
   echo   'Chargement de Linux 5.8.0-0.bpo.2-amd64…'
   linux   /boot/vmlinuz-5.8.0-0.bpo.2-amd64 root=UUID=14670662-fa63-4e49-a473-79a5d2cacb87 ro  quiet
   echo   'Chargement du disque mémoire initial…'
   initrd   /boot/initrd.img-5.8.0-0.bpo.2-amd64
}
submenu 'Options avancées pour Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-14670662-fa63-4e49-a473-79a5d2cacb87' {
   menuentry 'Debian GNU/Linux, avec Linux 5.8.0-0.bpo.2-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.8.0-0.bpo.2-amd64-advanced-14670662-fa63-4e49-a473-79a5d2cacb87' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  14670662-fa63-4e49-a473-79a5d2cacb87
      else
        search --no-floppy --fs-uuid --set=root 14670662-fa63-4e49-a473-79a5d2cacb87
      fi
      echo   'Chargement de Linux 5.8.0-0.bpo.2-amd64…'
      linux   /boot/vmlinuz-5.8.0-0.bpo.2-amd64 root=UUID=14670662-fa63-4e49-a473-79a5d2cacb87 ro  quiet
      echo   'Chargement du disque mémoire initial…'
      initrd   /boot/initrd.img-5.8.0-0.bpo.2-amd64
   }
   menuentry 'Debian GNU/Linux, with Linux 5.8.0-0.bpo.2-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.8.0-0.bpo.2-amd64-recovery-14670662-fa63-4e49-a473-79a5d2cacb87' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  14670662-fa63-4e49-a473-79a5d2cacb87
      else
        search --no-floppy --fs-uuid --set=root 14670662-fa63-4e49-a473-79a5d2cacb87
      fi
      echo   'Chargement de Linux 5.8.0-0.bpo.2-amd64…'
      linux   /boot/vmlinuz-5.8.0-0.bpo.2-amd64 root=UUID=14670662-fa63-4e49-a473-79a5d2cacb87 ro single
      echo   'Chargement du disque mémoire initial…'
      initrd   /boot/initrd.img-5.8.0-0.bpo.2-amd64
   }
   menuentry 'Debian GNU/Linux, avec Linux 4.19.0-12-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-12-amd64-advanced-14670662-fa63-4e49-a473-79a5d2cacb87' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  14670662-fa63-4e49-a473-79a5d2cacb87
      else
        search --no-floppy --fs-uuid --set=root 14670662-fa63-4e49-a473-79a5d2cacb87
      fi
      echo   'Chargement de Linux 4.19.0-12-amd64…'
      linux   /boot/vmlinuz-4.19.0-12-amd64 root=UUID=14670662-fa63-4e49-a473-79a5d2cacb87 ro  quiet
      echo   'Chargement du disque mémoire initial…'
      initrd   /boot/initrd.img-4.19.0-12-amd64
   }
   menuentry 'Debian GNU/Linux, with Linux 4.19.0-12-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-12-amd64-recovery-14670662-fa63-4e49-a473-79a5d2cacb87' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  14670662-fa63-4e49-a473-79a5d2cacb87
      else
        search --no-floppy --fs-uuid --set=root 14670662-fa63-4e49-a473-79a5d2cacb87
      fi
      echo   'Chargement de Linux 4.19.0-12-amd64…'
      linux   /boot/vmlinuz-4.19.0-12-amd64 root=UUID=14670662-fa63-4e49-a473-79a5d2cacb87 ro single
      echo   'Chargement du disque mémoire initial…'
      initrd   /boot/initrd.img-4.19.0-12-amd64
   }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
   fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
User avatar
Bernoot
 
Posts: 6
Joined: 2020-10-31 11:58

Re: intel card recognised but not used, llvmpipe used instea

Postby Deb-fan » 2020-10-31 12:48

Weird ... just some random thoughts which popped into head. You clearly installed kernel 5.8 which yep, you should do for a 10th gen i5, did you also upgrade whatever firmware pkgs too ? Other thing is try recreating your initrd.img cmd is something like "update-initramfs -u" etc, "man update-initramfs". I mean that should've been done, the script which handles that type of thing should've handled anything like this needed when you installed the new kernel. Something to investigate though, don't have a super deep understanding of the topic and how it's handled in Debian Buster.

Do you have anything which relies on dkms, might look into upgrading it too if needed, really overall hazy on much of this but may be of some help, so there you have it. I have(do remember)having to chase newer versions of dkms and the broadcom-sta-dkms pkgs to get my broadcom wireless "wl" module to build correctly and install with newer kernels.
Most powerful FREE tech-support tool on the planet * HERE. *
Deb-fan
 
Posts: 968
Joined: 2012-08-14 12:27

Re: intel card recognised but not used, llvmpipe used instea

Postby Bernoot » 2020-10-31 14:19

Hi, and thanks for answering so fast

Deb-fan wrote: did you also upgrade whatever firmware pkgs too ?


I have firmware-misc-nonfree firmware-linux-nonfree firmware-linux installed.
However, reinstalling firmware-misc-nonfree reslts in:

Code: Select all
$ sudo apt --reinstall install firmware-misc-nonfree
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 3 338 ko dans les archives.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Réception de :1 http://deb.debian.org/debian buster/non-free amd64 firmware-misc-nonfree all 20190114-2 [3 338 kB]
3 338 ko réceptionnés en 3s (1 290 ko/s)               
(Lecture de la base de données... 269790 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../firmware-misc-nonfree_20190114-2_all.deb ...
Dépaquetage de firmware-misc-nonfree (20190114-2) sur (20190114-2) ...
Paramétrage de firmware-misc-nonfree (20190114-2) ...
update-initramfs: deferring update (trigger activated)
Traitement des actions différées (« triggers ») pour initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-0.bpo.2-amd64
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.12.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_06.bin for module i915


Indeed, file names in /lib/firmware/i915/ do not match with the required ones:
Code: Select all
$ ls /lib/firmware/i915
bxt_dmc_ver1_07.bin  bxt_huc_ver01_07_1398.bin  kbl_dmc_ver1_04.bin  kbl_huc_ver02_00_1810.bin  skl_dmc_ver1.bin    skl_guc_ver6.bin
bxt_dmc_ver1.bin     cnl_dmc_ver1_07.bin        kbl_dmc_ver1.bin     skl_dmc_ver1_23.bin        skl_guc_ver1.bin    skl_guc_ver9_33.bin
bxt_guc_ver8_7.bin   glk_dmc_ver1_04.bin        kbl_guc_ver9_14.bin  skl_dmc_ver1_26.bin        skl_guc_ver4.bin    skl_huc_ver01_07_1398.bin
bxt_guc_ver9_29.bin  kbl_dmc_ver1_01.bin        kbl_guc_ver9_39.bin  skl_dmc_ver1_27.bin        skl_guc_ver6_1.bin


Is it safe to ln -s some existing files with names in the "missing" list?
Does initramfs require all these files to be present, or only one / some ?

Do you have anything which relies on dkms, might look into upgrading it too if needed


hmmm, not sure I understand what it is about.
I have installed dkms, then tried sudo dkms autoinstall and sudo dkms status, and got no answer at all.
then sudo update-initramfs -u gives the same warnings about missing i915/*.bin files.

Thanks again for your time!
User avatar
Bernoot
 
Posts: 6
Joined: 2020-10-31 11:58

Re: intel card recognised but not used, llvmpipe used instea

Postby Deb-fan » 2020-10-31 15:19

What I was meaning is when you upgrade the kernel like that on newer hardware, should also upgrade whatever firmware from buster-backports too. Try that and then if needed run the "update-initramfs" thing again, see if it clears up for you.

Ps, would also go ahead and install the kernel headers that correspond to the 5.8 kernel version you're using too. Why not, not sure it's needed but not like they take up overmuch space. Anyway, that's about best I've got, hopefully helps out. :)
Most powerful FREE tech-support tool on the planet * HERE. *
Deb-fan
 
Posts: 968
Joined: 2012-08-14 12:27

Re: intel card recognised but not used, llvmpipe used instea

Postby Bernoot » 2020-10-31 17:09

Deb-fan wrote:should also upgrade whatever firmware from buster-backports too.
[...]
install the kernel headers that correspond to the 5.8 kernel version

OK, I have done this:
Code: Select all
$ sudo apt install linux-headers-5.8.0-0.bpo.2-amd64
[...]
$ sudo apt -t buster-backports install firmware-misc-nonfree firmware-linux-nonfree firmware-linux
[...]
$ apt list firmware-misc-nonfree firmware-linux-nonfree firmware-linux
firmware-linux-nonfree/buster-backports,now 20200918-1~bpo10+1 all  [installé]
firmware-linux/buster-backports,now 20200918-1~bpo10+1 all  [installé]
firmware-misc-nonfree/buster-backports,now 20200918-1~bpo10+1 all  [installé]

Also, I found on another forum that the missing i915/*.bin files could be downloaded from intel's blob list. I downloaded all those required files.
Now, sudo update-initramfs -u does not complain about missing files anymore: :)

But after rebooting, I still have the intel/llvmpipe issue :( , and /var/log/Xorg.0.log shows the same strange/error lines as in my initial post:
  • it refers to 4.19.0-10-amd64, while uname -a says 5.8.0-0.bpo.2-amd64.
  • it shows the "/dev/dri/card0: No such file or directory" error, while in fact /dev/dri/card0 does exist (see below)
  • it ends after "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"
Code: Select all
$ ls -l /dev/dri
total 0
drwxr-xr-x  2 root root         80 oct.  31 18:11 by-path
crw-rw----+ 1 root video  226,   0 oct.  31 18:11 card0
crw-rw----+ 1 root render 226, 128 oct.  31 18:11 renderD128


... cannot figure out what to do.
User avatar
Bernoot
 
Posts: 6
Joined: 2020-10-31 11:58

Re: intel card recognised but not used, llvmpipe used instea

Postby Deb-fan » 2020-10-31 17:53

I can't figure it out either, what's this llvm thing ? Logical volume management ? You're using LVM ? Might look into upgrading it as well. Never dorked with LVM, just making a wild assumption at this point that it may be playing a role ? Honestly am about out of suggestions. Though if you figure it out, post the solution for whomever else.
Most powerful FREE tech-support tool on the planet * HERE. *
Deb-fan
 
Posts: 968
Joined: 2012-08-14 12:27

Re: intel card recognised but not used, llvmpipe used instea

Postby sgosnell » 2020-10-31 18:25

You're running this instance inside a virtual machine? Which is which? I don't see from a cursory reading which version is inside which. It appears that one is using 4.19 and one 5.8. The llvm is for virtualbox. Exactly what is going on with the system?
Take my advice, I'm not using it.
sgosnell
 
Posts: 905
Joined: 2011-03-14 01:49

Re: intel card recognised but not used, llvmpipe used instea

Postby p.H » 2020-10-31 19:45

Bernoot wrote:I also find puzzling that uname says the kernel is 5.8 while /var/log/Xorg.0.log says "Build Operating System: Linux 4.19.0-10-amd64 x86_64 Debian".

"Build Operating System" is the system used to build (compile) Xorg binaries. It is expected that Xorg for buster was built on a system running buster's kernel.
More interesting are the next two lines :
Code: Select all
[     3.445] Current Operating System: Linux ABI20 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64
[     3.445] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-amd64 root=UUID=14670662-fa63-4e49-a473-79a5d2cacb87 ro quiet nomodeset

They say that the current running kernel was 4.19.0-12. Obviously this log was not created while running a 5.8 kernel.
Check the Xorg.0.log file date. I bet it is outdated. AFAIK Gnome and GDM do not write Xorg logs in /var/log but in some dot directory under the user's home directory (check gdm home directory in /etc/passwd).

Also, the kernel parameter "nomodeset" disables graphic acceleration. So it is normal that /dev/dri/card0 does not exist and Xorg uses software rendering. This kernel parameter was not added automatically, so you added it somehow.

Bernoot wrote:Does initramfs require all these files to be present, or only one / some ?

The initramfs does not require any of these files to be present. The messages are only warnings. They are displayed when a kernel module is embedded in the initramfs (graphic modules are embedded if plymouth, the splash screen, is installed) and advertises that it may use missing firmware files for some supported hardware. But the firmware files actually needed, loaded or missing are only mentioned in the kernel logs, such as :
Code: Select all
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
oct. 30 13:19:21 ABI20 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)

So the only firmware needed was already present.

Bernoot wrote:hmmm, not sure I understand what it is about.
I have installed dkms

If you do not understand, why don't you just search or ask for explanation before installing anything ? dkms and kernel headers are used to build out-of-tree kernel modules. Irrelevant here.

Bernoot wrote:But after rebooting, I still have the intel/llvmpipe issue :( , and /var/log/Xorg.0.log shows the same strange/error lines as in my initial post:

Because the file you are reading was not updated. Still the same old outdated file. Look for the current Xorg log files in the proper places (see above).

Deb-fan wrote:I can't figure it out either, what's this llvm thing ?

Can't you just shut up when you're clueless, and spare us your annoying "random thoughts" and "wild assumptions" ?
LLVM has nothing to do with LVM. A quick search in Wikipedia would have given you useful information about LLVM and MESA's llvmpipe.
p.H
 
Posts: 1519
Joined: 2017-09-17 07:12

Re: intel card recognised but not used, llvmpipe used instea

Postby stevepusser » 2020-11-01 03:59

The simple and correct answer, which could be verified by testing a Live ISO of MX Linux AHS or KDE versions, which support 10th-gen out of the box, and which I've already mentioned quite a few times here: 10th-gen Intel requires a newer Mesa to work correctly (DRI acceleration instead of llvm), which is not available in buster-backports. I expect these questions to only become more common until Bullseye is released, so perhaps a note could be made of that fact.

I was behind the MX AHS release to start with, and would have preferred not to have to backport LLVM 10 and a newer Mesa, but facts are facts--I had to do so. Maybe a Debian maintainer could do it for backports, since it seems to work a treat for MX.
MX Linux packager and developer
User avatar
stevepusser
 
Posts: 12131
Joined: 2009-10-06 05:53

Re: intel card recognised but not used, llvmpipe used instea

Postby Bernoot » 2020-11-01 08:26

Many interesting thing,
Deb-fan wrote:I can't figure it out either, what's this llvm thing ?

AFAIK, a software replacement for graphic treatments provided by a dedicated chipset.
Honestly am about out of suggestions. Though if you figure it out, post the solution for whomever else.

OK, thanks for trying, anyway.
sgosnell wrote:You're running this instance inside a virtual machine?

No, the lvm in llvm does not mean this is a virtual machine. My system is a fresh debian 10 install in a new machine.
p.H wrote:Check the Xorg.0.log file date. I bet it is outdated.

You win the bet: file date is system install time. I was wrongly thinking that this was a log file which was re-generated at each boot.
p.H wrote:the kernel parameter "nomodeset" disables graphic acceleration.

Yes, my first boot after installation showed a black screen. This is why I added nomodeset.
:?: Now, after installing all the firmware / xorg stuff, I should be able to remove it and get a proper display, no?
p.H wrote:Because the file you are reading was not updated. Still the same old outdated file. Look for the current Xorg log files in the proper places (see above).

I tried to, but no success: sudo find / -iname "*Xorg*" shows no result in /home/, and no .log file except in /var/log.
stevepusser wrote:10th-gen Intel requires a newer Mesa to work correctly (DRI acceleration instead of llvm)

So, I understand I just have to wait for updates :? .

:?: In the meantime, is there a way to at least reconfigure Xorg under the 5.8 kernel, without the nomodeset option?
User avatar
Bernoot
 
Posts: 6
Joined: 2020-10-31 11:58

Re: intel card recognised but not used, llvmpipe used instea

Postby p.H » 2020-11-01 08:52

Bernoot wrote:Yes, my first boot after installation showed a black screen. This is why I added nomodeset.
Now, after installing all the firmware / xorg stuff, I should be able to remove it and get a proper display, no?

According to the output of fbset and journalctl and the contents of grub.cfg in your original post, nomodeset is no longer present. If you just added it once in the GRUB menu entry editor, it was not persistent.

Bernoot wrote:sudo find / -iname "*Xorg*" shows no result in /home/, and no .log file except in /var/log.

Sorry but I do not have any system with GNOME and cannot be more precise about Xorg log location.
p.H
 
Posts: 1519
Joined: 2017-09-17 07:12

Re: intel card recognised but not used, llvmpipe used instea

Postby Deb-fan » 2020-11-01 11:48

Thanks sgosnell, it's a VM, that's good to know.

Self-edit to take the vulgarity level down a notch:

@p.H .. can't you just sniff my dirty under shorts ? :D Perhaps you've heard of scrolling or can figure out how to utilize the forums ignore feature ?
Last edited by Deb-fan on 2020-11-01 17:59, edited 1 time in total.
Most powerful FREE tech-support tool on the planet * HERE. *
Deb-fan
 
Posts: 968
Joined: 2012-08-14 12:27

Re: intel card recognised but not used, llvmpipe used instea

Postby Bernoot » 2020-11-01 12:10

p.H wrote:nomodeset is no longer present. If you just added it once in the GRUB menu entry editor, it was not persistent.

Yes, if I remember well, I added nomodeset using the "e" option when grub boot screen was displayed. If I understand well, this is a one-shot option.
But if Xorg was configured during this session, does it result in nomodeset being active afterwards? In this case would it be a good idea to configure Xorg again (how?), while under 5.8 and nomodeset option removed?
N.B. in my grub config files, nomodeset is only present for the linux recovery option in /etc/grub.d/10_linux, which makes sense.
User avatar
Bernoot
 
Posts: 6
Joined: 2020-10-31 11:58

Re: intel card recognised but not used, llvmpipe used instea

Postby p.H » 2020-11-01 18:43

Bernoot wrote:But if Xorg was configured during this session, does it result in nomodeset being active afterwards?

No. By default, Xorg is autoconfigured each time it is started.
Bernoot wrote:N.B. in my grub config files, nomodeset is only present for the linux recovery option in /etc/grub.d/10_linux

I do not see "nomodeset" in recovery menu entries in the grub.cfg included in your original post.
p.H
 
Posts: 1519
Joined: 2017-09-17 07:12

Re: intel card recognised but not used, llvmpipe used instea

Postby stevepusser » 2020-11-02 04:45

Sigh...llvm is NOT a virtual machine. It's a compiler toolchain which also includes the clang compiler. Mesa is compiled with the llvm toolchain, which is why it's mentioned when a driver has to fall back onto software rendering instead of direct rendering. A newer Mesa requires a newer llvm toolchain, which takes quite a while to backport, plus you will also probably need to cross-compile the i386 version for your 64-bit install. I had to use sbuild to build and cross-compile llvm-10--pbuilder builds barf and die after an annoyingly long time of building. :(

You can get it to work on Debian correctly by either updating to Debian testing, adding the MX 19 main and AHS repos and updating your driver stack from there, or doing all the backports yourself (not a trivial job). All may have some hurdles.
MX Linux packager and developer
User avatar
stevepusser
 
Posts: 12131
Joined: 2009-10-06 05:53

Next

Return to System configuration

Who is online

Users browsing this forum: No registered users and 16 guests

fashionable