its .config built into your kernel.... i dont use it as i keep hard records of it in /boot i have used it and did advocate it in the past, just ive found other methods to the same ends, easier to cat than zcat... copy once and be done with it.... i actually have 2 records of it /boot/config.kernel-3.6.7 for kernel-3.6.7 and /usr/src/linux-3.6.7/.config 1s generally unmounted and 1s hidden, 3rd copy is a bit excessive, but i do agree, its the .config that the kernel is running, and known working.... i do keep a stale 3.5.4 and 3.6.2 kernel & config set around too incase 3.7.4 makes my old dv9000 hardware flip out and unbootable..... lol after re reading your post i realized your directing that to the other posters on the thread.....

udev-197 is up and running! sorry, for bothering you with my problems.

It was my fault!!!

Building Gentoo kernels since 2004 with genkernel, but it seems that something has changed in the past.

I always used "genkernel --menuconfig all", made my config and saved the config file to my home-directory using the save-option in the kernel menu (for later use, if I have to rebuild the kernel). This has worked in the past. But if I load the config file via the kernel menu and start compiling, my loaded config file is not used. Instead it uses the .config in /usr/src/linux !

I was able to fix this problem without going the rescue-disk way ... during boot I switched to Interactive boot, did not let udev load, and let the rest proceed normally. Then I used make menuconfig to fix the option and proceeded as per normal after such editing.

I was able to fix this problem without going the rescue-disk way ... during boot I switched to Interactive boot, did not let udev load, and let the rest proceed normally. Then I used make menuconfig to fix the option and proceeded as per normal after such editing.

cheers, Ian

In my case I tried npress "I" before start init but this not help. But will be good If you post some steps how you resolve this.

I was able to fix this problem without going the rescue-disk way ... during boot I switched to Interactive boot, did not let udev load, and let the rest proceed normally. Then I used make menuconfig to fix the option and proceeded as per normal after such editing.

cheers, Ian

In my case I tried npress "I" before start init but this not help. But will be good If you post some steps how you resolve this.

I found out the hard way (when my OTHER box would not boot) that there is a setting in /etc/conf.d/rc which enables this ... if it is set to no then you can't ....

Still trying to fix broken box ... the Live DVD fails to complete booting ( total waste of a 4GB download ... we need a small rescue disk please...) so trying with a minimal install CD which did complete booting ...

Think the live DVD fails because it doesn't like my LG blu-ray writer drive.

i generated documentation by hand in a note book so i could do gentoo installs with no net to see documentation (ie terminal only) and just a flash thumb drive. i still have links in terminal but its a pain to try to read the handbook as it has too many explanations and is far too verbose to do that. well i had net but was only using it to pull sources for emerge --sync and emerging goodies.

fair warning, these iso images are TERMINAL ONLY... so generate a notebook of documentation if you intend to use them. i use unetbootin if you go through the thread again you can find links to this to generate flash thumb drive rescue boot disks.

Still trying to fix broken box ... the Live DVD fails to complete booting ( total waste of a 4GB download ... we need a small rescue disk please...) so trying with a minimal install CD which did complete booting ...

I do believe that neither the LiveDVDs nor the Minimal Installation CDs are intended to be used as a 'rescue disk'.
Correct me if I'm wrong. ^^;

If you have not before, you might like to take a peek at the SystemRescueCd. That's what I always recommend at least, sometimes even for doing the initial installation of Gentoo. I used the Minimal Installation CD myself (which, I think, gives the realer experience, and that is an important part to include in the recommendation). Not that I even knew about the sysresccd existing back when I was taking my first steps...

It's very easy to put into a USB-stick, too!_________________Kind Regards,
~ The Noob Unlimited ~

I decided to upgrade to sys-fs/udev-200, so as usually happens I broke my system. So, fun , I lost 3 hours to fix it .
I was very careful following the instructions on http://www.gentoo.org/doc/en/udev-guide.xml . The following part of it broke my system ending with "kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0) Pid 1, comm: swapper Not tainted...":

It seems that the root cause is my old system and especially my old IBM ATA 30.7 GB hard disk (IC35L030AVVN07-0).
So, I set both CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y + CONFIG_IDE (ATA/ATAPI/MFM/RLL support (DEPRECATED)) was not set as advised above. Unfortunately my system ended with kernel panic.

I was not able to boot my old non-devtmpfs kernel with sys-fs/udev-200 as well. Finally, thanks to this topic I succeed to boot the old kernel like that:

Afterwards I rebuilt the kernel with CONFIG_IDE=y (+other sub parameters, see below) and CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y:

Quote:

[hostname] boot # diff config-3.8.13-gentoo_bad config-3.8.13-gentoo
682c682,748
< # CONFIG_IDE is not set
---
> CONFIG_IDE=y
>
> #
> # Please see Documentation/ide/ide.txt for help/info on IDE drives
> #
> CONFIG_IDE_XFER_MODE=y
> CONFIG_IDE_TIMINGS=y
> CONFIG_IDE_ATAPI=y
> # CONFIG_BLK_DEV_IDE_SATA is not set
> CONFIG_IDE_GD=y
> CONFIG_IDE_GD_ATA=y
> CONFIG_IDE_GD_ATAPI=y
> CONFIG_BLK_DEV_IDECD=y
> CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
> # CONFIG_BLK_DEV_IDETAPE is not set
> CONFIG_BLK_DEV_IDEACPI=y
> # CONFIG_IDE_TASK_IOCTL is not set
> CONFIG_IDE_PROC_FS=y
>
> #
> # IDE chipset support/bugfixes
> #
> CONFIG_IDE_GENERIC=y
> # CONFIG_BLK_DEV_PLATFORM is not set
> CONFIG_BLK_DEV_CMD640=y
> # CONFIG_BLK_DEV_CMD640_ENHANCED is not set
> # CONFIG_BLK_DEV_IDEPNP is not set
> CONFIG_BLK_DEV_IDEDMA_SFF=y
>
> #
> # PCI IDE chipsets support
> #
> CONFIG_BLK_DEV_IDEPCI=y
> CONFIG_IDEPCI_PCIBUS_ORDER=y
> # CONFIG_BLK_DEV_OFFBOARD is not set
> CONFIG_BLK_DEV_GENERIC=y
> # CONFIG_BLK_DEV_OPTI621 is not set
> CONFIG_BLK_DEV_RZ1000=y
> CONFIG_BLK_DEV_IDEDMA_PCI=y
> # CONFIG_BLK_DEV_AEC62XX is not set
> # CONFIG_BLK_DEV_ALI15X3 is not set
> # CONFIG_BLK_DEV_AMD74XX is not set
> # CONFIG_BLK_DEV_ATIIXP is not set
> # CONFIG_BLK_DEV_CMD64X is not set
> # CONFIG_BLK_DEV_TRIFLEX is not set
> # CONFIG_BLK_DEV_CS5520 is not set
> # CONFIG_BLK_DEV_CS5530 is not set
> # CONFIG_BLK_DEV_CS5535 is not set
> # CONFIG_BLK_DEV_CS5536 is not set
> # CONFIG_BLK_DEV_HPT366 is not set
> # CONFIG_BLK_DEV_JMICRON is not set
> # CONFIG_BLK_DEV_SC1200 is not set
> CONFIG_BLK_DEV_PIIX=y
> # CONFIG_BLK_DEV_IT8172 is not set
> # CONFIG_BLK_DEV_IT8213 is not set
> # CONFIG_BLK_DEV_IT821X is not set
> # CONFIG_BLK_DEV_NS87415 is not set
> # CONFIG_BLK_DEV_PDC202XX_OLD is not set
> # CONFIG_BLK_DEV_PDC202XX_NEW is not set
> # CONFIG_BLK_DEV_SVWKS is not set
> # CONFIG_BLK_DEV_SIIMAGE is not set
> # CONFIG_BLK_DEV_SIS5513 is not set
> # CONFIG_BLK_DEV_SLC90E66 is not set
> # CONFIG_BLK_DEV_TRM290 is not set
> # CONFIG_BLK_DEV_VIA82CXXX is not set
> # CONFIG_BLK_DEV_TC86C001 is not set
> CONFIG_BLK_DEV_IDEDMA=y
[hostname] boot #