search for: forcevesa

Hello, Long story short, example config: ### cut UI vesamenu.c32 MENU TITLE Multiboot USB MENU BACKGROUND #00000000 MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all MENU COLOR unsel 37;44 #50ffffff #a0000000 std MENU COLOR tabmsg 31;40 #30ffffff #00000000 std MENU BEGIN MENU TITLE System Rescue CD 2.4.1 INCLUDE sysrcd-2.4.1.conf MENU END MENU BEGIN MENU TITLE

...en_US bootkbd=us console-setup/layoutcode=us vga=791 -- label text menu label Start BackBox in Text Mode kernel /backbox-2.05-32bit/vmlinuz append initrd=/backbox-2.05-32bit/initrd.gz file=/cdrom/preseed/backbox.seed boot=casper live-media-path=/backbox-2.05-32bit quiet text vga=791 -- label xforcevesa menu label Start BackBox in Compatibility Mode kernel /backbox-2.05-32bit/vmlinuz append initrd=/backbox-2.05-32bit/initrd.gz file=/cdrom/preseed/backbox.seed boot=casper live-media-path=/backbox-2.05-32bit xforcevesa ramdisk_size=1048576 root=/dev/ram rw noapic noapci nosplash irqpoll -- lab...

...ers on the ubuntu 19.04 live CD and the System Rescue CD 6.0.3 produce the same "bad signal" errors on this monitor. For details (like X log files) see: https://bugzilla.redhat.com/show_bug.cgi?id=1575391 and https://bugzilla.redhat.com/show_bug.cgi?id=1648608 If I add nomodeset and forcevesa kernel parameters, I can boot and see (lower resolution) video rather than a black screen. Switching to the nvidia binary drivers makes the display work properly again. Booting the USB stick on different systems with more conventional resolution monitors, nouveau works fine. -- You are receivin...