[DONE] "Failed to start Wait..." after kernel upgrade

[doktor5000]

This morning I upgraded to the latest kernel version because the last upgrades went very smoothly. But this time something went wrong. I cannot boot directly into KDE anymore. The error message I get is: "Failed to start Wait for Plymouth Boot Screen to Quit" and the system seems to hang. But I can switch to an other terminal via "Ctrl+Alt+F2". From there I can log in as normal user. When I call then "startx" I get an error message - but after I while I get my fully functional KDE session. What might be wrong with the system configuration? I guess it has to to with the settings for the graphic card (nvidia quadro 4000). So I selected everything manually in mcc and rebooted the system. But the problem remains...

[doktor5000]

When KDE didn't load completely, can you take a look on another tty if there's something in /var/log/Xorg.0.log and after KDE has loaded, which driver is actually in use (same file)?

[magfan]

When KDE didn't load completely, can you take a look on another tty if there's something in /var/log/Xorg.0.log and after KDE has loaded, which driver is actually in use (same file)?

Well, I don't know when KDE should start. Maybe it is a problem with kdm? Searching on the internet shows that this problem is very often related to the nvidia driver. But the system already hang while everything on the screen was still in text mode. Luckily I disabled the splash screen a long time ago just to see what is going on while booting the system. This option was very helpful in the past. But mayby the system did not really "hang" because while I got the error message on "F1" I could still switch to console "F2, F3, ...". And I could start an X-session on every opened console after login with "startx". But logging in as root and running "init 5" made me switch back to "F1".

[doktor5000]

Sorry, can't understand more about the problem from your description.
Also, the Xorg.0.log is rather short, X server quits shortly after starting?

In any case, you should be aware about the issues with startx, see viewtopic.php?f=4&t=5479

[magfan]

Now I found the following when I called dmesg:

Code: Select all

[  426.911092] NVRM: Your system is not currently configured to drive a VGA console
[  426.911099] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[  426.911103] NVRM: requires the use of a text-mode VGA console. Use of other console
[  426.911107] NVRM: drivers including, but not limited to, vesafb, may result in
[  426.911111] NVRM: corruption and stability problems, and is not supported.


So I guess the problem is related to the nvidia driver. But I do not understand why. In mcc I configured the X-server to switch to graphic mode automatically. But it does not do it anymore. That is why I have to manually start a different tty (Ctrl+Alt+F2). Then I can login and start a graphical environment (startx). Any ideas where could be the problem?

Before I forget to mention: I switched back to the previous kernel (3.4.45-server) but the problem is still there. I also attached the latest Xorg.0.log file.

[doktor5000]

I've got that message too, and everything is working fine - may be bogus.
What kernel options do you currently use? Please show /proc/cmdline

[magfan]

Code: Select all

cat /proc/cmdline
BOOT_IMAGE=server_3.4.52-1.mga2 root=UUID=1372d436-e8c6-44aa-b822-467b9b60f23d nosplash verbose nokmsboot resume=UUID=df840f97-0ce3-4c57-bf7f-806485695a9f vga=788

[magfan]

I just read the following new topic https://forums.mageia.org/en/viewtopic.php?f=7&t=5568 which seems to be the same problem. Except that in my case the boot splash is disabled. In the meantime I tried older kernels which are installed on my system. But the problem remains.

Currently I wait until no new messages appear on tty1. Then I switch to tty2 and login as root. From there I call "init 5" and finally I end up on a graphical login screen on tty7. So I can logout from tty2 and continue my work on tty7...

[magfan]

Not really solved, but an upgrade to Mageia 3 made this problem disappear...