Hello. I'm facing a weird problem. On my laptop, since kmod replaced modules-init-tools, I get (for my last linux kernel upgrade) : [2012-01-07 20:47] ==> Building image from preset: 'default' [2012-01-07 20:47] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/ initramfs-linux.img [2012-01-07 20:47] ==> Starting build: 3.2.0-2-ARCH [2012-01-07 20:47] -> Parsing hook: [base] [2012-01-07 20:47] -> Parsing hook: [udev] [2012-01-07 20:47] -> Parsing hook: [autodetect] [2012-01-07 20:47] libkmod: kmod_lookup_alias_from_alias_bin: File name too long [2012-01-07 20:47] -> Parsing hook: [pata] [2012-01-07 20:47] -> Parsing hook: [scsi] [2012-01-07 20:47] -> Parsing hook: [sata] [2012-01-07 20:47] -> Parsing hook: [filesystems] [2012-01-07 20:47] -> Parsing hook: [usbinput] [2012-01-07 20:47] ==> Generating module dependencies [2012-01-07 20:47] ==> Creating gzip initcpio image: /boot/initramfs-linux.img [2012-01-07 20:47] ==> Image generation successful [2012-01-07 20:47] ==> Building image from preset: 'fallback' [2012-01-07 20:47] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect [2012-01-07 20:47] ==> Starting build: 3.2.0-2-ARCH [2012-01-07 20:47] -> Parsing hook: [base] And I have to boot 3 or 4 times to get a kernel which mount my root partition ! ERROR: Unable to find root device 'UUID=cfbc185c-cab3-48c0-bb97-820134b14bfd'. You are being dropped to a recovery shell Type 'exit" to try and continue booting sh: can't access tty; job control turned off When I type exit : mount: you must specify the filesystem type You are being dropped into an emergency shell sh: can't access tty; job control turned off And last exit : ERROR: Failed to mount the real root device. Bailing out, you're on your own. Good Luck. sh: can't access tty; job control turned off Of course, UUID is good. Opened bug #27862. not a single problem with my desktop computer. Weird... And here is the log of linux 3.2-2 upgrade...
Generating initial ramdisk, using mkinitcpio. Please wait... ==> Building image from preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 3.2.0-2-ARCH -> Parsing hook: [base] -> Parsing hook: [udev] -> Parsing hook: [autodetect] -> Parsing hook: [pata] -> Parsing hook: [scsi] -> Parsing hook: [sata] -> Parsing hook: [filesystems] -> Parsing hook: [usbinput] ==> Generating module dependencies ==> Creating gzip initcpio image: /boot/initramfs-linux.img ==> Image generation successful ==> Building image from preset: 'fallback' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect ==> Starting build: 3.2.0-2-ARCH -> Parsing hook: [base] -> Parsing hook: [udev] -> Parsing hook: [pata] -> Parsing hook: [scsi] -> Parsing hook: [sata] -> Parsing hook: [filesystems] -> Parsing hook: [usbinput] ==> Generating module dependencies ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img ==> Image generation successful
Something is busted with kmod or what ? -- Frederic Bezies fredbezies@gmail.com