Hi Guillaume, I bought a Rasppery-Pi(B) board to finally be able to test something I have the same trouble. So far the board does not boot. my current disk layout looks like this for the test image: parted /tmp/LimeJeOS-13.1.armv6l-1.13.1.raw print Model: (file) Disk /tmp/LimeJeOS-13.1.armv6l-1.13.1.raw: 774MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 211MB 210MB primary fat32 boot, lba, type=0c 2 212MB 774MB 562MB primary lvm, type=8e

If I resize FAT partition with YaST partitionner from 200 MB to 196 MB or less, it does boot.

Now that you remind me on this I remember you wrote me a mail I'm sorry I totally have missed that. So you are saying if I set it should work ? That sounds strange but I will build a new image with that size and see

Moreover, raspberrypi-firmware package has bootinclude flag set to true but files ending with *.dat are missing from BOOT partition. Is there any filter for such a file?

yes I fixed some bugs in that area. I also added support for the bootloader="berryboot" so that we don't have to do this nasty things with config.txt and cmdline.txt in our handmade scripts As soon as I get my image to fly I will update the kiwi in 13.1:Ports Regards, Marcus -- Public Key available gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

No, what I mean is if I resize manually the FAT partition with YaST partitionner, then it does boot. So the partition table may be wrong or there might be some overlap or something.

I'm running out of ideas the damn thing does not boot :) I even dd'ed the first 512byte from the _working_ image from Bernhard onto the sd card, then I created the fat fs then I copied all files from Bernhards working image over to my fat filesystem and the thing still does not boot and does not give any error message... what the heck is going on there ? do we need an MLO for raspberry ? do we need to have special fat options for the filesystem ? Thanks for any hint

One last thing. Now, DTB files should be located in /boot/dtb/ folder whereas, previously, we used /boot/. So we should update kiwi accordingly, otherwise DTB files are not in BOOT partition. Do you want I send you a patch for that one or could you do it?

Would be great if you can come up with a patch Thanks much Regards, Marcus -- Public Key available gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 13/12/2013 15:26, Guillaume Gardet a écrit :

Le 13/12/2013 15:10, Marcus Schäfer a écrit :

...

Hi,

...

No, what I mean is if I resize manually the FAT partition with YaST partitionner, then it does boot. So the partition table may be wrong or there might be some overlap or something. I'm running out of ideas the damn thing does not boot :) I even dd'ed the first 512byte from the _working_ image from Bernhard onto the sd card, then I created the fat fs then I copied all files from Bernhards working image over to my fat filesystem and the thing still does not boot and does not give any error message... what the heck is going on there ? do we need an MLO for raspberry ? do we need to have special fat options for the filesystem ? Thanks for any hint No need for MLO or SPL or such things for Raspberry Pi. Just a FAT32 partition.

Just take the OBS image and resize it from 200 MB to 190 MB using YaST partitionner. It will boot. Then if you want to size it up, you cannot reach 200 MB but only 196 MB. So, the problem seems to be in the partition size. Try it.

...

...

One last thing. Now, DTB files should be located in /boot/dtb/ folder whereas, previously, we used /boot/. So we should update kiwi accordingly, otherwise DTB files are not in BOOT partition. Do you want I send you a patch for that one or could you do it? Would be great if you can come up with a patch Will prepare it.

It is in attachment. Please check if it is ok to get /boot/dtb/ in BOOT partition. Guillaume

Guillaume

...

Thanks much

Regards, Marcus

Le 13/12/2013 15:57, Marcus Schäfer a écrit :

Hi,

...

...

files from Bernhards working image over to my fat filesystem and the thing still does not boot and does not give any error message... what the heck is going on there ? do we need an MLO for raspberry ? do we need to have special fat options for the filesystem ? Thanks for any hint No need for MLO or SPL or such things for Raspberry Pi. Just a FAT32 partition. Found the problem, "mkdosfs -F32 -I", without the -I switch the board does not boot

Nice. Looking forward for a new fixed kiwi to get a working Raspberry Pi image! :) Guillaume

Regards, Marcus

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 13.12.2013, at 16:12, Marcus Schäfer wrote:

Hi,

...

...

Found the problem, "mkdosfs -F32 -I", without the -I switch the board does not boot

Nice. Looking forward for a new fixed kiwi to get a working Raspberry Pi image! :)

me too :-) but now I'm struggling with the kernel not loading the initrd I'm running out of time for today but I will try this on Monday

config.txt

initramfs initrd.cpio 0x00a00000

our raspberry kernel is in principal able to use an initrd in simple gzip compressed format right ?

Any particular reason we're not using u-boot? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 13/12/2013 16:13, Alexander Graf a écrit :

On 13.12.2013, at 16:12, Marcus Schäfer wrote:

...

Hi,

...

...

Found the problem, "mkdosfs -F32 -I", without the -I switch the board does not boot Nice. Looking forward for a new fixed kiwi to get a working Raspberry Pi image! :) me too :-) but now I'm struggling with the kernel not loading the initrd I'm running out of time for today but I will try this on Monday

config.txt

initramfs initrd.cpio 0x00a00000

our raspberry kernel is in principal able to use an initrd in simple gzip compressed format right ? Any particular reason we're not using u-boot?

Stefan Seyfried worked on it some times ago but encountered problems with sd card support. Maybe we could try it again. Guillaume

Alex

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

...

...

me too :-) but now I'm struggling with the kernel not loading the initrd I'm running out of time for today but I will try this on Monday

Hmm, I did the following: config.txt ramfsfile=initrd.gz # load to some address after the kernel ramfsaddr=0x00a00000 cmdline.txt ... initrd=0xa00000,<size-in-bytes-as-hex> But imho the kernel doesn't look at the address to load the initrd from there. I checked the raspberry kernel config and found: # CONFIG_BLK_DEV_INITRD is not set Hrm, ok any reason why we compile it without initrd support ? Thanks Regards, Marcus -- Public Key available gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

...

# CONFIG_BLK_DEV_INITRD is not set

Hrm, ok any reason why we compile it without initrd support ?

AFAIK, there is no reason for that. You can enable it.

ok will try to build a new one. just to make sure I did it right adding CONFIG_BLK_DEV_INITRD in "%define config_vars" of the kernel-raspberrypi.spec is enough ? Thanks Regards, Marcus -- Public Key available gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi Marcus, Le 13/12/2013 15:57, Marcus Schäfer a écrit :

Hi,

...

...

files from Bernhards working image over to my fat filesystem and the thing still does not boot and does not give any error message... what the heck is going on there ? do we need an MLO for raspberry ? do we need to have special fat options for the filesystem ? Thanks for any hint No need for MLO or SPL or such things for Raspberry Pi. Just a FAT32 partition. Found the problem, "mkdosfs -F32 -I", without the -I switch the board does not boot

I copied your latest kiwi to devel:ARM:13.1:Contrib:RaspberryPi but the resulting JeOS image still does not boot... :( Guillaume

Regards, Marcus

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

...

I copied your latest kiwi to devel:ARM:13.1:Contrib:RaspberryPi but the resulting JeOS image still does not boot... :(

5.06.14 works fine for me, with regards to booting the kernel it doesn't get that far because if the missing initrd suppoer in the raspberry kernel though

Do you have a build log ?

I guess you did not have adapted to the berryboot loader in the XML I'm sorry I'm still not finished thus I did not blog or document the change. The way we build raspberry images in the buildservice is imho pretty weird. So in the default kiwi JeOS I use this:

berryboot-image-setup ---snip--- #!/bin/bash set -x #========================================== # Set variables #------------------------------------------ bootfs=$1 file=boot/config.txt #========================================== # disable overscan in config.txt #------------------------------------------ echo 'disable_overscan=1' >> $file ---snap--- and I don't need more, removed the editbootinstall hacks Regards, Marcus -- Public Key available gpg --keyserver gpg-keyserver.de --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

It is here: https://build.opensuse.org/build/devel:ARM:13.1:Contrib:RaspberryPi/images/a...

don't see any obvios error, the fat seems created correctly, the firmware and such is copied. Did you set a smaller size for the bootpartition ? I used bootpartsize="100M" other than that after your editboot scripts does the boot partition still look sane ? all data must be in the root of the boot partition berryboot can't read directories Regards, Marcus -- Public Key available gpg --keyserver gpg-keyserver.de --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

...

bootpartsize="100M"

Where did you add this option? In 'type' tag?

I added it in type tag and I got this error: unknown-1e2e000:0: Relax-NG validity error : Invalid attribute bootpartsize for element type

sorry my fault, must be an integer value handled as MB value. I also documented it that way... but wrote it wrong in the mail :) Regards, Marcus -- Public Key available gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

That is what I tried after sending my e-mail and indeed, it builds. ;) But still does not boot. :(

Can you send me a listing of the contents of the data on the boot partition ? just to make sure everything is there and makes sense Thanks Regards, Marcus -- Public Key available gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

bootcode.bin boot.scr Config.txt fixup_cd.dat fixup.dat fixup_x.dat start_cd.elf start.elf start_x.elf zImage

boot: 0xc815e551 boot.script initrd.uboot linux.vmx mbrid

If bootcode.bin is loaded, I should see a multi-color square on my screen. But I do not see anything.

Hmm, yes berryboot can't read from a directory but it should not matter because all required data seems to be there. Do you see the green led indicating access to the sd card on the board ? At the time I fixed the mkdosfs call I had this problem that there was simply no access to the sd card because the fat filesystem could not be read by the berryboot loader I'm sorry I have no idea what's the problem on your side. btw: I use real hardware (the board itself) to build the image Regards, Marcus -- Public Key available gpg --keyserver gpg-keyserver.de --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org