Can't get proprietary ATI drivers to work with Radeon HD 8790M on openSUSE 13.2

gonneman · 01-01-2015, 06:16 PM

Hello everyone. As the title says, I can't get the proprietary ATI drivers to work on a fresh install of openSUSE 13.2.

My computer is a DELL Latitude E6540 notebook with a Radeon HD 8790M. When I install the drivers using the "glrx64_xpic_SUSE132" package in yast, the drivers don't work. This seems to lead to strange behaviour like the yast GUI not starting. If I try running "aticonfig -initial", then this creats an xorg.conf file with which X cannot start (by default there does not seem to be an xorg.conf).

I've tried installing an older version of the "glrx64_xpic_SUSE132" package as well as building the rpm myself as outline at the bottom of:
https://en.opensuse.org/SDB:AMD_fglrx
Nothing has worked so far.

I'd be grateful for any advice. Here are my hardware details as output by lspci and the likes.

Code:

# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4)
00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d4)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
0e:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)

Code:

# uname -a
Linux linux-tuvi.site 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux

Edit: I would like to add dmesg and the xorg log here but they are too long. Is there a way for me to attach them as text files?

onebuck · 01-02-2015, 09:12 AM

You can use: http://pastebin.com/ to load the text then provide the link to that pastebin page within the post.

Please be sure to reply within your created thread instead of duplicating the thread. These are not network induced duplicates. You have hours between the post and you even noted the error with apologies if it was a duplicate.

No reason to continue this habit. You have done this several times over the last few days. So please, make some effort on your part so this problem does not continue.

John VV · 01-02-2015, 01:01 PM

as per the instructions
Did you black list the already installed OPEN source driver ?
and did you rebuild the boot image first
BEFORE trying to install the closed source driver from the ATI repo

you do need to do everything

gonneman · 01-02-2015, 06:05 PM

Quote:

Originally Posted by onebuck

You can use: http://pastebin.com/ to load the text then provide the link to that pastebin page within the post.

Please be sure to reply within your created thread instead of duplicating the thread. These are not network induced duplicates. You have hours between the post and you even noted the error with apologies if it was a duplicate.

No reason to continue this habit. You have done this several times over the last few days. So please, make some effort on your part so this problem does not continue.

Thank you for telling me about pastebin.

I appologise again for the double post, I posted a 2nd time because my original post disappeard after a few hours and I was worried that it had gotten lost somehow. I guess it was revealed prematurely pending admin approval and then got hidden again. I can't possibly have done this several times over the last few days, since I only just signed up yesterday.

Quote:

Originally Posted by John VV

as per the instructions
Did you black list the already installed OPEN source driver ?
and did you rebuild the boot image first
BEFORE trying to install the closed source driver from the ATI repo

you do need to do everything

I just blacklisted the driver now and rebooted. No change. But I used lsmod previously to check and the radeon driver was never getting loaded.

Apart from that I'm not sure which instructions you are referring to. The openSUSE page I linked to does not mention rebuilding a boot image.

After playing around with my configs, I now believe that the problem is that the integrated intel GPU is being given priority over the ATI card.
See my X log here: http://pastebin.com/Gbn9qDEq

If I force X to only use the ATI card (by using the commands "aticonfig --initial" and "aticonfig --px-dgpu), then I appear to be getting seg faults:
http://pastebin.com/cj91dfQT

And finally my dmesg log in case that is of any use:
http://pastebin.com/i5RiQVxY

onebuck · 01-03-2015, 09:24 AM

Quote:

Originally Posted by gonneman

Thank you for telling me about pastebin.

I appologise again for the double post, I posted a 2nd time because my original post disappeard after a few hours and I was worried that it had gotten lost somehow. I guess it was revealed prematurely pending admin approval and then got hidden again. I can't possibly have done this several times over the last few days, since I only just signed up yesterday.
<snip>

Your Welcome!
http://pastebin.com/ is just one to use. You can use http://imageshack.com/f/nmscreenshotat20120205145p for large images.

Our mod control panel shows the post/thread awaiting approval and the time mod getting to the task of approval can lag.
My inclusion for 'Last few days' was that you had done the same thing over the last two days. My mistake, should have stated as such.

John VV · 01-03-2015, 12:53 PM

Quote:

I just blacklisted the driver now and rebooted. No change. But I used lsmod previously to check and the radeon driver was never getting loaded.

BUT!!!!
did you rebuild the boot image to REMOVE the opensourcce driver BEFORE trying to install the AMD .bin driver

also
you HAVE to have already have installed the kernel source for the RUNNING kernel and gcc and autotools

gonneman · 01-03-2015, 06:42 PM

Quote:

Originally Posted by John VV

BUT!!!!
did you rebuild the boot image to REMOVE the opensourcce driver BEFORE trying to install the AMD .bin driver

also
you HAVE to have already have installed the kernel source for the RUNNING kernel and gcc and autotools

No I did not, since I was not compiling the driver by hand. I was using the package manager to install rpms. The one mildly "manual" thing that I tried was using a script to build the rpms, as explained here:
http://www.sebastian-siebert.de/2014...-installieren/
None of these installation methods mention the need for kernel sources.

After much mucking about, I came to the conclusiong that the fglrx drivers would load (I could see them in the output of lsmod), but that they caused segmentation faults when X was trying to start.

Unfortunately I ran out of patience after that and reverted back to openSUSE 13.1 where everything works. Thank you for taking the time to give me advice onebuck and John VV.