[SOLVED]Frozen screen in Linux kernel

jojo06 · 2024-02-05 06:15:50

I have installed linux-lts. After rebooting my pc, its booted into linux-lts. And i start to tinker with the in grub options.
I set

GRUB_TIMEOUT=3 (it was 5)
GRUB_DEFAULT=save
GRUB_SAVEDEFAULT=true

to manually select Linux once time, and it will be saved preference.

After these settings and first reboot; in hyprland firefox ran (from exec-once) executed with 2 seconds delay and after firefox, gBar ran (from exec-once) also with 2 seconds delay. It was slower than usual. I realize, something went wrong.**

optimus-manager might be caused the problem (it was problematic because it is not working in hyprland -removed now-)
nvx off (accidently i turned of gpu, and screen gone blank. All the problem start after this)

The problem starts in here:

Its now booting from Linux automaticly. In tty i login successfully but after 3-5 seconds later, its frozen. The cursor stops blinking. Cannot type or go to tty2.
I tried to intervene the GRUB_TIMEOUT with using arrow key in grub loader - stop auto select in 3 seconds - (for make it longer than 3 seconds) **in the forum i read, if grub_timeout is instant or lower, it can cause some problems.

New settings:

GRUB_TIMEOUT=3
GRUB_DEFAULT="1>2"
GRUB_SAVEDEFAULT=true

Now im in Linux-lts (initramfs) and after tty login, if run `nvx on` and than `Hyprland` its all good. But if i run `Hyprland` command first, its get frozen after output. It took a few restart to figure it out tho. And this is not working on Linux kernel.

Might give a hint:

Feb 04 21:28:42 roses kernel: firefox[672]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set

My hooks:

HOOKS=(base udev autodetect modconf keyboard kms keymap consolefont block filesystems fsck)

Nvidia set in kernel modules
Fast boot: enabled
Secure boot: enabled = Other OS option selected (cannot disable, other option is EUFI Windows) --even only Arch installed--

Really sorry for the shitty readability, and making it hard to understand. I just dont know the words to describe it but i tried my best with full effort.

Last edited by jojo06 (2024-02-06 10:57:44)

seth · 2024-02-05 09:48:43

remove nvidia-exec, then please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

jojo06 · 2024-02-05 11:11:36

seth wrote:

remove nvidia-exec, then please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

Forgive me, i dont know how to remove nvidia-exec. Is it same thing with ignore blacklist tho ? Can you please share me the code for this ?

Update:
In Linux kernel; run the command `nvx on` and after starting Hyprland is working. Changed boot options a bit more, cant hear the beep sound.

nvx is a good option for switching gpu's ?

seth · 2024-02-05 14:23:25

nvidia-exec is what provides nvx and unlikely what you want.
You installed the package, so remove it.

jojo06 · 2024-02-05 21:27:21

http://0x0.st/HkJF.txt
Right, that was the package name for nvx, i uninstalled it.
Nvidia is on and working now, before login i use `sudo modprobe -a nouveau` but active GPU is Nvidia now.
So cant i switch between GPU`s ?

In boot options, i uncomment the `GRUB_INIT_TUNE="480 440 1"` but i cant see the beep sound.
I added `splash` nothing changed tho.

seth · 2024-02-05 21:52:19

before login i use `sudo modprobe -a nouveau` but active GPU is Nvidia now

Sorry, incoprehensible.

So cant i switch between GPU`s ?

https://wiki.archlinux.org/title/PRIME

You cannot see sound anyway, but you'll have to re-run grub-mkconfig in order for changes to /etc/default/grub to apply.
For splash see https://wiki.archlinux.org/title/Plymouth
Also that's all vastly off topic.

jojo06 · 2024-02-05 23:24:48

seth wrote:

before login i use `sudo modprobe -a nouveau` but active GPU is Nvidia now
Sorry, incoprehensible.
So cant i switch between GPU`s ?
https://wiki.archlinux.org/title/PRIME
You cannot see sound anyway, but you'll have to re-run grub-mkconfig in order for changes to /etc/default/grub to apply.
For splash see https://wiki.archlinux.org/title/Plymouth
Also that's all vastly off topic.

I add nouveau to modprobe by this command: `sudo modprobe -a nouveau` after login in tty. But my active and running GPU is Nvidia.

I ran `sudo grub-mkconfig -o /etc/default/grub` after every changes yes. Oh i meant by `see` is hear sorry.
So splash with alone means nothing ? For that fancy grub with Arch logo, which Plymouth should i prefer ?

Yes it is sorry. I thought, while we are talking about grub, i can ask that too and might be problem on that one too.

So is the problem occur because of nvidia-exec ?

Last edited by jojo06 (2024-02-06 07:00:00)

seth · 2024-02-06 09:27:09

sudo modprobe -a nouveau

this will in doubt load the module which is pointless to harmful if you're using the binary nvidia blob

So is the problem occur because of nvidia-exec ?

What problem?
If you explicitly deactivate your GPU, using nvidia-exec or optimus-manager or bumblebee or whatever - it won't be available.

Read https://wiki.archlinux.org/title/NVIDIA_Optimus - use deepl.com for sections you don't really understand and google up information about nvidia optimus in your native tongue.

---

which Plymouth should i prefer

There's only one "plymouth" and the only advice on what to do with it you'll ever get from me is to not use it.
Hiding the boot status behind some animation yo're not looking at anyway is flat out dumb.

Arch Linux

#1 2024-02-05 06:15:50

[SOLVED]Frozen screen in Linux kernel

#2 2024-02-05 09:48:43

Re: [SOLVED]Frozen screen in Linux kernel

#3 2024-02-05 11:11:36

Re: [SOLVED]Frozen screen in Linux kernel

#4 2024-02-05 14:23:25

Re: [SOLVED]Frozen screen in Linux kernel

#5 2024-02-05 21:27:21

Re: [SOLVED]Frozen screen in Linux kernel

#6 2024-02-05 21:52:19

Re: [SOLVED]Frozen screen in Linux kernel

#7 2024-02-05 23:24:48

Re: [SOLVED]Frozen screen in Linux kernel

#8 2024-02-06 09:27:09

Re: [SOLVED]Frozen screen in Linux kernel

Board footer