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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
