Howto: Suse Boots To A Black Screen

Title: X boots to a black screen
Description: Install/Upgrade of software leads to a black screen

http://wiki.suselinuxsupport.de/wikka.php?...stoablackscreen

Post any comments / questions / etc. in here.

Well, a small comment:
The entries are not neccessarily "Linux" and "Failsafe". I would rewrite the HowTo some how like this:
Once at the boot menu, where you can select the operating system to boot, just select the entry for your Linux installation and type in "3".

That's more correct. In addition you do not have to type the name of the boot label, a simple "3" does the job too

Points taken, and corrected ;-)

something else I just noticed, make clear that the command is actually written "sax2" (so lower-case letters) - in your HowTo you wrote it with capital letters .

And it is called Runlevel 3 not init 3... - lol - okay now I stop

No it's ok!

I've always called it init 3 as the command, but I'll do some amends

X config maybe o.k. and one still wil get black screen:
GRUB video options. In this case init 3 will not help either because tt does not matter how X is configured as it is happening before even X will start. Prompt will be still black. What one need is to enter into GRUB options in menu selection: video=normal

The above will not affect correct X config. So GUI will start nice, however if GRUB video options are incorrect, then in case of X configuration from prompt one is screwed.

Point taken - but this is titled X boots...

I don't use grub (lilo fan) so hopefully someone can write a Grub one

Oh, I only wanted to point out that it is good to have video working at all.

No you have a very fair point Broch - only as I don't use Grub I cant talk from experience on it!

I think that this is a solution for some black screens, but not for all. There are a lot of people, like me, that get a black screen when booting X-Window and that cannot even run "sax2", because when running it the result is the same: "black screen", "out of range message" and hang. I posted this problem some time ago, but no solution was found for it.