From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] Early image startup
Date: Fri, 08 Apr 2011 08:01:36 -0600 [thread overview]
Message-ID: <4D9F1540.6020902@mlbassoc.com> (raw)
In-Reply-To: <1302270609.22904.128.camel@rex>
On 04/08/2011 07:50 AM, Richard Purdie wrote:
> On Fri, 2011-04-08 at 15:30 +0200, Koen Kooi wrote:
>> Op 8 apr 2011, om 15:20 heeft Gary Thomas het volgende geschreven:
>>
>>> I have a Poky image which uses a number of kernel modules. For
>>> whatever reason, the raw image has not had the modules configured
>>> (no /lib/modules/.../modules.dep) This file is created by 'update-modules'
>>> but that is run too late in the boot process. The problem is that
>>> other code, e.g. I'm using iptables via modules, requires the modules
>>> be configured early and this fails. If I reboot (after 'update-modules'
>>> has run), everything is fine.
>>
>> Sound like you need http://patches.openembedded.org/patch/1917/
>
> To be honest that sounds like a more fundamental problem as if the user
> cares which rtc should be rtc0, there are other ordering constraints
> being imposed such as a symlink to the "best" rtc device...
Indeed, this patch did not help my situation at all.
I think my problem is that of post-install package scripts (hence
'Configuring ...') not being run until quite late.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-04-08 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D9F0B82.9080803@mlbassoc.com>
2011-04-08 13:30 ` [poky] Early image startup Koen Kooi
2011-04-08 13:50 ` Richard Purdie
2011-04-08 14:01 ` Gary Thomas [this message]
2011-04-08 14:07 ` Gary Thomas
2011-04-08 14:17 ` Gary Thomas
2011-04-08 16:40 ` Hatle, Mark
2011-04-08 17:03 ` Gary Thomas
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=4D9F1540.6020902@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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