[opensuse-arm] pine64-image not booting on Pinebook 1080p
Hello all, I own an 11.6" Pinebook 1080p for a few weeks now and have some problems getting opensuse running on it. Maybe someone can help me figuring out what is going wrong. I do not have a serial cable. I am using the latest pine64 image from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pine64/images/ and write it to a 32GB sdcard using the openSUSE image writer. As I could see, these images now contain a sun50i-a64-pinebook.dtb so I am assuming that they should/could boot on a pinebook. These are my problems: 1. Whenever I look at an sdcard with a freshly written image using gparted, gdisk or any other disk utility it says: "The backup GPT table is not at the end of the disk, as it should be. Fix, by moving the backup to the end (and removing the old backup)?" "Yes" or "Ignore" When I answer "Yes", the card is not recognized afterwards during boot by the pinebook anymore and the pinebook boots Arch Linux from the installed emmc. When I answer "Ignore" the card is recognized during boot by the pinebook but the screen stays black and no matter how long I wait, the pinebook does not boot of it. My questions are, is there something wrong with the image and should I fix it as above or leave it alone and just use it as it is when the image writer has finished its job? 2. I am pretty sure that the pinebook can boot from the above mentioned images because it already did but only _one_ single time and, after that one time boot event, it never did that again. I saw openSUSE's grub coming up and the last message I could see was "Loading initial ramdisk". After that the screen went black and never came back to life again. After this single succesful boot I found the root partition enlarged and a swap partition being added to the sdcard when I looked at it with gparted afterwards. I do not recall anymore if I "fixed" the GPT on the card as above under 1. before inserting it into the pinebook or if I left it unchanged but I am pretty sure that the uboot coming up and starting openSUSE's grub was the Arch Linux one from the emmc. However, I was not able to reproduce this behaviour. What am I doing wrong? 3. After that I tried to start openSUSE's grub with the Arch Linux uboot on the emmc. I was able to list the content of the esp on the sdcard from within Arch Linux's uboot and find the/EFI/BOOT/bootaa64.efi but unable to start it. Is that possible anyway and how would I do that? Thanks guys -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Question about support for Banana Pi (M64)
Op maandag 26 november 2018 13:08:36 CET schreef Freek de Kruijf: > Op zondag 25 november 2018 22:53:41 CET schreef Andreas Färber: > > > My suggestion to you Freek would be to join us in IRC on Freenode's > > > #opensuse-arm channel and we'll try to figure this out together. > > 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. 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? > Also journalctl gives only lines of 80 characters and 40 lines. I installed > xterm and used resize to give the command "COLUMNS=132;LINES=41;export > COLUMNS LINES;", which solved that problem. Pleased with the results so > far. > > Using IRC would be my first time. Will search how to use it. So far I failed to use IRC. Nickname is freek. Tried also using the Because the installed openssh-7.8p1-1.1 does not allow ssh access I replaced it by openssh-7.9p1-198.1, which I found somewhere on OBS. I also did a "zypper dup --no-r" which replaced kernel-default from 4.19.2-1 to 4.18.15-1. Symbolic links in /boot all point to these new files. However "uname -a" still shows "4.19.2-1-default". Anyway it works and it uses the same aarch64 repository as for the Raspberry Pi 3B except for the u-boot... package. -- 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
Re: [opensuse-arm] Question about support for Banana Pi (M64)
Op zondag 25 november 2018 22:53:41 CET schreef Andreas Färber: > > My suggestion to you Freek would be to join us in IRC on Freenode's > > #opensuse-arm channel and we'll try to figure this out together. 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. 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? Also journalctl gives only lines of 80 characters and 40 lines. I installed xterm and used resize to give the command "COLUMNS=132;LINES=41;export COLUMNS LINES;", which solved that problem. Pleased with the results so far. Using IRC would be my first time. Will search how to use it. -- 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
