I recently did a fresh install of the Qtile community edition. The first boot into it works just fine, however the second time I get into it is broken. I can still navigate and do some things such as open programs like a browser etc. But a lot of commands simply don’t work.
Some commands I tried after the reboot that don’t work are, nmcli, making with dkms, and even the reboot command.
Basic things such as ls and cd work.
I type the command into the terminal and the cursor goes to the next line and does nothing.
I tried connecting with USB tethering as well and it won’t even recognize the USB I believe. So perhaps it’s hardware related.
And to reiterate, everything works completely fine on the initial boot of the system.
I’m not really sure what logs or information would need to be provided so let me know.
if possible share your hardware info: inxi -Fxxc0z or if you are able to connect to internet inxi -Fxxc0z | eos-sendlog
Just checked qtile install… and i see it still has picom enabled by default this can caus issues like you have in cases… you could try commenting it in autostart.sh
Ok, I tried that and problem still persists. I am now experiencing heavy delay of OS as a whole. Which leads to my previous though of a hardware issue, but to clarify my hardware is working fine on windows install I have on separate SSD. So maybe a problem with the relationship between the Linux os and my hardware.
Should chroot with the live iso to try the inxi command or stay here?
I’ve re installed eos three times due to this problem. 2 online and one offline. They all work fine in the first boot. It is only after I shutdown the first time and reboot back into it that this problem happens.
I know my hardware has no issues itself as I can run my separate windows installation just fine and because the first boot works.
This has no real meaning. Windows and Linux stress hardware in different ways. Sometimes failing hardware will appear to be working in Windows and broken in Linux. The opposite is also possible.
Probably not. We just need to work towards the root cause.
Can you boot off the ISO and get the inxi information @joekamprad asked for?
simply comment the line starts with picom …
it is also already autostarting on its own… so may remove the package to see if you can load the WM without it… sudo pacman -R picom
You have a lot of audio USB devices connected and Googling your error cannot set freq 48000 to ep 0x3 reveals it may be audio HW related. But I understand initial error is different. Anyway, for a time of troubleshooting I would disconnect everything.
Do you update your system before rebooting? You are not using latest kernel, so maybe update will solve problem? Also you can try to install some 5.x LTS kernel before first reboot - this way you can check if it is some weird kernel regression.
IDK this Endeavour edition… Would try also with some Ubuntu , then normal Endeavour before jumping on community edition. My understanding is this is your first Linux in that PC.
PS. To be on safe side, disconnect one of monitors as well.
