Op zaterdag 1 december 2018 16:59:44 CET schreef Freek de Kruijf: > Op zaterdag 1 december 2018 15:47:17 CET schreef Andreas Färber: > > Am 26.11.18 um 13:08 schrieb Freek de Kruijf: > > > I downloaded the Upstream Pine64 image, did put it on a 16 GB micro-SD, > > > and > > > started the Banana Pi M64 with it. It did boot, which I followed on the > > > serial console, USB-TTL serial cable. However the Ethernet device did > > > not > > > come up. > > Hi Andreas, > thanks for your answer. > > > Did you or did you not dd the M64 u-boot-sunxi-with-spl.bin file as I > > documented on the Wiki page? > > I did not. Didn't know where to find that file. > > > If you use the Pine64 bootloader and Device Tree, all kinds of things > > can go wrong. > > Apparently I am fine, except that when booting right after power on, the > Ethernet device does not come up. However a "shutdown -r now" does a reboot > and the device does come up. > > > > I did a reboot and now the Ethernet device comes up and gets addresses. > > > Also zypper ref works. > > > I inspected repository Factory-Contrib-Pine64 and u-boot-pine64plus is > > > installed. There I also found u-boot-bananapim64, should that one be > > > installed? > > I just tried a "zypper in --download-only u-boot- > bananapim64-2018.11-95.1.aarch64" which conflicts with u-boot- > pine64plus-2018.11-95.1.aarch64. > I downloaded it using curl and got: > # rpm -ql u-boot-bananapim64-2018.11-95.1.aarch64.rpm > /boot/sunxi-spl.bin > /boot/u-boot-sunxi-with-spl.bin > /boot/u-boot.itb > /usr/share/doc/packages/u-boot-bananapim64 > /usr/share/doc/packages/u-boot-bananapim64/README > /usr/share/licenses/u-boot-bananapim64 > /usr/share/licenses/u-boot-bananapim64/gpl-2.0.txt > > > It doesn't matter which package is installed, it only matters which > > binary was written (dd'ed) to the right location on the SD card. > > So these above files in /boot are not used in the boot process? > > > Uninstalling u-boot-pine64plus is certainly a good idea to avoid > > mistakes, but installing u-boot-bananapim64 is only one way of obtaining > > the binary to dd onto the SD card. You could also extract the .rpm on > > another machine, using e.g. file-roller or command line tools. > > So I should move the above /boot/u-boot-sunxi-with-spl.bin to my desktop > system and dd that file with "dd if=u-boot-sunxi-with-spl.bin of=/dev/sdX > bs=1024 seek=8" to the SD card? > This moves the content of that file to a location on the micro-SD which lies > before the sector 2048 on which /dev/mmcblk0p1 starts. Starts at sector 16? > > Regards, > > Andreas
Tried another test SD card with your recipe on the wiki. Did work. So I also transferred u-boot-sunxi-with-spl.bin to the SD card I already did have running. Now the Ethernet interface comes up right away. Will update the wiki on how to get u-boot-sunxi-with-spl.bin. On the test SD I saw also the eMMC visible, however it not visible on my first SD which I am preparing for production. On this SD I removed kernel 4.19.2, now running 4.18.15-1. Just saw Tumbleweed 20181129 is available. Will install that system. Uses 4.19.4. -- 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
