on my laptop 1=ASUS vivobook pro N552VW-FY204T (2016) running leap 16.0 and KDE GPU GTX960M after the last update it stuck at
Loading Linux 6.12.0-160000.33-default ...
Loading initial ramdisk
I tried also with kernel Linux 6.12.0-160000.28-default in recovery mode but without success.
what can I do to have my laptop working?
Rollback to a snapshot from before the last update?
I have no btrfs
How long did you wait?
10 minutes
When your system uses grub2-bootloader and selinux, you might try to start it with selinux=0.
If it is using apparmor instead, make sure that the option security=apparmor is part of the grub-boot command.
You can try both possibilities temporarily by adding one or the other option to the end of the line starting with linux … in the grub boot-menue.
I use selinux and I’m booting with selinux=0
also space in / and /home is tenth of GB
@pier_andreit do you have another system to see if it’s actually booted by pinging or remote login say over ssh?
If you add nomodeset to the boot options?
Why are you not using enforcing?
Else your going to have to boot from a rescue device and chroot in and see if the journal provides any info.
yes I have, what I have to do? I don’t know the IP address…
I tried with tumbleweed live and it works
added selinux=0 and nomodeset but nothing change
what is enforcing??
please can you give me more instructions about chrooting and copy the journal?
Is it doable booting with systemrescuecd or tumbleweed live that seems more simple?
Run sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: actual (secure)
Max kernel policy version: 35
If you boot from a rescue system and your using dhcp check the output from ip a on a reboot it will get the same ip address unless you router setup has a very short release period…
From the rescue system;
mount /dev/<root-device-name> /mnt
mount -o bind /dev /mnt/dev
mount -o bind /run /mnt/run
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
chroot /mnt
mount -a
Should be able to run journalctl -b to see the last boot or maybe add a -1
I tried to connect via ethernet cable but unsuccessfully
with tumbleweed live
--- 192.168.1.162 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 30.782/90.246/210.494/70.912 ms
pla@plaTW:~> ping 192.168.1.18
PING 192.168.1.18 (192.168.1.18) 56(84) bytes of data.
64 bytes from 192.168.1.18: icmp_seq=1 ttl=64 time=2.20 ms
64 bytes from 192.168.1.18: icmp_seq=2 ttl=64 time=0.981 ms
64 bytes from 192.168.1.18: icmp_seq=3 ttl=64 time=1.12 ms
^Crebooted normally after about 5minutes after Loading initial ramdisk
--- 192.168.1.18 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.981/1.431/2.197/0.544 ms
pla@plaTW:~> ping 192.168.1.18
PING 192.168.1.18 (192.168.1.18) 56(84) bytes of data.
From 192.168.1.125 icmp_seq=9 Destination Host Unreachable
From 192.168.1.125 icmp_seq=10 Destination Host Unreachable
From 192.168.1.125 icmp_seq=11 Destination Host Unreachable
^C
--- 192.168.1.18 ping statistics ---
14 packets transmitted, 0 received, +3 errors, 100% packet loss, time 13301ms
pipe 4
pla@plaTW:~>I chrooted
and here is the logs from journalctl of 07jun2026
https://paste.opensuse.org/pastes/a2c6c73e54b8
I chrooted again and run sestatus
it result
SELinux status: disabled
@pier_andreit So that log was before the update or after? Looks like you brought it out of suspend and then updated and shut the system down?
Is there a log after that one?
I posted at 4:51pm and it is after the update
the log ends at 16:33 so I don’t remember if 16:33 is before or after the update
anyway I run
journalctl > myfile2.txt
to get all the logs in a file becouse journalctl -b was empty and journalctl -b -1 > myfile1.txt ends at may 30
anyway the june 07 was the last log.
have I to try to do some other?
I don’t have an answer, maybe the kernel did not get installed properly. So boot into a chroot environment, then chroot as above then run dracut `` 6.12.0-160000.33-default and then ctrl+d to exit and reboot…
chrooted but this is the result>
linux@localhost:~> su -
localhost:~ # mount /dev/sda6 /mnt
localhost:~ # mount -o bind /dev /mnt/dev
localhost:~ # mount -o bind /run /mnt/run
localhost:~ # mount -o bind /proc /mnt/proc
localhost:~ # mount -o bind /sys /mnt/sys
localhost:~ # chroot /mnt
localhost:/ # mount -a
localhost:/ # dracut `` 6.12.0-160000.33-default
realpath: /lib/modules/6.18.7-1-default: No such file or directory
dracut[F]: Cannot find module directory
dracut[F]: and --no-kernel was not specified
localhost:/ # dracut `` 6.12.0-160000.33-default
realpath: /lib/modules/6.18.7-1-default: No such file or directory
dracut[F]: Cannot find module directory
dracut[F]: and --no-kernel was not specified
localhost:/ # dracut 6.12.0-160000.33-default
realpath: /lib/modules/6.18.7-1-default: No such file or directory
dracut[F]: Cannot find module directory
dracut[F]: and --no-kernel was not specified
localhost:/ #