After deleting my Ubuntu partition and using the free space to create a partition for openSUSE with 4GB swap, I installed the OS. The install ran smoothly and it even automatically set up a boot loader for my windows partition.
I logged in to the KDE Desktop. I updated through the Software Updates application, and it prompted me to reboot. When I clicked restart my screen went blank but my computer stayed on without restarting. This lasted over an hour before I decided to force a shut down by holding my CPU’s power button down.
OpenSUSE starts up fine, but after I select the OS from the boot loader the screen goes black twice while loading the KDE desktop. I’m quite new to openSUSE and have never had this problem before with Ubuntu, so I’m just curious if this is all normal? If it isn’t, any suggestions on how to fix the solution would be greatly appreciated.
I also shut down the computer last night, and it didn’t hang at all, so that’s good at least.
EDIT: If it helps, I installed openSUSE via the Live KDE method, on a bootable usb.
I think the first reboot during install is often done with “kernelexec” or something of the sort. The kernel is reloaded without a full boot.
When I installed on my desktop, it hung at that point. I had to power off and reboot. However, once that was done, the normal rebooting has worked fine (I reboot to Windows twice a week, to update virus table ).
On an older laptop, the initial reboot worked just fine. However, since then I must remember to shutdown rather than reboot, for a reboot always fails.
I believe this has to do with the hardware and BIOS support for power settings.
If you don’t, you can still use the atiupgrade script but you would either have to start X ‘somehow’ (for example by using the vesa driver) and run the script twice or initiate a network connection manually in console mode. This is normally not complicated (using ifconfig + route or dhclient). However it seems not to work as expected (as far as I can tell) when the network is configured to use the network manager.
This is a problem. Everyone should be able to connect in runlevel 3. Someone should write a howto explaining how to connect in console mode while using the networmanager - or they should just rewrite the networmanager so that it doesn’t need the GUI - this is not Windows!