#[NVIDIA] Problems while Booting and KDE Problemt

182 messages · Page 1 of 1 (latest)

stuck wolf
#

RTX 3060 (tripple fan edition if it matters)
32gb ram
Ryzen 5 2700X

Known problems:
• Doesn‘t even come to the bootloader
Solution: reboot
• Kernel Panic
Solution: Reboot
• KDE Loading Screen Freeze
Reboot
• KDE full ui reset
Just wait until it reset
• Emergency mode
Reboot

UPDATE:
Now it more likely freezes, I just switched to hyprland instead of kde which improved a bit but not everything
SysRq + REISUB doesn‘t work
TTY doesn‘t work
The kernel is deadlocked

#

@tired fractal Heres the post btw, thanks

ashen auroraBOT
#

dkwtc. received a thank you cookie!

stuck wolf
#

Also, TTY doesn‘t work here ^^

#

• Whatever happened here
Solution: Reboot

copper spoke
tired fractal
#

Ok I am here

#

So let's go step by step, what nvidia drivers do you use?

#

What bootloader do you use?

#

@stuck wolf

stuck wolf
stuck wolf
copper spoke
stuck wolf
#

oh read it wrong

#

yeah bootloader wait

#

systemd

copper spoke
#

You can try mounting your partitions and chrooting, and then running pacman -Qqn | pacman -S - to reinstall all packages

#

If the issues is from a improperly installed package then that could help

tired fractal
#

Okay I use systemd-boot, what error do you have when booting?

stuck wolf
#

that's the only error I can see

tired fractal
#

Oh so that is the error when booting, right?

#

So you enter bootloader, boot from your .conf(arch linux) and see that error

stuck wolf
tired fractal
#

Ok, do you dual boit

#

Boot*

stuck wolf
stuck wolf
tired fractal
#

lsblk -f

stuck wolf
#

[dervarex@stuck wolf ~]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 6BF7-5900 890.5M 13% /boot
└─sda2 btrfs c419b60a-9152-4ded-88e7-dfc54066b4ef 107.2G 51% /var/log
/var/cache/pacman/pkg
/home
/
sdb
└─sdb1 ext4 1.0 da54a552-24a9-441c-ae96-a7a9282cd6ac
zram0 swap 1 zram0 2fab630c-2231-4268-8f7d-3ac9f4f54cff [SWAP]
nvme0n1
└─nvme0n1p1 ext4 1.0 endeavouros 1d6bb68a-22f0-4c51-aeca-2e13c22ff269 714.3G 17% /run/media/dervarex/endeavouros
[dervarex@stuck wolf ~]$

tired fractal
#

Let me see partitions, if you dual boot with windows and you use same esp then sometimes windows eats your esp

tired fractal
stuck wolf
#

i dual boot with linux

#

[dervarex@dervarex ~]$ lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda ├─sda1 vfat FAT32 6BF7-5900 890.5M 13% /boot └─sda2 btrfs c419b60a-9152-4ded-88e7-dfc54066b4ef 107.2G 51% /var/log /var/cache/pacman/pkg /home / sdb └─sdb1 ext4 1.0 da54a552-24a9-441c-ae96-a7a9282cd6ac zram0 swap 1 zram0 2fab630c-2231-4268-8f7d-3ac9f4f54cff [SWAP] nvme0n1 └─nvme0n1p1 ext4 1.0 endeavouros 1d6bb68a-22f0-4c51-aeca-2e13c22ff269 714.3G 17% /run/media/dervarex/endeavouros [dervarex@dervarex ~]$

#

Arch Vanilla and EndevourOS

tired fractal
#

Can you confirm there is only a FAT32 type

#

Partition

stuck wolf
tired fractal
#

Ok better

#

run lsblk -f

#

I need to see type

#

You could be running same esp though

stuck wolf
tired fractal
#

Ok so you use same esp(efi system partition), so I know that with windows it can cause problems, but I don't really know if with linux it can have such issues

#

Can I see your /boot dir

stuck wolf
#

[dervarex@stuck wolf boot]$ ls -R
.:
amd-ucode.img EFI initramfs-linux.img loader vmlinuz-linux

./EFI:
BOOT Linux systemd

./EFI/BOOT:
BOOTX64.EFI

./EFI/Linux:

./EFI/systemd:
systemd-bootx64.efi

./loader:
entries entries.srel keys loader.conf random-seed

./loader/entries:
2026-01-25_18-54-38_linux.conf

./loader/keys:
[dervarex@stuck wolf boot]$

tired fractal
#

So how do you boot to endeavourous

stuck wolf
#

other ssd and I didn't boot that for half an eternity

#

in that ssd must be moos

#

theres a new ecosystem in that drive xD

tired fractal
#

When you run lsblk -f did you had the ssd plugged in?

stuck wolf
#

yeah it's my main drive

#

but I boot from my old main

#

it's complicated

tired fractal
#

what kernel do you have

stuck wolf
#

Kernel: Linux 6.18.9-arch1-2

tired fractal
#

try checking if removing normal one and installing lts fixes your issues

stuck wolf
#

i used lts kernel in endevour before it was worse

tired fractal
#

ever tried with arch?

#

try, worst case scenario you reinstall the normal one

stuck wolf
#

endevour is arch - kinda
it's based on arch with preinstalled stuff

tired fractal
#

yeah I know, but hey maybe it works

stuck wolf
#

okay do you know how to do that?

tired fractal
#

I don't know, and again you can just reinstall normal one if something goes wrong

#

sudo pacman -S linux-lts

#

sudo pacman -Rs linux (optional), you can keep it

#

then change .conf in your systemd configuration

stuck wolf
#

okay I'm gonna do that tomorrow
wanna show my friend mint linux today so 5 mins before he calls me installing another kernel maybe ain't a good idea haha
thanks

tired fractal
#

lmao, speedrun

#

yeah tell me how it goes

stuck wolf
# tired fractal lmao, speedrun

my internet be like:
server!!!!
yeah???
a zero!!!
ok
server!!!
yeah???
a one!!!
ok
server!!!
wait a sec
ok now what???
a 1!!!
ah sorry can you say that whole thing again?

tired fractal
#

dude how slow is it lol

#

in MB/S

stuck wolf
#

my school's wifi is about 200-300 times faster so yeah

tired fractal
#

oh

stuck wolf
#

download mint linux iso(2gb)?
2d 8h 32m
that's what firefox tells me
torrent of course is a bit faster but still more than 1d

tired fractal
#

oh

stuck wolf
#

(My schools speed)

tired fractal
#

that's fast!

stuck wolf
tired fractal
stuck wolf
#

Not every time

#

I didn‘t switch kernel yet

tired fractal
#

Oh, so it seems like it is a read error with vmlinuz-linux

#

Could you check if the permissions are right and your .conf entry

#

Share them here

stuck wolf
#

What permissions exactly and where can I find my boot conf?

tired fractal
#

permissions like rw-r-r...
.conf in /boot/loader/entries/.conf

#

IIRC, if the .conf are not there try searching those dirs

stuck wolf
#

Where you mean check permission, in /boot?

tired fractal
#

Of vmlinuz-linux, yes in /boot

#

And the other files

stuck wolf
#

`
[dervarex@dervarex ~]$ ls -lR /boot
/boot:
total 134344
-rwxr-xr-x 1 root root 307200 Jan 11 04:52 amd-ucode.img
drwxr-xr-x 5 root root 4096 Jan 25 19:58 EFI
-rwxr-xr-x 1 root root 120634499 Feb 24 19:05 initramfs-linux.img
drwxr-xr-x 4 root root 4096 Feb 25 18:05 loader
-rwxr-xr-x 1 root root 16613568 Feb 22 15:06 vmlinuz-linux

/boot/EFI:
total 12
drwxr-xr-x 2 root root 4096 Jan 25 19:58 BOOT
drwxr-xr-x 2 root root 4096 Jan 25 19:58 Linux
drwxr-xr-x 2 root root 4096 Jan 25 19:58 systemd

/boot/EFI/BOOT:
total 132
-rwxr-xr-x 1 root root 134656 Jan 6 18:29 BOOTX64.EFI

/boot/EFI/Linux:
total 0

/boot/EFI/systemd:
total 132
-rwxr-xr-x 1 root root 134656 Jan 6 18:29 systemd-bootx64.efi

/boot/loader:
total 20
drwxr-xr-x 2 root root 4096 Jan 25 19:58 entries
-rwxr-xr-x 1 root root 6 Jan 25 19:58 entries.srel
drwxr-xr-x 2 root root 4096 Jan 25 19:58 keys
-rwxr-xr-x 1 root root 29 Jan 25 19:58 loader.conf
-rwxr-xr-x 1 root root 32 Feb 25 18:05 random-seed

/boot/loader/entries:
total 4
-rwxr-xr-x 1 root root 253 Jan 25 19:58 2026-01-25_18-54-38_linux.conf

/boot/loader/keys:
total 0
[dervarex@dervarex ~]$
`

#

so now I would have time to switch bootloader

tired fractal
#

Also append arch install in this thread

stuck wolf
#

yeah i used archinstall

#

sorry i forgot to mention that

tired fractal
#

No worries

#

Permissions seem right, also the .conf

stuck wolf
#

if you want I can switch bootloader now

tired fractal
stuck wolf
#

where can I see it?

tired fractal
#

You booted in between?

#

Like

stuck wolf
#

yes had to

#

as boot after that failed too

tired fractal
#

Oh, see if it happens again. If it does just take a photo xD

#

Or

#

Run

#

journalctl -b -<number of boots ago>

#

@stuck wolf

stuck wolf
#

I don‘t even know how many boots that was
But if it happenes again yes I‘m gonna do that
So for example if I boot and error and then boot and it works it‘s 2 boots ago

tired fractal
#

It's one

#

Because you
Boot -> Fail -> Second Boot -> journalctl -b -1

stuck wolf
#

Heres the rest:

#

@tired fractal

#

I don‘t understand any of that logs here

#

Just a bit at the beginning

tired fractal
#

You got some problems with kde plasma

#

Like at a point it asks if wayland was dead

#

It also complains about some org.kde parts not found. Have you installed full kde plasma + optional apps?

stuck wolf
#

F*CK EVEN MY TTY FREEZES LMAO

#

Btw I also installed lts headers

#

Nice somehow i managed to do it

tired fractal
#

Okay great, does lts work better now?

tired fractal
#

So you use wayland

#

Because kde is based on wayland

stuck wolf
stuck wolf
#

My brain doesn’t know a difference between these two words but theres a big difference

stuck wolf
#

Why does this take so long?

copper spoke
#

You may want to try adding -p 3 to the journalctl so only errors are shown

stuck wolf
#

I’ll send you the file

#

With only error

#

why does this start a kde plasma session

#

i use hyprland

#

i don't want kde

tired fractal
#

uninstall kde

stuck wolf
#

I don‘t need it anyways so no problem

stuck wolf
#

Works better but still not great yet

#

Tf boot screen freezed

tired fractal
#

I have no idea

#

Lmao

stuck wolf
#

here

#

journalctl -b 1
because boot error -> boot worked and journalctl

stuck wolf
# tired fractal I have no idea

So I found that there are 12 unrepairable errors on my disk which btrfs couldn‘t fix, deleted them(minecraft libs and sole crash logs) and now I see this here

#

Not even REISUB works…

Alt + SysRq + R
Alt + SysRq + E
Alt + SysRq + I
Alt + SysRq + S
Alt + SysRq + U
Alt + SysRq + B

Nothing
So the kernel is deadlocked
(I sometimes read the wiki too)

tired fractal
#

Can you reinstall?

#

Also could it be an hard drive that is going to die?

stuck wolf
stuck wolf
#

On a newer ssd too

#

1TB

#

NVME

#

Is there any guide how to not use archinstall and instead do it yourself?

stuck wolf
tired fractal
tired fractal
stuck wolf
tired fractal
#

Not new one, just let it die

#

The cmos

stuck wolf
#

How to do that?

copper spoke
#

Yeah that's like the worst way to reset your CMOS lol