Re: [gentoo-user] sys-boot/plymouth could not work[solved]

[张春江]

On 2012-04-06 03:10:07,"Canek Peláez Valdés" <caneko@×××××.com> wrote:
>On Thu, Apr 5, 2012 at 2:03 PM, Michael Mol <mikemol@×××××.com> wrote:
>> On Thu, Apr 5, 2012 at 2:50 PM, Canek Peláez Valdés <caneko@×××××.com> wrote:
>>> On Thu, Apr 5, 2012 at 1:32 PM, Joost Roeleveld <joost@××××××××.org> wrote:
>>>> On Thursday, April 05, 2012 01:10:46 PM Canek Peláez Valdés wrote:
>>>>> On Thu, Apr 5, 2012 at 2:47 AM, 张春江 <zhangchunjiangrj@×××.com> wrote:

Thank you! The problem have been solved!

I'm ashamed to tell you that the reason is my wrong kernel complie option.
I knew little about gentoo and kernel complie when I install her,
so I choose genkernel and it generated a kernel image and an initramfs.
Weeks before, I complied my kernel manually with this option canceled:
General setup-->
    Initial RAM filesystem and RAM disk(initramfs/initrd) support

Then my machine can boot both with initramfs and  not, so I think the option
is not matter and I soon forgot it.

Today I suddenly realized it and recomplied my kernel with the option on and 
the plymouth works!

That's also the reason why the dmesg output didn't have any information about dracut.
The accessory is my new dmesg output, which have dracut information.

On 2012-04-06 18:18:26,"Jorge Martínez López" <jorgeml@×××××.com> wrote:
>Hi!
>
>The video=radeon:... option is not strictly necessary. Actually from
>the logs it seems you have a NVIDIA card...

You are right, I use NVIDIA card and video=radeon isn't neccessory. 
If I use "video=radeon:1366x768", which is my screen size, in kernel command line,
plymouth will just show fedora's default booting splash:
three bars(a deep blue one ,a blue one and a  white one) moving forward slowly,
no matter what theme you set.

If I use "vga=792" instead of "video=radeon:1366x768", every theme can be shown well,
and if no screen size specified, no splash at all.

>>>>> 2. GRUB cannot read ext4 partitions (GRUB2 can), so you are reading
>>>>> them as ext3 (I don't know if this can cause any problems). The reason
>>>>> I started to use GRUB2 was because I wanted to use ext4 for my /.
>>>>
>>>> I don't think ext4 and ext3 use the same disk layout, eg. I don't think that
>>>> can work.
>>>
>>> ext4 is fully backwards compatible with ext3, obviously; otherwise 张春江
>>> would not be able to boot his system.
>>
>> Not exactly. If you use them, ext4 adds structures and features which
>> means the filesystem isn't liked by ext3-only code. I don't remember
>> which these are, I just know I tended to accidentally enable them
>> while tweaking filesystems with tune2fs.
>
>tune2fs -O extents,uninit_bg,dir_index
>
>which, again, obviously 张春江 hasn't set, otherwise either he wouldn't
>be able to boot his system, or we had seen the warnings in his logs.
>
>Just as long as he doesn't use those new features, ext4 is fully
>backwards compatible with ext3.

I havn't set tune2fs, so in my machine, ext4 can backwards compatible with ext3.

>> 1. If you have a separate /boot partition, you should have something like
>>
>> kernel (hd0,14)/kernel-3.2.1-gentoo-r2 root=/dev/sda10 splash quiet
>> video=radeon:1366x768
>> initrd (hd0,14)/initramfs-3.2.1-gentoo-r2.img
>> in your grub.cfg.
>
> Grub starts counting at "0", not at "1". So the partition is marked as
> (hd0,13)
> The /boot partition has a symlink called boot pointing back to itself.
> (hd0,13)/boot = (hd0,13)
>
> When specifying "  root (hd0,13) " Grub will default to that partition.
>
> Eg. the grub config matches fstab.

My grub.conf is ok, I think that there is no need to specific (hd0,13) before /boot
In my opinion, "root (hd0,13)" command is before command kernel and initrd,
so GRUB will regard (hd0,13) as root fs, and it will looking for kernel and initramfs in
hd(0,13)/boot/kernel|initramfs. To test this, I tried to boot with:
title Gentoo Linux
root (hd0,13)
kernel /kernel-3.2.1-gentoo-r2 root=/dev/sda10 quiet splash vga=792
initrd /initramfs-3.2.1-gentoo-r2.img
this can boot successful too.

Than all of you!