Source: debian-installer Version: 20230607+deb12u6 Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me
Thank-you to Philip for pointing me to the OpenQA assets and details. I had explored those pages but totally missed that those words were actually hyperlinks to additional page content! Thanks also to Cyril for pointing me to the daily-image archives - very useful. My workstation is Bookworm amd64 with qemu 1:7.2+dfsg-7+deb12u6 >From snapshots I fetched and installed 1:7.2+dfsg-7+deb12u5 $ kvm --version QEMU emulator version 7.2.9 (Debian 1:7.2+dfsg-7+deb12u5) Good: gtk/mini.20240628.iso Fail: gtk/mini.20240629.iso So in all likelyhood we can rule out Qemu as a cause here (but still keep it in mind). I've looked at the upstream qemu commit history v7.2.9..v7.2.11 and do not see anything obviously touching on QXL (so far - will continue looking). Back to the 2 ISOs. Comparing the build logs nothing stands out aside from the kernel version 6.8.12 -> 6.9.7 although: debian-installer git tree head: 0cf307b35662c758828f12977d286edf2cb86f59 -> c0030a2713385804a392ff9d3ae46d9301373ce4 I now move on to executing the guests with serial console so I can capture the logs. $ kvm -m 1G -vga qxl -serial stdio -cdrom ... I interrupt the isolinux boot menu pressing Tab to edit it. I change it to begin: linux init=/bin/sh console=ttyS0,115200 console=tty0 ... To capture the kernel log: # dmesg > /dev/ttyS0 To capture Xorg log: # Xorg -logverbose 9 -logfile /dev/ttyS0 This reveals the Xorg fbdev driver is unable to manage the framebuffer /dev/fb0. $ diff <(grep -o ') .*' xorg-20240628.log ) <( grep -o ') .*' xorg-20240629.log ) 21d20 < ) FBDEV(2): using default device 27,40c26,29 < ) FBDEV(0): Creating default Display subsection in Screen section < ) FBDEV(0): Depth 16, (==) framebuffer bpp 16 < ) FBDEV(0): RGB weight 565 < ) FBDEV(0): Default visual is TrueColor < ) FBDEV(0): hardware: VESA VGA (video memory: 1875kB) < ) xf86MergeOutputClassOptions unsupported bus type 0 < ) FBDEV(0): checking modes against framebuffer device... < ) FBDEV(0): checking modes against monitor... < ) FBDEV(0): Virtual size is 800x600 (pitch 800) < ) FBDEV(0): Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz < ) FBDEV(0): Modeline "current"x0.0 48.00 800 832 928 1024 600 604 608 624 -hsync -vsync -csync (46.9 kHz b) < ) FBDEV(0): DPI set to (96, 96) < ) Loading sub module "fb" < ) LoadModule: "fb" --- > ) Device(s) detected, but none match those in the config file. > ) no screens found(EE) > ) Please also check the log file at "/dev/ttyS0" for additional information. > ) Server terminated with error (1). Closing log file. The key here is that first line which shows that 20240628 manages to open /dev/fb0 but 20240629 does not. This suggests we're back to considering a kernel change. I'm now inspecting the framebuffer related changes between v6.8..v6.9 and will likely do some git bisect kernel builds to test likely culprits.
