Questions about OpenSUSE (does it support AMD graphics driver)??

What is OpenSUSE ? Can i get a basic information ? im too noob for Linux.Does OpenSuse support amd graphics driver?? Is it a seperate distro from others? (I mean there is Debian there are so many distro’s based on it.Arch Linux or Red Hat are some examples.Is OpenSUSE like them or is it based on something?)Will it support amd or it will be like Ubuntu ? (which made me very very upset).I wanna know.If it supports what OpenSUSE you suggest me ? Tumbleweed or Leap ?I’m using a Toshiba Satellite Laptop.

openSUSE is Linux but as a distro it does not evolve from any other distro. It is pure open source (thus the name) so you must install any proprietary stuff,such as video drivers, from outside the distro. It does supply the open source drivers that do work for most hardware.

Tumbleweed is fast moving cutting edge thus more prone to problems so you need to understand more and be able to trouble shoot.

LEAP 42.1 is the current stable version and would be better for one that does not want to experment

IMO for those that have near zero experience with Linux it is better to start with other distros like Mint or Ubuntu because they often provide some proprietary drivers out of the box and thus are a bit easier to new users to install and get running. Sometimes openSUSE can be a bit more challenging depending on hardware

If you decide to go openSUSE then remember this forum you can get lots of expert help

So it does support amd.Well i used so many distros ! Like for example : Deepin, Ubuntu, Manjaro, Fedora, Zorin, Ubuntu Mate, Elementary, Peppermint, Antergos etc… I can’t use Ubuntu cause of my drivers … If it supported I would use Ubuntu ofc!

Well I’m sure that Ubuntu supports AMD drivers but you may have to install them. Also it does depend on the exact model of AMD since older GPU drivers may be dropped by AMD. Remember AMD driver are proprietary and supplied by AMD. There is a open source driver called radeon that is often shipped with the distro ISO that has decent performance

If you want or need the proprietary AMD driver you add the AMD repository and install. The default at install would be to use the radeon driver

Hi
Depends on the age of the AMD graphics card, if it’s a newer (BONAIRE, CARRIZO, FIJI, HAINAN, HAWAII, KABINI, KAVERI, MULLINS, OLAND, PITCAIRN, POLARIS10, POLARIS11, STONEY, TAHITI, TONGA, TOPAZ, VERDE) one you can use the amdgpu driver else stuck with radeon.


/sbin/lspci -nnk | grep -A3 VGA

For Leap 42.2 no proprietary driver unless AMD produce some rpm’s, else it’s Ub* fglrx won’t work with Xorg 1.18.

I have the amdgpu running on Tumbleweed, the kernel is fixed (apart from one bug report) for my MULLINS card, but not xf86-video-amdgpu yet, it’s included now but no updated release yet since my bug report, so have to build a git based one. I have a Kabini [Radeon HD 8180] device, but have not got around to testing that one yet with amdgpu.

I have AMD Radeon R7 M200/260.I wanna know.>: Wait so i can install AMD drivers on Ubuntu 16.04/16.10 !!! I’m trying to install fedora now. … It is giving me a dracut error.AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH i hate installation errors.I hope I can install SUSE with no problem (if i can install my driver in it):’(:’(:’(:’(

Am Sat, 10 Sep 2016 11:46:01 GMT
schrieb banapple890 <banapple890@no-mx.forums.microfocus.com>:

> ?!?!?!?!?!?!!?!??!?!?!??!?!?!?!?!?!?!!??!?! I’m trying to install fedora

Why do I suddenly feel the urge to read a book by Terry Pratchett?

(scnr)


Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

-.- it seems to be you copied wrong. Or understood the sentence wrong. Also the matter is not that. :sarcastic:

So you expect advice on Ubuntu and Fedora on a openSUSE site???

So is this a hybrid graphics laptop with both a Intel and AMD processor???

If so the hardware defaults to Intel and you must select the AMD. Maybe the Intel can be turned off in the UEFI (BIOS)?? But that does reduce the battery life because the AMD slurps more electricity

Hi
Not the amdgpu-pro diver from AMD, it’s only Ub* You either use radeon or amdgpu kernel drivers for tumbleweed and Leap 42.2 Beta 1.

What version of openSUSE are you going to install?

@banapple890, is it an APU there? in my case I have an A6-7400k APU (r5 gfx) and o/SUSE leap 42.1 works fine (radeon drivers) if you need catalyst, you have to try Manjaro IIRC they still use an older version of xorg so catalyst works there, don’t blame the distros for this, its the friggin AMD that stopped support for newer xorg.

On this (simply installed) openSUSE 13.2 system an OLAND AMD (pure) card is running perfectly happily the radeon driver:


 > /sbin/lspci -nnk | grep -A3 VGA
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240] [1002:6613]
        Subsystem: ASUSTeK Computer Inc. Device [1043:04bb]
        Kernel driver in use: radeon
        Kernel modules: radeon
 > 

On a (simply installed) dual-boot Leap 42.1 system AMD Dual-Graphics is running perfectly happily with the radeon driver:


 > /sbin/lspci -nnk | grep -A3 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b]
        Subsystem: Lenovo Device [17aa:3804]
        Kernel driver in use: radeon
        Kernel modules: radeon
 > 

[HR][/HR]Bottom line: simply installed openSUSE runs perfectly happily on AMD systems.

Hi
I’m guessing it’s an APU system…? Sure it all works fine with radeon, have the same GPU on one system… do you get the boost states for your CPU?


cpupower frequency-info


grover:~ # lspci -nnk |grep -A3 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8350G] [1002:9997]
    Subsystem: Hewlett-Packard Company Device [103c:194e]
    Kernel driver in use: radeon
    Kernel modules: radeon
grover:~ # cpupower frequency-info
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 4.0 us
  hardware limits: 1.40 GHz - 2.70 GHz
  available frequency steps:  2.70 GHz, 2.30 GHz, 1.90 GHz, 1.40 GHz
  available cpufreq governors: ondemand performance
  current policy: frequency should be within 1.40 GHz and 2.70 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency: 1.40 GHz (asserted by call to hardware)
  boost state support:
    Supported: yes
    Active: no
    Boost States: 3
    Total States: 8
    Pstate-Pb0: 3300MHz (boost state)
    Pstate-Pb1: 3100MHz (boost state)
    Pstate-Pb2: 2900MHz (boost state)
    Pstate-P0:  2700MHz
    Pstate-P1:  2300MHz
    Pstate-P2:  1900MHz
    Pstate-P3:  1400MHz
    Pstate-P4:  900MHz

Yes:


 # cpupower --cpu 0,1,2,3 frequency-info
analysiere CPU 0:
  Treiber: acpi-cpufreq
  Folgende CPUs laufen mit der gleichen Hardware-Taktfrequenz: 0
  Die Taktfrequenz folgender CPUs werden per Software koordiniert: 0
  Maximale Dauer eines Taktfrequenzwechsels: 4.0 us.
  Hardwarebedingte Grenzen der Taktfrequenz: 1.40 GHz - 2.50 GHz
  mögliche Taktfrequenzen: 2.50 GHz, 2.10 GHz, 1.80 GHz, 1.40 GHz
  mögliche Regler: ondemand, performance
  momentane Taktik: die Frequenz soll innerhalb 1.40 GHz und 2.50 GHz.
                    liegen. Der Regler "ondemand" kann frei entscheiden,
                    welche Taktfrequenz innerhalb dieser Grenze verwendet wird.
  momentane Taktfrequenz ist 1.40 GHz  (verifiziert durch Nachfrage bei der Hardware).
  boost state support:
    Supported: yes
    Active: no
    Boost States: 3
    Total States: 8
    Pstate-Pb0: 3500MHz (boost state)
    Pstate-Pb1: 3200MHz (boost state)
    Pstate-Pb2: 2800MHz (boost state)
    Pstate-P0:  2500MHz
    Pstate-P1:  2100MHz
    Pstate-P2:  1800MHz
    Pstate-P3:  1400MHz
    Pstate-P4:  900MHz
analysiere CPU 1:
  Treiber: acpi-cpufreq
  Folgende CPUs laufen mit der gleichen Hardware-Taktfrequenz: 1
  Die Taktfrequenz folgender CPUs werden per Software koordiniert: 1
  Maximale Dauer eines Taktfrequenzwechsels: 4.0 us.
  Hardwarebedingte Grenzen der Taktfrequenz: 1.40 GHz - 2.50 GHz
  mögliche Taktfrequenzen: 2.50 GHz, 2.10 GHz, 1.80 GHz, 1.40 GHz
  mögliche Regler: ondemand, performance
  momentane Taktik: die Frequenz soll innerhalb 1.40 GHz und 2.50 GHz.
                    liegen. Der Regler "ondemand" kann frei entscheiden,
                    welche Taktfrequenz innerhalb dieser Grenze verwendet wird.
  momentane Taktfrequenz ist 2.50 GHz  (verifiziert durch Nachfrage bei der Hardware).
  boost state support:
    Supported: yes
    Active: no
    Boost States: 3
    Total States: 8
    Pstate-Pb0: 3500MHz (boost state)
    Pstate-Pb1: 3200MHz (boost state)
    Pstate-Pb2: 2800MHz (boost state)
    Pstate-P0:  2500MHz
    Pstate-P1:  2100MHz
    Pstate-P2:  1800MHz
    Pstate-P3:  1400MHz
    Pstate-P4:  900MHz
analysiere CPU 2:
  Treiber: acpi-cpufreq
  Folgende CPUs laufen mit der gleichen Hardware-Taktfrequenz: 2
  Die Taktfrequenz folgender CPUs werden per Software koordiniert: 2
  Maximale Dauer eines Taktfrequenzwechsels: 4.0 us.
  Hardwarebedingte Grenzen der Taktfrequenz: 1.40 GHz - 2.50 GHz
  mögliche Taktfrequenzen: 2.50 GHz, 2.10 GHz, 1.80 GHz, 1.40 GHz
  mögliche Regler: ondemand, performance
  momentane Taktik: die Frequenz soll innerhalb 1.40 GHz und 2.50 GHz.
                    liegen. Der Regler "ondemand" kann frei entscheiden,
                    welche Taktfrequenz innerhalb dieser Grenze verwendet wird.
  momentane Taktfrequenz ist 1.40 GHz  (verifiziert durch Nachfrage bei der Hardware).
  boost state support:
    Supported: yes
    Active: no
    Boost States: 3
    Total States: 8
    Pstate-Pb0: 3500MHz (boost state)
    Pstate-Pb1: 3200MHz (boost state)
    Pstate-Pb2: 2800MHz (boost state)
    Pstate-P0:  2500MHz
    Pstate-P1:  2100MHz
    Pstate-P2:  1800MHz
    Pstate-P3:  1400MHz
    Pstate-P4:  900MHz
analysiere CPU 3:
  Treiber: acpi-cpufreq
  Folgende CPUs laufen mit der gleichen Hardware-Taktfrequenz: 3
  Die Taktfrequenz folgender CPUs werden per Software koordiniert: 3
  Maximale Dauer eines Taktfrequenzwechsels: 4.0 us.
  Hardwarebedingte Grenzen der Taktfrequenz: 1.40 GHz - 2.50 GHz
  mögliche Taktfrequenzen: 2.50 GHz, 2.10 GHz, 1.80 GHz, 1.40 GHz
  mögliche Regler: ondemand, performance
  momentane Taktik: die Frequenz soll innerhalb 1.40 GHz und 2.50 GHz.
                    liegen. Der Regler "ondemand" kann frei entscheiden,
                    welche Taktfrequenz innerhalb dieser Grenze verwendet wird.
  momentane Taktfrequenz ist 1.40 GHz  (verifiziert durch Nachfrage bei der Hardware).
  boost state support:
    Supported: yes
    Active: no
    Boost States: 3
    Total States: 8
    Pstate-Pb0: 3500MHz (boost state)
    Pstate-Pb1: 3200MHz (boost state)
    Pstate-Pb2: 2800MHz (boost state)
    Pstate-P0:  2500MHz
    Pstate-P1:  2100MHz
    Pstate-P2:  1800MHz
    Pstate-P3:  1400MHz
    Pstate-P4:  900MHz
 # 

German language machine . . .

Hi
Like me it’s inactive… only fglrx will kick it into life, work needs to be done.

If you load the system up and watch mperf Freq column it won’t kick the boost states into life…


watch -n 5 cpupower monitor mperf

Have checked the latest kernel options-- nothing has changed with respect to the options for the radeon driver. Maybe a later kernel will have something . . .
Please wait . . .

Hi
If the system is still around… I’ve just stuck windows 10 on a HDD that can pop into it and added to the list of systems to get rid of. I have a DELL 5555 that has a AMD A8-7410 APU with AMD Radeon R5 Graphics boost works fine with Tumbleweed and kernel 4.8.x. But even that system is only 1 year old and obsolete as far as AMD are concerned (from a openSUSE POV)… I know they are working on something, but since they won’t release details of where they are at with there road map, it’s just a wait and see… but amdgpu is working so I’m happy with that… :wink:

Aaaah!! The AMD “Islands” issue: <https://www.x.org/wiki/RadeonFeature/&gt; – scroll down to “Decoder ring for engineering vs marketing names”. And then this: <https://wiki.archlinux.org/index.php/AMDGPU&gt; –

At the moment there is support for the Volcanic Islands, some cards of the Sea Islands family and the Southern Islands family (more experimental than Sea Islands and coming only in Linux 4.8). AMD has absolutely no plans for supporting the pre-GCN GPUs.

Where GCN is the newer Radeon 3D Hardware.

[HR][/HR]In other words, amdgpu is not an option for my Northern Islands ARUBA / Richland [Radeon HD 8650G] machine – also not with openSUSE 42.2 (currently kernel 4.4.19-1-default – but, the amdgpu kernel module loads OK). On this 42.1 machine (kernel 4.1.31-30-default) the amdgpu kernel module is not present.

Hi
Correct, (which is what I was aware of) which I’m a bit grumpy about… have no issues with the radeon driver, but I would like my boost support back… else it’s a win only machine and no good around here :wink:

Yes amdgpu is in => 4.4 kernels. The way I understand it, there will be no support for AUBA’s etc… Only Volcanic, Sea (enabled on openSUSE later kernels now) and Southern.

darn, I am on leap, I think I will try the 4.8 from kernel-default now…