[Solved] Yet another X won't start thread

lpb331 · 2009-11-03 03:21:48

After updating the system over the weekend, I restarted the computer, and X doesn't seem to want to start anymore. A look at the log yields:

(EE) Failed to load /usr/lib/xorg/modules//driversradeon_drv.so

I have a Thinkpad T40 with a Radeon Mobility 7500 graphics card. Reinstalling xorg didn't help. Neither did switching to the vesa driver, or removing the xorg. conf file that I have. (The only difference was the error giving driversvesa_drv.so and driversati_drv.so.) While I can see that it's looking for the wrong file (the files are in /usr/lib/xorg/modules/drivers/), how can I make it look in the right place? Thanks!

Last edited by lpb331 (2009-11-06 15:19:06)

brando56894 · 2009-11-03 04:28:32

The only thing I can think of ATM is you could try a symlink. Is that a typo or is there really two slashes before drivers and none after?

lpb331 · 2009-11-03 12:43:08

I'm afraid that's not a typo; that's what the log spits out at me. I'm pretty sure if we can somehow get X to put the / in the right place, it'll work just fine, as the files are where they are supposed to be. Problem is, I have no clue about how to do that!

grey · 2009-11-03 13:30:38

My xorg.conf file has

Section "Files"
        ModulePath   "/usr/lib/xorg/modules"
...

and in Xorg.0.log I have

(**) ModulePath set to "/usr/lib/xorg/modules"
...
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so

How does that look in your case: is ModulePath set correctly, and are at least some modules loaded?

perbh · 2009-11-03 13:57:10

Try out 'cd /usr/local' and 'cd /usr//local'
Yup - no difference whatsoever!

Cyrusm · 2009-11-03 14:21:41

or you could try uninstalling and reinstalling xf86-video-ati. I had the same problems with radeonhd_drv.so and this seems to have fixed it.

lpb331 · 2009-11-03 15:10:33

@grey: The module path is correctly set. All extensions (dri, extmod, glx, etc.) are loading fine, but then it gets to loading radeon and X comes to a grinding halt. After that, it says that it loaded the mouse module properly, but then when trying to load the kbd module, it says that no drivers are found. Don't know if the first error is causing that one or not.

@Cyrusm: That was my first idea! Alas, no dice. Thanks though!

bgc1954 · 2009-11-03 15:22:31

Yup, just did a pacman -Syu this AM and low and behold my X won't start either and mine shows it can't find my nvidia driver so of course I came to the forums but this post isn't helping much yet. I'll keep slogging away at the problem or perhaps someone smarter will solve this for us.

Misfit138 · 2009-11-03 17:07:28

bgc1954 wrote:

Yup, just did a pacman -Syu this AM and low and behold my X won't start either and mine shows it can't find my nvidia driver so of course I came to the forums but this post isn't helping much yet. I'll keep slogging away at the problem or perhaps someone smarter will solve this for us.

This might help?

bgc1954 · 2009-11-03 17:32:37

Thanks for the suggestion Misfit138 but I tried that already along with alot of other things in all the posts here. I can get X to work if I switch to the good old "nv" driver but then I can't play any 3D stuff like neverball so I just did as suggested in some other posts and downgraded xorg-server and dependencies. I guess that's all I'll do for now since I don't feel like building nvidia drivers that seemed to work for some others.

Edit: Actually, I have to correct this statement. Misfit138, you're right This did work for me after I switched from nvidia-96xx to straight nvidia and rebooted. I didn't think my old Geforce 6200 card liked the newest nvidia driver but I guess I was wrong.

Last edited by bgc1954 (2009-11-03 19:38:58)

lpb331 · 2009-11-04 04:14:41

Since I'm not using an nvidia driver, that won't solve my problem. (Though I'm glad it solved bgc1954's!) Any other ideas?

bgc1954 · 2009-11-04 15:06:57

I would suggest that since your video driver worked before the upgrade you will likely have to do what I did in the first place and like many others seem to be doing, downgrade xorg-server and dependencies and, for now, add them to your IgnorePkg line in /etc/pacman.conf. until a more permanent solution is found. Your case is odd though since as soon as I switched to either the nv or vesa driver things started working.

lpb331 · 2009-11-06 15:18:05

Sorry for the delay; grad school has the ability to take away your life for a little while! Anyway, it appears that downgrading solves the problem! Still, I have no idea why that computer thinks it should be looking for the radeon module there. Especially since my other computer had no such trouble with the upgrade, and no one else with a radeon appears to have this problem. Oh well, all is good for now. Thanks bgc1954!

Arch Linux

#1 2009-11-03 03:21:48

[Solved] Yet another X won't start thread

#2 2009-11-03 04:28:32

Re: [Solved] Yet another X won't start thread

#3 2009-11-03 12:43:08

Re: [Solved] Yet another X won't start thread

#4 2009-11-03 13:30:38

Re: [Solved] Yet another X won't start thread

#5 2009-11-03 13:57:10

Re: [Solved] Yet another X won't start thread

#6 2009-11-03 14:21:41

Re: [Solved] Yet another X won't start thread

#7 2009-11-03 15:10:33

Re: [Solved] Yet another X won't start thread

#8 2009-11-03 15:22:31

Re: [Solved] Yet another X won't start thread

#9 2009-11-03 17:07:28

Re: [Solved] Yet another X won't start thread

#10 2009-11-03 17:32:37

Re: [Solved] Yet another X won't start thread

#11 2009-11-04 04:14:41

Re: [Solved] Yet another X won't start thread

#12 2009-11-04 15:06:57

Re: [Solved] Yet another X won't start thread

#13 2009-11-06 15:18:05

Re: [Solved] Yet another X won't start thread

Board footer