Re: [gentoo-user] sys-boot/plymouth could not work
Hi! The video=radeon:... option is not strictly necessary. Actually from the logs it seems you have a NVIDIA card... Greetings, -- Jorge Martínez López jorg...@gmail.com http://www.jorgeml.net Google Talk / XMPP: jorg...@gmail.com
Re: [gentoo-user] sys-boot/plymouth could not work
On 2012-04-05 01:29:36，Canek Peláez Valdés can...@gmail.com wrote： On Wed, Apr 4, 2012 at 12:28 PM, Canek Peláez Valdés can...@gmail.com wrote: Something is wrong. There is no dracut messages in your dmesg output, so either you are not using the rd.debug command line (which, according to your logs, you *are* using), or you are not using a dracut-created initramfs, or the initramfs is somehow corrupted. I used # dracut -H -f to create my initramfs. I don't know why there is no dracut message in my dmesg output. Can I see your grub.cfg file, as it is please? Also, it seems that the problem is OpenRC not creating the /run tmpfs early on during the boot process: https://bugs.gentoo.org/show_bug.cgi?id=409921 Until that gets fixed, recent versions of plymouth cannot work with OpenRC. Maybe you could try an old version? Regards. Also, can I see your fstab? It seems you use quite the complex setup for your partitions. The latest version of plymouth is 0.9_pre20111013-r1. I installed sys-boot/plymouth-0.8.3-r5 but it still couldn't work, just like v0.9_pre. There is no ebuild for other versions. Then I tried to install by tarball, but version 0.8.1 and 0.8.2 have a make error: fatal error: drm/drm.h: No such file or directory, but I have already installed x11-libs/libdrm and all the other drm related applications are masked. Version 0.7.2 have an another make error. This is my grub.conf: default 0 timeout 5 #splashimage=(hd0,13)/boot/grub/splash.xpm.gz title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 splash quiet video=radeon:1366x768 initrd /boot/initramfs-3.2.1-gentoo-r2.img title Win7 rootnoverify (hd0,0) makeactive chainloader +1 This is my /etc/fstab: # fs mountpointtype opts dump/pass # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. /dev/sda14 /boot ext4defaults,noatime 1 2 /dev/sda10 / ext4noatime 0 1 /dev/sda11 /usrext4noatime 0 0 /dev/sda12 /varext4noatime 0 0 /dev/sda13 /home ext4noatime 0 0 /dev/sda9 noneswapsw 0 0 /dev/cdrom /mnt/cdrom autonoauto,user 0 0 /dev/sda1 /media/win7 ntfs-3g rw,users,umask=000 0 0 /dev/sda5 /media/musicntfs-3g rw,users,umask=000 0 0 /dev/sda6 /media/animation ntfs-3grw,users,umask=000 0 0 /dev/sda7 /media/data ntfs-3g rw,users,umask=000 0 0 /dev/sda8 /media/videontfs-3g rw,users,umask=000 0 0 Thank you very much for your help!
Re: [gentoo-user] sys-boot/plymouth could not work
On Thu, Apr 5, 2012 at 2:47 AM, 张春江 zhangchunjian...@126.com wrote: On 2012-04-05 01:29:36，Canek Peláez Valdés can...@gmail.com wrote： On Wed, Apr 4, 2012 at 12:28 PM, Canek Peláez Valdés can...@gmail.com wrote: Something is wrong. There is no dracut messages in your dmesg output, so either you are not using the rd.debug command line (which, according to your logs, you *are* using), or you are not using a dracut-created initramfs, or the initramfs is somehow corrupted. I used # dracut -H -f to create my initramfs. I don't know why there is no dracut message in my dmesg output. Can I see your grub.cfg file, as it is please? Also, it seems that the problem is OpenRC not creating the /run tmpfs early on during the boot process: https://bugs.gentoo.org/show_bug.cgi?id=409921 Until that gets fixed, recent versions of plymouth cannot work with OpenRC. Maybe you could try an old version? Regards. Also, can I see your fstab? It seems you use quite the complex setup for your partitions. The latest version of plymouth is 0.9_pre20111013-r1. I installed sys-boot/plymouth-0.8.3-r5 but it still couldn't work, just like v0.9_pre. There is no ebuild for other versions. Then I tried to install by tarball, but version 0.8.1 and 0.8.2 have a make error: fatal error: drm/drm.h: No such file or directory, but I have already installed x11-libs/libdrm and all the other drm related applications are masked. Version 0.7.2 have an another make error. This is my grub.conf: default 0 timeout 5 #splashimage=(hd0,13)/boot/grub/splash.xpm.gz title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 splash quiet video=radeon:1366x768 initrd /boot/initramfs-3.2.1-gentoo-r2.img title Win7 rootnoverify (hd0,0) makeactive chainloader +1 This is my /etc/fstab: # fs mountpoint type opts dump/pass # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. /dev/sda14 /boot ext4 defaults,noatime 1 2 /dev/sda10 / ext4 noatime 0 1 /dev/sda11 /usr ext4 noatime 0 0 /dev/sda12 /var ext4 noatime 0 0 /dev/sda13 /home ext4 noatime 0 0 /dev/sda9 none swap sw 0 0 /dev/cdrom /mnt/cdrom auto noauto,user 0 0 /dev/sda1 /media/win7 ntfs-3g rw,users,umask=000 0 0 /dev/sda5 /media/music ntfs-3g rw,users,umask=000 0 0 /dev/sda6 /media/animation ntfs-3g rw,users,umask=000 0 0 /dev/sda7 /media/data ntfs-3g rw,users,umask=000 0 0 /dev/sda8 /media/video ntfs-3g rw,users,umask=000 0 0 Thank you very much for your help! I see several problems from your grub and fstab config files: 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. 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 /. 3. Where is the rd.debug command line? Without it, we can't see dracut's debug messages. Delete /boot/initramfs*, and recreate the initramfs again, add the rd.debug kernel command line in grub.cfg, and reboot again. The dmesg output should have a lot of lines with dracut:; send that to the list. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] sys-boot/plymouth could not work
On Thursday, April 05, 2012 01:10:46 PM Canek Peláez Valdés wrote: On Thu, Apr 5, 2012 at 2:47 AM, 张春江 zhangchunjian...@126.com wrote: On 2012-04-05 01:29:36，Canek Peláez Valdés can...@gmail.com wrote： On Wed, Apr 4, 2012 at 12:28 PM, Canek Peláez Valdés can...@gmail.com wrote: Something is wrong. There is no dracut messages in your dmesg output, so either you are not using the rd.debug command line (which, according to your logs, you *are* using), or you are not using a dracut-created initramfs, or the initramfs is somehow corrupted. I used # dracut -H -f to create my initramfs. I don't know why there is no dracut message in my dmesg output. Can I see your grub.cfg file, as it is please? Also, it seems that th e problem is OpenRC not creating the /run tmpfs early on during the boo t process: https://bugs.gentoo.org/show_bug.cgi?id=409921 Until that gets fixed, recent versions of plymouth cannot work with OpenRC. Maybe you could try an old version? Regards. Also, can I see your fstab? It seems you use quite the complex setup for your partitions. The latest version of plymouth is 0.9_pre20111013-r1. I installed sys-boot/plymouth-0.8.3-r5 but it still couldn't work, just like v0.9_pre. There is no ebuild for other versions. Then I tried to install by tarball, but version 0.8.1 and 0.8.2 have a make error: fatal error: drm/drm.h: No such file or directory, but I have already installed x11-libs/libdrm and all the other drm related applications are masked. Version 0.7.2 have an another make error. This is my grub.conf: default 0 timeout 5 #splashimage=(hd0,13)/boot/grub/splash.xpm.gz title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 splash quiet video=radeon:1366x768 initrd /boot/initramfs-3.2.1-gentoo-r2.img title Win7 rootnoverify (hd0,0) makeactive chainloader +1 This is my /etc/fstab: # fs mountpointtype opts dump/pass # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. /dev/sda14 /boot ext4 defaults,noatime1 2 /dev/sda10 / ext4noatime 0 1 /dev/sda11 /usrext4noatime 0 0 /dev/sda12 /varext4noatime 0 0 /dev/sda13 /home ext4noatime 0 0 /dev/sda9 noneswap sw 0 0 /dev/cdrom /mnt/cdrom autonoauto,user 0 0 /dev/sda1 /media/win7 ntfs-3g rw,users,umask=000 0 0 /dev/sda5 /media/musicntfs-3g rw,users,umask=000 0 0 /dev/sda6 /media/animation ntfs-3g rw,users,umask=000 0 0 /dev/sda7 /media/data ntfs-3g rw,users,umask=000 0 0 /dev/sda8 /media/videontfs-3g rw,users,umask=000 0 0 Thank you very much for your help! I see several problems from your grub and fstab config files: 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. 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. 3. Where is the rd.debug command line? Without it, we can't see dracut's debug messages. Delete /boot/initramfs*, and recreate the initramfs again, add the rd.debug kernel command line in grub.cfg, and reboot again. The dmesg output should have a lot of lines with dracut:; send that to the list. Why start with deleting the initramfs? Why not create a new one with a new name and keep the old one for comparison later? -- Joost
Re: [gentoo-user] sys-boot/plymouth could not work
On Thu, Apr 5, 2012 at 1:32 PM, Joost Roeleveld jo...@antarean.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, 张春江 zhangchunjian...@126.com wrote: On 2012-04-05 01:29:36，Canek Peláez Valdés can...@gmail.com wrote： On Wed, Apr 4, 2012 at 12:28 PM, Canek Peláez Valdés can...@gmail.com wrote: Something is wrong. There is no dracut messages in your dmesg output, so either you are not using the rd.debug command line (which, according to your logs, you *are* using), or you are not using a dracut-created initramfs, or the initramfs is somehow corrupted. I used # dracut -H -f to create my initramfs. I don't know why there is no dracut message in my dmesg output. Can I see your grub.cfg file, as it is please? Also, it seems that th e problem is OpenRC not creating the /run tmpfs early on during the boo t process: https://bugs.gentoo.org/show_bug.cgi?id=409921 Until that gets fixed, recent versions of plymouth cannot work with OpenRC. Maybe you could try an old version? Regards. Also, can I see your fstab? It seems you use quite the complex setup for your partitions. The latest version of plymouth is 0.9_pre20111013-r1. I installed sys-boot/plymouth-0.8.3-r5 but it still couldn't work, just like v0.9_pre. There is no ebuild for other versions. Then I tried to install by tarball, but version 0.8.1 and 0.8.2 have a make error: fatal error: drm/drm.h: No such file or directory, but I have already installed x11-libs/libdrm and all the other drm related applications are masked. Version 0.7.2 have an another make error. This is my grub.conf: default 0 timeout 5 #splashimage=(hd0,13)/boot/grub/splash.xpm.gz title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 splash quiet video=radeon:1366x768 initrd /boot/initramfs-3.2.1-gentoo-r2.img title Win7 rootnoverify (hd0,0) makeactive chainloader +1 This is my /etc/fstab: # fs mountpoint type opts dump/pass # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. /dev/sda14 /boot ext4 defaults,noatime 1 2 /dev/sda10 / ext4 noatime 0 1 /dev/sda11 /usr ext4 noatime 0 0 /dev/sda12 /var ext4 noatime 0 0 /dev/sda13 /home ext4 noatime 0 0 /dev/sda9 none swap sw 0 0 /dev/cdrom /mnt/cdrom auto noauto,user 0 0 /dev/sda1 /media/win7 ntfs-3g rw,users,umask=000 0 0 /dev/sda5 /media/music ntfs-3g rw,users,umask=000 0 0 /dev/sda6 /media/animation ntfs-3g rw,users,umask=000 0 0 /dev/sda7 /media/data ntfs-3g rw,users,umask=000 0 0 /dev/sda8 /media/video ntfs-3g rw,users,umask=000 0 0 Thank you very much for your help! I see several problems from your grub and fstab config files: 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. You are right about that; I just saw the sd14 on fstab, and thought it should be the same on grub. 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. 3. Where is the rd.debug command line? Without it, we can't see dracut's debug messages. Delete /boot/initramfs*, and recreate the initramfs again, add the rd.debug kernel command line in grub.cfg, and reboot again. The dmesg output should have a lot of lines with dracut:; send that to the list. Why start with deleting the initramfs? Why not create a new one with a new name and keep the old one for comparison later? Since I believed that the /boot partition and dir could differ, I thought it would be the safest route; now it doesn't really matter. But anyway, the initramfs is automatically generated by dracut; I don't see a reason to keep one if it seems to be failing, when I trivially can create a new one. I delete mine all
Re: [gentoo-user] sys-boot/plymouth could not work
On Thu, Apr 5, 2012 at 2:50 PM, Canek Peláez Valdés can...@gmail.com wrote: On Thu, Apr 5, 2012 at 1:32 PM, Joost Roeleveld jo...@antarean.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, 张春江 zhangchunjian...@126.com wrote: 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. Just noting this for clarity. -- :wq
Re: [gentoo-user] sys-boot/plymouth could not work
On Thu, Apr 5, 2012 at 2:03 PM, Michael Mol mike...@gmail.com wrote: On Thu, Apr 5, 2012 at 2:50 PM, Canek Peláez Valdés can...@gmail.com wrote: On Thu, Apr 5, 2012 at 1:32 PM, Joost Roeleveld jo...@antarean.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, 张春江 zhangchunjian...@126.com wrote: 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. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] sys-boot/plymouth could not work
El 04/04/2012 00:03, 张春江 zhangchunjian...@126.com escribió: On 2012-04-04 12:06:26，Canek Peláez Valdés can...@gmail.com wrote： Please add rd.debug to your grub kernel command line: title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 quiet splash rd.debug initrd /boot/initramfs-3.2.1-gentoo-r2.img Reboot, and immediately do dmesg output.txt Please post the contents of output.txt. We need to know what exactly is failing with the initramfs.javascript:void(0) The accessories are my dmesg output and my boot log. Now it is very strange that I have a /run tmpfs in my machine. # mount | grep run tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) # grep run /etc/mtab tmpfs /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0 And now when I shutdown my machine, there is no plymouth error message while no splash either. While booting, it shows plymouthd could not start boot splash: No such file or directory and no splash. I don't konw why, I just generated initramfs with dracut once again and run # plymouth --show-splash just now. Sorry, I forgot; you also need to remove the quiet option from your kernel command line: title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 splash rd.debug initrd /boot/initramfs-3.2.1-gentoo-r2.img The quiet option overrides the rd.debug option. Please reboot and send again the output from dmesg. Regards.
Re: [gentoo-user] sys-boot/plymouth could not work
On 2012-04-04 15:03:56，Canek Peláez Valdés can...@gmail.com wrote： Sorry, I forgot; you also need to remove the quiet option from your kernel command line: title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 splash rd.debug initrd /boot/initramfs-3.2.1-gentoo-r2.img The quiet option overrides the rd.debug option. Please reboot and send again the output from dmesg. Here is the new dmesg output.Linux version 3.2.1-gentoo-r2 (root@zcj) (gcc version 4.5.3 (Gentoo 4.5.3-r2 p1.1, pie-0.4.7) ) #19 SMP Mon Apr 2 13:04:49 CST 2012 BIOS-provided physical RAM map: BIOS-e820: - 0009f400 (usable) BIOS-e820: 0009f400 - 000a (reserved) BIOS-e820: 000d2000 - 000d4000 (reserved) BIOS-e820: 000dc000 - 0010 (reserved) BIOS-e820: 0010 - 7f8a1000 (usable) BIOS-e820: 7f8a1000 - 7f8a7000 (reserved) BIOS-e820: 7f8a7000 - 7f9ba000 (usable) BIOS-e820: 7f9ba000 - 7fa0f000 (reserved) BIOS-e820: 7fa0f000 - 7fb08000 (usable) BIOS-e820: 7fb08000 - 7fd0f000 (reserved) BIOS-e820: 7fd0f000 - 7fd19000 (usable) BIOS-e820: 7fd19000 - 7fd1f000 (reserved) BIOS-e820: 7fd1f000 - 7fd64000 (usable) BIOS-e820: 7fd64000 - 7fd9f000 (ACPI NVS) BIOS-e820: 7fd9f000 - 7fe0 (ACPI data) BIOS-e820: 7fe0 - 8000 (reserved) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fed0 - fed00400 (reserved) BIOS-e820: fed1 - fed14000 (reserved) BIOS-e820: fed18000 - fed1a000 (reserved) BIOS-e820: fed1c000 - fed9 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff80 - 0001 (reserved) Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! DMI present. DMI: LENOVO 20022 /NITU1, BIOS 18CN37WW(V2.10) 09/18/2009 e820 update range: - 0001 (usable) == (reserved) e820 remove range: 000a - 0010 (usable) last_pfn = 0x7fd64 max_arch_pfn = 0x10 MTRR default type: uncachable MTRR fixed ranges enabled: 0-9 write-back A-B uncachable C-D3FFF write-protect D4000-D uncachable E-F write-protect MTRR variable ranges enabled: 0 base 0 mask F8000 write-back 1 base 0FFE0 mask FFFE0 write-protect 2 disabled 3 disabled 4 disabled 5 disabled 6 disabled found SMP MP-table at [c00f75a0] f75a0 initial memory mapped : 0 - 01c0 Base memory trampoline at [c009e000] 9e000 size 4096 init_memory_mapping: -377fe000 00 - 40 page 4k 40 - 003740 page 2M 003740 - 00377fe000 page 4k kernel direct mapping tables up to 377fe000 @ 1bfb000-1c0 ACPI: RSDP 000f7510 00024 (v02 LENOVO) ACPI: XSDT 7fdf848f 00074 (v01 LENOVO CB-01 LTP ) ACPI: FACP 7fde8000 000F4 (v03 LENOVO CB-010001 ALAN 0001) ACPI: DSDT 7fde9000 066BF (v02 LENOVO CB-010001 INTL 20050624) ACPI: FACS 7fd9efc0 00040 ACPI: HPET 7fdfed52 00038 (v01 LENOVO CB-010001 LOHR 005A) ACPI: MCFG 7fdfed8a 0003C (v01 LENOVO CB-010001 LOHR 005A) ACPI: SLIX 7fdfedc6 00176 (v01 LENOVO CB-010001 TBD 0001) ACPI: DBGP 7fdfef3c 00034 (v01 LENOVO CB-010001 LOHR ) ACPI: APIC 7fdfef70 00068 (v01 PTLTD ? APIC LTP ) ACPI: BOOT 7fdfefd8 00028 (v01 PTLTD $SBFTBL$ LTP 0001) ACPI: SSDT 7fde7000 00655 (v01 PmRefCpuPm 3000 INTL 20050624) ACPI: SSDT 7fde6000 00259 (v01 PmRef Cpu0Tst 3000 INTL 20050624) ACPI: SSDT 7fde5000 0020F (v01 PmRefApTst 3000 INTL 20050624) ACPI: Local APIC address 0xfee0 1157MB HIGHMEM available. 887MB LOWMEM available. mapped low ram: 0 - 377fe000 low ram: 0 - 377fe000 Zone PFN ranges: DMA 0x0010 - 0x1000 Normal 0x1000 - 0x000377fe HighMem 0x000377fe - 0x0007fd64 Movable zone start PFN for each node early_node_map[6] active PFN ranges 0: 0x0010 - 0x009f 0: 0x0100 - 0x0007f8a1 0: 0x0007f8a7 - 0x0007f9ba 0: 0x0007fa0f - 0x0007fb08 0: 0x0007fd0f - 0x0007fd19 0: 0x0007fd1f - 0x0007fd64 On node 0 totalpages: 522891 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 3951 pages, LIFO batch:0 Normal zone: 1744 pages used for memmap Normal zone: 221486 pages, LIFO batch:31 HighMem zone: 2315 pages used for memmap HighMem zone: 293363 pages, LIFO batch:31 Using APIC driver default ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Re: [gentoo-user] sys-boot/plymouth could not work
On Wed, Apr 4, 2012 at 2:32 AM, 张春江 zhangchunjian...@126.com wrote: On 2012-04-04 15:03:56，Canek Peláez Valdés can...@gmail.com wrote： Sorry, I forgot; you also need to remove the quiet option from your kernel command line: title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 splash rd.debug initrd /boot/initramfs-3.2.1-gentoo-r2.img The quiet option overrides the rd.debug option. Please reboot and send again the output from dmesg. Here is the new dmesg output. Something is wrong. There is no dracut messages in your dmesg output, so either you are not using the rd.debug command line (which, according to your logs, you *are* using), or you are not using a dracut-created initramfs, or the initramfs is somehow corrupted. Can I see your grub.cfg file, as it is please? Also, it seems that the problem is OpenRC not creating the /run tmpfs early on during the boot process: https://bugs.gentoo.org/show_bug.cgi?id=409921 Until that gets fixed, recent versions of plymouth cannot work with OpenRC. Maybe you could try an old version? Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] sys-boot/plymouth could not work
On Wed, Apr 4, 2012 at 12:28 PM, Canek Peláez Valdés can...@gmail.com wrote: On Wed, Apr 4, 2012 at 2:32 AM, 张春江 zhangchunjian...@126.com wrote: On 2012-04-04 15:03:56，Canek Peláez Valdés can...@gmail.com wrote： Sorry, I forgot; you also need to remove the quiet option from your kernel command line: title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 splash rd.debug initrd /boot/initramfs-3.2.1-gentoo-r2.img The quiet option overrides the rd.debug option. Please reboot and send again the output from dmesg. Here is the new dmesg output. Something is wrong. There is no dracut messages in your dmesg output, so either you are not using the rd.debug command line (which, according to your logs, you *are* using), or you are not using a dracut-created initramfs, or the initramfs is somehow corrupted. Can I see your grub.cfg file, as it is please? Also, it seems that the problem is OpenRC not creating the /run tmpfs early on during the boot process: https://bugs.gentoo.org/show_bug.cgi?id=409921 Until that gets fixed, recent versions of plymouth cannot work with OpenRC. Maybe you could try an old version? Regards. Also, can I see your fstab? It seems you use quite the complex setup for your partitions. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] sys-boot/plymouth could not work
On Tue, Apr 3, 2012 at 12:43 AM, 张春江 zhangchunjian...@126.com wrote: Does anybody in the list have used plymouth. I do, but I also use systemd. And GRUB2. I installed and configured plymouth as http://dev.gentoo.org/~aidecoe/doc/en/plymouth.xml told. my grub.conf is title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 quiet splash initrd /boot/initramfs-3.2.1-gentoo-r2.img Seems correct. While I rebooting my machine, it shows [plymouth] could not create /run/plymouth and there is no splash. Then I created /run/plymouth directory in the initrd file system manually, but it seems that this doesn't change anything. And then I created /run/plymouth in my root file system, while this time system shows plymouthd could not start boot splash: No such file or directory. The /run directory should be created when installing dbus; it's a tmpfs: # mount | grep /run tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) And then it's bind-mounted in /var/run. At least that's how it happens with systemd, and that's the expected behaviour. Did you created your initramfs with dracut? I checked my Ubuntu virtual machine, which plymouth works well, there is no /run/plymouth directory in initram file system or real root file system. My initramfs doesn't have a /run directory either: # mkdir kk # cd kk # zcat /boot/initrd-3.2.12 | cpio -i 21514 blocks # ls bin dev etc init lib lib64 proc root run sbin shutdown sys sysroot tmp usr var However, inside /var, there is a symbolic link to /run: # ls -l var total 4 lrwxrwxrwx 1 root root9 Apr 3 12:15 lock - /run/lock drwxr-xr-x 2 root root 4096 Apr 3 12:15 log lrwxrwxrwx 1 root root4 Apr 3 12:15 run - /run So the problem it's not the existance (or not) of the run directory, I believe; it's the fact that it's mounted really early in the boot process as a tmpfs. So, did you use dracut to generate your initramfs, or did you use genkernel? Or you did it by hand? Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] sys-boot/plymouth could not work
On 2012-04-04 01:19:39，Canek Peláez Valdés can...@gmail.com wrote： I do, but I also use systemd. And GRUB2. I use OpenRC0.9.8.4 and GNU GRUB0.97-r10, maybe that's the difference. The /run directory should be created when installing dbus; it's a tmpfs: I have installed dbus, while I don't have a /run tmpfs. So the problem it's not the existance (or not) of the run directory, I believe; it's the fact that it's mounted really early in the boot process as a tmpfs. So, did you use dracut to generate your initramfs, or did you use genkernel? Or you did it by hand? I don't know how to mount /run before the boot process, I used dracut to generate my initramfs: # dracut -H -f I: *** Including module: dash *** I: *** Including module: i18n *** I: *** Including module: plymouth *** I: *** Including module: kernel-modules *** I: *** Including module: resume *** I: *** Including module: rootfs-block *** I: *** Including module: terminfo *** I: *** Including module: udev-rules *** I: Skipping udev rule: 50-udev.rules I: Skipping udev rule: 95-late.rules I: *** Including module: usrmount *** I: *** Including module: base *** I: *** Including module: fs-lib *** I: *** Including module: shutdown *** I: Skipping program kexec as it cannot be found and is flagged to be optional I: *** Including modules done *** I: Wrote /boot/initramfs-3.2.1-gentoo-r2.img: I: -rw-r--r-- 1 root root 2773237 Apr 4 11:52 /boot/initramfs-3.2.1-gentoo-r2.img
Re: [gentoo-user] sys-boot/plymouth could not work
On Tue, Apr 3, 2012 at 11:01 PM, 张春江 zhangchunjian...@126.com wrote: On 2012-04-04 01:19:39，Canek Peláez Valdés can...@gmail.com wrote： I do, but I also use systemd. And GRUB2. I use OpenRC0.9.8.4 and GNU GRUB0.97-r10, maybe that's the difference. The /run directory should be created when installing dbus; it's a tmpfs: I have installed dbus, while I don't have a /run tmpfs. So the problem it's not the existance (or not) of the run directory, I believe; it's the fact that it's mounted really early in the boot process as a tmpfs. So, did you use dracut to generate your initramfs, or did you use genkernel? Or you did it by hand? I don't know how to mount /run before the boot process, I used dracut to generate my initramfs: # dracut -H -f I: *** Including module: dash *** I: *** Including module: i18n *** I: *** Including module: plymouth *** I: *** Including module: kernel-modules *** I: *** Including module: resume *** I: *** Including module: rootfs-block *** I: *** Including module: terminfo *** I: *** Including module: udev-rules *** I: Skipping udev rule: 50-udev.rules I: Skipping udev rule: 95-late.rules I: *** Including module: usrmount *** I: *** Including module: base *** I: *** Including module: fs-lib *** I: *** Including module: shutdown *** I: Skipping program kexec as it cannot be found and is flagged to be optional I: *** Including modules done *** I: Wrote /boot/initramfs-3.2.1-gentoo-r2.img: I: -rw-r--r-- 1 root root 2773237 Apr 4 11:52 /boot/initramfs-3.2.1-gentoo-r2.img Please add rd.debug to your grub kernel command line: title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 quiet splash rd.debug initrd /boot/initramfs-3.2.1-gentoo-r2.img Reboot, and immediately do dmesg output.txt Please post the contents of output.txt. We need to know what exactly is failing with the initramfs. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] sys-boot/plymouth could not work
Does anybody in the list have used plymouth. I installed and configured plymouth as http://dev.gentoo.org/~aidecoe/doc/en/plymouth.xml told. my grub.conf is title Gentoo Linux root (hd0,13) kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 video=radeon:1366x768 quiet splash initrd /boot/initramfs-3.2.1-gentoo-r2.img While I rebooting my machine, it shows [plymouth] could not create /run/plymouth and there is no splash. Then I created /run/plymouth directory in the initrd file system manually, but it seems that this doesn't change anything. And then I created /run/plymouth in my root file system, while this time system shows plymouthd could not start boot splash: No such file or directory. I checked my Ubuntu virtual machine, which plymouth works well, there is no /run/plymouth directory in initram file system or real root file system. I googled this problem and found some guys had faced the same problem with me, but nobody have a solution. This is my first time to ask for help in the list, and this is even my first time to use a mailing list. Sorry for my poor English.
