Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,543
» Latest member: Alex115
» Forum threads: 16,208
» Forum posts: 116,953

Full Statistics

Latest Threads
Call recording?
Forum: PinePhone Pro Software
Last Post: biketool
2 hours ago
» Replies: 7
» Views: 6,096
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: Frank23t
8 hours ago
» Replies: 4
» Views: 1,301
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: biketool
Yesterday, 12:51 PM
» Replies: 4
» Views: 3,150
more mobile linux on redd...
Forum: General Discussion on PinePhone
Last Post: biketool
Yesterday, 12:03 PM
» Replies: 2
» Views: 1,195
Anyone selling a Pinebook
Forum: Pinebook Hardware and Accessories
Last Post: ams
Yesterday, 09:26 AM
» Replies: 2
» Views: 1,395
Having trouble reading MP...
Forum: Getting Started
Last Post: Alex92
09-05-2025, 08:49 PM
» Replies: 1
» Views: 2,517
Special keys stopped work...
Forum: General Discussion on PineNote
Last Post: cheepeero
09-05-2025, 07:32 PM
» Replies: 0
» Views: 1,612
Booting Issues
Forum: PineNote Software
Last Post: vlagged
09-04-2025, 12:52 PM
» Replies: 20
» Views: 9,408
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
09-04-2025, 01:40 AM
» Replies: 11
» Views: 3,866
[Article] RISC-V Ox64 BL8...
Forum: General
Last Post: PrinceMorissette
09-03-2025, 10:51 PM
» Replies: 2
» Views: 4,547

 
  How to deactivate kernel output on ttyS2?
Posted by: ellerbach - 09-30-2018, 09:03 AM - Forum: Linux on RockPro64 - Replies (1)

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


  STBY led is red, rock64 fail?
Posted by: heroes1412 - 09-29-2018, 08:44 PM - Forum: General Discussion on ROCK64 - Replies (1)

hi, please explain what is stby red light?


  Freeze/reboot/errors when compiling - unable to make - reproducible and not isolated
Posted by: jovval - 09-29-2018, 04:42 PM - Forum: Linux on Rock64 - Replies (2)

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.


  My "rockpro64" is different from the public circuit diagram.
Posted by: t4_4t - 09-29-2018, 03:20 AM - Forum: General Discussion on ROCKPRO64 - Replies (2)

"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.


  How to choose kernel to boot
Posted by: mjd - 09-29-2018, 02:43 AM - Forum: Linux on Rock64 - Replies (6)

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?


  Cannot make DAC Add-on Board work under debian
Posted by: szclsya - 09-29-2018, 12:57 AM - Forum: Linux on Rock64 - No Replies

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.


  Better performance
Posted by: larj - 09-28-2018, 04:59 AM - Forum: General Discussion on ROCK64 - Replies (10)

Hello, who could help me, which is more convenient for a plex server, a Pine64 4 gb ram, or an i3 notebook with 4 gb ram, both with ethenet gigabit, I want to watch movies remotely, the amount of users are not more than 5.

Google traductor.


Star Detailed NAS Case assembly (ameriDroid)
Posted by: Luke - 09-28-2018, 02:28 AM - Forum: RockPro64 Projects, Ideas and Tutorials - Replies (15)


  WiFi/BT, How to make a connection?
Posted by: Aesop - 09-27-2018, 11:07 PM - Forum: RockPro64 Hardware and Accessories - No Replies

How to make a WiFi/BT connection via shell command?

Tried WiFi first but doesn't succeed yet.

The following is some log.



Environment
- - - - - - - - - -
Board : RockPro64
OS : bionic-minimal-rockpro64-0.6.59-273-arm64.img
WiFi/BT Module : ROCKPro64 2×2 MIMO Dual Band WIFI 802.11AC/BLUETOOTH 4.2 MODULE[url=https://www.pine64.org/?product=rockpro64-2x2-mimo-dual-band-wifi-802-11acbluetooth-4-1-module][/url]


Log
- - -

Quote:rock64@rockpro64:~$ uname -a
Linux rockpro64 4.4.132-rockchip-ayufan-273 #1 SMP Tue Jul 3 21:35:20 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

rock64@rockpro64:~$ sudo ip link set wlan0 up
RTNETLINK answers: Operation not permitted

rock64@rockpro64:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted

rock64@rockpro64:~$ networkctl | awk '/wlan/ {print $2}'
wlan0

rock64@rockpro64:~$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet6 fe80::ec26:f5ff:fe58:fd1f  prefixlen 64  scopeid 0x20<link>
        ether ee:26:f5:58:fd:1f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5  bytes 681 (681.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 24  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rock64@rockpro64:~$ sudo lshw -c network
  *-network:0 DISABLED      
       description: Wireless interface
       physical id: 7
       logical name: wlan0
       serial: ac:83:f3:e6:25:16
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=wl driverversion=0 multicast=yes wireless=IEEE 802.11
  *-network:1
       description: Ethernet interface
       physical id: 8
       logical name: eth0
       serial: ee:26:f5:58:fd:1f
       size: 10Mbit/s
       capacity: 1Gbit/s
       capabilities: ethernet physical tp aui bnc mii fibre 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=st_gmac driverversion=March_2013 duplex=half link=no multicast=yes port=MII speed=10Mbit/s

rock64@rockpro64:~$ rfkill list all
0: bt_default: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no

rock64@rockpro64:~$ lsmod
Module                  Size  Used by
zram                   32768  6
lz4_decompress         16384  1 zram
lz4_compress           16384  1 zram
bcmdhd               1183744  0
rockchip_saradc        16384  0
snd_soc_rockchip_spdif    16384  2
snd_soc_rockchip_i2s    16384  4
snd_soc_rockchip_hdmi_dp    16384  0
ip_tables              24576  0
x_tables               32768  1 ip_tables
autofs4                40960  0
dw_hdmi_i2s_audio      16384  0

rock64@rockpro64:~$ nmcli c
NAME  UUID  TYPE  DEVICE 

rock64@rockpro64:~$ modinfo -p bcmdhd
dhd_doflow: (uint)
dhd_dpcpoll: (uint)
clockoverride:SDIO card clock override (int)
sd_msglevel: (uint)
sd_power: (uint)
sd_clock: (uint)
sd_divisor: (uint)
sd_sdmode: (uint)
sd_hiok: (uint)
sd_f2_blocksize: (int)
sd_f1_blocksize: (int)
g_assert_type: (int)
dhd_oob_gpio_numBig GrinHD oob gpio number (int)
clm_path: (string)
info_string: (string)
op_mode: (int)
dhd_msg_level: (int)
iw_msg_level: (int)
wl_dbg_level: (int)
android_msg_level: (int)
config_msg_level: (int)
dhd_arp_enable: (uint)
dhd_arp_mode: (uint)
disable_proptx: (int)
firmware_path: (string)
nvram_path: (string)
config_path: (string)
dhd_watchdog_ms: (uint)
dhd_console_ms: (uint)
dhd_slpauto: (uint)
dhd_pkt_filter_enable: (uint)
dhd_pkt_filter_init: (uint)
dhd_master_mode: (uint)
dhd_watchdog_prio: (int)
dhd_dpc_prio: (int)
dhd_rxf_prio: (int)
dhd_dongle_ramsize: (int)
passive_channel_skip: (int)
instance_base: (int)
iface_name: (string)
dhd_idletime: (int)
dhd_poll: (uint)
dhd_intr: (uint)
dhd_sdiod_drive_strength: (uint)
dhd_txbound: (uint)
dhd_rxbound: (uint)
dhd_deferred_tx: (uint)
dhd_pktgen: (uint)
dhd_pktgen_len: (uint)
allow_delay_fwdl: (int)


  WIFI on Android OS
Posted by: Berkut - 09-27-2018, 05:51 AM - Forum: Android on Pine A64(+) - Replies (2)

Hello Everyone!
I have one silly question ...
Will Pine A64 work with PINE64 WIFI 802.11BGN/BLUETOOTH 4.0 MODULE on Android OS ?
Thanks in a advance.