Announcement

Collapse
No announcement yet.

OpenSUSE Ends Support For Binary AMD Graphics Driver

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • nevion
    replied
    People - read what I typed, AMDGPU Pro works on OpenSUSE already. I've already installed it and it seems to be working just fine. The installer already supports OpenSUSE (tested on 42.2). No one needs to repackage anything at this point and it's packaged about as well as proprietary closed source driver can be packaged.

    Leave a comment:


  • stiiixy
    replied
    I'm having the exact same issues as Passso, except on a slightly newer-gen laptop with i7-3612QM and Radeon 7670M (Thames Pro/Turks/TeraScale 2):

    lspci

    Code:
    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] (rev ff)
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    
    00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
    00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
    00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
    I am getting the exact same results, ie only able to use the CPU GFX. However it's REALLY shit. Audio problems and incredibly fast drop in FPS to the point I have to reboot in a minute. It doesn't matter what kernel I use with the distro packaged MESA and GFX stack, and so I then start using PPA's like oibaf and Padoka to try get some sanity back, but nothing there either. All produce the same results. I'm hoping it's just some kernel module I need to blacklist, because this all used to work well enough until about a year ago.

    lsmod |grep -i radeon

    Code:
    radeon               1503232  0
    ttm                   102400  1 radeon
    i2c_algo_bit           16384  2 radeon,i915
    drm_kms_helper        159744  2 radeon,i915
    drm                   364544  8 radeon,i915,ttm,drm_kms_helper
    So Bridgeman, you're suggesting using the latest spin of Ubuntu as it possibly has the basic building blocks that could now support the 'older' card's that seemingly got nerfed?

    I was also dabbling in using the DRI_PRIME method as detailed on Arch, and it sort of worked somewhat when I last tested 6 months+ ago, but apparently this has been included in some of the newer kernels? So I'd need to look in to that again. I'd prefer not to use arch on my laptop however.

    Leave a comment:


  • Amarildo
    replied
    Originally posted by TheBlackCat View Post

    Again, there is no "re-build", the package maintainer never built AMDGPU-PRO. The package that is no longer being built is fglrx, not AMDGPU-PRO. You are asking the maintainer to create a new package from scratch, not re-build an existing package. I have explained this to you over and over and over again, yet you still insist on pretending this is just a matter of re-enabling an existing package.

    And if you want it so much, why don't you build it? One of the basic rules of open-source is "the ones who do, decide". The one who was doing something decided here. Those who refuse to do anything can ask, but they aren't owed anything, especially if they don't even use the distro to begin with.
    There seems to be a small confusion here. "Built" to me basically means "pre-built binaries". "Re-build" is basically re-pacakge to me. I probably use the term "build" wrong, to be honest, because most people think of "re-build" as "re-build from source". If that's the case, I'm OK with changing to "re-PACKAGE" then
    (If I grab a package that was packaged/built for Debian (meaning no sources), extract them, and then re-package everything to fit my distro, that's what I call "re-building" ATM.)

    Most of the packages of AMDGPU-PRO are pre-built, I think the only piece that is not pre-built is the Kernel module, everything else is proprietary. So yes, if the grabs any of the packages he can re-build them (re-package them) for openSUSE.

    I would volunteer to package AMDGPU-PRO for openSUSE if I had prior knowledge of how to package for the OS, and if I had free time. The most I can offer right now is to test the packages and report bugs. I was going to re-package them for Arch since the AUR repo hasn't been touched in several weeks, but I don't have time to do that too. I'm considering just switching to Ubuntu for the time being, or just using AMDGPU from amd-staging 4.7 and wait until the OpenCL in AMDGPU-PRO is correctly compatible with my card (because right now, using amdgpu-pro 16.50 on Ubuntu, the OpenCL is broken).

    Leave a comment:


  • TheBlackCat
    replied
    Originally posted by Slartifartblast View Post
    Or use openSUSE Tumbleweed, lots of new stuff to play with that breaks things there; remember to file a bug report.
    Even Tumbleweed isn't untested. Although package are less tested than in Leap or SLES, packages that go in are still expected to work. They still have to go through QA, for example, and unit tests are often enabled when available.

    Leave a comment:


  • TheBlackCat
    replied
    Originally posted by Amarildo View Post
    Tell you what, I'm volunteering to use openSUSE if the package maintainer re-builds AMDGPU-PRO 16.50.
    Again, there is no "re-build", the package maintainer never built AMDGPU-PRO. The package that is no longer being built is fglrx, not AMDGPU-PRO. You are asking the maintainer to create a new package from scratch, not re-build an existing package. I have explained this to you over and over and over again, yet you still insist on pretending this is just a matter of re-enabling an existing package.

    And if you want it so much, why don't you build it? One of the basic rules of open-source is "the ones who do, decide". The one who was doing something decided here. Those who refuse to do anything can ask, but they aren't owed anything, especially if they don't even use the distro to begin with.

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by Passso View Post
    I tried all radeon packages but maybe I am wrong concerning the name?
    ...

    Yes. Yes you are. Mesa is open-source OpenGL.

    Leave a comment:


  • bridgman
    replied
    Originally posted by Passso View Post
    I have a new Ubuntu 16.04 (I only use LTS), the AMD card is still not activated (as far as I know) : glxinfo shows Mesa
    I don't understand - Mesa is what you should be getting.

    That said... if you see "llvmpipe" you are not getting HW acceleration, but if you see "GALLIUM 0.4" then you are.

    Leave a comment:


  • Passso
    replied
    Originally posted by Amarildo View Post
    Tell you what, I'm volunteering to use openSUSE if the package maintainer re-builds AMDGPU-PRO 16.50.
    Are you trying to blackmail them???

    Leave a comment:


  • Passso
    replied
    Originally posted by bridgman View Post

    Thanks. OK, that's a VLIW part (a Caicos derivative) so definitely radeon kernel driver not amdgpu.

    That's not right... maybe they were just talking about proprietary driver support. You want to be using the open source drivers anyways.

    You should be able to install a recent Ubuntu (I would test with 16.10 if you can) and have good support in the distro image.
    Thanks for your answer. This is where I did give up, because radeon driver is installed :

    xserver-xorg-video-radeon/xenial,now 1:7.7.0-1 amd64 [installé]
    X.Org X server -- AMD/ATI Radeon display driver

    I have a new Ubuntu 16.04 (I only use LTS), the AMD card is still not activated (as far as I know) : glxinfo shows Mesa

    I tried all radeon packages but maybe I am wrong concerning the name?

    Leave a comment:


  • theriddick
    replied
    The AMDGPU-PRO also supports freesync now so thats a gaming feature, I would definitely be using the PRO driver if I had a 490 in my hands right about now!

    Leave a comment:

Working...
X