• Debian Trixie: xorg with fb instead of intel or nouveau driver

    From =?UTF-8?Q?Chris_J=C3=B6lly?=@21:1/5 to All on Mon Feb 24 22:10:01 2025
    This is a multi-part message in MIME format.
    Hello,

    I have a Lenovo Thinkpad P50, which has the following setup:

    chris@laptop:~$ inxi -Gaz --za
    Graphics:
      Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915 v: kernel
        arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
        empty: none bus-ID: 00:02.0 chip-ID: 8086:191b class-ID: 0300
      Device-2: NVIDIA GM107GLM [Quadro M1000M] vendor: Lenovo driver: nouveau
        v: kernel non-free: 550/565.xx+ status: current (as of 2025-01;
        EOL~2026-12-xx) arch: Maxwell code: GMxxx process: TSMC 28nm
        built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max:
    gen: 3
        speed: 8 GT/s ports: active: DP-2 empty: DP-1,DP-3 bus-ID: 01:00.0
        chip-ID: 10de:13b1 class-ID: 0300 temp: 43.0 C
      Device-3: Bison ThinkPad P50 Integrated Camera driver: uvcvideo type: USB
        rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:6 chip-ID: 5986:0706
        class-ID: 0e02
      Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.5 driver: X:
        loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915,nouveau
        display-ID: :0 screens: 1
      Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
        s-diag: 1055mm (41.55")
      Monitor-1: DP-2 mapped: DP-1-2 pos: primary,left model: AOC 2260W
        serial: <filter> built: 2014 res: mode: 1920x1080 hz: 60 scale:
    100% (1)
        dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5")
        ratio: 16:9 modes: max: 1920x1080 min: 720x400
      Monitor-2: eDP-1 pos: right model: LG Display 0x054f built: 2016 res:
        mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2
        size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
        modes: 1920x1080
      API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau platforms:
        device: 0 drv: iris device: 1 drv: nouveau device: 2 drv: swrast gbm:
        drv: iris surfaceless: drv: iris x11: drv: iris inactive: wayland
      API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v: 24.3.4-3
    glx-v: 1.4
        direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL GT2)
        device-ID: 8086:191b memory: 14.96 GiB unified: yes
      Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr


    Everything works fine, except that I do not understand the messages in Xorg.0.log :)

    Its written that the fb and vesa drivers are loaded by the x server. I
    have no xorg.conf in /etc/X11.

    [    27.806] (==) Matched fbdev as autoconfigured driver 1
    [    27.806] (==) Matched vesa as autoconfigured driver 2

    ...

    [    27.815] (II) LoadModule: "fbdev"
    [    27.815] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so

    [    27.816] (II) LoadModule: "vesa"
    [    27.816] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so

    [    27.817] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [    27.817] (II) FBDEV: driver for framebuffer: fbdev
    [    27.817] (II) VESA: driver for VESA chipsets: vesa
    [    27.817] xf86EnableIO: failed to enable I/O ports 0000-03ff
    (Operation not permitted)
    [    27.817] (II) modeset(0): using drv /dev/dri/card1
    [    27.817] (WW) Falling back to old probe method for fbdev
    [    27.817] (II) Loading sub module "fbdevhw"
    [    27.817] (II) LoadModule: "fbdevhw"
    [    27.817] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [    27.818] (II) Module fbdevhw: vendor="X.Org Foundation"
    [    27.818]     compiled for 1.21.1.15, module version = 0.0.2
    [    27.818]     ABI class: X.Org Video Driver, version 25.2
    [    27.818] (II) modeset(G0): using drv /dev/dri/card0
    [    27.818] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
    [    27.818] (II) modeset(0): Creating default Display subsection in
    Screen section
        "Default Screen Section" for depth/fbbpp 24/32
    [    27.818] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
    [    27.818] (==) modeset(0): RGB weight 888
    [    27.818] (==) modeset(0): Default visual is TrueColor

    [    27.818] (II) Loading sub module "glamoregl"
    [    27.818] (II) LoadModule: "glamoregl"
    [    27.818] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [    27.822] (II) Module glamoregl: vendor="X.Org Foundation"
    [    27.822]     compiled for 1.21.1.15, module version = 1.0.1
    [    27.822]     ABI class: X.Org ANSI C Emulation, version 0.4
    [    27.865] (II) modeset(0): glamor X acceleration enabled on Mesa
    Intel(R) HD Graphics 530 (SKL GT2)
    [    27.865] (II) modeset(0): glamor initialized

    ...

    [    28.115] (II) Loading sub module "fb"
    [    28.115] (II) LoadModule: "fb"
    [    28.115] (II) Module "fb" already built-in
    [    28.115] (II) UnloadModule: "fbdev"
    [    28.115] (II) Unloading fbdev
    [    28.116] (II) UnloadSubModule: "fbdevhw"
    [    28.116] (II) Unloading fbdevhw
    [    28.116] (II) UnloadModule: "vesa"
    [    28.116] (II) Unloading vesa


    Shouldnt one of intel or nouveau drivers get loaded?

    Is there anything "wrong" or is it ok that the fb driver is loaded?

    Thanks for clarification!

    BR, Chris

    <!DOCTYPE html>
    <html>
    <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <p>Hello,</p>
    <p>I have a Lenovo Thinkpad P50, which has the following setup:</p>
    <p><font face="Courier New, Courier, monospace">chris@laptop:~$ inxi
    -Gaz --za<br>
    Graphics:<br>
      Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915 v:
    kernel<br>
        arch: Gen-9 process: Intel 14n built: 2015-16 ports: active:
    eDP-1<br>
        empty: none bus-ID: 00:02.0 chip-ID: 8086:191b class-ID:
    0300<br>
      Device-2: NVIDIA GM107GLM [Quadro M1000M] vendor: Lenovo
    driver: nouveau<br>
        v: kernel non-free: 550/565.xx+ status: current (as of
    2025-01;<br>
        EOL~2026-12-xx) arch: Maxwell code: GMxxx process: TSMC 28nm<br>
        built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3<br>
        speed: 8 GT/s ports: active: DP-2 empty: DP-1,DP-3 bus-ID:
    01:00.0<br>
        chip-ID: 10de:13b1 class-ID: 0300 temp: 43.0 C<br>
      Device-3: Bison ThinkPad P50 Integrated Camera driver:
    uvcvideo type: USB<br>
        rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:6
    chip-ID: 5986:0706<br>
        class-ID: 0e02<br>
      Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.5
    driver: X:<br>
        loaded: modesetting unloaded: fbdev,vesa dri: iris gpu:
    i915,nouveau<br>
        display-ID: :0 screens: 1<br>
      Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm
    (40.00x11.26")<br>
        s-diag: 1055mm (41.55")<br>
      Monitor-1: DP-2 mapped: DP-1-2 pos: primary,left model: AOC
    2260W<br>
        serial: &lt;filter&gt; built: 2014 res: mode: 1920x1080 hz:
    60 scale: 100% (1)<br>
        dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag:
    547mm (21.5")<br>
        ratio: 16:9 modes: max: 1920x1080 min: 720x400<br>
      Monitor-2: eDP-1 pos: right model: LG Display 0x054f built:
    2016 res:<br>
        mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2<br>
        size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio:
    16:9<br>
        modes: 1920x1080<br>
      API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau
    platforms:<br>
        device: 0 drv: iris device: 1 drv: nouveau device: 2 drv:
    swrast gbm:<br>
        drv: iris surfaceless: drv: iris x11: drv: iris inactive:
    wayland<br>
      API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v:
    24.3.4-3 glx-v: 1.4<br>
        direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL
    GT2)<br>
        device-ID: 8086:191b memory: 14.96 GiB unified: yes<br>
      Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo,
    xprop, xrandr</font></p>
    <p><br>
    </p>
    <p>Everything works fine, except that I do not understand the
    messages in Xorg.0.log :)</p>
    <p>Its written that the fb and vesa drivers are loaded by the x
    server. I have no xorg.conf in /etc/X11.</p>
    <p><font face="Courier New, Courier, monospace">[    27.806] (==)
    Matched fbdev as autoconfigured driver 1<br>
    [    27.806] (==) Matched vesa as autoconfigured driver 2</font></p>
    <p><font face="Courier New, Courier, monospace">...</font></p>
    <p><font face="Courier New, Courier, monospace">[    27.815] (II)
    LoadModule: "fbdev"<br>
    [    27.815] (II) Loading
    /usr/lib/xorg/modules/drivers/fbdev_drv.so</font></p>
    <p><font face="Courier New, Courier, monospace">[    27.816] (II)
    LoadModule: "vesa"<br>
    [    27.816] (II) Loading
    /usr/lib/xorg/modules/drivers/vesa_drv.so</font></p>
    <p><font face="Courier New, Courier, monospace">[    27.817] (II)
    modesetting: Driver for Modesetting Kernel Drivers: kms<br>
    [    27.817] (II) FBDEV: driver for framebuffer: fbdev<br>
    [    27.817] (II) VESA: driver for VESA chipsets: vesa<br>
    [    27.817] xf86EnableIO: failed to enable I/O ports 0000-03ff
    (Operation not permitted)<br>
    [    27.817] (II) modeset(0): using drv /dev/dri/card1<br>
    [    27.817] (WW) Falling back to old probe method for fbdev<br>
    [    27.817] (II) Loading sub module "fbdevhw"<br>
    [    27.817] (II) LoadModule: "fbdevhw"<br>
    [    27.817] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so<br>
    [    27.818] (II) Module fbdevhw: vendor="X.Org Foundation"<br>
    [    27.818]     compiled for 1.21.1.15, module version = 0.0.2<br>
    [    27.818]     ABI class: X.Org Video Driver, version 25.2<br>
    [    27.818] (II) modeset(G0): using drv /dev/dri/card0<br>
    [    27.818] (WW) VGA arbiter: cannot open kernel arbiter, no
    multi-card support<br>
    [    27.818] (II) modeset(0): Creating default Display
    subsection in Screen section<br>
        "Default Screen Section" for depth/fbbpp 24/32<br>
    [    27.818] (==) modeset(0): Depth 24, (==) framebuffer bpp 32<br>
    [    27.818] (==) modeset(0): RGB weight 888<br>
    [    27.818] (==) modeset(0): Default visual is TrueColor</font></p>
    <p><font face="Courier New, Courier, monospace">[    27.818] (II)
    Loading sub module "glamoregl"<br>
    [    27.818] (II) LoadModule: "glamoregl"<br>
    [    27.818] (II) Loading /usr/lib/xorg/modules/libglamoregl.so<br>
    [    27.822] (II) Module glamoregl: vendor="X.Org Foundation"<br>
    [    27.822]     compiled for 1.21.1.15, module version = 1.0.1<br>
    [    27.822]     ABI class: X.Org ANSI C Emulation, version 0.4<br>
    [    27.865] (II) modeset(0): glamor X acceleration enabled on
    Mesa Intel(R) HD Graphics 530 (SKL GT2)<br>
    [    27.865] (II) modeset(0): glamor initialized</font></p>
    <p><font face="Courier New, Courier, monospace">...</font></p>
    <p><font face="Courier New, Courier, monospace">[    28.115] (II)
    Loading sub module "fb"<br>
    [    28.115] (II) LoadModule: "fb"<br>
    [    28.115] (II) Module "fb" already built-in<br>
    [    28.115] (II) UnloadModule: "fbdev"<br>
    [    28.115] (II) Unloading fbdev<br>
    [    28.116] (II) UnloadSubModule: "fbdevhw"<br>
    [    28.116] (II) Unloading fbdevhw<br>
    [    28.116] (II) UnloadModule: "vesa"<br>
    [    28.116] (II) Unloading vesa</font></p>
    <p><br>
    </p>
    <p>Shouldnt one of intel or nouveau drivers get loaded?</p>
    <p>Is there anything "wrong" or is it ok that the fb driver is
    loaded?</p>
    <p>Thanks for clarification!</p>
    <p>BR, Chris<br>
    </p>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Greg Wooledge@21:1/5 to All on Mon Feb 24 22:20:01 2025
    On Mon, Feb 24, 2025 at 21:52:43 +0100, Chris Jlly wrote:
    chris@laptop:~$ inxi -Gaz --za
    Graphics:
    Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
    empty: none bus-ID: 00:02.0 chip-ID: 8086:191b class-ID: 0300
    Device-2: NVIDIA GM107GLM [Quadro M1000M] vendor: Lenovo driver: nouveau v: kernel non-free: 550/565.xx+ status: current (as of 2025-01;

    Shouldnt one of intel or nouveau drivers get loaded?

    No, because it's using modeset (for the Intel device at least).

    [ 27.817] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 27.817] (II) FBDEV: driver for framebuffer: fbdev
    [ 27.817] (II) VESA: driver for VESA chipsets: vesa
    [ 27.817] xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
    [ 27.817] (II) modeset(0): using drv /dev/dri/card1

    etc.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Felix Miata@21:1/5 to All on Mon Feb 24 22:30:01 2025
    Chris Jölly composed on 2025-02-24 21:52 (UTC+0100):

    I have a Lenovo Thinkpad P50, which has the following setup:

    chris@laptop:~$ inxi -Gaz --za
    Graphics:
      Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915

    i915 is the kernel module (hardware driver) required by your Intel 530 GPU.

      Device-2: NVIDIA GM107GLM [Quadro M1000M] vendor: Lenovo driver: nouveau

    nouveau is the kernel module (hardware driver) required by your NVidia GPU.

      Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.5 driver: X:
        loaded: modesetting

    modestting is the X display driver required by either the in use Intel 530 GPU or
    the inactive NVidia GPU.

      Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
        s-diag: 1055mm (41.55")

    This shows you have two identically configured screens mapped side by side as an
    expanded desktop.

    Everything works fine, except that I do not understand the messages in Xorg.0.log :)

    Its written that the fb and vesa drivers are loaded by the x server. I
    have no xorg.conf in /etc/X11.

    Their presence there with your hardware indicated serves only to confuse uninitiated users.

    [    27.806] (==) Matched fbdev as autoconfigured driver 1
    [    27.806] (==) Matched vesa as autoconfigured driver 2
    ...

    These could have been used if called upon, but the weren't/aren't necessary.

    What exactly from the log between .806 and .815 did you leave out?

    [    27.815] (II) LoadModule: "fbdev"
    ...
    [    27.817] (II) modeset(0): using drv /dev/dri/card1

    As inxi showed you, the dri system is employing the modesetting display driver. ...
    [    27.818] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
    [    27.818] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
    [    27.818] (==) modeset(0): RGB weight 888
    [    27.818] (==) modeset(0): Default visual is TrueColor

    [    27.818] (II) Loading sub module "glamoregl"
    [    27.818] (II) LoadModule: "glamoregl"
    [    27.818] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [    27.822] (II) Module glamoregl: vendor="X.Org Foundation"
    [    27.822]     compiled for 1.21.1.15, module version = 1.0.1 [    27.822]     ABI class: X.Org ANSI C Emulation, version 0.4 [    27.865] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) HD Graphics 530 (SKL GT2)
    [    27.865] (II) modeset(0): glamor initialized

    Shouldnt one of intel or nouveau drivers get loaded?

    Those actually needed were loaded and remained loaded.

    Is there anything "wrong" or is it ok that the fb driver is loaded?

    According to inxi, nothing is wrong with anything. (WW) lines in Xorg.0.log are just noise. X normally reports all drivers that could possibly have been required
    that succeeded to load did indeed load, but there should also be corresponding unload messages in the full log for those drivers not actually required.
    # inxi -G | grep Device-1
    Device-1: Intel HD Graphics 630 driver: i915 v: kernel
    # grep -i load /var/log/Xorg.0.log
    [ 10.603] (II) Loader magic: 0x55f3098a9de0
    [ 10.610] (II) LoadModule: "glx"
    [ 10.611] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
    [ 10.616] (II) LoadModule: "intel"
    [ 10.617] (EE) Failed to load module "intel" (module does not exist, 0)
    [ 10.617] (II) LoadModule: "modesetting"
    [ 10.617] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
    [ 10.617] (II) LoadModule: "fbdev"
    [ 10.617] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
    [ 10.618] (II) LoadModule: "vesa"
    [ 10.618] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    [ 10.642] (II) Loading sub module "fbdevhw"
    [ 10.642] (II) LoadModule: "fbdevhw"
    [ 10.642] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
    [ 10.643] (II) Loading sub module "glamoregl"
    [ 10.643] (II) LoadModule: "glamoregl"
    [ 10.643] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
    [ 10.919] (II) Loading sub module "fb"
    [ 10.919] (II) LoadModule: "fb"
    [ 10.919] (II) UnloadModule: "fbdev"
    [ 10.919] (II) Unloading fbdev
    [ 10.919] (II) UnloadSubModule: "fbdevhw"
    [ 10.919] (II) Unloading fbdevhw
    [ 10.919] (II) UnloadModule: "vesa"
    [ 10.919] (II) Unloading vesa
    [ 11.119] (II) AIGLX: Loaded and initialized iris
    [ 11.189] (II) LoadModule: "libinput"
    [ 11.189] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
    #
    --
    Evolution as taught in public schools is, like religion,
    based on faith, not based on science.

    Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

    Felix Miata

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonathan Dowland@21:1/5 to Greg on Thu Feb 27 10:30:01 2025
    On Tue Feb 25, 2025 at 1:38 PM GMT, Greg wrote:
    Did I read somewhere that the maintainer of the nouveau driver
    resigned due to the toxic atmosphere among the kernel developers, or
    did I dream that?

    The lead of the Asahi project (providing support for Apple-silicon Macs) recently resigned. Perhaps you're thinking of that.

    I read today that Christoph Hellwig, who was the person on the other
    side of that argument, has just stepped down from 2 of his kernel responsibilities, including the DRM subsystem.




    --
    Please do not CC me for listmail.

    👱🏻 Jonathan Dowland
    jmtd@debian.org
    🔗 https://jmtd.net

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonathan Dowland@21:1/5 to Greg on Thu Feb 27 17:00:01 2025
    On Thu Feb 27, 2025 at 2:23 PM GMT, Greg wrote:
    On 2025-02-27, Jonathan Dowland <jmtd@debian.org> wrote:
    On Tue Feb 25, 2025 at 1:38 PM GMT, Greg wrote:
    Did I read somewhere that the maintainer of the nouveau driver
    resigned due to the toxic atmosphere among the kernel developers, or
    did I dream that?

    The lead of the Asahi project (providing support for Apple-silicon Macs)
    recently resigned. Perhaps you're thinking of that.

    Thank you, but the article I saw (I looked it up) actually referred to Karol Herbst.

    https://www.phoronix.com/news/Karol-Herbst-Nouveau-No

    Ah. Thanks for sharing!

    --
    Please do not CC me for listmail.

    👱🏻 Jonathan Dowland
    jmtd@debian.org
    🔗 https://jmtd.net

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Felix Miata@21:1/5 to All on Fri Feb 28 23:10:01 2025
    Chris Jölly composed on 2025-02-28 21:28 (UTC+0100):

    So, modesetting is the real thing?

    Since about a decade or so ago. It originally was provided as a separate packge,
    but was moved into the Xorg server .deb as a default for all GPUs for which an appropriate kernel module exists, mainly radeon, amdgpu, i915, xe & nouveau.

    no need to keep fbdev, vesa, intel
    and nouveau x-server driver packages on the system (as well as ati, amd, radeon...)?

    No real need, unless something breaks WRT using the modesetting that can be worked
    around by using another. For the 530, I have on occasion seen reports of more favorable results from intel than from modesetting. My 620s both provide entirely
    satisfactory results from modesetting, as does my 730, and all those I have older
    than 530 that it supports.
    --
    Evolution as taught in public schools is, like religion,
    based on faith, not based on science.

    Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

    Felix Miata

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Chris_J=C3=B6lly?=@21:1/5 to Felix Miata on Fri Feb 28 21:40:01 2025
    This is a multi-part message in MIME format.
    On 2/24/25 22:25, Felix Miata wrote:
    Chris Jölly composed on 2025-02-24 21:52 (UTC+0100):

    modestting is the X display driver required by either the in use Intel 530 GPU or
    the inactive NVidia GPU.
    Ok, so modesetting is the X display driver, not how I expected the intel
    or nouveau driver, right?
    Its written that the fb and vesa drivers are loaded by the x server. I
    have no xorg.conf in /etc/X11.
    Their presence there with your hardware indicated serves only to confuse uninitiated users.

    [    27.806] (==) Matched fbdev as autoconfigured driver 1
    [    27.806] (==) Matched vesa as autoconfigured driver 2
    ...

    These could have been used if called upon, but the weren't/aren't necessary.

    What exactly from the log between .806 and .815 did you leave out?

    Here is the part including with what I left out:

    [    27.806] (==) Matched modesetting as autoconfigured driver 0
    [    27.806] (==) Matched fbdev as autoconfigured driver 1
    [    27.806] (==) Matched vesa as autoconfigured driver 2
    [    27.806] (==) Assigned the driver to the xf86ConfigLayout
    [    27.806] (II) LoadModule: "modesetting"
    [    27.814] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [    27.815] (II) Module modesetting: vendor="X.Org Foundation"
    [    27.815]     compiled for 1.21.1.15, module version = 1.21.1
    [    27.815]     Module class: X.Org Video Driver
    [    27.815]     ABI class: X.Org Video Driver, version 25.2
    [    27.815] (II) LoadModule: "fbdev"
    [    27.815] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [    27.816] (II) Module fbdev: vendor="X.Org Foundation"
    [    27.816]     compiled for 1.21.1.3, module version = 0.5.0
    [    27.816]     Module class: X.Org Video Driver
    [    27.816]     ABI class: X.Org Video Driver, version 25.2
    [    27.816] (II) LoadModule: "vesa"
    [    27.816] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [    27.817] (II) Module vesa: vendor="X.Org Foundation"
    [    27.817]     compiled for 1.21.1.9, module version = 2.6.0
    [    27.817]     Module class: X.Org Video Driver
    [    27.817]     ABI class: X.Org Video Driver, version 25.2
    [    27.817] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [    27.817] (II) FBDEV: driver for framebuffer: fbdev
    [    27.817] (II) VESA: driver for VESA chipsets: vesa
    [    27.817] xf86EnableIO: failed to enable I/O ports 0000-03ff
    (Operation not permitted)
    [    27.817] (II) modeset(0): using drv /dev/dri/card1
    [    27.817] (WW) Falling back to old probe method for fbdev
    [    27.817] (II) Loading sub module "fbdevhw"
    [    27.817] (II) LoadModule: "fbdevhw"
    [    27.817] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [    27.818] (II) Module fbdevhw: vendor="X.Org Foundation"
    [    27.818]     compiled for 1.21.1.15, module version = 0.0.2
    [    27.818]     ABI class: X.Org Video Driver, version 25.2
    [    27.818] (II) modeset(G0): using drv /dev/dri/card0
    [    27.818] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
    [    27.818] (II) modeset(0): Creating default Display subsection in
    Screen section
        "Default Screen Section" for depth/fbbpp 24/32
    [    27.818] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
    [    27.818] (==) modeset(0): RGB weight 888
    [    27.818] (==) modeset(0): Default visual is TrueColor
    [    27.818] (II) Loading sub module "glamoregl"
    [    27.818] (II) LoadModule: "glamoregl"
    [    27.818] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [    27.822] (II) Module glamoregl: vendor="X.Org Foundation"
    [    27.822]     compiled for 1.21.1.15, module version = 1.0.1
    [    27.822]     ABI class: X.Org ANSI C Emulation, version 0.4
    [    27.865] (II) modeset(0): glamor X acceleration enabled on Mesa
    Intel(R) HD Graphics 530 (SKL GT2)
    [    27.865] (II) modeset(0): glamor initialized

    Shouldnt one of intel or nouveau drivers get loaded?
    Those actually needed were loaded and remained loaded.

    Ok, it is just confusion on my side. Basically, I did not know how the
    actual graphics stack works, its some years where knew more details
    about how a desktop environment works. Things changed a lot it seems
    since the times where one needed to fiddle around with modlines in
    xorg.conf.

    Is there anything "wrong" or is it ok that the fb driver is loaded?
    According to inxi, nothing is wrong with anything. (WW) lines in Xorg.0.log are
    just noise. X normally reports all drivers that could possibly have been required
    that succeeded to load did indeed load, but there should also be corresponding
    unload messages in the full log for those drivers not actually required.
    # inxi -G | grep Device-1
    Device-1: Intel HD Graphics 630 driver: i915 v: kernel
    # grep -i load /var/log/Xorg.0.log
    [ 10.603] (II) Loader magic: 0x55f3098a9de0
    [ 10.610] (II) LoadModule: "glx"
    [ 10.611] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
    [ 10.616] (II) LoadModule: "intel"
    [ 10.617] (EE) Failed to load module "intel" (module does not exist, 0)
    [ 10.617] (II) LoadModule: "modesetting"
    [ 10.617] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 10.617] (II) LoadModule: "fbdev"
    [ 10.617] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
    [ 10.618] (II) LoadModule: "vesa"
    [ 10.618] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    [ 10.642] (II) Loading sub module "fbdevhw"
    [ 10.642] (II) LoadModule: "fbdevhw"
    [ 10.642] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
    [ 10.643] (II) Loading sub module "glamoregl"
    [ 10.643] (II) LoadModule: "glamoregl"
    [ 10.643] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
    [ 10.919] (II) Loading sub module "fb"
    [ 10.919] (II) LoadModule: "fb"
    [ 10.919] (II) UnloadModule: "fbdev"
    [ 10.919] (II) Unloading fbdev
    [ 10.919] (II) UnloadSubModule: "fbdevhw"
    [ 10.919] (II) Unloading fbdevhw
    [ 10.919] (II) UnloadModule: "vesa"
    [ 10.919] (II) Unloading vesa
    [ 11.119] (II) AIGLX: Loaded and initialized iris
    [ 11.189] (II) LoadModule: "libinput"
    [ 11.189] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
    #

    So, modesetting is the real thing? no need to keep fbdev, vesa, intel
    and nouveau x-server driver packages on the system (as well as ati, amd, radeon...)?

    chris@laptop1:~$ dpkg -l | grep xserver.*video
    ii  xserver-xorg-video-amdgpu 23.0.0-1                           
    amd64        X.Org X server -- AMDGPU display driver
    ii  xserver-xorg-video-ati 1:22.0.0-1                         
    amd64        X.Org X server -- AMD/ATI display driver wrapper
    ii  xserver-xorg-video-fbdev 1:0.5.0-2                          
    amd64        X.Org X server -- fbdev display driver
    ii  xserver-xorg-video-intel 2:2.99.917+git20210115-1            amd64        X.Org X server -- Intel i8xx, i9xx display driver
    ii  xserver-xorg-video-nouveau 1:1.0.18-1                         
    amd64        X.Org X server -- Nouveau display driver
    ii  xserver-xorg-video-qxl 0.1.6-1.1                          
    amd64        X.Org X server -- QXL display driver
    ii  xserver-xorg-video-radeon 1:22.0.0-1                         
    amd64        X.Org X server -- AMD/ATI Radeon display driver
    ii  xserver-xorg-video-vesa 1:2.6.0-1                          
    amd64        X.Org X server -- VESA display driver
    ii  xserver-xorg-video-vmware 1:13.4.0-1                         
    amd64        X.Org X server -- VMware display driver
    chris@laptop1:~$

    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2/24/25 22:25, Felix Miata wrote:<br>
    </div>
    <blockquote type="cite"
    cite="mid:0464f4f0-82d9-0de4-a375-1cd75e6aa92b@stanis.net">
    <pre wrap="" class="moz-quote-pre">Chris Jölly composed on 2025-02-24 21:52 (UTC+0100):

    </pre>
    <pre wrap="" class="moz-quote-pre">modestting is the X display driver required by either the in use Intel 530 GPU or
    the inactive NVidia GPU.</pre>
    </blockquote>
    Ok, so modesetting is the X display driver, not how I expected the
    intel or nouveau driver, right?<br>
    <blockquote type="cite"
    cite="mid:0464f4f0-82d9-0de4-a375-1cd75e6aa92b@stanis.net">
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">Its written that the fb and vesa drivers are loaded by the x server. I
    have no xorg.conf in /etc/X11.
    </pre>
    </blockquote>
    <pre wrap="" class="moz-quote-pre">
    Their presence there with your hardware indicated serves only to confuse uninitiated users.

    </pre>
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">[    27.806] (==) Matched fbdev as autoconfigured driver 1
    [    27.806] (==) Matched vesa as autoconfigured driver 2
    </pre>
    </blockquote>
    <pre wrap="" class="moz-quote-pre">...

    These could have been used if called upon, but the weren't/aren't necessary.

    What exactly from the log between .806 and .815 did you leave out?</pre>
    </blockquote>
    <p>Here is the part including with what I left out:</p>
    <p><font face="Courier New, Courier, monospace">[    27.806] (==)
    Matched modesetting as autoconfigured driver 0<br>
    [    27.806] (==) Matched fbdev as autoconfigured driver 1<br>
    [    27.806] (==) Matched vesa as autoconfigured driver 2<br>
    [    27.806] (==) Assigned the driver to the xf86ConfigLayout<br>
    [    27.806] (II) LoadModule: "modesetting"<br>
    [    27.814] (II) Loading
    /usr/lib/xorg/modules/drivers/modesetting_drv.so<br>
    [    27.815] (II) Module modesetting: vendor="X.Org Foundation"<br>
    [    27.815]     compiled for 1.21.1.15, module version = 1.21.1<br>
    [    27.815]     Module class: X.Org Video Driver<br>
    [    27.815]     ABI class: X.Org Video Driver, version 25.2<br>
    [    27.815] (II) LoadModule: "fbdev"<br>
    [    27.815] (II) Loading
    /usr/lib/xorg/modules/drivers/fbdev_drv.so<br>
    [    27.816] (II) Module fbdev: vendor="X.Org Foundation"<br>
    [    27.816]     compiled for 1.21.1.3, module version = 0.5.0<br>
    [    27.816]     Module class: X.Org Video Driver<br>
    [    27.816]     ABI class: X.Org Video Driver, version 25.2<br>
    [    27.816] (II) LoadModule: "vesa"<br>
    [    27.816] (II) Loading
    /usr/lib/xorg/modules/drivers/vesa_drv.so<br>
    [    27.817] (II) Module vesa: vendor="X.Org Foundation"<br>
    [    27.817]     compiled for 1.21.1.9, module version = 2.6.0<br>
    [    27.817]     Module class: X.Org Video Driver<br>
    [    27.817]     ABI class: X.Org Video Driver, version 25.2<br>
    [    27.817] (II) modesetting: Driver for Modesetting Kernel
    Drivers: kms<br>
    [    27.817] (II) FBDEV: driver for framebuffer: fbdev<br>
    [    27.817] (II) VESA: driver for VESA chipsets: vesa<br>
    [    27.817] xf86EnableIO: failed to enable I/O ports 0000-03ff
    (Operation not permitted)<br>
    [    27.817] (II) modeset(0): using drv /dev/dri/card1<br>
    [    27.817] (WW) Falling back to old probe method for fbdev<br>
    [    27.817] (II) Loading sub module "fbdevhw"<br>
    [    27.817] (II) LoadModule: "fbdevhw"<br>
    [    27.817] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so<br>
    [    27.818] (II) Module fbdevhw: vendor="X.Org Foundation"<br>
    [    27.818]     compiled for 1.21.1.15, module version = 0.0.2<br>
    [    27.818]     ABI class: X.Org Video Driver, version 25.2<br>
    [    27.818] (II) modeset(G0): using drv /dev/dri/card0<br>
    [    27.818] (WW) VGA arbiter: cannot open kernel arbiter, no
    multi-card support<br>
    [    27.818] (II) modeset(0): Creating default Display
    subsection in Screen section<br>
        "Default Screen Section" for depth/fbbpp 24/32<br>
    [    27.818] (==) modeset(0): Depth 24, (==) framebuffer bpp 32<br>
    [    27.818] (==) modeset(0): RGB weight 888<br>
    [    27.818] (==) modeset(0): Default visual is TrueColor<br>
    [    27.818] (II) Loading sub module "glamoregl"<br>
    [    27.818] (II) LoadModule: "glamoregl"<br>
    [    27.818] (II) Loading /usr/lib/xorg/modules/libglamoregl.so<br>
    [    27.822] (II) Module glamoregl: vendor="X.Org Foundation"<br>
    [    27.822]     compiled for 1.21.1.15, module version = 1.0.1<br>
    [    27.822]     ABI class: X.Org ANSI C Emulation, version 0.4<br>
    [    27.865] (II) modeset(0): glamor X acceleration enabled on
    Mesa Intel(R) HD Graphics 530 (SKL GT2)<br>
    [    27.865] (II) modeset(0): glamor initialized</font><br>
    </p>
    <blockquote type="cite"
    cite="mid:0464f4f0-82d9-0de4-a375-1cd75e6aa92b@stanis.net">
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">Shouldnt one of intel or nouveau drivers get loaded?
    </pre>
    </blockquote>
    <pre wrap="" class="moz-quote-pre">
    Those actually needed were loaded and remained loaded.</pre>
    </blockquote>
    <p>Ok, it is just confusion on my side. Basically, I did not know
    how the actual graphics stack works, its some years where knew
    more details about how a desktop environment works. Things changed
    a lot it seems since the times where one needed to fiddle around
    with modlines in xorg.conf.</p>
    <blockquote type="cite"
    cite="mid:0464f4f0-82d9-0de4-a375-1cd75e6aa92b@stanis.net">
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">Is there anything "wrong" or is it ok that the fb driver is loaded?
    </pre>
    </blockquote>
    <pre wrap="" class="moz-quote-pre">
    According to inxi, nothing is wrong with anything. (WW) lines in Xorg.0.log are just noise. X normally reports all drivers that could possibly have been required
    that succeeded to load did indeed load, but there should also be corresponding unload messages in the full log for those drivers not actually required.
    # inxi -G | grep Device-1
    Device-1: Intel HD Graphics 630 driver: i915 v: kernel
    # grep -i load /var/log/Xorg.0.log
    [ 10.603] (II) Loader magic: 0x55f3098a9de0
    [ 10.610] (II) LoadModule: "glx"
    [ 10.611] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
    [ 10.616] (II) LoadModule: "intel"
    [ 10.617] (EE) Failed to load module "intel" (module does not exist, 0)
    [ 10.617] (II) LoadModule: "modesetting"
    [ 10.617] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
    [ 10.617] (II) LoadModule: "fbdev"
    [ 10.617] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
    [ 10.618] (II) LoadModule: "vesa"
    [ 10.618] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    [ 10.642] (II) Loading sub module "fbdevhw"
    [ 10.642] (II) LoadModule: "fbdevhw"
    [ 10.642] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
    [ 10.643] (II) Loading sub module "glamoregl"
    [ 10.643] (II) LoadModule: "glamoregl"
    [ 10.643] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
    [ 10.919] (II) Loading sub module "fb"
    [ 10.919] (II) LoadModule: "fb"
    [ 10.919] (II) UnloadModule: "fbdev"
    [ 10.919] (II) Unloading fbdev
    [ 10.919] (II) UnloadSubModule: "fbdevhw"
    [ 10.919] (II) Unloading fbdevhw
    [ 10.919] (II) UnloadModule: "vesa"
    [ 10.919] (II) Unloading vesa
    [ 11.119] (II) AIGLX: Loaded and initialized iris
    [ 11.189] (II) LoadModule: "libinput"
    [ 11.189] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
    #
    </pre>
    </blockquote>
    <p>So, modesetting is the real thing? no need to keep fbdev, vesa,
    intel and nouveau x-server driver packages on the system (as well
    as ati, amd, radeon...)?</p>
    <p><font face="Courier New, Courier, monospace">chris@laptop1:~$
    dpkg -l | grep xserver.*video<br>
    ii  xserver-xorg-video-amdgpu                                  
    23.0.0-1                            amd64        X.Org X server
    -- AMDGPU display driver<br>
    ii  xserver-xorg-video-ati                                     
    1:22.0.0-1                          amd64        X.Org X server
    -- AMD/ATI display driver wrapper<br>
    ii  xserver-xorg-video-fbdev                                   
    1:0.5.0-2                           amd64        X.Org X server
    -- fbdev display driver<br>
    ii  xserver-xorg-video-intel                                   
    2:2.99.917+git20210115-1            amd64        X.Org X server
    -- Intel i8xx, i9xx display driver<br>
    ii  xserver-xorg-video-nouveau                                 
    1:1.0.18-1                          amd64        X.Org X server
    -- Nouveau display driver<br>
    ii  xserver-xorg-video-qxl                                     
    0.1.6-1.1                           amd64        X.Org X server
    -- QXL display driver<br>
    ii  xserver-xorg-video-radeon                                  
    1:22.0.0-1                          amd64        X.Org X server
    -- AMD/ATI Radeon display driver<br>
    ii  xserver-xorg-video-vesa                                    
    1:2.6.0-1                           amd64        X.Org X server
    -- VESA display driver<br>
    ii  xserver-xorg-video-vmware                                  
    1:13.4.0-1                          amd64        X.Org X server
    -- VMware display driver<br>
    chris@laptop1:~$</font><br>
    </p>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)