CSC Armbian for RK322X TV Boxes


Recommended Posts

On 9/24/2020 at 7:40 PM, jock said:

I don't see any error in your dmesg log (please put your logs in a "spoiler" section), but if you think there is a missing module I can enable it. Maybe you are missing the firmware for the DVB USB stick.

I have tried to copy relate firmwares to lib/firmware,but didn't work.Looks like that certain modules or drivers wasn't build into kernel(si2157,si2168,si2141,m88ds3103,m88ds3103b,...).Maybe some kernel configuration options not being seleced.(CONFIG_MEDIA_SUBDRV_AUTOSELECT).Could you pls look into it?Thx.

Link to post
Share on other sites
Donate and support the project!

7 hours ago, megaduo said:

I have tried to copy relate firmwares to lib/firmware,but didn't work.Looks like that certain modules or drivers wasn't build into kernel(si2157,si2168,si2141,m88ds3103,m88ds3103b,...).Maybe some kernel configuration options not being seleced.(CONFIG_MEDIA_SUBDRV_AUTOSELECT).Could you pls look into it?Thx.

I checked your dvb stick, it should have si2168 chip which surely is not enabled at the moment. si2141 is the tuner, but I see no references in the kernel.

I will try to compile a kernel with si2168 module soon

Link to post
Share on other sites
On 1/9/2020 at 3:31 AM, jock said:

Alternative: you can install the bootloader in NAND and let it boot from SD Card or USB:

  • Download a copy of the Multitool and burn it on an SD card;
  • Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears;
  • RECOMMENDED: make a backup of the existing firmware with "Backup flash" menu option;
  • Choose "Install Jump Start for Armbian" menu option: the Jump Start uses the internal NAND to boot from external SD Card or external USB Stick;
  • Follow the general instructions to boot from SD Card below, skip the first erase eMMC step.


Hi @jock & @fabiobassa, Thanks for supporting RK322x SoC.

I have read the manual, I want to use SD Card to boot to Armbian while keeping my android image in eMMC.
I had burned the multitool image, then insert my SD Card to to the box and now it boots to the multitool menu.

However I cannot find the "Install Jump Start for Armbian".
Here's the menu that I got:

1. Backuo flash

2. Restore flash

3. Erase flash

4. Drop to bash shell

5. Burn image to flash

8. Reboot

9. Shutdown

 

How can I find this "Install Jump Start for Armbian" from multitool?
Thanks for your help,

rna

Link to post
Share on other sites
17 hours ago, jock said:

I checked your dvb stick, it should have si2168 chip which surely is not enabled at the moment. si2141 is the tuner, but I see no references in the kernel.

I will try to compile a kernel with si2168 module soon

Thx,i've got log from amlogic s905d set top box that  works fine with the stick which you can refer to.

Spoiler

Module                  Size  Used by
hci_uart               34102  1
cifs                  402687  0
bnep                   15079  2
si2157                  7659  1
si2168                 11076  1
dhd                   902634  0
8021q                  21855  0
btsdio                  4874  0
dvb_usb_dvbsky         11024  0
m88ds3103              22727  1 dvb_usb_dvbsky
dvb_usb_v2             24019  1 dvb_usb_dvbsky
dvb_core              125735  3 dvb_usb_v2,m88ds3103,dvb_usb_dvbsky
videobuf2_vmalloc       6593  1 dvb_core
videobuf2_memops        2012  1 videobuf2_vmalloc
frame_vector            3190  2 videobuf2_vmalloc,videobuf2_memops
bluetooth             372939  25 bnep,btsdio,hci_uart
videobuf2_common       43214  1 dvb_core
6lowpan_iphc           10231  1 bluetooth
cfg80211              417431  1 dhd
mali                  224703  5
wireguard             126823  0
wifi_dummy               894  0
amlvideodri            13834  0
videobuf_res            5794  1 amlvideodri
videobuf_core          18415  2 amlvideodri,videobuf_res
videodev              201143  2 amlvideodri,videobuf2_common
mc                     38700  5 si2157,dvb_usb_v2,videobuf2_common,videodev,dvb_core
dwc_otg               261556  0
fbcon                  40863  0
bitblit                 4820  1 fbcon
softcursor              1344  1 bitblit
font                    7399  1 fbcon

Spoiler

dmesg | grep dvb
[    5.907339@0] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[    5.940723@0] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.dvb-latest/lib/modules/3.14.29
[   11.147513@0] usb 1-1: dvb_usb_v2: found a 'MyGica Mini DVB-T2 USB Stick T230C v2' in warm state
[   11.199443@2] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   11.199474@2] dvbdev: DVB: registering new adapter (MyGica Mini DVB-T2 USB Stick T230C v2)
[   11.200280@2] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[   11.229182@2] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[   11.230396@2] usb 1-1: dvb_usb_v2: 'MyGica Mini DVB-T2 USB Stick T230C v2' successfully initialized and connected
[   11.230551@2] usbcore: registered new interface driver dvb_usb_dvbsky

 

Edited by megaduo
Link to post
Share on other sites
5 hours ago, megaduo said:

Thx,i've got log from amlogic s905d set top box that  works fine with the stick which you can refer to.

  Reveal hidden contents

Module                  Size  Used by
hci_uart               34102  1
cifs                  402687  0
bnep                   15079  2
si2157                  7659  1
si2168                 11076  1
dhd                   902634  0
8021q                  21855  0
btsdio                  4874  0
dvb_usb_dvbsky         11024  0
m88ds3103              22727  1 dvb_usb_dvbsky
dvb_usb_v2             24019  1 dvb_usb_dvbsky
dvb_core              125735  3 dvb_usb_v2,m88ds3103,dvb_usb_dvbsky
videobuf2_vmalloc       6593  1 dvb_core
videobuf2_memops        2012  1 videobuf2_vmalloc
frame_vector            3190  2 videobuf2_vmalloc,videobuf2_memops
bluetooth             372939  25 bnep,btsdio,hci_uart
videobuf2_common       43214  1 dvb_core
6lowpan_iphc           10231  1 bluetooth
cfg80211              417431  1 dhd
mali                  224703  5
wireguard             126823  0
wifi_dummy               894  0
amlvideodri            13834  0
videobuf_res            5794  1 amlvideodri
videobuf_core          18415  2 amlvideodri,videobuf_res
videodev              201143  2 amlvideodri,videobuf2_common
mc                     38700  5 si2157,dvb_usb_v2,videobuf2_common,videodev,dvb_core
dwc_otg               261556  0
fbcon                  40863  0
bitblit                 4820  1 fbcon
softcursor              1344  1 bitblit
font                    7399  1 fbcon

  Reveal hidden contents

dmesg | grep dvb
[    5.907339@0] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[    5.940723@0] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.dvb-latest/lib/modules/3.14.29
[   11.147513@0] usb 1-1: dvb_usb_v2: found a 'MyGica Mini DVB-T2 USB Stick T230C v2' in warm state
[   11.199443@2] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   11.199474@2] dvbdev: DVB: registering new adapter (MyGica Mini DVB-T2 USB Stick T230C v2)
[   11.200280@2] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[   11.229182@2] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[   11.230396@2] usb 1-1: dvb_usb_v2: 'MyGica Mini DVB-T2 USB Stick T230C v2' successfully initialized and connected
[   11.230551@2] usbcore: registered new interface driver dvb_usb_dvbsky

 

Okay, the log from 905d was useful, I see that some modules have been loaded so I enabled them in the kernel config.

This is a development debian minimal image to test for you, kernel is 5.8.12:

 

https://drive.google.com/file/d/1WMEuJYW2tam-9y0eK4VLGAzoEFXmjQwJ/view?usp=sharing

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


Hi @jock & @fabiobassa, Thanks for supporting RK322x SoC.

I have read the manual, I want to use SD Card to boot to Armbian while keeping my android image in eMMC.
I had burned the multitool image, then insert my SD Card to to the box and now it boots to the multitool menu.

However I cannot find the "Install Jump Start for Armbian".
Here's the menu that I got:

1. Backuo flash

2. Restore flash

3. Erase flash

4. Drop to bash shell

5. Burn image to flash

8. Reboot

9. Shutdown

 

How can I find this "Install Jump Start for Armbian" from multitool?
Thanks for your help,

rna

 

Hello, Jumpstart is for boxes with NAND flash memory. You're lucky because you have an eMMC, which is much less troublesome.

 

Anyway at the moment the Armbian bootloader is almost entirely based on open source software (u-boot), so when the original firmware is installed in eMMC, it just does not boot from sdcard. I know that this may seem a bit odd, but this way bootloader upgrades are safer and don't rely upon rockchip proprietary tools.

 

For this reason the Multitool has the ability to do backup and restore of the entire eMMC content with ease.

Link to post
Share on other sites
22 hours ago, jock said:

Hello, Jumpstart is for boxes with NAND flash memory. You're lucky because you have an eMMC, which is much less troublesome.

 

Anyway at the moment the Armbian bootloader is almost entirely based on open source software (u-boot), so when the original firmware is installed in eMMC, it just does not boot from sdcard. I know that this may seem a bit odd, but this way bootloader upgrades are safer and don't rely upon rockchip proprietary tools.

 

For this reason the Multitool has the ability to do backup and restore of the entire eMMC content with ease.

Thanks for your reply,

I just want to confirm:
Does this mean that I have to erase the original firmware from the eMMC?

Is there a way that does not involve erasing the original firmware? instead just using SD Card to boot Armbian while keeping the android in the eMMC.

Link to post
Share on other sites
22 hours ago, jock said:

so when the original firmware is installed in eMMC, it just does not boot from sdcard. I know that this may seem a bit odd, but this way bootloader upgrades are safer and don't rely upon rockchip proprietary tools.

ok got it!
 

 

22 hours ago, jock said:

For this reason the Multitool has the ability to do backup and restore of the entire eMMC content with ease.

It means I have to prepare an SD card that is bigger than 16GB to backup my entire eMMC content

Link to post
Share on other sites
1 hour ago, rna said:

Is there a way that does not involve erasing the original firmware? instead just using SD Card to boot Armbian while keeping the android in the eMMC.

Yes, there is a way but it is absolutely not really comfy and fast, plus requires some advanced skills to prepare the whole thing and involves the use os some proprietary rockchip tools and the rockchip miniloader

 

1 hour ago, rna said:

It means I have to prepare an SD card that is bigger than 16GB to backup my entire eMMC content

Not necessarily, if you use the Multitool to make a backup, it will backup the eMMC content directly into a compressed file. It depends on how much data you already stored in your eMMC, but usually it fits into much smaller sdcards. Since the partition of the Multitool is FAT for maximum compatibility, the compressed file must not be bigger than 4GB but you may give it a try.

Link to post
Share on other sites

Hey guys I just updated my V88 mini 4k with legacy kernel. During upgrade I saw some errors for rk3229-legacy-kernel update or something. After reboot try it didn't halt as usual, but after replug the box doesn't start anymore just the red led. I installed the armbian onto NAND and it worked quite well even with wifi I used it with around 30 Mbit /s up and down. I just wanted to keep on maintaining and did the upgrade. Now I guess I lost the correct upgrade path between legacy kernels since I haven't updated for at least around 5 months. 

 

So what can you recommend and is there a chance to get back onto my data in NAND or do I need to start from zero again with multitool? 

Link to post
Share on other sites
18 hours ago, jock said:

Yes, there is a way but it is absolutely not really comfy and fast, plus requires some advanced skills to prepare the whole thing and involves the use os some proprietary rockchip tools and the rockchip miniloader

Could you please share a reading about this? It doesn't matter if it is a complicated process for me. Anyway thanks for your reply

Link to post
Share on other sites
13 minutes ago, rna said:

Could you please share a reading about this? It doesn't matter if it is a complicated process for me. Anyway thanks for your reply

 

Sure. This is a description of the boot process I made in an earlier post. You have to follow the first process which uses the miniloader. The existing bootloader in the internal flash memory is always engaged first, but if you put the miniloader-based bootloader on the external sdcard, the internal miniloader will boot from external sdcard

 

This is the operative approach followed by LibreELEC source code which does the operation to create the bootloader with all the things in the proper places:

https://github.com/knaerzche/LibreELEC.tv/blob/master/projects/Rockchip/bootloader/install

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

Hey guys I just updated my V88 mini 4k with legacy kernel. During upgrade I saw some errors for rk3229-legacy-kernel update or something. After reboot try it didn't halt as usual, but after replug the box doesn't start anymore just the red led. I installed the armbian onto NAND and it worked quite well even with wifi I used it with around 30 Mbit /s up and down. I just wanted to keep on maintaining and did the upgrade. Now I guess I lost the correct upgrade path between legacy kernels since I haven't updated for at least around 5 months. 

 

So what can you recommend and is there a chance to get back onto my data in NAND or do I need to start from zero again with multitool? 

Uhm, I'm sorry about this, can't think about what went wrong... the legacy kernel is in practice frozen from the first publication day.

What may have happened is some kind of corruption of the trust or the bootloader.

 

The Multitool has a nice function to give you a bash shell to access the NAND partition and make the manual necessary checks, but of course you need to be aware of what you do.

 

These commands may be helpful to restore the trustos and u-boot on the NAND, in case they were somehow damaged:

mount /dev/mmcblk0p1 /mnt
dd if=/mnt/bsp/legacy-uboot.img of=/dev/rknand0 bs=4M seek=1 oflag=direct
dd if=/mnt/bsp/trustos.img of=/dev/rknand0 bs=4M seek=2 oflag=direct
sync
exit

then you can shutdown via multiboot menu and cycle power to see if it works

Link to post
Share on other sites

Hi @jockthanks for your answer unfortunately it didn't work out. It is still not booting.

 

I decided with pain to flash the new minimal legacy image. Before flashing it asked to heavily keep the idbloader even when the image has a different one. So I followed the suggestion. 

 

Burning successfully finished, shutdown and reboot, Red led is still very weak visible and it doesn't boot... 

 

Should I try to reflash with idbloader? 

Link to post
Share on other sites

Hi @fabiobassa,

 

Noticed a mistake. Did use wrong flash method for NAND... 

 

Reflashed with... NAND-method. 

 

Now the device is booting again... Sorry guys. This was my mistake, I didn't read carefully enough again... 

 

Thanks for your hard work which I really celebrate than just only appreciate which of course I also do! 😊

 

Hey is it worth to give it a try with new image kernel 5.8 or still no working wifi driver for ssv6051? 

 

Edit: guys! I'm blasted of the development! It detected and selected already everything correctly when I ran 

 

sudo rk3229-config

 

Awesome! Crossing fingers for reboot and tests with internal wifi 

 

Id 3030:3030

 

Cheers Alex 

Edited by Alex83
Surprisingly blasted
Link to post
Share on other sites

@Alex83

glad to see that everything is OK.
Yes, @jock did some surprising enanchments to the whole process and now is working even the dual band ssv6x5x wifi chip, but yet on legacy

For mainline kernel  the work to do is rewrite the wifi driver , but really it could take some expensive time consuming efforts , while now energies are concentrating on desktop usage  and acceleration side on mainline kernel

Link to post
Share on other sites

Fingers crossed for development. 

 

Dpkg: error processing package linux-image-legacy-rk322x (--configure) : installed linux-image-legacy-rk322x package post-installation scripts subprocess returned error exit status 1

 

Errors were encountered while processing :

 

linux-image-legacy-rk322x 

E: Sub-process /usr/bin/dpkg returned an error code (1)

 

Hope you guys can tell why it's not going well with the update... 

 

Also I noticed reboot is still not working unfortunately. I need to replug the power adapter... 

 

First test with Iperf3 were more weak than with older versions... 

 

68 Mbit/s with - R option and 86 Mbit/s if device is sending to internal host. 

 

Localhost Iperf3 is around 640 Mbit/s up and down. 

 

With old versions it went

 

~95 Mbit/s up and down to local network hosts and 1,6Gbit/s 

 

So maybe you guys have still some good ideas to solve the issues... 

 

Edit:

 

WiFi measurements also more weak than with Armbian 20.05 image before 

 

 

 

      _    _________  ____            _
 _ __| | _|___ /___ \|___ \__  __    | |__   _____  __
| '__| |/ / |_ \ __) | __) \ \/ /____| '_ \ / _ \ \/ /
| |  |   < ___) / __/ / __/ >  <_____| |_) | (_) >  <
|_|  |_|\_\____/_____|_____/_/\_\    |_.__/ \___/_/\_\

Welcome to Armbian 20.08.5 Focal with Linux 4.4.194-rk322x

No end-user support: community creations

System load:   136%             Up time:       48 min
Memory usage:  6% of 980M       IP:
CPU temp:      65°C             Usage of /:    11% of 7.0G


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

Last login: Tue Aug 25 11:50:22 2020

[ Kernel was updated, please reboot ]

root@rk322x-box:~# iperf3 -c 192.168.178.193
Connecting to host 192.168.178.193, port 5201
[  5] local 192.168.178.191 port 55986 connected to 192.168
178.193 port 5201
[ ID] Interval           Transfer     Bitrate         Retr
Cwnd
[  5]   0.00-1.00   sec   385 KBytes  3.15 Mbits/sec    0
35.4 KBytes
[  5]   1.00-2.00   sec   175 KBytes  1.44 Mbits/sec    0
35.4 KBytes
[  5]   2.00-3.00   sec   201 KBytes  1.65 Mbits/sec    0
35.4 KBytes
[  5]   3.00-4.00   sec   127 KBytes  1.04 Mbits/sec    0
35.4 KBytes
[  5]   4.00-5.00   sec   304 KBytes  2.49 Mbits/sec    0
35.4 KBytes
[  5]   5.00-6.00   sec   491 KBytes  4.02 Mbits/sec    0
35.4 KBytes
[  5]   6.00-7.00   sec   588 KBytes  4.82 Mbits/sec    0
35.4 KBytes
[  5]   7.00-8.00   sec  1.16 MBytes  9.77 Mbits/sec    0
35.4 KBytes
[  5]   8.00-9.00   sec  1.12 MBytes  9.43 Mbits/sec    0
35.4 KBytes
[  5]   9.00-10.00  sec  1.45 MBytes  12.2 Mbits/sec    0
35.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  5.96 MBytes  5.00 Mbits/sec    0
          sender
[  5]   0.00-10.00  sec  5.90 MBytes  4.95 Mbits/sec
          receiver

iperf Done.
root@rk322x-box:~# iperf3 -c 192.168.178.193 -R
Connecting to host 192.168.178.193, port 5201
Reverse mode, remote host 192.168.178.193 is sending
[  5] local 192.168.178.191 port 55990 connected to 192.168
178.193 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   481 KBytes  3.94 Mbits/sec

[  5]   1.00-2.00   sec   567 KBytes  4.65 Mbits/sec

[  5]   2.00-3.00   sec   494 KBytes  4.04 Mbits/sec

[  5]   3.00-4.00   sec   359 KBytes  2.94 Mbits/sec

[  5]   4.00-5.00   sec   564 KBytes  4.62 Mbits/sec

[  5]   5.00-6.00   sec   536 KBytes  4.39 Mbits/sec

[  5]   6.00-7.00   sec   544 KBytes  4.46 Mbits/sec

[  5]   7.00-8.00   sec   540 KBytes  4.43 Mbits/sec

[  5]   8.00-9.00   sec   523 KBytes  4.29 Mbits/sec

[  5]   9.00-10.00  sec   998 KBytes  8.18 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  6.65 MBytes  5.58 Mbits/sec    0
          sender
[  5]   0.00-10.00  sec  5.48 MBytes  4.59 Mbits/sec
          receiver

iperf Done.
root@rk322x-box:~#
root@rk322x-box:~#
root@rk322x-box:~#

 

Edited by Alex83
Tried wifi, worked once down with around 30 Mbit/s
Link to post
Share on other sites
 

35.4 KBytes
[  5]   4.00-5.00   sec   304 KBytes  2.49 Mbits/sec    0
35.4 KBytes
[  5]   5.00-6.00   sec   491 KBytes  4.02 Mbits/sec    0
35.4 KBytes
[  5]   6.00-7.00   sec   588 KBytes  4.82 Mbits/sec    0
35.4 KBytes
[  5]   7.00-8.00   sec  1.16 MBytes  9.77 Mbits/sec    0
35.4 KBytes
[  5]   8.00-9.00   sec  1.12 MBytes  9.43 Mbits/sec    0
35.4 KBytes
[  5]   9.00-10.00  sec  1.45 MBytes  12.2 Mbits/sec    0
35.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  5.96 MBytes  5.00 Mbits/sec    0
          sender
[  5]   0.00-10.00  sec  5.90 MBytes  4.95 Mbits/sec
          receiver

iperf Done.
root@rk322x-box:~# iperf3 -c 192.168.178.193 -R
Connecting to host 192.168.178.193, port 5201
Reverse mode, remote host 192.168.178.193 is sending
[  5] local 192.168.178.191 port 55990 connected to 192.168
178.193 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   481 KBytes  3.94 Mbits/sec

[  5]   1.00-2.00   sec   567 KBytes  4.65 Mbits/sec

[  5]   2.00-3.00   sec   494 KBytes  4.04 Mbits/sec

[  5]   3.00-4.00   sec   359 KBytes  2.94 Mbits/sec

[  5]   4.00-5.00   sec   564 KBytes  4.62 Mbits/sec

[  5]   5.00-6.00   sec   536 KBytes  4.39 Mbits/sec

[  5]   6.00-7.00   sec   544 KBytes  4.46 Mbits/sec

[  5]   7.00-8.00   sec   540 KBytes  4.43 Mbits/sec

[  5]   8.00-9.00   sec   523 KBytes  4.29 Mbits/sec

[  5]   9.00-10.00  sec   998 KBytes  8.18 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  6.65 MBytes  5.58 Mbits/sec    0
          sender
[  5]   0.00-10.00  sec  5.48 MBytes  4.59 Mbits/sec
          receiver

iperf Done.
root@rk322x-box:~#
root@rk322x-box:~#
root@rk322x-box:~# iperf3 -c 192.168.178.193 -R
Connecting to host 192.168.178.193, port 5201
Reverse mode, remote host 192.168.178.193 is sending
[  5] local 192.168.178.191 port 55994 connected to 192.168
178.193 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  2.80 MBytes  23.5 Mbits/sec

[  5]   1.00-2.00   sec  3.32 MBytes  27.8 Mbits/sec

[  5]   2.00-3.00   sec  3.46 MBytes  29.0 Mbits/sec

[  5]   3.00-4.00   sec  3.93 MBytes  33.0 Mbits/sec

[  5]   4.00-5.00   sec  3.65 MBytes  30.6 Mbits/sec

[  5]   5.00-6.00   sec  3.77 MBytes  31.6 Mbits/sec

[  5]   6.00-7.00   sec  3.86 MBytes  32.4 Mbits/sec

[  5]   7.00-8.00   sec  3.91 MBytes  32.8 Mbits/sec

[  5]   8.00-9.00   sec  3.84 MBytes  32.2 Mbits/sec

[  5]   9.00-10.00  sec  3.79 MBytes  31.9 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  38.4 MBytes  32.2 Mbits/sec   36
          sender
[  5]   0.00-10.00  sec  36.3 MBytes  30.5 Mbits/sec
          receiver

iperf Done.
root@rk322x-box:~# iperf3 -c 192.168.178.193
Connecting to host 192.168.178.193, port 5201
[  5] local 192.168.178.191 port 55998 connected to 192.168
178.193 port 5201
[ ID] Interval           Transfer     Bitrate         Retr
Cwnd
[  5]   0.00-1.00   sec  2.83 MBytes  23.7 Mbits/sec    0
 130 KBytes
[  5]   1.00-2.00   sec  2.06 MBytes  17.3 Mbits/sec    0
 130 KBytes
[  5]   2.00-3.00   sec  2.09 MBytes  17.5 Mbits/sec    0
 130 KBytes
[  5]   3.00-4.00   sec  2.02 MBytes  16.9 Mbits/sec    0
 130 KBytes
[  5]   4.00-5.00   sec  2.21 MBytes  18.5 Mbits/sec    0
 130 KBytes
[  5]   5.00-6.00   sec  2.12 MBytes  17.8 Mbits/sec    0
 130 KBytes
[  5]   6.00-7.00   sec  2.19 MBytes  18.4 Mbits/sec    0
 130 KBytes
[  5]   7.00-8.00   sec  2.35 MBytes  19.7 Mbits/sec    0
 130 KBytes
[  5]   8.00-9.00   sec  2.37 MBytes  19.9 Mbits/sec    0
 130 KBytes
[  5]   9.00-10.00  sec  2.36 MBytes  19.8 Mbits/sec    0
 130 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  22.6 MBytes  19.0 Mbits/sec    0
          sender
[  5]   0.00-10.00  sec  22.4 MBytes  18.8 Mbits/sec
          receiver

iperf Done.
root@rk322x-box:~#

 

 

After a reboot (plug out and in) the device is surprisingly still booting. Unfortunately I noticed before reboot in armbian-config there were two wireless connections. One p2p and a wifi interface. Both discovered the same wifis around and I used the p2p interface for above measurement. 

 

After reboot there is just one wifi connection still there and the HotSpot function disappeared unfortunately... 

 

I guess it has something to do with kernel upgrade error. 

 

Why does it still try to upgrade the legacy kernel by using the usual 

 

apt update && apt upgrade

 

 

Link to post
Share on other sites
12 minutes ago, Alex83 said:

Dpkg: error processing package linux-image-legacy-rk322x (--configure) : installed linux-image-legacy-rk322x package post-installation scripts subprocess returned error exit status 1

 

Errors were encountered while processing :

 

linux-image-legacy-rk322x 

E: Sub-process /usr/bin/dpkg returned an error code (1)

The output as-is does not provide any hint of what the problem may be unfortunately :unsure:

13 minutes ago, Alex83 said:

Also I noticed reboot is still not working unfortunately. I need to replug the power adapter... 

Yes, this is an issue with almost all NAND devices, could not find a software workaround because I didn't understand the reason this happens.

 

About the iperf performances, I made some tests during the adaptation of the other ssv6x5x driver. I remember very well that the ssv6x5x was around ~60-65 Mbit/s, the ssv6051 was around ~40Mbit/s and the ethernet was steady around ~90Mbit/s.

Of course wifi drivers were tested in ideal conditions: the router and the box were in line of sight each other without obstacles and without interference from other routers/devices.

 

Also in the latest images the ssv6051 and ssv6x5x drivers have been compiled with compiler optimizations on (-Os), the hardware cyphers active, and the p2p interface deactivated so they should perform even better than before. p2p interface was causing a lot of performance degradation in the past because network manager was scanning the networks thus interfering with the wlan0 network.

 

Did you use one of the stable images from the armbian download page or one of my compiles in the first page of this post?

 

 

Link to post
Share on other sites

Hi thanks a lot for your very quick reply! I used your compiled images. 

 

Can I also try to use ssv6x5x driver with ssv6051 chipset? 

 

Id: 3030:3030

 

Cheers and very good work and fantastic that it made to official armbian side! I'm very happy to see that after such a long period of collecting this electronic trash devices. Unfortunately they were never usable with original firmwares under Android... 

 

BTW is there a solution for switching eth0 mac address after each reboot? 

Link to post
Share on other sites
Quote

BTW is there a solution for switching eth0 mac address after each reboot


Sure, you have two:
1) don't use network manager and for eth0 put the config in /etc/network/interfaces  where you can define a mac address too :

 

auto eth0
iface eth0 inet static
address 192.168.xxx.x
gateway 192.168.xxx.x
netmask 255.255.255.0
dns-nameservers 8.8.8.8 8.8.4.4
hwaddress ether 11:22:33:44:55:66



2) in network-manager you must CLONE the actual mac address shown by ifconfig and it will be overwritten at every reboot with same mac address

content of /etc/NetworkManager/system-connections

 

[connection]
id=Wired connection 1
uuid=xxxxxxxx-xxxxxx-xxxxxxx-xxxxx-xxxxxxx
type=ethernet
autoconnect-priority=-999
interface-name=eth0
permissions=
timestamp=1586859373

[ethernet]
cloned-mac-address=C4:2A:FE:23:82:82
mac-address-blacklist=

[ipv4]
address1=192.168.xxx.x/24,192.168.xxx.x
dns=208.67.222.222;
dns-search=
may-fail=false
method=manual

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=ignore


put attention on the line cloned mac address and edit as per your needs
 

Link to post
Share on other sites
On 9/30/2020 at 11:19 PM, Alex83 said:

Can I also try to use ssv6x5x driver with ssv6051 chipset? 

Unfortunately not, the ssv6x5x is only for ssv6256p chip. People at SSV company are not very well acquainted with names and IDs, in fact they used the very same ID 3030:3030 for both ssv6051 and ssv6256p wifi chips and the driver name is also confusing (looking at ssv6x5x you may think it works for ssv6051 too, but it doesn't -_- )

 

On 9/30/2020 at 11:19 PM, Alex83 said:

BTW is there a solution for switching eth0 mac address after each reboot? 

Did you download the image you installed recently? This was a problem of u-boot and has been solved months ago. LibreELEC had the same issue, but has been fixed. If you use a fresh image you should get a stable MAC address.

Link to post
Share on other sites

Hey @jock, hey @fabiobassa, what's up? just from time to time come to this topic to see how is evolving all, never mind that I find some nice surprises and I miss them.

Actually to be honest, I cut short and betrayed the case with a 4 gb rasberry-pi 4 which for my jobs with the diy CNC that I built myself, and with the 3d printer with octoprint, is optimal, I admit that it is also convenient for browsing  and since the videos on youtube run in full hd without problems, and now that they have developed the Vulkan 3D drivers it's even better .. i noticed the big difference between armbian and raspberry pi os where the whole community is concentrated to make the software run better on those few existing hardware versions and I must say that in my opinion it is a good technique ... having all the same hardware it is easier to find bugs, to be fixed and there is a greater e solid stability between hardware and software.
While armbian focuses on trying to get the same os to work on the most varied arm-based hardware in existence, and it's a nice challenge that doesn't always succeed.
However, I admit that I enjoyed chatting on this channel, seeing the progress, and in a sense there is a small niche that has focused on these specific devices, which are actually a big deal, too bad the hardware and drivers creators are a bit stupid (or conveniently stupid for some obscure reason), they didn't directly decide to release good openosource drivers and made everything more complicated, the community would take care to keep them working well ..

Already, I just wanted to comment with my opinions based on the accumulated experience, and now I come here mostly for hobbies and fun, I would like to have more skills to make some contribution greater than just as a beta tester, or one who goes to try the luck in making things work, well I'd like to, but unfortunately it's not in my ability. :lol:

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

Unfortunately not, the ssv6x5x is only for ssv6256p chip. People at SSV company are not very well acquainted with names and IDs, in fact they used the very same ID 3030:3030 for both ssv6051 and ssv6256p wifi chips and the driver name is also confusing (looking at ssv6x5x you may think it works for ssv6051 too, but it doesn't -_- )

 

Did you download the image you installed recently? This was a problem of u-boot and has been solved months ago. LibreELEC had the same issue, but has been fixed. If you use a fresh image you should get a stable MAC address.

Hey, 

 

Thank you very much your explanation. I haven't tried the ssv6x5x driver. 

 

Actually I'm not sure yet if wifi mac changes every reboot or the eth0. 

 

I actually installed the newest image of you 20.08 legacy kernel. 

 

Is it maybe because I did it wrong with the option "burn flash to Rom"? But I didn't install the idbloader. It recommended not to install, so I didn't install it. 

 

As far as I understand @fabiobassahe also thinks we need the unclean workaround.

 

How can I actually get the real Mac address? It's not the one on the bottom of my box because I changed pcb once and did not write it down somewhere... 

 

In my experience with ifconfig I get after each reboot the different Mac addresses as it is recognized in my DHCP. 

Link to post
Share on other sites
2 hours ago, Alex83 said:

Is it maybe because I did it wrong with the option "burn flash to Rom"? But I didn't install the idbloader. It recommended not to install, so I didn't install it. 

Ahhh... right, I forgot you have NAND :rolleyes:

To make things work on NAND, it is needed to use the legacy u-boot which has not the right patch to make MAC address stable... so @fabiobassa workaround is the best way to go in your situation.

Link to post
Share on other sites

@nokirunner

ciao Nokirunner, you are half true half wrong

Is the starting point that is different , not the operating system

Raspberry is a single board computer that is BORN to be a computer so the kernel ( because we must speak about THIS, the userland part is just something that we can change as we want having the appropriate modules and libraries ....) is well supported in community and researches

mxq 4k pro, andowl tv box, shishion, hk1 mini etc etc etc are TVBOXES and it happened that thanks to some intuition, efforts, botta di culo even,  we discovered how to have a decent linux running on those evil things

Is not armbian or fedora for arm or even mageia for arm, is the lack of trustable documentation , as you said 
"conveniently stupid for some obscure reason" because have a 10 dollars SBC  to decently compete against more expensive boards could have done some market instability 
that is all ;-)

Link to post
Share on other sites

@fabiobassa  Yes I understand the hint, cheaper devices, cheaper support etc .. but what I don't understand, their modules being based on the linux kernel anyway, why don't they have a native release of the drivers sources?
They don't violate the Linux kernel GPL license ??
I noticed this also happens on other arm phones, due to their blob drivers, which then remain abandoned to old kernels which are difficult to update..

I also noticed that this happened more frequently in the past years .. now they tend to release drivers sources more easily to have them natively included in the linux kernel main line, maybe they have realized that it is more convenient for general maintenance, and to stay up to date with kernels with security and more.

Link to post
Share on other sites