Skip to contentSkip to conversation

Using RPM with Poky

DISCUSSION Gary Thomas 8 participants 24 messages Mar 21, 2011 – Mar 22, 2011

lore
Share & tools
lore
#0 lore raw

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. How do I do that with the RPM based images? 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.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 10 lines · Gary Thomas

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.

Quoted 1 line

How do I do that with the RPM based images?

The same switch turns on/off the package manager data for rpm and opkg.

Quoted 7 lines

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...

You didn't mention which branch this is with btw.

Cheers,

Richard

#2 lore raw
Quoted 12 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

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.

Quoted 7 lines

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.

Quoted 1 line

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 "

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?

Quoted 10 lines
Quoted 8 lines

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

Quoted 2 lines

You didn't mention which branch this is with btw.

master aeaa356a5ee77b4596c479451a9db289381a4d16

Thanks again

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#3 lore raw
Quoted 17 lines · Gary Thomas
Quoted 16 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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 "

I'm really not sure if this is the right fix for the problem.. (Actually I'm guessing you found an issue, both documentation and functional that it's difficult to enable this by itself.)

I believe if you add "task-poky-rpm" to the packages to be installed that will do it.. the problem I'm seeing is I'm not sure how or where you would add that.

The task-poky-rpm is constructed from the task-poky-basic... (I've been building poky-image-basic recently because it's a step up from "minimal", but yet it doesn't have the full size of the system like sato.)

Quoted 1 line

BTW, where is this documented? Not in the Poky handbook from what I can tell.

We really need to start to document these combinations, magic values, etc...

Quoted 1 line

Also, is there documentation on how to use zypper, how to set up repositories, etc?

There is no documentation yet on how to use Zypper. Below is how I've been using it to test things:

On the host:

1) Build the environment -- full set of rpm packages you want available

2) Build "createrepo-native"

3) Copy tmp/deploy/rpm and contents of somewhere it can be accessed via HTTP, such as /var/www/html.

4) Create the repository database:

<poky directory>/scripts/poky-setup-rpmrepo /var/www/html/rpm

On the target:

(assuming qemu)

1) zypper addrepo http://192.167.7.1/rpm main

2) zypper refresh

3) zypper install <package>

Some other useful commands:

zypper info <package>

This will give you basic info on a package, and tell you if it's already installed (@System repository) or which remote repository it's stored in.

zypper remove <package>

This will remove a package, and clean up any other packages that are dependent upon it.

Note, there are a couple of flaws in the current zypper implementation in regards to Poky.

The first is that there is a problem on ARM targets. For some reason it can't process packages for ARM targets properly. We're still investigating.

The second is Zypper does not understand RPM dependency hinting at this point. There is a concept in RPM5 called weak and strong dependencies. A strong dependency says that this thing MUST be installed, or its a failure. A weak dependency is this thing can be installed, but if it's not we don't fail. Zypper treats all dependencies equally at this point and assumes they are strong.

--Mark

Quoted 20 lines
Quoted 10 lines
Quoted 8 lines

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

Quoted 2 lines

You didn't mention which branch this is with btw.

master aeaa356a5ee77b4596c479451a9db289381a4d16

Thanks again

#4 lore raw
Quoted 86 lines · Mark Hatle
Quoted 17 lines · Gary Thomas
Quoted 16 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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 "

I'm really not sure if this is the right fix for the problem.. (Actually I'm guessing you found an issue, both documentation and functional that it's difficult to enable this by itself.)

I believe if you add "task-poky-rpm" to the packages to be installed that will do it.. the problem I'm seeing is I'm not sure how or where you would add that.

The task-poky-rpm is constructed from the task-poky-basic... (I've been building poky-image-basic recently because it's a step up from "minimal", but yet it doesn't have the full size of the system like sato.)

Quoted 1 line

BTW, where is this documented? Not in the Poky handbook from what I can tell.

We really need to start to document these combinations, magic values, etc...

Quoted 1 line

Also, is there documentation on how to use zypper, how to set up repositories, etc?

There is no documentation yet on how to use Zypper. Below is how I've been using it to test things:

On the host:

1) Build the environment -- full set of rpm packages you want available

2) Build "createrepo-native"

3) Copy tmp/deploy/rpm and contents of somewhere it can be accessed via HTTP, such as /var/www/html.

4) Create the repository database:

<poky directory>/scripts/poky-setup-rpmrepo /var/www/html/rpm

On the target:

(assuming qemu)

1) zypper addrepo http://192.167.7.1/rpm main

2) zypper refresh

3) zypper install<package>

Some other useful commands:

zypper info<package>

This will give you basic info on a package, and tell you if it's already installed (@System repository) or which remote repository it's stored in.

zypper remove<package>

This will remove a package, and clean up any other packages that are dependent upon it.

Note, there are a couple of flaws in the current zypper implementation in regards to Poky.

Quoted 8 lines

The first is that there is a problem on ARM targets. For some reason it can't process packages for ARM targets properly. We're still investigating.

The second is Zypper does not understand RPM dependency hinting at this point. There is a concept in RPM5 called weak and strong dependencies. A strong dependency says that this thing MUST be installed, or its a failure. A weak dependency is this thing can be installed, but if it's not we don't fail. Zypper treats all dependencies equally at this point and assumes they are strong.

Thanks, this should get me started (I certainly would have had a hard time guessing all these details!)

Perhaps I should file a bug (or 2) about the missing/incomplete documentation?

Quoted 25 lines
Quoted 11 lines
Quoted 10 lines
Quoted 8 lines

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...

Quoted 9 lines

It complains it can't find /dev/fb0. See the boot log at http://www.mlbassoc.com/poky/boot_2011-03-21.log

Quoted 2 lines

You didn't mention which branch this is with btw.

master aeaa356a5ee77b4596c479451a9db289381a4d16

Thanks again

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#5 lore raw
In reply to Mark Hatle
Quoted 37 lines · On Monday 21 March 2011 17:00:44 Mark Hatle wrote:
Quoted 2 lines · Gary Thomas

Also, is there documentation on how to use zypper, how to set up repositories, etc?

There is no documentation yet on how to use Zypper. Below is how I've been using it to test things:

On the host:

1) Build the environment -- full set of rpm packages you want available

2) Build "createrepo-native"

3) Copy tmp/deploy/rpm and contents of somewhere it can be accessed via HTTP, such as /var/www/html.

4) Create the repository database:

<poky directory>/scripts/poky-setup-rpmrepo /var/www/html/rpm

On the target:

(assuming qemu)

1) zypper addrepo http://192.167.7.1/rpm main

2) zypper refresh

3) zypper install <package>

Some other useful commands:

zypper info <package>

Quoted 8 lines

This will give you basic info on a package, and tell you if it's already installed (@System repository) or which remote repository it's stored in.

zypper remove <package>

This will remove a package, and clean up any other packages that are dependent upon it.

Mark, you beat me to it :) I just finished copying this onto the wiki:

https://wiki.yoctoproject.org/wiki/Zypper_Repository_Setup

We could probably do with this in the documentation in reworked form. Scott R, what do you think?

Cheers,
Paul

#6 lore raw
In reply to Gary Thomas
Quoted 17 lines · Gary Thomas
Quoted 16 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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.

Quoted 3 lines

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!

Quoted 11 lines
Quoted 9 lines
Quoted 7 lines

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...

Cheers,

Richard

#7 lore raw
Quoted 25 lines · Richard Purdie
Quoted 17 lines · Gary Thomas
Quoted 16 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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 "
Quoted 7 lines

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.

Quoted 7 lines
Quoted 4 lines

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.

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#10 lore raw
In reply to Richard Purdie
Quoted 49 lines · Richard Purdie
Quoted 17 lines · Gary Thomas
Quoted 16 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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.

Quoted 3 lines

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!

Quoted 8 lines
Quoted 8 lines
Quoted 7 lines

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

http://git.pokylinux.org/cgit.cgi/meta-intel/

Thanks,

Darren

Quoted 10 lines

Cheers,

Richard

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#11 lore raw
Quoted 54 lines · Darren Hart
Quoted 51 lines · Richard Purdie
Quoted 17 lines · Gary Thomas
Quoted 16 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

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.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

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.

Quoted 3 lines

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!

Quoted 10 lines
Quoted 9 lines
Quoted 7 lines

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...

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#12 lore raw
Quoted 70 lines · Gary Thomas
Quoted 69 lines · Darren Hart
Quoted 65 lines · Richard Purdie
Quoted 21 lines · Gary Thomas
Quoted 20 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 5 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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.

Quoted 5 lines

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!

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

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

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

(*) 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...

Quoted 7 lines
Quoted 3 lines

And if you need emenlow, that bsp is now part of the meta-intel layer:

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#13 lore raw
Quoted 75 lines · Darren Hart
Quoted 72 lines · Gary Thomas
Quoted 71 lines · Darren Hart
Quoted 58 lines · Richard Purdie
Quoted 21 lines · Gary Thomas
Quoted 20 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 5 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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.

Quoted 5 lines

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!

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

Quoted 7 lines
Quoted 5 lines
Quoted 1 line

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'
| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359 for further information)

This from yesterday's master (aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there an easy fix?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#14 lore raw
Quoted 100 lines · Gary Thomas
Quoted 76 lines · Darren Hart
Quoted 73 lines · Gary Thomas
Quoted 72 lines · Darren Hart
Quoted 59 lines · Richard Purdie
Quoted 22 lines · Gary Thomas
Quoted 21 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 5 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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.

Quoted 5 lines

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!

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359 for further information)

Quoted 4 lines

This from yesterday's master (aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1

Author: Bruce Ashfield <[email protected]>
Date:   Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Cheers,

Bruce

Quoted 1 line
#8 lore raw
In reply to Gary Thomas
Quoted 71 lines · Gary Thomas
Quoted 30 lines · Richard Purdie
Quoted 21 lines · Gary Thomas
Quoted 20 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 5 lines

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.

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

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 "

Quoted 7 lines

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.

Quoted 9 lines
Quoted 6 lines

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.

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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...

Quoted 6 lines

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.

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#9 lore raw
Quoted 81 lines · Darren Hart
Quoted 71 lines · Gary Thomas
Quoted 30 lines · Richard Purdie
Quoted 21 lines · Gary Thomas
Quoted 20 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 5 lines

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.

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

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 "

Quoted 7 lines

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.

Quoted 9 lines
Quoted 6 lines

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.

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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...

Quoted 6 lines

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?

Quoted 2 lines

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)

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#15 lore raw
In reply to Bruce Ashfield
Quoted 131 lines · Bruce Ashfield
Quoted 100 lines · Gary Thomas
Quoted 76 lines · Darren Hart
Quoted 73 lines · Gary Thomas
Quoted 72 lines · Darren Hart
Quoted 59 lines · Richard Purdie
Quoted 22 lines · Gary Thomas
Quoted 21 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 5 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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.

Quoted 5 lines

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!

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359 for further information)

Quoted 4 lines

This from yesterday's master (aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1

Author: Bruce Ashfield <[email protected]>
Date:   Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Quoted 9 lines

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Hmm, strange - the SRCREV does look like it needed to be updated but yet I nor the autobuilder have been seeing this.

Anyway, I just updated the kernel SRCREVs in master, please try again...

Thanks,

Tom

Quoted 11 lines

Cheers,

Bruce

Quoted 1 line

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#16 lore raw
Quoted 142 lines · Tom Zanussi
Quoted 131 lines · Bruce Ashfield
Quoted 100 lines · Gary Thomas
Quoted 76 lines · Darren Hart
Quoted 73 lines · Gary Thomas
Quoted 72 lines · Darren Hart
Quoted 59 lines · Richard Purdie
Quoted 22 lines · Gary Thomas
Quoted 21 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 5 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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.

Quoted 5 lines

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!

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359 for further information)

Quoted 4 lines

This from yesterday's master (aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1

Author: Bruce Ashfield<[email protected]>
Date:   Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Quoted 9 lines

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Quoted 4 lines

Hmm, strange - the SRCREV does look like it needed to be updated but yet I nor the autobuilder have been seeing this.

Anyway, I just updated the kernel SRCREVs in master, please try again...

It work now, thanks. It also found my display and SATA devices. Sadly, when it's running X, I can't use the mouse. It seems to be found, but doesn't work.

I get these messages during boot:
usb 1-1.2: USB disconnect, address 6
usb 1-1.2: new low speed USB device using ehci_hcd and address 7
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.2/1-1.2:1.0/input/input4 generic-usb 0003:046D:C03D.0005: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-1.2/input0
And there is a device created:

  root@emenlow:~# ls -l /dev/input/
  drwxr-xr-x    2 root     root            60 Mar 21 22:27 by-id
  drwxr-xr-x    2 root     root            60 Mar 21 22:27 by-path
  crw-r-----    1 root     root       13,  63 Mar 21 06:31 mice
  crw-r-----    1 root     root       13,  32 Mar 21 22:27 mouse0

Ideas?

Now, if I can just figure out how to make the [live] image larger... (free space) I can get on with the real testing I need to do.

Thanks for the help

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#17 lore raw
Quoted 170 lines · Gary Thomas
Quoted 152 lines · Tom Zanussi
Quoted 141 lines · Bruce Ashfield
Quoted 108 lines · Gary Thomas
Quoted 84 lines · Darren Hart
Quoted 81 lines · Gary Thomas
Quoted 80 lines · Darren Hart
Quoted 65 lines · Richard Purdie
Quoted 25 lines · Gary Thomas
Quoted 24 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 6 lines

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.

Quoted 1 line

How do I do that with the RPM based images?

Quoted 7 lines
Quoted 2 lines

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.

Quoted 6 lines

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!

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359

Quoted 6 lines

for further information)

This from yesterday's master (aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1
Author: Bruce Ashfield<[email protected]>
Date: Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Quoted 9 lines

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Quoted 4 lines

Hmm, strange - the SRCREV does look like it needed to be updated but yet I nor the autobuilder have been seeing this.

Anyway, I just updated the kernel SRCREVs in master, please try again...

It work now, thanks. It also found my display and SATA devices. Sadly, when it's running X, I can't use the mouse. It seems to be found, but doesn't work.

I get these messages during boot:
usb 1-1.2: USB disconnect, address 6
usb 1-1.2: new low speed USB device using ehci_hcd and address 7
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.2/1-1.2:1.0/input/input4 generic-usb 0003:046D:C03D.0005: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-1.2/input0
And there is a device created:

Quoted 7 lines
root@emenlow:~# ls -l /dev/input/
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-id
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-path
crw-r----- 1 root root 13, 63 Mar 21 06:31 mice
crw-r----- 1 root root 13, 32 Mar 21 22:27 mouse0

Ideas?

By "doesn't work" do you mean that you don't see the cursor? Or do you see the cursor, but it doesn't move? Or it moves but clicking has no effect?

If "I don't see a cursor" try looking at the formfactor file and check the value of "HAVE_TOUCHSCREEN":

# grep -r TOUCHSCREEN /etc/formfactor/
/etc/formfactor/config:if [ -z "$HAVE_TOUCHSCREEN" ]; then
/etc/formfactor/config:    HAVE_TOUCHSCREEN=0
/etc/formfactor/machconfig:HAVE_TOUCHSCREEN=0

You want that to be 0, if it's 1, then matchbox will hide the mouse. See /etc/matchbox/session

Quoted 6 lines

Now, if I can just figure out how to make the [live] image larger... (free space)
I can get on with the real testing I need to do.
Thanks for the help

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#18 lore raw
Quoted 185 lines · Darren Hart
Quoted 171 lines · Gary Thomas
Quoted 153 lines · Tom Zanussi
Quoted 142 lines · Bruce Ashfield
Quoted 109 lines · Gary Thomas
Quoted 84 lines · Darren Hart
Quoted 81 lines · Gary Thomas
Quoted 80 lines · Darren Hart
Quoted 65 lines · Richard Purdie
Quoted 25 lines · Gary Thomas
Quoted 24 lines · Richard Purdie
Quoted 8 lines · Gary Thomas

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 (*)

Quoted 6 lines

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.

Quoted 1 line

How do I do that with the RPM based images?

Quoted 7 lines
Quoted 2 lines

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.

Quoted 6 lines

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!

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359

Quoted 6 lines

for further information)

This from yesterday's master (aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1
Author: Bruce Ashfield<[email protected]>
Date: Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Quoted 9 lines

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Quoted 4 lines

Hmm, strange - the SRCREV does look like it needed to be updated but yet I nor the autobuilder have been seeing this.

Anyway, I just updated the kernel SRCREVs in master, please try again...

It work now, thanks. It also found my display and SATA devices. Sadly, when it's running X, I can't use the mouse. It seems to be found, but doesn't work.

I get these messages during boot:
usb 1-1.2: USB disconnect, address 6
usb 1-1.2: new low speed USB device using ehci_hcd and address 7
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.2/1-1.2:1.0/input/input4 generic-usb 0003:046D:C03D.0005: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-1.2/input0
And there is a device created:

Quoted 7 lines
root@emenlow:~# ls -l /dev/input/
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-id
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-path
crw-r----- 1 root root 13, 63 Mar 21 06:31 mice
crw-r----- 1 root root 13, 32 Mar 21 22:27 mouse0

Ideas?

By "doesn't work" do you mean that you don't see the cursor? Or do you see the cursor, but it doesn't move? Or it moves but clicking has no effect?

Quoted 8 lines

If "I don't see a cursor" try looking at the formfactor file and check the value of "HAVE_TOUCHSCREEN":

# grep -r TOUCHSCREEN /etc/formfactor/
/etc/formfactor/config:if [ -z "$HAVE_TOUCHSCREEN" ]; then
/etc/formfactor/config: HAVE_TOUCHSCREEN=0
/etc/formfactor/machconfig:HAVE_TOUCHSCREEN=0

You want that to be 0, if it's 1, then matchbox will hide the mouse. See /etc/matchbox/session

I had already checked that file - it's correct & I do see a cursor, it just doesn't move.

Quoted 7 lines
Quoted 6 lines

Now, if I can just figure out how to make the [live] image larger... (free space)
I can get on with the real testing I need to do.
Thanks for the help

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#19 lore raw
Quoted 212 lines · Gary Thomas
Quoted 211 lines · Darren Hart
Quoted 187 lines · Gary Thomas
Quoted 166 lines · Tom Zanussi
Quoted 155 lines · Bruce Ashfield
Quoted 120 lines · Gary Thomas
Quoted 93 lines · Darren Hart
Quoted 90 lines · Gary Thomas
Quoted 88 lines · Darren Hart
Quoted 74 lines · Richard Purdie
Quoted 30 lines · Gary Thomas
Quoted 29 lines · Richard Purdie
Quoted 18 lines · Gary Thomas

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.

Quoted 1 line

How do I do that with the RPM based images?

Quoted 8 lines
Quoted 3 lines

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.

Quoted 6 lines

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!

Quoted 12 lines
Quoted 11 lines
Quoted 8 lines

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...

Quoted 6 lines
Quoted 2 lines

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

http://git.pokylinux.org/cgit.cgi/meta-intel/

Quoted 8 lines
Quoted 4 lines

Do you have instructions/suggestions on how to add this to my extant
Poky tree?

It's just another layer, so you checkout it out somewhere and add the
meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359

Quoted 8 lines

for further information)

This from yesterday's master
(aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there
an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1
Author: Bruce Ashfield<[email protected]>
Date: Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Quoted 9 lines

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Quoted 6 lines

Hmm, strange - the SRCREV does look like it needed to be updated but yet
I nor the autobuilder have been seeing this.

Anyway, I just updated the kernel SRCREVs in master, please try again...

It work now, thanks. It also found my display and SATA devices. Sadly, when
it's running X, I can't use the mouse. It seems to be found, but doesn't work.

I get these messages during boot:
usb 1-1.2: USB disconnect, address 6
usb 1-1.2: new low speed USB device using ehci_hcd and address 7
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.2/1-1.2:1.0/input/input4 generic-usb 0003:046D:C03D.0005: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-1.2/input0
And there is a device created:

Quoted 7 lines
root@emenlow:~# ls -l /dev/input/
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-id
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-path
crw-r----- 1 root root 13, 63 Mar 21 06:31 mice
crw-r----- 1 root root 13, 32 Mar 21 22:27 mouse0

Ideas?

By "doesn't work" do you mean that you don't see the cursor? Or do you see the cursor, but it doesn't move? Or it moves but clicking has no effect?

If "I don't see a cursor" try looking at the formfactor file and check the value of "HAVE_TOUCHSCREEN":

# grep -r TOUCHSCREEN /etc/formfactor/
/etc/formfactor/config:if [ -z "$HAVE_TOUCHSCREEN" ]; then
/etc/formfactor/config: HAVE_TOUCHSCREEN=0
/etc/formfactor/machconfig:HAVE_TOUCHSCREEN=0
Quoted 5 lines
Quoted 2 lines

You want that to be 0, if it's 1, then matchbox will hide the mouse. See /etc/matchbox/session

I had already checked that file - it's correct & I do see a cursor, it just doesn't move.

The other thing to check is the xorg.conf and see if adding/removing the following makes a difference:

Option "AutoAddDevices" "False"

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#21 lore raw
In reply to Gary Thomas
Quoted 188 lines · Gary Thomas
Quoted 187 lines · Darren Hart
Quoted 171 lines · Gary Thomas
Quoted 153 lines · Tom Zanussi
Quoted 142 lines · Bruce Ashfield
Quoted 109 lines · Gary Thomas
Quoted 84 lines · Darren Hart
Quoted 81 lines · Gary Thomas
Quoted 80 lines · Darren Hart
Quoted 65 lines · Richard Purdie
Quoted 25 lines · Gary Thomas
Quoted 24 lines · Richard Purdie
Quoted 14 lines · Gary Thomas

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.

Quoted 1 line

How do I do that with the RPM based images?

Quoted 7 lines
Quoted 2 lines

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.

Quoted 6 lines

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!

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

http://git.pokylinux.org/cgit.cgi/meta-intel/

Do you have instructions/suggestions on how to add this to my extant Poky tree?

It's just another layer, so you checkout it out somewhere and add the meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359

Quoted 6 lines

for further information)

This from yesterday's master (aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1
Author: Bruce Ashfield<[email protected]>
Date: Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Quoted 9 lines

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Quoted 4 lines

Hmm, strange - the SRCREV does look like it needed to be updated but yet I nor the autobuilder have been seeing this.

Anyway, I just updated the kernel SRCREVs in master, please try again...

It work now, thanks. It also found my display and SATA devices. Sadly, when it's running X, I can't use the mouse. It seems to be found, but doesn't work.

I get these messages during boot:
usb 1-1.2: USB disconnect, address 6
usb 1-1.2: new low speed USB device using ehci_hcd and address 7
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.2/1-1.2:1.0/input/input4 generic-usb 0003:046D:C03D.0005: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-1.2/input0
And there is a device created:

Quoted 7 lines
root@emenlow:~# ls -l /dev/input/
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-id
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-path
crw-r----- 1 root root 13, 63 Mar 21 06:31 mice
crw-r----- 1 root root 13, 32 Mar 21 22:27 mouse0

Ideas?

By "doesn't work" do you mean that you don't see the cursor? Or do you see the cursor, but it doesn't move? Or it moves but clicking has no effect?

If "I don't see a cursor" try looking at the formfactor file and check the value of "HAVE_TOUCHSCREEN":

Quoted 9 lines
Quoted 6 lines
# grep -r TOUCHSCREEN /etc/formfactor/
/etc/formfactor/config:if [ -z "$HAVE_TOUCHSCREEN" ]; then
/etc/formfactor/config: HAVE_TOUCHSCREEN=0
/etc/formfactor/machconfig:HAVE_TOUCHSCREEN=0

You want that to be 0, if it's 1, then matchbox will hide the mouse. See /etc/matchbox/session

I had already checked that file - it's correct & I do see a cursor, it just doesn't move.

The mouse on my emenlow system, a WEBS-2120 box, works ok with a fresh build from master. Here's my dmesg output:

usb 2-1: new low speed USB device using uhci_hcd and address 2
input: USB Optical Mouse
as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input2 generic-usb 0003:0461:4D65.0001: input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.0-1/input0

The difference seems to be uhci_hcd vs ehci_hcd in your case...

Tom

Quoted 13 lines
Quoted 7 lines
Quoted 6 lines

Now, if I can just figure out how to make the [live] image larger... (free space)
I can get on with the real testing I need to do.
Thanks for the help

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#20 lore raw
In reply to Darren Hart
Quoted 220 lines · Darren Hart
Quoted 217 lines · Gary Thomas
Quoted 215 lines · Darren Hart
Quoted 189 lines · Gary Thomas
Quoted 168 lines · Tom Zanussi
Quoted 157 lines · Bruce Ashfield
Quoted 122 lines · Gary Thomas
Quoted 93 lines · Darren Hart
Quoted 90 lines · Gary Thomas
Quoted 88 lines · Darren Hart
Quoted 74 lines · Richard Purdie
Quoted 30 lines · Gary Thomas
Quoted 29 lines · Richard Purdie

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?

Quoted 8 lines
Quoted 3 lines

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.

Quoted 6 lines

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!

Quoted 12 lines
Quoted 11 lines

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...

Quoted 6 lines
Quoted 2 lines

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...

And if you need emenlow, that bsp is now part of the meta-intel layer:

http://git.pokylinux.org/cgit.cgi/meta-intel/

Quoted 8 lines
Quoted 4 lines

Do you have instructions/suggestions on how to add this to my extant
Poky tree?

It's just another layer, so you checkout it out somewhere and add the
meta-intel/meta-$MACHINE directory to your conf/bblayer.conf file.

I did that, changed MACHINE=emenlow, but I got this error:

| cc1: warnings being treated as errors
| cc1: error: include location "/usr/local/include" is unsafe for
cross-compilation
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
| make: Leaving directory `/home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/linux/tools/perf'

| FATAL: oe_runmake failed
| ERROR: Function 'do_compile_perf' failed (see /home/local/pc_test/tmp/work/emenlow-poky-linux/linux-yocto-2.6.37+git2+29047c254624e0bd8a0ac6da92862f7c6357cb0b_1+c6299ae5bece8e3a6e1bc2c236862ae004629aae-r16/temp/log.do_compile_perf.10359

Quoted 8 lines

for further information)

This from yesterday's master
(aeaa356a5ee77b4596c479451a9db289381a4d16)

I recall seeing similar errors recently, but not the solution. Is there
an easy fix?

It means that the SRCREV for the branch doesn't have the following commit covered:

----------

commit 2b412826bbeb4a16abe2ea74f2456ab880c6e3c1
Author: Bruce Ashfield<[email protected]>
Date: Fri Feb 25 13:18:51 2011 -0500

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Quoted 9 lines

----------

The kernel repo has this, and I thought that the meta-intel emenlow had an updated SRCREV .. but your build error indicates otherwise.

Quoted 6 lines

Hmm, strange - the SRCREV does look like it needed to be updated but yet
I nor the autobuilder have been seeing this.

Anyway, I just updated the kernel SRCREVs in master, please try again...

It work now, thanks. It also found my display and SATA devices. Sadly, when
it's running X, I can't use the mouse. It seems to be found, but doesn't work.

I get these messages during boot:
usb 1-1.2: USB disconnect, address 6
usb 1-1.2: new low speed USB device using ehci_hcd and address 7
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.2/1-1.2:1.0/input/input4 generic-usb 0003:046D:C03D.0005: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-1.2/input0
And there is a device created:

Quoted 7 lines
root@emenlow:~# ls -l /dev/input/
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-id
drwxr-xr-x 2 root root 60 Mar 21 22:27 by-path
crw-r----- 1 root root 13, 63 Mar 21 06:31 mice
crw-r----- 1 root root 13, 32 Mar 21 22:27 mouse0

Ideas?

By "doesn't work" do you mean that you don't see the cursor? Or do you see the cursor, but it doesn't move? Or it moves but clicking has no effect?

If "I don't see a cursor" try looking at the formfactor file and check the value of "HAVE_TOUCHSCREEN":

# grep -r TOUCHSCREEN /etc/formfactor/
/etc/formfactor/config:if [ -z "$HAVE_TOUCHSCREEN" ]; then
/etc/formfactor/config: HAVE_TOUCHSCREEN=0
/etc/formfactor/machconfig:HAVE_TOUCHSCREEN=0

You want that to be 0, if it's 1, then matchbox will hide the mouse. See /etc/matchbox/session

Quoted 6 lines
Quoted 2 lines

I had already checked that file - it's correct & I do see a cursor, it just doesn't move.

The other thing to check is the xorg.conf and see if adding/removing the following makes a difference:

Option "AutoAddDevices" "False"

Looking at the output when starting X, I think there is another problem:

(==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 22 10:42:18 2011 (==) Using config file: "/etc/X11/xorg.conf"
(EE) module ABI major version (11) doesn't match the server's version (8) (EE) Failed to load module "mouse" (module requirement mismatch, 0) (EE) module ABI major version (11) doesn't match the server's version (8) (EE) Failed to load module "kbd" (module requirement mismatch, 0)

In particular, neither the keyboard nor mouse X drivers could be loaded.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#22 lore raw
In reply to Gary Thomas
Quoted 3 lines · Gary Thomas

Now, if I can just figure out how to make the [live] image larger... (free space)
I can get on with the real testing I need to do.

Have you fiddled with IMAGE_OVERHEAD_FACTOR ? If I read meta/classes/image.bbclass right setting that to 2 might give you enough free space. And time to reconcile openembedded.master and oe-core on some image creation bits...

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#23 lore raw
Quoted 8 lines · Tom Rini
Quoted 3 lines · Gary Thomas

Now, if I can just figure out how to make the [live] image larger... (free space)
I can get on with the real testing I need to do.

Have you fiddled with IMAGE_OVERHEAD_FACTOR ? If I read meta/classes/image.bbclass right setting that to 2 might give you enough free space. And time to reconcile openembedded.master and oe-core on some image creation bits...

Similar to other configs, I was setting IMAGE_ROOTFS_SIZE_ext3, but this seems ineffective. Setting IMAGE_ROOTFS_SIZE directly does seem to work properly.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------