From: Gary Thomas <gary@mlbassoc.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Using RPM with Poky
Date: Mon, 21 Mar 2011 14:52:06 -0600 [thread overview]
Message-ID: <4D87BA76.3080406@mlbassoc.com> (raw)
In-Reply-To: <4D87B974.1040704@linux.intel.com>
On 03/21/2011 02:47 PM, Darren Hart wrote:
>
>
> On 03/21/2011 11:17 AM, Gary Thomas wrote:
>> On 03/21/2011 11:57 AM, Richard Purdie wrote:
>>> On Mon, 2011-03-21 at 10:35 -0600, Gary Thomas wrote:
>>>> On 03/21/2011 09:54 AM, Richard Purdie wrote:
>>>>> On Mon, 2011-03-21 at 09:25 -0600, Gary Thomas wrote:
>>>>>> I'm trying to do some testing with Poky on an atom-PC. I thought
>>>>>> I'd try with a minimal system and then add pieces I need. Sadly,
>>>>>> I've run aground doing this. I've built a couple of images with
>>>>>> varying results:
>>>>>> poky-image-minimal-live - boots on my box
>>>>>> poky-image-sato-live - boots, but fails to find X display, then
>>>>>> hangs (*)
>>>>>>
>>>>>> There seem to be no RPM tools on the minimal image. Did I miss
>>>>>> something?
>>>>>> On my old, ipk based system, I'd build up a minimal image then use
>>>>>> opkg
>>>>>> to install additional packages.
>>>>>
>>>>> Minimal images were never meant to ship with the package manager and
>>>>> now
>>>>> don't. You can obviously change the image definitions easily enough as
>>>>> needed.
>>>>>
>>>>>> How do I do that with the RPM based images?
>>>>>
>>>>> The same switch turns on/off the package manager data for rpm and opkg.
>>>>
>>>> I tried adding this to local.conf, but nothing changed when I build
>>>> minimal image:
>>>> IMAGE_FEATURES += " package-management ssh-server-dropbear "
>>>
>>> There is also this:
>>>
>>> # remove not needed ipkg informations
>>> ROOTFS_POSTPROCESS_COMMAND += "remove_packaging_data_files ; "
>>>
>>> in poky-image-minimal.bbclass which has been there for a long time and
>>> removes the package manager data files.
>>
>> I guess I'm just used to my own minimal image which does have all these
>> present.
>>
>>>
>>>> BTW, where is this documented? Not in the Poky handbook from what I
>>>> can tell.
>>>>
>>>> Also, is there documentation on how to use zypper, how to set up
>>>> repositories, etc?
>>>
>>> I think others have helped here. Please do send patches for the manual
>>> when people go to the trouble of finding information to help though!
>>
>> I'll see what I can do to help with this.
>>
>>>>>> I've checked the documentation and there's basically nothing
>>>>>> about this, unless I looked in the wrong place.
>>>>>>
>>>>>> Any ideas or pointers gladly accepted. Thanks
>>>>>>
>>>>>> (*) I had success with this in the past when I booted with
>>>>>> MACHINE=emenlow
>>>>>> but that hardware isn't in the primary list.
>>>>>
>>>>> I'm not sure why this isn't working or what the problem might be...
>>>>
>>>> It complains it can't find /dev/fb0. See the boot log at
>>>> http://www.mlbassoc.com/poky/boot_2011-03-21.log
>>>
>>> Does your board have Intel graphics or PVR/SGX? emenlow has PVR/SGX
>>> which might explain this...
>>
>> I'm not familiar with the details - it's an older Atom with the Poulsbo
>> chipset.
>> The details (cpuinfo, lspci) are at
>> http://www.mlbassoc.com/poky/cpu_2011-03-21.info
>> The kernel is also not finding my SATA controller - should I expect that
>> to work?
>
> I'd suggest trying the meta-emenlow BSP from the meta-intel layer and see if you make it further as it also uses the Poulsbo chipset. Tom Z. on CC as he has the most experience
> with that BSP.
I'd be happy to try, but it doesn't build the kernel (already reported)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-21 20:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 15:25 Using RPM with Poky Gary Thomas
2011-03-21 15:54 ` Richard Purdie
2011-03-21 16:35 ` Gary Thomas
2011-03-21 17:00 ` Mark Hatle
2011-03-21 17:04 ` Gary Thomas
2011-03-21 17:10 ` Paul Eggleton
2011-03-21 17:57 ` Richard Purdie
2011-03-21 18:17 ` Gary Thomas
2011-03-21 20:47 ` Darren Hart
2011-03-21 20:52 ` Gary Thomas [this message]
2011-03-21 18:27 ` Darren Hart
2011-03-21 18:33 ` Gary Thomas
2011-03-21 19:45 ` Darren Hart
2011-03-21 20:20 ` Gary Thomas
2011-03-21 20:25 ` Bruce Ashfield
2011-03-21 21:02 ` Tom Zanussi
2011-03-21 22:58 ` Gary Thomas
2011-03-21 23:24 ` Darren Hart
2011-03-22 0:55 ` Gary Thomas
2011-03-22 2:49 ` Darren Hart
2011-03-22 11:20 ` Gary Thomas
2011-03-22 6:22 ` Tom Zanussi
2011-03-22 22:58 ` Tom Rini
2011-03-22 23:30 ` 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=4D87BA76.3080406@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=dvhart@linux.intel.com \
--cc=poky@lists.pokylinux.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