Hi

Just downloaded version 20181104 of the OS from Github and burned it to an SD card.

The board starts up nicely and gets to the login screen, but no matter what I do, it loops back to the login page. I've tried root/root and alarm/alarm, but it just bounces back to the screen where you select the user to log in with.

Am I doing something wrong?

Hi everyone.

About to buy a rock64 to use OMV for a basic NAS.
It will be used only really to serve as a file server for Kodi and general file networking and backups.

My question is will the 1gb ram option be enough? Would there be much differences using 2gb or 4gb options

If you are attending FOSDEM please let me know in this thread  (and PM or emai me your email address) -- we'll be hosting a community evening / drinks night with devs from various projects as well as community members :

I haven't been able to find the arch built against for the Android images. I don't yet own a ROCKPro64, so I can't look for myself.

It would be helpful if this information was specified somewhere.

Are the images built for armeabi-v7a or arm64-v8a?

Just saw these nice cases the other day on twitter and thought its worth sharing on here.

built my new Rockpro64 NAS recently and setup OMV using Ayufan's 0.7.9: ggitlab-ci-linux-build-67 latest stable release.. the system works flawlessly with all my requirements

my question is, if I am to upgrade to the next release (pre release/stable release) should I just run the command as specified by Ayufan on his page as shown below or am I missing something here..

sudo apt-get update -y
sudo apt-get install linux-rock64 -y
sudo apt-get install linux-rockpro64 -y

thanks in advance..

I was wondering if it's possible to stack the acrylic enclosures (https://www.pine64.org/?product=pine64-a...-enclosure) to hold multiple Pine A64s.

From what I see, this might be possible? I suppose I can use the bottom piece repeatedly to mount the individual boards and just use one single top piece at the very top?

Hi all. In the store there's an out-of-stock listing for a spare screen for both Pinebooks.

https://www.pine64.org/?product=pinebook...-in-camera

My questions are:

• Will this be re-stocked with 1080p Pinebook screens?
  
• Will the 1080p screens work on the original (1366x768) release of Pinebooks?
  

I needed the ds1307 real-time clock kernel module, and decided to write a set of instructions on how to do add it (or any other module).

Hopefully this can be helpful for others:

Kernel module compilation.md

Hi all. My recent attempts to find a new use case for the Pine64 have been dashed on my particular hardware. I keep coming up against road blocks.
A recent attempt to Install and run Asterisk on Armbian Stable proved problematic. As posted on the Pine-Armbian sub-forum, I found a Call Trace in the kernel and
had to question its suitability for this task. Now, with a new install of Archlinux with kernel (4.20.0-2-ARCH) I find that problems with the Pine64 persist. Not sure where to go from here. The Pine64 worked fine for Android 6,7 as a media box. Your thoughts ..


......snip

[ 7994.007884] watchdog: BUG: soft lockup - CPU#3 stuck for 21s! [swapper/3:0]
[ 7994.014835] Modules linked in: snd_soc_hdmi_codec rc_cec dw_hdmi_i2s_audio dw_hdmi_cec hid_logitech_hidpp realtek sun8i_drm_hdmi dw_hdmi cec dwmac_sun8i stmmac_platform snd_soc_simple_card stmmac rc_core snd_soc_simple_card_utils mdio_mux hid_logitech_dj axp20x_pek joydev sun4i_drm sun4i_frontend sunxi_wdt sun4i_tcon sun8i_tcon_top sun8i_mixer drm_kms_helper drm drm_panel_orientation_quirks syscopyarea sysfillrect sysimgblt fb_sys_fops nvmem_sunxi_sid
[ 7994.054768] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G             L    4.20.0-2-ARCH #1
[ 7994.062670] Hardware name: Pine64+ (DT)
[ 7994.066501] pstate: 60000005 (nZCv daif -PAN -UAO)
[ 7994.071288] pc : arch_cpu_idle+0x34/0x1b8
[ 7994.075293] lr : arch_cpu_idle+0x30/0x1b8
[ 7994.079295] sp : ffff000009b5bf00
[ 7994.082603] x29: ffff000009b5bf00 x28: 0000000000000000
[ 7994.087908] x27: 0000000000000000 x26: ffff8000775f6c00
[ 7994.093213] x25: 0000000000000000 x24: ffff0000098297b0
[ 7994.098518] x23: ffff00000981a5b8 x22: ffff0000098296c8
[ 7994.103823] x21: ffff000009829780 x20: 0000000000000008
[ 7994.109128] x19: ffff00000980e018 x18: 0000000000000000
[ 7994.114432] x17: 0000000000000000 x16: 0000000000000000
[ 7994.119737] x15: 0000000000000000 x14: 0000000000000000
[ 7994.125041] x13: 0000000000000000 x12: 0000000000000000
[ 7994.130345] x11: 0000000000000000 x10: 00000000000009a0
[ 7994.135649] x9 : ffff000009b5be80 x8 : ffff8000775f7600
[ 7994.140954] x7 : 0000000000000364 x6 : ffff00000dcbbcc0
[ 7994.146259] x5 : ffff800079fc0870 x4 : 00008000707aa000
[ 7994.151565] x3 : 4000000000000000 x2 : 0000000000000000
[ 7994.156870] x1 : ffff00000980e018 x0 : ffff000009b5bf00
[ 7994.162173] Call trace:
[ 7994.164618]  arch_cpu_idle+0x34/0x1b8
[ 7994.168278]  do_idle+0x210/0x288
[ 7994.171504]  cpu_startup_entry+0x2c/0x30
[ 7994.175424]  secondary_start_kernel+0x158/0x168
[ 8004.010819] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 8004.016754] rcu:     3-...!: (0 ticks this GP) idle=c18/0/0x0 softirq=12922/12922 fqs=448
[ 8004.024743] rcu:     (detected by 1, t=72924 jiffies, g=20185, q=45839)
[ 8004.031092] Task dump for CPU 0:
[ 8004.034316] kworker/0:1H    R    0   359      2 0x00000028
[ 8004.039811] Workqueue: kblockd mmc_blk_mq_complete_work
[ 8004.045031] Call trace:
[ 8004.047479]  __switch_to+0x74/0x98
[ 8004.050881]  __schedule+0x288/0x8e8
[ 8004.054365]  schedule+0x30/0x88
[ 8004.057505]  schedule_timeout+0x2dc/0x420
[ 8004.061510]  wait_for_common+0x1c0/0x228
[ 8004.065427]  wait_for_completion+0x28/0x38
[ 8004.069521]  mmc_wait_for_req_done+0x30/0x170
[ 8004.073871]  mmc_wait_for_req+0xb0/0xf0