Open M-Bab opened 7 years ago
Updated to kernels 4.9.50+, 4.12.13+, 4.12.13+_UBUNTU Updated firmware package with Raven binaries. Updated README.
Updated to kernels 4.9.51+, 4.12.14+, 4.12.14+_UBUNTU
Updated to kernels 4.9.53+, 4.13.5+, 4.13.5+_UBUNTU
Updated to kernels 4.9.55+, 4.13.6+, 4.13.6+_UBUNTU
Updated to kernels 4.9.59+, 4.13.10+, 4.13.10+_UBUNTU Updated firmware binaries.
Updated to kernels 4.14.0+ and 4.14.0+_Ubuntu Kernel 4.9 is removed because 4.14 is the next longterm support (LTS) kernel. Caution: Issues when re-activating the screen from standby or after screen lock can still occur. I have kind of given up on the issue - I could find nothing that helps the AMD developers to resolve the issue.
Updated to kernels 4.15+ and 4.15+_Ubuntu These are pre-release kernels but amd-staging-drm-next jumped to 4.15 so I had to follow. At least it should resolve the standby issues.
Updated to kernels 4.15.0-rc4+, 4.15.0-rc4+_UBUNTU
Updated to kernels 4.15.0-rc5+, 4.15.0-rc5+_UBUNTU
Updated to kernels 4.15.0-rc6+, 4.15.0-rc6+_UBUNTU Happy New Year!
Thanks Martin. Running it now without issue on Mint 18.3, Compiz enabled. Amd Radeon R6 Carrizo w/ Vulkan. Thanks for your work, and Happy New Year!
On Tue, Jan 2, 2018 at 3:06 AM, Martin notifications@github.com wrote:
Updated to kernels 4.15.0-rc6+, 4.15.0-rc6+_UBUNTU Happy New Year!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/23#issuecomment-354717460, or mute the thread https://github.com/notifications/unsubscribe-auth/AYOpud85gkRgBfEZGDKHpJUnO5SEkthuks5tGeOPgaJpZM4PZWo1 .
Updated to kernels 4.15.0-rc8+, 4.15.0-rc8+_UBUNTU
Updated to kernels 4.15.1+, 4.15.1+_UBUNTU
Little delay I was pretty busy. So 4.15 is officially out and includes DAL hooray! Now you can also get your kernel with sound from more official sources like: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
Why did I still build this one and why it might (depends on the case) still be worth to install it?
Updated to kernels 4.15.4+, 4.15.4+_UBUNTU
Kernel 4.16 based on amd-staging-drm-next (vanilla and Ubuntu) replaces 4.15. VBlank crash after screen lock is finally fixed. Screen locking can still result in an unresponsive system or screen flickering.
Updated to kernels 4.16.0-rc7+, 4.16.0-rc7+_UBUNTU
Updated to kernels 4.16.0, 4.16.0_UBUNTU Release versions. Updated firmware package (Vega12, Vega20).
Updated to kernels 4.16.2+, 4.16.2+_UBUNTU Flickering not fixed unfortunately.
Rebuild 4.16.2+ just to get rid of the flickering.
Updated to kernels 4.16.3+, 4.16.3+_UBUNTU
Updated to kernel 4.16.15+
Kernel 4.18 based on amd-staging-drm-next (vanilla and Ubuntu) replaces 4.17.
Updated to kernel 4.18.0 RELEASE
Updated to kernel 4.18.5
Updated to kernel 4.18.8, updated firmware binaries.
Updated to kernel 4.19.1
After a long break: Updated to kernel 5.0-rc4
5.0-rc6 was pushed by Martin 12 days ago, self-notifying after the fact :)
Updated to kernel 5.0-rc8.
Updated to kernel 5.0, updated firmware binaries package.
Updated to kernel 5.0.1. Is there still interest in such a bleeding edge kernel? Ubuntu 19.04 will include the 5.0 kernel most likely with freesync and I am not sure if this project needs to be continued.
@M-Bab yes, very much so, thank you! I am using Debian / testing for my Ryzen 3 2200G and this kernel is a real treasure :)
This project is a godsend for those of us who likes experimenting with "bleeding edge" hardware, so I'd personally love to see the project continued.
Updated to kernel 5.0.2.
Update to kernel 5.0.4
Updated kernels to 5.0.9. Updated firmware binaries.
Updated kernels to 5.0.17. Updated firmware binaries. (addendum: no, I did not do it... I just noticed there is a new kernel and wrote a comment here :D )
I just wanted to say Thank you for continuing to roll these kernels. I'm still on Kde-Neon and your kernels are still the best way to have freesync + the latest cve protection. For what ever reason Ubuntu mainline kernels have dropped the freesync patch after 5.1_rc2. None of them have the option to turn on freesync, nor does newest 5.2_rc1 that includes the drm-tip and daily branches. Sorry for not filling out or adding to bug reports, I've been busy over the last few months trying to track down [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS with error code 4! using the mainline kernels turns out it started with 4.18_rc1 which means it's time to learn to bisect and go through 120+ AMD commits.
Update to kernel 5.0.19.
Update to new kernel 5.2.0-rc6. Already includes Navi 10 support. If anyone buys such a card in the next weeks please inform me if it works!
Updated to released kernel 5.2.0.
Updated to kernel 5.2.4 by @M-Bab
Updated to kernel 5.2.5 ( @M-Bab )
Updated to kernel 5.2.9
Had to replace kernel 5.2.9 with another build. The original 5.2.9 crashed on boot on my PC.
Updated to kernel 5.2.10
Arg, after a having some trouble for a few kernel versions, having to boot to recovery mode, I've found nomodeset means I can boot... though brightness controls have stopped working.
Not really the right place to put this, but wish AMD and / or HP would get it together, I don't know if it's the kernel / firmware or the BIOS update / tweaking GRUB that's done it :/
Are updates planned? You can give ready-made instructions or script for building the linux kernel + amd-staging. And I might be able to release updates more often... thanks
Yeah there are still updates planned and this on a weekly basis again. But to be honest: the builds on 5.3 were simply not successful. So I skipped them hoping that AMD will soon rebase to 5.4. If it helps I can still do the patch releases of 5.2 but for the other stuff I need properly building kernel code. I really hope it works well again with 5.4.
Okay tried it again with 5.3 - whatever changed in the meantime. Both kernels build again. Enjoy 5.3.11 based on amd-staging-drm-next.
This isn't a real issue. It is just there to inform interested people about pushed updates. I will add an entry on each pushed major update.
Please do not comment to this issue.