Failed to boot after reboot

FTouzain

This sort of bug related to NVIDIA driver packages, being not present in the previous driver version, how can I install this previous version, please ?

Staudey

FTouzain You can't. The driver modules are bound to the kernel version. But if it's the same issue with both the 470 driver and the 570 driver, it's unlikely that it's the driver itself that's the problem (could be an issue with how it's packaged though).

FTouzain

Staudey Thank you for this information. So, I will wait the "Black screen after login" bug correction to at less use solus without nvidia drivers.

FTouzain

I upgraded in a chroot, UEFI mode... Still a strange behavior. The system is booting but I only see the motherboard screen (I know it because I ear the small "click" of my sound card): no login screen.
Therefore with Ctrl Alt F2, I can go in Solus, without graphics.

I tried with nvidia drivers, without... it is always the same.

When I did the upgrade, I saw something like "bind to ... LTS success" but no LTS kernel was installed. So, I installed the LTS kernel (in case the graphic drivers try to communicate with a lts not installed)... it does not change anything.

I tried startx when logged in TTY... it told me "no screen available".

Strangely, I boot in TTY2, but I have always the same error message for sudo clr-boot-manager update:
[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device

What surprise me the most is that my usb key live session can display screen without problem while my current session can't. Is there a way to put --nomodeset like for my usb live key to at least use my current session without nvidia drivers the time this bug is solved ?

brent

FTouzain
had no idea you get get the terminal...
sudo sync && sudo clr-boot-manager update (updates and clears old entries just in case)
sudo sync && sudo clr-boot-manager update (this do after an update)
sudo eopkg check | grep Broken | awk '{print $4}'| xargs sudo eopkg -y it --reinstall (repairs broken packages; if it returns no output consider itself successful)
sudo eopkg check (will check broken stuff if you are playing it safe)

solus doesn't use startx.
I fear anything I write would just be ruling stuff out...still think you need uniformity (grub or uefi) in format/partition/bios....then let solus do the rest (rebuild boot in chroot)

FTouzain

I have no broken package (I have checked after each upgrade). I have completely erased the nvme before solus fresh install.

The bios? Maybe. My motherboard has an uefi of 2017. But why this would be not working just now (I had no really problems until now) ?

I will try again ´sudo sync && sudo clr-boot-manager update’.

How solus can tell ´no booting device’: I arrive in solus tty2, therefore solus has booted, isn’t it? It is probably not the nvidia graphic driver itself because when I remove it, it does not change anything. What files are needed to start graphic session and what must I find into ?
Do you think it is still a booting problem or just a graphic configuration problem ?

brent

FTouzain Do you think it is still a booting problem or just a graphic configuration problem ?

Beats me.

FTouzain My motherboard has an uefi of 2017. But why this would be not working just now (I had no really problems until now) ?

Going into the BIOS might be interesting.
Secure boot, csm, other weirdness you probably already looked. We are at post 62!

As for a graphical problem, I am not experienced enough to comment. I run Nouveu drivers with integrated gpu on an older machine.

FTouzain I did all the steps you describe here already (except unplug other drives)

I always unplug the other drives when I install something new. Every time. The other boots mess with each other. If you don't unplug the other drives then someone is giving boot orders and you won't know who.

But still---I had no idea you proceeded with fresh install as you told that guy a few responses up. So now the problem is no longer 'an update broke my boot' to 'I did a fresh install and get a black screen'?

🙂 I have to keep up, sorry!

At this point I know nothing except you have Grub installed on bios UEFI. Again. I did not think that was allowed to happen in installer but I've never tried Grub.

Go nuts----unplug everything and see if SOlus boots right up. It would rule a lot out, And a lot in.
You also never said (maybe you did?) if you spammed F12 and got a menu with all your distros on so you could manually choose.
I fear we are doing circles on somethings.

Axios

FTouzain As I say on bios updates the choice is yours.
You are like 12 bios updates behind (NEVER USE BETA BIOS) always update last non beta version.
I see with this particular bios you cant return to previous versions
Usually a 1 or 2 version jump normal doesnt solve much but above that it could solve issues.
Just read and understand it before doing update.
UEFI is strange animal sometimes
You have to do a solid process of elimination other wise you chase your tail.

Asianbullet has got a good post on order of doing things in tuff situations

brent

Axios
I wish I was that guy who was smart enough to say "if it's a graphics problem run inxi -xyx to confirm or had a list of commands to narrow it down to boot or graphics.

This site is loaded with people who could get to the root of graphics problem or boot problem with a snap of one command.

if we had one certainty there would be no tail-chasing as you say. Now OP has a new install maybe a new thread?

FTouzain

The end of the story.

First, I booted on a more recent live Solus USB key (the last).
I formated the whole system nvme, choosing mbr (intel, I realized it is the default on my nvme) instead of gpt.
I reinstalled completely Solus (the same way as previously) and restarted

here, I was able to boot (no booting menu, I arrive at Solus login page)

I got the "black screen after login bug"
I logged in TTY2, remove nvidia drivers, restarted

no booting

I restarted on Live Solus, do chroot (EFI), upgrade, installed lts kernel, checked clr-boot-manager, and miracle, I see my kernels AND one is selected (the last but not the good one, not the one used by the system, because, as described in the troubleshooting page:
eopkg info linux-lts | head -n2; uname -a gives two different results (I tried with linux-current too)
Therefore, I used sudo clr-boot-manager set-kernel com.solus-project.lts.6.6.83-266
I probably did a 'sudo eopkg up'
I rebooted, and now, I can login in Solus and graphical part is working after login windows (I restarted, it is still working).

I always have the error message of clr-boot-manager:

[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device

but it has no repercution on the booting capability or even sleep mode of the computer.

Thank you for your help.

FTouzain

For information.
I updated the bios of the motherboard and selected lts kernel and nvidia drivers:

with last stable reversible BIOS (UEFI) (meaning one that allow to come back to a previous bios): failed to boot
with the last "1" (same major) stable version of the BIOS (UEFI):
- it is working
- I don't have any error message with clr-boot-manager
- today update with new kernels worked perfectly

Thank you @Axios for your advices on BIOS motherboard updates (update to last reversible stable BIOS of motherboard, otherwise try earlier).

Great community, stability of my system seems to be back 🙂

Axios

FTouzain Cool glad it worked.

« Previous Page