Re: Leap 15.4 hangs on Terminate Plymouth boot screen
On 12/14/22 13:00, Jeffrey Taylor wrote:
After updating from 15.3 to 15.4 with "zypper dup", I can boot into runlevel 1 and run startx. Runlevels 2, 3, and the default (multi-user GUI) hang at the message in the title. Adding plymouth.enable at the end of the linux line in grub changes nothing. Any ideas or resources to debug? This is a Lenovo T520.
TIA, Jeffrey
I have had this problem more times than I can remember on my laptop with a Nvidia card in it. Solution - nuke plymouth (my choice): # rpm -e plymouth-dracut plymouth-scripts plymouth-branding-openSUSE plymouth-plugin-script plymouth plymouth-plugin-label-ft or kernel pass the kernel parameter on the kernel command line: "plymouth.enable=0" You will never hang-on-shutdown again.... -- David C. Rankin, J.D.,P.E.
Same result, only boots in runlevel 1 On Wed, Dec 14, 2022, 3:28 PM David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
After updating from 15.3 to 15.4 with "zypper dup", I can boot into runlevel 1 and run startx. Runlevels 2, 3, and the default (multi-user GUI) hang at
message in the title. Adding plymouth.enable at the end of the linux
On 12/14/22 13:00, Jeffrey Taylor wrote: the line in
grub changes nothing. Any ideas or resources to debug? This is a Lenovo T520.
TIA, Jeffrey
I have had this problem more times than I can remember on my laptop with a Nvidia card in it.
Solution - nuke plymouth (my choice):
# rpm -e plymouth-dracut plymouth-scripts plymouth-branding-openSUSE plymouth-plugin-script plymouth plymouth-plugin-label-ft
or kernel pass the kernel parameter on the kernel command line:
"plymouth.enable=0"
You will never hang-on-shutdown again....
-- David C. Rankin, J.D.,P.E.
On 15/12/2022 00.16, Jeffrey Taylor wrote:
Same result, only boots in runlevel 1
If you have uninstalled plymouth, the message can not be "Terminate Plymouth2, it has to be something else. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.4 (Legolas))
Still hangs. Last message is (from memory) Finished Creating List of Device Nodes. Jeffrey On Wed, Dec 14, 2022, 5:27 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
On 15/12/2022 00.16, Jeffrey Taylor wrote:
Same result, only boots in runlevel 1
If you have uninstalled plymouth, the message can not be "Terminate Plymouth2, it has to be something else.
-- Cheers / Saludos,
Carlos E. R.
(from openSUSE 15.4 (Legolas))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2022-12-15 a las 08:00 -0600, Jeffrey Taylor escribió:
Still hangs. Last message is (from memory) Finished Creating List of Device Nodes. Jeffrey
It is this region: Dec 13 13:18:47 Legolas systemd[1]: dracut-cmdline-ask.service: Deactivated successfully. Dec 13 13:18:47 Legolas systemd[1]: Stopped dracut ask for additional cmdline parameters. Dec 13 13:18:47 Legolas systemd[1]: Starting Cleanup udev Database... Dec 13 13:18:47 Legolas systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully. Dec 13 13:18:47 Legolas systemd[1]: Stopped Create Static Device Nodes in /dev. Dec 13 13:18:47 Legolas systemd[1]: kmod-static-nodes.service: Deactivated successfully. Dec 13 13:18:47 Legolas systemd[1]: Stopped Create List of Static Device Nodes. Dec 13 13:18:47 Legolas systemd[1]: systemd-vconsole-setup.service: Deactivated successfully. Dec 13 13:18:47 Legolas systemd[1]: Stopped Setup Virtual Console. Dec 13 13:18:47 Legolas systemd[1]: initrd-udevadm-cleanup-db.service: Deactivated successfully. Dec 13 13:18:47 Legolas systemd[1]: Finished Cleanup udev Database. Dec 13 13:18:47 Legolas systemd[1]: Reached target Switch Root. Dec 13 13:18:47 Legolas systemd[1]: Starting Switch Root... Dec 13 13:18:47 Legolas systemd[1]: Switching root. Dec 13 13:18:47 Legolas systemd-journald[164]: Journal stopped Dec 13 13:18:51 Legolas systemd-journald[164]: Received SIGTERM from PID 1 (systemd). Dec 13 13:18:51 Legolas systemd[1]: systemd 249.12+suse.142.g0cd50eedcc running in system mode (+PAM +AUD> Dec 13 13:18:51 Legolas systemd[1]: Detected architecture x86-64. You should check the log on yours. - -- Cheers Carlos E. R. (from openSUSE 15.4 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY5suvBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVUwYAniab4WNhtOPw2kb4iCfJ XBvUk/W/AKCSbIHyDgKbfOsjA901DGBaj095XA== =bKw0 -----END PGP SIGNATURE-----
Unplugging the Lenovo USB 2.0 port replicator allows the laptop to boot up completely. I'll check Bugzilla. Thanks for your help, Jeffrey On 12/14/22 15:28, David C. Rankin wrote:
On 12/14/22 13:00, Jeffrey Taylor wrote:
After updating from 15.3 to 15.4 with "zypper dup", I can boot into runlevel 1 and run startx. Runlevels 2, 3, and the default (multi-user GUI) hang at the message in the title. Adding plymouth.enable at the end of the linux line in grub changes nothing. Any ideas or resources to debug? This is a Lenovo T520.
TIA, Jeffrey
participants (3)
-
Carlos E. R. -
David C. Rankin -
Jeffrey Taylor