Help me with X problem!

[hasrin]

Hi,
I don't know where is wrong but its happened when i halt the machine and move it to another place. The Xserver is working properly before that. Now, it can restart the Xserver and i've got this messages at the log file

Aug 7 11:50:32 microsite kernel: mtrr: your processor doesn't support write-combining
Aug 7 11:50:32 microsite kernel: mtrr: your processor doesn't support write-combining
Aug 7 11:50:38 microsite gdm[1765]: gdm_slave_windows_kill_ioerror_handler: Fatal X error - Restarting :0

Anybody can help on how to solve it? Thanks

btw: i'm using redhat 7.1

 

[Guest_imported]

is your screen flashing &, most annoyingly, not letting you type things in except breifly & incompletely at a console? If so then I've had & fixed the same problem.

If not then I'll defer to real guru.

 

[hasrin]

yup.. it is exactly whats happened to me... thanks in advanced

 

[Guest_imported]

distros try & do things for you & wind up doing things to you. don't ask me how but...

I'll bet that one of either your XF86Config or the version for X4 got reset.

Arrrg... I have RedHat 7.1 at home but SuSE at work & the Xconfig is a wee bit different. (I am soooo ditching SuSE) So this is from memory & I can't now look at the EXACT file locations.

1) Either during the blinking process log in as root & then at the console give the magic incantation "init 3" (don't type the quotes). This was annoyingly slow & I'll bet you can just boot into rescue mode directly. What "init 3" does is turn off the X systems.

Now that you're in console mode...

2) either cd into /etc or /etc/X11. I think is was the later on redfat. You are looking for the XF86Config (the v4 name is a bit different) w/o the extension & its nost recent backup. Something like XF86Config.save. -- That is something good about redhat, it does make its own backups.

3) Save your current config files with a ".ithinkitsbroke" extension. Never just delete files like this w/o saving them.

4) copy red's most recent backups to the "real" config file name. That is w/o the extension.

5) either "init 5" to get back into Xwindow mode or if you booted into rescue mode just reboot.

Yup that was it for me. Restoring the X configs from the saves. Simple to do but for me it took a while to figure out.

I'll bet a real guru could figure out a real effcient way to get this done & debugged to boot. Oh well, sucks to be a newbie but I can pass on what little I learned.

 

[Guest_imported]

distros try & do things for you & wind up doing things to you. don't ask me how but...

I'll bet that one of either your XF86Config or the version for X4 got reset.

Arrrg... I have RedHat 7.1 at home but SuSE at work & the Xconfig is a wee bit different. (I am soooo ditching SuSE) So this is from memory & I can't now look at the EXACT file locations.

1) Either during the blinking process log in as root & then at the console give the magic incantation "init 3" (don't type the quotes). This was annoyingly slow & I'll bet you can just boot into rescue mode directly. What "init 3" does is turn off the X systems.

Now that you're in console mode...

2) either cd into /etc or /etc/X11. I think is was the later on redfat. You are looking for the XF86Config (the v4 name is a bit different) w/o the extension & its nost recent backup. Something like XF86Config.save. -- That is something good about redhat, it does make its own backups.

3) Save your current config files with a ".ithinkitsbroke" extension. Never just delete files like this w/o saving them.

4) copy red's most recent backups to the "real" config file name. That is w/o the extension.

5) either "init 5" to get back into Xwindow mode or if you booted into rescue mode just reboot.

Yup that was it for me. Restoring the X configs from the saves. Simple to do but for me it took a while to figure out.

I'll bet a real guru could figure out a real effcient way to get this done & debugged to boot. Oh well, sucks to be a newbie but I can pass on what little I learned.