Package Details: linux-amd-staging-drm-next-git 6.2.r1160701.672228ae9ba1a-1

Git Clone URL: https://aur.archlinux.org/linux-amd-staging-drm-next-git.git (read-only, click to copy)
Package Base: linux-amd-staging-drm-next-git
Description: The Linux kernel with bleeding-edge AMDGPU drivers kernel and modules
Upstream URL: https://gitlab.freedesktop.org/agd5f/linux
Keywords: amd amdgpu dal dc radeon vega
Licenses: GPL2
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: yurikoles
Maintainer: yurikoles
Last Packager: yurikoles
Votes: 24
Popularity: 0.000000
First Submitted: 2017-08-24 18:09 (UTC)
Last Updated: 2023-08-19 12:01 (UTC)

Required by (5)

Sources (2)

Pinned Comments

yurikoles commented on 2017-09-25 18:29 (UTC) (edited on 2020-07-07 21:03 (UTC) by yurikoles)

Pull requests are welcome on github.

Please report bugs on upstream GitLab.

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

Crashone commented on 2023-03-09 16:59 (UTC) (edited on 2023-03-09 17:03 (UTC) by Crashone)

The package cannot be installed, as the installer (yay) fails to validate the 'config' file with sha256sums and ends with an exit status 1.

dedguy21 commented on 2022-03-16 15:58 (UTC)

I didn't notice a spot where one could include the option to build the kernel with local drivers. Is there an ldconfig somewhere?

dedguy21 commented on 2022-03-16 15:58 (UTC)

I didn't notice a spot where one could include the option to build the kernel with local drivers. Is there an ldconfig somewhere?

Bednar commented on 2021-03-15 13:41 (UTC)

sphinx-workaround.patch seems not to be needed anymore. patching now fails. removing the patch from the pkgbuild allows the package to build just fine.

Bednar commented on 2021-01-11 09:43 (UTC)

has anything changed with the repo?

I see plenty of new commits at https://gitlab.freedesktop.org/agd5f/linux/-/commits/amd-staging-drm-next/ but there hasn't been anything in weeks on https://cgit.freedesktop.org/~agd5f/linux/

Do we need to change the PKGBUILD to cater for a new location?

gardotd426 commented on 2020-10-11 21:11 (UTC)

@DanEng1982 There is no such thing as 5.10 right now. It doesn't exist yet.

mixedCase commented on 2020-10-11 14:27 (UTC)

Anybody else kernel panicking?

DanEng1982 commented on 2020-10-08 09:53 (UTC)

The package description says 5.10.949809.8f0ba3310c12-1 (or whatever 5.10.x) but what I actually get right now for example is 5.9.0-rc2-1 which works perfectly fine for me but due to the nature of my hardware (Lenonvo ThinkPad E595 with Ryzen 7 3700U Zen+ APU and NVMe SSD) I might actually benefit from the 5.10.x kernel and certainly would love to give it a try as your 5.9 version of the kernel is already brilliantly working with my laptop.

gardotd426 commented on 2020-09-04 23:24 (UTC)

@Bednar the update fails as of a while ago, actually...

It's the included patches, some of them have already been merged (and thus fail), while another (the GCC patch) is only partially merged. I filed an issue on the github repo for this PKGBUILD yesterday, but so far have not gotten a response.

Bednar commented on 2020-09-04 08:21 (UTC)

the update fails as of today:

==> Starting prepare()... Setting version... Applying patch sphinx-workaround.patch... patching file Documentation/conf.py Hunk #1 succeeded at 36 with fuzz 2. Applying patch gcc10-early-boot-fix.patch... patching file arch/x86/include/asm/stackprotector.h Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file arch/x86/include/asm/stackprotector.h.rej patching file arch/x86/kernel/smpboot.c Hunk #1 succeeded at 264 (offset -2 lines). patching file arch/x86/xen/smp_pv.c Hunk #1 succeeded at 94 with fuzz 2 (offset 1 line). patching file include/linux/compiler.h Hunk #1 succeeded at 231 with fuzz 2 (offset -125 lines). patching file init/main.c Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file init/main.c.rej ==> ERROR: A failure occurred in prepare().