5 5
chwe

RockPi 4b 'board bring up'

Recommended Posts

My mistake, I forgot to write that the SD was ignored and simply booted from eMMC. Parted showed the SD card.

Share this post


Link to post
Share on other sites

By default, RK3399 boot order is SPIFlash, eMMC, and then SDCard ...

If you wish to boot the SDCard, you need to stop U-Boot with <spacebar> before it try to load kernel stuff, then you can do the following commands :

mmc list
setenv devnum X          // where X is the SDCard number shown in previous list
run mmc_boot

Of course, if the eMMC has a old Android U-Boot, there is no warranty that the above commands will work.

In such case, the Raxda provided a eMMC-2-SDCard adaptor to be able to write to eMMC using normal USB-SDCard adaptor.

 

Share this post


Link to post
Share on other sites
On 1/20/2019 at 2:26 PM, chwe said:

for whatever reason compiling ATF fails from time to time..


3.2.1.make -C plat/rockchip/rk3399/drivers/m0 BUILD=/home/chwe/armbian/build/cache/sources/arm-trusted-firmware-rockchip64/rockchip/build/rk3399/debug/m0
make[1]: Entering directory '/home/chwe/armbian/build/cache/sources/arm-trusted-firmware-rockchip64/rockchip/plat/rockchip/rk3399/drivers/m0'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/chwe/armbian/build/cache/sources/arm-trusted-firmware-rockchip64/rockchip/plat/rockchip/rk3399/drivers/m0'
make: Nothing to be done for 'bl31'.
out:trust.bin
E: [mergetrust] filter_elf ./build/rk322xh/debug/bl31/bl31.elf file failed
merge failed!
[ error ] ERROR in function compile_atf [ compilation.sh:83 ]
[ error ] ATF file not found [ trust.bin ]
[ o.k. ] Process terminated 

the sources with ATF were still there.. but int fails.. the merge looks like doing it for the wrong soc? someone has a clue?

 

Edit: if you build an image for the rockpro first.. it normally doesn't break.. 

'fixed' well it's not a nice fix but it does the job...

 

https://github.com/armbian/build/commit/6d9ab1c07c16ac990f620885dd9f0a6812f2a573

 

btw. it doesn't' like ISP1 as well.. means the kernel crashes quite soon.. :P

 

 

Share this post


Link to post
Share on other sites
(edited)

Hello all,

I have just got a all new Rockpi 4B.

I have installed the armbian image and xfce desktop.

I just have a problem, the wireless device is not available.

hwinfo --short gives the following result. I guess that broadcom is the wifi device but looks not to be recognized by the armbian image. Am I right ?

Spoiler

 

Quote

cpu:                                                            
                       CPU
                       CPU
                       CPU
                       CPU
                       CPU
                       CPU
keyboard:
  /dev/input/event1    SiGma Micro Keyboard TRACER Gamma Ivory
mouse:
  /dev/input/event4    Logitech TrackMan Wheel
network:
  eth0                 ARM Ethernet 0
network interface:
  lo                   Loopback network interface
  eth0                 Ethernet network interface
disk:
  /dev/zram3           Disk
  /dev/zram1           Disk
  /dev/zram4           Disk
  /dev/mmcblk1         Disk
  /dev/zram2           Disk
  /dev/sda             Verbatim STORE N GO
  /dev/zram0           Disk
partition:
  /dev/mmcblk1p1       Partition
usb controller:
                       ARM USB 0
                       ARM USB 0
                       ARM USB 0
                       ARM USB 0
                       ARM USB 0
                       ARM USB 0
hub:
                       Linux Foundation 3.0 root hub
                       Linux Foundation 1.1 root hub
                       Linux Foundation 2.0 root hub
                       Linux Foundation 1.1 root hub
                       Linux Foundation 3.0 root hub
                       Linux Foundation 2.0 root hub
                       Linux Foundation 2.0 root hub
                       Linux Foundation 2.0 root hub
memory:
                       Main Memory
unknown:
                       Broadcom Unclassified device
                       Broadcom Unclassified device
                       Broadcom Unclassified device
  /dev/input/event3    SiGma Micro Keyboard TRACER Gamma Ivory

 

 

Edited by Tido
added spoiler - for better reading, please do that yourself next time. thx

Share this post


Link to post
Share on other sites
31 minutes ago, patrick-81 said:

the wireless device is not available.

It is working on my RockPi ...

What is the output shown when doing "dmesg | grep -i sdio" ?

 

Share this post


Link to post
Share on other sites

[    1.972199] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    7.229963] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    8.458767] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[    9.471131] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

Share this post


Link to post
Share on other sites

Strange ! On my RockPi, I'm getting :

[    2.269328] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    5.297409] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    5.297415] brcmfmac: brcmf_sdio_prepare_fw_request: using firmware 'brcm/brcmfmac43455-sdio.bin' and nvram 'brcm/brcmfmac43455-sdio.txt'
[    5.522691] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9

 

Share this post


Link to post
Share on other sites

On armbian there is problem with HDMI. That what i have in terminal (kinda hard to see on video, but symbols tremble a bit)

P.S. Also

On 2/1/2019 at 11:36 PM, martinayotte said:

By default, RK3399 boot order is SPIFlash, eMMC, and then SDCard ...

If you wish to boot the SDCard, you need to stop U-Boot with <spacebar> before it try to load kernel stuff, then you can do the following commands :

default Radxa image have other boot priority. I.e. microsd is the first one to boot.

Share this post


Link to post
Share on other sites
3 hours ago, Dante4 said:

default Radxa image have other boot priority. I.e. microsd is the first one to boot.

Maybe their U-Boot check for presence of SDCard and give it a new priority, but the Rockchip SoC itself looks in this specific order is SPIFlash, eMMC, and then SDCard ...

So, if their U-Boot is erased/replaced by Armbian one, the order will be the one I've mentioned.

Share this post


Link to post
Share on other sites
1 minute ago, martinayotte said:

Maybe their U-Boot check for presence of SDCard and give it a new priority, but the Rockchip SoC itself looks in this specific order is SPIFlash, eMMC, and then SDCard ...

So, if their U-Boot is erased/replaced by Armbian one, the order will be the one I've mentioned.

Yes, i understand that much, just to clarify from where mitag got idea of this behavior

Share this post


Link to post
Share on other sites
12 hours ago, martinayotte said:

4.20.0 built myself 2 weeks ago ...

Obviously the problem comes from the Armbian image. I tested the Radxa Ubuntu server and with it the wifi is functional. Maybe I have to do the same as you have done, compile a kernel on my side. What type of platform do you specify Rockpro64 ?

Share this post


Link to post
Share on other sites
(edited)

I build a kernel as recommended in "expert" mode for RockPi-4b and also no wlan

On 2/11/2019 at 3:57 PM, patrick-81 said:

[    1.972199] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    7.229963] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    8.458767] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[    9.471131] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

same here

 

the integrated rtl8814au works well

Edited by hbmaennchen
add comment

Share this post


Link to post
Share on other sites
14 minutes ago, hbmaennchen said:

same here

I've looked at bash history of my RockPi, and ... : Oh ! I didn't remember, but I've used another firmware ...

mv /lib/firmware/brcm/brcmfmac43455-sdio.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin-ORIG
mv /lib/firmware/brcm/brcmfmac43455-sdio.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt-ORIG
cp /lib/firmware/rkwifi/fw_bcm43456c5_ag.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /lib/firmware/rkwifi/nvram_ap6256.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt

 

Share this post


Link to post
Share on other sites

@martinayotte

 

Your mods works fine but only to connect to a network.

But the wifi is really unstable when used as hotspot.

Hope it will improve a bit in the future with new firmwares.

 

ping 172.24.1.1
PING 172.24.1.1 (172.24.1.1) 56(84) bytes of data.
64 bytes from 172.24.1.1: icmp_seq=1 ttl=64 time=1970 ms
64 bytes from 172.24.1.1: icmp_seq=2 ttl=64 time=948 ms
64 bytes from 172.24.1.1: icmp_seq=3 ttl=64 time=91.1 ms
64 bytes from 172.24.1.1: icmp_seq=4 ttl=64 time=118 ms
64 bytes from 172.24.1.1: icmp_seq=5 ttl=64 time=4.38 ms
64 bytes from 172.24.1.1: icmp_seq=6 ttl=64 time=5.03 ms
64 bytes from 172.24.1.1: icmp_seq=7 ttl=64 time=5.49 ms
64 bytes from 172.24.1.1: icmp_seq=8 ttl=64 time=5.84 ms
64 bytes from 172.24.1.1: icmp_seq=9 ttl=64 time=5.81 ms
64 bytes from 172.24.1.1: icmp_seq=10 ttl=64 time=5.75 ms
64 bytes from 172.24.1.1: icmp_seq=11 ttl=64 time=2.35 ms
From 172.24.1.140 icmp_seq=12 Destination Host Unreachable
From 172.24.1.140 icmp_seq=13 Destination Host Unreachable
From 172.24.1.140 icmp_seq=14 Destination Host Unreachable
From 172.24.1.140 icmp_seq=15 Destination Host Unreachable
From 172.24.1.140 icmp_seq=16 Destination Host Unreachable
From 172.24.1.140 icmp_seq=17 Destination Host Unreachable
From 172.24.1.140 icmp_seq=18 Destination Host Unreachable
From 172.24.1.140 icmp_seq=19 Destination Host Unreachable
From 172.24.1.140 icmp_seq=20 Destination Host Unreachable
From 172.24.1.140 icmp_seq=21 Destination Host Unreachable
From 172.24.1.140 icmp_seq=22 Destination Host Unreachable
From 172.24.1.140 icmp_seq=23 Destination Host Unreachable

Share this post


Link to post
Share on other sites
5 minutes ago, patrick-81 said:

But the wifi is really unstable when used as hotspot.

Is it stable in STA mode ?

5 minutes ago, patrick-81 said:

Hope it will improve a bit in the future with new firmwares.

I don't know since it is not Armbian code ...

Share this post


Link to post
Share on other sites

Can someone show me the output of "cpufreq-info" please, wonder if model B ( and A ) have 1,8GHz freq limit or 2GHz like NEO4. thanks

Share this post


Link to post
Share on other sites
(edited)
Spoiler

 ____            _    ____  _       _  _   ____  
|  _ \ ___   ___| | _|  _ \(_)     | || | | __ ) 
| |_) / _ \ / __| |/ / |_) | |_____| || |_|  _ \ 
|  _ < (_) | (__|   <|  __/| |_____|__   _| |_) |
|_| \_\___/ \___|_|\_\_|   |_|        |_| |____/ 
                                                 

Welcome to ARMBIAN 5.74.190131 nightly Debian GNU/Linux 9 (stretch) 4.20.0-rockchip64   
System load:   1.03 0.24 0.08  	Up time:       0 min		
Memory usage:  2 % of 3887MB 	IP:            192.168.178.103
CPU temp:      32°C           	
Usage of /:    5% of 29G    	

[ General system configuration (beta): armbian-config ]

Last login: Thu Feb  7 12:14:30 2019 from 192.168.178.24

pi@rpi4b:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:2.99%, 600 MHz:49.20%, 816 MHz:6.66%, 1.01 GHz:1.30%, 1.20 GHz:0.96%, 1.42 GHz:1.01%, 1.51 GHz:37.87%  (168)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:2.99%, 600 MHz:49.20%, 816 MHz:6.66%, 1.01 GHz:1.30%, 1.20 GHz:0.96%, 1.42 GHz:1.01%, 1.51 GHz:37.87%  (168)
analyzing CPU 2:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:2.99%, 600 MHz:49.20%, 816 MHz:6.66%, 1.01 GHz:1.30%, 1.20 GHz:0.96%, 1.42 GHz:1.01%, 1.51 GHz:37.87%  (168)
analyzing CPU 3:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:2.99%, 600 MHz:49.20%, 816 MHz:6.66%, 1.01 GHz:1.30%, 1.20 GHz:0.96%, 1.42 GHz:1.01%, 1.51 GHz:37.87%  (168)
analyzing CPU 4:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 4 5
  CPUs which need to have their frequency coordinated by software: 4 5
  maximum transition latency: 540 us.
  hardware limits: 408 MHz - 2.02 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 600 MHz and 1.90 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:12.10%, 600 MHz:29.94%, 816 MHz:1.64%, 1.01 GHz:0.48%, 1.20 GHz:1.01%, 1.42 GHz:0.96%, 1.61 GHz:0.96%, 1.80 GHz:49.32%, 2.02 GHz:3.57%  (175)
analyzing CPU 5:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 4 5
  CPUs which need to have their frequency coordinated by software: 4 5
  maximum transition latency: 540 us.
  hardware limits: 408 MHz - 2.02 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 600 MHz and 1.90 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:12.10%, 600 MHz:29.94%, 816 MHz:1.64%, 1.01 GHz:0.48%, 1.20 GHz:1.01%, 1.42 GHz:0.96%, 1.61 GHz:0.96%, 1.80 GHz:49.32%, 2.02 GHz:3.57%  (175)

 

 

Spoiler

 _   _                         _   __  __ _  _   
| \ | | __ _ _ __   ___  _ __ (_) |  \/  | || |  
|  \| |/ _` | '_ \ / _ \| '_ \| | | |\/| | || |_ 
| |\  | (_| | | | | (_) | |_) | | | |  | |__   _|
|_| \_|\__,_|_| |_|\___/| .__/|_| |_|  |_|  |_|  
                        |_|                      

Welcome to ARMBIAN 5.73 stable Ubuntu 18.04.1 LTS 4.4.172-rk3399   
System load:   0.22 0.08 0.02  	Up time:       1 day		
Memory usage:  8 % of 3811MB 	IP:            192.168.178.100
CPU temp:      34°C           	
Usage of /:    3% of 110G   	


pi@npim44:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: interactive, conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "interactive" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:99.70%, 816 MHz:0.02%, 1.01 GHz:0.10%, 1.20 GHz:0.05%, 1.42 GHz:0.05%, 1.51 GHz:0.08%  (5825)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: interactive, conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "interactive" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:99.70%, 816 MHz:0.02%, 1.01 GHz:0.10%, 1.20 GHz:0.05%, 1.42 GHz:0.05%, 1.51 GHz:0.08%  (5825)
analyzing CPU 2:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: interactive, conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "interactive" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:99.70%, 816 MHz:0.02%, 1.01 GHz:0.10%, 1.20 GHz:0.05%, 1.42 GHz:0.05%, 1.51 GHz:0.08%  (5825)
analyzing CPU 3:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 40.0 us.
  hardware limits: 408 MHz - 1.51 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.51 GHz
  available cpufreq governors: interactive, conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 600 MHz and 1.51 GHz.
                  The governor "interactive" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:99.70%, 816 MHz:0.02%, 1.01 GHz:0.10%, 1.20 GHz:0.05%, 1.42 GHz:0.05%, 1.51 GHz:0.08%  (5825)
analyzing CPU 4:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 4 5
  CPUs which need to have their frequency coordinated by software: 4 5
  maximum transition latency: 540 us.
  hardware limits: 408 MHz - 1.99 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz
  available cpufreq governors: interactive, conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 600 MHz and 1.99 GHz.
                  The governor "interactive" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:99.95%, 816 MHz:0.02%, 1.01 GHz:0.01%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:0.01%  (859)
analyzing CPU 5:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 4 5
  CPUs which need to have their frequency coordinated by software: 4 5
  maximum transition latency: 540 us.
  hardware limits: 408 MHz - 1.99 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz
  available cpufreq governors: interactive, conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 600 MHz and 1.99 GHz.
                  The governor "interactive" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:99.95%, 816 MHz:0.02%, 1.01 GHz:0.01%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:0.01%  (859)

 

 

 

Edited by Tido
added spoiler - for better reading, please do that yourself next time. thx

Share this post


Link to post
Share on other sites

thanks very much - this makes me confident model A should be able to handle 2.02 as well

although stated differently at their page " Dual Cortex-72, frequency 1.8GHz ", cheers

Share this post


Link to post
Share on other sites
4 hours ago, dolphs said:

thanks very much - this makes me confident model A should be able to handle 2.02 as well

although stated differently at their page " Dual Cortex-72, frequency 1.8GHz ", cheers

well, that's just a device tree patching to run at 1.8 or 2.0GHz, cause RockPi is WIP don't expect that thermal behavior and stability at 2.0GHz is well tested at the moment.

Share this post


Link to post
Share on other sites

Hi - I would be happy to test Rockpi4A with accompanying heatsink, but it seems a bit expensive to order in EU ( EUR48,29 ) instead China (USD39) - once I received these items I like to contribute testing its stability at 2.0GHz.

Anyway the heatsink looks decent to me and since it does not have to run 24/7 at 2.0GHz I am confident it can be "overclocked" to 2.0GHz for shorter periods, but I like to test that out for my use case ( ovpn with pi-hole ) .

Applied similar tweaks recently overlocking the nano pi neo2 lts (v1.1), updating armbianEnv.txt and cpufrequtils . 

The key to this is temperature, based on current findings neo2 board runs for little while ( 10-15 minutes ) on 1.3Ghz which makes roughly a 10 degrees CPU increase within 6 minutes,

but once it throttles back temp drops rapidly ( of course ) and as said I am condifent similar could be achieved with the Rockpi4...

Share this post


Link to post
Share on other sites
6 hours ago, dolphs said:

it seems a bit expensive to order in EU

I order regularly in China, the USA and in the EU, when comparing prices there are some things to consider.

Spoiler

 

1. In case of domestic orders, the dealer is obliged in the event of a warranty claim. How expensive and complex the return to China is, does not have to burden us. Furthermore, we sometimes have significantly higher shipping costs to China than the Chinese to Europe.

 

2 The call sales tax must be paid here with receipt. If DHL delivers, then they want to double the value of the tax for processing and loaning the amount! DHL delivers once, the drivers have no change and cannot settle cashless!  If you don't have the matching money, you have to go to the customs office! If the Deutsche Post delivers the parcel, then it is delivered directly to the nearest customs office and must be released there. This can be different in other EU countries. I live in a city of 500 K inhabitants, without a customs office and, as a cyclist with 6 hours time to pick up the parcel, I have to use public transport. If the invoice is not, easily accessible to customs, placed outside the packaging, customs cannot charge tax. Either we have to send a credible invoice, or the goods are estimated (extremely expensive!), or the goods are sent back. It is also important to note that shipping costs are subject to tax, which is quite expensive with Express Service.

 

 

Share this post


Link to post
Share on other sites
7 hours ago, mitag said:

there are some things to consider.

:o

 

Those "things" are insane.  Is the shipping system run by some kind of mafia?  Surely the EU can handle simple shipping more effectively than that?

Share this post


Link to post
Share on other sites
On 2/12/2019 at 9:51 PM, patrick-81 said:

@martinayotte

 

Your mods works fine but only to connect to a network.

But the wifi is really unstable when used as hotspot.

Hope it will improve a bit in the future with new firmwares.

 

ping 172.24.1.1
PING 172.24.1.1 (172.24.1.1) 56(84) bytes of data.
64 bytes from 172.24.1.1: icmp_seq=1 ttl=64 time=1970 ms
64 bytes from 172.24.1.1: icmp_seq=2 ttl=64 time=948 ms
64 bytes from 172.24.1.1: icmp_seq=3 ttl=64 time=91.1 ms
64 bytes from 172.24.1.1: icmp_seq=4 ttl=64 time=118 ms

 

USB 3 isn't working properly, only usb2 via hub is reliable

neither wlan sticks nor other external devices like external storage can be used

The hostapd itself is cool

 

[ 2875.987373] usb 8-1: new SuperSpeed Gen 1 USB device number 4 using xhci-hcd
[ 2876.010119] usb 8-1: device descriptor read/8, error -71
[ 2876.119098] usb 8-1: new SuperSpeed Gen 1 USB device number 4 using xhci-hcd
[ 2876.139790] usb 8-1: device descriptor read/8, error -71
[ 2877.056002] usb 8-1: new SuperSpeed Gen 1 USB device number 5 using xhci-hcd
[ 2877.077232] usb 8-1: New USB device found, idVendor=067b, idProduct=2773, bcdDevice= 1.00
[ 2877.077247] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2877.077254] usb 8-1: Product: ATAPI-6 Bridge Controller
[ 2877.077262] usb 8-1: Manufacturer: Prolific Technology Inc.
[ 2877.077269] usb 8-1: SerialNumber: 0123456789000000005
[ 2877.078392] usb-storage 8-1:1.0: USB Mass Storage device detected
[ 2877.087869] scsi host0: usb-storage 8-1:1.0
[ 2877.121300] usbcore: registered new interface driver uas
[ 2899.033921] usb 8-1: reset SuperSpeed Gen 1 USB device number 5 using xhci-hcd

Spoiler
Spoiler

 

 

 

Share this post


Link to post
Share on other sites
28 minutes ago, hbmaennchen said:

Your mods works fine but only to connect to a network.

Yes, I've only tested STA mode, never done testing AP mode.

Maybe the driver/firmware don't handle that, I'm not the author of those ... :o

Share this post


Link to post
Share on other sites
5 5