after trying to solve PPM Error on Boot while HDD is mounted - #7 by stairs I got a new error.
While on the login screen in KDE I can’t use any usb device (keyboard / mouse) until the screensaver appears, then every device works again.
Other post I read on different forums suggest, that the Usb Bus may be blocked by a different device and the boot log suggests the same:
Linux device descriptor read/64, error -110
usb 3-7: device not accepting address 9, error -71
usb 3-7: device not accepting address 10, error -71
However out of the blue, the login screen freezes when the screensaver should normally appear…
Sadly because of that I can no longer login to my device.
I cannot provide any after logs that are not already listed in PPM Error on Boot while HDD is mounted - #7 by stairs because of that
Help would be greatly appreciated.
This usually indicates a lack of power required for a usb device. What do you have connected to the laptop when booting?
I have a normal desktop Pc, to which I connected a keyboard, mouse, and an usb headset.
It has two m2 ssds, a m2 networkcard and a sata hdd.
Try the usb headset in other ports maybe?
Edit: Maybe you could post the hardware.
inxi -Faz | eos-sendlog
Ok I just unplugged everything except the keyboard and I could use the login screen and login to the system.
However after one minute the whole screen fezzes, regardless of being logged in or not.
I already tried
inxi -Faz | eos-sendlog but it doesn’t return a link to the log.
When did the issue of the freezing start and not being able to log in?
Edit: Did you remove the amd_iommu=off kernel parameter and reinstall kernels from your previous post.
About 20 minutes before creating the post.
I wanted to check if I have the correct USB setting in Bios, checked, and closed it (without changing anything)
Then after the next boot it started freezing.
EDIT: I never came to the part where I added
amd_iommu=off. I wanted to do that after checking the bios but well then the freezing started to happen.
Are you able to look at any logs?
sudo dmesg | eos-sendlog
journalctl -p 3 -xb | eos-sendlog
I wonder if the freezing is caused by the drive because of a power management issue. This is quite common.
You could try the kernel parameter
/etc/kernel/cmdline and then run
I change the global KDE theme to a standard one and know “only” the screen freezes while the mouse can still move.
I don’t think it’s a power management issue but I will try to get the logs while the system is usable.
EDIT: I can’t send logs anymore, because my network card stopped working after switching the global theme . And I’m kind of stick of all the hard power offs so I will just reinstall the hole Os and do everything all over again.
If for some reasons the same errors happen again I will update this post.
You should not change the global themes. Leave it set to standard breeze. I can tell you from experience most of the issues with users on kde is because they change things. I have been using kde for a long time and it is flawless. I am also on Ryzen hardware with AMD graphics. You have newer hardware currently. I don’t change settings unless i know they work and it is very minimal. I think if you change your settings to Breeze default and log out and back in. Try it and see what happens.
I changed it from my modified version back to breeze, that’s when the mouse started to still work will everything else freezes.
And isn’t the hole point of kde that it can be modified?
Well I will reinstall everything and keep you up to date with that I stumble upon.
I think reinstalling is too much.
You should try with a new user account first.
Actually, your descriptions are messing with login screen and screensaver in a way that we can’t really understand the exact behavior.
At login (sddm) there is no screensaver.
Ok I will try to explain.
With login screen I mean the normal KDE Endeavour Os login screen.
With screensaver I meant a screen that appeared for me, I don’t know if that’s indented or not, but the login form disappeared and the background got un-blurred if that makes sense and once you pressed a button the login form appeared again.
Kde is very customizable but there are things that work well and things that don’t just like other desktops. I am using Kde and i can use it on Wayland or X11 without issue. I don’t change global themes. I change minor settings, backgrounds, sometimes icons etc. But I do one thing and try it out. If it doesn’t work properly i change it back. I also always log out and back in with any change or reboot. I have no issues. You shouldn’t either with the hardware you have. I use btrfs file system with btrfs-assistant and snapper-support and btrfsmaintenace. I don’t use encryption and i also use grub. Systemd-boot is fine also. I just prefer grub. Can’t really say why? It just feels right.
Edit: Not saying you can’t change global themes. There are just ones that work and ones that don’t! They cause issues!
Alright, I guess I will follow this advice, yesterday I changed the global theme like five times in a row without restarting the system so maybe that is at fault.
I think I will commit to the reinstall and use grub as bootloader like you. While troubleshooting I found way more tutorials for that then systemd boot so grub seems like the better option
There’s nothing wrong with systemd boot. I just have more experience with grub. I’m not an expert on linux but i try to do things at the hardware level.
I don’t know what to do anymore… I can’t reinstall the system via the live Os (Boot over USB) because the screen freezes there too…