When genkernel is used to build a UDEV-based kernel and initrd, mounting an md-based root filesystem fails because /dev/md* don't exist, either in the initrd's underlying /dev directory or in the mounted udev filesystem. GRUB reports that /dev/md3 does not exist. If I enter the recovery shell, unmount /dev and create the device nodes manually.then exit the recovery shell and try to mount root on /dev/md3 again, I get an Input/output error, although the fileystem is mountable from a LiveCD. I'm using genkernel-3.1.6. The grub clause looks like this: title=Gentoo Linux 2.6.11-r11 root (hd0,0) kernel /kernel-2.6.11-gentoo-r11 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/md3 doscsi udev initrd /initrd-2.6.11-gentoo-r11 The md driver is not linked into the kernel, but is included in the initrd (because I modified modules_load) and it is loaded (I checked the boot sequence prior to the root mount attempt). Obviously, I can link the md driver into the kernel and use root=/dev/md3. But I'm trying to produce a one-size-fits-most kernel and initrd to reduce my management overheads. And if I specify the md device as the root partition, I may as well not use genkernel. Can something be done here, or is this just not going to work and I have to suck it up and link md into the kernel? If the latter, and you're sure, please feel free to close this bug. It'll remain as a useful reference for other intrepid adventurers. Reproducible: Always Steps to Reproduce: Build a 2.6.11-gentoo-r11 kernel and initrd using: genkernel --no-bootsplash --no-gensplash --udev --install all Make sure that the md driver is built as a module, not linked into the kernel.
I think we're going to have to end up manually making the device nodes depending on real_root... udev doesn't pick up /dev/mdX... :/
What about device tarball ("not pure UDEV") support, which would probably have more general application?
The problem is with the actual md driver in-kernel. It doesn't create device nodes properly if it is built as a module. As for the device node tarball support, I definitely have no desire to ever re-enable it in catalyst or on any release, so that isn't a viable option in my eyes. This was actually just recently discussed on the gentoo-dev mailing list, so it is possible that a proper fix might be forthcoming in the near future.
Fixed in 3.2.2; please test that and reopen this bug if issues still occur.
Still doesn't work for me :-( Environment: md compiled into kernel raid1 compiled into kernel partition type raid-autodetect /etc/lilo.conf: lba32 large-memory boot=/dev/md0 raid-extra-boot=mbr-only root=/dev/md1 prompt delay=20 timeout=100 install=text map=/boot/System.map-genkernel-x86-2.6.12-gentoo-r4 append="noapic hda=4998,255,63 hde=4998,255,63 init=/linuxrc root=/dev/ram0 real_root=/dev/md1 elevator=deadline gentoo=nodevfs udev" image=/boot/kernel-genkernel-x86-2.6.12-gentoo-r4 label="gentoo" initrd=/boot/initramfs-genkernel-x86-2.6.12-gentoo-r4 addappend="video=vesafb:1024x768-24@75 splash=silent,fadein,theme:livecd-2005.1 quiet CONSOLE=/dev/tty1" image=/boot/kernel-2.6.12-gentoo-r4 label="gentoo-old" initrd=/boot/initrd-2.6.12-gentoo-r4 addappend="video=vesafb:1024x768-24@75 splash=silent,fadein,theme:livecd-2005.1 quiet CONSOLE=/dev/tty1" /etc/fstab: # <fs> <mountpoint> <type> <opts> <dump/pass> /dev/md1 / jfs defaults 1 1 /dev/md0 /boot jfs defaults,noauto 1 1 /dev/md2 /home jfs defaults 1 2 /dev/md3 /tmp jfs defaults 1 2 /dev/md4 /usr jfs defaults 1 2 /dev/md5 /var jfs defaults 1 2 /dev/mapper/crypt-swap none swap sw 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/cdroms/cdrom0 /mnt/cdrom iso9660 defaults,noauto,user,ro 0 0 /dev/pktcdvd/pktcdvd0 /mnt/dvd udf defaults,noauto,noatime 0 0 /dev/fd0 /mnt/floppy auto defaults,noauto,user,sync 0 0 bootup messages: -install: applet not found /init: 41: ln: not found /init: 45: cat: not found /init: 150: sed: not found >> Loading modules /init: 172: touch: not found /init: 172: cat: not found /init: 172: sed: not found /init: 1: touch: not found /init: 1: cat: not found /init: 1: sed: not found /init: 1: touch: not found /init: 1: cat: not found /init: 1: sed: not found /init: 1: touch: not found /init: 1: cat: not found /init: 1: sed: not found >> Activating udev /init: 178: mkdir: not found /init: 178: mkdir: not found /init: 178: /sbin/udevstart: not found /init: 178: ln: not found /init: 178: ln: not found /init: 178: ln: not found /init: 178: ln: not found /init: 178: ln: not found /init: 181: sed: not found [: /dev/md: unknown operand /init: 187: mkdir: not found >> Determining root device... !! The root block device is unspecified or not detected. Please specify a device to boot, or "shell" for a shell... boot fails for the gentoo LILO image created with genkernel-3.2.2 boot succeeds for the gentoo-old LILO image created with genkernel-3.1.6 Question: Does initramfs require the same init=, root= and real_root= arguments to the kernel command line as initrd does? Regards, Neil Darlow
it appears your busybox installation is broken. Did you change its configuration? If so please remerge genkernel to get the standard busybox config to load. please remove the contents of /usr/share/genkernel/pkg/x86 and try running genkernel again.
> it appears your busybox installation is broken. Selectively broken for genkernel-3.2.2 but not for genkernel-3.1.6? > Did you change its configuration? I haven't touched anything to do with busybox. busybox-1.00-r4 was emerged onto my system a while back as a dependency of something and hasn't been touched since. > If so please remerge genkernel to get the standard busybox config to load. Did that. There was some stuff left behind by previous genkernel versions. Shouldn't a genkernel version update (not revision) clear the cache directory? > please remove the contents of /usr/share/genkernel/pkg/x86 and try running > genkernel again. Did that too. The boot verbose output was: >> Loading modules ... ... >> Activating udev >> real_root is a md device. Setting up the device node (If necessary)... >> Creation of /dev/md1 Succeeded... >> Determining root device... mount: Mounting /dev/md1 on /newroot failed. Invalid argument !! Could not mount specified ROOT, try again !! The root block device is unspecified or not detected. Please specify a device to boot, or "shell" for a shell... I'm prepared to accept there was an inconsistency with the cache directory but I don't believe it's come about as a result of me changing anything or my system becoming corrupted. I'm more inclined to think that genkernel should do a little more cleaning-up at version updates. I think there's a problem lurking in the initramfs md boot logic. The previous initrd-based boot still works fine. Regards, Neil Darlow
Reopening this bug as it appears to still be an issue.
As we dont normally use md and dont have a test system setup to replicate this issue. We cant troubleshoot the cause of this at the moment. It appears compiling it into the kernel works for you so that is probably what you should do for now. I am reassigning this bug to the udev team as there appears to be a bug with udev and md as a module from my google searches. In the near future if time permits I hope to have a test system setup to work on this issue. If you find a fix and post it we will be happy to incorporate it into the next genkernel release.
(In reply to comment #9) > compiling it into the kernel works for you so that is probably what you should > do for now. The problem affects MD root whether compiled-in or as a mnodule. It only works for me with genkernel-3.1.6, and earlier, with initrd. Regards, Neil Darlow
Eh? You say genkernel-3.1.6 _did_ work for you with initrd, using UDEV? That was the version of genkernel for which I reported this bug in the first place! :-) To rocket@gentoo.org: I'm testing all this under vmware, so if you come up with any snapshots you'd like me to try to test this bug, it's not much work for me.
We may have a patch shortly. We are adding mdadm to the initrd/initramfs with the --mdadm option. though we will need to see if the scripts work properly to enable the md devices etc at that point.
(In reply to comment #11) > Eh? You say genkernel-3.1.6 _did_ work for you with initrd, using UDEV? Yes BUT md and raid1 are compiled into my kernel and using udev. When adding mdadm support, please consider the case where the raid devices are auto-started by the kernel (partition type raid-autodetect). The last thing we need is for it to break due to attempting to start an already running array. Don't feel bad guys, I've had to work through this one with every distribution I've used (to date Red Hat, Debian and Mandrake). Regards, Neil Darlow
(In reply to comment #0) > When genkernel is used to build a UDEV-based kernel and initrd, mounting an > md-based root filesystem fails because /dev/md* don't exist, either in the > initrd's underlying /dev directory or in the mounted udev filesystem. GRUB > reports that /dev/md3 does not exist. > > If I enter the recovery shell, unmount /dev and create the device nodes > manually.then exit the recovery shell and try to mount root on /dev/md3 again, > I get an Input/output error, although the fileystem is mountable from a > LiveCD. > > I'm using genkernel-3.1.6. > > The grub clause looks like this: > > title=Gentoo Linux 2.6.11-r11 > root (hd0,0) > kernel /kernel-2.6.11-gentoo-r11 root=/dev/ram0 init=/linuxrc ramdisk=8192 > real_root=/dev/md3 doscsi udev > initrd /initrd-2.6.11-gentoo-r11 > > The md driver is not linked into the kernel, but is included in the initrd > (because I modified modules_load) and it is loaded (I checked the boot > sequence prior to the root mount attempt). > > Obviously, I can link the md driver into the kernel and use root=/dev/md3. > But I'm trying to produce a one-size-fits-most kernel and initrd to reduce my > management overheads. And if I specify the md device as the root partition, I > may as well not use genkernel. > > Can something be done here, or is this just not going to work and I have to > suck it up and link md into the kernel? If the latter, and you're sure, > please feel free to close this bug. It'll remain as a useful reference for > other intrepid adventurers. > > Reproducible: Always > Steps to Reproduce: > Build a 2.6.11-gentoo-r11 kernel and initrd using: > > genkernel --no-bootsplash --no-gensplash --udev --install all > > Make sure that the md driver is built as a module, not linked into the kernel. hey guys. i opened another bug almost identical to this one. this is happening to me as well when i use genkernel to build a udev kernel. udev seems to really hose the boot process, and i'm left without a paddle when i try to boot using root console. genkernel --version 3.2.3 linux-2.6.12-gentoo-r5 bootup messages: -install: applet not found /init: 41: ln: not found /init: 45: cat: not found /init: 150: sed: not found >> Loading modules /init: 172: touch: not found /init: 172: cat: not found /init: 172: sed: not found /init: 1: touch: not found /init: 1: cat: not found /init: 1: sed: not found /init: 1: touch: not found /init: 1: cat: not found /init: 1: sed: not found /init: 1: touch: not found /init: 1: cat: not found /init: 1: sed: not found >> Activating udev /init: 178: mkdir: not found /init: 178: mkdir: not found /init: 178: /sbin/udevstart: not found /init: 178: ln: not found /init: 178: ln: not found /init: 178: ln: not found /init: 178: ln: not found /init: 178: ln: not found /init: 181: sed: not found [: /dev/md: unknown operand /init: 187: mkdir: not found >> Determining root device... !! The root block device is unspecified or not detected. Please specify a device to boot, or "shell" for a shell... eep!
rm /usr/share/genkernel/pkg/x86/* and then rerun genkernel and it should fix this issue.
I've just emerged from 3.1.6 up to 3.2.5 and have the following error with the --dmraid option. This is from the /var/log/genkernel.log * dmraid: >> Compiling... COMMAND: make -j2 CC="gcc" LD="ld" AS="as" make -C lib make[1]: Entering directory `/var/tmp/genkernel/dmraid/1.0.0.rc8/lib' gcc -MM -MF activate/activate.d -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -Wshadow -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/activate.c; \ gcc -c -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -Wshadow -Wmissing-protot ypes -Wmissing-declarations -Wnested-externs -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/activate.c -o activate/activate.o gcc -MM -MF activate/devmapper.d -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -Wshadow -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/devmapper.c; \ gcc -c -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -Wshadow -Wmissing-protot ypes -Wmissing-declarations -Wnested-externs -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/devmapper.c -o activate/devmapper.o activate/devmapper.c:12:26: libdevmapper.h: No such file or directory activate/devmapper.c: In function `mkdm_path': activate/devmapper.c:29: warning: implicit declaration of function `dm_dir' activate/devmapper.c:29: warning: initialization makes pointer from integer without a cast activate/devmapper.c: In function `_init_dm': activate/devmapper.c:49: warning: implicit declaration of function `dm_log_init' activate/devmapper.c: At top level: activate/devmapper.c:53: warning: `struct dm_task' declared inside parameter list activate/devmapper.c:53: warning: its scope is only this definition or declaration, which is probably not what you want activate/devmapper.c: In function `_exit_dm': activate/devmapper.c:56: warning: implicit declaration of function `dm_task_destroy' activate/devmapper.c:58: warning: implicit declaration of function `dm_lib_release' activate/devmapper.c:59: warning: implicit declaration of function `dm_lib_exit' activate/devmapper.c: In function `get_target_list': activate/devmapper.c:72: warning: implicit declaration of function `dm_task_create' activate/devmapper.c:72: error: `DM_DEVICE_LIST_VERSIONS' undeclared (first use in this function) activate/devmapper.c:72: error: (Each undeclared identifier is reported only once activate/devmapper.c:72: error: for each function it appears in.) activate/devmapper.c:72: warning: assignment makes pointer from integer without a cast activate/devmapper.c:73: warning: implicit declaration of function `dm_task_run' activate/devmapper.c:74: warning: implicit declaration of function `dm_task_get_versions' activate/devmapper.c:74: warning: pointer/integer type mismatch in conditional expression activate/devmapper.c: In function `valid_ttype': activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:94: error: dereferencing pointer to incomplete type activate/devmapper.c:98: error: dereferencing pointer to incomplete type activate/devmapper.c: At top level: activate/devmapper.c:109: warning: `struct dm_task' declared inside parameter list activate/devmapper.c: In function `handle_table': activate/devmapper.c:133: warning: implicit declaration of function `dm_task_add_target' activate/devmapper.c: At top level: activate/devmapper.c:141: warning: `struct dm_task' declared inside parameter list activate/devmapper.c: In function `parse_table': activate/devmapper.c:143: warning: passing arg 2 of `handle_table' from incompatible pointer type activate/devmapper.c: In function `dm_create': activate/devmapper.c:162: error: `DM_DEVICE_CREATE' undeclared (first use in this function) activate/devmapper.c:162: warning: assignment makes pointer from integer without a cast activate/devmapper.c:163: warning: implicit declaration of function `dm_task_set_name' activate/devmapper.c:164: warning: passing arg 2 of `parse_table' from incompatible pointer type activate/devmapper.c:170: warning: passing arg 1 of `_exit_dm' from incompatible pointer type activate/devmapper.c: In function `dm_remove': activate/devmapper.c:184: error: `DM_DEVICE_REMOVE' undeclared (first use in this function) activate/devmapper.c:184: warning: assignment makes pointer from integer without a cast activate/devmapper.c:188: warning: passing arg 1 of `_exit_dm' from incompatible pointer type activate/devmapper.c: In function `dm_status': activate/devmapper.c:199: error: storage size of `info' isn't known activate/devmapper.c:204: error: `DM_DEVICE_STATUS' undeclared (first use in this function) activate/devmapper.c:204: warning: assignment makes pointer from integer without a cast activate/devmapper.c:207: warning: implicit declaration of function `dm_task_get_info' activate/devmapper.c:210: warning: passing arg 1 of `_exit_dm' from incompatible pointer type activate/devmapper.c:199: warning: unused variable `info' activate/devmapper.c: In function `dm_version': activate/devmapper.c:226: error: `DM_DEVICE_VERSION' undeclared (first use in this function) activate/devmapper.c:226: warning: assignment makes pointer from integer without a cast activate/devmapper.c:228: warning: implicit declaration of function `dm_task_get_driver_version' activate/devmapper.c:230: warning: passing arg 1 of `_exit_dm' from incompatible pointer type make[1]: *** [activate/devmapper.o] Error 1 make[1]: Leaving directory `/var/tmp/genkernel/dmraid/1.0.0.rc8/lib' make: *** [lib] Error 2 * Gentoo Linux Genkernel; Version 3.2.5 * Running with options: --dmraid all COMMAND: make -j2 CC="gcc" LD="ld" AS="as" prepare * ERROR: Failed to compile the "" target... My emerge --info details as follows: Portage 2.0.51.19 (hardened/x86/2.6, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.11-hardened-r15 i686) ================================================================= System uname: 2.6.11-hardened-r15 i686 VIA Nehemiah Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 10 2005, 20:47:05)] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://194.117.143.72 ftp://ftp.heanet.ie/pub/gentoo/ ftp://194.117.143.72/mirrors/gentoo http://ftp.snt.utwente.nl/pub/os/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage//packages/x86/" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage/" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="berkdb crypt dlloader gpm ncurses nls nptl nptlonly pam perl python readline ssl tcpd userlocales x86 zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
You need to install device-mapper. Now, PLEASE post new bugs in a new bug and NOT as a comment in an already existing bug. This bug is ONLY about software raid via md not working with udev. Thanks
Nice work people. genkernel-3.2.5 fixes the case with md and raidX compiled into the kernel. Regards, Neil Darlow
Excellent!
Hello, I'm on ~amd64 and this bug is present for me :( I still have the problem witout using genkernel. The boot process can't find the root device because /dev/md* are not present in the /dev directory. I need to enter the root password and launch udevstart for find all the devices. I use a 2.6.11-gentoo-r11 and the bug is only present with udev > 059. udev-059 work just fine, 060, 062, 063 don't work at all :( If you have a workaround in genkernel why not in the main baselayout ?? I need to stick with udev-059 for the moment. my emerge --info : Portage 2.0.51.22-r1 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r0, 2.6.11-gentoo-r11 x86_64) ================================================================= System uname: 2.6.11-gentoo-r11 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.13 ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r8, 2.16.90.0.3, 2.16.91.0.1 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=k8 -mtune=k8 -momit-leaf-frame-pointer -ftracer -ggdb -pipe -mmmx -msse -msse2 -m3dnow -feliminate-dwarf2-dups " CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=k8 -mtune=k8 -momit-leaf-frame-pointer -ftracer -ggdb -pipe -mmmx -msse -msse2 -m3dnow -feliminate-dwarf2-dups " DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks nostrip sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://mirror.switch.ch/mirror/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo" LC_ALL="fr_FR.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.fr.gentoo.org/gentoo-portage" USE="X X509 Xaw3d a52 aac acl acpi acpi4linux adns alsa amd64 apache2 artworkextra audiofile avi bash-completion berkdb bitmap-fonts bluetooth bmp bonobo bzip2 c++ cairo caps cddb cdr chroot crypt cups curl dbm dbus dga dmx dts dv dvd eds encode esd evo exif expat ext-png ext-zlib fam fbcon ffmpeg foomaticdb fortran ftp gcc-libffi gcj gd gd-external gdbm gif gimp gimpprint gkrellm glade gnome gnutls gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile hal howl ieee1394 imagemagick imap imlib imlib2 innodb ipv6 jabber java javamail jce jikes jpeg junit lame latex lcms ldap libwww lm_sensors logrotate lzo lzw lzw-tiff mad mime mng motif mozilla mp3 mpeg mpeg4 mysql ncurses nfs nls nptl objc ogg oggvorbis opengl oss pam pcre pda pdflib perl php png posix postgres ppds python quicktime readline real scanner sdl silc slang spell ssl svg sysfs syslog tcltk tcpd tetex tga theora threads tidy tiff tiff-lzw truetype truetype-fonts type1-fonts unicode usb userlocales vorbis xine xinerama xinetd xml xml2 xosd xpm xrandr xv xvid xvmc yahoo yv12 zeroconf zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS This bug need to be reopened or I can create a new one ? Thanks
If the problem is not the exact same as this one, then a new bug should be filed against the appropriate package.
Thanks for working on this. I'll test it today.
fyi I entered bug #100169 for a similiar but different case where genkernel 3.2.x is used to boot lvm2 on top of md0.
