SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I'm not really sure what happened, but the fglrx ATi driver won't load on my system anymore. I'm using the 8.12 driver and have been for two months, its been working perfectly fine and today all I get is an empty screen trying to boot into an X session.
As of last night, the only changes I made to my system were upgrading Seamonkey and maybe changing my wallpaper and when I came home from work today the ATi driver stopped loading. I boot into runlevel 3 and reload the vesa driver and it works fine but I hate the vesa driver lol.
I just do not understand what would have possibly caused this to happen?
P.S. I am aware that using 9.x fglrx drivers need MSI to work but I have not upgraded them. Its still the same old 8.12 drivers that I have been using fine for like two months.
I have the exact same problem, On slack 12.2. My HD4870 failed a couple of week ago,so i installed another card(NVIDIA) as a temporary replacement. I was given a new card but when i try to use it with the same xorg.conf that i used before, i get a blank screen (which is of the correct resolution, 1280x1024, according to my monitor).
Edit: I did a slackpkg upgrade whilte i was using the Nvidia card, could it be responsible?
Last edited by koloth; 04-16-2009 at 01:54 AM.
Reason: Added stuff
very weird. So I did # aticonfig --intial -f to try using the fglrx driver again and it works. What is extremely odd about this is I thought this command only affects xorg.conf, similar to nvidia-xconfig, it just configures your xorg.conf file.
I am 120% positive I did not touch my xorg.conf file while my system was up the day before I had this problem. In fact it is the exact same xorg.conf file I have right now. Oh well it works again I guess :\
That thing is dangerous, and overwrites loads of other stuff
I got this installed as follows.
Make a kernel. The config is in /boot if you don't want to cook your own. DO NOT RUN MAKE CLEAN. Boot your new kernel with modules installed. Run the driver and do not switch focus away from that console while it is making. it sticks on the progress bar, but that's all right.
Alternatively use the radeon OSS driver as part of Xorg. Reiunstall libGL stuff, Mesa, and your window manager. For me the difference was about 200 FPS in glxgears, but DRI is crap with radeon atm under linux.
Just in case somebody runs into the same issue, my problem was solved after I uninstalled the Nvidia drivers. Apparently some alteration they did to the system was incompatible with the Radeon drivers and the new radeonhd drivers, which failed before the uninstall but now work as expected.
Just in case somebody runs into the same issue, my problem was solved after I uninstalled the Nvidia drivers. Apparently some alteration they did to the system was incompatible with the Radeon drivers and the new radeonhd drivers, which failed before the uninstall but now work as expected.
Hi your problem is different than mine. In my case the fglrx driver would load but apparently the fglrx module didn't. Simple solution was just adding a line for it at the end of rc.modules 'modprobe fglrx' This problem seems to be fixed with the later catalyst releases so you wouldn't even have to do this.
Personally I have no idea why I had to explicitly add it after it worked fine for so long.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.