Other Help Topics :: Problem Upon Reboot

I selected the reboot option from the menu in dsl, upon booting back up I got the following message and am unable to do much of anything.

XIO: Fatal IO error 104(Connection Reset By Peer) on X server "0.0" after 0 requests (0 know processed) with 0 events remaining

I tried using "startx" and "xinit" but I just keep getting the same error. I have run into this problem before and was never able to resolve it so I ended up reinstalling. I would really appreciate it if someone could please tell me how to fix this.

Is there anything listed before that error, such as "no screens found"?

Have you made any changes to X recently? Added or removed nvidia, a window manager, changed resolution, etc? Are you trying to run X as root?

I just reinstalled a few days ago. About all I have done is change to Xfbdev instead of Xvesa because my computer kept locking up, presumably from a memory leak. I also enabled apt-get and I selected synaptic from the menu but it gave me an error and did not finish installing. That is the only problem I have run into since my latest reinstall.

Here is what I get when I boot up:

cloop: Initializing cloop v2.01
init: Entering run level: 5
mount: no medium found
unmount: /cdrom: not mounted
Loading /usr/share/keymaps/i386/qwerty/us.kmap.gz
Using X resolution from previously selected or default settings.
If you want to change the resolution, run 'xsetup.sh'.

It than gives me the error I mentioned in my previous post and leaves me with the following prompt:

dsl@tty1[dsl]$

I am sorry for not providing enough info from the beginning but at this stage I wasnt sure what was needed. I believe this is all the info I have and any help would be appreciated, as I have run into this problem before.

Hmm... Anyone have any ideas. I was hoping to avoid reinstalling, at least not until I found out what caused this.

Usually, it means that you are trying to use the frame buffer server but you did not boot up using a frame buffer.

Typically, this means that you booted with "vga=normal", or it means that you pressed the spacebar after receiving the undefined mode number message at boot-time.

Try typing

xsetup.sh

and choose Xvesa server and then type startx and see if you can get into xwindows again.

Next Page...
original here.