From: Stefan Buschmann <s_buschmann@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: some RRECOMMENDed packages do not get included into the image
Date: Sun, 02 Aug 2009 12:50:55 +0200 [thread overview]
Message-ID: <4A756F8F.30405@gmx.de> (raw)
In-Reply-To: <200908021211.14793.mok@mnet-online.de>
Hi,
I'm experiencing problems with current SHR images as well. In my case,
everything gets built and the image is created successfully, but when I
boot into the system on my device, I get a few error messages like "no
sound device" for alsa, "no network card" etc., and the X server fails
to start. However the fso-daemons etc. seem to be working, or at least
starting, correctly.
I haven't been able to understand what is going wrong here, as I'm still
starting to learn how the whole openembedded/bitbake system works. I
turned on logging in the hope that I would find out why e.g. the
X-server is not starting, but found no helpful error messages in the
logs. I first thought it was a fault in my build system, but than I
started completely from scratch with the SHR-Makefile, and got the same
non-working image in the end. So, any tips on how to debug this?
Currently I'm working on the fso/milestone5.5 branch again, as this
still results in a working image. But I know that this is going to be
abandoned, soon...
Bye,
Stefan
next prev parent reply other threads:[~2009-08-02 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 10:11 some RRECOMMENDed packages do not get included into the image Klaus 'mrmoku' Kurzmann
2009-08-02 10:32 ` Nicola Mfb
2009-08-02 10:50 ` Stefan Buschmann [this message]
2009-08-02 11:04 ` Klaus 'mrmoku' Kurzmann
2009-08-04 7:48 ` Nicola Mfb
2009-09-21 17:03 ` Nicola Mfb
2009-09-21 18:05 ` [Shr-Devel] " Klaus 'mrmoku' Kurzmann
2009-09-22 13:11 ` Nicola Mfb
2009-09-22 14:35 ` Nicola Mfb
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=4A756F8F.30405@gmx.de \
--to=s_buschmann@gmx.de \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.