[Buildroot] Image created is not booting, waiting for infinite time

[Buildroot] Image created is not booting, waiting for infinite time

[inblueswithu]

Hi,

I am trying to build a custom ARM linux kernel which must be very small 
in size. I'm new to these things.

NOTE: As I was getting errors with u-boot, I omitted bootloaders (i 've 
not selected any of it).
After compilation, I 've got zImage and rootfs.ext2 images.
When I try to run the image

    $ qemu-system-arm -M versatilepb -m 128 -kernel
    ./output/images/zImage --nographic
    oss: Could not initialize DAC
    oss: Failed to open `/dev/dsp'
    oss: Reason: No such file or directory
    oss: Could not initialize DAC
    oss: Failed to open `/dev/dsp'
    oss: Reason: No such file or directory
    audio: Failed to create voice `lm4549.out'
    Uncompressing Linux... done, booting the kernel.

It waits here for infinite time. I also tried like this as shown in 
/board/qemu/arm-versatile/readme.txt/

    $ qemu-system-arm -M versatilepb -kernel ./output/images/zImage
    -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio
    oss: Could not initialize DAC
    oss: Failed to open `/dev/dsp'
    oss: Reason: No such file or directory
    oss: Could not initialize DAC
    oss: Failed to open `/dev/dsp'
    oss: Reason: No such file or directory
    audio: Failed to create voice `lm4549.out'
    Uncompressing Linux... done, booting the kernel.

Here also it waits for infinite time. I dont know if my configuration is 
wrong or the way I'm trying to boot is wrong.
I'm attaching my configuration file also.
This is not the first time it is happening like this. I tried using 
Cross-LFS(clfs) for doing this (custom ARM linux OS).
Even then It has same effect, it waits for infinite time after that last 
line!!
Can someone plz help me.

Thanks & Regards
/inblueswithu/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120128/9a043e3a/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120128/9a043e3a/attachment-0001.ksh>

[Buildroot] Image created is not booting, waiting for infinite time

[Thomas Petazzoni]

Le Sat, 28 Jan 2012 13:55:19 +0530,
inblueswithu <inblueswithu@hotmail.com> a ?crit :

>     $ qemu-system-arm -M versatilepb -m 128 -kernel
>     ./output/images/zImage --nographic
>     oss: Could not initialize DAC
>     oss: Failed to open `/dev/dsp'
>     oss: Reason: No such file or directory
>     oss: Could not initialize DAC
>     oss: Failed to open `/dev/dsp'
>     oss: Reason: No such file or directory
>     audio: Failed to create voice `lm4549.out'
>     Uncompressing Linux... done, booting the kernel.

Most likely your kernel configuration is wrong. Please use the
qemu_arm_versatile_defconfig available in Buildroot as an initial
configuration, so that you start from a known-working configuration for
the ARM Versatile platform emulated by Qemu.

For example, your configuration selects the armeb architecture, while
most likely the Versatile Qemu support in arm only (i.e little-endian).
More or less everybody uses little-endian on ARM anyway, so you should
really start from here.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Image created is not booting, waiting for infinite time

[inblueswithu]

Hi,

On Saturday 28 January 2012 05:19 PM, Thomas Petazzoni wrote:
> Most likely your kernel configuration is wrong. Please use the
> qemu_arm_versatile_defconfig available in Buildroot as an initial
> configuration, so that you start from a known-working configuration for
> the ARM Versatile platform emulated by Qemu.
Now I 've taken qemu_arm_versatile_defconfig and added few more options. 
I 've attached the .config file.
I 've got a problem here. I 've selected Kernel headers as "Linux 
2.6.37.x" in Toolchain configuration.
But in the Kernel configuration I 've selected

      [*] Linux Kernel
                    Kernel version (Same as toolchain kernel headers)  --->
              ()    Custom kernel patches
                    Kernel configuration (Using a custom config file)  --->
              (board/qemu/arm-versatile/linux-3.1.config) Configuration
    file pa
                    Kernel binary format (zImage)  --->
                    Linux Kernel Extensions  --->

But the default here is linux-3.1.config. Is that ok??

Thanks & Regards
/inblueswithu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120129/b50aed54/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120129/b50aed54/attachment-0001.ksh>

[Buildroot] Image created is not booting, waiting for infinite time

[Thomas Petazzoni]

Le Sun, 29 Jan 2012 12:00:41 +0530,
inblueswithu <inblueswithu@hotmail.com> a ?crit :

> But the default here is linux-3.1.config. Is that ok??

Yes. The kernel headers version can be older than the kernel version
running on the platform, since the kernel-to-userspace ABI is backward
compatible.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Image created is not booting, waiting for infinite time

[inblueswithu]

On Sunday 29 January 2012 03:06 PM, Thomas Petazzoni wrote:
>
> Yes. The kernel headers version can be older than the kernel version
> running on the platform, since the kernel-to-userspace ABI is backward
> compatible.
The kernel headers version I used is 2.6.37.x. So my kernel on the 
target will be of that version.
But the kernel configuration is given as linux-3.1.config
So, my doubt is, will this new config file which indicates to be for 
kernel 3.1.x version
work fine with 2.6.37.x version of kernel?

Thanks & Regards
/inblueswithu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120129/39dd10be/attachment.html>

[Buildroot] Image created is not booting, waiting for infinite time

[Thomas Petazzoni]

Le Sun, 29 Jan 2012 17:12:57 +0530,
inblueswithu <inblueswithu@hotmail.com> a ?crit :

> The kernel headers version I used is 2.6.37.x. So my kernel on the 
> target will be of that version.

Your conclusion is wrong: it is not because you have used the kernel
headers 2.6.37.x that you *must* use 2.6.37 on your target.

Please read carefully:

 The kernel headers version *CAN* be different from the kernel version
 running on the target, as long as the kernel headers version is
 *OLDER* than the kernel version running on the target.

> But the kernel configuration is given as linux-3.1.config
> So, my doubt is, will this new config file which indicates to be for 
> kernel 3.1.x version
> work fine with 2.6.37.x version of kernel?

It might require some minor adaptation.

But still, I don't understand your persistence in trying to use 2.6.37
while the qemu_arm_versatile_defconfig is a known working
configuration. Can you please try with that one without any
modification.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Image created is not booting, waiting for infinite time

[inblueswithu]

On Sunday 29 January 2012 05:14 PM, Thomas Petazzoni wrote:
>
> Your conclusion is wrong: it is not because you have used the kernel
> headers 2.6.37.x that you *must* use 2.6.37 on your target.
Thankyou for that clarification.
> It might require some minor adaptation.
>
> But still, I don't understand your persistence in trying to use 2.6.37
> while the qemu_arm_versatile_defconfig is a known working
> configuration. Can you please try with that one without any
> modification.
I 've proceeded with few changes in the qemu_arm_versatile_defconfig but 
with out any
potential changes, it worked find. I 've got the Images and successfully 
booted them!
/This is my first successful Build!/ Thanks for all those who 
contributed to buildroot.

I still 've a lot to try, to learn the buildroot for full length 
customizing my OS.

I'll try with out any changes to the qemu_arm_versatile_defconfig and 
let you know if
it is successful.

Thanks & Regards
/inblueswithu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120129/3690af7b/attachment.html>

[Buildroot] Image created is not booting, waiting for infinite time

[inblueswithu]

On Sunday 29 January 2012 05:14 PM, Thomas Petazzoni wrote:
> But still, I don't understand your persistence in trying to use 2.6.37
> while the qemu_arm_versatile_defconfig is a known working
> configuration. Can you please try with that one without any
> modification.
I 've tried with qemu_arm_Versatile_defconfig & it worked like a charm! 
ThankU

Thanks & Regards
/inblueswithu/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120130/6a250079/attachment.html>

[Buildroot] Image created is not booting, waiting for infinite time

[Samuel Martin]

Hi,

> NOTE: As I was getting errors with u-boot, I omitted bootloaders (i 've not selected any of it).
> After compilation, I 've got zImage and rootfs.ext2 images.
> When I try to run the image
>
> $ qemu-system-arm -M versatilepb -m 128 -kernel ./output/images/zImage --nographic
> oss: Could not initialize DAC
> oss: Failed to open `/dev/dsp'
> oss: Reason: No such file or directory
> oss: Could not initialize DAC
> oss: Failed to open `/dev/dsp'
> oss: Reason: No such file or directory
> audio: Failed to create voice `lm4549.out'
> Uncompressing Linux... done, booting the kernel.
>
It looks like you did not provide any disk image[1] which can be used
by the kernel as a rootfs in the qemu command line.
Try to add '-hda ./output/images/rootfs.ext2' to the qemu command line.

[1] http://qemu.weilnetz.de/qemu-doc.html#sec_005finvocation


Regards,

Sam