Bug #1011: Installed x86_64 systems stay on fbdev: the old forced xorg.conf survives upgrades

Closed assigned to pankso, opened 2026-10-21 23:53 UTC, updated 2026-10-22 22:30 UTC

The x86_64 ISOs built from flavors r305 to r356 (2026-07-19 to 2026-10-19:
core-x86_64, firefox-x86_64, gtkonly-x86_64) shipped /etc/X11/xorg.conf
forcing Driver "fbdev" (first line "# UEFI live: efifb + fbdev...").
The installer copies it to the disk, no package owns it, so upgrades keep
it. tazx video (run by the slim and lxtaz-dm init scripts) steps aside
when a Device section exists, so these systems stay on fbdev even with a
KMS driver bound and modesetting installed. Flavors r381 fixed new ISOs
only.

Seen on: Atom D525 GMA3150 (reports 23-24), Celeron N3450 (report 16),
and a dev VivoBook (i915).

Fix, in progress:
- slitaz-tools tazx video: set the file aside when its md5 matches
  exactly (an edited file is kept), then write 20-Video.conf with
  modesetting. Waiting for a modesetting test on a real machine.
- reprise r43: when the tazx-generated modesetting setup makes Xorg die,
  fall back to fbdev, never to the driver that just failed; fixes DB
  entry xorg-modesetting-failed (repair=xorg-safe fbdev).

To keep fbdev on purpose: edit /etc/X11/xorg.conf, or put a Device
section in /etc/X11/xorg.conf.d.

History