From: oliver <ohem...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: musl - can't boot with kernel 4.0.6_1 (4.0.5_2 works)
Date: Tue, 14 Jul 2015 05:52:11 -0700 (PDT) [thread overview]
Message-ID: <88712e6e-c968-4ce7-b2bd-6d8bf44ea8fd@googlegroups.com> (raw)
In-Reply-To: <cdc2c093-17b2-4dd2-bc68-7af735d56e0b@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1162 bytes --]
Thanks for the great info!
On Tuesday, July 14, 2015 at 5:39:25 AM UTC-4, Ernesti Käpylä wrote:
>
> I had the exact same problem and it was caused by missing modules and
> drivers in dracut created initramfs that boots the kernel. Try booting to
> livecd or older kernel and run "lsinitrd
> /boot/initramfs-your-failing-kernel-version | less" and it should list
> included modules.
>
> Open /etc/dracut.conf and modify to include needed ones, in my case sata
> driver was missing and crypt module
>
> add_drivers+="ahci"
> add_dracutmodules+="crypt caps"
>
> next run sudo dracut -f /boot/initramfs-your-failing-kernel-version
> your-failing-kernel-version
>
> reboot and hopefully it works. If it still doesn't work you can try
> mkinitcpio.
>
> maanantai 13. heinäkuuta 2015 17.41.50 UTC+3 oliver kirjoitti:
>>
>> Further to this, I was able to re-create the problem every time using the
>> 6/15 MUSL ISO. As soon as the kernel is upgraded, the box fails to boot
>> (tried 4.0.x and 4.1.x)
>>
>> Installing from the 7/13 ISO (with kernel 4.1.2) worked so I think
>> whatever the problem was is now resolved.
>>
>
[-- Attachment #1.2: Type: text/html, Size: 1475 bytes --]
prev parent reply other threads:[~2015-07-14 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 13:25 oliver
2015-07-13 14:41 ` oliver
2015-07-14 9:39 ` Ernesti Käpylä
2015-07-14 12:52 ` oliver [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88712e6e-c968-4ce7-b2bd-6d8bf44ea8fd@googlegroups.com \
--to="ohem..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).