From: ijc@debian•org (Ian Campbell)
To: linux-arm-kernel@lists•infradead.org
Subject: I/O issues with writing to mtdblock devices on kirkwood
Date: Thu, 22 Oct 2015 07:40:44 +0100 [thread overview]
Message-ID: <1445496044.32735.26.camel@debian.org> (raw)
In-Reply-To: <5628022A.9050707@mcfarlanes.me>
On Wed, 2015-10-21 at 22:22 +0100, Iain McFarlane wrote:
> >> 3.16 - No SATA errors when updating initrd - the kernel is flashed using
> >> dtb but how do I tell if it is used?
> [...]
> In which case it is using the board file
>
> How do I force it to use the dtb?
If the DTB has been appended then it should Just Happen on reboot, I
think. I'm 99% certain that the 3.16 kernel in Jessie had the options
to enable DTB on this platform turned on. Specifically it should have
CONFIG_ARCH_KIRKWOOD_DT=y.
You say "the kernel is flashed using the dtb", please could you post
the logs from flash-kernel to confirm this. And the dmesg from the
subsequent boot (whether board or DTB) would be useful too.
> On a different note anyone know why udev would not be running modprobe?
> Every time I reboot this box I have to the reload any of the modules not
> specified in the initrd even things like mvmdio to get the network working.
I've no smart ideas, but you could maybe workaround by listing them in
/etc/modules?
Ian
next prev parent reply other threads:[~2015-10-22 6:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 12:24 I/O issues with writing to mtdblock devices on kirkwood Ian Campbell
2015-08-21 13:07 ` Andrew Lunn
2015-08-21 20:23 ` Ian Campbell
2015-09-05 21:08 ` Andrew Lunn
2015-09-06 12:11 ` Ian Campbell
2015-10-11 14:37 ` JM
2015-10-11 15:35 ` Andrew Lunn
2015-10-12 14:29 ` JM
2015-10-12 16:05 ` Rob J. Epping
2015-10-12 16:21 ` Andrew Lunn
2015-10-13 7:51 ` Ian Campbell
[not found] ` <5626B4DC.8000407@mcfarlanes.me>
[not found] ` <5627F4E8.3030907@mcfarlanes.me>
2015-10-21 21:11 ` Ian Campbell
2015-10-21 21:22 ` Iain McFarlane
2015-10-21 21:28 ` JM
2015-10-21 21:31 ` Iain McFarlane
2015-10-22 0:38 ` Andrew Lunn
2015-10-22 6:40 ` Ian Campbell
2015-10-22 6:40 ` Ian Campbell [this message]
2016-01-11 23:00 ` Martin Michlmayr
2016-01-11 23:22 ` Mark Brown
2016-01-11 23:43 ` Andrew Lunn
2016-01-12 1:21 ` Mark Brown
2016-01-12 0:07 ` Martin Michlmayr
2016-01-12 0:47 ` Mark Brown
2016-01-12 1:19 ` Andrew Lunn
2016-01-12 1:31 ` Mark Brown
2016-01-12 16:29 ` Arnd Bergmann
2016-01-12 18:02 ` Mark Brown
2016-01-12 21:49 ` Arnd Bergmann
2016-01-12 22:00 ` Mark Brown
2016-01-12 22:41 ` Arnd Bergmann
2016-01-13 11:42 ` Mark Brown
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=1445496044.32735.26.camel@debian.org \
--to=ijc@debian$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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