Search the Community
Showing results for 'pinebook' in topics.
-
You need a special version for that one to work ... but just for trying. Nobody will waste time on kernel 3.10.y Its all written here: https://www.armbian.com/pinebook-a64/ While with modern kernel - one SD card works on both: Today/tomorrow images will be updated and tested once again.
-
This one from the website downloads https://dl.armbian.com/pinebook-a64/Debian_stretch_dev_desktop.7z It boots up fine now that I swapped to a 1920x1080 LCD. Before I didn't even see the boot text messages, now I do and it starts all the way into the desktop. Of course now the Armbian Bionic Legacy Kernel 3.10 that used to work, no longer does but I kind of expected that.
-
Did you try to boot the console or the Desktop version? I did find armbian 5.56 only with kernel 3.10 in the downloads. This is the "oldest" 4.19 download (but with armbian 5.67): https://dl.armbian.com/pinebook-a64/archive/Armbian_5.67_Pinebook-a64_Debian_stretch_dev_4.19.2_desktop.7z The latest 5.59 nightly is at kernel 4.18: https://dl.armbian.com/pinebook-a64/nightly/Armbian_5.59.180830_Pinebook-a64_Debian_stretch_dev_4.18.5_desktop.7z Which download-link did you use?
-
Mine is also the Non-HD 1366x768 Pinebook
-
Today I compiled DEV for the Pinebook via the armbian-build-system and the created stretch-Desktop-image ARMBIAN 5.68 user-built Debian GNU/Linux 9 (stretch) 4.19.12-sunxi64 Linux pinebook 4.19.12-sunxi64 #5.68 SMP Mon Jan 7 12:43:14 +03 2019 aarch64 GNU/Linux did boot without problems from my sdcard on my Non-HD-Pinebook Also did install & boot from eMMC (did use ext4-format)
-
[RFC 001] Changes for boards and features implementing
Igor replied to Igor's topic in Armbian build framework
I see. It will work this way: https://github.com/armbian/build/blob/tvboxes/config/packages/99-board/dedicated/pinebook-a64/armbian.postinst.bash -
Hi! I already successfully get mainline Armbian working on Pinebook (no sound - working on fix, and also suspend took much time to wake up), but, I don't like the way how I made it. Github repo: https://github.com/gamelaster/build/tree/pinebook-build I set the branch to "next", I set kernel repository to anarsoul's kernel (contains latest patches for A64 and also for Pinebook & Sopine devices) and deleted all patches from sunxi-next (all that patches has been for 4.14), I just kept and add some of patches. But this is probably terrible idea. @Igor or anyone, can you please me suggest better way to support "next" kernel (The task is to support latest anarsoul's kernel)? I was thinking about changing KERNELFAMILY variable, but really dunno, I'm using Armbian build environment for first time. P.S. the beta automatical build for Pinebook boots u-boot, then kernel, but in kernel is something messed up (the LCD shutdowns after few second of kernel booted), but I will try to fix it, to have "dev" support too Thanks for advices! - gamiee
-
Haven't found the problem either, but I applied a dirty fix that we have at least screen. https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/xxx-pinebook-revert-pwm-polairity-TEMP-WORKAROUND.patch This gives screen but kills pwm control. https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/Revert_BT_HCIUART_RTL_ACPI_dependency.patch Fix to make bluetooth part compilable, but I could not get it working yet.
-
Outside of the PineBook and the RPi based items... ChromeOS - Samsung Chromebook Plus (1st gen) and Acer R13 (CB5-312T-K5X4) support Crostini (Linux KVM as guest OS running Debian) and Android's Google Play Store... both of these are ARM based, and there are other ARM chromebooks that might also be useful...
-
You already helped a LOT! Indeed! Let's fix this Pinebook's troubles and we might slowly switch 4.19.y to nightly NEXT building ...
-
Nice to have those tested: Sopine A64 Olimex Lime 2 eMMC Those are still problematic and should be fixed before any update: Orange Pi Zero Plus2 H5 Pinebook
-
Good day. Can you please tell me what needs to be done to make the bluetooth work? As I understand it, you need a file https://github.com/armbian/build/blob/master/packages/bsp/pinebook/pinebook-bluetooth.service. What to do with it? My opi prime works on Armbian Stretch mainline kernel 4.14.y
-
It works on A64/Pinebook (LCD brightness). It should work on H5 but I haven't done any tests. DEV branch (4.19.y).
-
Latest build from Armbian dev 4.19.2 Still strange ... Are you using pinebook image on a pine64 board ? Because the SDIO node doesn't exist on Pine64 DT, but it is there for Pinebook ... -
Using custom kernel for a board
martinayotte replied to gamelaster's topic in Armbian build framework
@Igor Did you figured out why those patch prevent Pinebook to boot ? (it didn't previously) -
@gamelaster If you will try with our patchset, disable those and Pinebook should boot: general-add-overlay-compilation-support.patch general-enable-kernel-dtbs-symbol-generation.patch general-sunxi-overlays.patch
-
Great progress!!! We need to keep one kernel for many hw and that's why patches are a must. Current situation is still messy and I only find out that some of my additional patches are causing Pinebook to hang at boot. I also plan to merge a dozent of patches, some sent upstream to make it easier to maintain. I was working whole day yesterday and the day before and the day before ... I can add new updated test image, but it is much better for me to do nothing for a few days. When things are merged in, images can be produced automatically. No need to rush anywhere. Production ready images shell go out when DEV branch is tested very well and is moved to NEXT. We still miss suspend / resume, right? This is a must function for notebooks. I haven't saw if there is a solution developed for that?
-
1st build: https://dl.armbian.com/pinebook-a64/Debian_stretch_dev_desktop.7z (still cleaning patches)
-
which Pinebook problems? I did see that the report for the Pinebook is out of date, but there was no newer kernel as the latest report on your page. For testing other Pinebook things - I only have a "old" Pinebook - the non-1080-one at 14" -
Perhaps those warnings can be cleared out even they are harmless ... @guidol tnx. I am getting close to Pinebook(s) problems.
-
Those boards still need to be tested - some of them I don't have: Nanopi Neo Core 2 LTS Orange Pi R1 Pinebook A64 (know to break booting atm) Sopine A64 Olimex Lime 2 eMMC Nanopi Neo Air Pine64
-
We need to sort that out, 4.19.y is only interesting on this Pinebook. Remove all but https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/general-packaging-4.17-dev.patch and try ... than add patch by patch. I have no idea which is breaking this ATM.
-
board support - general discussion / project aims
Igor replied to chwe's topic in Advanced users - Development
There is no diff between OdroidC2 NEXT and meson64 next since the last update. Known problems: USB hot plugging and network initialisation on some C2 boards. I don't know if this latter happens on a stock 3.x kernel too. XU4 default 3.10.y could be also added to the EOS list. Maturity is unknown to me as well. Back then I did a basic adjustment and made few tests. Known problems and shortcomings: no HDMI, no DVFS, halt on reboot, ... modern u-boot support? Not sure if this will change anytime soon. We can drop 3.x and wait with mainline for a few months else drop C1 completely? Allwinner 3.4 and 3.10/Pinebook should stay in the system. There are many users and projects such as H3Droid and Retroorangepi are dependent from it. Even there is no more development and support. Even code quality is so so ... Since we started to talk about changing u-boot update from auto to manual, which should have bigger impact on support pressure, we can lower threshold for EOS on only most obvious ones. -
Hello! Thanks for the note. It seems to be the same scenario... I'm still playing around with this Bionic and then I'll give a try to Debian stretch... I'll post here in case of success with Bionic or Deb-Stretch. Thanks and I'm still open for ideas for this armbian version recommended on Pinebook's own site... kuszi@pinebook:~$ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic kuszi@pinebook:~$ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=pinebook-a64 BOARD_NAME="Pinebook A64" BOARDFAMILY=sun50iw1 VERSION=5.56 LINUXFAMILY=pine64 BRANCH=default ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=Image
-
Today I installed the nightly version of armbian stretch ( https://dl.armbian.com/pinebook-a64/nightly/Armbian_5.59.180830_Pinebook-a64_Debian_stretch_dev_4.18.5_desktop.7z ) on my Pinebook. After using it from MicroSD card it could be installed via armbian-config to eMMC (but I did swap the original 16GB FORESEE to a 32GB SanDIsk - did buy the 32GB from Pine with my Pinebook) Seems to work - but the Wifi has on every boot a new MAC-Adress, so nmtui (Network-Manager) has many configs for the WiFi
