* Trying to add Compulab CM-X300 machine configuration files, don't work as expected.
@ 2009-04-08 8:32 s hakkesteegt
2009-04-12 22:46 ` GNUtoo
0 siblings, 1 reply; 3+ messages in thread
From: s hakkesteegt @ 2009-04-08 8:32 UTC (permalink / raw)
To: Openembedded-devel
I'm currently trying to add the machine configuration files for the Compulab
CM-X300 and I'm experiencing some problems.
What I currently have can be found here: http://www.xAs Kernel I'm using
2.6.26, with patch provided bij Compulab, there they provide a working
example from this kernel with a rootfs, it seemed to me to be a good
starting point for
me.s4all.nl/~hakkest1/oe/cm-x300.conf<http://www.xs4all.nl/%7Ehakkest1/oe/cm-x300.conf>
problem 1)
When I create an Angstrom-console image (using oe dev branch), in a fresh
tmp directory, it creates a rootfs, only containing the following
directories: *bin, dev, etc, lib, sbin, usr. *
So it seems there is missing quite a lot, and the .jffs2 image is only 2.2
MB. Can this be because of a mistake in my machine .conf file or might it be
something different?
problem 2)
But when I first run *bitbake console-image* for the CM-X270 and then for
the CM-X300 then the rootfs seems to be normal, but I don't know if it is,
because I experience quite some problems using it. When I flash the machine
with the created kernel and rootfs, It gives me most of the time
segmentation faults and kernel oops, as you can see in the next file:
http://www.xs4all.nl/~hakkest1/oe/boot_1st_time_cm-x300.txt<http://www.xs4all.nl/%7Ehakkest1/oe/boot_1st_time_cm-x300.txt>
I don't think it is a hardware based problem, because the example kernel and
rootfs from Compulab work fine on the machine, without these errors.
As Kernel I'm using 2.6.26, with patch provided bij Compulab, there they
provide a working example from this kernel with a rootfs, it seemed to me to
be a good starting point for me.
When I use the example kernel provided by Compulab, with my, with OE
created, rootfs, it gives me the segmentation faults and kernel oops aswell
(and some errors about not found modules, wich seems logical there the
modules dir is in a different location in the example rootfs). So I suspect
there is something wrong with my own created rootfs / jffs2 images, but I
have no Idea what it can be.
Thanks in advance,
Siebren Hakkesteegt
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Trying to add Compulab CM-X300 machine configuration files, don't work as expected.
2009-04-08 8:32 Trying to add Compulab CM-X300 machine configuration files, don't work as expected s hakkesteegt
@ 2009-04-12 22:46 ` GNUtoo
2009-04-13 7:02 ` Koen Kooi
0 siblings, 1 reply; 3+ messages in thread
From: GNUtoo @ 2009-04-12 22:46 UTC (permalink / raw)
To: openembedded-devel
On Wed, 2009-04-08 at 10:32 +0200, s hakkesteegt wrote:
> I'm currently trying to add the machine configuration files for the Compulab
> CM-X300 and I'm experiencing some problems.
> What I currently have can be found here: http://www.xAs Kernel I'm using
> 2.6.26, with patch provided bij Compulab, there they provide a working
> example from this kernel with a rootfs, it seemed to me to be a good
> starting point for
> me.s4all.nl/~hakkest1/oe/cm-x300.conf<http://www.xs4all.nl/%7Ehakkest1/oe/cm-x300.conf>
>
>
> problem 1)
> When I create an Angstrom-console image (using oe dev branch), in a fresh
> tmp directory, it creates a rootfs, only containing the following
> directories: *bin, dev, etc, lib, sbin, usr. *
> So it seems there is missing quite a lot, and the .jffs2 image is only 2.2
> MB. Can this be because of a mistake in my machine .conf file or might it be
> something different?
Maybe try angstrom directly(not console-image but full angstrom)
>
> problem 2)
> But when I first run *bitbake console-image* for the CM-X270 and then for
> the CM-X300 then the rootfs seems to be normal, but I don't know if it is,
> because I experience quite some problems using it. When I flash the machine
> with the created kernel and rootfs, It gives me most of the time
> segmentation faults and kernel oops, as you can see in the next file:
> http://www.xs4all.nl/~hakkest1/oe/boot_1st_time_cm-x300.txt<http://www.xs4all.nl/%7Ehakkest1/oe/boot_1st_time_cm-x300.txt>
>
> I don't think it is a hardware based problem, because the example kernel and
> rootfs from Compulab work fine on the machine, without these errors.
>
> As Kernel I'm using 2.6.26, with patch provided bij Compulab, there they
> provide a working example from this kernel with a rootfs, it seemed to me to
> be a good starting point for me.
>
> When I use the example kernel provided by Compulab, with my, with OE
> created, rootfs, it gives me the segmentation faults and kernel oops aswell
> (and some errors about not found modules, wich seems logical there the
> modules dir is in a different location in the example rootfs). So I suspect
> there is something wrong with my own created rootfs / jffs2 images, but I
> have no Idea what it can be.
Could it be that you have a kenrel from Compulab and incompatibles
kernel modules from openembedded in your filesystem?
Denis.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Trying to add Compulab CM-X300 machine configuration files, don't work as expected.
2009-04-12 22:46 ` GNUtoo
@ 2009-04-13 7:02 ` Koen Kooi
0 siblings, 0 replies; 3+ messages in thread
From: Koen Kooi @ 2009-04-13 7:02 UTC (permalink / raw)
To: openembedded-devel
On 13-04-09 00:46, GNUtoo wrote:
> Maybe try angstrom directly(not console-image but full angstrom)
Say what? That doesn't make sense at all.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-04-13 7:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-08 8:32 Trying to add Compulab CM-X300 machine configuration files, don't work as expected s hakkesteegt
2009-04-12 22:46 ` GNUtoo
2009-04-13 7:02 ` Koen Kooi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox