"Jose M. Sanchez" wrote:
> Interrupt the Aurora boot and get to the console.
> Log in or enter the root password, depending on how you got there.
> Then UNINSTALL Aurora.
I do not think this is the Aurora problem. I booted also without using Aurora at
all and the problem persists. I managed however to get Gnome running at one of
the times I rebooted Mandrake. That was after I disabled X start-up at boot (I
booted from CD in rescue mode and edited file responsible for it, commenting out
the lines). However after trying to configure screen saver everything blew up
again.
mike ryder wrote:
> Use the rescue CD to boot the system and then change /etc/inittab so that
> the initdefault is 3 not 5. This will force the system to boot without the
> X-windows stuff.
This I managed to do in different way, (see above)
> Now reboot the server and you should come up with a console login.
When I do just startx -> black screen (I can here my monitor changing its mode).
One could suspected wrongly defined monitor. However when I do
xinit -- kde | gnome // or
startx -- kde | gnome
I get the following error message:
Connection refuse errno (111) unable to connect X server
No such process errno (3) :Server error
> I had this problem when upgrading from MDK 7.1 to MDK 7.2 and it was caused
> by a setting in the X config files that stopped the X server from loading
> correctly and chewed up all of the resources. Problem - I forgot what the
> problem was !! ;-)
While screen is black, it seems like X server or whatever process is really
chewed up all of the resources. The machine does not react on any keyboard
action (event Caps Lock does not work).
I reinstalled MAndrake again and surprisingly the same effect. CAn it be a bug
in Xfree 3.6.X ? Previously I used Xfree 4.X. By the way I have Matrox MGA G200
with 4 MB VRAM.
Any help still appreciated. I am tempted to install Red Hat again.
Declan Moriarty wrote:
> Have you tried piping the output from X to a file to see what the system
> thinks it's doing? If you're starting X from a console, I think the line is
>
> startx >xerrors 2>&1.
That might be a solution. Cheers.
> There's a standard output hidden (like everything in Unix) in some obscure
> file anyhow. It would be interesting to know what problem the system sees
I started to look for one, but at 3 o'clock in the morning I decided to get some
sleep before another working day.
Any help still appreciated.
Thanks for the suggestions already sent.
Darek
