RaspberryPi Kernel - Fails to boot when sound driver is a built-in

RaspberryPi Kernel - Fails to boot when sound driver is a built-in

[Chris Tapp]

If I build the RPi kernel (SRCREV 3fc65f9f291fb19cad434968a4a0f66ab749e637) then the board boots as expected.

However, if a modify the .config (either manually after -c configure, or by -c menuconfig) so that CONFIG_SND, CONFIG_SND_TIMER, CONFIG_SND_PCM and CONFIG_BCM2835 are set to 'y' (i.e. changed from modules) then the kernel no longer boots.

Has anyone else tried to do this? I'm trying to get a kernel that has ALSA working out-of-the-box.

Chris Tapp

opensource@keylevel.com
www.keylevel.com

Re: RaspberryPi Kernel - Fails to boot when sound driver is a built-in

[Paul Eggleton]

On Monday 18 June 2012 22:16:44 Chris Tapp wrote:
> If I build the RPi kernel (SRCREV 3fc65f9f291fb19cad434968a4a0f66ab749e637)
> then the board boots as expected.
> 
> However, if a modify the .config (either manually after -c configure, or by
> -c menuconfig) so that CONFIG_SND, CONFIG_SND_TIMER, CONFIG_SND_PCM and
> CONFIG_BCM2835 are set to 'y' (i.e. changed from modules) then the kernel
> no longer boots.
> 
> Has anyone else tried to do this? I'm trying to get a kernel that has ALSA
> working out-of-the-box.

Well, FWIW I can't even get a kernel with the default configuration built from 
meta-raspberrypi to boot - I even tried copying it to a Debian SD-card and it 
doesn't boot there either. All I get is a black screen or with the newer 
firmware I get the four-colour display which apparently indicates it couldn't 
load the kernel.

Any suggestions would be welcome...

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: RaspberryPi Kernel - Fails to boot when sound driver is a built-in

[Chris Tapp]

Hi Paul,

On 24 Jun 2012, at 16:25, Paul Eggleton wrote:

> On Monday 18 June 2012 22:16:44 Chris Tapp wrote:
>> If I build the RPi kernel (SRCREV 3fc65f9f291fb19cad434968a4a0f66ab749e637)
>> then the board boots as expected.
>> 
>> However, if a modify the .config (either manually after -c configure, or by
>> -c menuconfig) so that CONFIG_SND, CONFIG_SND_TIMER, CONFIG_SND_PCM and
>> CONFIG_BCM2835 are set to 'y' (i.e. changed from modules) then the kernel
>> no longer boots.
>> 
>> Has anyone else tried to do this? I'm trying to get a kernel that has ALSA
>> working out-of-the-box.
> 
> Well, FWIW I can't even get a kernel with the default configuration built from 
> meta-raspberrypi to boot - I even tried copying it to a Debian SD-card and it 
> doesn't boot there either. All I get is a black screen or with the newer 
> firmware I get the four-colour display which apparently indicates it couldn't 
> load the kernel.
> 
> Any suggestions would be welcome...


Firstly:
1) Are you using the SRCREVs as supplied, or have you updated them?
2) Which version of the bootfiles are you using?

Everything is in such a state of flux at the moment that it does seem to be difficult to be sure what works one day will work if you upgrade anything to use the latest versions. I can get some combinations to work, the most up-to-date being:

1) Use the bootfiles with SRCREV = "9308c7ed387e5422883753f7fb71a75506abd1f8"
2) Build the kernel using SRCREV = "3fc65f9f291fb19cad434968a4a0f66ab749e637"

Later kernels should be 'better', but I've not yet got any to boot. I use the serial port to monitor the boot and this shows nothing. Not seen if the color bars show as I've not looked - will do next time I have a play.

BTW - you need to update the .conf file for the machine to use ttyAMA0 if you want to use the serial port for kernel debug.

There have been a lot of changes to the kernel / bootfiles that mean you must update both to get a working image. Some of these relate to where the image is loaded, some to how the screen is activated (my config.txt entries to set the HDMI video mode stopped working at one point). It seems as if nothing is really fixed at the moment and you need to be prepared to 'do some digging' if you change anything. When I get a moment I want to suggest that a list of matched SRCREVs for 'stable' builds that have been verified can be kept somewhere.

Chris Tapp

opensource@keylevel.com
www.keylevel.com

Re: RaspberryPi Kernel - Fails to boot when sound driver is a built-in

[Chris Tapp]

On 24 Jun 2012, at 21:31, Chris Tapp wrote:

> Hi Paul,
> 
> On 24 Jun 2012, at 16:25, Paul Eggleton wrote:
> 
>> On Monday 18 June 2012 22:16:44 Chris Tapp wrote:
>>> If I build the RPi kernel (SRCREV 3fc65f9f291fb19cad434968a4a0f66ab749e637)
>>> then the board boots as expected.
>>> 
>>> However, if a modify the .config (either manually after -c configure, or by
>>> -c menuconfig) so that CONFIG_SND, CONFIG_SND_TIMER, CONFIG_SND_PCM and
>>> CONFIG_BCM2835 are set to 'y' (i.e. changed from modules) then the kernel
>>> no longer boots.
>>> 
>>> Has anyone else tried to do this? I'm trying to get a kernel that has ALSA
>>> working out-of-the-box.
>> 
>> Well, FWIW I can't even get a kernel with the default configuration built from 
>> meta-raspberrypi to boot - I even tried copying it to a Debian SD-card and it 
>> doesn't boot there either. All I get is a black screen or with the newer 
>> firmware I get the four-colour display which apparently indicates it couldn't 
>> load the kernel.
>> 
>> Any suggestions would be welcome...
> 
> 
> Firstly:
> 1) Are you using the SRCREVs as supplied, or have you updated them?
> 2) Which version of the bootfiles are you using?
> 
> Everything is in such a state of flux at the moment that it does seem to be difficult to be sure what works one day will work if you upgrade anything to use the latest versions. I can get some combinations to work, the most up-to-date being:
> 
> 1) Use the bootfiles with SRCREV = "9308c7ed387e5422883753f7fb71a75506abd1f8"
> 2) Build the kernel using SRCREV = "3fc65f9f291fb19cad434968a4a0f66ab749e637"
> 
> Later kernels should be 'better', but I've not yet got any to boot. I use the serial port to monitor the boot and this shows nothing. Not seen if the color bars show as I've not looked - will do next time I have a play.

Yep, the later kernels just give the four-colour display. I wonder what's changed this time round?

> BTW - you need to update the .conf file for the machine to use ttyAMA0 if you want to use the serial port for kernel debug.
> 
> There have been a lot of changes to the kernel / bootfiles that mean you must update both to get a working image. Some of these relate to where the image is loaded, some to how the screen is activated (my config.txt entries to set the HDMI video mode stopped working at one point). It seems as if nothing is really fixed at the moment and you need to be prepared to 'do some digging' if you change anything. When I get a moment I want to suggest that a list of matched SRCREVs for 'stable' builds that have been verified can be kept somewhere.
> 
> Chris Tapp
> 
> opensource@keylevel.com
> www.keylevel.com
> 
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Chris Tapp

opensource@keylevel.com
www.keylevel.com

Re: RaspberryPi Kernel - Fails to boot when sound driver is a built-in

[Paul Eggleton]

On Sunday 24 June 2012 21:31:41 Chris Tapp wrote:
> On 24 Jun 2012, at 16:25, Paul Eggleton wrote:
> > Well, FWIW I can't even get a kernel with the default configuration built
> > from meta-raspberrypi to boot - I even tried copying it to a Debian
> > SD-card and it doesn't boot there either. All I get is a black screen or
> > with the newer firmware I get the four-colour display which apparently
> > indicates it couldn't load the kernel.
> 
> Firstly:
> 1) Are you using the SRCREVs as supplied, or have you updated them?
> 2) Which version of the bootfiles are you using?
> 
> Everything is in such a state of flux at the moment that it does seem to be
> difficult to be sure what works one day will work if you upgrade anything
> to use the latest versions. I can get some combinations to work, the most
> up-to-date being:
> 
> 1) Use the bootfiles with SRCREV =
> "9308c7ed387e5422883753f7fb71a75506abd1f8" 2) Build the kernel using SRCREV
> = "3fc65f9f291fb19cad434968a4a0f66ab749e637"

So far I've tried the following:

1) The current default in meta-raspberrypi - bootfiles at 
56cd7ffb3f7244017c8eb3b492ea37592c678506 and kernel 
0ec4154d64ebba48ca2446cde60a90546311defc

2) The above kernel with known-good bootfiles from a Debian SD card

3) The above kernel *on* the known-good Debian SD card

4) Known good kernel with the above bootfiles

5) The combination you suggested above

6) The latest available kernel + bootfiles

Of those, only option 4 sort-of worked.

> BTW - you need to update the .conf file for the machine to use ttyAMA0 if
> you want to use the serial port for kernel debug.

I did that, however it's not going to be much help as I don't yet have a 
serial cable (I have one on order).
 
I'm beginning to wonder if it's something about the way the kernel is being 
built. Are you using denzil or master of Poky?/OE-core?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre