Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#63860 - linux-5.3arch1-1 hangs at loading initial ramdisk

Attached to Project: Arch Linux
Opened by kursu (kursu) - Friday, 20 September 2019, 12:19 GMT
Task Type Bug Report
Category Packages: Core
Status Unconfirmed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details


linux-5.14-arch2-1 works just fine, however upgrading to 5.3-arch1-1 makes system unable to boot. Hangs at "Loading Inital Ramdisk..."


Downgrading to 5.14-arch2-1 again as a temporary solution
This task depends upon

Comment by kursu (kursu) - Friday, 20 September 2019, 13:22 GMT
Typo, 5.2.14-arch2-1 not 5.14 lol
Comment by daimonion (demon) - Friday, 20 September 2019, 13:35 GMT
I can confirm this, all I know from Xorg log is that radeon driver is not loaded.
   Xorg.log (5.2 KiB)
Comment by kursu (kursu) - Friday, 20 September 2019, 14:12 GMT
Ok, I tried module_blacklist=amdgpu as kernel parameter and removed "quite" but with no success in even booting, I get no screen output at all after "Loading initial ramdisk"
Comment by kursu (kursu) - Friday, 20 September 2019, 22:03 GMT
Downloaded the 5.3 source, and configured a minimal kernel and recompiled. 10 reboots later and now it works. Was suspicious about he new navi code but navi seems to work also. Will dig deeper into the 5.3arch1-1 config tomorrow
Comment by kursu (kursu) - Saturday, 21 September 2019, 21:50 GMT
Found the solution.

AMD IOMMU Version 2 driver cant be compiled as module. must be included in kernel
Comment by loqs (loqs) - Saturday, 21 September 2019, 22:02 GMT Comment by daimonion (demon) - Sunday, 22 September 2019, 11:49 GMT
@loqs This is not a solution as I am experiencing same problem on my laptop with Intel graphics.
Comment by loqs (loqs) - Sunday, 22 September 2019, 12:00 GMT
@demon I was not suggesting it was a solution. I responding to kurso's post above mine
pointing out the conclusion did not match with the facts I provided.

Loading...