Hi, this is a question about Kernel 4.19 and Analog Audio Jack Output on Pine64 Original (old) board.

For the Kernel 3.10, I've found a thread stating that the following modules can make the Audio Jack works:
https://forum.pine64.org/showthread.php?tid=807

[ modules - Kernel 3.10 ]
sunxi_codec
sunxi_i2s
sunxi_sndcodec

I am trying Armbiam with Kernel 4.19 and want to ask what are the modules that I need to have in order to make the Analog Audio Jack work?

The following are the default modules for current Armbiam (5.70):
[ lsmod - Armbiam 5.70, Kernel 4.19 ]
Module                  Size  Used by
fuse                   94208  3
overlay                90112  1
zstd                   16384  4
sun50i_codec_analog    24576  1
snd_soc_simple_card    16384  3
snd_soc_hdmi_codec     16384  1
snd_soc_spdif_tx       16384  0
sun8i_adda_pr_regmap    16384  1 sun50i_codec_analog
sun4i_i2s              24576  4
snd_soc_simple_card_utils    16384  1 snd_soc_simple_card
sun8i_codec            24576  1
axp20x_ac_power        16384  0
axp20x_battery         16384  0
snd_soc_core          126976  7 sun4i_i2s,snd_soc_spdif_tx,snd_soc_hdmi_codec,sun50i_codec_analog,sun8i_codec,snd_soc_simple_card_utils,snd_soc_simple_card
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_pcm                90112  5 sun4i_i2s,snd_soc_hdmi_codec,sun8i_codec,snd_soc_core,snd_pcm_dmaengine
axp20x_adc             20480  0
snd_timer              32768  1 snd_pcm
sun4i_gpadc_iio        24576  0
snd                    57344  10 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm
soundcore              16384  1 snd
industrialio           53248  4 axp20x_battery,sun4i_gpadc_iio,axp20x_ac_power,axp20x_adc
cpufreq_dt             16384  0
thermal_sys            65536  2 cpufreq_dt,sun4i_gpadc_iio
ip6t_REJECT            16384  1
zram                   24576  5
nf_reject_ipv6         16384  1 ip6t_REJECT
nf_log_ipv6            16384  6
xt_hl                  16384  22
ip6t_rt                16384  3
ipt_REJECT             16384  1
nf_reject_ipv4         16384  1 ipt_REJECT
nf_log_ipv4            16384  6
nf_log_common          16384  2 nf_log_ipv4,nf_log_ipv6
xt_LOG                 16384  12
xt_multiport           16384  2
xt_limit               16384  15
xt_addrtype            16384  4
xt_conntrack           16384  12
ip6table_filter        16384  1
ip6_tables             28672  53 ip6table_filter
nf_conntrack_netbios_ns    16384  0
nf_conntrack_broadcast    16384  1 nf_conntrack_netbios_ns
nf_nat_ftp             16384  0
nf_nat                 28672  1 nf_nat_ftp
nf_conntrack_ftp       16384  1 nf_nat_ftp
nf_conntrack          110592  6 xt_conntrack,nf_nat,nf_nat_ftp,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ftp
nf_defrag_ipv6         20480  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
iptable_filter         16384  1
pinctrl_axp209         16384  0
lima                   49152  0
dw_hdmi_cec            16384  0
dw_hdmi_i2s_audio      16384  0
gpu_sched              20480  1 lima
ttm                    86016  1 lima
realtek                20480  1

I have tested with a 3 connectors headphone and also with a 4 connector headset... both fail...

Also, when I plug a USB to Audio (CM108) Adapter, everything works fine, so, the issue seems to be around the Audio Jack itself...

Does anybody have the Audio Jack working with Kernel 4.19 (Armbian)?
If so, what are the procedures/setup that works?

Basically, I just want audio output from the Jack, mic input, in my case is not needed...

Thanks all,
Valter Fukuoka

Hi All,

I got a rock64 (4G) thinking it would be an upgrade to my raspberry pi 2 B v1.1 . However I was surprised to discover that it performed worse than my pi.

My experience so far has been:

With raspberry pi:
- install rasbpian
- install ubeify (a wrapper around omxplayer) to use the pi as a media player. the gui kinda sucks but it can handle 1080p no sweat and works well with my 4k tv
- firefox / iceweasel is slow and can't be used for youtube.

The pi was easy to setup. There were literally no extra steps other than flashing my sd card with raspbian and running the ubeify install script.

With rock64
- wanted to do a custom install of debian (thought this was possible) but couldn't because bios wouldn't show up on hdmi without an os
- installed armbian image on to my sd card (debian 9)
- firefox behaves not much better than raspberry pi. youtube incredibly and not usable
- video incredibly choppy with vlc
- attempted to use ubeify (omxplayer) and performance much worse than my pi. Video stutters and stalls.


What gives? I thought the rock64 was a more powerful computer and could do what my pi did but better (i.e. so I could use firefox and vlc on it no sweat).
Also the rock64 runs hot too. The aluminum case feels warm vs the pi which seems to manage power better.

Thoughts? Suggestions? I know I'm not the first to attempt this, but finding information on how to get a lightweight computer for multimedia purposes hasn't given many useful results to me.

-ekg

Batocera - a retro-gaming distro - has now been released for the RockPro64.

You can download it here.

More information about Batocera can be found on their website and wiki.
Many thanks to the devs!

Hi there, 

First post in as I'm discovering the world of SoC / SBC and would like to get a RockPro64. I enjoyed reading some of the post around here over the past week as many are very informative!

I was wondering if the Nas case offered for the rockPro would allow the heatsink of 30mm or if it would not work with the disks in. Would anyone know or have a way to measure from the spec?

Side question also, does anyone know if the cards have a low / high chance of having issues? Can we find he failure rate, faulty board %. I guess not but it would be handy to be prepared to the appropriate risk!

Thank for anyone answering here!
Slam.

Hello Everyone, I am looking to have a linux server edition. Anyone did get any edition working?
Please help!

My Pine A64 doesn´t boot up  
Only the red LED near the power Jack blinking but nothing else
I use a 5V 2amp powersupply, can anybody help me?

   

M.

Hi,
Can anyone tell me if there will be support for camera on linux platform? 
I am using Ubuntu18 image on my rockpro64.
Thanks.

I had a problem compiling the rock64 kernel（https://github.com/rock64-linux?tab=repositories），
Buiding kernel and u-boot image: build/mk-kernel.sh rk3328-rock64（build/mk-uboot.sh rk3328-rock64） 
The current uboot partial compilation is OK。


 Building kernel for rk3328-rock64 board! 
 Using rockchip_linux_defconfig 
#
# configuration written to .config
#
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CHK     include/generated/timeconst.h
  CHK     include/generated/bounds.h
  CHK     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
make[1]: 'include/generated/vdso-offsets.h' is up to date.
  CHK     include/generated/compile.h
  CC      arch/arm64/kernel/topology.o
  CC      block/elevator.o
  CC      crypto/ablk_helper.o
arch/arm64/kernel/topology.c: In function ‘parse_cluster’:
arch/arm64/kernel/topology.c:133:40: warning: ‘%d’ directive output may be truncated writing between 1 and 10 bytes into a region of size 3 [-Wformat-truncation=]
error, forbidden warning: topology.c:133
scripts/Makefile.build:258: recipe for target 'arch/arm64/kernel/topology.o' failed
make[1]: *** [arch/arm64/kernel/topology.o] Error 1
Makefile:983: recipe for target 'arch/arm64/kernel' failed
make: *** [arch/arm64/kernel] Error 2
make: *** Waiting for unfinished jobs....
  GZIP    kernel/config_data.gz
  CC      kernel/relay.o
crypto/ablk_helper.c: In function ‘ablk_init’:
crypto/ablk_helper.c:144:49: warning: ‘%s’ directive output may be truncated writing up to 63 bytes into a region of size 55 [-Wformat-truncation=]
error, forbidden warning: ablk_helper.c:144
scripts/Makefile.build:258: recipe for target 'crypto/ablk_helper.o' failed
make[1]: *** [crypto/ablk_helper.o] Error 1
Makefile:983: recipe for target 'crypto' failed
make: *** [crypto] Error 2
  CC      drivers/cpufreq/rockchip-cpufreq.o
block/elevator.c: In function ‘elv_register’:
block/elevator.c:839:14: warning: ‘snprintf’ output may be truncated before the last format character [-Wformat-truncation=]
error, forbidden warning: elevator.c:839
scripts/Makefile.build:258: recipe for target 'block/elevator.o' failed
make[1]: *** [block/elevator.o] Error 1
Makefile:983: recipe for target 'block' failed
make: *** [block] Error 2
kernel/relay.c: In function ‘relay_create_buf_file’:
kernel/relay.c:420:35: warning: ‘snprintf’ output may be truncated before the last format character [-Wformat-truncation=]
error, forbidden warning: relay.c:420
scripts/Makefile.build:258: recipe for target 'kernel/relay.o' failed
make[1]: *** [kernel/relay.o] Error 1
Makefile:983: recipe for target 'kernel' failed
make: *** [kernel] Error 2
^CTraceback (most recent call last):
  File "./scripts/gcc-wrapper.py", line 102, in <module>
    scripts/Makefile.build:403: recipe for target 'drivers/firmware' failed
scripts/Makefile.modbuiltin:54: recipe for target 'drivers/gpu/arm/mali400/ump' failed

I'm a CS student at the University of Arizona.  I have a $500 budget for educational supplies to kill this semester and decided I wanted to take a dive into cluster computing.  After careful research and deliberation, I decided that the clusterboard would be the best balance of power, price and desk space.  This research was hindered by the fact that I could not find a good step by step guide to setting up a clusterboard.  So I've decided to make my own.  I have a reasonable amount of experience with hardware, software, and networking so (with plenty of chat support) I was able to figure this out.  I'm still in the process of updating this post but the machine is up and running!

--------------
TL;DR

https://www.youtube.com/watch?v=vfFoCpkS_Ho

--------------
Hardware

FROM PINE64 STORE:

Cluterboard
https://www.pine64.org/?product=clusterb...dule-slots

Compute Modules - (7)
https://www.pine64.org/?product=sopine-a64

---Optional extras---

64GB eMMC (for NAS/high speed disk space)
https://www.pine64.org/?product=64gb-emmc

USB eMMC interface (for debugging)
https://www.pine64.org/?product=usb-adap...mmc-module

SOPINE baseboard (backup interface for testing compute modules)
https://www.pine64.org/?product=sopine-h...rd-model-a

USB TTY (allows terminal access through GPIO for debugging)
https://www.pine64.org/?product=padi-serial-console

---FROM AMAZON---

16gb SD Card 10 pack - (3 left over)
https://www.amazon.com/gp/product/B00WUCNGVQ/

80mm fans - (2 x exhaust)
https://www.amazon.com/gp/product/B002QVFN7G/

Fan power adapter - (1 end for 200mm that comes with the case, 2 for the back)
https://www.amazon.com/gp/product/B075NPZ94N/

Case - (This case is oversized but extra space is used for air flow)
https://www.amazon.com/gp/product/B00M2UKGSM/

Heatsinks 8 pack - (3 packs,Each compute module should get a heatsink on CPU, memory and power management unit.  21 total)
https://www.amazon.com/gp/product/B00637X42A/
**WARNING THESE MIGHT NOT COME WITH ADHESIVE**
These pads can replace the missing adhesive
https://www.amazon.com/dp/B074K55CWF/

Power Supply - (12V 12.5A 150W Provides more power than the one from the Pine store for running fans.)
https://www.amazon.com/dp/B01N3ASWZ0/

160w Power Header For board and fans - (splits power to board and fans)
https://www.amazon.com/dp/B07H1M8B1S/

-Extras
- continuous switch from my local electrical supply store
- clear acrylic to block the extra vents and create a wind tunnel.

--------------
Power

There are lots of ways to power the board.  The Pine Store sells a power supply but you'll have to modify your board to power fans.  You can use the ATX port on the board, but you'll need to soldier some pretty large resistors.  If you don't make the special ATX mods, you'll need to use a continuous switch to keep it on.
--------------
Gateway/Management Computer

The internal networking switch on the clusterboard does not provide DHCP.  As an alternative to running on my router, I've decided to build a gateway out of a first edition Pine64 from the kickstarter.  It acts as DHCP, a router allowing the cluster to access the internet via wifi, terminal access to the cluster, and a time/file/dhcp/dns/etc server.  While this is certainly something I recommend doing, how you implement it will depend on what kind of device you use.  In this guide I'll refer to things you need to do but only when dealing with the clusterboard itself will I be providing specific steps.

Ideally, the sopine LTS kit would make the best gateway.  However, the network port on it is only 10/100.  Gigabit is what you need.  Most newer boards have this just make sure to research the specs before you buy.  If you want to go all out, the rockboard pro has a NAS setup that would work nicely.  With any luck, the same linux distro on any Cortex A53 should be able to compile programs and act as part of the cluster but no promises until I can do some more testing.
--------------
Airflow/Cooling

I've added a lot of extra case space and hardware for cooling.  I've been told this is overkill but if you want experience building clusters, you should probably know that cooling takes up a good part of the budget.
--------------
Bench Testing

Before we fully assemble the machine, we're going to do all of the initial setup.  Once we know everything runs, we can put it together and put it to work.
--------------
Prepare the SD cards

https://www.armbian.com/sopine-a64/

The best image (as of this post) is Armbian because of the continuous support.  However, I had to use the 3.10 xenial image (found under "other options") instead of Stretch (Debian) or Bionic (Ubuntu).

https://etcher.io/

The armbian site recommends this software for writing the images to the SD cards.  Feel free to use whatever software you like.  I don't think it matters.
--------------
For each compute module

(Notice the ATX style power switch connection just below the ATX power connector.  Helps when you want to turn it on --


You need to plug each module in one at a time (DO NOT HOT SWAP) and do the following steps:

-Assign it a static IP address from your DHCP server
--find it when it pulls an IP address
--use the MAC address to make the assignment from the DHCP server configuration
--be sure to give it an address outside of the automatic range (ie give them *.10-16 if your DHCP server hands out *.50-100)
--make a list of the static assignments to help later

-Login (ssh client from your gateway or management computer) with root access(if using ARMbian [username: root][pw: 1234])
--complete any first time setup
--this may include generating a user account(you'll probably want to make it's the same username on all of them)
--use "hostnamectl set-hostname [myhostname]" to give each a unique hostname (ie cluster[0-6])
--be sure to shutdown before turning the power off and test the module in the slot you plan to use it.

once each module has been tested, we can move on to testing it as a whole.
--------------
csftp and cssh

These next steps will require special software on the computer you're using to access the cluster.  Linux offers an easy way to connect to all clients at once.  See your distribution's pacman or apt-get information for details on how to install it if it isn't already there.

Alternate Windows software:
https://github.com/dprokscha/cputty

I don't know of an FTP option for windows at this point.  However, if you setup RSA keys, Filezilla will at least make it easy on you.
--------------
RSA keys

The next task involves generating RSA keys so the gateway and compute modules can talk to each other without login authorization.  Linux users can use "ssh-keygen -t rsa".  With default options, that should create two files in "~/.ssh/" named "id_rsa" and "id_rsa.pub".  If you're already using RSA keys, you can direct these files to be generated elsewhere.  Rename "id_rsa.pub" to "authorized_keys".  Then you can SFTP those files in to the "~/" (known as home) folder of the account you would like to use on all the compute modules.  Personally, "sudo" has never saved me from doing anything stupid so I like to live dangerously and use root.

Windows users can generate the keys while logged in to the first node in the cluster or generate "id_rsa"(private) and "authorized_keys"(public) using an online tool like this:
https://qsandbox.com/tools/private-public-keygen

You'll need to configure your ssh/sftp client software to use the keys.
--------------
cssh/csftp clusters file

Users of cssh can create a file "/etc/clusters" that contains a text label that will allow you to tap in to all the compute modules at once just by typing "cssh [label]".
https://linux.die.net/man/1/cssh


I'm sure other clients have a way of doing this.  For now, just make sure you can with whatever software you're using.  Now that we know everything works, time to box it up.
--------------
Disassembling the case



All the sides and the top are only connected by obvious screws.  I also took out and set aside the HDD mounting brackets.  The front can be pulled off gently.  I had to take off the big fan and take apart the mounting plate for the ATX switch to put in the continuous switch.
--------------
Adhesive Thermal Pad/Heatsinks



Because The hearsinks didn't dome with any adhesive the way they're supposed to, I got up close and personal with the exacto knife.  The goal is to have a heatsink on all 3 of the major parts (CPU, memory and power)



Steer clear from the white border or you'll have trouble installing the compute modules.



This is also the point of no return for GPIO headers.  Once the heatsinks are on, they're hard to get at.  Make sure everything is running so you don't need to get at them with the serial interface.




Once they're all set up, sandwich the chips between some bubble wrap and put a softcover book on top for a couple hours / overnight to let the adhesive set.
--------------
Motherboard mounting (or how I learned to stop worrying and love zip ties)



I can't say enough bad things about the mounting holes on this board.  The placement complies with Micro ITX but their size is just a tad smaller than the holes on the case.  Not to mention that one is right up against the ATX molex.  The case came with rubber feet and zip ties so I improvised.  Afterwards, I installed the case fans and routed power.
--------------
Acrylic

I put some clear plastic over most of the vents to create a wind tunnel.  I took a picture but it wasn't very clear.
--------------
Setting up servers

From here, what software you set up will depend greatly on what task you plan to do with it.  The good news is that from here on out, every other guide for setup should be valid.  You have 7 quad core Arm64 processors running a basic setup of Linux that will allow you to do anything any other cluster would do.  (assuming they don't require a different processor architecture)  As a CS student who will be doing parallel programming in the near future, I wanted to setup Open MPI.  I wound up setting up my gateway as a time server and a file server.  I was able to use apt-get to update software on the compute modules and install packages needed to access server functionality.  As long as you can figure out how to apt-get or compile the software you want to run, you should be good to go.
--------------
Open MPI

I used the steps in this guide to get the basics of Open MPI going:
http://mpitutorial.com/tutorials/running...hin-a-lan/

But I made my own version of the "hello world" program:
https://github.com/PhillBenoit/OpenMPI-h...i_sample.c

This is what it looks like when it runs:


--------------
Final thoughts

The board itself has some hardware quirks but the processing power is real.  Setting up a server/gateway solves lots of problems and can offload what would normally be cluster0 tasks.  This build is more challenging on the software side than it is the hardware side.  I wouldn't recommend it for novice linux users / network admins.  That being said, it's not overly difficult if you can manage to work your way around Linux.  If you want to build a small ARM cluster capable of running serious tasks, this is definitely the way to go.  The board itself consolidates what would be a massive amount of space as well as preventing wiring headaches.
--------------
Thank you for reading my post.  If you have any input or suggestions (including information that needs to be updated.), please leave a comment to let me know.