Entropy and Kernel Update today

[nickdanger]

I have been using Sabayon Gnome 4.2 for about two weeks with no major issues, learning as I use it.
Not sure what I did today. The automatic package manger updated Entropy and the Linux Kernel a few minutes ago, and now X server (1.5.3) will not start. The OS version is Linux 2.6.29-sabayon #1 SMP x86_64. There is a configuration problem now, but I have no clue how to fix it. The error codes are:
(ww) fglrx: No matching Device section for instance (BusID PCI:000:17:0)
(ww) fglrx: No matching Device section for instance (BusID PCI:000:18:0)
(ww) fglrx: No matching Device section for instance (BusID PCI:000:18:1)
...
(ww) fglrx: No matching Device section for instance (BusID PCI:000:20:5}
FATAL : Module fglrx not found.
(EE) fglrx(0) : Unknown EDID version 0
(EE) fglrx(0) : atiddxDriScreenInit failed, GPS not been initialized.
(EE) fglrx(0) : FB pci_device_maprange error ! (EE) fglrx(0): Failed to ma

Fatal server error:
AddScreen/ScreenInit failed for driver 0

(EE) fglrx(0): PPLIB: PPLIB is not initialized!.
(EE) fglrx(0): PPLIB: swIPPLibNotifyEventToPPLib( ) failed!


(EE) fglrx(0): firegl_SetSuspendResumeState FAILED -9

Just a nooooby guess, the ATI video driver is not compatible with the new update.
Is there a fix short of buying a InVidia display card?

Thank you very much,
N.D.

[joost]

Did you try reinstalling the driver?

Code: Select all

equo install ati-drivers

then make sure opengl set to ati

Code: Select all

eselect opengl set ati

To be sure, reboot and see if they work.

[nickdanger]

I started in "safe mode" logged in as root, and reloaded the ATI drivers using equo. That went just fine, then I set opengl to the ATi drivers as you suggested. Xserver still refuses to start. I remember when I gave the package manager the OK to download the updates, there was a reference to "miscellaneous X11 files" (or similar). I think that the problem must be int the xorg configuration. I executed the command X -configure from the command line, but it won't complete. I get:

Fatal server error:
Caught signal 11. Server aborting
Aborted

Then The command line returns.

Not sure what that means,
N.D.

[nickdanger]

Just a "shot-in-the-dark," I renamed xorg.conf to xorg.conf.bak and then rebooted. The Xsever started normally and generated a new xorg.conf file. I do not know if the contents of the new xorg.conf are optimal, but it works. I am not recommending this course of action until someone with more experience passes judgment on it. I don't see a lot of posts like my original, so I guess my experience today was unique to my setup or actions.

Thanks for the quick response, especially during a weekend.
N.D.