Processed: Re: Bug#760127: initramfs-tools: creating initrd fails

2014-09-27 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 Cannot find root device if booted without initramfs; MODULES=dep > fails Bug #760127 [initramfs-tools] update-initramfs failed when running non-modular 3.16 kernel and installing 3.14-2-amd64 Bug #760126 [initramfs-tools] update-initramfs failed when run

Bug#760127: initramfs-tools: creating initrd fails

2014-09-27 Thread Ben Hutchings
Control: retitle -1 Cannot find root device if booted without initramfs; MODULES=dep fails On Sat, 2014-09-27 at 19:56 -0400, westlake wrote: > If someone tests it without any kernel modules paths (/lib/modules > empty), and with a kernel(not needing an initrd in /boot as well), > apt-get insta

Bug#760127: initramfs-tools: creating initrd fails

2014-09-27 Thread westlake
If someone tests it without any kernel modules paths (/lib/modules empty), and with a kernel(not needing an initrd in /boot as well), apt-get install kernel will fail I can understand why nobody wants to verify anything here because it takes time to compile a kernel without "initrd" nor any /l

Bug#760127: initramfs-tools: creating initrd fails

2014-09-27 Thread Ben Hutchings
On Sat, 2014-09-27 at 15:25 -0400, westlake wrote: > apt-get install linux-image-3.14-2-amd64 and fails. But it works for me, so how am I supposed to know in what way it went wrong for you? > I suggest to close the bug because nobody is using a custom kernel. That is not true; many Debian users

Bug#760127: initramfs-tools: creating initrd fails

2014-09-27 Thread westlake
apt-get install linux-image-3.14-2-amd64 and fails. I suggest to close the bug because nobody is using a custom kernel. The scripts are looking for /lib/modules/ where kernel version=="My unpackaged kernel that has been copied to /boot". And this is the running kernel. I already explained w

Bug#760127: initramfs-tools: creating initrd fails

2014-09-27 Thread Ben Hutchings
On Fri, 2014-09-26 at 21:39 -0400, westlake wrote: > "WARNING: missing /lib/modules/3.16.1--std-ipv6-64-vps" > > ^ Already implies the kernel since the first message. I thought the > provided information was replicable enough. > > If someone wants to test this out, be my guest. I'm just go

Bug#760127: initramfs-tools: creating initrd fails

2014-09-26 Thread westlake
"WARNING: missing /lib/modules/3.16.1--std-ipv6-64-vps" ^ Already implies the kernel since the first message. I thought the provided information was replicable enough. If someone wants to test this out, be my guest. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with

Bug#760127: initramfs-tools: creating initrd fails

2014-09-26 Thread westlake
(/boot/bzImage-3.16.1--std-ipv6-64 to be more complete, but it occurs with any kernel that doesn't have modules built externally) /boot/3.16.1--std-ipv6-64-vps and it doesn't have any modules external of it(this is by intention to minimize surface attacks on a thanks -- To UNSUBSCR

Bug#760127: initramfs-tools: creating initrd fails

2014-09-26 Thread Ben Hutchings
On Fri, 2014-09-26 at 11:33 -0400, westlake wrote: > the kernel version is quite irrelevant [...] It is very relevant as mkinitramfs cannot read your mind. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digital

Bug#760127: initramfs-tools: creating initrd fails

2014-09-26 Thread westlake
the kernel version is quite irrelevant because it occurs with any custom kernel that does not have "modules" built outside the kernel. So it happens for 3.14, 3.15 and 3.16 kernels that don't have any /lib/modules/ paths needed for them. The problem is dramatic because I would be using such a

Bug#760127: initramfs-tools: creating initrd fails

2014-09-25 Thread Ben Hutchings
Control: tag -1 moreinfo You wrote: > a booted custom kernel is being used and installing a new kernel package > fails as the initramfs script in /etc/kernel/postinst.d/ fails In what way does it fail? What are the error messages? > apt-get install linux-image-3.14-2-amd64 was issued > , and m

Bug#760127: initramfs-tools: creating initrd fails

2014-09-01 Thread westlake
update: path actually -> /etc/initramfs-tools/conf.d/driver-policy Not sure if this is a bug or not but it prevents a kernel install from completing. My apology for sending report 760126 without a proper subject heading, thanks mika and everyone revising. -- To UNSUBSCRIBE, email to debian-

Bug#760127: initramfs-tools: creating initrd fails

2014-09-01 Thread westlake
fwiw I commented-out line "MODULES=dep" (there's only one line in this file) /etc/initramfs-tools/initramfs.conf and installation(apt-get -f install) was able to complete while making an initrd image for kernel 3.14-2-amd64 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org wi

Bug#760127: initramfs-tools: creating initrd fails

2014-08-31 Thread westlake
Package: initramfs-tools Version: 0.116 Severity: important a booted custom kernel is being used and installing a new kernel package fails as the initramfs script in /etc/kernel/postinst.d/ fails apt-get install linux-image-3.14-2-amd64 was issued , and mkinitramfs also fails ' mkinitramfs -k