Recent update switched to LTS kernel, boot fails, manual steps required.

GueGuerreiro

colorado_chris I think I have the same issue as you. I was running the LTS Kernel for the longest time, because the current would always give me a black screen forcing me to restart. This time around the LTS gives me the white cursor, while the current gives me the black screen. Tried pressing F11 on boot and trying all the possible entries. No dice.

Any way I could possibly debug this even? I get no error mesages or anything 🙁

Edit: Seems I can login into the shell (CTRL+ALT+ one of the F keys) on both LTS and current. Anything I can do here to figure out what's going wrong?

Scotty-Trees

GueGuerreiro There has been an update since yesterday that addressed and fixed this. I would recommend when you boot, if you can drop into a TTY and then run a sudo eopkg up command and reboot and hopefully fingers crossed, you should be back in working order, at least with your LTS kernel.

GueGuerreiro

Scotty-Trees I'm afraid not, I had all updates since yesterday before I shut off my laptop for the night (the .conf update that was pushed later is the last one I had installed).

I've been trying to get it to run on the Current kernel for a while now. Tried installing linux-current, nvidia-glx-driver-current, adding nomodeset to boot (I believe I had that before when installing solus for the first time, many years ago. Unfortunately the forum post I used to troubleshoot my issue was on the old domain and has since been lost). Then I tried restarting lightdm. Blank blinking cursor. Tried rebooting several times, and selecting every available entry, but still no dice.

I saw someone on reddit mentioning they ran systemctl --failed to get a list of failed services, so I tried that and I get failed on lightdm.service and vboxdrv.service (on the 5.0 current kernel. Running this on 5.6 gives me a lot more, and it seems my ethernet nor my external keyboard are working on that one, so I gave up on that version for the time being).

Seeing the Virtual Box service fail there led me to believe that it could be the issue linked above, but I'm already on the latest Vbox version and I removed virtualbox-guest-common. Also installed virtualbox-current, but the service still fails.

Not sure what I can try next :/

Sorry for the bad formatting in parts, or some typos that might be there, I'm having to type all this on mobile

GueGuerreiro

Chrym Try installing virtualbox-current. I noticed that one exists too.

Harvey

GueGuerreiro
Indeed. There is a version for LTS kernel and the "current" kernel as explained here:
https://getsol.us/articles/software/virtualbox/en/

Chrym

GueGuerreiro thx, didn't notice that normal one is LTS.

sudo eopkg search virtualbox Passwort: minikube-dbginfo - Debug symbols for minikube minikube - Kubernetes development environment virtualbox - VirtualBox host modules for the linux-lts kernel virtualbox-common - Common components for VirtualBox host packages virtualbox-guest-common - Common components for the VirtualBox guest packages virtualbox-guest - VirtualBox guest additions for the linux-lts kernel virtualbox-32bit-dbginfo - 32-bit debug symbols for virtualbox virtualbox-dbginfo - Debug symbols for virtualbox virtualbox-devel - Development components for VirtualBox virtualbox-current - VirtualBox host modules for the linux-current kernel

it even is described as LTS Version

GueGuerreiro

I did a rollback and it's currently working as before. So some other package was causing issues (possibly with lightdm). I'll try to look into this further when I have some extra time, but I wasted enough time as it is trying to get it to work, and I'll need this laptop working tomorrow for work.

DataDrake

Chrym @kyrios may be able to shed some light on that, I'm not sure why that's a runtime dependency for virtualbox itself. I don't think it needs to be.

kyrios

DataDrake

DataDrake Chrym I am not in front of my computer but virtualbox comes with 4.9 kernel modules (LTS) so it doesn't seem odd to me.

If you are running the current kernel you have to install virtualbox-current as explained in the documentation.

https://getsol.us/articles/software/virtualbox/en/#solus-as-host

colorado_chris

InFamousM All I know so far is that you will need to boot a Solus .ISO and mount your hard drive to be able to update the broken files.

colorado_chris

SuperJC710e Hello. Were you able to fix this?

Trying the directions to mount EFI and my OS boot sector here https://getsol.us/articles/troubleshooting/boot-rescue/en/

but having no luck. "unknown filesystem type 'LVM2_member' message after mounting to the /target dir.

Updates have become very problematic with this OS to the point that I am no longer saving any files on local disk. Chances are you will lose that data after a simple update. Needs to be addressed.

DataDrake

kyrios We should think about flipping that now that -current is default. Pretty sure that dates back to the -lts days.

Chrym

kyrios as I said: I'm to stupid to read descriptions 🙂

kyrios

DataDrake Indeed. It currently follows the same naming convention as the other drivers so if we change this for vbox, we'll probably want to do it for the other packages to be consistent.

pappkamerad

@DataDrake i tried your suggestions, but when i boot the LTS kernel i still only get a blinking cursor. Current kernel boots fine, but i cannot use it as it is still lagging as hell and freezes completely after some time on the XPS 9560.

The blinking cursor issue was also there a couple of updates ago ☹️

Anything else i can try?

DataDrake

pappkamerad I think there was a regression with the LTS kernel on some newer hardware. We are all waiting on upstream to release a new version. I'll be creating a post shortly to get some feedback around LTS.

pappkamerad

DataDrake thanks for the update!

catfishsushi

DataDrake This was helpful for me today. Ran update to get the latest firefox & brave updates with other stuff, and it returned this for the second time in a week :

The Manual changing may have helped me, Thank You so Much !!

[deleted]

catfishsushi Your EFI boot partition is too small.

catfishsushi

I have 3 drives on my system, Windows 10, linux Solus on one and a fresh install of Solus on another. Right now, i am having issues trying to both: connect to Twitch on the Fresh install-- (Which shows "Unsupported Browser Type") even after updating the OS, the other version on Solus was....my bad, typed in commands to force an update of the kernel to 'clr-boot-manager' which..has erased the boot record/and/or messed up its ability to boot.....the Kernel is the 6.3.6-239 and its not working. the edit menu command line does not allow for clr-boot-manager to work/run.
So, to get around the unsupported browser type issue, i tried installing a VPN, when i try to activate it, the KDE-wallet pops up asking for a password. so, i went to settings and tried to disable it...but it seems i don't have permission to turn that off, and thus, the VPN will not connect. Being objective oriented, I booted in windows 10...and it connected to twitch. In the meantime, i'm stuck needing a means of re-installing and/or grafting a new kernel to my Primary Solus installation. Any ideas/help?

« Previous Page Next Page »