1 |
On Thu, Apr 5, 2012 at 1:32 PM, Joost Roeleveld <joost@××××××××.org> wrote: |
2 |
> On Thursday, April 05, 2012 01:10:46 PM Canek Peláez Valdés wrote: |
3 |
>> On Thu, Apr 5, 2012 at 2:47 AM, 张春江 <zhangchunjiangrj@×××.com> wrote: |
4 |
>> > On 2012-04-05 01:29:36,"Canek Peláez Valdés" <caneko@×××××.com> wrote: |
5 |
>> > |
6 |
>> |
7 |
>>>On Wed, Apr 4, 2012 at 12:28 PM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
8 |
>> >>> Something is wrong. There is no dracut messages in your dmesg output, |
9 |
>> >>> so either you are not using the rd.debug command line (which, |
10 |
>> >>> according to your logs, you *are* using), or you are not using a |
11 |
>> >>> dracut-created initramfs, or the initramfs is somehow corrupted. |
12 |
>> > |
13 |
>> > I used |
14 |
>> > # dracut -H -f |
15 |
>> > to create my initramfs. I don't know why there is no dracut message in |
16 |
>> > my dmesg output. |
17 |
>> > |
18 |
>> >>> Can I see your grub.cfg file, as it is please? Also, it seems that th |
19 |
>> >>>e |
20 |
>> >>> problem is OpenRC not creating the /run tmpfs early on during the boo |
21 |
>> >>>t |
22 |
>> >>> process: |
23 |
>> >>> |
24 |
>> >>> https://bugs.gentoo.org/show_bug.cgi?id=409921 |
25 |
>> >>> |
26 |
>> >>> Until that gets fixed, recent versions of plymouth cannot work with |
27 |
>> >>> OpenRC. Maybe you could try an old version? |
28 |
>> >>> |
29 |
>> >>> Regards. |
30 |
>> >> |
31 |
>> >>Also, can I see your fstab? It seems you use quite the complex setup |
32 |
>> >>for your partitions. |
33 |
>> >> |
34 |
>> > The latest version of plymouth is 0.9_pre20111013-r1. |
35 |
>> > I installed sys-boot/plymouth-0.8.3-r5 but it still couldn't work, just |
36 |
>> > like v0.9_pre. There is no ebuild for other versions. |
37 |
>> > Then I tried to install by tarball, but version 0.8.1 and 0.8.2 have a |
38 |
>> > make error: "fatal error: drm/drm.h: No such file or directory", but I |
39 |
>> > have already installed x11-libs/libdrm and all the other drm related |
40 |
>> > applications are masked. Version 0.7.2 have an another make error. |
41 |
>> > |
42 |
>> > This is my grub.conf: |
43 |
>> > default 0 |
44 |
>> > timeout 5 |
45 |
>> > #splashimage=(hd0,13)/boot/grub/splash.xpm.gz |
46 |
>> > |
47 |
>> > title Gentoo Linux |
48 |
>> > root (hd0,13) |
49 |
>> > kernel /boot/kernel-3.2.1-gentoo-r2 root=/dev/sda10 splash quiet |
50 |
>> > video=radeon:1366x768 initrd /boot/initramfs-3.2.1-gentoo-r2.img |
51 |
>> > |
52 |
>> > title Win7 |
53 |
>> > rootnoverify (hd0,0) |
54 |
>> > makeactive |
55 |
>> > chainloader +1 |
56 |
>> > |
57 |
>> > This is my /etc/fstab: |
58 |
>> > # <fs> <mountpoint> <type> <opts> |
59 |
>> > <dump/pass> # NOTE: If your BOOT partition is ReiserFS, add the notail |
60 |
>> > option to opts. /dev/sda14 /boot ext4 |
61 |
>> > defaults,noatime 1 2 /dev/sda10 / |
62 |
>> > ext4 noatime 0 1 /dev/sda11 |
63 |
>> > /usr ext4 noatime 0 0 /dev/sda12 |
64 |
>> > /var ext4 noatime 0 |
65 |
>> > 0 /dev/sda13 /home ext4 noatime |
66 |
>> > 0 0 /dev/sda9 none swap |
67 |
>> > sw 0 0 /dev/cdrom /mnt/cdrom |
68 |
>> > auto noauto,user 0 0 /dev/sda1 |
69 |
>> > /media/win7 ntfs-3g rw,users,umask=000 0 0 /dev/sda5 |
70 |
>> > /media/music ntfs-3g rw,users,umask=000 0 0 |
71 |
>> > /dev/sda6 /media/animation ntfs-3g |
72 |
>> > rw,users,umask=000 0 0 /dev/sda7 /media/data |
73 |
>> > ntfs-3g rw,users,umask=000 0 0 /dev/sda8 |
74 |
>> > /media/video ntfs-3g rw,users,umask=000 0 0 |
75 |
>> > |
76 |
>> > Thank you very much for your help! |
77 |
>> |
78 |
>> I see several problems from your grub and fstab config files: |
79 |
>> |
80 |
>> 1. If you have a separate /boot partition, you should have something like |
81 |
>> |
82 |
>> kernel (hd0,14)/kernel-3.2.1-gentoo-r2 root=/dev/sda10 splash quiet |
83 |
>> video=radeon:1366x768 |
84 |
>> initrd (hd0,14)/initramfs-3.2.1-gentoo-r2.img |
85 |
>> in your grub.cfg. |
86 |
> |
87 |
> Grub starts counting at "0", not at "1". So the partition is marked as |
88 |
> (hd0,13) |
89 |
> The /boot partition has a symlink called boot pointing back to itself. |
90 |
> (hd0,13)/boot = (hd0,13) |
91 |
> |
92 |
> When specifying " root (hd0,13) " Grub will default to that partition. |
93 |
> |
94 |
> Eg. the grub config matches fstab. |
95 |
|
96 |
You are right about that; I just saw the sd14 on fstab, and thought it |
97 |
should be the same on grub. |
98 |
|
99 |
>> 2. GRUB cannot read ext4 partitions (GRUB2 can), so you are reading |
100 |
>> them as ext3 (I don't know if this can cause any problems). The reason |
101 |
>> I started to use GRUB2 was because I wanted to use ext4 for my /. |
102 |
> |
103 |
> I don't think ext4 and ext3 use the same disk layout, eg. I don't think that |
104 |
> can work. |
105 |
|
106 |
ext4 is fully backwards compatible with ext3, obviously; otherwise 张春江 |
107 |
would not be able to boot his system. |
108 |
|
109 |
>> 3. Where is the rd.debug command line? Without it, we can't see |
110 |
>> dracut's debug messages. |
111 |
>> |
112 |
>> Delete /boot/initramfs*, and recreate the initramfs again, add the |
113 |
>> rd.debug kernel command line in grub.cfg, and reboot again. The dmesg |
114 |
>> output should have a lot of lines with "dracut:"; send that to the |
115 |
>> list. |
116 |
> |
117 |
> Why start with deleting the initramfs? |
118 |
> Why not create a new one with a new name and keep the old one for comparison |
119 |
> later? |
120 |
|
121 |
Since I believed that the /boot partition and dir could differ, I |
122 |
thought it would be the safest route; now it doesn't really matter. |
123 |
But anyway, the initramfs is automatically generated by dracut; I |
124 |
don't see a reason to keep one if it seems to be failing, when I |
125 |
trivially can create a new one. I delete mine all the time. |
126 |
|
127 |
Regards. |
128 |
-- |
129 |
Canek Peláez Valdés |
130 |
Posgrado en Ciencia e Ingeniería de la Computación |
131 |
Universidad Nacional Autónoma de México |