Hey everyone. 
I am planning on building a (edited "table PC" using the Rock64 (don't have it yet). I have an old monitor from my old laptop for which I bought a controller board and would like to use it somehow. But I would also like to add a touch layer to the LCD. More precisely this resistive touch layer. 

However, I have no idea, if or how is that supported on Rock64, so if anyone can give me an advice if it will even work, or how to make it work, I would greatly appreciate it. 
Thanks, everyone.

I recently received my ROCK64 and installed various flavours of Linux on it. One thing I cannot seem to figure out is how to change the MAC address of ETH0.

On Armbian Bionic I tried putting it in /boot/armbianEnv.txt as etheraddr= or mac_addr=, I tried putting it in /etc/network/interfaces - all to no avail.
On Ayufan I was entirely unable to find anything to configure in this regard.

I read that a bunch of people complained about having ever changing MAC addresses on their board. I have not experienced that problem, but I want to set a specific MAC address - not fix the standard one.

Is there any way to do this? I could also recompile (part of) the DTBs if that is what it takes. I just need to know where I can find this setting (if at all). I can also install a new operating system.

I did find this; http://wiki.pine64.org/index.php/Set_Mac..._on_ROCK64 - which suggests it is possible on Android. I really do need a normal Linux though...

Anyone know how to do this?

Hi,

If you are unable to hear HDMI audio with your rockpro64 and the latest Linux release, you need to follow the instructions on setting PulseAudio default audio output
https://wiki.archlinux.org/index.php/Pul...put_source

Once you set the default to the HDMI, your audio will be routed to your HDMI monitor / TV

BTW - this also fixed the double playing speed on YouTube. Playing is at normal speed

Good luck

Yoram

If anyone is looking for a project, the RTL-SDR is pretty fun with the pine (2gb ram helps).
I created a plane tracker map, that allows to see the location, altitude and speed of planes in the region.
(update: fixed bug on my website that made two minus "--" to a long line)

Hi,
I'd like to fully deactivate the console output on ttyS2 as I'd like to use it. How is it possible to do it?
I'm quite new on Linux boards, I4ve try to search for that, understand that there are things to do with the u-boot or equivalent but really didn't find a simple how to to make it possible.
I'm using a Debian version on the RockPro64. The one recommended.
Thanks a lot

hi, please explain what is stby red light?

I am reporting failures to compile resulting in Rock64 freezing, rebooting, or producing errors.


Trials with hashcat (only available for amd64 and i386, and even then just as 3.30 in stretch) with ayunfan 0.7.9 stretch installed are below.

I fulfilled hashcat's demand for opencl-headers.
apt-get install opencl-headers
The following NEW packages will be installed:
  opencl-c-headers opencl-clhpp-headers opencl-headers

wget https://hashcat.net/files/hashcat-4.2.1.tar.gz
tar -zxf hashcat-4.2.1.tar.gz
cd hashcat-4.2.1/
make
    First effort yielded MANY errors like this one (with "Killed" and coming at the end),
gcc: internal compiler error: Killed (program as)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions.
src/Makefile:479: recipe for target 'obj/LzmaDec.NATIVE.STATIC.o' failed
make: *** [obj/LzmaDec.NATIVE.STATIC.o] Error 4

    Later attempt gave,
...
gcc -c -pipe -std=gnu99 -Iinclude/ -IOpenCL/ -Ideps/lzma_sdk/ -O2 -Ideps/OpenCL-Headers/ -DWITH_HWMON deps/lzma_sdk/Lzma2Dec.c -o obj/Lzma2Dec.NATIVE.STATIC.o
gcc -c -pipe -std=gnu99 -Iinclude/ -IOpenCL/ -Ideps/lzma_sdk/ -O2 -Ideps/OpenCL-Headers/ -DWITH_HWMON deps/lzma_sdk/LzmaDec.c -o obj/LzmaDec.NATIVE.STATIC.o
Write failed: Broken pipe

    The last line was a red herring. The system rebooted perhaps because of a kernel panic. I was able to reproduce the behavior several times.


    Trying to install source from github's master.zip showed the following.
unzip hashcat-master.zip
cd hashcat-master
make linux
gcc -W -Wall -pipe -I include/ -O2 -s -fomit-frame-pointer -funroll-loops -I/opt/hashcat-deps/gmp/linux32/include -D__HC_x86_32__ -DPOSIX -m32 -msse2 -c src/common.c -o obj/common.LINUX.32.o
gcc -W -Wall -pipe -I include/ -O2 -s -fomit-frame-pointer -funroll-loops -I/opt/hashcat-deps/gmp/linux64/include -D__HC_x86_64__ -DPOSIX -m64 -msse2 -c src/common.c -o obj/common.LINUX.64.o
gcc -W -Wall -pipe -I include/ -O2 -s -fomit-frame-pointer -funroll-loops -I/opt/hashcat-deps/gmp/linux64/include -D__HC_XOP__ -DPOSIX -m64 -mxop -c src/common.c -o obj/common.LINUX.XOP.o
gcc: error: unrecognized command line option '-m64'
gcc: error: unrecognized command line option '-mxop'
src/Makefile:316: recipe for target 'obj/common.LINUX.XOP.o' failed
make: *** [obj/common.LINUX.XOP.o] Error 1
make: *** Waiting for unfinished jobs....
gcc: error: unrecognized command line option '-m64'
gcc: error: unrecognized command line option '-m32'
gcc: error: unrecognized command line option '-msse2'
gcc: error: unrecognized command line option '-msse2'
src/Makefile:190: recipe for target 'obj/common.LINUX.64.o' failed
make: *** [obj/common.LINUX.64.o] Error 1
src/Makefile:148: recipe for target 'obj/common.LINUX.32.o' failed
make: *** [obj/common.LINUX.32.o] Error 1


    I added jessie to my sources.list
deb http://cdn.debian.net/debian/ jessie main contrib non-free
deb-src http://cdn.debian.net/debian/ jessie main contrib non-free

and installed gcc-4.9.
Compiling the .tar froze and rebooted the system; the .zip, produced the same errors but in a slightly different order:
CC="gcc-4.9" make linux
...
gcc: error: unrecognized command line option '-m64'
gcc: error: unrecognized command line option '-mxop'
gcc: error: unrecognized command line option '-m32'
src/Makefile:316: recipe for target 'obj/common.LINUX.XOP.o' failed
make: *** [obj/common.LINUX.XOP.o] Error 1
make: *** Waiting for unfinished jobs....
gcc: error: unrecognized command line option '-m64'
gcc: error: unrecognized command line option '-msse2'
gcc: error: unrecognized command line option '-msse2'
src/Makefile:148: recipe for target 'obj/common.LINUX.32.o' failed
make: *** [obj/common.LINUX.32.o] Error 1
src/Makefile:190: recipe for target 'obj/common.LINUX.64.o' failed
make: *** [obj/common.LINUX.64.o] Error 1


    On a Raspberry Pi, I was able to compile from the same .tar without errors.
    The RPi had at the time,
uname -a
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
     I have re-verified that, after a brief hang (where Rock64 reboots), RPi with a clean installation of 4.9.35-v7+ compiles hashcat 4.2.1 just fine.
     I have again searched hashcat's forums, and found no mention of the fragment "compil" aside from one hit, which does not indicate any difficulty with compiling from source.
     I deduce aarch64 to somehow be the origin of the problem, but am open to alternative explanations (and concomittant solutions).


    I had similar issues (including the reboot) when attempting to compile golang 1.11. Unlike hashcat, golang /does/ have a package suitable for my needs (golang-1.10 in backports as opposed to 1.7 in stretch) which I installed by adding to my sources.list:
deb http://cdn.debian.net/debian/ stretch-backports main contrib non-free
deb-src http://cdn.debian.net/debian/ stretch-backports main contrib non-free

and by using its peculiarly placed binary,
/usr/lib/go-1.10/bin/go

My point of including golang 1.11 is simply that I anticipate further challenges with gcc, so I would like at the very least to overcome this one. Despite my attentiveness and web searches, I am as of yet, empty-handed on all counts with compiling.


Any guidance on how to surmount these freezes, reboots, and errors (and compile hashcat 4.2.1) on Rock64 would be most welcome.

"ROCKPro64 Schematic v2.1 (Second Batch Production Release)"
http://files.pine64.org/doc/rockpro64/ro...21-SCH.pdf

Question 1)
In the above published circuit diagram (Sheet of "CODEC/Head phone")
"R225 = DNP,   R226 = 0R" is presented.

However, the result of examining my "rockpro64" is
"R225 = 10kΩ, R226 = DNP".

Please tell me whether this difference is due to the production lot or just the mistake of the circuit diagram.
*) I think that it is merely a mistake in the circuit diagram.


Question 2)
Connection of headphone-jack = "J16:pj_35A063" is obviously wrong.
*) I think that the top and bottom are connected in reverse.

Please introduce the datasheet of "pj_35A063" or present the correct circuit diagram.
I searched the datasheet for "pj_35A063", but I could not find it.

As for the signal name "HPGND / HPOL / HPOR", its connection relation can be inferred.
However, as for the signal name "PHONE_DET / MIC_IN 2 P",
since the specification of "pj_35A063" is unknown,
it is impossible to infer the correct connection relation.

---
My "rockpro64" is a "RAM=4GB" version, and it arrived in 2018-August.
I think that it is probably the "second batch production" lot.

Hi all,

I have Rock64 2GB with Debian minimal Stretch on HDD, using the USB adapter from Pine64 shop.
System i even upgraded to buster/testing using just official Debian repo.
So far works excelent and I'm happy, except for the ancient kernel 4.14.

So here is my questions.
I plan to upgrade kernel, build it myself or wait for 4.18 from Ayufan.
But what if the new kernel will not boot, how can I recover?
Is it just possible to connect HDD to PC and change some conf file?

Another question is about HDMI.
Is it normal that I do not have output on TV (two tested) in early boot? Serial Console is needed to see SPI boot menu and his messages?
HDMI output starts workingvery late in 2-3 seconds before login.

Thanks for help for another ARM newbie?

Hi everyone,

I tried to run debian and mpd on my Rock64 with the add-on board. I turned out that there are three sound cards in alsamixer, which are I2S, SPDIF and HDMI. But I just cannot let the RCA to output any sound. Neither MPD nor speaker-test produce any sound.

Is there any special trick I need to do to make the POT work?

P.S: I'm running ayufan's debian, version 0.7.9.