From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Need help booting allmodconfig on arm64
Date: Sat, 3 Jun 2017 00:10:06 +0100 [thread overview]
Message-ID: <20170602231006.GC4902@n2100.armlinux.org.uk> (raw)
In-Reply-To: <8fca2513-759d-3747-63f1-cd7d11b34ec2@codeaurora.org>
On Fri, Jun 02, 2017 at 06:01:55PM -0500, Timur Tabi wrote:
> On 06/02/2017 03:01 PM, Russell King - ARM Linux wrote:
> >ATA devices appear via the SCSI layer, which means you need the SCSI disk
> >driver, CONFIG_BLK_DEV_SD, for ATA disks to be visible as block devices.
>
> Great, that fixed that problem.
>
> I also had to set CONFIG_UNIX=y and CONFIG_AUTOFS4_FS=y so that udev would
> start, but it's still not quite 100% there. lsmod still shows no drivers
> being loaded. All of the modules were copied on the initramfs, why aren't
> they being loaded?
>
> A couple boot log messages stand out:
>
> [ TIME ] Timed out waiting for device
> dev-disk-by\x2duuid-AB6C\x2d1CCA.device.
> [DEPEND] Dependency failed for /boot/efi.
> [DEPEND] Dependency failed for Local File Systems.
Sounds like systemd? Systemd has a list of requirements that it makes
of the kernel, I guess you're missing some of those requirements.
Check the systemd docs (/usr/share/doc/systemd/README ?) under
"REQUIREMENTS".
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2017-06-02 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 22:43 Need help booting allmodconfig on arm64 Timur Tabi
2017-06-01 22:50 ` Russell King - ARM Linux
2017-06-01 23:26 ` Timur Tabi
2017-06-01 23:54 ` Florian Fainelli
2017-06-02 0:23 ` Timur Tabi
2017-06-02 8:36 ` Mark Rutland
2017-06-02 13:50 ` Timur Tabi
2017-06-02 20:01 ` Russell King - ARM Linux
2017-06-02 23:01 ` Timur Tabi
2017-06-02 23:10 ` Russell King - ARM Linux [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=20170602231006.GC4902@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).