From mboxrd@z Thu Jan  1 00:00:00 1970
From: iain@mcfarlanes.me (Iain McFarlane)
Date: Wed, 21 Oct 2015 22:31:45 +0100
Subject: I/O issues with writing to mtdblock devices on kirkwood
In-Reply-To: <CAKzmTe2Z2hOTuHYcXx9HUjJbri1Tm9qwye-rxxsWNxrsjGqp+w@mail.gmail.com>
References: <1444722697.16876.55.camel@debian.org>
 <5626B4DC.8000407@mcfarlanes.me> <5627F4E8.3030907@mcfarlanes.me>
 <1445461864.32735.21.camel@debian.org> <5628022A.9050707@mcfarlanes.me>
 <CAKzmTe2Z2hOTuHYcXx9HUjJbri1Tm9qwye-rxxsWNxrsjGqp+w@mail.gmail.com>
Message-ID: <56280441.1010007@mcfarlanes.me>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

On 21/10/15 22:28, JM wrote:
> On Wed, Oct 21, 2015 at 11:22 PM, Iain McFarlane <iain@mcfarlanes.me> wrote:
>> 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.
>>
> If you see something like ' kmod_search_moddep() could not open moddep
> file' in your logs, you need to run depmod -a manually.
>
> I've had it happen once for not entirely clear reasons, but probably
> related to the interrupted kernel package installation.
>
> HTH,
> Jan
>
> PS Now we have Ian, Iain and Jan posting in this thread.
>
I tried that but no luck - any other ideas?