cancel
Showing results for 
Search instead for 
Did you mean: 

PC Graphics

joe_schulte
Journeyman III

RX5700 Boot Issue with Linux 5.3-rc6

I just recently built a new desktop with the specs below. The only operating system I have been able to install is Arch Linux, and even that is only in UEFI mode. From there I could only boot into a command line since the update drivers for Navi 10 aren't supported in Linux 5.2.x. Once I have a successful install I then install linux-mainline and grub-hook from the AUR with yay to have the newer kernel, and have pacman auto config grub. I set the log level to 8 in grub when booting. And my systems freezes after the last log message shown below.

Specs:

   Ryzen 3600

   RX 5700

   Asus Tuf Gaming Motherboard

   16B of Corsair Vengeance Ram

Boot log messages:

   kvm: disabled by bios

   [drm] amdgpu kernel modesetting enabled.

   r8169 0000:06:00.0 en6s0: Link is Down

   Parsing CRAT table with 1 nodes

   Ignoring ACPI CRAT on non-APU system

   Virtual CRAT table created for CPU

   Parsing  CRAT table with 1 nodes

   Creating topology SYSFS entries

   pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:0.1

   pcieport 0000:00:01.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)   

   pcieport 0000:00:01.1: AER:  device [1022:1483] error status/mask=00000040/00000600

   pcieport 0000:00:01.1: AER:     [ 6] BadTLP

   iwlwifi 0000:05:00.0: Applying debug destination EXTERNAL_DRAM

   Topology: Add CPU node

   Finished initializing topology

   amdgpu 0000:0c:00.0: remove_conflicting_pci_framebuffers: bar0: 0xe0000000 -> 0xefffffff

   amdgpu 0000:0c:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf01ffff

   amdgpu 0000:0c:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xfcb00000 -> 0xfcb7ffff

   checking generic (e0000000 300000) vs hw (e0000000 10000000)

   fb0: switching to amdpudrmfb from EFI VGA

At this point the system freezes. I also get the same problem when I try to boot with Linux 5.9.11, with the last 7 log messages being the same. Also, I didn't include the log time for the sake of my sanity when typing that out. If needed I can provide them.

0 Likes
0 Replies