I’ve just installed OpenSUSE 11.0 second time on the same machine and everything works just fine including Compiz except that it boots into tty1 mode even though default run level is 5 ( id:5:initdefault: ) After first installation it was booting in graphical mode.
Many thanks in advance, any help is greatly appreciated. - Jags
At OpenSUSE login / System boot it says following:
Master Resource Control: runlevel 2 has been
Wlcome to OpenSUSE 11.0 (i586) - kernel 2.6.25.5-1.1-pae (tty1)
OpenSUSE login:
Yast, System, System Services, F7: What’s the default runlevel set to?
Uwe
hi ‘buckesfeld’
Many thanks for the reply.
YaST > System > System Services (Runlevel) > Expert Mode >
Set default runlevel after booting to: 5: Full multiuser with network and display manager
I guess that’s what you asked for…
that looks okay. You could try setting it hence and forth to see if it helps.
When you boot, on the grub screen: Do you have an option “2” or “init 2” set?
Once you are in runlevel 2, what happens if you login as root and issue a “init 5”?
Uwe
hi buckesfeld
You could try setting it hence and forth to see if it helps.
I tried YaST > System > System Services (Runlevel) > Expert Mode > Changed to Runlevel 3 > Restarts > it boots in Runlevel 2 > changed it back again to Runlevel 5 > Restarts > and it still boots into runlevel 2 (tty1)
on the grub screen: Do you have an option “2” or “init 2” set?
No I don’t have that option. At the Grub screen I have following options available:
1, OpenSUSE 11.0 (i586) - kernel 2.6.25.5-1.1-pae
2, OpenSUSE Failsafe
3, Windows
Once you are in runlevel 2, what happens if you login as root and issue a “init 5”?
When I enter init 5, it says switching runlevel and graphical interface kicks in and I have to re-login as a root / regular user. (I have only GNOME installed and in graphical log-in I selected GNOME under the session tab)
In last 6 months or so I have installed OpenSUSE 11 Alphas, Betas and nightly builds like 25+ times and I never ever had this Runlevel problem ever(same machine all the time and with GNOME). I guess format & re-install would be the only option available or what…
Many thanks for your replies. - Jags
no errors anywhere? (Alt Ctrl F10, e.g.?)
Can you please post the content of your /boot/grub/menu.lst?
Uwe
ok here’s the /boot/grub/menu.lst :
:::::::::::
default 0
timeout 15
gfxmenu (hd0,3)/boot/message
##YaST - activate
###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.0 - 2.6.25.5-1.1
root (hd0,3)
kernel /boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_WDC_WD800AB-22CWD-WMAA51925700-part4 2 resume=/dev/sda3 splash=silent showopts vga=0x31a
initrd /boot/initrd-2.6.25.5-1.1-pae
###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.0 - 2.6.25.5-1.1
root (hd0,3)
kernel /boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_WDC_WD800AB-22CWD-WMAA51925700-part4 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x31a
initrd /boot/initrd-2.6.25.5-1.1-pae
###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,3)
chainloader (hd0,0)+1
:::::::::::
no errors anywhere? (Alt Ctrl F10, e.g.?)
I’m sorry but I didn’t get that part… At the system boot when I hit Alt+Ctrl+f10 it quickly ran few things and the last line was something like Susefirewall2 not activated… But then it was kinda froze so I had to Ctrl+Alt+Delete to reboot.
Thanks again, - Jags
Jags FL schrieb:
> I guess format & re-install would be the only option
> available or what…
Certainly not. Your system boots, after all. Everything else can be sorted out … 
> ok here’s the /boot/grub/menu.lst :
…]
Unfortunately line-wrapped, but I think I can sort it out:
> ###Don’t change this comment - YaST2 identifier: Original name: linux###
> title openSUSE 11.0 - 2.6.25.5-1.1
> root (hd0,3)
> kernel /boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_WDC_WD800AB-22CWD-WMAA51925700-part4 2 resume=/dev/sda3 splash=silent showopts vga=0x31a
A-ha! There we have the culprit. See the “2” before the “resume” parameter?
That’s telling your system to come up in runlevel 2 instead of the default
runlevel. I wonder where that comes from. Remove it (with YaST bootloader
configuration or your favorite text editor) and your problem will be gone.
>> no errors anywhere? (Alt Ctrl F10, e.g.?)
>
> I’m sorry but I didn’t get that part… At the system boot when I hit
> Alt+Ctrl+f10 it quickly ran few things and the last line was something
> like Susefirewall2 not activated… But then it was kinda froze so I
> had to Ctrl+Alt+Delete to reboot.
You didn’t have to. It isn’t frozen, it just doesn’t accept any keyboard
input. Console 10 is an output only console for syslog messages. You can
just leave it by switching to a different console, for example by
Alt+Ctrl+F1 (for the first text console) or Alt+Ctrl+F7 (for the
X display provided X is running.)
HTH
T.
On 07/01/2008 Jags FL wrote:
> root=/dev/disk/by-id/scsi-SATA_WDC_WD800AB-22CWD-WMAA51925700-part4 2
HA!
SCNR, else what Tilman said 
Uwe
Tilman Schmidt and buckesfeld
You guys Rocks
I removed that ‘2’ from /boot/grub/menu.lst and voila and OpenSUSE 11.0 booted in Runlevel 5 (guess I would never know where that 2 came from as it never happened on the same machine during numerous previous installations)
Ok I have side question about what happened before I read Tilman’s post, please. After the failed installation of daily build for Ubuntu 8.10 when I tried to boot OpenSUSE 11.0 it gave me some sort of ‘Hard Drive Inconsistancy Error’ for the second hard drive and said to run ‘fsck manually’ (OpenSUSE 11.0 is installed on first HD). Which I ran but ultimately it lead to nowhere.
So I booted the system with ‘Parted Magic’ and formatted the partition I was installing Ubuntu on as EXT3 and voila OpenSUSE 11.0 was working back again like nothing happened.
So my question is what is with ‘Unreadable’ second hard drive when the OS partition, Swap partition and MBR is on the first HD ? I was thinking at the most it would not read the filesystem on the second HD (I had same thing happened once in Fedora 8 and Ubuntu 8.04 too)
Thanks a million guys for your help, I greatly appreciated it.
> So my question is what is with ‘Unreadable’ second hard drive when the
> OS partition, Swap partition and MBR is on the first HD ? I was
> thinking at the most it would not read the filesystem on the second HD
> (I had same thing happened once in Fedora 8 and Ubuntu 8.04 too)
Good question for the Ubuntu forums 
(Sorry, really I got no idea)
> Thanks a million guys for your help, I greatly appreciated it.
You’re welcome!
Uwe
Jags FL schrieb:
> Tilman Schmidt and buckesfeld
>
> You guys Rocks
Thanks for the flowers. Of course Uwe’s idea to ask four your menu.lst
was the decisive one. Once you posted that, the extra “2” really stuck
out like the proverbial sore thumb.
> Ok I have side question about what happened before I read Tilman’s
> post, please. After the failed installation of daily build for Ubuntu
> 8.10 when I tried to boot OpenSUSE 11.0 it gave me some sort of ‘Hard
> Drive Inconsistancy Error’ for the second hard drive and said to run
> ‘fsck manually’ (OpenSUSE 11.0 is installed on first HD). Which I ran
> but ultimately it lead to nowhere.
>
> So I booted the system with ‘Parted Magic’ and formatted the partition
> I was installing Ubuntu on as EXT3 and voila OpenSUSE 11.0 was working
> back again like nothing happened.
>
> So my question is what is with ‘Unreadable’ second hard drive when the
> OS partition, Swap partition and MBR is on the first HD ? I was
> thinking at the most it would not read the filesystem on the second HD
> (I had same thing happened once in Fedora 8 and Ubuntu 8.04 too)
Difficult to tell without seeing the exact error messages and contents
of your /etc/fstab file, but I would guess that openSUSE tried to
detect the partitions your second disk automatically just in case
(it does that sort of things) and the failed Ubuntu installation left
some sort of half-written filesystem there. You could probably have
formatted the partition from openSUSE just as well.