I am using a Raspi3 with SuSE 42.1 (32b) Tumbleweed on a 32GB sdcard for some months now as a small server and firewall. Works nice.
Now I want to try the 64b version of Tumbleweed, but I cannot get the thing to boot.
I bought another 32GB sdcard, downloaded an image from http://download.opensuse.org/ports/aarch64/distribution/leap/42.2/, wrote it to the sdcard as usual, even made a verify and put the card into the Raspi. After power on - nothing. Next image, same nothing. I expanded an image on my hard disk, put it on a loop device and examined sector 0 (the GPU boot loader of the raspi does this too after power on). I did NOT find a FAT partition via sector zero) The GPT points to a FAT partition, but this has not bootcode.bin.
This means, to my understanding, that the image is not bootable for raspberry, which explains why it is not booting.
But there are reports from other people who had success.
I don’t understand it - am I missing something?
Please enlighten me, so that my poor little ARM CPU can soon execute its first real 64b commands
sorry my inexactness - I tried both, but neither worked. The last image I tried was
openSUSE-Leap42.2-ARM-JeOS-efi.aarch64-2016.11.25-Build1.12.raw.xz (download verified with sha256)
The problem must be something basic, but I’m stuck.
The hardware I use is a Raspberry 3 which is about half a year old and runs on “openSUSE Tumbleweed” 32b on a 32GB sdcard since then.
I use an USB-SDCard writer, so my raw device is not /dev/mmcblk1 but /dev/sdX, but I used it (and dd) many times before to fiddle around with the image. I dont think the problem is there.
I also copied (via dd) the card content of the working installation to the newly bought sdcard (in order to verify that the new card is OK). It works.
My procedure for trying a newly downloaded image always is
zero the whole sdcard with “dd if=/dev/zero bs=1M of=/dev/sdX”
uncompress <image>.*
dd if=<image> bs=1M of=/dev/sdX
dd bs=1M if=/dev/sdX of=<tempfile>
cmp <tempfile> <image>
So it is certain that the image was on the card.
Is it possible that the very newest Pi3 models have a different boot loader?
If you want to review the official recommended command and how to burn the image, the info is on the RPiv1 page
Note that it’s different than what you describe. Although what you describe may work, the xzcat command is the officially recommended way which I’ve found works using Linux (There is another procedure which works if you’re burning on a Windows box, but I vastly prefer the official openSUSE instructions).
From what you describe, I’ve seen similar and always related to burning the image correctly.
If you see <anything> on a monitor when you boot, only then I’ve found it’s some configuration or the image itself.
Thanks! This image works.
I downloaded
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.10.18-Build10.4.raw.xz
and did exactly what I did before with the other images. It boots and reaches the login prompt. That’s all I need.
openSUSE-Leap42.2-ARM-JeOS-efi.aarch64-2016.11.25-Build1.12.raw.xz does not boot.
Out of curiosity I compared the DOS partitions of the two images and I think I found the problem: Bootloader missing.
Somehow the build system which generates the images referenced by https://en.opensuse.org/HCL:Raspberry_Pi3 is generating images without bootloader code.
Also, the page does not seem to be properly updated, as all the links to the upstream-images (Leap and Tumbleweed) are dangling (404, Object not found).
Could please somebody fix the build script? I do not know who is the maintainer, but it would be nice if someone who knows could notify him.
Finally, I want to say thank you for your fast and helpful replies and for the great effort to launch a 64b raspi suse linux.
