| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
8 hours ago
» Replies: 6
» Views: 3,989
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
Yesterday, 08:23 AM
» Replies: 0
» Views: 47
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 150
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 70
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,547
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,169
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 235
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 160
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,640
|
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
06-27-2026, 02:43 PM
» Replies: 13
» Views: 18,833
|
|
|
| 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.
|
|
|
|
| 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_num HD 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)
|
|
|
|
| Sata/PCI-E problems? |
|
Posted by: Takenover83 - 09-26-2018, 05:16 PM - Forum: Linux on RockPro64
- Replies (6)
|
 |
I am currently running Ubuntu 18.04 Bionic minimal 0.7.9, with a custom 4.18.9 kernel. Although I have tried others kernels as well. My board is in the NAS enclosure with the 30mm heatsink and a 80mm fan (5-amp power supply). I am running it as a server for Plex, Radarr, Sonarr, Jackett, Deluge, Ombi, and Tautulli.
I am currently experiencing a strange problem with the sata drive, a Western Digital 8TB Red Drive. Or perhaps the problem is with the pci-e card, not sure. I often have quiet a few torrents downloading via deluge. Usually about once or twice a day, I come back to see all of my torrents have error'ed out. Likely, because the drive is somewhat disconnected? Doing a df -h shows it is still mounted, but the drive will not function properly until I do a complete power down. Just curious if anyone else has experienced any troubles similar to this. Either way I am documenting the problem here just in case someone else experiences the problem in the future and can chime in.
|
|
|
|
| Gentoo, Current state, Test Phase |
|
Posted by: khaosgrille - 09-26-2018, 05:11 AM - Forum: Linux on RockPro64
- Replies (12)
|
 |
Hi,
I changed the title to avoid confusion since i decided to fork ayufan's buildscript. Currently it is very promising but I need to fix a few issues before I make it forum post about it.
Here is a link to my todo list for the script https://gitlab.com/khaosgrille/linux-bui...aster/ToDo and ofc the script itself https://gitlab.com/khaosgrille/linux-build
The goal of the script is to crosscompile an Image with I3Wm and some basic packages.
It will use one script where you can look over all stuff i preinstall so you can change it and get your own Image. Currently there is not much missing for an headless system (see my ToDo file).
I deleted the text of my old post here and changed the title since the method I used first did boot but didn't gave me a nice way for modding and testing. I will do a fresh new release thread when all is in a more presentable state.
Sorry for the inconvience and the silence for a month. presentable
Khaosgrille
Edit/Latest Post:
Quote:Hi,
quick update from me. I had few problems with scripting the last steps. I have given up (quite early honestly) and done them by hand and here is an image (https://grmr.de/khaosgrille/gentoo3.img.tar.xz)
I only made a minimal image without X or any tweaks. If u use a sd card as a medium I strongly recommend using TMPDIR on tmpfs.
SD Cards have not enough space/inodes and compiling several packages in a row is nearly impossible.
(https://wiki.gentoo.org/wiki/Portage_TMPDIR_on_tmpfs)
If everything works fine I will make a bigger announcement in the forum. I would like feedback and hear about things you would like to add.
The /boot dir is currently not quite working in the script (but in the image). Sadly I will be to busy to finish the script. I just copied the /boot and the /boot/efi/ from ayufans ubuntu^^.
Greetings
Khaosgrille
PS: The image is for 16gb SD cards and is with DHCPCD aswell as the arm/17.0/Desktop profile.
EDIT: username is root and pw is "rock64"
|
|
|
|
| What do i use the pinebook for? |
|
Posted by: icemeister - 09-25-2018, 04:37 PM - Forum: General Discussion on Pinebook
- Replies (14)
|
 |
i have yet to find a good reason to own the pinebook. i had high hope when i first got it but now not so much. I keep setting it aside for awhile then keep coming back to computer and getting frustrated i keep getting an error about internal 16.04 failed, unable to get software, unable to install vpn, touch pad works to well, no upgrade to 18.4 ubuntu, unable to format flash drive,etc.
what i like is battery life, used on plane to watch movies worked ok, lightweight, good looking, easy to load operating system.
As a newbie i would like to use to help me learn more about linux so i do not have to go to win 10 but as an old guy i just am not getting it.
looks like most of the attention is going to the rock64 and the pinebook is just being set aside or is it.
Thanks for the forum to vent
icemeister
|
|
|
|
| NVMe and new kernel |
|
Posted by: bjbb17 - 09-25-2018, 03:39 PM - Forum: Linux on Pine A64(+)
- No Replies
|
 |
Hi,
Ive got my rockpro64 up and running basically following the procedure of flashing the ubuntu image to Emmc and from there , move / to an NVMe (Samsung 960Pro), which works great,
just .. how to get to a new Ayufan kernel up and running. Tried pretty much what I can (incl extlinux, manual dd's, flags, flash-kernel, tinkering in /boot, etc.) to the extent where it still loads .132-10975 kernel, whatsoever (even though all is installed for .138-1094)
Before going any deeper, anybody know this issue ?
A simple snippet on how the boot procedure actually works on the rockpro64 eMMC case would probably help as well.
Thanks a lot,
Bjoern
|
|
|
|
| Help with linux task schuduler at 4.18, please |
|
Posted by: dukla2000 - 09-25-2018, 02:10 PM - Forum: Linux on RockPro64
- Replies (3)
|
 |
Hi all
Is there anyone here who understands how to "tune" the Linux task scheduler? My problem is that at 4.18.9 it does not obviously favour the big cores for CPU heavy jobs which is crazy.
I wrote a little script to demonstrate what I mean - it uses an additional package stress as an example that can spawn n jobs for t seconds. In my case I run the load for 10 seconds, and after 5 seconds have a look which CPUs are in use:
Code: stress -c 1 -t 10 &
sleep 5
ps -L -o pid,lwp,pcpu,cpuid,time
sleep 6
stress -c 2 -t 10 &
sleep 5
ps -L -o pid,lwp,pcpu,cpuid,time
sleep 6
stress -c 3 -t 10 &
sleep 5
ps -o pid,lwp,pcpu,cpuid,time
sleep 6
stress -c 4 -t 10 &
sleep 5
ps -L -o pid,lwp,pcpu,cpuid,time
On the 4.4.138 (Ayufan) kernel things are pretty much to be expected - CPUs 4 & 5 (the big A72 cores) are always used:
Code: $ ./testcpu
stress: info: [1043] dispatching hogs: 1 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
741 741 0.0 4 00:00:00
1042 1042 0.0 0 00:00:00
1043 1043 0.0 4 00:00:00
1045 1045 100 4 00:00:05
1047 1047 0.0 5 00:00:00
stress: info: [1043] successful run completed in 10s
stress: info: [1050] dispatching hogs: 2 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
741 741 0.0 4 00:00:00
1042 1042 0.0 5 00:00:00
1050 1050 0.0 5 00:00:00
1052 1052 98.6 5 00:00:04
1053 1053 100 4 00:00:05
1055 1055 0.0 0 00:00:00
stress: info: [1050] successful run completed in 10s
stress: info: [1058] dispatching hogs: 3 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
741 741 0.0 4 00:00:00
1042 1042 0.0 5 00:00:00
1058 1058 0.0 4 00:00:00
1060 1060 99.8 0 00:00:04
1061 1061 100 5 00:00:05
1062 1062 100 4 00:00:05
1064 1064 0.0 3 00:00:00
stress: info: [1058] successful run completed in 10s
stress: info: [1067] dispatching hogs: 4 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
741 741 0.0 4 00:00:00
1042 1042 0.0 4 00:00:00
1067 1067 0.0 2 00:00:00
1069 1069 100 1 00:00:05
1070 1070 100 4 00:00:05
1071 1071 100 3 00:00:05
1072 1072 100 5 00:00:05
1074 1074 0.0 0 00:00:00
stress: info: [1067] successful run completed in 10s
On 4.18.9 (despite all my efforts configuring the kernel) it is more luck whether CPUs 4 or 5 do any work:
Code: $ ./testcpu
stress: info: [2375] dispatching hogs: 1 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
2354 2354 0.1 3 00:00:00
2374 2374 0.0 0 00:00:00
2375 2375 0.0 4 00:00:00
2377 2377 83.5 2 00:00:05
2379 2379 1.0 5 00:00:00
stress: info: [2375] successful run completed in 10s
stress: info: [2382] dispatching hogs: 2 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
2354 2354 0.0 3 00:00:00
2374 2374 0.0 0 00:00:00
2382 2382 0.0 1 00:00:00
2384 2384 100 3 00:00:05
2385 2385 100 4 00:00:05
2387 2387 0.0 0 00:00:00
stress: info: [2382] successful run completed in 10s
stress: info: [2390] dispatching hogs: 3 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
2354 2354 0.0 3 00:00:00
2374 2374 0.0 1 00:00:00
2390 2390 0.0 4 00:00:00
2392 2392 100 3 00:00:05
2393 2393 100 5 00:00:05
2394 2394 100 2 00:00:05
2396 2396 0.0 0 00:00:00
stress: info: [2390] successful run completed in 10s
stress: info: [2399] dispatching hogs: 4 cpu, 0 io, 0 vm, 0 hdd
PID LWP %CPU CPUID TIME
2354 2354 0.0 3 00:00:00
2374 2374 0.0 3 00:00:00
2399 2399 0.0 5 00:00:00
2401 2401 100 0 00:00:05
2402 2402 100 4 00:00:05
2403 2403 100 5 00:00:05
2404 2404 100 2 00:00:05
2406 2406 0.0 1 00:00:00
stress: info: [2399] successful run completed in 10s
There does seem to be a kernel CONFIG option at 4.4, ARM_ROCKCHIP_CPUFREQ, that could explain the 4.4 behaviour. And is not available at 4.18.9. But in reality I would expect stock/mainline 4.18 scheduling to cope properly with big.LITTLE CPUs?
Any thoughts/suggestions welcomed.
|
|
|
|
| Upcoming Shipments? |
|
Posted by: jschall - 09-25-2018, 01:59 PM - Forum: General Discussion on Pinebook
- Replies (5)
|
 |
I received my BTO coupon for my 11" Pinebook about 2 weeks ago, and it mentioned that if I ordered then it would ship around the end of October. I ordered the same day.
I sent an email to inquire when my Pinebook would be shipped, but so far I haven't heard from Pine64.
Is it possible to get an update on the production and shipping status of all the recent Pinebook orders?
|
|
|
|
|