<![CDATA[PINE64 - Archlinux ]]> https://forum.pine64.org/ Sat, 04 Apr 2026 08:44:50 +0000 MyBB <![CDATA[manual install archlinux]]> https://forum.pine64.org/showthread.php?tid=19357 Tue, 23 Jul 2024 19:00:39 +0000 BlackMage]]> https://forum.pine64.org/showthread.php?tid=19357
on a PINE A64]]>
on a PINE A64]]> <![CDATA[eMMC doesn't work after kernel start]]> https://forum.pine64.org/showthread.php?tid=8076 Sun, 13 Oct 2019 21:17:27 +0000 m.bakhterev]]> https://forum.pine64.org/showthread.php?tid=8076
1. I flash three u-boot images, as in tutorial. It seems working, because...

2. When i power up the Rock64, it writes some usuall messages to the UART on the. So, as i understand, u-boot images are being loaded successfully, partition table is being read successfully, so the Linux Kernel starts and writes a lot of info to the UART.

3. But when the kernel attempts to mount root file system, it can't do this and throws me to the emergency shell. Where i try to read from emmc, e.g., using the command
Code:
dd if=/dev/mmcblk1 of=/dev/stdout count=10
i get nothing. When i'm trying to

Code:
hexdump /dev/mmcblk1

i get I/O error.

4. So... What is wrong? It does not looks like as hardware error. Because u-boot somehow figures out the correct PARTUUID for the partition and passes it to the kernel. So, the partition table sectors are readable, but no to the kernel... May be some driver option will help?

Screenlog is here http://k.imm.uran.ru/tmp/screenlog.0

Thanks in advance]]>
1. I flash three u-boot images, as in tutorial. It seems working, because...

2. When i power up the Rock64, it writes some usuall messages to the UART on the. So, as i understand, u-boot images are being loaded successfully, partition table is being read successfully, so the Linux Kernel starts and writes a lot of info to the UART.

3. But when the kernel attempts to mount root file system, it can't do this and throws me to the emergency shell. Where i try to read from emmc, e.g., using the command
Code:
dd if=/dev/mmcblk1 of=/dev/stdout count=10
i get nothing. When i'm trying to

Code:
hexdump /dev/mmcblk1

i get I/O error.

4. So... What is wrong? It does not looks like as hardware error. Because u-boot somehow figures out the correct PARTUUID for the partition and passes it to the kernel. So, the partition table sectors are readable, but no to the kernel... May be some driver option will help?

Screenlog is here http://k.imm.uran.ru/tmp/screenlog.0

Thanks in advance]]> <![CDATA[HDMI does not work]]> https://forum.pine64.org/showthread.php?tid=7551 Fri, 31 May 2019 19:49:39 +0000 baltasarq]]> https://forum.pine64.org/showthread.php?tid=7551

Code:
$ uname -a

Linux pinebook 3.10.105-bsp-1.2-ayufan-1 #1 SMP PREEMPT Wed May 3 12:48:42 MYT 2017 aarch64 aarch64 aarch64 GNU/Linux


The desktop is linux mint.

The problem is, no matter how much I struggle, I'm unable to obtain an image from a project connected to the mini HDMI port. I even installed a package called disper, bit with disper -l it does not recognize any other screen apart from the laptop's monitor itself.

What am I doing wrong?
Thanks in advance,
-- Baltasar]]>

Code:
$ uname -a

Linux pinebook 3.10.105-bsp-1.2-ayufan-1 #1 SMP PREEMPT Wed May 3 12:48:42 MYT 2017 aarch64 aarch64 aarch64 GNU/Linux


The desktop is linux mint.

The problem is, no matter how much I struggle, I'm unable to obtain an image from a project connected to the mini HDMI port. I even installed a package called disper, bit with disper -l it does not recognize any other screen apart from the laptop's monitor itself.

What am I doing wrong?
Thanks in advance,
-- Baltasar]]> <![CDATA[No sound. 20190112 from anarsoul]]> https://forum.pine64.org/showthread.php?tid=7421 Thu, 25 Apr 2019 16:33:48 +0000 cootcraig]]> https://forum.pine64.org/showthread.php?tid=7421 anarsoul's 20190112 image. WiFi is working after doing the suggested NIC hack. However I have not been able to get sound working on either speaker or headphone.
System updates have been run.]]> anarsoul's 20190112 image. WiFi is working after doing the suggested NIC hack. However I have not been able to get sound working on either speaker or headphone.
System updates have been run.]]> <![CDATA[Cannot log in]]> https://forum.pine64.org/showthread.php?tid=7025 Fri, 04 Jan 2019 17:16:08 +0000 dr5mn]]> https://forum.pine64.org/showthread.php?tid=7025
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?]]>
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?]]> <![CDATA[Hopes for Pine64 dashed]]> https://forum.pine64.org/showthread.php?tid=7014 Wed, 02 Jan 2019 08:21:25 +0000 S265]]> https://forum.pine64.org/showthread.php?tid=7014 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]]> 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]]> <![CDATA[Asterisk Phone Software]]> https://forum.pine64.org/showthread.php?tid=7010 Tue, 01 Jan 2019 22:11:35 +0000 S265]]> https://forum.pine64.org/showthread.php?tid=7010 Can anyone comment in why it will not start? ... please refer to attachment. Any helpful advice on using the new Archlinux also appreciated.

.jpg   20190102-v3.jpg (Size: 233.93 KB / Downloads: 643) ]]> Can anyone comment in why it will not start? ... please refer to attachment. Any helpful advice on using the new Archlinux also appreciated.

.jpg   20190102-v3.jpg (Size: 233.93 KB / Downloads: 643) ]]> <![CDATA[Arch Linux mainline XFCE]]> https://forum.pine64.org/showthread.php?tid=5538 Sat, 06 Jan 2018 07:28:15 +0000 pineadmin]]> https://forum.pine64.org/showthread.php?tid=5538 Arch Linux mainline with XFCE GUI [20171225-1] by anarsoul on PINE64 Installer]]> Arch Linux mainline with XFCE GUI [20171225-1] by anarsoul on PINE64 Installer]]> <![CDATA[how about this non-offical archlinux ?]]> https://forum.pine64.org/showthread.php?tid=3275 Sun, 12 Feb 2017 14:12:36 +0000 joe]]> https://forum.pine64.org/showthread.php?tid=3275
https://archlinuxarm.org/forum/viewtopic.php?f=7&t=9644]]>
https://archlinuxarm.org/forum/viewtopic.php?f=7&t=9644]]> <![CDATA[Archlinux VLC]]> https://forum.pine64.org/showthread.php?tid=2007 Sat, 13 Aug 2016 01:00:17 +0000 AUDIOTEK]]> https://forum.pine64.org/showthread.php?tid=2007
How do you install VLC on Archlinux????]]>
How do you install VLC on Archlinux????]]> <![CDATA[No CIFS support in Kernel?]]> https://forum.pine64.org/showthread.php?tid=1538 Mon, 27 Jun 2016 10:45:34 +0000 jamespo]]> https://forum.pine64.org/showthread.php?tid=1538 mount error(19): No such device


[root@alarm autofs]# modprobe cifs
modprobe: FATAL: Module cifs not found in directory /lib/modules/3.10.65-4-pine64-longsleep]]> mount error(19): No such device


[root@alarm autofs]# modprobe cifs
modprobe: FATAL: Module cifs not found in directory /lib/modules/3.10.65-4-pine64-longsleep]]> <![CDATA[Pine64 makes snappy file server]]> https://forum.pine64.org/showthread.php?tid=876 Sun, 01 May 2016 17:30:30 +0000 RaimundEge]]> https://forum.pine64.org/showthread.php?tid=876
I installed/updated the latest longsleep Archlinux system with Xfce4.
Only snafu so far is the Chromium problem reported in this forum.

My goal is to use the pine64 as a file server to my home network.
Installed samba via pacman, configured the smb.conf file and was up and running.

With the help of the friendly folks at altdrive.com I was able to install
the altdrive Java-based backup service, including its GUI client.

I will give this setup a little time to settle, and then will swap out my old trusty i386-based server.]]>
I installed/updated the latest longsleep Archlinux system with Xfce4.
Only snafu so far is the Chromium problem reported in this forum.

My goal is to use the pine64 as a file server to my home network.
Installed samba via pacman, configured the smb.conf file and was up and running.

With the help of the friendly folks at altdrive.com I was able to install
the altdrive Java-based backup service, including its GUI client.

I will give this setup a little time to settle, and then will swap out my old trusty i386-based server.]]> <![CDATA[Arch Killing long running node/npm processes before finishing]]> https://forum.pine64.org/showthread.php?tid=823 Thu, 28 Apr 2016 16:14:33 +0000 faddah]]> https://forum.pine64.org/showthread.php?tid=823 hello all,
when i run certian longer processes in node.js/npm, like an update ($ npm update -g) or to search for an npm package ($ npm search elm), it starts the process on my Pine64 A64+ w/ 2 GB board, but then half- or even three-quarters of the way through, it just kills the process before it completes; particularly, i noticed, when it's waiting for info to come back across the 'net through the ethernet port, with —

Killed

then it just gives me the command prompt again, process never completes. this happens no matter how many times i re-try it.

is there anyway to change a setting, somewhere, that will extend the amount of time before these processes are killed? any help would be much appreciated, please. thank you and advance. 

best,

—  faddah
     portland, oregon, u.s.a.
]]> hello all,
when i run certian longer processes in node.js/npm, like an update ($ npm update -g) or to search for an npm package ($ npm search elm), it starts the process on my Pine64 A64+ w/ 2 GB board, but then half- or even three-quarters of the way through, it just kills the process before it completes; particularly, i noticed, when it's waiting for info to come back across the 'net through the ethernet port, with —

Killed

then it just gives me the command prompt again, process never completes. this happens no matter how many times i re-try it.

is there anyway to change a setting, somewhere, that will extend the amount of time before these processes are killed? any help would be much appreciated, please. thank you and advance. 

best,

—  faddah
     portland, oregon, u.s.a.
]]> <![CDATA[using dd to clone image]]> https://forum.pine64.org/showthread.php?tid=810 Thu, 28 Apr 2016 00:29:10 +0000 jproffer]]> https://forum.pine64.org/showthread.php?tid=810
I'm trying to burn arch to a microsd via 
Code:
dd if=arch-pine64-bspkernel-20160403-1.img of=/dev/sdg1 bs=1M

the image burns fine, but once i eject/reinsert the microsd, my OS cannot mount or recognize the FS on the microsd.  Any help?
I run arch linux with XFCE here, and my kernel supports all the common FS's up to ext4fs, reiserfs, and ntfs.]]>
I'm trying to burn arch to a microsd via 
Code:
dd if=arch-pine64-bspkernel-20160403-1.img of=/dev/sdg1 bs=1M

the image burns fine, but once i eject/reinsert the microsd, my OS cannot mount or recognize the FS on the microsd.  Any help?
I run arch linux with XFCE here, and my kernel supports all the common FS's up to ext4fs, reiserfs, and ntfs.]]> <![CDATA[Archlinux up and Running]]> https://forum.pine64.org/showthread.php?tid=802 Wed, 27 Apr 2016 15:43:51 +0000 scnd]]> https://forum.pine64.org/showthread.php?tid=802
I'm still getting everything configured, but so far I've done the following:
Powered on
Set up Wifi
Set up SSH
Pacman Init
chmod & chgrp & chown for /tmp/ and /var/tmp
set up external storage
set up smb
user settings

The thing is nice and fast, seems to work pretty well so far. I only had about an hour to interact with the thing, so i couldn't get through all the things that I wanted, but I think this is a good start.]]>
I'm still getting everything configured, but so far I've done the following:
Powered on
Set up Wifi
Set up SSH
Pacman Init
chmod & chgrp & chown for /tmp/ and /var/tmp
set up external storage
set up smb
user settings

The thing is nice and fast, seems to work pretty well so far. I only had about an hour to interact with the thing, so i couldn't get through all the things that I wanted, but I think this is a good start.]]>