You are not logged in.
Hi,
I've just updated my desktop (I think it was a few weeks since my last update).
Before restarting my system I also (stupidly?) removed a few orphaned packages (I do not remember what exactly, I think it is irrelevant by I mention it to be accurate).
After restarting I come to the KDE login screen but the keyboard does not work. The mouse works but I cannot click on anything (clicking on restart button for example does not do anything).
I cannot switch to console or whatever, nothing on keyboard works. I tried with another keyboard and the result was the same. Which was to be expected since the keyboard works up until I get to the KDE login screen (BIOS, live CD, everywhere it works).
I had an old live CD hanging around and used it to chroot into the system. I ran pacman -Syu again but there was nothing needing update (as I guess was expected).
I am not sure exactly where I have to look to fix this.
Last edited by imargonis (2024-02-18 23:38:09)
Offline
Test the behavior on the multi-user.target and w/ the LTS kernel.
Can you ssh into the system? (otherwise it's gonna be tricky to get a journal from the broken boot)
Offline
I am not sure what you mean with your 1st sentence.
About the 2nd I am not sure how I would go about to ssh into the system. I tried (from my laptop) to do ssh username@ip but it said connection refused.
However I am chrooted as I said in my system and I was just looking at the pacman log to see what I removed (thinking about reinstalling to see if that was the problem).
What journal should I look into?
Offline
2n link below.
The LTS kernel is this here: https://archlinux.org/packages/core/x86_64/linux-lts/
You'd first and foremost install and enable the sshd service, https://wiki.archlinux.org/title/OpenSSH#Server_usage
Chroot won't help if you reboot w/ the power button, because that'll lose most of the journal.
Offline
Ok, so I accessed journalctl and it seems there is a core dump by sddm-greeter. It seems the login crashes. But I do not know why.
The radeonsi_dri.so is referenced though.
Last edited by imargonis (2024-02-18 22:43:47)
Offline
Please post your complete system journal, eg. for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
So, this is actually the output of journalctl -b -1 (just -b was empty)
Offline
That looks like the mesa24 bug, downgrade to 23.3.5-1
If it's no longer in the cache, see https://wiki.archlinux.org/title/Arch_Linux_Archive
Edit: you can alteratively test
Feb 19 00:26:08 marg-desktop kernel: amdgpu 0000:01:00.0: amdgpu: Use radeon.cik_support=0 amdgpu.cik_support=1 to override.
to use the amdgpu module - whther this can sidestep the mesa issue has afaik not yet been reported.
Last edited by seth (2024-02-18 23:30:35)
Offline
So I downgraded mesa and now everything seems to be ok.
I followed the advice from here https://bbs.archlinux.org/viewtopic.php?id=292988.
But it also reminded me of a similar problem I had a while back (with black screen) where the culprit was mesa.
And this is one of the reasons why I am sometimes hesitant to update my system. Because I do not know if problems such as this are resolved. I am pretty sure I had made a few updates after my black screen problem so this must be either a regression or a new problem.
Offline
That looks like the mesa24 bug, downgrade to 23.3.5-1
If it's no longer in the cache, see https://wiki.archlinux.org/title/Arch_Linux_ArchiveEdit: you can alteratively test
Feb 19 00:26:08 marg-desktop kernel: amdgpu 0000:01:00.0: amdgpu: Use radeon.cik_support=0 amdgpu.cik_support=1 to override.
to use the amdgpu module - whther this can sidestep the mesa issue has afaik not yet been reported.
So it seems at the same time you were writing your comment I was already doing the downgrade (to a slightly older version of mesa (23.3.3. something) and had begun writing my comment.
Anyway thank you for your time. I guess I will mark as solved if I find out how to do it.
Last edited by imargonis (2024-02-18 23:36:28)
Offline
I had a similar issue where my sway would start up with only a grey screen and a mouse cursor. The mouse wouldn't work nor would the keyboard. About 15 seconds later, it would log me out back to tty. I could login on a different tty just fine. The errors in the swaylog indicated dbus issues which were different in each run but I thought it could be because of the dbus-broker change and I tried a bunch of things including moving back to dbus-daemon-unit and downgrading the linux package to 6.7.4 to no avail.
Came here to create a post and saw this thread and thought I might as well give mesa downgrade a whirl and sure enough it worked. So mesa 1:24 is causing issues with sway as well.
Last edited by Inxsible (2024-02-18 23:59:20)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
mesa 24 is causing issues w/ older radeon GPUs - if you're eligible for si_support or cik_support in amdgpu, you could also test that.
Offline
just fyi, This has been fixed with the latest update to mesa 1:24.0.2-1
Last edited by Inxsible (2024-03-01 15:29:16)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Hey Inxsible,
Always a pleasure. How are things with you?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline