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: 25
Popularity: 0.026807
First Submitted: 2017-08-24 18:09
Last Updated: 2021-01-13 20:45

Pinned Comments

yurikoles commented on 2017-09-25 18:29

Pull requests are welcome on github.

Please report bugs on upstream GitLab.

Latest Comments

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

EnSER commented on 2020-04-07 07:08

The build is failing for me at the moment with: Extension error: Could not import extension cdomain (exception: cannot import name 'c_funcptr_sig_re' from '' (/usr/lib/python3.8/site-packages/sphinx/domains/

This points to this bug:

Not sure if the mentioned workaround would make sense at the moment or not:

yurikoles commented on 2020-02-03 19:03

According to site ( the latest commit was 4 days ago, it seems like they just had forgot to merge/rebase on top of linus repo. I do magic of patch + 1 because of this tags mess, but as for now I think it worth to do a +2.

Regardless of number reported by uname this package has fresh material, e.g. 4 days old. I do infrequent rebases on top of linux-mainline package, but they are often not required, since it just works. Feel free to re-build this package as often as you want to pull new commits.

yurikoles commented on 2020-02-03 18:52

It's next branch, it has material targeting 5.5, but no 5.5 tag obviously. Feel free to examine commit log or repo site.

gardotd426 commented on 2020-02-03 18:45

Why is this a months-old kernel? It's reported here as 5.5.875752.a90553955f0c-1 but it's not. It's 5.4.0-rc7-amd-staging-drm-next-git-01924-ga90553944f0c. Which means the kernel itself from the repo is months old, but that doesn't explain why this page (and the PKGBUILD) is reporting it incorrectly. And yes, I chose to cleanBuild all three involved packages, and they were updated like 2 hours ago. So this is the most up-to-date package available, and it's still only 5.4.0-rc7. Also confirmed by having none of the 5.5 patches, so it's not like uname and every other system utility is just reporting it wrong (which would be ridiculous anyway)

yurikoles commented on 2020-01-11 20:17

I had successfully booted KDE Plasma with my latest build.

sklorpion commented on 2020-01-11 19:46

@yurikoles - still doesnt work for me, not loading initial ramdisk at all.

update: works like a charm, i had wrong ucode.

yurikoles commented on 2020-01-11 08:33

@EnSER, @Bednar

Thanks for report! Should be fixed now.

Bednar commented on 2020-01-10 18:49

@EnSER - same problem.

EnSER commented on 2020-01-06 10:52

I'm not getting an initrd image with the newest pkgbuild update. The output during package build is: -> Installing hooks... sed: can't read ../linux.preset: No such file or directory sed: can't read ../60-linux.hook: No such file or directory sed: can't read ../90-linux.hook: No such file or directory

This points to line 117-122 in PKGBUILD. Diff shows these files have been removed?!?

sklorpion commented on 2020-01-04 08:48

after recent update i got "unknown filesystem type 'ext4'" after reboot - i gues i got something wrong with modules. Can you help me fix?

After few rebuilds and using also linux-amd-wip-git i got system freez after i pick in grub2 new builds.