1 |
Canek Peláez Valdés wrote: |
2 |
> On Mon, Apr 2, 2012 at 7:19 PM, Dale <rdalek1967@×××××.com> wrote: |
3 |
>> Canek Peláez Valdés wrote: |
4 |
>>> On Mon, Apr 2, 2012 at 5:21 PM, Dale <rdalek1967@×××××.com> wrote: |
5 |
>>>> Neil Bothwick wrote: |
6 |
>>>>> zgrep DEVTMP /proc/config.gz |
7 |
>>>> |
8 |
>>>> |
9 |
>>>> Ooops, it sort of snipped a bit much. lol Here you go: |
10 |
>>>> |
11 |
>>>> root@fireball / # zgrep DEVTMP /proc/config.gz |
12 |
>>>> # CONFIG_DEVTMPFS is not set |
13 |
>>>> root@fireball / # |
14 |
>>>> |
15 |
>>>> Looks like a nope to me. ;-) |
16 |
>>> |
17 |
>>> That was the reason for asking for your /usr/src/linux/.config file. |
18 |
>>> The udev ebuild ask for: |
19 |
>>> |
20 |
>>> CONFIG_CHECK="~BLK_DEV_BSG ~DEVTMPFS ~HOTPLUG ~INOTIFY_USER ~NET |
21 |
>>> ~PROC_FS ~SIGNALFD ~SYSFS ~!IDE ~!SYSFS_DEPRECATED |
22 |
>>> ~!SYSFS_DEPRECATED_V2" |
23 |
>>> |
24 |
>>> The dracut ebuild ask for: |
25 |
>>> |
26 |
>>> CONFIG_CHECK="~BLK_DEV_INITRD ~DEVTMPFS ~MODULES" |
27 |
>>> |
28 |
>>> So please check that you have all those options (and don't have the |
29 |
>>> ones with !), recompile your kernel, and reboot. |
30 |
>>> |
31 |
>>> Also, the divergence between /boot/kernel... and (hd0,0)/kernel... in |
32 |
>>> your grub could be causing funny things. Check that also. |
33 |
>>> |
34 |
>>> Regards. |
35 |
>> |
36 |
>> |
37 |
>> OK. I hate modules. Can they be built into the kernel? The only |
38 |
>> module I have is nvidia for my video card. |
39 |
> |
40 |
> MODULES is only for the kernel to be *able* to load modules, not to |
41 |
> *make* modules. If you use nvidia.ko, you must already have it. All |
42 |
> the options can be compiled into the kernel; I had them like that: |
43 |
> |
44 |
> $ grep "BLK_DEV_BSG\\|DEVTMPFS\\|HOTPLUG\\|INOTIFY_USER\\|NET=\\|PROC_FS\\|SIGNALFD\\|SYSFS" |
45 |
> /usr/src/linux/.config |
46 |
> # CONFIG_SYSFS_DEPRECATED is not set |
47 |
> CONFIG_HOTPLUG=y |
48 |
> CONFIG_SIGNALFD=y |
49 |
> CONFIG_BLK_DEV_BSG=y |
50 |
> # CONFIG_BLK_DEV_BSGLIB is not set |
51 |
> # CONFIG_MEMORY_HOTPLUG is not set |
52 |
> CONFIG_HOTPLUG_CPU=y |
53 |
> CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y |
54 |
> CONFIG_ACPI_HOTPLUG_CPU=y |
55 |
> # CONFIG_HOTPLUG_PCI is not set |
56 |
> CONFIG_NET=y |
57 |
> CONFIG_INET=y |
58 |
> CONFIG_WIRELESS_EXT_SYSFS=y |
59 |
> CONFIG_DEVTMPFS=y |
60 |
> CONFIG_DEVTMPFS_MOUNT=y |
61 |
> # CONFIG_SCSI_PROC_FS is not set |
62 |
> # CONFIG_ISCSI_BOOT_SYSFS is not set |
63 |
> CONFIG_ETHERNET=y |
64 |
> CONFIG_USB_USBNET=y |
65 |
> CONFIG_RTC_INTF_SYSFS=y |
66 |
> # CONFIG_DMI_SYSFS is not set |
67 |
> CONFIG_INOTIFY_USER=y |
68 |
> CONFIG_PROC_FS=y |
69 |
> CONFIG_SYSFS=y |
70 |
> |
71 |
> |
72 |
>> |
73 |
>> Also, if you can put this in one email, what about the /dev line in fstab? |
74 |
> |
75 |
> /dev should not be in /etc/fstab; but since you had this error: |
76 |
> |
77 |
>> switch_root: failed to mount moving /dev to /sysroot/dev: Invaild argument |
78 |
>> switch_root: forcing unmount of /dev |
79 |
>> switch_root: failed to unlink dev: Directory not empty |
80 |
> |
81 |
> I thought that it was maybe because you had /dev on fstab. Now we |
82 |
> know it was because you didn't compile DEVTMPFS in your kernel. |
83 |
> |
84 |
>> I didn't check the ebuild but I don't recall seeing anything when I |
85 |
>> emerged dracut either. o_O Maybe we are on to something here. ^_O |
86 |
> |
87 |
> The messages appear for sure; CONFIG_CHECK is defined in |
88 |
> /usr/portage/eclass/linux-info.eclass, and if a config option is |
89 |
> missing, a non-fatal warning will appear. If you have them, check your |
90 |
> emerge logs: |
91 |
> |
92 |
> cat /var/log/portage/sys-fs\:udev-* | less |
93 |
> |
94 |
> You can look for the string: |
95 |
> |
96 |
> * Checking for suitable kernel configuration options... |
97 |
> [ ok ] |
98 |
> |
99 |
> (Obviously that's in my case). |
100 |
> |
101 |
> You could also reemerge udev and dracut; if you haven't changed your |
102 |
> kernel config options, they will complain loudly about it. |
103 |
> |
104 |
> I think that will solve the mistery; however, we will not know until |
105 |
> you reboot and actually test it (after recompiling your kernel, of |
106 |
> course). |
107 |
> |
108 |
> Regards. |
109 |
|
110 |
|
111 |
I think I got it all sorted and am building a new kernel. It will have |
112 |
a -2 on the end instead of a -1. I'll test it in a bit. I got some |
113 |
things to prepare for tomorrow plus we have storms coming in tonight. |
114 |
The rain is already on the radar and it is a bit windy here. May take a |
115 |
bit before I reboot. Just depends. ;-) |
116 |
|
117 |
I'm hoping to get this sorted so I can then move on to more issues, and |
118 |
maybe a new thread. lol |
119 |
|
120 |
Will reply in a bit on what blows up. ROFL |
121 |
|
122 |
Dale |
123 |
|
124 |
:-) :-) |
125 |
|
126 |
-- |
127 |
I am only responsible for what I said ... Not for what you understood or |
128 |
how you interpreted my words! |
129 |
|
130 |
Miss the compile output? Hint: |
131 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |