Geeko no longer shown at boot

This morning, I updated my GRUB config. I reordered some menu items and set openSUSE as default OS.

When I boot into openSUSE, I am no longer greeted by Geeko when openSUSE is loading. I only see text from the boot procedure scroll by like it’s still the 90s. While there’s a certain coolness in seeing openSUSE switch to runlevel 5 and all that jazz, I want my chameleon back.

A few weeks ago, I configured openSUSE to boot with flag vga=0x3ef so that it would boot with my preferred resolution immediately. This used to work fine. Since this morning, openSUSE crashes when X is attempting to start. I can still boot into openSUSE by removing that flag, but even then I still don’t see the chameleon.

How do I get my favorite Linux mascot back?

Do you have


splash=silent

As part of the kernel options in GRUB?

Yes. Here is my value for “Optional Kernel Command Line Parameter”:
resume=/dev/disk/by-id/ata-ST9250410AS_5VG6PVQA-part5 splash=silent quiet showopts

Just guessing here but maybe you could add

vga=0x3ef nomodeset

to the “Optional Kernel Command Line Parameter”. So it would end up like this:

resume=/dev/disk/by-id/ata-ST9250410AS_5VG6PVQA-part5 splash=silent quiet showopts vga=0x3ef nomodeset

The addition of the nomodeset flag allowed me to start openSUSE with a 1600x900 resolution without having X crash at startup, but it doesn’t bring the splash back. I also tried reverting to the proposed GRUB configuration, but that didn’t fix the issue either.

What about removing the

vga=0x3ef nomodeset

options and just adding

vga=791

Just guessing here. It might cause X to crash just like on 0x3ef but it is worth a try

I had tried booting without any VGA flag before creating this thread, but that didn’t restore the splash. I’ll give vga=791 a try though.

Alas… no difference. I’m thinking the GRUB parameters aren’t the culprit here. Are there any logs or config files that I could examine for clues?

If X is crashing with


vga=0x3ef

Then you could look in /var/log/Xorg.0.log for clues

Here’s the difference between a successful X boot and an X boot that ended up hanging the system.

http://www.pieterdedecker.be/tmp/Xorg.0.log
http://www.pieterdedecker.be/tmp/Xorg.0.log.old

These errors seem noteworthy:


18.436] failed to get auxch 0030 40 30 02
18.437] failed to get auxch 0031 40 30 02
18.437] failed to get auxch 0037 40 30 02
18.437] failed to get auxch 0050 40 30 02
18.437] failed to get auxch 0050 40 30 02
18.437] failed to get auxch 0050 40 30 02
18.438] failed to get auxch 0050 40 30 02

18.455] (II) RADEON(0): Not using default mode “640x350” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “320x175” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “640x400” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “320x200” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “720x400” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “360x200” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “320x240” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “640x480” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “320x240” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “640x480” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “320x240” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “640x480” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “320x240” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “800x600” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “400x300” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “400x300” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “800x600” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “400x300” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “800x600” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “400x300” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “800x600” (vrefresh out of range)
18.455] (II) RADEON(0): Not using default mode “400x300” (doublescan mode not supported)
18.455] (II) RADEON(0): Not using default mode “1024x768i” (interlace mode not supported)

I have no experience with the inner workings of X, but it appears that it fails to find a working resolution when I boot with vga=0x3ef which, again, used to work perfectly fine.

Fortunately I can work around this problem by not starting with a custom vga flag, but I do want to get the Geeko splash back. Does sysVinit keep a log that could help diagnose the problem?

So even with the vga= part you still don’t see Geeko?

No, I don’t. I have tried several vga settings and omitting vga entirely as well as booting with nomodeset and no vga flag.

Let us see the menu.lst file.

Hmm… I was trying to make sure that my config wasn’t broken before I posted it, so I did “Start from Scratch” and then “Propose New Configuration” in the boot loader config. All of a sudden, everything went back to normal. I must have messed up somewhere along the way, somehow. Thanks everyone!

Glad its fixed - Enjoy the Geeko! :slight_smile:

Geeko disappeared again. This time, the default boot loader config doesn’t restore the problem. One thing I did notice is that this is shown at boot:

1.192510] pci 0000:01:00.0: no compatible bridge window for [mem 0xfffe0000-0xffffffff pref]

Here’s menu.lst:

Modified by YaST2. Last modification on Mon Jan 17 17:55:41 CET 2011

THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader

Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,5)/boot/message
##YaST - activate

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.3
root (hd0,5)
kernel /boot/vmlinuz-2.6.34.7-0.7-desktop root=/dev/disk/by-id/ata-ST9250410AS_5VG6PVQA-part6 resume=/dev/disk/by-id/ata-ST9250410AS_5VG6PVQA-part5 splash=silent quiet showopts
initrd /boot/initrd-2.6.34.7-0.7-desktop

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.3
root (hd0,5)
kernel /boot/vmlinuz-2.6.34.7-0.7-desktop root=/dev/disk/by-id/ata-ST9250410AS_5VG6PVQA-part6 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
initrd /boot/initrd-2.6.34.7-0.7-desktop

###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,0)
chainloader +1

###Don’t change this comment - YaST2 identifier: Original name: linux###
title Kernel-2.6.34.7-0.7-desktop
root (hd0,5)
kernel /boot/vmlinuz-2.6.34.7-0.7-desktop root=/dev/disk/by-id/ata-ST9250410AS_5VG6PVQA-part6 resume=/dev/disk/by-id/ata-ST9250410AS_5VG6PVQA-part5 splash=silent quiet showopts
initrd /boot/initrd-2.6.34.7-0.7-desktop

Hello? Anyone?