27 Nov
2018
27 Nov
'18
8:18 a.m.
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:/Pin…
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+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
2 Dec
2 Dec
3:26 a.m.
Hello,
Am 26.11.18 um 20:18 schrieb Freigeist:
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:/Pin…
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.
That assumption is wrong. To boot you mainly need the right bootloader,
and you're using that of the Pine64 board instead of one for Pinebook,
so all kinds of subtle differences such as display vs. HDMI or differing
Ethernet PHYs can cause problems.
Same as for the Banana Pi M64 you can use the Pine64 image as a base but
need the right U-Boot for your hardware. Otherwise it will not load the
right .dtb even if installed - it simply doesn't know it's a Pinebook.
A pinebook_defconfig exists. I don't have a Pinebook myself, so can't
test it. You could add it to the hardware:boot:staging/u-boot package,
look for pine64 in pre_checkin.sh.
Beware that there's a known serial output issue with
arm-trusted-firmware in version 2.0.
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?
Leave it alone. The SD card image is smaller than your card (therefore
no backup table at the end of the card) and it resizes on first boot.
If your tools make the primary GPT too large (by using its default size)
it will overwrite U-Boot at offset 8K.
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(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
3 Dec
3 Dec
8:02 a.m.
Hello Andreas,
thanks for your answer. It helped me to come some steps further, please
see below.
On 01/12/2018 15:26, Andreas Färber wrote:
Hello,
Am 26.11.18 um 20:18 schrieb Freigeist:
I understand, thanks for the explanation.
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.
That assumption is wrong. To boot you mainly need the right bootloader,
and you're using that of the Pine64 board instead of one for Pinebook,
so all kinds of subtle differences such as display vs. HDMI or differing
Ethernet PHYs can cause problems.
Same as for the Banana Pi M64 you can use the Pine64 image as a base but
need the right U-Boot for your hardware. Otherwise it will not load the
right .dtb even if installed - it simply doesn't know it's a Pinebook.
A pinebook_defconfig exists. I don't have a Pinebook myself, so can't
test it. You could add it to the hardware:boot:staging/u-boot package,
look for pine64 in pre_checkin.sh.
Beware that there's a known serial output issue with
arm-trusted-firmware in version 2.0.
Thanks alot, I found pinebook_defconfig here
https://github.com/u-boot/u-boot/tree/master/configs
I have to admit that I have no experience in how to add/change files
to/in obs but I am willing to learn it but it will take some time.
However, I could need some initial help to get started if you don't mind.
1. I branched hardware:boot:staging/u-boot into my home project,
downloaded u-boot-2018.11.tar.bz2, added pinebook_defconfig to
u-boot-2018.11.tar.bz2/configs, uploaded it and submitted it to
hardware:boot:staging/u-boot.
I got an error message telling me that no source files have been changed
but when I do a refresh on hardware:boot:staging/u-boot it says that
u-boot-2018.11.tar.bz2 has been changed 10 mins ago, so I assume that it
has arrived. I hope I did everything right.
2. There is no pure pine64 in pre_checkin.sh only these two lines:
_Code_
# Allwinner
aarch64_boards="$aarch64_boards bananapi_m64 nanopi_a64 orangepi_pc2
pine64_plus pine_h64"
BINEND=img
SUNXI_SPL=1
;;
bananapi_m64|nanopi_a64|orangepi_pc2|pine64_plus|pine_h64)
_Code end_
What would I be doing now? Simply add pinebook_a64 to the above lines in
pre_checkin.sh?
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
5 Dec
5 Dec
7:39 a.m.
On 02/12/2018 20:02, Freigeist wrote:
What would I be doing now? Simply add pinebook_a64 to
the above lines in
pre_checkin.sh?
Never mind, I think I figured it out. Submit request sent.
Regards, Andreas
--
On a long enough timeline the survival rate for everyone drops to zero...
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
816
days inactive
824
days old
3 comments
2 participants
participants (2)
-
Andreas Färber -
Freigeist