On Mon, Apr 2, 2012 at 7:19 PM, Dale <rdalek1967@...> wrote:
> Canek Peláez Valdés wrote:
>> On Mon, Apr 2, 2012 at 5:21 PM, Dale <rdalek1967@...> wrote:
>>> Neil Bothwick wrote:
>>>> zgrep DEVTMP /proc/config.gz
>>> Ooops, it sort of snipped a bit much. lol Here you go:
>>> root@fireball / # zgrep DEVTMP /proc/config.gz
>>> # CONFIG_DEVTMPFS is not set
>>> root@fireball / #
>>> Looks like a nope to me. ;-)
>> That was the reason for asking for your /usr/src/linux/.config file.
>> The udev ebuild ask for:
>> CONFIG_CHECK="~BLK_DEV_BSG ~DEVTMPFS ~HOTPLUG ~INOTIFY_USER ~NET
>> ~PROC_FS ~SIGNALFD ~SYSFS ~!IDE ~!SYSFS_DEPRECATED
>> The dracut ebuild ask for:
>> CONFIG_CHECK="~BLK_DEV_INITRD ~DEVTMPFS ~MODULES"
>> So please check that you have all those options (and don't have the
>> ones with !), recompile your kernel, and reboot.
>> Also, the divergence between /boot/kernel... and (hd0,0)/kernel... in
>> your grub could be causing funny things. Check that also.
> OK. I hate modules. Can they be built into the kernel? The only
> module I have is nvidia for my video card.
MODULES is only for the kernel to be *able* to load modules, not to
*make* modules. If you use nvidia.ko, you must already have it. All
the options can be compiled into the kernel; I had them like that:
$ grep "BLK_DEV_BSG\\|DEVTMPFS\\|HOTPLUG\\|INOTIFY_USER\\|NET=\\|PROC_FS\\|SIGNALFD\\|SYSFS"
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_MEMORY_HOTPLUG is not set
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_SCSI_PROC_FS is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_DMI_SYSFS is not set
> Also, if you can put this in one email, what about the /dev line in fstab?
/dev should not be in /etc/fstab; but since you had this error:
> switch_root: failed to mount moving /dev to /sysroot/dev: Invaild argument
> switch_root: forcing unmount of /dev
> switch_root: failed to unlink dev: Directory not empty
I thought that it was maybe because you had /dev on fstab. Now we
know it was because you didn't compile DEVTMPFS in your kernel.
> I didn't check the ebuild but I don't recall seeing anything when I
> emerged dracut either. o_O Maybe we are on to something here. ^_O
The messages appear for sure; CONFIG_CHECK is defined in
/usr/portage/eclass/linux-info.eclass, and if a config option is
missing, a non-fatal warning will appear. If you have them, check your
cat /var/log/portage/sys-fs\:udev-* | less
You can look for the string:
* Checking for suitable kernel configuration options...
[ ok ]
(Obviously that's in my case).
You could also reemerge udev and dracut; if you haven't changed your
kernel config options, they will complain loudly about it.
I think that will solve the mistery; however, we will not know until
you reboot and actually test it (after recompiling your kernel, of
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México