I’ve just download the latest updates (twice) for 4.2 and am now unable to boot into it
The message I get is
Master Resource Control in runleve 5 has been skipped services in run level 5
So I googled and came up with that I should type in init 5, which I did, no errors. Then I tried sax2 -r -m O=vesa, which didn’t fix the problem
Any ideas?
caf4926
December 31, 2008, 5:34am
#2
I have just updated too. With no problem.
I don’t think this a graphics issue (vesa)
Did you reach level 5 and type startx
?
ok startx gets me into KDE
The screen is completely out of whack, not taking up the full screen, the panel is only taking up half the width of the bottom screen, I have no reboot or shut down options, just a logout option, and I have to use startx each time to get into KDE, and it is incredibly sluggish.
caf4926
December 31, 2008, 5:50am
#4
You just ran a command to switch your graphics to VESA!
You need to run sax2 outside the graphical env. Boot to runlevel 3, login and go su, then do sax2 -r
(or check for your particular video card etc)
caf4926
December 31, 2008, 5:52am
#5
Not too sure about all your buttons being missing
You may have to start with a new .kde4 folder
(mv /home/*username/.kde4 .kde4old) from a CLI
reboot
hi, thanks for you help
What do I have to do to stop having to write startx each time?
started a new kde4 folder, but still no logout or reboot button, but that isn’t a biggie
caf4926
December 31, 2008, 6:41am
#7
AlienHealer:
hi, thanks for you help
What do I have to do to stop having to write startx each time?
started a new kde4 folder, but still no logout or reboot button, but that isn’t a biggie
I had to add those button on my upgrade to 4.2
Post your /boot/grub/menu.lst
is this what you want?
Modified by YaST2. Last modification on Wed Dec 31 19:21:32 NZDT 2008
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.1
root (hd0,5)
kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-ST3160815A$
initrd /boot/initrd-2.6.27.7-9-default
###Don ’t change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
rootnoverify (hd0,0)
chainloader +1
###Don ’t change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
rootnoverify (hd0,1)
chainloader +1
###Don ’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.1
root (hd0,5)
kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-ST3160815A$
initrd /boot/initrd-2.6.27.7-9-default
caf4926
December 31, 2008, 7:47am
#9
AlienHealer:
is this what you want?
Modified by YaST2. Last modification on Wed Dec 31 19:21:32 NZDT 2008
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.1
root (hd0,5)
kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-ST3160815A$
resume=/dev/disk/by-id/ata-ST3160815A$ splash=silent showopts vga=0x367
initrd /boot/initrd-2.6.27.7-9-default
###Don ’t change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
rootnoverify (hd0,0)
chainloader +1
###Don ’t change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
rootnoverify (hd0,1)
chainloader +1
###Don ’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.1
root (hd0,5)
kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-ST3160815A$
initrd /boot/initrd-2.6.27.7-9-default
First look to see if there is a menu.lst.old in the /boot/grub/ - location you can open with kwrite
It may have the correct info for you, the kernel MAY be different, so watch for that.
I edited your menu as above (blue/red)
RED* vga= will be different to what I quote, your old menu file may have that, otherwise find out what it should be, depends on your resolution screen size.
ok, have done that, but am still having to use startx to get in
caf4926
December 31, 2008, 9:17am
#11
You didn’t say if you found the menu.lst.old or if you had made changes yourself it would be menu.lst~
green color
yeah I found the menu.lst.old and tried that as well, still same problem.
I think I might drop back to 4.1.3 until the next release.
It has to be something in the KDE update, because I reinstalled, just upgraded KDE 4.2, rebooted, and the same thing happened.