On Friday 02 November 2007 16:54:53 Matt T. wrote: > There was indeed an update, a few weeks ago, IIRC even a security update, > which updated X11, but not the drivers, and stopped X from loading, just > like described here by the OP. Took me half a day of googling and thinking > and sweating to find and solve it. Here is what I remember: > > First of all this seems to be a problem which appeared only with x86_64, > not with the 32 bit version. > > I had xorg-x11-7.2-whatever and the update installed xorg-x11-7.3-whatever. > The update should have pulled in the xorg-x11 driver etc modules for 7.3 > too, because the 7.2 driver modules do not work with xorg-x11-7.3 (I think > that is even mentioned somewhere in the 7.3 sources) > > (The 32 bit versions are for whatever reasons still on 7.2, thus this > problem does not show.) > > So after the upgrade I had a mix of 7.3 and 7.2 > > - xorg-x11-7.3-whatever > - xorg-x11-server-7.3-whatever > - xorg-x11-driver-input-7.2-whatever > - xorg-x11-driver-video-7.2-whatever > - etc. > > and about the same errors as mukul. After upgrading all other xorg-x11 > parts to 7.3 the error disappeared and X came up fine again. > > Now I have all on 7.3.x : > > - xorg-x11-server-7.3-10 > - xorg-x11-7.3-9 > - xorg-x11-driver-video-7.3-12 > - xorg-x11-driver-input-7.3-8 > etc.
Then may I suggest that you remove factory from your installation sources These packages were never released for 10.3, but they are in the factory repository (which is never a safe thing to use, unless you really know what you're doing, and are prepared to do some beta testing for the next version) Anders -- Madness takes its toll -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
