X-Server doesn't start anymore

After the installation of Suse 10.0 I changed the graphic seetings in Yast
because the resolution and the number of colors were not set correctly.
Unfortunately the test of the new seetings failed and therefor I reeboted
the system. Since that the system did not succede in starting the x-server,
the KDE respectively.

The /var/log/warn sais:
Io Error in XopenDisplay
X server for display :0 terminated unexspectedly
Display cannot be opened
Unable to fire up local display ; disabling

1. Does anybody know where the mistake is and how to solve it?
2. Does anybody believe that this problem is not connectd with the changes
of the graphic seetings

simon@adon.li adjusted his/her tinfoil beanie to post:

> After the installation of Suse 10.0 I changed the graphic seetings in
> Yast because the resolution and the number of colors were not set
> correctly. Unfortunately the test of the new seetings failed and
> therefor I reeboted the system. Since that the system did not succede
> in starting the x-server, the KDE respectively.
>
> The /var/log/warn sais:
> Io Error in XopenDisplay
> X server for display :0 terminated unexspectedly
> Display cannot be opened
> Unable to fire up local display ; disabling
>
> 1. Does anybody know where the mistake is and how to solve it?

Don`t know what might be causing it but when you boot type "init 3"
without quotes at the boot screen, the one that has the countdown
marker ( you might have to press the F2 or F3 key to get the command
line up on the screen )

The machine will then boot to a terminal, login as root and enter root
pass.

next run

sax2


And re-configure your card and monitor again, make sure you *test*
before you save hopefully that should get it going again, to bring up X
just type "init 5"


> 2. Does anybody believe that this problem is not connectd with the
> changes of the graphic seetings

Not at the moment no :-)

If this does not work then holler back with any more errors that you
might find in /var/log/messages or xorg.log

HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

baskitcaise wrote:
> simon@adon.li adjusted his/her tinfoil beanie to post:
>
>> After the installation of Suse 10.0 I changed the graphic seetings in
>> Yast because the resolution and the number of colors were not set
>> correctly. Unfortunately the test of the new seetings failed and
>> therefor I reeboted the system. Since that the system did not succede
>> in starting the x-server, the KDE respectively.
>>
>> The /var/log/warn sais:
>> Io Error in XopenDisplay
>> X server for display :0 terminated unexspectedly
>> Display cannot be opened
>> Unable to fire up local display ; disabling
>>
>> 1. Does anybody know where the mistake is and how to solve it?
>
> Don`t know what might be causing it but when you boot type "init 3"
> without quotes at the boot screen, the one that has the countdown
> marker ( you might have to press the F2 or F3 key to get the command
> line up on the screen )
>
> The machine will then boot to a terminal, login as root and enter root
> pass.
>
> next run
>
> sax2
>
>
> And re-configure your card and monitor again, make sure you *test*
> before you save hopefully that should get it going again, to bring up X
> just type "init 5"
>
>
>> 2. Does anybody believe that this problem is not connectd with the
>> changes of the graphic seetings
>
> Not at the moment no :-)
>
> If this does not work then holler back with any more errors that you
> might find in /var/log/messages or xorg.log
>
> HTH

There's a problem in the SaX2 test environment which has bitten me twice
now. (Yes, I'm having fun, thank you.) I have an nVIDIA card in an IBM
ThinkPad G41. After loading the binary update from nvidia, I ran SaX2,
and got to the test. Problem is, I had specified the nvidia agp, which
is incompatible with agpgart, so the test crashed. When I rebooted,
however, the new driver was in place, with very strange settings. I had
to go through the process again.

Simon seems to have had a similar experience. He ran the test and it
seems to have crashed.

Simon, your log will be in Xorg.0.log in /var/log if it's required.

Peter