[opensuse-arm] Rasberry Pi 3B image openSUSE Tumbleweed starts on Banana Pi M64
Instead of a Banana Pi M3 I got a Banana Pi M64, of which I was uncertain that the processor was the same as the one on a Raspberry Pi 3B. Still I did put the image for the Raspberry Pi 3B (aarch64) on a micro-SD card and booted the BPi. I was very happy to see the system came alive. Before this I did put the Debian image on the eMMC and was able to boot that system without a micro-SD card. On this system I inserted the micro-SD with the above mentioned openSUSE system, which came alive. The initialization of the system was not completely as it should be. There was no swap at the end of the micro-SD card and the root partition was not enlarged. I did put the swap on the eMMC, effectively erasing what was there and enlarged the root partition on the micro-SD. However after that I did a "zypper dup --no-recommends" and did a reboot. The system does not start anymore. My experiments with it will be continued, but if you have any advice I will be happy to receive it. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zondag 22 juli 2018 13:26:02 CEST schreef Freek de Kruijf:
Instead of a Banana Pi M3 I got a Banana Pi M64, of which I was uncertain that the processor was the same as the one on a Raspberry Pi 3B. Still I did put the image for the Raspberry Pi 3B (aarch64) on a micro-SD card and booted the BPi. I was very happy to see the system came alive.
Before this I did put the Debian image on the eMMC and was able to boot that system without a micro-SD card. On this system I inserted the micro-SD with the above mentioned openSUSE system, which came alive. The initialization of the system was not completely as it should be. There was no swap at the end of the micro-SD card and the root partition was not enlarged. I did put the swap on the eMMC, effectively erasing what was there and enlarged the root partition on the micro-SD.
However after that I did a "zypper dup --no-recommends" and did a reboot. The system does not start anymore.
My experiments with it will be continued, but if you have any advice I will be happy to receive it.
Left the eMMC with Debian untouched and now I have a working updated Tumbleweed system after "zypper dup --no-r" and a reboot. However "uname -a" reports the Debian BPI kernel name. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 22.07.2018 um 13:26 schrieb Freek de Kruijf:
Instead of a Banana Pi M3 I got a Banana Pi M64, of which I was uncertain that the processor was the same as the one on a Raspberry Pi 3B.
It is not. Allwinner vs. Broadcom.
My experiments with it will be continued, but if you have any advice I will be happy to receive it.
My advice: Don't do that. Use a proper image, don't reuse Raspberry Pi images on non-Raspberry-Pi boards. Same for most other boards, but the Raspberry Pi uses a special MBR partitioning whereas you want GPT here. Not to mention "wrong" bootloader packages. If apparently you have the bootloader on eMMC instead of SD, you can use the generic JeOS-efi.aarch64 image, for instance. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zondag 22 juli 2018 20:35:57 CEST schreef Andreas Färber:
Am 22.07.2018 um 13:26 schrieb Freek de Kruijf:
Instead of a Banana Pi M3 I got a Banana Pi M64, of which I was uncertain that the processor was the same as the one on a Raspberry Pi 3B.
It is not. Allwinner vs. Broadcom.
My experiments with it will be continued, but if you have any advice I will be happy to receive it.
My advice: Don't do that. Use a proper image, don't reuse Raspberry Pi images on non-Raspberry-Pi boards. Same for most other boards, but the Raspberry Pi uses a special MBR partitioning whereas you want GPT here. Not to mention "wrong" bootloader packages.
If apparently you have the bootloader on eMMC instead of SD, you can use the generic JeOS-efi.aarch64 image, for instance.
Which one? I see the JeOS-efi.aarch64 install version and the normal version. Should I put the openSUSE boot image on the eMMC and how? The reason to ask is that "uname -a" shows the Debian kernel name. The root partition is on the SD. With "yast partitioner" I can enlarge the root partition and create a swap partition on the SD. I leave the eMMC alone. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zondag 22 juli 2018 21:31:22 CEST schreef Freek de Kruijf:
Op zondag 22 juli 2018 20:35:57 CEST schreef Andreas Färber:
If apparently you have the bootloader on eMMC instead of SD, you can use the generic JeOS-efi.aarch64 image, for instance.
Which one? I see the JeOS-efi.aarch64 install version and the normal version. Should I put the openSUSE boot image on the eMMC and how?
I tried the version without install in its name at no avail.
The reason to ask is that "uname -a" shows the Debian kernel name. The root partition is on the SD. With "yast partitioner" I can enlarge the root partition and create a swap partition on the SD. I leave the eMMC alone.
After searching I found two version for the BPiM64 based on openSUSE Tumbleweed dated 2017-08-29. One with MATE and one with XFCE in its name. Tried the XFCE which did boot OK. Did not use the boot system on the eMMC. However the eMMC is not visible in the system. Tried a "zypper dup --no-r", but that failed. Currently trying the MATE version with more careful upgrading the system. Boots OK without using anything on the eMMC. Removed already a lot of MATE, XFCE and GNOME. I need the system only with basic types of software, no desktop stuff. Also the cautious upgrade resulted in a failure. Maybe I have to stick with the Debian system for my server. Asked on the BPi forum how to build a newer openSUSE Tumbleweed version. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Andreas Färber -
Freek de Kruijf