Mageia forum

I have installed Mageia 6 in my UEFI alone supporting asus laptop along with windows 10. Mageia installs fine and works without any issues. This morning, the system reports there are some updates available and I updated and rebooted the laptop. It is not showing login screen instead it hangs on the splash screen for a long time. If i select Advance boot options for Magiea in grub , it lists Mageia 4.9.35 and 4.14.20. I am able to login with 4.9.35 option, however 4.14.20 gets freezed in splash screen. I searched and I didn't found any option to recover this. Can anyone help me to fix this issue?

Thanks in advance

Please show the output of

Code: Select all

lspcidrake -v | grep VGA
rpm -qa --last|head -50

I am getting the following output

Code: Select all

[name@localhost ~]$ lspcidrake -v | grep VGA
Card:Intel 810 and later: Intel Corporation|Device 591b [DISPLAY_VGA] (vendor:8086 device:591b subv:1043 subd:15e0) (rev: 04)
[name@localhost ~]$ rpm -qa --last |head -50
isodumper-gtk-0.59-1.mga6.noarch              Mon 26 Feb 2018 09:57:25 AM IST
isodumper-0.59-1.mga6.noarch                  Mon 26 Feb 2018 09:57:25 AM IST
python3-yui-1.1.1-1.mga6.x86_64               Mon 26 Feb 2018 09:57:24 AM IST
python3-parted-3.10.7-2.mga6.x86_64           Mon 26 Feb 2018 09:57:24 AM IST
lib64yui7-mga-ncurses-1.0.2-3.mga6.x86_64     Mon 26 Feb 2018 09:57:24 AM IST
lib64yui7-ncurses-2.47.6-1.mga6.x86_64        Mon 26 Feb 2018 09:57:23 AM IST
lib64yui7-mga-gtk-1.0.2-3.mga6.x86_64         Mon 26 Feb 2018 09:57:23 AM IST
lib64yui7-mga-1.0.7-3.mga6.x86_64             Mon 26 Feb 2018 09:57:23 AM IST
lib64yui7-gtk-2.44.7-1.mga6.x86_64            Mon 26 Feb 2018 09:57:23 AM IST
lib64yui7-3.2.7-1.mga6.x86_64                 Mon 26 Feb 2018 09:57:22 AM IST
microcode-0.20180108-1.mga6.nonfree.noarch    Sun 25 Feb 2018 11:43:07 PM IST
rtlwifi-firmware-20171220-1.mga6.nonfree.noarch Sun 25 Feb 2018 11:43:06 PM IST
ralink-firmware-20171220-1.mga6.nonfree.noarch Sun 25 Feb 2018 11:43:06 PM IST
hplip-model-data-3.17.10-1.mga6.x86_64        Sun 25 Feb 2018 11:43:06 PM IST
radeon-firmware-20180118-1.mga6.nonfree.noarch Sun 25 Feb 2018 11:43:05 PM IST
kernel-userspace-headers-4.14.20-1.mga6.x86_64 Sun 25 Feb 2018 11:43:05 PM IST
lib64hpip0-3.17.10-1.mga6.x86_64              Sun 25 Feb 2018 11:43:04 PM IST
kernel-firmware-nonfree-20171220-1.mga6.nonfree.noarch Sun 25 Feb 2018 11:43:04 PM IST
iwlwifi-firmware-20171220-1.mga6.nonfree.noarch Sun 25 Feb 2018 11:42:59 PM IST
cpupower-4.14.20-1.mga6.x86_64                Sun 25 Feb 2018 11:42:59 PM IST
lib64nm-glib-vpn1-1.8.6-1.mga6.x86_64         Sun 25 Feb 2018 11:42:57 PM IST
lib64nmclient-gir1.0-1.8.6-1.mga6.x86_64      Sun 25 Feb 2018 11:42:57 PM IST
cups-filters-1.13.4-2.2.mga6.x86_64           Sun 25 Feb 2018 11:42:57 PM IST
kernel-desktop-latest-4.14.20-1.mga6.x86_64   Sun 25 Feb 2018 11:42:56 PM IST
kernel-desktop-4.14.20-1.mga6-1-1.mga6.x86_64 Sun 25 Feb 2018 11:42:56 PM IST
lib64qpdf18-7.1.1-1.mga6.x86_64               Sun 25 Feb 2018 11:42:51 PM IST
lib64nm-glib4-1.8.6-1.mga6.x86_64             Sun 25 Feb 2018 11:42:51 PM IST
lib64networkmanager-gir1.0-1.8.6-1.mga6.x86_64 Sun 25 Feb 2018 11:42:51 PM IST
lib64cups-filters1-1.13.4-2.2.mga6.x86_64     Sun 25 Feb 2018 11:42:51 PM IST
lib64nm-util2-1.8.6-1.mga6.x86_64             Sun 25 Feb 2018 11:42:50 PM IST
libgomp1-5.5.0-1.mga6.x86_64                  Sun 25 Feb 2018 11:42:32 PM IST
libxml2-python-2.9.7-1.mga6.x86_64            Sun 25 Feb 2018 11:42:31 PM IST
poppler-0.52.0-3.6.mga6.x86_64                Sun 25 Feb 2018 11:42:30 PM IST
libxml2-utils-2.9.7-1.mga6.x86_64             Sun 25 Feb 2018 11:42:30 PM IST
lib64wayland-cursor0-1.14.0-1.3.mga6.x86_64   Sun 25 Feb 2018 11:42:30 PM IST
p7zip-16.02-2.1.mga6.x86_64                   Sun 25 Feb 2018 11:42:29 PM IST
lib64ruby2.2-2.2.8-1.1.mga6.x86_64            Sun 25 Feb 2018 11:42:29 PM IST
lib64kms1-2.4.89-1.mga6.x86_64                Sun 25 Feb 2018 11:42:29 PM IST
x11-driver-video-ati-7.10.0-1.mga6.x86_64     Sun 25 Feb 2018 11:42:28 PM IST
lib64gd3-2.2.5-2.mga6.x86_64                  Sun 25 Feb 2018 11:42:28 PM IST
lib64xatracker2-17.3.2-1.1.mga6.x86_64        Sun 25 Feb 2018 11:42:27 PM IST
lib64ncurses5-6.0-8.1.mga6.x86_64             Sun 25 Feb 2018 11:42:27 PM IST
rsync-3.1.2-1.3.mga6.x86_64                   Sun 25 Feb 2018 11:42:26 PM IST
nscd-2.22-27.mga6.x86_64                      Sun 25 Feb 2018 11:42:26 PM IST
lib64gcab1.0_0-0.7-1.1.mga6.x86_64            Sun 25 Feb 2018 11:42:26 PM IST
x11-driver-video-intel-2.99.917-42.mga6.x86_64 Sun 25 Feb 2018 11:42:25 PM IST
x11-driver-video-amdgpu-1.4.0-1.mga6.x86_64   Sun 25 Feb 2018 11:42:25 PM IST
lib64mariadb18-10.1.30-1.mga6.x86_64          Sun 25 Feb 2018 11:42:25 PM IST
bind-utils-9.10.6.P1-1.mga6.x86_64            Sun 25 Feb 2018 11:42:24 PM IST
tkinter-2.7.13-1.1.mga6.x86_64                Sun 25 Feb 2018 11:42:23 PM IST

do you have proprietary wifi card ?

if so you may have to wait for the wifi driver to build and then to be installed.
this would occur every time a new kernel is installed.

I installed on the laptop. My laptop is https://www.asus.com/Laptops/ASUS-FX553VD/ which I believe it is a proprietary. Is it possible to uninstall the latest update and revert back to old working kernal? or How long I have to wait to get the WIFI driver build?

from the spec sheet it does not specify your wifi brand.

as root

Code: Select all

lspcidrake -v | grep -iE "wlan|wifi|wireless|net"

and post back.

if you are using grub2 as your boot menu (likely if you have UEFI) it will remember your last boot entry, i.e. which-ever kernel you last used, so there is no requirement to remove your new kernel.

when you get a new kernel installed, if you are using a proprietary driver, it is built by your system and installed on the fly, the first time you boot the new kernel.
depending on your system it can take from 3 to 10 minutes to build and install.
(I have an old(er) laptop with an nvidia driver that took over 30 minutes to build and install the drivers)

for subsequent boots of the kernel, the driver is already built and installed, so, the boot time is back to normal.

it is possible that the driver that you have already installed on the Mageia 4.9.35 is not compatible with the 4.14.20.

try also starting the Mageia 4.14.20 in failsafe mode.
this will just present a scrolling text screen and if there is a problem will stop with something like "a start ..... will wait for 3 minutes 30 seconds ...."

premkumaru wrote:This morning, the system reports there are some updates available and I updated and rebooted the laptop. It is not showing login screen instead it hangs on the splash screen for a long time.

How long did you wait?

Also, when you see the splash screen, just press the escape key and you will get text output which shows you what is currently happening. I believe it's the dkms rebuild that benmc mentioned, which might take a few minutes.

doktor5000 wrote:Also, when you see the splash screen, just press the escape key and you will get text output which shows you what is currently happening. I believe it's the dkms rebuild that benmc mentioned, which might take a few minutes.

If so, there should be a message displayed on the splash screen telling you what driver is being built/installed.

doktor5000 wrote:

premkumaru wrote:This morning, the system reports there are some updates available and I updated and rebooted the laptop. It is not showing login screen instead it hangs on the splash screen for a long time.

How long did you wait?

Also, when you see the splash screen, just press the escape key and you will get text output which shows you what is currently happening. I believe it's the dkms rebuild that benmc mentioned, which might take a few minutes.

I have waited for 15 to 20 Minutes. But the splash image is running on the screen

martinw wrote:

doktor5000 wrote:Also, when you see the splash screen, just press the escape key and you will get text output which shows you what is currently happening. I believe it's the dkms rebuild that benmc mentioned, which might take a few minutes.

If so, there should be a message displayed on the splash screen telling you what driver is being built/installed.

I attached the screen shot at the time of hanging

I spot in that screen that kworker is blocked.
But i guess kworker should not be started at all until after kernel module rebuild, right?
Can you at boot menu select to start in safe mode, and have a look in the journal?
Ask if you do not know or find on the forum how to do
Also, you could try urpmi --auto-up in safe mode if you have ethernet to internet available.

urpmi --auto-up says all the packages are up to date.
I tried that command in recovery mode as a root user. (I am assuming that recovery mode is safe made)

I don't know what is KWorker. Sorry for that

It is really nice to getting help from different parts of the world. Thank you all friends for your answers. I am thinking about reinstalling using my existing mageia ISO file if I am unable to solve this.

You could try to increase the CONFIG_RCU_CPU_STALL_TIMEOUT by using the kernel parameter rcu_cpu_stall_timeout as described at https://www.kernel.org/doc/Documentatio ... llwarn.txt

Also, if you're not using the proprietary nvidia driver, you could try using nouveau.runpm=0 as kernel parameter.

My idea was that as i saw "kworker" on your screen it is an indication it is not stuck at compiling, and is attempting to run KDE/plasma but i may be wrong.

To see what is happening: first boot in this way that it hangs, and make sure to bring it down in a controlled manner so system log (journal) is saved, meaning: do not cut power. It is OK to either:
o Press Alt+F2 and get a prompt, log in as root, and issue "reboot"
o Hold down Ctrl and quickly hit backspace twice
o Press power button for 2 seconds ( >4 s usually cuts power immediately)

Then next boot you can view that log; as root at the prompt issue:
# journalctl --boot=-1
Navigate with buttons end, pgup, etc.
For future reference you may want to store the log as text:
# journalctl --boot=-1 > nameyourlogfile.txt
You can use grep for filtering, simple example:
grep ERROR yourlogfile.txt

To launch it either boot in... ah yes recovery mode it is named
- or select the working configuration so you get to desktop, and then open a terminal on your desktop and do that there.

( If you want to know more of journal: https://www.freedesktop.org/software/systemd/man/journalctl.html )

An experiment would be to change graphics driver to something simple and reliable:
Boot in safe mode and launch drakx11. Select Xorg vesa. OK and type reboot.

premkumaru wrote:I am thinking about reinstalling using my existing mageia ISO file if I am unable to solve this.

As you say that the 4.9.35 kernel does work why not just use that until the problem is found?

morgano wrote:My idea was that as i saw "kworker" on your screen it is an indication it is not stuck at compiling, and is attempting to run KDE/plasma but i may be wrong.

kworker is a placeholder process for kernel worker threads, which perform most of the actual processing for the kernel, especially in cases where there are interrupts, timers, I/O, etc. See e.g. https://askubuntu.com/a/52299/329633

At that early point in the boot process, it cannot be KDE/plasma, as a login manager has not even been started.

going by your photo there is something holding up the system before 112 seconds.
it should have presented the login greeter before 55 seconds.

anyway, to remove the suspect kernel, boot up using the 4.9.35 kernel
either login to desktop, open a terminal and become root via

Code: Select all

 su -

or
at the login prompt press"ctrl"+ "alt" + "F2", this will give you a tty
login as root.

unfortunately I do not know which of the kernel variants you have installed.

run

Code: Select all

urpme kernel-

and press "tab".
this will list all available kernels listed with the kernel- header and present the "urpme kernel-" text waiting for your input.
fill in the rest of the line with the correct kernel you wish to remove: ie "urpme kernel-desktop-devel-4.1( + tab here to auto fill with 4.20 mga6)" and "enter"
repeat as required.

when done,

Code: Select all

update-grub2

this will remove the 4.14.20 kernel entry (and any others you removed) from your boot menu.
then reboot by typing "reboot" if in the tty or reboot from the desktop icon

unfortunately, this will not fix what-ever is the problem on your system with the 4.14.20 kernel, and it may re-present on further kernel updates.
this kernel update is to mitigate spectre and meltdown issues, so it would be unwise to continue using the 4.9.35 kernel.
If your problem can be corrected, I would recommend creating a bug report, so that the correction is reported to the kernel maintainer(s)