Package Base Details: linux-amd-staging-drm-next-git

Git Clone URL: (read-only, click to copy)
Keywords: amd amdgpu dal dc radeon vega
Submitter: yurikoles
Maintainer: yurikoles
Last Packager: yurikoles
Votes: 24
Popularity: 1.49
First Submitted: 2017-08-24 18:09
Last Updated: 2020-05-31 10:40

Pinned Comments

yurikoles commented on 2017-09-25 18:29

Pull-requests are welcome:

Please report bugs upstream: or amd-gfx mailing list.

Please make sure that build output is not localized by adding LC_ALL=C in front of command that you use to build a kernel, e.g. LC_ALL=C makepkgs -si

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

txtsd commented on 2018-03-03 17:40

Is this working for anyone on a 2400G? My system appears to freeze around when the IOMMU error shows, but the keyboard and mouse flash hardware colors, as opposed to when actually frozen. Also, are the tux supposed to appear tiled at the top of the screen during boot?

libgradev commented on 2017-12-13 13:15

@CyberShadow same here - 4.15-rc3 working fine though!

CyberShadow commented on 2017-12-13 03:42

It's worth noting that the amd-staging-drm-next branch still has and continues to accumulate commits that are not in mainline, likely to be submitted in 4.16 and successive Linux versions.

It looks like some refactorings have been pushed there today, which incidentally broke the whole thing for me (boot freezes after a "fb: switching to amdgpudrmfb from EFI VGA" message).

holunder commented on 2017-12-11 02:23

I encourage you all to move to linux-mainline now as this finally got mainlined. 4.15 RC2 didn’t crash on me once, before with the patched kernels, my system with a RX580 was basically guaranteed to crash within a few hours.

ejrs commented on 2017-12-10 19:01

I've started to kernel panic, I fixed it by downgrading to mesa-git 97055.109de3049d. something between 109de3049d and 3ba973fe37 was the offending commit. as far as I'm aware seems like anything built before oct 26th doesn't cause a protection fault.

Related bug:

Edit: It was caused by llvm, I rolled back llvm and rebuilt the latest mesa-git

zzrzlk commented on 2017-12-05 10:15

Thank you so much for this package. I was looking for something that could fix a random blank screen when booting the official 4.14 Arch kernel on a Carrizo rev c5 A10-8700p) . (Will 4.15 kernel include all the add on of this package?)

Joch commented on 2017-11-16 10:59

Hello, thanks a lot for this paket. I got my Vega 64 running and get the graphical interface with xorg running. I think I had to do

mkinitcpio -p linux-amd-staging-drm-next-git

manually. But this is just fine. If I want to add openCL support to my Vega 64 I have to add the ROCm stuff to your solution or did I get something wrong?
Have someone any hints about that or resolved this issue already?

First I tried to build the ROCm kernel without linux-amd-staging-drm-next-git but this ends with an black screen and kernel crash.

So I am grateful for any hints.

LeJimster commented on 2017-11-05 20:39

@laichiaheng - just build&install linux-amd-staging-drm-next-git and the headers/docs will get installed afterwards. I made the same mistake selecting all 3 packages and it will clone and build the entire kernel 3 times, lol.

BTW, Not sure if it's just me being stupid and doing something wrong. But I got an error after it had finished compiling:

"==> ERROR: Failed to load preset: `/etc/mkinitcpio.d/linuxlinux-amd-staging-drm-next-git.preset' error: command failed to execute correctly"

However, the preset *was* there when I checked, so I ran:

mkinitcpio -p linux-amd-staging-drm-next-git

and it installed all ok.

laichiaheng commented on 2017-10-31 03:35

Do i need to install linux-amd-staging-drm-next-git-header it if I want to install linux-amd-staging-drm-next-git or just need to it alone?

HellishINC commented on 2017-10-17 20:53

==> Validating source files with sha256sums...
config.x86_64 ... FAILED
==> ERROR: One or more files did not pass the validity check!
:: failed to verify linux-amd-staging-drm-next-git

setting it to 'SKIP' allows it to successfully build but fails to install though it will install via pacman -U.