Boots into black screen - unresponsive (AMD)

Hi,
I’m able to boot into latest LTS kernel but when selecting latest non-LTS I boot into a black screen with a dash in the upper left and the keyboard is completely unresponsive.
Running latest firmware for asus rog strix g15 advantage edition (AMD).

Below is journalctl after booting into LTS

Dec 28 08:48:00 kernel: ucsi_acpi USBC000:00: unknown error 4104
Dec 28 08:48:00 kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
Dec 28 08:48:28 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.GPP0.VGA], AE_NOT_FOUND (20220331/psargs-330)
Dec 28 08:48:28 kernel: ACPI Error: Aborting method _GPE._L05 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Dec 28 08:48:28 kernel: ACPI Error: AE_NOT_FOUND, while evaluating GPE method [_L05] (20220331/evgpe-511)
Dec 28 08:48:30 pa_supplicant[1297]: bgscan simple: Failed to enable signal strength monitoring
Dec 28 08:48:52 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:48:52 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:48:56 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:48:56 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:48:58 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:48:58 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:48:59 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:48:59 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:20 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:20 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:26 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:26 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:28 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:28 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:28 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:28 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:43 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:43 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:44 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:45 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:50 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:50 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:50 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:49:50 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:50:03 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:50:03 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:50:04 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128
Dec 28 08:50:04 kernel: logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128

Hello,
I did a quick search (top right) with “asus rog strix g15”.

This thread:

In support by Mr. BS86 (a very knowledgeable member) might start you up to repair the screen issue.

The other very experienced volunteers might need help if you post some more information if you can …

This here:
https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

I will be following to learn more.

Take care,
François

Hi,

Not sure I understand. I read the article but it does not apply to what I’m encountering and wasn’t sure what other systemlog to post that would be needed.
The laptop you linked is the correct one so thanks.

google the above

This appears to be for a different cpu architecture and from what I’ve read in other threads it should not impact booting into the system I believe ?

This was functional until around a few kernel upgrades ago (right around qt5 or whatever it was with the ‘5’ version) and the system loads fine in LTS.

I tried to do it to confirm if this was the issue but getting permission denied even when adding sudo or bash ahead of the command.
I ran chmod -R +w /sys/firmware/acpi/interrupts/gpe6F and it said directory not found. below is command I was originally trying to run
echo “disable” > /sys/firmware/acpi/interrupts/gpe6F (also tried “mask”)

Shouldn’t it be gpe05? Where are you getting gpe6F from?

echo "mask" > /sys/firmware/acpi/interrupts/gpe05

Edit: Looks like you are using what’s posted on the google page but that’s not necessarily your specific hardware output. I’m just going by the journal you posted. I may be wrong but please check. :thinking:

Hi, I’m getting permission denied with sudo and bash ahead of the command even after successfully running chmod -R +w /sys/firmware/acpi/interrupts/gpe05 but still get permission denied

I don’t really know the reason for the permission denied. :thinking: I was just pointing out maybe you also didn’t have the correct hardware reference.

You could instead try using a kernel parameter to mask the acpi error on boot as explained on the page here at the bottom of the page. Just make sure you to: (ensure the relevant gpe= value is substituted as appropriate for your situation)

Edit: Double check if there are any new UEFI Bios updates. I think it is version 331 if i have the right hardware you mentioned.

thanks, so steps seem a bit confusing and not familiar with what I’m looking at but I’m running latest Bios and systemd.
It says to edit the file here (/boot/loader/entries/arch.conf`) but after going into endeavouros and boot the only file I see within is amd-ucode.img

Once I find the file do I just add an extra line that says options root=UUID=0a3407de-014b-458b-b5c1-848e92a327a3(do I need to edit this UUID to display main partition??) rw acpi_mask_gpe=05

I would do it this way as per the wiki how to modify kernel options then you have to reinstall the kernels.

https://discovery.endeavouros.com/installation/systemd-boot/2022/12/

would I just add acpi_mask_gpe=05

would I just add acpi_mask_gpe=05

Yes if using systemd-boot you would add it to /etc/kernel/cmdline and then run sudo reinstall-kernels
Can’t guarantee it will work but it’s worth a try. Make sure you removed what you have tried before so nothing is conflicting.

Edit: I’m also not sure if it should be 0x05 ? Try it first and if not maybe like this? I don’t know what output you see exactly. I’m just looking at the example from the link so I’m not 100%

acpi_mask_gpe=0x05

sorry for all the questions but where exactly do I add it within what I currently have. Would the below be fine ?
nvme_load=YES acpi_mask_gpe=0x05 nowatchdog rw rd.luks.uuid=(removed for security) root=/dev/mapper/luks-(removed for security)

You just add it in the line. It doesn’t matter where as long as you leave a space before and after what you are adding. Looks okay from what you are showing. Then save and do the command to reinstall the kernels. Reboot after and see if it does anything.

Edit: Like i said previously I’m not sure whether it has to be acpi_mask_gpe=05 OR acpi_mask_gpe=0x05

just tried both with no success

Can you post your hardware output? Just provide the links to the output.

inxi -Faz | eos-sendlog

Edit: You could also show what dmesg is showing

sudo dmesg | eos-sendlog

Inxi - https://0x0.st/H6aR.txt
dmesg - https://0x0.st/H6a5.txt

I see you are using Wayland. Are you able to boot into desktop using X11?
Edit: Also there was just a new kernel update 6.6.9-arch1-1 . Have you updated to try the latest kernel? I see you are booting on lts.