Unable to enter graphical desktop-I think some problem with drivers

perergrino_ · 2022-03-26 18:50:08

Hello guys my first post here.
So what the title says I installed arch on a dual boot system (windows 11 / arch) and when I installed a desktop(plasma) and a desktop display manager(sddm) and I entered plasma from sddm(I can be in sddm with no problem but when I login it crashes) I have a crash (https://imgur.com/a/fTejGW4).I have access to the system from CLI and it works fine.
I think I have everything needed for the drivers to work (amdgpu with rx 590) as I followed the wiki.
The GPU is working perfectly fine on windows where I'm writing this and I've been troubleshooting for some days now but I don't find the problem.

Some outputs:

journalctl | grep amdgpu

 Mar 26 16:53:03 arch-pc kernel: perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
Mar 26 16:53:03 arch-pc kernel: [drm] amdgpu kernel modesetting enabled.
Mar 26 16:53:03 arch-pc kernel: amdgpu: Ignoring ACPI CRAT on non-APU system
Mar 26 16:53:03 arch-pc kernel: amdgpu: Virtual CRAT table created for CPU
Mar 26 16:53:03 arch-pc kernel: amdgpu: Topology: Add CPU node
Mar 26 16:53:03 arch-pc kernel: fb0: switching to amdgpu from EFI VGA
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: vgaarb: deactivate vga console
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: No more image in the PCI ROM
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: amdgpu: Fetched VBIOS from ROM BAR
Mar 26 16:53:03 arch-pc kernel: amdgpu: ATOM BIOS: 113-59085SMD1-W90
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: amdgpu: VRAM: 8192M 0x000000F400000000 - 0x000000F5FFFFFFFF (8192M used)
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
Mar 26 16:53:03 arch-pc kernel: [drm] amdgpu: 8192M of VRAM memory ready
Mar 26 16:53:03 arch-pc kernel: [drm] amdgpu: 8192M of GTT memory ready.
Mar 26 16:53:03 arch-pc kernel: amdgpu: hwmgr_sw_init smu backed is polaris10_smu
Mar 26 16:53:03 arch-pc kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Mar 26 16:53:03 arch-pc kernel: amdgpu: SRAT table not found
Mar 26 16:53:03 arch-pc kernel: amdgpu: Virtual CRAT table created for GPU
Mar 26 16:53:03 arch-pc kernel: amdgpu: Topology: Add dGPU node [0x67df:0x1002]
Mar 26 16:53:03 arch-pc kernel: kfd kfd: amdgpu: added device 1002:67df
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 36
Mar 26 16:53:03 arch-pc kernel: fbcon: amdgpudrmfb (fb0) is primary device
Mar 26 16:53:03 arch-pc kernel: amdgpu 0000:07:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Mar 26 16:53:03 arch-pc kernel: [drm] Initialized amdgpu 3.42.0 20150101 for 0000:07:00.0 on minor 0
Mar 26 16:53:03 arch-pc kernel: snd_hda_intel 0000:07:00.1: bound 0000:07:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

lshw

  *-display
       description: VGA compatible controller
       product: Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:07:00.0
       version: e1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:50 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:f000(size=256) memory:fce00000-fce3ffff memory:c0000-dffff

lspci -v

07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e1) (prog-if 00 [VGA controller])
	Subsystem: XFX Pine Group Inc. Radeon RX 590 FATBOY 8GB
	Flags: bus master, fast devsel, latency 0, IRQ 50, IOMMU group 16
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Memory at e0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at f000 [size=256]
	Memory at fce00000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Legacy Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [150] Advanced Error Reporting
	Capabilities: [200] Physical Resizable BAR
	Capabilities: [270] Secondary PCI Express
	Capabilities: [2b0] Address Translation Service (ATS)
	Capabilities: [2c0] Page Request Interface (PRI)
	Capabilities: [2d0] Process Address Space ID (PASID)
	Capabilities: [320] Latency Tolerance Reporting
	Capabilities: [328] Alternative Routing-ID Interpretation (ARI)
	Capabilities: [370] L1 PM Substates
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

Some help needed or some pointers.
Thank you in advance and sorry for my english.

seth · 2022-03-26 21:35:39

windows 11 / arch

See the 3rd link below

journalctl | grep amdgpu

No grep, post the entire journal.
Also please your xorg log, https://wiki.archlinux.org/title/Xorg#General

I can be in sddm with no problem but when I login it crashes

When this happens:
1. What happens when you suspend the compositor (SHIFT+Alt+F12)?
2. Can you switch to another VT (Ctrl+Alt+F2)?
3. From there access "xrandr -display :0 -q"?

perergrino_ · 2022-03-27 10:13:26

Thank you for your response.

I disabled windows fast-boot.
Here is the full journalctl https://0x0.st/oqq8.txt
And for the xorg log I find to logs with info here xorg.0 https://0x0.st/oqqq.old and here xorg.1 https://0x0.st/oqqb.log but for what I understand these numbers are the display number and I only have one display.

For the last part now I can't start sddm it says it's masked from systemctl so I tried with lightdm and now it's just a black screen with a tilling underscore on top left and the shortcuts doesn't work.

I don't know if it is related but sometimes in those crashes when i have to force shutdown with power button i have to reset bios to re enter the system.

Update:
now I can't even get to the bios and unable to boot

Last edited by perergrino_ (2022-03-27 11:31:31)

seth · 2022-03-27 11:48:24

[     9.510] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=d735cb04-ff1a-42bc-8c34-fd7547fc1cd2 rw loglevel=3 quiet nomodeset

Don't boot nomodeset - you won't get a display server this way.

https://0x0.st/oqqb.log shows a successful X11 server that ran for ~1s ie. most likely the session crashed?
Can you log into a different session? (Openbox)
I highly suspect this to be an issue w/ budgie, but it could be as simple as

Mar 26 15:36:33 arch-pc gnome-session-c[571]: Locale not supported by C library.
                                                      Using the fallback 'C' locale.

fixing your locale… https://wiki.archlinux.org/title/Locale

I tried with lightdm and now it's just a black screen with a tilling underscore on top left

https://wiki.archlinux.org/title/Kernel … _KMS_start

Edit:

now I can't even get to the bios and unable to boot

You mean you cannot enter the BIOS or that the system doesn't post at all?

Last edited by seth (2022-03-27 11:50:57)

perergrino_ · 2022-03-27 13:01:31

You mean you cannot enter the BIOS or that the system doesn't post at all?

Nvm about the bios thing I cleares CMOS and after some reboots I'm on again

Don't boot nomodeset

How do I remove nomodeset? because from grub editing the entry I don't see nomodeset anywhere.

I highly suspect this to be an issue w/ budgie

Also I uninstalled budgie but I don't think it's the problem because the xorg default session(xterm twm and xclock) also crashed.

seth · 2022-03-27 14:19:00

The modeset xorg log is actually from "Sat Mar 26 16:10:05 2022", it's no longer in the later boots in the journalctl

Looking at the journal, there's a couple of

Mar 26 18:07:07 arch-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125

on early boots, but none on the 27th

For a more structured approach, please boot into SDDM, try to login, have the session "crash", switch to a different VT and post the journal of that boot as well as the latest xorg log.
If that's not possible, reboot into the multi-user.target (2nd link below) and post the xorg log as well as the journal of the previous boot ("sudo journalctl -b -1") from there.

Arch Linux

#1 2022-03-26 18:50:08

Unable to enter graphical desktop-I think some problem with drivers

#2 2022-03-26 21:35:39

Re: Unable to enter graphical desktop-I think some problem with drivers

#3 2022-03-27 10:13:26

Re: Unable to enter graphical desktop-I think some problem with drivers

#4 2022-03-27 11:48:24

Re: Unable to enter graphical desktop-I think some problem with drivers

#5 2022-03-27 13:01:31

Re: Unable to enter graphical desktop-I think some problem with drivers

#6 2022-03-27 14:19:00

Re: Unable to enter graphical desktop-I think some problem with drivers

Board footer