try altering the vetical refresh rate range in the monitor section by incresing or decreasing the second number

I'm just going to back up my stuff and reformat. My problem wasn't fixed, but i learned some stuff.Thanks for helping fraz

just sorry i couldn't be more help

Hoi Fraz and Scriptn00b,

I essentially have the same problem, though I posted it in a different forum. Sofar I've been able to track it down to my videocard driver (an Intel I810), but I have not been able to solve it. It all started when I upgraded my system with yum, which installed updated versions of xorg-x11.

Any suggestions?

Regards,
Regulus

I'm just going to reformat. and as a work around im just not going to update xorg...

well it sounds like there is clearly an issue with the i810 driver.
i have an nvidia card and am using the nvidia driver. in order to use it you have to recompile it every time you eg use a new kernel. perhaps there is a similar issue being caused with this driver. ie an incompatibility with the new version of x.
since you have decided to reinstall anyway maybe changing to fc4 at this point is worthwhile. it may not have the same issue

We are having the same problem with a Dell Latitude D400 that uses the i810 driver. It is hosed since a yum update. We are able to work using the vesa driver but the graphics are horrible at 8 bit depth and a 1024x768 screen resolution. It does appear the i810 drivers are hosed.

Hi flyfishin,

I had the same problem, but managed to reinstall the older, working, version of xorg-x11. The trick is to reinstall all the xorg-x11 rpms. Locate them, copy them into a directory and use rpm -Uvh --force xorg-*.rpm to force rpm to install them.

I got this one from here .

Good luck,
Regulus

I found this solution in the Fedora mail list. Start with some location where you have the xorg rpms from before the update. In our case we used the /var/cache/yum/updates-released/packages directory and found the cached rpms there(They have 45 in the name of the file. The broken ones have 48 in the name). cd into that directory and run this command as root:

rpm -Uvh xorg-X11* --oldpackage

The old X11 packages are installed over the newer X11 packages and all is well again using an i810 driver.

you also might want to add thes packages to yums exclude lists to prevent them being updated again

In order to make this work, you better have to run:

rpm -Uvh xorg-X11*45* --oldpackage

That's the way I did it, and it worked. Otherwise, I got an error message.

Also, check these new beta RPMs from RedHat, they seem to be working for most people.

https://bugzilla.redhat.com/bugzilla....cgi?id=168752

I read that the new xorg has security fixes so maybe dont just exclude them. Does anyone know anything about these xorg security fixes?

I also fell victim of such vicious xorg updates. :P

I use Fedora Core 3 on a genuine Intel Celeron motherboard, with integrated video.

I managed to use the console terminal with the rescue disk, and reupdated the files using yum, from version 45 to 45.1.

Of course, before that, I tried lots and lots of other stuff that may have caused me this new problem - here's the story:

Now, my X works fine, I can log into it, and so far, everything looks just the same. Then I have to go to a console terminal using CTRL + ALT + F1 (which I have to do a LOT, due to the software we use here), and so far, everything looks fine too.

Then I try to return to my X (ALT + F7), and it simply freezes everything. The screen goes blank, the keyboard hangs, I can't return to the consoles to kill any services... and I have to force a hard reset in the machine.

It's not over yet: when rebooting, it asks if I want to do the integrity check, because of the hard reset. Regardless of yes or no, when the X finish loading and should prompt me for login, everything freezes and the screen goes blank again.

And then I have to do a new hard reset. It gets complicated, because it always ask for the integrity check if I do that. To log on into X again, I have to quickly visit the terminal while X is loading, and there log as root, and halt the system.

When I do that, the system shuts down properly, and on the next boot up, it does not ask me for the integrity check again, and the X loads up normally.

Any ideas?

(damn xorg updates - I breaked the number 1 rule of a linux user: if it's working, it does not need a update)

Update:

So it is that this problem only occurs if I use this xorg.conf config:



Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24




If I change the DefaultDepth to 16, I don't have this problem anymore. Weird. I've used 24 since forever. And it looks better too. :P

Anyone out there is using the default depth as 24 and DON'T have my same problem?