I realize using TDE for Mageia 9 on Mageia 10 can't be expected to be perfect, but there is no other option than to wait until built for it, and I've had good success for several releases until 10, starting last September. 10 is now in beta, so should only be some weeks until release. This particular case is on 32bit, so may have nothing to do with software versions other than end of support by Mesa for the Gen2 0x2572 iGPU. The thing is, same PC works just fine with Tumbleweed, KDM3, 6.18.9 and 6.19.6 kernels, and newer Mesa 26.0.1, while 10 has mesa 25.3.6. I'm hoping there is a way to rule out Mageia mesa and X problems prior to release of either 10 or 14.1.6.
# systemctl status tdm ● tdm.service - Trinity Display Manager Loaded: loaded (/usr/lib/systemd/system/tdm.service; enabled; preset: disabled) Active: active (running) since Mon 2026-03-09 12:09:31 EDT; 28min ago Invocation: ff9b163fafed46f5918a23a3befbd915 Docs: man:tdm-trinity(1) Main PID: 958 (tdm) Tasks: 1 (limit: 3525) CPU: 753ms CGroup: /system.slice/tdm.service └─958 /opt/trinity/bin/tdm
Mar 09 12:09:31 gx27c systemd[1]: Started Trinity Display Manager. # dmesg | grep -E 'aile|drm' [ 33.925764] systemd[1]: Starting Load Kernel Module drm... [ 34.604120] ACPI: bus type drm_connector registered [ 34.606161] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 34.606688] systemd[1]: Finished Load Kernel Module drm. [ 38.043169] i915 0000:00:02.0: [drm] Found i865g (device ID 2572) integrated display version 2.00 stepping N/A [ 38.074479] i915 0000:00:02.0: [drm] Initialized overlay support. [ 38.075005] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0 [ 38.123326] fbcon: i915drmfb (fb0) is primary device [ 38.207725] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device [ 40.298561] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2 [ 40.298583] cfg80211: failed to load regulatory.db # tail -18 /var/log/tdm.log X.Org X Server 1.21.1.21 X Protocol Version 11, Revision 0 Current Operating System: Linux gx27c 6.18.16-desktop-1.mga10 #1 SMP PREEMPT_DYNAMIC Wed Mar 4 21:26:12 UTC 2026 i686 Kernel command line: root=LABEL=mga10p19 rw audit=0 ipv6.disable=1 net.ifnames=0 plymouth.enable=0 noresume consoleblank=0 mitigations=off Build ID: x11-server 21.1.21-9.mga10 Current version of pixman: 0.46.4 Before reporting problems, check https://bugs.mageia.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 9 12:14:03 2026 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" MESA: warning: Driver does not support the 0x2572 PCI ID. Mar 9 12:15:03 tdm[958] error: X server startup timeout, terminating Mar 9 12:16:03 tdm[958] info: X server termination timeout, killing Mar 9 12:16:03 tdm[958] error: X server for display :0 can't be started, session disabled # journalctl -b -p3 Mar 09 12:09:25 gx27c rpcbind[593]: cannot create socket for udp6 Mar 09 12:09:25 gx27c rpcbind[593]: cannot create socket for tcp6 Mar 09 12:09:31 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:31 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:31 gx27c rpc.statd[955]: Failed to create listener xprt (statd, 1, udp6) Mar 09 12:09:32 gx27c rpc.statd[955]: Failed to create listener xprt (statd, 1, tcp6) Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol
No such problem in Tumbleweed and KDM3 with 6.18.9 or 6.19.6 kernels: # pinxi -GSaz --vs --za --hostname pinxi 3.3.40-01 (2025-11-25) System: Host: gx27c Kernel: 6.19.6-1-default arch: i686 bits: 32 compiler: gcc v: 15.2.1 clocksource: tsc avail: hpet,acpi_pm parameters: root=/dev/sda10 rw ipv6.disable=1 net.ifnames=0 noresume consoleblank=0 mitigations=off Desktop: KDE v: 3.5.10 tk: Qt v: 3.3.8c wm: kwin with: kicker vt: 7 dm: 1: KDM note: stopped 2: XDM Distro: openSUSE Tumbleweed 20260308 Graphics: Device-1: Intel 82865G Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-2 process: Intel 130nm built: 2002-03 ports: active: VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2572 class-ID: 0300 Display: x11 server: X.Org v: 21.1.21 compositor: kwin driver: X: loaded: intel unloaded: modesetting alternate: fbdev,vesa dri: swrast gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1680x1050 s-dpi: 108 s-size: 395x246mm (15.55x9.69") s-diag: 465mm (18.32") Monitor-1: VGA-1 mapped: VGA1 model: Dell P2213 serial: <filter> built: 2013 res: mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 91 gamma: 1.2 size: 470x300mm (18.5x11.81") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL Message: Unreliable API tool+hardware. Override with --egl. API: OpenGL v: 4.5 vendor: mesa v: 26.0.1 glx-v: 1.4 es-v: 3.2 direct-render: yes renderer: llvmpipe (LLVM 21.1.8 128 bits) device-ID: ffffffff:ffffffff memory: 1.42 GiB unified: yes API: Vulkan v: 1.4.341 layers: 2 device: 0 type: cpu name: llvmpipe (LLVM 21.1.8 128 bits) driver: mesa llvmpipe v: 26.0.1 (LLVM 21.1.8) device-ID: 10005:0000 surfaces: N/A Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo x11: xdriinfo, xdpyinfo, xprop, xrandr # free total used free shared buff/cache available Mem: 1522856 425816 858464 80332 496048 1097040 Swap: 1052220 0 1052220 #
Anno domini 2026 Mon, 9 Mar 13:10:36 -0400 Felix Miata via tde-devels scripsit:
rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol
Might be dure to siabled IPv6, see here:
https://unix.stackexchange.com/questions/454231/rpc-bind-errors-when-disabli...
Nik
Le 09/03/2026 à 18:10, Felix Miata via tde-devels a écrit :
I realize using TDE for Mageia 9 on Mageia 10 can't be expected to be perfect, but there is no other option than to wait until built for it, and I've had good success for several releases until 10, starting last September. 10 is now in beta, so should only be some weeks until release. This particular case is on 32bit, so may have nothing to do with software versions other than end of support by Mesa for the Gen2 0x2572 iGPU. The thing is, same PC works just fine with Tumbleweed, KDM3, 6.18.9 and 6.19.6 kernels, and newer Mesa 26.0.1, while 10 has mesa 25.3.6. I'm hoping there is a way to rule out Mageia mesa and X problems prior to release of either 10 or 14.1.6.
Hello Felix,
Thanks for reporting.
In case this is a software issue, I will (try to) build mga10 packages for i686 and x86_64 and let you know when they are ready.
François
François Andriot composed on 2026-03-10 20:20 (UTC+0100):
Felix Miata a écrit:
I realize using TDE for Mageia 9 on Mageia 10 can't be expected to be perfect, but there is no other option than to wait until built for it, and I've had good success for several releases until 10, starting last September. 10 is now in beta, so should only be some weeks until release. This particular case is on 32bit, so may have nothing to do with software versions other than end of support by Mesa for the Gen2 0x2572 iGPU. The thing is, same PC works just fine with Tumbleweed, KDM3, 6.18.9 and 6.19.6 kernels, and newer Mesa 26.0.1, while 10 has mesa 25.3.6. I'm hoping there is a way to rule out Mageia mesa and X problems prior to release of either 10 or 14.1.6.
Hello Felix,
Thanks for reporting.
In case this is a software issue, I will (try to) build mga10 packages for i686 and x86_64 and let you know when they are ready.
I saw the archive mirror got populated, so I gave it a try on the Gen2 Intel. No help so far, but only 15 rpms got --auto-select updated to versions for 10:
# alias | grep rpm alias rpmqa='rpm -qa | sort | grep $*' alias rpmqf='rpm -qf ' # rpmqa mga9 | wc -l 77 # rpmqa mga10 | grep 14.1.5 libart_lgpl_2-2-2.3.22-14.1.5_1.mga10 libavahi-tqt1-0.6.30-14.1.5_1.mga10 libdbus-1-tqt0-0.9-14.1.5_1.mga10 libdbus-tqt-1-0-0.63-14.1.5_1.mga10 libflac14-1.5.0-4.mga10 libtqt3-mt-3.5.0-14.1.5_1.mga10 libtqt4-4.2.0-14.1.5_1.mga10 trinity-arts-1.5.10-14.1.5_1.mga10 trinity-filesystem-14.1.5-1.mga10 trinity-kcalc-14.1.5-1.mga10 trinity-kdf-14.1.5-1.mga10 trinity-kedit-14.1.5-1.mga10 trinity-kicker-applets-14.1.5-1.mga10 trinity-kmix-14.1.5-1.mga10 trinity-kruler-14.1.5-1.mga10 trinity-ksnapshot-14.1.5-1.mga10 # urpmi trinity-tdebase-bin A requested package cannot be installed: trinity-tdebase-bin-14.1.5-1.mga10.i686 (in order to keep trinity-tdebase-bin-14.1.5-2.mga9.i586) Continue installation anyway? (Y/n) n # Looking at help for urpmi, I recognized nothing that allowed the mass downgrade required to replace all the -2s with -1s, so I built the following to run: # cat g0.sh urpmi --downgrade trinity-kappfinder \ trinity-kate \ trinity-kcontrol \ trinity-kdesktop \ trinity-kfind \ trinity-khelpcenter \ trinity-kicker \ trinity-klipper \ trinity-kmenuedit \ trinity-konqueror \ trinity-konqueror-nsplugins \ trinity-konsole \ trinity-kpager \ trinity-kpersonalizer \ trinity-ksmserver \ trinity-ksplash \ trinity-ksysguard \ trinity-ksysguardd \ trinity-ktip \ trinity-kwrite \ trinity-libkateinterfaces \ trinity-libkonq \ trinity-tdebase \ trinity-tdebase-bin \ trinity-tdebase-data \ trinity-tdebase-libtqt3-integration \ trinity-tdebase-runtime-data-common \ trinity-tdebase-tdeio-pim-plugins \ trinity-tdebase-tdeio-plugins \ trinity-tdebase-tdeio-smb-plugin \ trinity-tdelibs \ trinity-tdepasswd \ trinity-tdeprint \ trinity-tdm \ trinity-twin # Looks like it worked: # rpmqa trinity | grep mga9 # But doesn't seem to have changed anything: /var/log/tdm.log (tail) ... (==) Using system config directory "/usr/share/X11/xorg.conf.d" MESA: warning: Driver does not support the 0x2572 PCI ID. Mar 12 20:04:11 tdm[987] error: X server startup timeout, terminating Mar 12 20:05:12 tdm[987] info: X server termination timeout, killing Mar 12 20:05:12 tdm[987] error: X server for display :0 can't be started, session disabled # journalctl -b | grep drm Mar 12 20:02:02 gx27c systemd[1]: Starting Load Kernel Module drm... Mar 12 20:02:02 gx27c kernel: ACPI: bus type drm_connector registered Mar 12 20:02:03 gx27c systemd[1]: modprobe@drm.service: Deactivated successfully. Mar 12 20:02:03 gx27c systemd[1]: Finished Load Kernel Module drm. Mar 12 20:02:07 gx27c kernel: i915 0000:00:02.0: [drm] Found i865g (device ID 2572) integrated display version 2.00 stepping N/A Mar 12 20:02:07 gx27c kernel: i915 0000:00:02.0: [drm] *ERROR* Initial plane programming using invalid range, dma_addr=0x00000000e954a000 ((null) [0x000000009f800000-0x000000009ffe0000]) Mar 12 20:02:07 gx27c kernel: i915 0000:00:02.0: [drm] Initialized overlay support. Mar 12 20:02:07 gx27c kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0 Mar 12 20:02:07 gx27c kernel: fbcon: i915drmfb (fb0) is primary device Mar 12 20:02:07 gx27c kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device # I'm guessing this is not a TDE problem. :p
# cat /proc/cmdline ... rw audit=0 ipv6.disable=1 net.ifnames=0 plymouth.enable=0 noresume consoleblank=0 mitigations=off vga=791 drm.debug=0x1e log_buf_len=1M # journalctl -b | grep drm | fpaste Uploading (89.3KiB)... https://paste.centos.org/view/1363720c
I just did my first 10 update in over a month due to heart attack, first 10 update since then, and, IIRC, first using 10 repos instead of 9. Still most TDE packages remain mga9 versions, and the TDM greeter doesn't show, just wallpaper on the 0x0 display, while black on the other two, and mouse confined to the 0x0 display. No xorg.conf* is being used.
I just did my second Mageia 10 update in over a month due to heart attack, second 10 update since then, and, IIRC, second using 10 repos instead of 9. No xorg.conf* is being used. I removed most unnecessary addtions in /etc/X11/xorg.conf.d/, keeping only 90-keytable.conf. On this installation, a startup script is placing the three displays in expected locations, but the other script that sets DPI, which I've been using for over a decade, is ignored, with the resulting 96 DPI mousetype I can barely make out. Setting Xft.dpi: 120 fixes it, but this was never before necessary, and doesn't work from my X script set used according to which and how many displays are connected, only via .Xresources (so far).
-
Dr. Nikolaus Klepp -
Felix Miata -
François Andriot