So I’ve been messing around with EOS for a while now.
My first install was going great, then it seemily died.
The same problem persisted in the second reinstall and I figured out it was lightdm /greeter not starting.
Lesson learned.
I fixed that and all was good(ish) again.
But as I fixed minor niggles more things broke, but it wasn’t until a restart would they be apparent, so often a few things would break at once.
somehow i ended up with 4 kernels and 4 fall back kernels.
As things would break, I’d jump on a new kernel and continue trying to learn, fix and understand the OS.
I did learn a lot but I’ll admit I’m still quite the novice.
I’ve dabbled with Linux in the past but most of my proper learning has been on EOS.
I want to stay on EOS, as a daily driver and get the games i like to play working on it properly/working.
So jumping forward, I have not only managed to break all 8 EOS kernel options in my (old) boot (systemd).
One of the issues I started having, which still persists on the LiveEOS and now on my third iteration of EOs is when my keyboard is running on wireless…
When not used it goes in to powersave, when i start using it again, it will register one keystroke and then shutdown the system.
I searched for a long time and there was no where with quite this problem.
I ‘think’ I traced it to the power save state of the USB ports.
other things I tried.
#gamemoderun would often fix this.
#powermode balanced (/performance) would often fix this.
Interestingly in some kernels the system wouldn’t shut down when the issue arose but instead the desktop would crash in places and I would sign out and sign back in and it would no longer be broken until a system restart.
I can quickly cause the issue by switching my keyboard from bluetooth to wired and back to bluetooth, system restarts or shuts down.
I’m also having issues with my sound too, when I first log on (auto logon) I will have no sound.
I can fix this by logging out and logging in manually, I later discovered I can go in to sound settings, turn the audio off on my nvidia card and turning back on again.
This is my first post, usually I muddle on and search the net and try to fix all my problems under my own voialition, but my track record of doing that on linux can and has lead to a total OS fail.
I wiped and formatted my entire boot drive, fresh installed windows, then fresh installed EOS, this time using the fancier KDE plasma desktop.
I’ve done very little with windows install and to EOS, only the basics I’ve learned from my last two installs of EOS.
There was a time during my first install that neither the forced shut down or sound issues existed, so i’m confident it can be fixed.
I also don’t have these issues on windows.
My hardware is also very highend.
Right now, its working very well, even getting proton GE working quite well considering how bad my last two attempts at it were, but I am somewhat apprehensive to experiment with potential fixes using my limited Linux skillset.
So here I am, asking the wonderful community for advice, can somebody please help me?
What logs are needed, and what commands do i need to use to fetch them?
If you need more info, no problem.
Thanks,
Crow.
