[SOLVED]nouveau kernel module black screen after login & battery

cernunnos · 2023-03-09 10:30:20

Yes maybe it was my fault because I edited the /etc/default/grub file but did't launch the

grub-mkconfig -o /boot/grub/grub.cfg

So i installed again the nvidia package, added ibt=off to GRUB_CMDLINE_LINUX_DEFAULT and applied the changes with grub-mkconfig and the output was

[root@cernunnos ~]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

But the grub doesn't start again so I have broke it.

I think that now it's the right time to reinstall it.

Last edited by cernunnos (2023-03-09 12:43:37)

seth · 2023-03-09 13:15:29

What makes you believe you won't arrive at the same position again?

Post the current grub.cfg and "the backup file that [you] have created before the mess"

cernunnos · 2023-03-09 13:42:24

seth wrote:

What makes you believe you won't arrive at the same position again?

Never said that, I really want understand how this system works, and also know that it can happen.

Post the current grub.cfg

Too late, I did not do the backup file before I did the last grub-mkconfig (my bad... Last time I renamed that backup file to "grub.cfg" and then applied changes).
But when I applied the last changes it didn't got any errors.

But a thing that I have noticed is that now the actual grub.cfg is formatted like the old grub.cfg file that I got when grub-customizer broke it...

Here's the actual grub.cfg I got with grub-mkconfig --> https://pastebin.com/FJfDGBaQ
Here the grub.cfg that grub-customizer generated causing the mess --> https://pastebin.com/CYiiwfMA

cernunnos · 2023-03-09 14:03:45

Okk now I understand...It's possible that grub-mkconfig went wrong because that grub-customizer already modified my /etc/default/grub. So the fact that I restored only the file /boot/grub/grub.cfg means nothing, because the important changes were made to the writable config file.
So I could do the backup of /etc/default/grub instead of grub.cfg, which is generated by /etc/default/grub
That's why now the grub.cfg output is practically identical to the one that i renamed to grub.cfg_oldbad

Well, once I can't restore the /etc/default/grub, would be better if I directly reinstall the grub?
With

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

cernunnos · 2023-03-09 14:43:16

I'm glad to announce that finally I did it.
I reinstalled the grub, set the ibt=off to /etc/default/grub and applied changes.
In the end I installed the nvidia package and rebooted it.
Thanks a lot for the help!
I know this was not a huge trouble, but for me this was the very first time that I interacted with chroot and kernel modules, so I'm glad I could resolve it. Thanks for your time and your patience.

I'm marking as solved this topic.

Arch Linux

#26 2023-03-09 10:30:20

Re: [SOLVED]nouveau kernel module black screen after login & battery

#27 2023-03-09 13:15:29

Re: [SOLVED]nouveau kernel module black screen after login & battery

#28 2023-03-09 13:42:24

Re: [SOLVED]nouveau kernel module black screen after login & battery

#29 2023-03-09 14:03:45

Re: [SOLVED]nouveau kernel module black screen after login & battery

#30 2023-03-09 14:43:16

Re: [SOLVED]nouveau kernel module black screen after login & battery

Board footer