Re: cryptsetup failing on boot with 3.4.x kernels
On Tue, 12 Jun 2012 15:32:28 -0400
Tom H <tomh0665@gmail.com> wrote:
> On Tue, Jun 12, 2012 at 2:23 PM, Celejar <celejar@gmail.com> wrote:
> > On Tue, 12 Jun 2012 11:17:35 -0400
> > Tom H <tomh0665@gmail.com> wrote:
> >> On Tue, Jun 12, 2012 at 9:41 AM, Jon Dowland <jmtd@debian.org> wrote:
> >> > On Sun, Jun 10, 2012 at 10:19:13PM -0400, Celejar wrote:
> >> >>
> >> >> Hand built from vanilla upstream sources.
> >> >
> >> > If you need/want a 3.4 kernel, there are debian packages for them in
> >> > experimental. It might be worth trying them and seeing if that works. If you
> >> > need a hand-built/customized kernel, I've ran out of ideas :)
> >>
> >> Are the 3.4 initramfs and a previous working initramfs different?
> >
> > It's not an exact, bitwise copy, but I don't really know what to look
> > for in terms of significant differences.
>
> Bitwise?! :)
>
> No, content. You can either unpack them both or use lsinitramfs.
Okay, I think I've found the problem. When configuring the 3.4, I
turned off SATA AHCI support (CONFIG_SATA_AHCI). The kernel devs really
need to rethink some of those "if unsure, say n" messages ;)
I guess they assume that those building kernels generally know what
they're doing, but still ...
I'll report back if / when the rebuilt 3.4 works.
> You can also, as a test, at the grub menu, edit the 3.4 initrd line to
> point to working initramfs to check whether'll the box'll boot.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] CAOdo=SyXeA9yXpA5jgpSQvsZ0OZGSxb40-QFXwT3phN0Qu=_pw@mail.gmail.com">http://lists.debian.org/[🔎] CAOdo=SyXeA9yXpA5jgpSQvsZ0OZGSxb40-QFXwT3phN0Qu=_pw@mail.gmail.com
Celejar
Reply to: