[opensuse-arm] [aarch64] TW on Pinebook?
Hello, yesterday I finally got my 14'' Pinebook [1]. There is Ubuntu 16.04 MATE as a default OS, but I would like to use openSUSE TW on it of course. So, I found raw.xz XFCE-image for aarch64 [2] and used this command "to burn" image on the microSD card: # unxz -c openSUSE-Tumbleweed-ARM-XFCE-efi.aarch64-2017.06.10-Build2.3.raw.xz | sudo dd of=/dev/mmcblk1p No success. Pinebook tried to boot from microSD card, but... it seems that there is something wrong with bootloader. Here [3] I found this command: # xzcat openSUSE-Tumbleweed-ARM-XFCE-efi.aarch64-2017.06.10-Build2.3.raw.xz | dd bs=4M of=/dev/ mmcblk1p oflag=sync Exactly the same... image is there, echo $? tells 0, but pinebook ignore it. Image on microSD card is marked as a bootable. I checked it with parted(8). I asked Google and it showed me this [4]. This is HOWTO for fedora 21 on Cubietruck, but there is one interesting thing: step (4) Write U-Boot to Media. Do we also need to install bootloader extra? Because, as I said, for me it seems like a bootloader problem. If yes, where is this script or documentation about it? Also I would ask about rootfs-images. Do we have some information/HOWTOs about these? Cheers, Alex [1] https://www.pine64.org/?page_id=3707 [2] http://download.opensuse.org/ports/aarch64/tumbleweed/images/openSUSE-Tumble... [3] https://en.opensuse.org/HCL:AArch64_EFI [4] https://kashyapc.fedorapeople.org/arm/installing-Fedora-21-on-microSD-card-f... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Samstag, 12. August 2017 20:20:03 CEST Alex Naumov wrote:
Hello,
yesterday I finally got my 14'' Pinebook [1]. There is Ubuntu 16.04 MATE as a default OS, but I would like to use openSUSE TW on it of course.
So, I found raw.xz XFCE-image for aarch64 [2] and used this command "to burn" image on the microSD card:
All Aarch64 SBCs (Single board computer) I am aware of do not support UEFI boot, but require a (more or less) board specific boot image. For the Pinebook, your best bet is with the Pine64 Contrib image: https://en.opensuse.org/HCL:Pine64 But although this will likely boot, you will get much less than you might expect: 1. No graphics on LCD 2. No graphics via HDMI 3. Wireless may work - probably not With some luck, HDMI will be ready end of the year, but this will *not* include 2D/3D acceleration nor hardware video decoding. For the current state of the A64 support, see here: http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, about 2 months ago I installed armbian[1] on my Pinebook. Everything works well. That would be great to integrate everything (Pinebook support) what have armbian to us TW images. But here we have to decide: do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it? I would like to help, but need to be supported from coordinator, who has more experience. Cheers, Alex [1] https://www.armbian.com/ On Sun, Aug 13, 2017 at 2:27 AM, Stefan Bruens <stefan.bruens@rwth-aachen.de> wrote:
On Samstag, 12. August 2017 20:20:03 CEST Alex Naumov wrote:
Hello,
yesterday I finally got my 14'' Pinebook [1]. There is Ubuntu 16.04 MATE as a default OS, but I would like to use openSUSE TW on it of course.
So, I found raw.xz XFCE-image for aarch64 [2] and used this command "to burn" image on the microSD card:
All Aarch64 SBCs (Single board computer) I am aware of do not support UEFI boot, but require a (more or less) board specific boot image. For the Pinebook, your best bet is with the Pine64 Contrib image:
https://en.opensuse.org/HCL:Pine64
But although this will likely boot, you will get much less than you might expect:
1. No graphics on LCD 2. No graphics via HDMI 3. Wireless may work - probably not
With some luck, HDMI will be ready end of the year, but this will *not* include 2D/3D acceleration nor hardware video decoding.
For the current state of the A64 support, see here:
http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix
Kind regards,
Stefan
-- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Alex, Am 11.12.2017 um 14:22 schrieb Alex Naumov:
do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it?
I don't think it's possible to combine the Pinebook into an existing image, as it likely needs its own U-Boot with matching Device Tree. That leaves us with two options: a) Derive a new separate image once all needed packages are in place. As long as arm-trusted-firmware is not in Tumbleweed, such an image can only live in some Contrib repository, not officially part of Tumbleweed. b) Use pine64-instsd [*] as inspiration to build a bootable SD image and then install interactively from an .iso on USB stick. Regards, Andreas [*] https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Pine64/pin... -- 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
On 11 December 2017 at 20:23, Andreas Färber <afaerber@suse.de> wrote:
Hi Alex,
Am 11.12.2017 um 14:22 schrieb Alex Naumov:
do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it?
I don't think it's possible to combine the Pinebook into an existing image, as it likely needs its own U-Boot with matching Device Tree.
That leaves us with two options:
a) Derive a new separate image once all needed packages are in place. As long as arm-trusted-firmware is not in Tumbleweed, such an image can only live in some Contrib repository, not officially part of Tumbleweed.
Is there a particular reason why arm-trusted-firmware isn't in Tumbleweed yet? Sorry but I missed any previous discussion on ATF.
b) Use pine64-instsd [*] as inspiration to build a bootable SD image and then install interactively from an .iso on USB stick.
Regards, Andreas
[*] https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Pine64/pin...
-- 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
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Monday, December 11, 2017 9:47:02 PM CET Andrew Wafaa wrote:
On 11 December 2017 at 20:23, Andreas Färber <afaerber@suse.de> wrote:
Hi Alex,
Am 11.12.2017 um 14:22 schrieb Alex Naumov:
do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it?
I don't think it's possible to combine the Pinebook into an existing image, as it likely needs its own U-Boot with matching Device Tree.
That leaves us with two options:
a) Derive a new separate image once all needed packages are in place. As long as arm-trusted-firmware is not in Tumbleweed, such an image can only live in some Contrib repository, not officially part of Tumbleweed.
Is there a particular reason why arm-trusted-firmware isn't in Tumbleweed yet? Sorry but I missed any previous discussion on ATF.
At least for the Pine64 (which the Pinebook is based on) the ATF is a fork of the upstream ATF ... Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
Am 11.12.2017 um 21:47 schrieb Andrew Wafaa:
On 11 December 2017 at 20:23, Andreas Färber <afaerber@suse.de> wrote:
Am 11.12.2017 um 14:22 schrieb Alex Naumov:
do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it?
I don't think it's possible to combine the Pinebook into an existing image, as it likely needs its own U-Boot with matching Device Tree.
That leaves us with two options:
a) Derive a new separate image once all needed packages are in place. As long as arm-trusted-firmware is not in Tumbleweed, such an image can only live in some Contrib repository, not officially part of Tumbleweed.
Is there a particular reason why arm-trusted-firmware isn't in Tumbleweed yet? Sorry but I missed any previous discussion on ATF.
Short summary: U-Boot is in Base:System devel project and for some boards now has a soft dependency on ATF - builds okay but won't work. Base:System has so few maintainers and keeps blocking and rebuilding packages (due to core packages such as glibc), that we've already resorted to Base:System:Staging for actually being able to test new sub-packages and updates. So I really don't want to submit my ATF packages to Base:System. Additionally, Andre did not yet get his Allwinner A64/H5 support merged into upstream ATF, so an arm-trusted-firmware package today would only help e.g. Firefly-RK3399 and Geekbox, not Pine64 or Orange Pi PC 2. One proposed idea was a new sub-project under "hardware" (where u-boot or arm-trusted-firmware don't fit 100%, I'm surprised vboot was accepted despite not being about peripherals), but so far we haven't discussed any names or alternative locations. Opinions? 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
On Monday, December 11, 2017 9:23:32 PM CET Andreas Färber wrote:
Hi Alex,
Am 11.12.2017 um 14:22 schrieb Alex Naumov:
do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it?
I don't think it's possible to combine the Pinebook into an existing image, as it likely needs its own U-Boot with matching Device Tree.
That leaves us with two options:
a) Derive a new separate image once all needed packages are in place. As long as arm-trusted-firmware is not in Tumbleweed, such an image can only live in some Contrib repository, not officially part of Tumbleweed.
The Pinebook is based on the Pine64. The most important difference is the eMMC and the missing Ethernet. I think it should be possible to run the Pine64 image on the Pinebook, although without any graphics. The UART which on the Pine64 is exposed on the Euler and EXP connector (PB8/ PB9) is available on the headphone port when either "SW11" is closed or PL10 is set to "High". When you connect a USB-Ethernet dongle, it should fetch an IP address via DHCP, and you should be able to ssh into it (login/pw: root/linux or linux/ linux). Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
participants (5)
-
Alex Naumov -
Andreas Färber -
Andrew Wafaa -
Stefan Bruens -
Stefan Brüns