| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
Yesterday, 11:02 AM
» Replies: 0
» Views: 56
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,019
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-04-2026, 08:23 AM
» Replies: 0
» Views: 97
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 202
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 107
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,578
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,190
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 260
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 186
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,663
|
|
|
| Can't connect to wifi on a Rock64 |
|
Posted by: SuperSaiyanCaleb - 12-18-2018, 07:14 PM - Forum: Linux on Rock64
- Replies (2)
|
 |
I'm trying to set up a Rock64 to connect to wifi using a Panda PAU09 USB wifi adapter. The adapter is mounted in a fixed location, and when connected to my laptop running Ubuntu Bionic, I am able to easily connect to my own wifi network, as well as my school's secure network and their guest network using NetworkManager. However, when I connect the adapter to the Rock64, I am unable to connect to any wifi networks, in spite of seeing them listed when I do a network scan. I have tried this using Armbian Stretch and Bionic images, and also using ayufan's Bionic image. When using nmcli to bring up the connection, I usually receive the error message "The Wi-Fi network could not be found". However, scanning for networks usually shows the network I am attempting to connect to with good signal strength. Other times, the connection will actually "succeed" but I won't be able to communicate over it and then the connection just goes down within seconds.
Any ideas on how I could make this work?
|
|
|
|
| MAME on Standard KDE Neon |
|
Posted by: Corkonian - 12-18-2018, 06:05 AM - Forum: Linux on Pinebook
- Replies (2)
|
 |
So I tried to install MAME on the Pinebook. Would be nice, to have some games around and MAME should be lightweight....
So, after installing and basically configuring, I tried to start my first game
$ mame -nojoy galaga
... and what did I get?
libGL error: unable to load driver : sunxi_dri.so
|
|
|
|
| Input not working after a forced shutdown |
|
Posted by: dic1911 - 12-18-2018, 05:59 AM - Forum: Getting Started
- Replies (1)
|
 |
As title, I just got my Pinebook(14', 1366x768 edition) today,
was using apt command to upgrade LibreOffice and launched Firefox at the same time, just when I typed a few characters at address bar in Firefox,
everything stucked, I had to force it to shutdown and boot again, after that I just can't get the keyboard and touchpad working again, now the only working input is the power button, I can still connect my USB mouse/keyboard to have working input, but that'd totally lose the meaning of Pinebook being easy to carry around, the same situation doesn't change when I switch to Android from Ubuntu Mate, any suggestion?
|
|
|
|
| Overclock the microSD |
|
Posted by: Pine - 12-17-2018, 06:25 PM - Forum: Armbian
- No Replies
|
 |
Has anyone successfully overclocked the SoPine A64 microSD reader with a device tree overlay? U-Boot reports it's 50MHz out of the box. However, this person was able to overclock his Pi3 microSD frequency with a device tree overlay.
Ref: https://www.jeffgeerling.com/blog/2016/h...berry-pi-3
Have we this know-how in our community for our Allwinner A64?
|
|
|
|
| Swapout Pinebook keyboard? |
|
Posted by: maddmike - 12-17-2018, 02:22 PM - Forum: Pinebook Hardware and Accessories
- No Replies
|
 |
Anyone tried to swapout the pinebook keyaboad? The Pinebook has got to has the worst keyboard I ever used and I'm looking to swap it out with something with bigger SHIFT keys and NO POWER Button! Why they decided a "regular" key would be a good power button instead of a separate push button or even a toggle is beyond me.
I know that the bottom half will need to be modified but I am willing to toss it if someone can bpoint me to a good alternative that will fit the general space and form factor.
|
|
|
|
| ROCKPRO64 with 10GbE NICs |
|
Posted by: H.HSEL - 12-17-2018, 06:44 AM - Forum: General Discussion on ROCKPRO64
- Replies (13)
|
 |
I bought a RockPro64 and am trying to build a budget 10GbE storage.
I plugged an AQC107 based ASUS 10GbE card (XG-C100C) into its PCIEx4 adapter and Samsung 860EVO 1TB via USBC-SATA conversion cable (lsusb shows "ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge"), and no problem mounting it.
The image I chose this time is stretch-minimal-rockpro64-0.7.11-1075-arm64 and the driver for the card is Atlantic driver (Atlantic-2.0.15.0).
I downloaded the driver from Aquantia's website and had no problem building and installing.
After 'modprobe atlantic' the board immediately recognized the card as enp1s0. Then its idle power consumption (with all devices active) is around 10W, whose almost half the 10GbE card accounts for.
After changing its MTU from 1500 (default) to 9000, I performed iperf and I got a result around 2.70Gbps, though it seems that the result is not stable, sometimes the value going down to 2.30Gbps or lower.
I don't know why but manually assining iperf processes to a specific core (taskset -c 5 iperf -s, for example) seems to offer better and stable results that is 3.00Gbps.
At this point the effective speed as a NAS (sharing the SSD through SMB and mount it from a Windows client, transferring large data manually and observe how much it takes to complete) is approx. 330MB/s for read and write, and 4k random read/write is 7MB/s and 4KB Q8T8 and 4K Q32T1 for read are both 117MB/s, while it's both 100MB/s for write, says CrystalDiskMark 6.0.2. The peak power consumption is just 15.0W, so it's very power-efficient compared to x86-based 10GbE systems.
This is a great gain to have, considering the limit ROCK64 has.
Currently I have an impression that RockPro64 is an ideal solution for HDD-based NAS, and it would be fun if I would buy more boards and build a distributed system. But it's a little slow for SSD-based NAS, especially when looking at random read/write values.
I wonder if there is anyone who have had more comfortable results with 10GbE NICs and SSDs, to know whether I can get more out of this board or I've reached the limit.
Launching iperf multithreaded (-P6) greatly increased total bandwidth from 3Gbps at most to over 9Gbps, but after all SMB is not multithreaded and what matters most is achieving higher single-thread performance for personal use.
I admit there is room for optimization, so I will post if I have a significant improvement in performance.
|
|
|
|
| Rock64 fedora core 29 boot issue: Help please? |
|
Posted by: forwardbackwards - 12-15-2018, 11:28 PM - Forum: Linux on Rock64
- Replies (5)
|
 |
Hello all!
I'm looking to run fedora core 29 on my Rock64 board and am running into the following issue... The grub.efi app fails to start after its loaded into ram...
Code: ## Starting EFI application at 02080000 ...
"Synchronous Abort" handler, esr 0x96000210
I'm using fedoras u-boot for the evb-rk3288 and wrapping the ayufan bits around it.
I've tried different versions of the DDR binary because I've read the issue may be due to DDR timing issues. So far I'm at a loss as to why it isn't working.
The ayufan git log doesn't seem to contain a lot of info as to what the differences between the versions are between rk33/rk3328_ddr_786MHz_v1.06.bin and rk33/rk3328_ddr_786MHz_v1.13.bin.
any suggestions?
cheers
Code: ~/Desktop/repos/rock64/rkbin-ayufan [master|…9]
21:39 $ git log rk33/rk3328_ddr_786MHz_v1.13.bin
commit b841f4cad608cd5254758457e76f559d5fee5922
Author: Jonas Karlman <jonas@kwiboo.se>
Date: Fri May 18 21:16:12 2018 +0200
rk3328: add ddr v1.13
21:39 $ git log rk33/rk3328_ddr_786MHz_v1.06.bin
commit 701be11ca27c144ded128af93424f7b9735a1d78
Author: Kever Yang <kever.yang@rock-chips.com>
Date: Fri May 12 11:59:48 2017 +0800
rk3328: ddr: add 786M v1.06
suppoart all type and all capability DRAM.
Change-Id: I26749355486a7192fd38305bec30d8c5ad1a407a
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
21:39 $ git log rk33/rk3328_ddr_786MHz_v1.08.bin
commit 10b2468096e88f0c68ec87be8bd26a6f3af53050
Author: Jonas Karlman <jonas@kwiboo.se>
Date: Mon Dec 25 15:33:57 2017 +0100
rk3328: add ddr v1.08 and miniloader v2.44
here's basically how I build the following boot bits:
Code: -rw-rw-r-- 1 86020 Dec 15 21:28 idbloader.bin
-rw-rw-r-- 1 4194304 Dec 15 21:28 trust.img
-rw-rw-r-- 1 4194304 Dec 15 21:28 uboot.img
$TOOLPATH/mkimage -n ${CHIP} -T rksd -d $SRC/rk33/rk3328_ddr_786MHz_v1.06.bin out/idbloader.bin
cat $SRC/rk33/rk3328_miniloader_v2.43.bin >> out/idbloader.bin
$TOOLPATH/loaderimage --pack --uboot ${UBOOT}/u-boot.bin out/uboot.img 0x200000
cat >out/trust.ini <<EOF
[VERSION]
MAJOR=1
MINOR=2
[BL30_OPTION]
SEC=0
[BL31_OPTION]
SEC=1
PATH=../rkbin-ayufan/rk33/rk3328_bl31_v1.39.bin
ADDR=0x10000
[BL32_OPTION]
SEC=0
[BL33_OPTION]
SEC=0
[OUTPUT]
PATH=out/trust.img
EOF
$TOOLPATH/trust_merger out/trust.ini
cp out/idbloader.bin ${OUT}/u-boot/
cp out/uboot.img ${OUT}/u-boot/
cp out/trust.img ${OUT}/u-boot/
This is where I am stuck...
The bootlog
Code: DDR version 1.08 20170628
In
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Boot1 Release Time: 2017-06-12, version: 2.44
ChipType = 0x11, 127
emmc reinit
emmc reinit
SdmmcInit=2 20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 59825
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x92bd4
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):9d3f591
NOTICE: BL31: Built : 14:39:02, Jan 17 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE iK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2019.01-rc1 (Dec 04 2018 - 16:09:21 +0000)
Model: Rockchip RK3328 EVB
DRAM: 4 GiB
MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environmt
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Rockchip RK3328 EVB
Net:
Warning: ethernet@ff540000 (eth0) using random MAC address - 5a:49:f6:fd:87:ae
eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found EFI removable media binary efi/fedora/grubaa64.efi
Found DTB mmc 1:2 /dtb/rockchip/rk3328-evb.dtb
32498 bytes read in 3 ms (10.3 MiB/s)
Scanning disk rksdmmc@ff500000.blk...
Card did not respond to voltage select!
Scanning disk rksdmmc@ff520000.blk...
Disk rksdmmc@ff520000.blk not ready
Found 4 disks
1882872 bytes read in 88 ms (20.4 MiB/s)
## Starting EFI application at 02080000 ...
Speed: 100, full duplex
"Synchronous Abort" handler, esr 0x96000210
elr: fffffffffcf419b0 lr : fffffffffcf419a8 (reloc)
elr: 00000000fbc799b0 lr : 00000000fbc799a8
x0 : 0000000000000000 x1 : 00000000fbb6ae56
x2 : 00000000ffffffff x3 : 00000000fbd718cc
x4 : 00000000fbb6f080 x5 : 0000000000000020
x6 : 00000000fcf26538 x7 : 00000000fbb6be20
x8 : 0000000000000001 x9 : 0000000000000008
x10: 00000000fcf56070 x11: 00000000fcf56070
x12: 000000000000a3c0 x13: 0000000000000001
x14: 00000000fcf2686c x15: 00000000ffffffff
x16: 0000000000001550 x17: 0000000000000000
x18: 00000000fcf2fdf8 x19: 0000000000000000
x20: 00000000fcf56130 x21: 00000000fef385c8
x22: 0000000000000000 x23: 0000000002080000
x24: 0000000000000003 x25: 0000000000000000
x26: 0000000000000000 x27: 0000000000000000
x28: 00000000fcf56010 x29: 00000000fcf26920
Resetting CPU ...
resetting ...
|
|
|
|
|