Mailinglist Archive: opensuse-factory (341 mails)

[Larx <bugzilla@xxxxxxxxxx>]

Hello,

It might be related to a new harddisk I have added to my system, but I can't 
grub make to use the correct vga mode any longer sinced about this time. (I'm 
talking about 64bit openSUSE Factory here.)

Usually my vga mode is 31A, which is as it is defined in YaST and in all grub  
config files I know of. Even the grub output claims that this video mode is 
passed on to the kernel.

However, about two lines later the kernel starts and at once complains that it 
doesn't know what to do with the vga mode 1F. I have to selected the vga mode 
31A manually, then everything boots as expected.

I don't have the slightest idea where this 1F is coming from, I simply can't 
get rid of it!?!??!?!?!?!?

mkinitrd, grub-install, yast2 bootloader with all different places I could 
write the bootloader to - the wrong vga mode 1F stays.

device-map is

hd1 - /dev/disk/by-id/ata-Maxtor (new drive, containing Windows)
hd0 -  /dev/disk/by-id/ata-SAMSUNG (old drive, containing the SuSE 
installation working flawlessly before YaST2 proposed me a new grub config in 
order to boot the new Windows drive, too)

menu.lst entry of the defective section is

title openSUSE 11.2 Alpha 0 - 2.6.27.10-2
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.27.10-2-default root=/dev/disk/by-id/ata-SAMSUNG 
resume=/dev/disk/by-id/ata-SAMSUNG splash=silent showopts vga=31a
    initrd /boot/initrd-2.6.27.10-2-default

/etc/grub.conf reads

setup --stage2=/boot/grub/stage2 --force-lba (hd0) (hd0,0)
setup --stage2=/boot/grub/stage2 --force-lba (hd0,0) (hd0,0)
setup --stage2=/boot/grub/stage2 --force-lba (hd0,0) (hd0,0)
quit

(Why so many  entries?)

One more remark: The  newly added Windows-harddisk already contained a working 
windows partition, so Windows has  not fiddled around with the bootloader, it 
is all YaST2's problem :(.

-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx