PDA

View Full Version : Broken X on first update Fedora 10


BobNutfield
2nd October 2008, 09:05 AM
Hello Everyone,

Had a disaster yesterday trying to install F10 to a spare partition on my laptop. I will accept that it is probably my fault, but I damaged all of the other partitions. After selecting custom partitioning, F10 attempted to install to the entire drive. It was instaneous that I noticed what was happening and immediately cancelled the process, but it was too late. Oh well. Fortunately, I had good backups of all of my important files.

I took the opportunity to go ahead and install anyway after repartitioning my disk. I loved it. The new Gnome is terrific, and I now have native support for my wireless. No more ndiswrapper! Very buggy, as I would expect an Alpha release to be, but not too bad. My touchpad also worked immediately, though erratic, but that was something it took me ages to fix in F9. I like it so much that I decided I would leave it on the first partition and boot the other distros from Fedora's grub.

But now, the problem. Just as I expected, there were 321 updates waiting. It took the better part of two hours to download and install. My original download of F10 had kernel 2.6.27-0.352.rc7, the update installed kernel 2.6.27-0.372.rc8. Things were looking good. But upon reboot, X would not start, complaining about connection refused. So, I did what I would have done in all distros, looked for a backup of xorg.conf in /etc/X11/xorg.conf, only to find it was not there. I found a lot of xorg files in /usr/lib. but no xorg.conf. I figured this was a download gone bad, and just reinstalled. Same 321 updates waiting. Same result after rebooting, and a third rre-install. Broken X.

So, I have two questions for someone who may be able to help me save my installation:

1. I have re-installed again, but not updated. What could have been in the updates that continues to break X? It is not a kernel issue, as I get the same broken X in trying to boot from the original kernel.

2. Where is the xorg.conf file in F10? I have read the release notes, but find nothing about it.

Any help very much appreciated.

Bob

Demz
2nd October 2008, 09:25 AM
your better to post to Fedora Devel list than post here,you may get faster reply, but someone might know how to fix your problem here

BobNutfield
2nd October 2008, 09:31 AM

OK, thank you for your reply. Can't seem to find the developer list. Do you have a link? In case anyone here can help, the only part of the updates that concern xorg is this:

xkeyboard-config.noarch 1.3-2.fc10 rawhide
xorg-x11-drv-ati.i386 6.9.0-20.fc10 rawhide
xorg-x11-drv-nv.i386 2.1.12-5.fc10 rawhide
xorg-x11-drv-synaptics.i386 0.15.2-1.fc10 rawhide
xorg-x11-server-Xorg.i386 1.5.1-4.fc10 rawhide
xorg-x11-server-common.i386

Nothing harmfull-looking here.

Demz
2nd October 2008, 09:47 AM
yeah the devel list is in my signature noted as fedora test list

BLooDMaN
2nd October 2008, 08:34 PM
I've the same problem exactly after update.
I've found that starting x from console has the following error:
/usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers//intel_drv.so: indefined symbol: intel_bufmgr_gem_init

I suppose problem is because of double slash.
I'll try to find something at "fedora test".

vallimar
2nd October 2008, 08:46 PM
AFAIK, Fedora 10 is to ship without an xorg.conf file, instead using the newer evdev and hal subsystems to rely solely on polling for configuration. To generate a config file based on what it will run with as probed, you can (as root) do: Xorg -configure. Then modify away.

The intel driver has been in some flux, I don't have one so haven't been following it, but they probably just released it broken, not much of a surprise. Try using vesa instead for X until they sort it out.

daf1983
2nd October 2008, 08:48 PM
another way is to open system-config-display and just click on 'Ok'. it'll generate a classic xorg.conf

vallimar
2nd October 2008, 08:49 PM
I've the same problem exactly after update.
I've found that starting x from console has the following error:


I suppose problem is because of double slash.
I'll try to find something at "fedora test".
The double-slash has nothing to do with it, all the X module paths are like that, just sloppiness on the maintainers part, nothing more. As I said above, it's just the standard RedHat/Fedora screwup leftover from a bunch of intel changes and backouts and them not testing anything themselves.

BLooDMaN
2nd October 2008, 09:12 PM
another way is to open system-config-display and just click on 'Ok'. it'll generate a classic xorg.conf

Tried this one, not helped, got error:

Couldn't start X server on card 0
Couldn't start X server with old config, trying with a fresh configuration
Couldn't start X server on card 0
Error, failed to start X server.

Also tried to change driver to vesa, not helped. But it's possible I've incorrectly changed xorg.conf. Do you have any examples?

Thanks!

vallimar
2nd October 2008, 09:23 PM
Try something like this:
Section "ServerLayout"
Identifier "Xorg"
Screen 0 "Screen0" 0 0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

BLooDMaN
2nd October 2008, 09:38 PM
Try something like this:
Section "ServerLayout"
Identifier "Xorg"
Screen 0 "Screen0" 0 0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Unfortunately had almost the same. Instead of:
Driver "Intel"
I wrote Driver "vesa".
Looks like have to wait bugfix and use offtopic for the time.

BLooDMaN
5th October 2008, 09:12 PM
I've updated system today and it's OK now. Problem is solved!