Armbian for Pine64

[pineadmin]

Updated Armbian (PINE A64(+)) 5.38 on PINE64 Installer. Please visit the Wiki.

[pineadmin]

Updated Armbian (PINE A64(+)) 5.65 on Wiki and PINE64 Installer.

[pineadmin]

Added Armbian Debian Buster Minimal 5.91 on Wiki and PINE64 Installer
Added Armbian Ubuntu Bionic Minimal 5.90 on Wiki and PINE64 Installer
Added Armbian Ubuntu Xenial Deskop 5.90 on Wiki and PINE64 Installer
Updated Armbian Ubuntu Xenial Minimal 5.69 on Wiki and PINE64 Installer

[CVBruce]

Having a learning curve with Pine A64+ and Armbian Buster.

I used SD Card Formater to format using overwrite on a Samsung 64GB card.
I downloaded a fresh copy of Armbian Buster (Armbian_20.02.1_Pine64_buster_current_5.4.20)
I connected the Pine A64+ via Ethernet.
I applied power.
I see activity on the Ethernet connector.
I see DHCP has allocated an address to pine64 (192.168.1.130)
I use ssh to connect to the address. (ssh -p 22 -x -v root@192.168.1.130 )
This is what happens next:
OpenSSH_7.8p1, LibreSSL 2.6.2
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: /etc/ssh/ssh_config line 53: Applying options for *
debug1: Connecting to 192.168.1.130 [192.168.1.130] port 22.
debug1: Connection established.
debug1: identity file /Users/bjskelly/.ssh/id_rsa type -1
debug1: identity file /Users/bjskelly/.ssh/id_rsa-cert type -1
debug1: identity file /Users/bjskelly/.ssh/id_dsa type -1
debug1: identity file /Users/bjskelly/.ssh/id_dsa-cert type -1
debug1: identity file /Users/bjskelly/.ssh/id_ecdsa type -1
debug1: identity file /Users/bjskelly/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/bjskelly/.ssh/id_ed25519 type -1
debug1: identity file /Users/bjskelly/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/bjskelly/.ssh/id_xmss type -1
debug1: identity file /Users/bjskelly/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.8
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9p1 Debian-10+deb10u1
debug1: match: OpenSSH_7.9p1 Debian-10+deb10u1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.130:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:nafm3rJLa1g0cqIZmS4Y0KOSJMyvUgGZrVSULvGi8nE
debug1: Host '192.168.1.130' is known and matches the ECDSA host key.
debug1: Found key in /Users/bjskelly/.ssh/known_hosts:115
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/bjskelly/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/bjskelly/.ssh/id_dsa
debug1: Trying private key: /Users/bjskelly/.ssh/id_ecdsa
debug1: Trying private key: /Users/bjskelly/.ssh/id_ed25519
debug1: Trying private key: /Users/bjskelly/.ssh/id_xmss
debug1: Next authentication method: password
root@192.168.1.130's password:
debug1: Authentication succeeded (password).
Authenticated to 192.168.1.130 ([192.168.1.130]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Requesting authentication agent forwarding.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
packet_write_wait: Connection to 192.168.1.130 port 22: Broken pipe

[Process completed]

Increasing the debugging level gets these additional messages.
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env SSH_AUTH_SOCK
debug3: Ignored env DISPLAY
debug3: Ignored env XPC_SERVICE_NAME
debug3: Ignored env TERM_PROGRAM
debug3: Ignored env TERM_PROGRAM_VERSION
debug3: Ignored env TERM_SESSION_ID
debug3: Ignored env SHELL
debug3: Ignored env HOME
debug3: Ignored env LOGNAME
debug3: Ignored env USER
debug3: Ignored env PATH
debug3: Ignored env __CF_USER_TEXT_ENCODING
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768



As you can see I get past the password, but then the connection eventually times out and closes.

Questions:
1. Is this the right place to ask questions?
2. If it isn't can you direct me to the correct place?
3. As always I've suspected my USB cable isn't delivering enough power (Power supply has been tested under load and is ok.). Is there some cable that will deliver more power? Will adding a lithium battery help?

Thanks in advance for any help you can give me.

Bruce

[CVBruce]

Having a learning curve with Pine A64+ and Armbian Buster.

Questions:
1. Is this the right place to ask questions?
2. If it isn't can you direct me to the correct place?
***3. As always I've suspected my USB cable isn't delivering enough power  (Power supply has been tested under load and is ok.).  Is there some cable that will deliver more power?  Will adding a lithium battery help?

Thanks in advance for any help you can give me.

Bruce

Yes number three is the winner.  Some of the new mobile phones have a quick charging feature.  I figured that the certified cables must be capable of handling more current so I bought a cable and most of my problems have been cured.

[bratoff]

I'm running the latest buster (5.4.28) image downloaded from the Armbian site on a 2gb A64+ with the official WiFi/BT card.  Haven't done much with it before now - i'm an original KS backer.

I can't get bluetooth working - nothing seems to recognize the existence of the bt adapter.  The WiFi works fine so I know the board is installed correctly and the realtek chip's ok.

The bluez package is installed and I get a bt icon in the desktop, but there are no adapters found.  The command line utilities also don't seem to see it.

Anyone know what the trick is to get it working?

[thebrave]

I'm running the latest buster (5.4.28) image downloaded from the Armbian site on a 2gb A64+ with the official WiFi/BT card.  Haven't done much with it before now - i'm an original KS backer.

I can't get bluetooth working - nothing seems to recognize the existence of the bt adapter.  The WiFi works fine so I know the board is installed correctly and the realtek chip's ok.

The bluez package is installed and I get a bt icon in the desktop, but there are no adapters found.  The command line utilities also don't seem to see it.

Anyone know what the trick is to get it working?

Look at the dmesg, out of the box, it complain of missing blobs.

In /lib/firmware/rtl_bt, I needed at least 

• rtl8723bs_fw.bin from https://git.kernel.org/pub/scm/linux/ker...3bs_fw.bin
  
• rtl8723bs_config-pine64.bin from https://github.com/shuhaowu/armbian-buil...n?raw=true
  

[e-minguez]

I sent a PR here https://github.com/armbian/firmware/pull/14 for them to include the bluetooth firmware files out of the box. I guess you just need to use a newer firmware package that includes that file.
I've also wrote this https://gist.github.com/e-minguez/dcf785...5eba3a04c6 to verify it works.
HTH!

[bratoff]

@thebrave @e-minguez
Thanks for getting me much closer! Still apparently not quite there, though. After adding the firmware and config files, I was able to start the bluetooth service and it did also start at reboot, but "hcitool lescan" fails with "device not found". Also tried a device scan from the bt icon on the launcher and it couldn't find any devices, even though several bt devices were in the immediate vicinity. Have I missed something else?

[e-minguez]

@thebrave @e-minguez
Thanks for getting me much closer! Still apparently not quite there, though. After adding the firmware and config files, I was able to start the bluetooth service and it did also start at reboot, but "hcitool lescan" fails with "device not found". Also tried a device scan from the bt icon on the launcher and it couldn't find any devices, even though several bt devices were in the immediate vicinity. Have I missed something else?

You need to install bluez then enable the Bluetooth service as systemctl enable bluetooth --now

Enviado desde mi ONEPLUS A5010 mediante Tapatalk