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 the time. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
