Plymouth Modules - Fatal

[matt12]

Whilst booting the i686 F10 B Live CD, I received the following message:
FATAL: Module sr_mod not found
FATAL: Module loop not found

Still seemed to finally boot ok although my install to the HD failed and stuck with the white bar at the bottom of the screen fully complete but frozen. Will try a second install.

[matt12]

The second boot from the live CD still had the error message, but at least the install booted ok this time! Hopefully with the 300 updates, everything should be smooth going forward.

[pedora]

What does it mean when it gets stuck on that part of the screen and freezes (i.e. won't continue booting)?

I was trying it out on another computer and that's what happened.

It boots on my main computer but I needed it to boot on another computer.

What is the solution and is it going to be fixed? Why's it doing that?

[JoshuaK]

Well, I have this problem too. It gives me fatal messages yet mine boots fine and rest of system plays nicely, that is on live cd. In real installation though it wont load Plymouth yet it boots without error other than that. Hmm... I never had any problems with RHGB. Odd. I have a Samsung SyncMaster 941BW with DVI hooked up to a nvidia heforce 6200 256MB. Help?

[pedora]

Whatever it is, I think it's getting stuck on video driver loading. I suspect this because the computer it's getting stuck on has an Nvidia GeForce 4 video card in it. It's old so maybe Fedora's base install CDs/DVDs are not loading or supporting the drivers for it?

Fedora 10 beta boots up on my computer and does give the 'modules -fatal' message but does continue to boot up and I get into the KDE desktop.

How come Fedora Live discs doesn't have more options for selecting drivers, resolutions, monitors etc.? Unfortunate...

[daf1983]

unfortunately, i've heard that Plymouth won't work with nvidia graphics as they lack KMS. both intel and ati have the option to run KMS while until Nvidia releases full documentation, we won't see Plymouth. i can't actually believe that but i installed beta 2 days ago, i keep it updated but Plymouth does not start. i can only see an ugly bar at the bottom of the screen.

[Quasar8000]

Try to update to the latest packages in Rawhide, I had that same problem but it went away after an update.

[leigh123linux]

unfortunately, i've heard that Plymouth won't work with nvidia graphics as they lack KMS. both intel and ati have the option to run KMS while until Nvidia releases full documentation, we won't see Plymouth. i can't actually believe that but i installed beta 2 days ago, i keep it updated but Plymouth does not start. i can only see an ugly bar at the bottom of the screen.


Plymouth works Ok with my 7600GT :cool:

I had to add vga=0x318 to grub.conf .

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd2,0)
# kernel /boot/vmlinuz-version ro root=/dev/sdc1
# initrd /boot/initrd-version.img
#boot=/dev/sdc1
default=0
timeout=5
splashimage=(hd2,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.27-0.382.rc8.git4.fc10.x86_64)
root (hd2,0)
kernel /boot/vmlinuz-2.6.27-0.382.rc8.git4.fc10.x86_64 ro root=UUID=f446f1c8-c9a1-4bb1-b489-039f1f7dd890 rhgb quiet vga=0x318
initrd /boot/initrd-2.6.27-0.382.rc8.git4.fc10.x86_64.img
title Fedora (2.6.27-0.370.rc8.fc10.x86_64)
root (hd2,0)
kernel /boot/vmlinuz-2.6.27-0.370.rc8.fc10.x86_64 ro root=UUID=f446f1c8-c9a1-4bb1-b489-039f1f7dd890 rhgb quiet vga=0x318
initrd /boot/initrd-2.6.27-0.370.rc8.fc10.x86_64.img
title Fedora (2.6.27-0.354.rc7.git3.fc10.x86_64)
root (hd2,0)
kernel /boot/vmlinuz-2.6.27-0.354.rc7.git3.fc10.x86_64 ro root=UUID=f446f1c8-c9a1-4bb1-b489-039f1f7dd890 rhgb quiet vga=0x318
initrd /boot/initrd-2.6.27-0.354.rc7.git3.fc10.x86_64.img

[crainey69]

ok came back here because I have never been able to get Plymouth to work. I'm running an Nvidia card myself so I guess it's just something I have to live with for now. I do notice on my actual install that it throws some errors regarding loops as it starts.

Guess I'll wait. Finally got F10 to resinstall in my VM not using LVM. I'm wondering if they ever got the LVM problem straightened out entirely. I don't use LVM on my normal installs anyway. Just an extra layer of figuring things out when there is a problem.

[Demz]

im not liking what im hearing about this :( it maybe another distro for me

[crainey69]

im not liking what im hearing about this :( it maybe another distro for me

It still boots. It just isn't pretty while it does it. It will get worked out eventually. I mean, RHGB hasn't worked for about a month in F9 for me anyway.

[crainey69]

Leigh,

I'm running a 6800 Nvidia, I'll try your trick and let you know how it works.

[Demz]

It still boots. It just isn't pretty while it does it. It will get worked out eventually. I mean, RHGB hasn't worked for about a month in F9 for me anyway.

thats true,, guess at the end of the day who cares if its not pretty at the moment , as long as it boots an works

[crainey69]

Just finished downloading 840 meg of updates for my virtual install. The updates are installing now. We'll see how that goes.

[stefan1975]

Plymouth works Ok with my 7600GT :cool:
I had to add vga=0x318 to grub.conf .


so how does the extra grub entry work / perform? on the fedora site it says:


'vga=0x318' on the command line will force the hardware into graphics mode without using KMS drivers. This will give 1024x768 resolution and will have weird interactions with X, so should only be used for testing.


so that doesn't sound too promising or pretty in 1024 on my widescreen laptop. It really sucks that nvidia got so far behind so fast. I selected this laptop for its quadro 350 videocard and the availability of linux drivers but now i regret not having an ATI card instead, KMS for nvidia seems like a long distance away for now :-(

stefan

[TheIcebreaker]

I am running intel driver, xserver, kernel and mesa from rawhide. When I set vga=0x318 I only get an ugly line at the bottom of my screen. How can I enable KMS for my intel drivers. I think they do support KMS.

[scottro]

Plymouth still doesn't work all that well with several graphics cards. You can simply remove the
rhgb quiet
from your grub/menu.lst to disable it. (It's in the release notes in the boot section.)

[Demz]

KMS will officially be in the 2.6.29 kernel or 2.6.28 kernel kernel mode-setting (KMS) has yet to enter the mainline Linux kernel and it will not be until at least Linux 2.6.29 when this happens. http://www.phoronix.com/scan.php?page=article&item=fedora_10_freeze&num=2

[TheIcebreaker]

But I thought the fedora kernel is parched for KMS. Its been advertised that KMS is supported for ATI chips. Is KMS a single feature in kernel across all chips or every vendor needs to get get its own bits in the kernel for it to work on the.

If its the later then you are saying that intel KMs will be in the kernel for 2.6.29 release because the merge window for the 28 version is closed.

[Demz]

no,, Nvidia or ATI do not Support KMS as of yet ( someone correct me if im wrong ) where did you hear that KMS was supported on ATI chips? this might explain more http://www.phoronix.com/scan.php?page=news_item&px=NjgxMQ read the kernel mailing list http://lkml.org/lkml/2008/10/24/3

[stefan1975]

perhaps the confusion stems from the fact that this thread was mainly about plymouth and less about KMS and that plymouth seems to be working best for ATI users and much less so for nvidia users and when you look at the "better startup" feature page for plymouth it is very much intertwined with KMS so perhaps we are getting the differences between the two or their dependencies wrong?

[TheIcebreaker]

Well now I am completely confused. Here is how I understand it.

1. RHGB is gone due to some changes in xserver which made input detection through evdev, hence rhgb could not run.

2. Plymouth replaced it, it needs KMS to set the screen mode in the kernel and hence avoid flicker. Currently as there not many drivers which support KMS it falls back to a text mode with a line progress bar at the bottom.

3. ATI chips do support KMS for fedora 10 as is mentioned in this article in phoronix. http://www.phoronix.com/scan.php?page=article&item=xorg_kms_2008&num=1

4. KMS is not in the mainline kernel but it is somehow in the fedora 10 kernel. (very confusing).

[Demz]

no idea how its supported in fedora10 but my guess is that perhaps they have backported some testing KMS feature that will go into the 2.6.29 kernel into the 2.6.27 kernel