[SOLVED] Is it possible to install Catalyst 15.9 or the new Crimson software on current?
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.
Is it possible to install Catalyst 15.9 or the new Crimson software on current?
I don't know but I think neither of them will work with Xorg 1.18, at least that's the impression I got after some searching. I couldn't get crimson to install and catalyst installs but errors when starting X.
Edit: Actually I answered my own question. It even says in the release notes that these drivers won't work with xorg server 1.18. Maybe I should just get myself an nvidia card. They seem to be more on the ball than AMD.
And the Nvidia blob didn't work with 1.18 when it was first added to Slack. They needed to wait a bit for Nvidia to pump out an update.
For proprietary drivers, Nvidia is definitely better than AMD, but for open source support, AMD is miles ahead of Nvidia (which still puts it behind Nvidia's proprietary drivers, but, personally, I like to vote for open source with my wallet).
Maybe I missed something... I applied the patches from that thread, set the two environment variables, ran
Code:
./ati-installer.sh 15.201 --install
. The installation went through this time but I get the same segmentation fault that catalyst gave when starting X.
Do I still have to downgrade to xorg server 1.17?
Alas, you do. I didn't get the segmentation fault you did; my hard drive simply quit loading at some point after the "Starting X11" screen disappeared, and I was left with a black screen. I had to manually reboot, and come up in level 3 to recover. However the symptoms show themselves, it all adds up to the fact that Crimson Edition simply does not support 1.18. My own testing showed this to be true.
I would probably reboot into level 3 (I have 'Slacker' as my boot image name, so for me it would be 'Slacker 3', after hitting <Tab> when the LILO boot screen comes up), regress to the earlier versions using upgradepkg (sounds ironic, doesn't it?) and then run the installer again (you'll have to uninstall the earlier installation using
Code:
aticonfig --uninstall
and then reboot before running the installer again.
Let me know if I can help further.
Regards,
Matt
Last edited by 1337_powerslacker; 12-04-2015 at 08:07 AM.
Reason: Added note for clarification
I decided to give Team Fortress 2 a go using the open source radeon driver on xorg-server 1.18. Whenever the game crashes my computer reboots. With the catalyst driver it would always CTD instead.
So I finally decided to downgrade to xorg-server 1.17 using your packages. Now when X starts I have no input at all. Can't even switch to another terminal. The only thing I can to is a hard reboot.
I decided to give Team Fortress 2 a go using the open source radeon driver on xorg-server 1.18. Whenever the game crashes my computer reboots. With the catalyst driver it would always CTD instead.
So I finally decided to downgrade to xorg-server 1.17 using your packages. Now when X starts I have no input at all. Can't even switch to another terminal. The only thing I can to is a hard reboot.
I guess there are more packages I need?
You should not need any more packages. My own experience at the state of -current then gave me no problems whatsoever. There may have been some changes in -current which are affecting your input devices. Of course, there is always the possibility that there might be a configuration issue on your end. Without more detail, that's about all I can come up with at the present.
[ 29.149] (EE) module ABI major version (20) doesn't match the server's version (19)
[ 29.149] (EE) Failed to load module "ati" (module requirement mismatch, 0)
[ 29.185] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 29.192] (EE) module ABI major version (20) doesn't match the server's version (19)
[ 29.192] (EE) Failed to load module "vesa" (module requirement mismatch, 0)
[ 32.541] (EE) module ABI major version (22) doesn't match the server's version (21)
[ 32.541] (EE) Failed to load module "evdev" (module requirement mismatch, 0)
[ 32.541] (EE) No input driver matching `evdev'
[ 32.541] (EE) module ABI major version (22) doesn't match the server's version (21)
[ 32.541] (EE) Failed to load module "evdev" (module requirement mismatch, 0)
[ 32.541] (EE) No input driver matching `evdev'
[ 32.542] (EE) module ABI major version (22) doesn't match the server's version (21)
[ 32.542] (EE) Failed to load module "evdev" (module requirement mismatch, 0)
[ 32.542] (EE) No input driver matching `evdev'
[ 32.544] (EE) module ABI major version (22) doesn't match the server's version (21)
[ 32.544] (EE) Failed to load module "evdev" (module requirement mismatch, 0)
[ 32.544] (EE) No input driver matching `evdev'
It looks like I may need to downgrade xf86-video-ati, xf86-video-vesa, xf86-input-evdev. I don't know if that's true nor what versions to get nor where to get them.
So I've been googling like hell and can't for the life of me find any older packages for xorg. I wanted to find xf86-input-evdev-2.10.0 and possibly libevdev but they are nowhere to be found.
Someone on the arch forums also had the same problem I have downgrading to xorg-server-1.17. No mouse or keyboard input. They solved it by downgrading a libinput package. I don't see such a package for slackware.
Just grab the source/x11/ directory from a -current mirror and build only those drivers. They should be able to be built fine on 1.17. Your problem is they were built on 1.18, so it is expecting Xorg 1.18.
(I think the following is correct, it was done off the top of my head... it may need a few minor corrections)
Code:
wget --r --no-parent --nH --reject="index.html*" --cut-dirs=5 https://www.slackbuilds.org/mirror/slackware/slackware64-current/source/x/x11/
cd x11
sh x11.SlackBuild driver xf86-video-ati
sh x11.SlackBuild driver xf86-video-vesa
sh x11.SlackBuild driver xf86-input-evdev
upgradepkg /tmp/x11-build/xf86*.txz #assuming you've never built anything from the x11.SlackBuild before, otherwise, specify the actual packages
Just grab the source/x11/ directory from a -current mirror and build only those drivers. They should be able to be built fine on 1.17. Your problem is they were built on 1.18, so it is expecting Xorg 1.18.
(I think the following is correct, it was done off the top of my head... it may need a few minor corrections)
Code:
wget --r --no-parent --nH --reject="index.html*" --cut-dirs=5 https://www.slackbuilds.org/mirror/slackware/slackware64-current/source/x/x11/
cd x11
sh x11.SlackBuild driver xf86-video-ati
sh x11.SlackBuild driver xf86-video-vesa
sh x11.SlackBuild driver xf86-input-evdev
upgradepkg /tmp/x11-build/xf86*.txz #assuming you've never built anything from the x11.SlackBuild before, otherwise, specify the actual packages
I was thinking that was probably what is needed to solve ahc_fan's problem. It is interesting,though,that I never did run into his kind of problem after I downgraded to 1.17.4.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
