No not a kernel. I was having problems with the power management, the screen kept locking and dulling, it’s always happened, so I used YAST and updated anything that was to do with powersave and the screen that were in blue and when asking for updates had no conflicts. All ok till re-boot.
When it’s working - leave alone - a lesson learnt again.
I can’t help with the xwindow problem but with the bootloader: you need to reinstall Grub using Yast to recalculate the entries for Grub’s menu. Do this after booting into openSUSE:
go to Yast –> System –> Boot Loader. The Grub configuration screen comes up with the Tab “Section Management” activated. In the lower right is a drop-down selector labelled “Other”. Select from “Other” the option “Propose New Configuration” and then wait for Grub to analyse your partitions and display a new configuration. This may take a while. Important: When that finishes, activate the tab labelled “Boot Loader Installation” and select to “Boot from the Master Boot Record”. [Yast will often default to booting from the root or boot partition rather than from the MBR but that’s for experts only – always choose the MBR.] Then click Finish to save the changes and install the reconfigured Grub into the hard drive’s MBR. If you get a message that "The bootloader boot sector will be written to a floppy disk … don’t bother with the floppy – just click OK to proceed and install to the MBR. Reboot and you should be able to boot to openSUSE using the Grub menu screen.
The new Grub menu should contain an entry for vista. If that entry has problems, make sure it looks like this in menu.lst:
title Windows bootloader menu
rootnoverify (hdx,y)
chainloader (hdx,y)+1
where x,y is most often 0,0 for vista on the first partition. If puzzled, post here the menu.lst entry that you find for vista together with the return you get in a terminal when you enter this command:
Windows . Suse 11.1 and 11.1 safe mode and another entry like a kernel.
Suse 11.1 boots up but only goes as far as the text login screen. does not pick up the Xwindow or KDE3.5? but safe mode does. I will just log out and check if windows is working?
Though more important to get this KDE3.5 working from the text log in screen.
That’s one of the cases where the manufacturer puts a utility partition first up on the drive (sad1) and then the bootloader goes sometimes into sda1 and sometimes into sda2. So it might be one of two possibilities. But before I go on, what does the file menu.lst contain after you made the new bootloader as per my first post? To open the bootloader’s menu file and look at it, run this command:
in KDE it’s: kdesu kwrite /boot/grub/menu.lst
in Gnome it’s: gnomesu gedit /boot/grub/menu.lst
all with text
then fatal error
caught signal 11 server aborting
giving up
xinit: connection refused (errno11): unable to connect to X server
xinit: No such process (errno 3) server error
then the login text
I can type out the backtrace lines 0 to 9 if of any use?