GueGuerreiro If you're using the LTS kernel use nvidia-glx-driver. If you're using 5.6.18(current) use nvidia-glx-driver-current
Can't boot into latest kernel
WannaBeOCer Yes, or course, that was one of the first steps I did:
Go into TTY, run (...)
sudo eopkg it nvidia-glx-driver-current.
I just had to do a rollback of all of that because I couldn't get it work in the end and I still need a machine I can boot into for work
GueGuerreiro When you have a chance, I'd like to see dmesg output from a failed boot.
[deleted]
GueGuerreiro I asked because nvidia remove support for old video cards in the new drivers and maybe that's the reason why the old driver works fine
DataDrake Thank you for popping by. I installed all pending updates, booted into current, installed the nvidia current drivers and rebooted into current again, then ran dmesg and this is the output: https://hastebin.com/ewibiloceh.coffeescript
[deleted] Gotcha. That would make sense. I appreciate you taking the time to reply, I admit I'm not the best when it comes to more in-depth Linux inner workings and keeping up with all the stuff that happens around the ecosystem, so it's always good to get an explanation 
GueGuerreiro So it looks like the kernel booted fine and then your Intel GPU takes over. Maybe /var/log/Xorg.0.log will shed some like after a failed boot?
DataDrake This is what I had there on a failed boot: https://hastebin.com/mukekayogu.cpp
I actually tried uninstalling the Nvidia drivers with doflicky and yeah, I can boot into the current kernel that way, it just makes stuff like gaming impossible 
but I guess the problem is with the driver somehow
[deleted]
GueGuerreiro What is your GPU?
[deleted] It is a GeForce GTX 1050 Ti Mobile, should have added that initially, my bad.
The new driver (440.100) has a changelog entry that says
"Added a workaround for some Pascal based notebooks, where the GPU could fall off the bus when idle."
Not sure if that is connected to your problem though.
4 days later
I'll try to wait for resync next friday, and see if somehow it was just the driver version that's messing me up. I'll try again and report back then.
5 days later
So I tried this again with the new sync. Same thing. Couldn't boot.
This time, however, the rollback failed. I tried running it again, and it kept failing. Something about libcrypt, I guess it was missing with the rollback.
I couldn't even run stuff like reboot or shutdown. I forcefully shutdown with the laptop button, and now I get a Kernel panic every time I boot into the Kernel.
So that's gg, right? Nothing I can do other than start over?
GueGuerreiro Have you tried pressing esc on boot and checking if the PC is booting into the lts kernel, if it is then change to the latest current version?
tadcan tried both, yes
GueGuerreiro You might want to try chrooting into your system and repairing whatever package is broken there. Only downside is that you need a live ISO of Solus.
See here for a quick HowTo: https://getsol.us/articles/troubleshooting/boot-rescue/en/
That being said, if you manage to get around it, could you post the output of the libcrypt error when attempting to rollback with sudo eopkg history -t {whatever version you want to rollback to} -d? there might be some workaround to get it to work
curtisy Thank you for that link, might be what saves me in the end.
I couldn't get the Solus Live ISO to work just yet, though. It takes a while to get to the greeting screen, and as soon as I login, it eventually crashes and asks me to log out, and it gets stuck. Going into TTY doesn't seem to work either, I just go into a black screen when I try.
I think just running Solus, in general, seems to be a problem from my Laptop now :/
I still have my work laptop lying around. It's not as powerful, and I like to work on my personal one while remote for that reason, but I think I'll be good for work for a while. I'll try to revisit this topic next weekend. If I can't get to work though, I don't think I can keep using Solus, I'd have to look for something else that works on my PC, which I'm not too excited about.
- Edited
Ok, it seems what causes this bad Solus Live launch is the fact that I have my ethernet cable connected when I boot it up? If I unplug it, it boots quick and fine.
The problem now becomes that I can't seem to have an internet connection for the boot rescue, which I need if I want to run eopkg commands.
After a while, the network service itself just crashes.
If I open the Wi-fi settings window, I get:
"Oops, something has gone wrong. Please contact your sofware vendor.
NetworkManager needs to be running."
So I tried to restart the network manager with:
systemctl restart NetworkManager.service
But eventually it'll fail with a timeout.
One time as I booted up I tried to immediately connect to my Wifi, and it kinda worked, but if I tried to open my terminal then it wouldn't work. In fact, nothing seemed to work past that point.
I also tried to only connect my ethernet cable once I had booted into Solus successfuly, but everything stops working past that point as well. I can move my mouse, but that's about it.
I'll keep trying for now, but is there something I'm missing here to get networking to work?
EDIT: But I WAS able to mount my Solus partition, and I got the error back, if it's helpful, the libcrypto error was this:
Error while loading shared libraries: libcrypto.so.1.1: Cannot open shared object file: No such file or directory
Looking into that specific error, it leads me to believe this is related to OpenSSL. I know there was an upgrade to that done to Solus recently. @DataDrake could this then be related to that? This happened when I tried to rollback after the OpenSSL upgrade.
Trying to run some basic eopkg commands while chrooted into my Solus instalation, I always get pisi errors, which I believe means they're eopkg errors, since it is a fork of the former.
That must mean eopkg broke somehow during the rollback, I suppose? Is there any coming back from that, or do I really have to start over?
I can't provide text logs, unfortunatelly, I can only provide it into picture format, so apologies in advance.
Running eopkg up gives me this:
And attempting a rollback gives me this:
