Is it just me? Can't get 'Atom-PC' to boot.

Is it just me? Can't get 'Atom-PC' to boot.

[Chris Tapp]

I've built the 'atom-pc' kernel as follows:

1) git clone git://git.yoctoproject.org/poky.git
2) git checkout denzil
3) source poky/oe-init-build-env work-area
4) Edit local.conf so that threads/parallel make are both 16 and MACHINE is 'atom-pc'
8) bitbake virtual/kernel.

However, the kernel that gets produced fails to boot. All I get is a screen full of random characters and nothing comes out of the serial port (configured for kernel messages). I don't get any 'Loading...' or 'Uncompressing...' messages either. Using a kernel image from else where (e.g. Voyage Linux) works as expected.

What do I need to do differently to get the above to build a bootable image? I'm assuming that 'atom-pc' works for others?

Chris Tapp

opensource@keylevel.com
www.keylevel.com

Re: Is it just me? Can't get 'Atom-PC' to boot.

[Jim Abernathy]

On 07/16/2012 04:25 PM, Chris Tapp wrote:
> I've built the 'atom-pc' kernel as follows:
>
> 1) git clone git://git.yoctoproject.org/poky.git
> 2) git checkout denzil
> 3) source poky/oe-init-build-env work-area
> 4) Edit local.conf so that threads/parallel make are both 16 and MACHINE is 'atom-pc'
> 8) bitbake virtual/kernel.
>
> However, the kernel that gets produced fails to boot. All I get is a screen full of random characters and nothing comes out of the serial port (configured for kernel messages). I don't get any 'Loading...' or 'Uncompressing...' messages either. Using a kernel image from else where (e.g. Voyage Linux) works as expected.
>
> What do I need to do differently to get the above to build a bootable image? I'm assuming that 'atom-pc' works for others?
When I build for Atom PCs, I'm usually targeting a specific BSP like 
CrownBay, n450, Cedartrail. All of those require the meta-intel layer. 
So you need to edit the local.conf with a machine like n450, crownbay, 
cedartrail, etc. and you need to edit bblayer.conf to add the meta-intel 
layer and the meta-intel/meta/crownbay, etc.

I always bitbake core-image minimal or core-image-sato.

Jim A

> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Is it just me? Can't get 'Atom-PC' to boot.

[Ross Burton]

On Monday, 16 July 2012 at 21:25, Chris Tapp wrote:
> I've built the 'atom-pc' kernel as follows:
> 
> 1) git clone git://git.yoctoproject.org/poky.git (http://git.yoctoproject.org/poky.git)
> 2) git checkout denzil
> 3) source poky/oe-init-build-env work-area
> 4) Edit local.conf so that threads/parallel make are both 16 and MACHINE is 'atom-pc'
> 8) bitbake virtual/kernel.
> 
> However, the kernel that gets produced fails to boot. All I get is a screen full of random characters and nothing comes out of the serial port (configured for kernel messages). I don't get any 'Loading...' or 'Uncompressing...' messages either. Using a kernel image from else where (e.g. Voyage Linux) works as expected.
> 
> What do I need to do differently to get the above to build a bootable image? I'm assuming that 'atom-pc' works for others?
How are you actually booting the kernel?  I frequently boot the generated hddimg when written to a USB stick on my Zotac box, but it's well known that PC hardware is a nightmare to boot reliably... 

Ross

Re: Is it just me? Can't get 'Atom-PC' to boot.

[Chris Tapp]

On 16 Jul 2012, at 22:02, Ross Burton wrote:

> On Monday, 16 July 2012 at 21:25, Chris Tapp wrote:
>> I've built the 'atom-pc' kernel as follows:
>> 
>> 1) git clone git://git.yoctoproject.org/poky.git (http://git.yoctoproject.org/poky.git)
>> 2) git checkout denzil
>> 3) source poky/oe-init-build-env work-area
>> 4) Edit local.conf so that threads/parallel make are both 16 and MACHINE is 'atom-pc'
>> 8) bitbake virtual/kernel.
>> 
>> However, the kernel that gets produced fails to boot. All I get is a screen full of random characters and nothing comes out of the serial port (configured for kernel messages). I don't get any 'Loading...' or 'Uncompressing...' messages either. Using a kernel image from else where (e.g. Voyage Linux) works as expected.
>> 
>> What do I need to do differently to get the above to build a bootable image? I'm assuming that 'atom-pc' works for others?
> How are you actually booting the kernel?  I frequently boot the generated hddimg when written to a USB stick on my Zotac box, but it's well known that PC hardware is a nightmare to boot reliably... 


I've got a USB stick with Extlinux on it. The profile I use is always the same - I just change the 'KERNEL' stanza to point to a different kernel image.

opensource@keylevel.com
www.keylevel.com

Re: Is it just me? Can't get 'Atom-PC' to boot.

[Chris Tapp]

On 16 Jul 2012, at 21:40, Jim Abernathy wrote:

> On 07/16/2012 04:25 PM, Chris Tapp wrote:
>> I've built the 'atom-pc' kernel as follows:
>> 
>> 1) git clone git://git.yoctoproject.org/poky.git
>> 2) git checkout denzil
>> 3) source poky/oe-init-build-env work-area
>> 4) Edit local.conf so that threads/parallel make are both 16 and MACHINE is 'atom-pc'
>> 8) bitbake virtual/kernel.
>> 
>> However, the kernel that gets produced fails to boot. All I get is a screen full of random characters and nothing comes out of the serial port (configured for kernel messages). I don't get any 'Loading...' or 'Uncompressing...' messages either. Using a kernel image from else where (e.g. Voyage Linux) works as expected.
>> 
>> What do I need to do differently to get the above to build a bootable image? I'm assuming that 'atom-pc' works for others?
> When I build for Atom PCs, I'm usually targeting a specific BSP like CrownBay, n450, Cedartrail. All of those require the meta-intel layer. So you need to edit the local.conf with a machine like n450, crownbay, cedartrail, etc. and you need to edit bblayer.conf to add the meta-intel layer and the meta-intel/meta/crownbay, etc.

I've just tried 'n450' and that gives the same result - I.e. screen full of random stuff.

> I always bitbake core-image minimal or core-image-sato.

I generally build a full image as well, but I'm just after a kernel that I can boot at the moment so virtual/kernel is enough for now ;-)

The 2.6.? kernel for my BSP that I build under Poky-4 runs, but I've not managed to get 3.0 or 3.2 to work from Poky-7 (for my BSP). So I thought I would go for a 'known good' kernel and modify it for my needs. However, I've not managed to get the 'known good' start point yet ;-)

Chris Tapp

opensource@keylevel.com
www.keylevel.com