strange boot order problem

Hi
I’ve encountered a strange problem.
I did a fresh install of OpenSuse 11 today, from the DVD.
And now the default kernel, fails to load.
After I see the screen blinking a few times I see many things being loaded but all I get is a command prompt.

The thing is, if I select the one above it, it will load properly.
Since I can’t take a screenshot of anything before it’s booted, I’ll show you what the boot loader configuration shows me.

http://xxlimg.com/images/cfqjm0ss3dsmbkre1qp_thumb.jpg](http://xxlimg.com/viewer.php?file=cfqjm0ss3dsmbkre1qp.jpg) (hmm that thumbnail appears empty, but I assure you there’s an image on the other side of it)

As you can see, there are 3 different options for Suse.
(why the others only show windows 1 and windows 2 is beyond me since one is a backup partition while the other is vista, but that’s besides the point as vista loads well enough)

Anyway, the top one, labeled “Trace” is the one that loads perfectly
The one that’s now set as default, however, does not.
I have not tried the fail safe.
But as I said, I only get a command prompt with the default option.
And I have no experience with Linux so I wouldn’t know what command to give to log in or reboot.
This leaves me with the option to simply push the button on my tower (not something I prefer :slight_smile: )

Like I said, the top one works and I have now set it to default, but can anyone tell me why this happened?
Did I do something wrong during install?
Because I followed one of the tutorials on here as the install process was a bit more elaborate then that of Ubuntu (or windows for that matter)

These look like 2 different kernel versions (Trace and failsafe are 2.6.27.19.xx and the selected one 2.6.27.7.xx). Choose which one you want and boot into it - probably the trace image. The middle one is probably your backup image.
When you install suse, it checks your system and adds the other operating systems and adds them to the bootloader. This means that if, say, you installed ubuntu on a separate partition and then installed suse to another, the bootloader would let you choose which to boot into. Likewise with your windows.
To login at the command prompt type your user name, hit enter. It will now ask for the password. Enter this (you won’t see anything when you type it), press enter. If username/pwd are correct you will be logged in.
If you are new to linux, try looking at some of the how-tos (yast will let you install them on your system as text,pdf or html.)

actually trace is the only 2.6.27.19
the failsafe is also 2.6.27.7.
The reason I find it strange is because I thought the failsafe should’ve been of the same kernel.
I thought the failsafe is similar to windows’ safe mode.
But if that’s the case, shouldn’t it be the same, newer, kernel?

As for that command prompt, the thing about that is it does indeed ask for my username and password.
But then still waits for a command.
I can login in as root as well with sudo -s.
I just don’t know what else I should be doing with it. Meaning, if I should be able to go to my desktop, I wouldn’t know how.
I’ll look at some of those how to’s though, maybe I can find something there.

2.6.27.19-3.2 is the latest kernel version. It looks like you installed the latest kernel only for the trace variety. According the package description it is the real-time kernel, who knows how you selected it to be installed. Anyway you can update the other kernel varieties to the latest version also using YaST online update.