Search the Community

Normally when you have installed a XFCE-Desktop image for the Pinebook A64 you could set the display brigthness with the following pkexec command to a readable higher level - like I did in the past (possible brightness values are 1-10 - on startup this is only set to 2): pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 read-out command for the current value: pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness but on standard CLI-install pkexec and xfpm-power-backlight-helper are missing, so to use this command-line (in /etc/rc.local) you have to install these 2 packages: sudo apt install xfce4-power-manager pkexec

Hi, i got a Pinebook and install the latest Armbian Image. All is working fine, only the sound output make problems. It isn't matter if i play a mp3 file or a play a YT Video. The sound is just strechted, drawned, like in slow motion. What can i do to solve this issue? Any ideas? Thank you for your help.

Hi, I update Armbian (Debian) from Kernel 5.4 to the last version Armbina 20.08.2 with Kernel 5.8.6-sunxi64, but now I don't boot the GUI. I have connected only the power and I can use from other pc from ssh. Thank you for all!

Hi, I started using pinebook armbian buster when it was beta, it worked. From that beta I upgraded yeysterday and I see no display (LCD) after kernel starts (I only see the boot). The same using a new official image [1] I know there is another places to track this issue [2], but the thing is that in the official image page [1] it says it is fully working and that is not true. There are two options: - changing the status to something beta (like before) so you are less responsible of problems - putting an image that works [1] https://www.armbian.com/pinebook-a64/ [2] https://armbian.atlassian.net/browse/AR-443

Re: the built-in 16GB emmc on a 14" pinebook (early model). Applies to Armbian_20.02.1_Pinebook-a64_bionic_current_5.4.20.img and also to trunk build with dev kernel. Prevents installation to emmc from SD, which worked from trunk@3b1418fb5b58f187c658a050c592f2c50fb2db04 in January. I haven't managed to find from which commit it started failing yet. It is in some partial/invalid state in u-boot: => mmc list mmc@1c0f000: 0 (SD) mmc@1c10000: 2 mmc@1c11000: 1 => mmc dev 0 switch to partitions #0, OK mmc0 is current device => mmc info Device: mmc@1c0f000 Manufacturer ID: 1b OEM: 534d Name: 00000 Bus Speed: 50000000 Mode: SD High Speed (50MHz) Rd Block Len: 512 SD version 2.0 High Capacity: Yes Capacity: 7.6 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes => mmc dev 1 => mmc info Device: mmc@1c0f000 Manufacturer ID: 1b OEM: 534d Name: 00000 Bus Speed: 50000000 Mode: SD High Speed (50MHz) Rd Block Len: 512 SD version 2.0 High Capacity: Yes Capacity: 7.6 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes => mmc dev 2 Card did not respond to voltage select! It is absent when booted, though has a token line in the log as "mmc1": # dmesg | grep -i mmc [ 2.515757] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 2.541026] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB, uses new timings mode [ 2.542017] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq [ 2.560303] mmc0: error -110 whilst initialising SD card [ 2.565772] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB, uses new timings mode [ 2.584669] mmc1: new high speed SDIO card at address 0001 [ 2.592188] sunxi-mmc 1c11000.mmc: initialized, max. request size: 2048 KB, uses new timings mode [ 3.645870] mmc0: new high speed SDHC card at address 0001 [ 3.646999] mmcblk0: mmc0:0001 00000 7.61 GiB [ 3.649985] mmcblk0: p1 p2 [ 4.019864] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 5.389779] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro

I've created an armbian minimal image for my pinebook with luks encryption. It works fine but I cannot see the password prompt on screen... the boot process is: * The armbian uboot is displayed * Then a black screen... After a few seconds I'm assuming it is time to put my luks password, so I do it * Then the screen starts to show the boot text Is this expected? Am I doing something wrong? I don't want to install plymouth, just the usual LUKS password prompt. Thanks!

I have an early model of the 14" pinebook with the 1366x768 panel, apparently this model has invalid EDID which prevents the display working. During booting the log is full of errors like this and also a [ 10.808400] [drm:anx_aux_transfer [analogix_dp_i2c]] *ERROR* Failed to wait for AUX channel (status: 02) [ 10.816392] [drm:anx_aux_transfer [analogix_dp_i2c]] *ERROR* Failed to wait for AUX channel (status: 02) [ 10.816409] [drm:anx6345_bridge_enable [analogix_anx6345]] *ERROR* Failed to power up DisplayPort link: -110 [ 10.816415] [drm:anx6345_bridge_enable [analogix_anx6345]] *ERROR* Failed transmitter initialization: -110 [ 10.816420] [drm:anx6345_bridge_enable [analogix_anx6345]] *ERROR* Failed DisplayPort transmitter initialization: -110 [ 10.827228] [drm:anx6345_bridge_enable [analogix_anx6345]] *ERROR* Failed to initialize: -110 [ 10.829757] Console: switching to colour frame buffer device 128x48 [ 12.003087] sun4i-drm display-engine: fb0: sun4i-drmdrmfb frame buffer device [ 12.036141] asoc-simple-card soc:sound_hdmi: i2s-hifi <-> 1c22800.i2s mapping ok [ 19.479538] ------------[ cut here ]------------ [ 19.479672] WARNING: CPU: 0 PID: 474 at drivers/gpu/drm/bridge/analogix/analogix-anx6345.c:531 anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 19.479675] Modules linked in: zstd snd_soc_hdmi_codec dw_hdmi_cec dw_hdmi_i2s_audio zram 8723cs analogix_anx6345 analogix_dp_i2c axp20x_adc axp20x_ac_power axp20x_usb_power axp20x_battery snd_soc_simple_card snd_soc_simple_card_utils snd_soc_spdif_tx sun50i_codec_analog sun8i_adda_pr_regmap cfg80211 lima rfkill sun4i_gpadc_iio gpu_sched industrialio sun8i_codec sun4i_i2s pwm_sun4i snd_soc_simple_amplifier pwm_bl snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer cpufreq_dt snd soundcore pinctrl_axp209 i2c_mv64xxx [ 19.479742] CPU: 0 PID: 474 Comm: kworker/0:2 Not tainted 5.3.9-sunxi64 #19.11.3 [ 19.479744] Hardware name: Pinebook (DT) [ 19.479760] Workqueue: events output_poll_execute [ 19.479767] pstate: 40000005 (nZcv daif -PAN -UAO) [ 19.479774] pc : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 19.479780] lr : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 19.479782] sp : ffff000011163a00 [ 19.479785] x29: ffff000011163a00 x28: 0000000000000001 [ 19.479790] x27: 0000000000000300 x26: ffff000008c42178 [ 19.479795] x25: 00000000fffffffd x24: ffff000010ca43e0 [ 19.479799] x23: ffff000010ef6000 x22: ffff000010e886c8 [ 19.479804] x21: ffff800074b48080 x20: ffff800074b485d0 [ 19.479809] x19: ffff000010e886c8 x18: 00000000fffffff0 [ 19.479814] x17: 0000000000000000 x16: 0000000000010101 [ 19.479818] x15: ffff000010ea2aa8 x14: ffff000010f3f10a [ 19.479823] x13: 00000000000042b8 x12: ffff000010f3e000 [ 19.479828] x11: ffff000010ea2000 x10: ffff000010f3e750 [ 19.479832] x9 : 0000000000000000 x8 : 0000000000000004 [ 19.479837] x7 : 000000000000022b x6 : 0000000000000001 [ 19.479841] x5 : 0000000000000000 x4 : 0000000000000000 [ 19.479845] x3 : 0000000000000000 x2 : 28413e20c265e700 [ 19.479850] x1 : 0000000000000000 x0 : 0000000000000024 [ 19.479855] Call trace: [ 19.479862] anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 19.479869] drm_helper_probe_single_connector_modes+0x190/0x670 [ 19.479876] drm_client_modeset_probe+0x238/0xee8 [ 19.479884] drm_fb_helper_hotplug_event.part.13+0x84/0xc8 [ 19.479889] drm_fbdev_client_hotplug+0x38/0x188 [ 19.479893] drm_client_dev_hotplug+0x70/0xb8 [ 19.479898] drm_kms_helper_hotplug_event+0x30/0x40 [ 19.479903] output_poll_execute+0x198/0x1e0 [ 19.479913] process_one_work+0x1ec/0x370 [ 19.479918] worker_thread+0x4c/0x4f8 [ 19.479923] kthread+0x120/0x128 [ 19.479930] ret_from_fork+0x10/0x18 [ 19.479934] ---[ end trace d810ecbc95ab5c05 ]--- [ 33.765167] vcc3v3: disabling [ 74.826296] ------------[ cut here ]------------ [ 74.826415] WARNING: CPU: 2 PID: 1768 at drivers/gpu/drm/bridge/analogix/analogix-anx6345.c:531 anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.826418] Modules linked in: zstd snd_soc_hdmi_codec dw_hdmi_cec dw_hdmi_i2s_audio zram 8723cs analogix_anx6345 analogix_dp_i2c axp20x_adc axp20x_ac_power axp20x_usb_power axp20x_battery snd_soc_simple_card snd_soc_simple_card_utils snd_soc_spdif_tx sun50i_codec_analog sun8i_adda_pr_regmap cfg80211 lima rfkill sun4i_gpadc_iio gpu_sched industrialio sun8i_codec sun4i_i2s pwm_sun4i snd_soc_simple_amplifier pwm_bl snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer cpufreq_dt snd soundcore pinctrl_axp209 i2c_mv64xxx [ 74.826486] CPU: 2 PID: 1768 Comm: Xorg Tainted: G W 5.3.9-sunxi64 #19.11.3 [ 74.826488] Hardware name: Pinebook (DT) [ 74.826494] pstate: 40000005 (nZcv daif -PAN -UAO) [ 74.826501] pc : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.826506] lr : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.826509] sp : ffff000012ad3a40 [ 74.826511] x29: ffff000012ad3a40 x28: 0000000000000001 [ 74.826516] x27: 0000000000002000 x26: ffff000008c42178 [ 74.826521] x25: 00000000fffffffd x24: ffff000010ca43e0 [ 74.826526] x23: ffff000010ef6000 x22: ffff000010e886c8 [ 74.826530] x21: ffff800074b48080 x20: ffff800074b485d0 [ 74.826535] x19: ffff000010e886c8 x18: 00000000fffffff0 [ 74.826540] x17: 0000000000000000 x16: 0000000000000000 [ 74.826545] x15: ffff000010ea2aa8 x14: ffff000010f3f10a [ 74.826549] x13: 0000000000004d8c x12: ffff000010f3e000 [ 74.826554] x11: ffff000010ea2000 x10: ffff000010f3e750 [ 74.826558] x9 : 0000000000000000 x8 : 0000000000000004 [ 74.826563] x7 : 0000000000000253 x6 : 0000000000000001 [ 74.826567] x5 : 0000000000000000 x4 : 0000000000000000 [ 74.826571] x3 : 0000000000000000 x2 : 28413e20c265e700 [ 74.826576] x1 : 0000000000000000 x0 : 0000000000000024 [ 74.826581] Call trace: [ 74.826588] anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.826602] drm_helper_probe_single_connector_modes+0x190/0x670 [ 74.826611] drm_mode_getconnector+0x2a8/0x428 [ 74.826619] drm_ioctl_kernel+0xbc/0x108 [ 74.826624] drm_ioctl+0x22c/0x3d0 [ 74.826632] do_vfs_ioctl+0xb8/0x8b0 [ 74.826637] ksys_ioctl+0x78/0xa8 [ 74.826641] __arm64_sys_ioctl+0x1c/0x28 [ 74.826650] el0_svc_common.constprop.0+0x88/0x150 [ 74.826655] el0_svc_handler+0x20/0x80 [ 74.826660] el0_svc+0x8/0xc [ 74.826663] ---[ end trace d810ecbc95ab5c06 ]--- [ 74.831375] ------------[ cut here ]------------ [ 74.831496] WARNING: CPU: 2 PID: 1768 at drivers/gpu/drm/bridge/analogix/analogix-anx6345.c:531 anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.831499] Modules linked in: zstd snd_soc_hdmi_codec dw_hdmi_cec dw_hdmi_i2s_audio zram 8723cs analogix_anx6345 analogix_dp_i2c axp20x_adc axp20x_ac_power axp20x_usb_power axp20x_battery snd_soc_simple_card snd_soc_simple_card_utils snd_soc_spdif_tx sun50i_codec_analog sun8i_adda_pr_regmap cfg80211 lima rfkill sun4i_gpadc_iio gpu_sched industrialio sun8i_codec sun4i_i2s pwm_sun4i snd_soc_simple_amplifier pwm_bl snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer cpufreq_dt snd soundcore pinctrl_axp209 i2c_mv64xxx [ 74.831567] CPU: 2 PID: 1768 Comm: Xorg Tainted: G W 5.3.9-sunxi64 #19.11.3 [ 74.831569] Hardware name: Pinebook (DT) [ 74.831575] pstate: 40000005 (nZcv daif -PAN -UAO) [ 74.831580] pc : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.831586] lr : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.831588] sp : ffff000012ad3a40 [ 74.831591] x29: ffff000012ad3a40 x28: 0000000000000001 [ 74.831596] x27: 0000000000002000 x26: ffff000008c42178 [ 74.831601] x25: 00000000fffffffd x24: ffff000010ca43e0 [ 74.831605] x23: ffff000010ef6000 x22: ffff000010e886c8 [ 74.831610] x21: ffff800074b48080 x20: ffff800074b485d0 [ 74.831618] x19: ffff000010e886c8 x18: 00000000fffffff0 [ 74.831623] x17: 0000000000000000 x16: 0000000000000000 [ 74.831627] x15: ffff000010ea2aa8 x14: ffff000010f3f10a [ 74.831632] x13: 00000000000057b4 x12: ffff000010f3e000 [ 74.831637] x11: ffff000010ea2000 x10: ffff000010f3e750 [ 74.831641] x9 : 0000000000000000 x8 : 0000000000000004 [ 74.831646] x7 : 0000000000000278 x6 : 0000000000000001 [ 74.831650] x5 : 0000000000000000 x4 : 0000000000000000 [ 74.831655] x3 : 0000000000000000 x2 : 28413e20c265e700 [ 74.831659] x1 : 0000000000000000 x0 : 0000000000000024 [ 74.831664] Call trace: [ 74.831671] anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 74.831686] drm_helper_probe_single_connector_modes+0x190/0x670 [ 74.831694] drm_mode_getconnector+0x2a8/0x428 [ 74.831703] drm_ioctl_kernel+0xbc/0x108 [ 74.831708] drm_ioctl+0x22c/0x3d0 [ 74.831716] do_vfs_ioctl+0xb8/0x8b0 [ 74.831720] ksys_ioctl+0x78/0xa8 [ 74.831724] __arm64_sys_ioctl+0x1c/0x28 [ 74.831736] el0_svc_common.constprop.0+0x88/0x150 [ 74.831741] el0_svc_handler+0x20/0x80 [ 74.831746] el0_svc+0x8/0xc [ 74.831750] ---[ end trace d810ecbc95ab5c07 ]--- [ 79.631807] ------------[ cut here ]------------ [ 79.631988] WARNING: CPU: 0 PID: 1768 at drivers/gpu/drm/bridge/analogix/analogix-anx6345.c:531 anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 79.631993] Modules linked in: zstd snd_soc_hdmi_codec dw_hdmi_cec dw_hdmi_i2s_audio zram 8723cs analogix_anx6345 analogix_dp_i2c axp20x_adc axp20x_ac_power axp20x_usb_power axp20x_battery snd_soc_simple_card snd_soc_simple_card_utils snd_soc_spdif_tx sun50i_codec_analog sun8i_adda_pr_regmap cfg80211 lima rfkill sun4i_gpadc_iio gpu_sched industrialio sun8i_codec sun4i_i2s pwm_sun4i snd_soc_simple_amplifier pwm_bl snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer cpufreq_dt snd soundcore pinctrl_axp209 i2c_mv64xxx [ 79.632066] CPU: 0 PID: 1768 Comm: Xorg Tainted: G W 5.3.9-sunxi64 #19.11.3 [ 79.632068] Hardware name: Pinebook (DT) [ 79.632074] pstate: 40000005 (nZcv daif -PAN -UAO) [ 79.632081] pc : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 79.632086] lr : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 79.632089] sp : ffff000012ad3a40 [ 79.632091] x29: ffff000012ad3a40 x28: 0000000000000001 [ 79.632096] x27: 0000000000002000 x26: ffff000008c42178 [ 79.632101] x25: 00000000fffffffd x24: ffff000010ca43e0 [ 79.632106] x23: ffff000010ef6000 x22: ffff000010e886c8 [ 79.632111] x21: ffff800074b48080 x20: ffff800074b485d0 [ 79.632115] x19: ffff000010e886c8 x18: 00000000fffffff0 [ 79.632120] x17: 0000000000000000 x16: 0000000000000000 [ 79.632125] x15: ffff000010ea2aa8 x14: ffff000010f3f10a [ 79.632130] x13: 00000000000061f8 x12: ffff000010f3e000 [ 79.632135] x11: ffff000010ea2000 x10: ffff000010f3e750 [ 79.632139] x9 : 0000000000000000 x8 : 0000000000000004 [ 79.632144] x7 : 000000000000029d x6 : 0000000000000001 [ 79.632148] x5 : 0000000000000000 x4 : 0000000000000000 [ 79.632152] x3 : 0000000000000000 x2 : 28413e20c265e700 [ 79.632157] x1 : 0000000000000000 x0 : 0000000000000024 [ 79.632162] Call trace: [ 79.632169] anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 79.632187] drm_helper_probe_single_connector_modes+0x190/0x670 [ 79.632197] drm_mode_getconnector+0x2a8/0x428 [ 79.632208] drm_ioctl_kernel+0xbc/0x108 [ 79.632213] drm_ioctl+0x22c/0x3d0 [ 79.632221] do_vfs_ioctl+0xb8/0x8b0 [ 79.632226] ksys_ioctl+0x78/0xa8 [ 79.632230] __arm64_sys_ioctl+0x1c/0x28 [ 79.632241] el0_svc_common.constprop.0+0x88/0x150 [ 79.632246] el0_svc_handler+0x20/0x80 [ 79.632252] el0_svc+0x8/0xc [ 79.632256] ---[ end trace d810ecbc95ab5c08 ]--- [ 80.691657] fuse: init (API version 7.31) [ 85.456411] ------------[ cut here ]------------ [ 85.456566] WARNING: CPU: 0 PID: 1768 at drivers/gpu/drm/bridge/analogix/analogix-anx6345.c:531 anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 85.456570] Modules linked in: fuse zstd snd_soc_hdmi_codec dw_hdmi_cec dw_hdmi_i2s_audio zram 8723cs analogix_anx6345 analogix_dp_i2c axp20x_adc axp20x_ac_power axp20x_usb_power axp20x_battery snd_soc_simple_card snd_soc_simple_card_utils snd_soc_spdif_tx sun50i_codec_analog sun8i_adda_pr_regmap cfg80211 lima rfkill sun4i_gpadc_iio gpu_sched industrialio sun8i_codec sun4i_i2s pwm_sun4i snd_soc_simple_amplifier pwm_bl snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer cpufreq_dt snd soundcore pinctrl_axp209 i2c_mv64xxx [ 85.456640] CPU: 0 PID: 1768 Comm: Xorg Tainted: G W 5.3.9-sunxi64 #19.11.3 [ 85.456643] Hardware name: Pinebook (DT) [ 85.456648] pstate: 40000005 (nZcv daif -PAN -UAO) [ 85.456655] pc : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 85.456660] lr : anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 85.456663] sp : ffff000012ad3a40 [ 85.456665] x29: ffff000012ad3a40 x28: 0000000000000001 [ 85.456670] x27: 0000000000002000 x26: ffff000008c42178 [ 85.456675] x25: 00000000fffffffd x24: ffff000010ca43e0 [ 85.456680] x23: ffff000010ef6000 x22: ffff000010e886c8 [ 85.456684] x21: ffff800074b48080 x20: ffff800074b485d0 [ 85.456689] x19: ffff000010e886c8 x18: 00000000fffffff0 [ 85.456694] x17: 0000000000000000 x16: 0000000000000000 [ 85.456699] x15: ffff000010ea2aa8 x14: ffff000010f3f10a [ 85.456703] x13: 0000000000006c54 x12: ffff000010f3e000 [ 85.456708] x11: ffff000010ea2000 x10: ffff000010f3e750 [ 85.456713] x9 : 0000000000000000 x8 : 0000000000000004 [ 85.456717] x7 : 00000000000002c3 x6 : 0000000000000001 [ 85.456723] x5 : 0000000000000000 x4 : 0000000000000000 [ 85.456727] x3 : 0000000000000000 x2 : 28413e20c265e700 [ 85.456731] x1 : 0000000000000000 x0 : 0000000000000024 [ 85.456736] Call trace: [ 85.456743] anx6345_get_modes+0x1c8/0x1d8 [analogix_anx6345] [ 85.456760] drm_helper_probe_single_connector_modes+0x190/0x670 [ 85.456769] drm_mode_getconnector+0x2a8/0x428 [ 85.456779] drm_ioctl_kernel+0xbc/0x108 [ 85.456784] drm_ioctl+0x22c/0x3d0 [ 85.456792] do_vfs_ioctl+0xb8/0x8b0 [ 85.456796] ksys_ioctl+0x78/0xa8 [ 85.456801] __arm64_sys_ioctl+0x1c/0x28 [ 85.456812] el0_svc_common.constprop.0+0x88/0x150 [ 85.456817] el0_svc_handler+0x20/0x80 [ 85.456822] el0_svc+0x8/0xc [ 85.456827] ---[ end trace d810ecbc95ab5c09 ]--- I found a BSD patch that provided a clue: that the early panels had no EDID and that it could be provided manually: https://wiki.netbsd.org/users/youri/pinebook-bugs/ So, I wrote the EDID struct from the patch to a file and found a forum post that explained how to manually provide it: https://forum.armbian.com/topic/9714-edid-firmware-for-800x480-lcd-loading-failed/ logo=disabled console=both edid=0 disp_mode=800x480 extraargs=drm.edid_firmware=edid/800x480.bin It seems that I need to provide a disp_mode too and disable EDID probing. Even then, only some boots seem to work, others just fail in the same way: a blank grey screen. Behaviour seems inconsistent: only once, the entire u-boot log was displayed on the pinebook screen (I'd love to know how to get u-boot to do this every time) occasionally (maybe about 1/4 of boots) the kernel log will display on the pinebook screen and then lightdm displays. most boots just result in a blank grey screen I have tried with the 19.11.4 nightly too, with the same results.

Yesterday my 14" Pinebook arrived so I thought I'll collect some already available information. A lot of work still has to be done to get a decent laptop experience with this hardware so this is neither a review nor a stupid Un-Review but just a preview instead. To get the idea about dimensions I added a 13" and a 15" laptop to the picture. Pinebook is wedge-shaped and thickness matches both the 2011 15" MacBook Pro and the 13" from 2015: Display size closely matches the 13" MacBook Pro (but of course pixel density / resolution don't match as well as quality: TN vs. IPS and coating -- it should be obvious if you've the 'you get what you pay for' principle in mind but I'm sure we'll see reviews somewhere else where people are comparing Pinebook with Chrome/MacBooks and think they would get the same display quality for a fraction of costs) Last hardware detail: heat dissipation. I've been curious how well the Pinebook's thermal design is and it looks pretty good. This is the moronic sysbench pseudo benchmark calculating prime numbers endlessly and the Pinebook sitting on a pillow to prevent airflow below the case bottom. Throttling settings are rather conservative with 65°C defined as first trip point and only after a couple of minutes the internal A64 SoC temperature reached this value and slight throttling occured (1.15 GHz down to 1.1 GHz, that's a 'difference' you won't be able to notice). So it seems the combination of a thermal pad with a large metal plate inside the case is rather sufficient: What you see here is a graph drawn by RPi-Monitor, one of my favourite tools to get a clue what's going on with ARM devices (since it's not a heavy monitoring tool that changes the way the OS behaves but it's pretty lightweight sp you can run it in the background and let it monitor/record stuff like cpufreq scaling, consumption and so on). Pinebook currently ships with a rather clean Ubuntu Xenial on the eMMC with Mate desktop environment based on latest BSP u-boot and kernel. To get RPi-Monitor installed on this Ubuntu @pfeerickprovides a script (please follow progress over there). When I played around with Wi-Fi I noticed that Wi-Fi powermanagement seems to be enabled (makes working via SSH close to impossible) and that MAC address changes on every reboot. To disable Wi-Fi powermanagement I simply used the Armbian way: root@pinebook:~# cat /etc/NetworkManager/dispatcher.d/99disable-power-management #!/bin/sh case "$2" in up) /sbin/iwconfig $1 power off || true ;; down) /sbin/iwconfig $1 power on || true ;; esac Unless Wi-Fi driver gets a fix to use a MAC address based on the SoC's individual so called SID one way to assign a fixed MAC address for the Wi-Fi is to add a wifi.cloned-mac-address property to all NetworkManager profiles after establishing a Wi-Fi connection first: nmcli con show | grep wlan | while read ; do set ${REPLY}; nmcli con modify "$1" wifi.cloned-mac-address $(cat /sys/class/net/$4/address); done (I'm pretty sure some masochistic people prefer fiddling around in /etc/network/interfaces instead so if you're not using your laptop as a laptop being carried around and seeing a lot of Wi-Fis you can also use the usual tweaks for the interfaces file. Please also note that using a random MAC address can be considered a privacy feature on laptops since it makes tracking of you in public environments harder). While watching the Pinebook's charging/discharging behaviour I noticed that consumption drawn from wall while charging oscillates between 9W and 15W while being used and display active so it's really great that Pine Inc fixed Pine64's design flaw N° 1: Pinebook is NOT equipped with shitty Micro USB for DC-IN leading to all sorts of trouble but just like SoPine baseboard now uses a 3.5mm/1.35mm barrel jack combined with a 5V/3A PSU (for other hardware details please refer to linux-sunxi wiki page). Battery status (health, capacity, voltage and so on) is already available through sysfs but some values are wrong or need calibration. This needs to be fixed with further upgrades. Also interesting: charging seems to be under control of the ARISC core inside A64 SoC and works together with Pinebook's AXP803 PMIC (powermanagement IC) even when there's no OS running. This will be somewhat challenging to implement later with mainline I would believe... I'll stop here for now since Pinebook is still stuff for developers and not end users. Just some resources for interested parties: https://github.com/ayufan-pine64/boot-tools (Kamil implemented an u-boot based approach to flash directly to eMMC and there you find the necessary BLOBs to convert other BSP based Pine64 images for Pinebook since different DRAM and other settings require different SPL+u-boot) https://github.com/ayufan-pine64/linux-pine64 (based on longsleep's BSP kernel but with more fixes currently for Pinebook) $mainline resources (I lost track where to find most recent stuff but will add this later) Wrt Armbian running on Pinebook we could now simply exchange u-boot+SPL+DT of our Xenial Desktop image... but I hope we won't do that but wait until dust has settled while helping with development efforts in the meantime. In other words: no Armbian on Pinebook (right) now

It is possible to drag backlight control slider to far left position and this completely dims the screen's backlight. This might cause a lot of trouble, if backlight levels get saved by systemd service, as it will persist across reboots and will require you to shine a flashlight on a screen to actually see something and turn backlight back on.

Hello! I'm using Armbian Stretch for 1080P Pinebook A64. I've installed Armbian Stretch about 2 months ago, when it was still "Unsupported" and in-development. Now, however, it's supported. Currently, I'm on Armbian Stretch 5.60 and dev branch. I would like to update to 5.69 and next branch. However, from armbian-config, I'm only able to go from stable to nightly build (5.68, but still dev branch). Moreover, I can't select next kernel from Other menu. Is there a way to switch branches (barring re-flashing from latest image)?

Armbian Legacy 5.56 Kernel 3.10 boots and installs to the eMMC (as long as ext2fs is picked). Armbian Dev 5.56 Kernel 4.19 does not boot from the SD Card at all (power LED and black screen). I don't have the serial console adapter (yet) so I don't know if there is something useful there.

Hi, just a quick sanity check - is install to eMMC on pinebook known to be working (with recent Armbian images from the wip section), and is nand-sata-install the right way to do it? It just occurred to me that I might be spinning my wheels trying to figure out something that just isn't ready yet Thanks, James

Some of the functions keys on my Pinebook like volume up, down and mute doesn't work. Any clues on that? Thank you in advance.

i'm trying to make suspend on lid close work. i saw in this thread that some people are aware that there's a problem. i'd prefer to achieve this from within xfce4-power-manager. here's the thing: 1. using the normal xfce desktop * for "when laptop lid is closed", only 'lock screen' and 'switch off diplay' are available * "System sleep mode" is completely grayed out, as well as security 'lock screen when system is going to sleep' * the 'Ask' option is available only for "Buttons". Choosing it, then choosing "Suspend" from the dialog, causes the ui to hang (desktop darkened), but after a minute i can 'escape' out of it. * 'systemctl suspend' suspends as expected (without locking the screen) 2. using plain openbox without display manager (i.e. console login & startx instead of nodm) or desktop environment, xfce4-power-manager autostarted * for "when laptop lid is closed", 'lock screen', 'switch off diplay', 'suspend' and 'hibernate' are available, but only the first 2 work * "System sleep mode" gives me a choice between 'suspend' and 'hibernate' - only suspend works (!) as expected. * security 'lock screen when system is going to sleep' is not greyed out, and un/checking it works as advertised * the 'Ask' option is available only for "Buttons". It does nothing. * 'systemctl suspend' suspends as expected (without locking the screen) in other words, choice nr. 2. works in all aspects except the lid switch! i tried to let systemd handle the lid switch - to no avail. i also tried to not use xfce4-power-manager at all, only systemd - to no avail. reading `man logind.conf` i notice this: Interesting... 'udevadm monitor' showed nothing for opening/closing the lid. dmesg showed this: hall: (D) hall_isr hall: (I) HALL_CLOSE hall: (D) hall_isr hall: (I) HALL_OPEN every time i open/close the lid... so, where exactly would i have to add this "power-switch" udev tag? phew, my head swims... any ideas? maybe a secret solution already exists?

Hello, recently got a pinebook. I have a strong Linux-on-PC-user background (running ArchLinux on my desktop & older netbook, and debian oldstable on my home server laptop), but not really a developer background and no experience with single board computers at all! Ubuntu Mate is happily chugging along right now, but video playback (h264 packed in .mkv) is abysmal to non-existent. I have tried these releases; the stable 0.6.2 first: AFAICS, it uses a frambuffer driver (fbturbo) under Xorg. video playback was more than choppy, and the UX drops to zero because the video window can't be resized and sticks to the screen, always on top across all desktops. I upgraded to 0.7.8 and ran the scripts according to the rather sparse instructions (and I haven't found better instructions): Now video playback is non-existent! But according to the glmark2-es2 benchmarking utility i get 100points. hm. i think i read on pine64 forums that the drivers responsible provide only a subset of opengl v2.0, and that subset has nothing to do with video playback. True? Some additional info in this post. My questions: Is video playback possible at all? The answers i see on pine64 forums range from "With these mplayer settings it works" or "It is OK; not perfect but usable." to "It is what it is because the driver is closed source and nothing to do" ... I get the impression there's some self-delusion in this (who'd want to admit that getting a pinebook was a mistake)... About the pinebook Linux releases: Why a (the same?) 3.10 kernel in all pine64 releases? Is an alternative OS available and will it bring improvement? Can I install any pine64 OS, or does it have to be a binebook release (I am quite capable of setting up my own desktop, but I'm not sure how deep the differences between pine64 and pinebook run)? About armbian for pine64: A Xenial stable release is on offer. why xenial? the name "armbian" suggests debian, not ubuntu? Thanks for reading. PS: I am aware that there's 2 stickies that relate to my questions; if the information I'm asking for is buried in them, I apologize and will accept any pointers given.