Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #67199 > unrolled thread

Debian 10.0 works with 3rd generation Ryzen

Back to article view | Back to linux.debian.kernel

Contents

  Debian 10.0 works with 3rd generation Ryzen Mick Ab <recoverymail123890@gmail.com> - 2020-05-29 16:10 +0200
    Re: Debian 10.0 works with 3rd generation Ryzen Ben Hutchings <ben@decadent.org.uk> - 2020-05-30 20:10 +0200
      Re: Debian 10.0 works with 3rd generation Ryzen Nicholas D Steeves <nsteeves@gmail.com> - 2020-05-31 00:20 +0200
        Re: Debian 10.0 works with 3rd generation Ryzen Michel Dänzer <michel@daenzer.net> - 2020-05-31 01:40 +0200
          Re: Debian 10.0 works with 3rd generation Ryzen Nicholas D Steeves <nsteeves@gmail.com> - 2020-06-05 04:50 +0200
            Re: Debian 10.0 works with 3rd generation Ryzen Michel Dänzer <michel@daenzer.net> - 2020-06-05 09:40 +0200

#67199 — Debian 10.0 works with 3rd generation Ryzen

[Multipart message — attachments visible in raw view] — view raw

https://www.phoronix.com/scan.php?page=article&item=3900x-linux-distros&num=1

The above article shows that Debian 10.0 will work with a third generation
Ryzen CPU.

I understood that the stable release of Buster had problems with such CPUs.
Has the problem been overcome by installing appropriate AMD firmware ? Has
the BIOS setting of the motherboard also played a part ?

[toc] | [next] | [standalone]

#67208

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2020-05-29 at 15:00 +0100, Mick Ab wrote:
> https://www.phoronix.com/scan.php?page=article&item=3900x-linux-distros&num=1
> 
> The above article shows that Debian 10.0 will work with a third generation
> Ryzen CPU.
> 
> I understood that the stable release of Buster had problems with such CPUs.
> Has the problem been overcome by installing appropriate AMD firmware ? Has
> the BIOS setting of the motherboard also played a part ?

I don't the specifics, but new CPU models tend to work without specific
support in the kernel.  The most critical model-specific setup is done
by the system firmware (BIOS).  However, features such as power
management and performance monitoring may not work as well as with a
current kernel version.

I believe the latest AMD *GPUs* won't work with Debian 10, though. 
They require both new firmware and kernel driver changes (and possibly
user-space driver changes, but I don't know).

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                         - Albert Camus

[toc] | [prev] | [next] | [standalone]

#67209

[Multipart message — attachments visible in raw view] — view raw

Hi,

Ben Hutchings <ben@decadent.org.uk> writes:

> On Fri, 2020-05-29 at 15:00 +0100, Mick Ab wrote:
>> https://www.phoronix.com/scan.php?page=article&item=3900x-linux-distros&num=1
>> 
>> The above article shows that Debian 10.0 will work with a third generation
>> Ryzen CPU.
>> 
>> I understood that the stable release of Buster had problems with such CPUs.
>> Has the problem been overcome by installing appropriate AMD firmware ? Has
>> the BIOS setting of the motherboard also played a part ?
>
> I don't the specifics, but new CPU models tend to work without specific
> support in the kernel.  The most critical model-specific setup is done
> by the system firmware (BIOS).  However, features such as power
> management and performance monitoring may not work as well as with a
> current kernel version.
>
> I believe the latest AMD *GPUs* won't work with Debian 10, though. 
> They require both new firmware and kernel driver changes (and possibly
> user-space driver changes, but I don't know).
>

For AMD Navi, Mesa 19.2 (released sept 2019) is the oldest usable
version.  Imho it's time we provide a "hardware enablement" backport of
the graphics stack, not only for users, but also to thank AMD for their
new phase of GPL-friendly driver development.

This will also require a backport of llvm-10-toolchain.  The only thing
I'm not sure about is if additional Xorg components would additionally
need to be backported.

I've CCed the backports list and the teams involved.

Cheers,
Nicholas

[toc] | [prev] | [next] | [standalone]

#67210

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2020-05-31 12:16 a.m., Nicholas D Steeves wrote:
> Ben Hutchings <ben@decadent.org.uk> writes:
>>
>> I believe the latest AMD *GPUs* won't work with Debian 10,
>> though. They require both new firmware and kernel driver changes
>> (and possibly user-space driver changes, but I don't know).
>
> For AMD Navi, Mesa 19.2 (released sept 2019) is the oldest usable
> version.  Imho it's time we provide a "hardware enablement"
> backport of the graphics stack, not only for users, but also to
> thank AMD for their new phase of GPL-friendly driver development.
>
> This will also require a backport of llvm-10-toolchain.

FWIW, Navi GPUs can work with LLVM 9.


> The only thing I'm not sure about is if additional Xorg components
> would additionally need to be backported.

None, but kernel 5.6 or newer is required for Navi 14 (RX 5500).


- -- 
Earthling Michel Dänzer               |               https://redhat.com
Libre software enthusiast             |             Mesa and X developer
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSwn681vpFFIZgJURRaga+OatuyAAUCXtLmUAAKCRBaga+Oatuy
AMhVAJ9pX2aW01mQLc5zoZMqXwGO63PfrwCeNtFThR+hYJG7vQhbEug5JfSn/FE=
=F/Gq
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#67231

[Multipart message — attachments visible in raw view] — view raw

Hi,

Michel Dänzer <michel@daenzer.net> writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2020-05-31 12:16 a.m., Nicholas D Steeves wrote:
>> Ben Hutchings <ben@decadent.org.uk> writes:
>>>
>>> I believe the latest AMD *GPUs* won't work with Debian 10,
>>> though. They require both new firmware and kernel driver changes
>>> (and possibly user-space driver changes, but I don't know).
>>
>> For AMD Navi, Mesa 19.2 (released sept 2019) is the oldest usable
>> version.  Imho it's time we provide a "hardware enablement"
>> backport of the graphics stack, not only for users, but also to
>> thank AMD for their new phase of GPL-friendly driver development.
>>
>> This will also require a backport of llvm-10-toolchain.
>
> FWIW, Navi GPUs can work with LLVM 9.
>

Noted :-)  I didn't realise this, and have two biases: 1) no-change
backports of pkgs are strongly preferred, and Mesa in testing uses LLVM
10.  2) an irony-mode (clang-powered Emacs mode for C, C++, and Obj-C)
user filed an upstream issue requesting clang-10 support in the Debian
package.

>
>> The only thing I'm not sure about is if additional Xorg components
>> would additionally need to be backported.
>
> None, but kernel 5.6 or newer is required for Navi 14 (RX 5500).
>

Thank you for confirming this!

So it looks like the main blocker at this time is #952710
"firmware-amd-graphics: AMD Navi GPU doesn't work".

Best,
Nicholas

[toc] | [prev] | [next] | [standalone]

#67235

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2020-06-05 4:44 a.m., Nicholas D Steeves wrote:
> Michel Dänzer <michel@daenzer.net> writes:
>> On 2020-05-31 12:16 a.m., Nicholas D Steeves wrote:
>>
>>> The only thing I'm not sure about is if additional Xorg
>>> components would additionally need to be backported.
>>
>> None, but kernel 5.6 or newer is required for Navi 14 (RX 5500).
>>
>
> Thank you for confirming this!

Actually, I mis-interpreted the gitk output before, Navi 14 is already
supported as of 5.4.


- -- 
Earthling Michel Dänzer               |               https://redhat.com
Libre software enthusiast             |             Mesa and X developer
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSwn681vpFFIZgJURRaga+OatuyAAUCXtnxgQAKCRBaga+Oatuy
AOTdAJ9KNLIGwCW0r3qyXtJC44YBNr5cUQCdGwjAmpr/5en6g56OgjrfoSxeVgk=
=j2Ri
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web