I installed openSUSE 11.3 today, and I after installing a couple of softwares from Yast, I opened it again and applied the patches/updates it had listed, which included a Kernel one too. After the update and restart, it hangs at the progress bar screen just before it is about to finish, after flashing a black screen.
Here is the xorg log I got by going to terminal before it happens, and logging in. Last few lines:
In the future, it is possible to setup YaST to maintain more than one kernel version by doing this:
edit the file /etc/zypp/zypp.conf to say:
##
## Packages which can be installed in different versions at the same time.
##
## Packages are selected either by name, or by provides. In the later case
## the string must start with "provides:" immediately followed by the capability.
##
## Example:
## kernel - just packages whith name 'kernel'
## provides:multiversion(kernel) - all packages providing 'multiversion(kernel)'
## (kenel and kmp packages should do this)
## Valid values:
## Comma separated list of packages.
##
## Default value:
## empty
##
## multiversion = provides:multiversion(kernel)
multiversion = kernel-desktop
This above change modifies YaST for Kernel-Desktop so that instead of bullets, where you select just one version, you get check blocks to keep more than one version (this is on the versions tab in Yast / Software Management). In the above example you would only maintain multiple copies of kernel-desktop. If you use the example setting that is commented out, ALL kernels you load will be multiple version. This works with openSUSE 11.3, but not with openSUSE.11.2, where you must specify each kernel type individually. Using the setting as I show for only kernel-desktop works on many openSUSE versions.
I am reluctant to try any Kernel related recovery, unless I am sure that the problem is caused by the updated kernel. As I mentioned the kernel was one of the updates. In zypp/history, I see updates from libkde4 and xorg among a lot of others.
Is there a way to first know if the hang is caused by Kernel or either kde or X? . BTW I was suggested on the forum to rename .kde folder, but that didn’t fix it.
If you think it is KDE4, the folder would be .kde4. But you can also just create a new user and see if you can log in then. If so, the delete of .kde4 may fix the problem. If you have loaded any other desktops, use the session selection on the bottom left to switch. If a different desktop works, then indeed the problem is with kde. You could go into YaST and reload kde for instance.
Sorry, I meant .kde4 . And it was actually suggested on the irc channel.
I will try the kernel fix. BTW I am using Grub2 not legacy, as I am Multibooting with Ubuntu, and in the setup it didn’t detect the ubuntu installations if I selected to install bootloader. I have added the entry for Suse via probe-os and update-grub in ubuntu. But as I can get to terminal if I press Ctrl + alt + F1 before the system hangs, I guess I can try that first fix. Hopefully it has the image in cache, because I am not on an ethernet based internet connection so it won’t be able to download anything.
It appears that yast needed to download the files after all, but as I had set up my provider and modem broadband modem settings during install and I was using ifup to use internet (Wanted to use Network Manager, but it failed to connect), yast was able to download the older kernel, and I am back on Suse.
Also I noticed before log in prompt in terminal that there was an error reported, which most probably was the time when GUI used to hang up:
Failed Services in userlevel 5 … rng-(something) [in red]
Skipped services in userlevel 5 … something else [in yellow]
It appears that yast needed to download the files after all, but as I had set up my provider and modem broadband modem settings during install and I was using ifup to use internet (Wanted to use Network Manager, but it failed to connect), yast was able to download the older kernel, and I am back on Suse.
Also I noticed before log in prompt in terminal that there was an error reported, which most probably was the time when GUI used to hang up:
Failed Services in userlevel 5 … rng-(something) [in red]
Skipped services in userlevel 5 … something else [in yellow]
So sosaited, what is your status right now? Can you get your GUI to run for any desktop? Does any kernel version load and at least get you to run level 3? When you select a kernel to load, you can add a three at the end of the options (at least for Grub1), where the desktop is not loaded and you could fix the desktop, by running YaST in terminal or reload a video driver, if you have decided to use one of them for ATI or nVidia.