Bugzilla – Bug 310115
sax2: modifies grub's menu.lst - why is sax2 modifying a boot loader?!
Last modified: 2007-09-23 22:15:35 UTC
every time i run sax2 and try to finish, it updates /boot/grub/menu.lst and modifies the "vga=" part of my open suse title from "0x31a" to "0x0", so when i reboot next the text is 10 inches tall and looks like pewp. maybe this is because i have chosen to leave in the yast ident comment? regardless, sax2 shouldn't be doing anything to modify a boot loader!!! before sax2: ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd0,0) kernel /boot/vmlinuz-2.6.22.5-10-default root=/dev/disk/by-id/scsi-SATA_WDC_WD2500JB-00WD-WMAEH2470464-part1 vga=0x31a resume=/dev/sda2 splash=verbose showopts initrd /boot/initrd-2.6.22.5-10-default after sax2: ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd0,0) kernel /boot/vmlinuz-2.6.22.5-10-default root=/dev/disk/by-id/scsi-SATA_WDC_WD2500JB-00WD-WMAEH2470464-part1 vga=0x0 resume=/dev/sda2 splash=verbose showopts initrd /boot/initrd-2.6.22.5-10-default
The bootloader needs to be changed for fbdev X driver configurations. You need to set the correct kernel framebuffer (resolution and color depth). Setting it to 0x0 indeed looks like a bug to me. Possibly it is no longer required to configure a # EVGA Corporation:GeForce 7800 GT 10de 0092 3842 c517 still with fbdev. You can check this with "sax2 -r -m 0=nv" to use the nv driver instead. Let me know if this driver works for you and attach /var/log/SaX.log.
like Stefan already said it is required to setup the kernel framebuffer mode if you want to be able to change the resolution in case of a fbdev based X11 configuration I have added a check to the mode value of the grub updater
Thanks, but shouldn't we also figure out, why the framebuffer mode determination didn't work?
I get that information from hwinfo and we need /var/log/SaX.log
no further details
> I get that information from hwinfo and we need /var/log/SaX.log was this comment for me?
Of course. Who else could provide this information?
Created attachment 173917 [details] sax.log sorry, i didn't see any indication that it was tasked back to me. here is the log.
re-opening for now.
in rc1 sax2 was able to write an xorg.conf correctly and any modifications to grub's menu.lst didn't cause any major problems or mess with the size of the text during the bootloader. marking this bug as resolved.