Jump to content

CSC Armbian for RK322x TV box boards

jock

By jock
in Rockchip CPU Boxes

 Share

Recommended Posts

jock

jock

Posted
  • Author
Posted

@Khoa Nguyen

The kernel crash does not look specific to a device, but it is happening when a core exit the idle state handling an interrupt.

I suspect stability issues, so I suggest you these two things:

  • sun sudo rk322x-config and select rk3228a soc from the list. This limits the highest frequency to 1.2ghz
  • edit /boot/armbianEnv.txt and append cpu-stability to overlays= line

do both of them, then reboot the board and try again to install the desktop environment.

I have a board with similar issues like yours, and cpu-stability overlay solved my issues so far, I hope it solves yours too!

0
jock

jock

Posted
  • Author
Posted
  On 5/22/2021 at 8:21 PM, ArkhanLK said:

And second, the errors are in/with the armsoc install from media framework, because it changes some stuff with xorg, that makes it break. And this has nothing todo with lightdm because it was the first problem I had in first plance when first talked to you about it.

Expand  

The armsoc .deb package actually installs the armsoc X.org .so driver (the same as .dll in windows) and places armsoc.conf it in /etc/X11/xorg.conf.d to enable it.

 

Looking at the logs you provided I now see something that actually should not be there... a reference to "Lima" driver, which is not expected in non-mainline kernel... now I'm starting to understand that maybe you got 40-serverflags.conf in /etc/X11/xorg.conf.d directory. If so, remove that file and try again. I will double check this, because the way desktop packages are assembled changed recently in armbian and maybe I did a mistake with some configuration.

 

1
Khoa Nguyen

Khoa Nguyen

Posted
Posted
  On 5/25/2021 at 3:38 PM, jock said:

@Khoa Nguyen

The kernel crash does not look specific to a device, but it is happening when a core exit the idle state handling an interrupt.

I suspect stability issues, so I suggest you these two things:

  • sun sudo rk322x-config and select rk3228a soc from the list. This limits the highest frequency to 1.2ghz
  • edit /boot/armbianEnv.txt and append cpu-stability to overlays= line

do both of them, then reboot the board and try again to install the desktop environment.

I have a board with similar issues like yours, and cpu-stability overlay solved my issues so far, I hope it solves yours too!

Expand  

I edited armbianEnv.txt file, overlays= emmc led-conf1 cpu-stability, then reboot and tried install desktop interface but it still not work :( sometimes it crashed, sometimes it just freezed 

0
jock

jock

Posted
  • Author
Posted
  On 5/25/2021 at 4:46 PM, Khoa Nguyen said:

I edited armbianEnv.txt file, overlays= emmc led-conf1 cpu-stability, then reboot and tried install desktop interface but it still not work :( sometimes it crashed, sometimes it just freezed 

Expand  

Can't say anything more without further details. Please provide photos of the board (both sides), maybe the original dtb or the original firmware (or a link to a firmware upgrade supplied by manufacturer), the link provided by armbianmonitor -u command.

As already said, eMCP boards are quite unknown at the moment, so every detail is essential.

 

0
jock

jock

Posted
  • Author
Posted

@ArkhanLK

I made some further investigation and it seems that lightdm-gtk-greeter is the great offender: the package in Ubuntu Focal seems to be broken for armhf architecture: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1897491

 

I just tried to install the lightdm-autologin-greeter and uninstall lightdm-gtk-greeter and, after a reboot, it looks like it works: 

apt install lightdm-autologin-greeter && apt remove lightdm-gtk-greeter

 

If apt is lamenting issues about armsoc, that's because of a previous package upgrade. I don't know why, but it tries to install armsoc-exynos as a dependency of Kodi. It is unclear to me why it tries to install packaged Kodi instead of keeping the one from media-framework, but probably I made some mess with versioning.

 

However, to try to get back the media framework situation, first uninstall the wrong armsoc driver: 

apt remove xserver-xorg-video-armsoc

 

The install the media framework packages manually: 

apt install armsoc/*.deb

apt install kodi/*.deb

apt install ffmpeg/*.deb

 

And finally mark the packages as hold, so apt upgrade won't try to update them: 

apt-mark hold xserver-xorg-video-armsoc

apt-mark hold kodi kodi-addon-dev kodi-bin kodi-data kodi-tools-texturepacker

apt-mark hold ffmpeg libavutil56 libpostproc55 libswscale5 libavutil-dev libpostproc-dev libswresample3 libavresample4 libswscale-dev libavcodec58 libavcodec-dev libavresample-dev libavformat-dev libavfilter7 libavfilter-dev libavdevice58 libavdevice-dev

 

If you start from a fresh system, just run the apt-mark hold commands after installing the media framework and you should be fine enough.

 

This is not exactly tested, because I'm headless right now, so if you feel comfortable enough, it may be a wise idea to start from a fresh system.

I will update the media framework in the next days to include the apt-mark commands automatically, so this further step won't be needed.

 

edit: ah, another thing about /etc/X11/xorg.conf.d directory... The stable image from the download page include 40-serverflags.conf file which should not be there! Curiously a freshly built image by me instead does not include that file, which should be there only on mainline images... so please delete it. I will ask the high towers what happened, maybe fix the lightdm greeter thing and ask for a stable image rebuild.

1
ArkhanLK

ArkhanLK

Posted
Posted

Hi @jock ! Thanks for all the help and ways to fix and/or bypass these issues!

I took some time to replay back exactly as I was investigating it myself! And got to some findings similar to yours: the only thing I need to set as hold is the xserver-xorg-video-armsoc. The rest will update and upgrade just fine.

Doing this, I am able to run some stuff. The gears are working on glxgears. I manage to play quake 1 and 2 (tho I had to add some params, LD_LIBRARY_PATH=/opt/gl4es LIBGL_GL=15 LIBGL_FB=3 LIBGL_MIPMAP=3 LIBGL_FORCENPOT=1 LIBGL_FPS=1 LIBGL_POTFRAMEBUFFER=1 LIBGL_FORCE16BITS=1 quake2)

I also had to change one thing on the install media framework: allow downgrades. Some of the stuff there I had newer versions and the install would just stop. So, in order to avoid it, I allowed downgrades and then upgraded them. Some of the entries on the enxynos were right or interesting, so I merged them on the armsoc config and so far so good. All went ok! And I am still happily using the minimal image you compiled for me + lubuntu. It is working quite well!


I am now with 2 errors but I think they're unrelated to any of these events:
1. For the sake of it, I decided to take a look at armbianmonitor -v and got "It appears you may have corrupt packages.", pointing to "a symptom of filesystem corruption caused by SD cards or eMMC dying", which makes that first suggestion of yours to remain true, but also that it could be "burning the OS image to the installation media went wrong", which I don't think to be the case. It also says, "

The following changes from packaged state files were detected:

/usr/lib/arm-linux-gnueabihf/libgbm.so.1.0.0
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf"
Is this an entirely new problem or may have something to do with video and whatnot?
2. There is something wrong, I think, with the rk322x-config. When I select rk3229, the wifi doesn't work. If I choose rk3228a/b, everything works. Well, after I remove the emmc from overlays, that is. So, is this a thing you've noticed before? Actually, this might not be true. I just reverted the config the wifi is not turning on again! This is what I get from dmesg | grep ssv

  Quote

[    8.620941] redirect to /lib/firmware/ssv6051-wifi.cfg
[    8.624426] WARNING: CPU: 3 PID: 359 at drivers/net/wireless/rockchip_wlan/ssv6xxx/ssvdevice/ssvdevice.c:169 sta_cfg_set+0xc0/0x220 [ssv6051]()
[    8.624441] Modules linked in: lz4 lz4_compress ssv6051(+) mali snd_soc_rk3228 lzo zram sch_fq_codel ip_tables autofs4
[    8.624744] [<b00277c8>] (warn_slowpath_null) from [<af0a5b00>] (sta_cfg_set+0xc0/0x220 [ssv6051])
[    8.624900] [<af0a5b00>] (sta_cfg_set [ssv6051]) from [<af08a4b4>] (ssvdevice_init+0xf4/0x12c [ssv6051])
[    8.625051] [<af08a4b4>] (ssvdevice_init [ssv6051]) from [<af0a59c4>] (initWlan+0x40/0x8c [ssv6051])
[    8.625187] [<af0a59c4>] (initWlan [ssv6051]) from [<af0bf020>] (generic_wifi_init_module+0x20/0x1000 [ssv6051])
[    8.625278] [<af0bf020>] (generic_wifi_init_module [ssv6051]) from [<b0009a68>] (do_one_initcall+0xa0/0x1f8)
[    8.625808] ssv6xxx_sdio_init
[    8.626181] ssv6xxx_set_sdio_clk:set sdio clk 25000000Hz
[    8.725161] ssv6xxx_sdio_power_on
[    8.745760] ssv6xxx_dev_probe(): ssv6200 device found !
[    8.746030] WARNING: CPU: 0 PID: 359 at drivers/net/wireless/rockchip_wlan/ssv6xxx/smac/init.c:1471 ssv6xxx_dev_probe+0x2b8/0x1c70 [ssv6051]()
[    8.746045] Modules linked in: gpio_ir_recv lz4 lz4_compress ssv6051(+) mali snd_soc_rk3228 lzo zram sch_fq_codel ip_tables autofs4
[    8.746278] [<b00277c8>] (warn_slowpath_null) from [<af0910a4>] (ssv6xxx_dev_probe+0x2b8/0x1c70 [ssv6051])
[    8.746409] [<af0910a4>] (ssv6xxx_dev_probe [ssv6051]) from [<b066b11c>] (platform_drv_probe+0x60/0xbc)
[    8.746626] [<b066af34>] (platform_device_add) from [<af0aa34c>] (ssv6xxx_sdio_probe+0x358/0x3bc [ssv6051])
[    8.746743] [<af0aa34c>] (ssv6xxx_sdio_probe [ssv6051]) from [<b09011a8>] (sdio_bus_probe+0x9c/0x12c)
[    8.746954] [<b09013f8>] (sdio_register_driver) from [<af0a9e08>] (ssv6xxx_sdio_init+0x2c/0x30 [ssv6051])
[    8.747120] [<af0a9e08>] (ssv6xxx_sdio_init [ssv6051]) from [<af08a4d8>] (ssvdevice_init+0x118/0x12c [ssv6051])
[    8.747276] [<af08a4d8>] (ssvdevice_init [ssv6051]) from [<af0a59c4>] (initWlan+0x40/0x8c [ssv6051])
[    8.747413] [<af0a59c4>] (initWlan [ssv6051]) from [<af0bf020>] (generic_wifi_init_module+0x20/0x1000 [ssv6051])
[    8.747497] [<af0bf020>] (generic_wifi_init_module [ssv6051]) from [<b0009a68>] (do_one_initcall+0xa0/0x1f8)
[    8.747666] SSV WLAN driver ssv6200: Failed to initialize device
[    8.747748] SSV WLAN driver: probe of ssv6200 failed with error -12

Expand  

Well, I ran a bunch of stuff from armbian-config and it is working again... Here is the last log:

  Quote

[    8.528862] redirect to /lib/firmware/ssv6051-wifi.cfg
[    8.570261] ssv6xxx_sdio_init
[    8.572794] ssv6xxx_set_sdio_clk:set sdio clk 25000000Hz
[    8.646940] ssv6xxx_sdio_power_on
[    8.669819] ssv6xxx_dev_probe(): ssv6200 device found !
[    8.693045] ssv6xxx_sdio_irq_disable
[    8.755147] SSV WLAN driver ssv6200: Crypto task 448 running with priority 120.
[    8.757019] SSV WLAN driver ssv6200: Crypto task 449 running with priority 120.
[    8.765543] SSV WLAN driver ssv6200: Crypto task 450 running with priority 120.
[    8.777224] SSV WLAN driver ssv6200: Crypto task 452 running with priority 120.
[    8.839754] ieee80211 phy0: Selected rate control algorithm 'ssv6xxx_rate_control'
[   29.168139] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[   29.316423] Firmware "/lib/firmware/ssv6051-sw.bin" loaded
[   29.424934] Firmware name sh->cfg.firmware_path=/lib/firmware/ssv6051-sw.bin
[   29.425524] ssv6xxx_watchdog_controller 6
[   29.448922] ssv6xxx_sdio_irq_enable
[   29.615759] ssv6200_start(): current channel: 1,sc->ps_status=0
[   29.619391] ssv6200_add_interface(): vif->type = 2, NL80211_IFTYPE_AP=3
[   29.619420] ssv6xxx_config_vif_res id[0].
[   29.619444] SSV WLAN driver ssv6200: VIF a4:7d:9f:31:c7:74 of type 2 is added.
[   29.620244] ssv6200_bss_info_changed(): leave
[   29.621807] ssv6200_bss_info_changed(): leave

Expand  



And my main question is: assuming I can make it all work nice and well... Can I "clone" this system and install on another box exactly equal to this one? Like, if I go to multitool and do a "backup" then try to install this on a different box, will it work? I suppose the only way would be to compile a image of my system, but using the multitool would be so much easier, haha.
 

  On 5/25/2021 at 4:46 PM, Khoa Nguyen said:

I edited armbianEnv.txt file, overlays= emmc led-conf1 cpu-stability, then reboot and tried install desktop interface but it still not work :( sometimes it crashed, sometimes it just freezed 

Expand  

And hey, @Khoa Nguyen , maybe I'm mistaken and should not be giving advice as I'm very noob, but I think your overlays is still wrong. You have to remove the word "emmc" from it entirely. At least, for me, that's the only way it works...

0
jock

jock

Posted
  • Author
Posted
  On 5/27/2021 at 9:32 PM, hexdump said:

@jock - just in case: the slick greeter is also working well on armhf

Expand  

Yeah I wanted to mention in the previous post but I forgot!

However today had access to the box and it was still not logging in. I'll check further later, but this lightdm thing is very annoying <_<

  On 5/28/2021 at 1:47 AM, ArkhanLK said:

For the sake of it, I decided to take a look at armbianmonitor -v

Expand  

Uh, to be honest I never tried armbianmonitor -v. Actually the packages installed by media framework are "overwriting" those from armbian/ubuntu, I don't really know how armbianmonitor -v reacts to.

 

  On 5/28/2021 at 1:47 AM, ArkhanLK said:

There is something wrong, I think, with the rk322x-config. When I select rk3229, the wifi doesn't work. If I choose rk3228a/b, everything works. Well, after I remove the emmc from overlays, that is. So, is this a thing you've noticed before? Actually, this might not be true. I just reverted the config the wifi is not turning on again! This is what I get from dmesg | grep ssv

Expand  

rk3228b and rk3229 are enabling exactly the same overlay, which brings the cpu to 1.4ghz, nothing else.

emmc overlay enabled the ddr mode for eMMC and some other configuration bits. eMMC, sdcard and Wifi share the same subsystem since they are all controlled by mmc controllers, so it is very possibile that a malfunction/misconfiguration on eMMC reflects also over Wifi; usually badly designed boards do this.

 

  On 5/28/2021 at 1:47 AM, ArkhanLK said:

And my main question is: assuming I can make it all work nice and well... Can I "clone" this system and install on another box exactly equal to this one? Like, if I go to multitool and do a "backup" then try to install this on a different box, will it work? I suppose the only way would be to compile a image of my system, but using the multitool would be so much easier, haha.

Expand  

Usually it will work fine even if the board is slightly different; you can however clone the thing and, if it boots, run rk322x-config to reconfigure the overlays for the other board

1
ArkhanLK

ArkhanLK

Posted
Posted
  On 5/28/2021 at 7:49 AM, jock said:

 Usually it will work fine even if the board is slightly different; you can however clone the thing and, if it boots, run rk322x-config to reconfigure the overlays for the other board

Expand  

Oh, that's very cool to know! It will be very helpful if it works this way indeed ^^

 

One thing I noticed but haven't looked into yet: kodi is installing without the "install from repositories option", so I can't really use it... I will try to reinstall or something. But I have encountered this error on 2 or 3 other times when I freshly installed everything... Only once, so far, I managed to install Kodi and it actually worked well (at least on twitch I could watch normally at 720p).

0
ArkhanLK

ArkhanLK

Posted
Posted
  On 5/29/2021 at 9:21 AM, jock said:

@ArkhanLK I confirm that slick-greeter is a much better choice, X.org now works and I'm able to login finally!

Expand  

HI @jock! I tried slick-greeter with icewm and that was super fast! Very nice, but not that user friendly. But, you know, consumed 120mb ram to have it up and running, so very decent choice for limited boards!

 

Also, I figured out a solution for the kodi part on the media framework: hold on 3 packages only: xserver-xorg-video-armsoc, kodi, and kodi-bin. But the other packages don't need the hold. Tested on twitch, 1080p smooth! 

 

I am now going to test kodi and lxde... Should be faster and lighter than both xfce and lxqt! 

 

I will keep you all updated o/

Thanks for the incredible support!!! 

1
beretas

beretas

Posted
Posted

Sorry for late reply.

For the record: MXQ PRO 4K 5G, announced on sitck as 4GB Ram, 32GB ROM, Rk3229. Inside it was Rk3228A, 1GB DDR3L Ram and 8GB NAND ROM of unknown chinesse manufacturer.

 

@jock definitely, Nand is not detected with multitool, only armbian can be loaded from SD Card after erasing Nand.

 

  for the record or anyone with same system:

 1.- Rom detection with rkdeveloptool:

rkdeveloptool rfi
Flash Info:
    Manufacturer: SAMSUNG, value=00
    Flash Size: 7301 MB
    Flash Size: 14952960 Sectors
    Block Size: 16384 KB
    Page Size: 16 KB
    ECC Bits: 40
    Access Time: 32
    Flash CS: Flash<0>

  2.- Flash cant be erased directly, on new system, if you do "rkdeveloptool ef" it writes: "Starting to erase flash..." and got stuck there, blocked, forever (i waited 24h, think its enough). So working method to get flash erased, its:

 

   rkdeveloptool wl 0x4000 u-boot-main.img (you can download and check command on first post)
      Write LBA from file (100%)

 

  after it, disconnect and reconnect again with the toothpick and Male-Male usb again. I tried to do "rkdeveloptool rd 3" which is supposed to reset device on MaskRoom mode, it responds: "Reset Device OK." but things cant be done, with errors like: "Getting flash info from device failed!".  So after writing u-boot, disconnect and reconnect.

   

    rkdeveloptool ef
       Erasing flash complete.

 

  after it, plug SD card with Armbian and it boots ok. NAND is not useable from it, as it recognizes but can be accessed.

  if it helps someone, loading system with thoothpick method and Male-Male usb gives this result also:

 

    rkdeveloptool ld
       DevNo=1    Vid=0x2207,Pid=0x320b,LocationID=301    Loader

 

Hope this helps someone.

Best Regards,

Beretas

 

 

 

0
jock

jock

Posted
  • Author
Posted
  On 6/2/2021 at 3:19 AM, beretas said:

I tried to do "rkdeveloptool rd 3" which is supposed to reset device on MaskRoom mode, it responds: "Reset Device OK." but things cant be done, with errors like: "Getting flash info from device failed!".  So after writing u-boot, disconnect and reconnect.

Expand  

 

It is right that after rkdeveloptool rd 3 you are not able to execute any other command: that's because the board is in maskrom mode.

Once there, you must run rkdeveloptool db loader.img to have access to further commands.

When done, rkdeveloptool ef will clean the existing data, and finally you need also upgrade_tool binary to finally install the new bootloader in the NAND.

 

This is the procedure to upgrade to NAND bootloader:

https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/page/28/?tab=comments#comment-121103

 

 

If you don't install a bootloader, you will never be able to boot from NAND neither the Multitool will detect it.

 

 

0
beretas

beretas

Posted
Posted

@jock

 

   don't know if i did it as it should, but upgrade_tool was giving me an error:

 

upgrade_tool ul rk322x_loader_v1.10.256.bin
Not found config.ini
Program Data in /home/me/rkbin/tools
Loading loader...
Support Type:RK322A    Loader ver:2.56    Loader Time:2021-03-13 16:06:57
Prepare IDB Fail

 

so checked:

rkdeveloptool ld
DevNo=1    Vid=0x2207,Pid=0x320b,LocationID=301    Maskrom

 

and did:

rkdeveloptool ul rk322x_loader_v1.10.256.bin

Upgrading loader succeeded.

 

armbianmonitor -U

  Reveal hidden contents

 

 

0
RaptorSDS

RaptorSDS

Posted
Posted

@jock i have a small request is it possible to get a 4 led config ?

i got with

 

Ledconfig 1 -power =first red than red and blue on  ( i thing its not good for Led)

                   -kernel =  blue on 

                  -power off = red and blue on 

ledconfig 2 -power =red on

                 -kernel = red on ,blue disk work status

                -power off = red on

ledconfig3 -power = red on

                 -kernel = red off , blue off

              

 

my request

 

ledconfig4 power= red on

                 kernel = red off, blue on

 

 

also after ledconfig3 the box did not get back to ledconfig1 mode at reboot only with power off

ledconfig3  to ledconfig2 work with reboot

0
jock

jock

Posted
  • Author
Posted

@beretas Can't say anything about upgrade_tool error. I have only one board with NAND and it always worked so far. I asked @fabiobassa to do some tests with his NAND board and AFAIK it worked there too.

rkdeveloptool ul with NAND boards often tell you everything went well, but does not always work (on my board it does not do anything).

 

Did you try the other bootloaders available in the instructions post? Do you have any serial log?

0
jock

jock

Posted
  • Author
Posted

@RaptorSDS

The led configurations are not for intended as on/off switches, you should use the one and only that is suitable for your board because the led GPIO pins changes among boards (ie: the leds are connected to different "ports" on the SoC). You have to spot the led configuration that works for your board, or just read the board signature and find a match in rk322x-config proposals.

 

Once you do that, the leds can be controlled independently via /sys/class/leds/working and /sys/class/leds/auxiliary sysfs paths.

By default the working led is set to stay always on and auxiliary is set to blink when there is MMC access, but you can change writing into trigger file you find in those paths. Use cat trigger to show the list of possible values that you can write into and search google for documentation.

 

 

0
Luiz Rocha

Luiz Rocha

Posted
Posted

Hi everyone, I've been following this topic for a while. I've been working with environment settings for a few years and I'm really enjoying these single board computers (raspberry, banana, orange). And reading your content, I decided to purchase a rock-chip rk3228a. I tried to change the ROM of it, but I was unsuccessful.

 

https://photos.google.com/share/AF1QipPl7CExQWOgwruHVVWZplC76vnzXTkNJpeCMlNMQdqSTPExIVibc5hO6v2LXVq9kQ?key=VzBQUTk4ZFk3a3VRZjhjQVZzRHNYLWxTMS1NQU13

 

Can anyone help? I shared the photos from the tv box on the link above.

0
fabiobassa

fabiobassa

Posted
Posted

@Luiz Rocha

 

  Quote

"I tried to change the ROM of it"

Expand  

if you speak about android rom  this isn 't the right place since here we discuss about linux-armbian on those board

If you instead speak of linux-armbian you are in the right place but apart from photos you didn't describe what the problem is ( no boot ? - have you a uart , have you logs ?)

0
Luiz Rocha

Luiz Rocha

Posted
Posted
  On 6/11/2021 at 8:44 AM, fabiobassa said:

@Luiz Rocha

 

if you speak about android rom  this isn 't the right place since here we discuss about linux-armbian on those board

If you instead speak of linux-armbian you are in the right place but apart from photos you didn't describe what the problem is ( no boot ? - have you a uart , have you logs ?)

Expand  

 

I did the procedures using multitool.img and couldn't find eMMC, so I tried to enter maskrom mode and change the linux-armbian image. My machine is Ubuntu 20.04.2 LTS, I believe that I have not properly installed rkdeveloptool and upgrade_tool or even has an old version including multitool.img.
What official repository are you using on github or gitlab? Where can I download updated versions of this project to try again to switch to linux-armbian?

0
ArkhanLK

ArkhanLK

Posted
Posted

Hi everyone, I'm doing really well on the board I have! I am sure this is a really capable board! 

 

So far I have:

. Played emulator games and some old/retro games such as quake 1, 2, and doom;

. Web-browesed on Firefox to almost any website (netflix doesn't work, some issues with google meet as well);

. Edited photos and pdf with gimp, libreoffice draw, kolourpaint... Flawlessly!;

. Draw 2d cad with librecad and will be testing leocad soon!;

. When videos work, like in YouTube or twitch, I can watch them decent at 480p, very decent at 360p;

. Watched 1080p on kodi (at least on twitch), but the other services (Amazon, Netflix, Disney, YouTube...) I wasn't able to try yet. 

 

Overall, this makes for a REALLY good and cheap basic desktop.

 

But just to be sure, let me ask something: is there any way to dual boot with android + armbian? That'd be possible with, I suppose, partitioning the emmc... I am aware that there is a way to install linux in Android and then ssh into it. But that's not the same thing I'm asking about!

 

As always, thanks a lot for the help and support here. You guys are awesome. Much love <3 

1
jock

jock

Posted
  • Author
Posted

@ArkhanLK Glad you're finding the box useful and thanks for reporting! ;)

Netflix and friends usually have other issues related to Digital Rights Management, but never really dig into. I know that on LibreELEC you need to download the Widevine plugin.

 

@jaum20 It should be already enabled, but honestly I never checked the coaxial SPDIF output. Will check right now ;)

edit: just checked on both mainline and legacy kernel and it is working fine up to 192khz! Maybe you need to tell pulseaudio to use SPDIF (IEC958) from the speaker icon in the upper right corner

3
fabiobassa

fabiobassa

Posted
Posted

@ArkhanLK

ad Jock already said is not a problem of the soc per se , but netflix and other need DRM and this must be enabled in some way as libreelec already did.
I am very but very happy that you found this little black box usefull, I use plenty of those for the most wide purposes

1
ArkhanLK

ArkhanLK

Posted
Posted

Thanks @jock and @fabiobassa!

 

Yeah, it is partially due to these limitations and also the limitations of how I am currently using Kodi that I am trying that dual boot alternative. You guys don't happen to know anything about it, do you?

 

Even if it'd mean run android on eMMC and Linux from the sdcard, it'd still be very helpful!


If things keep running as they are, I think I can turn this into a product soon enough - and then help with donations! ^^

0
jock

jock

Posted
  • Author
Posted
  On 6/15/2021 at 6:30 PM, ArkhanLK said:

Thanks @jock and @fabiobassa!

 

Yeah, it is partially due to these limitations and also the limitations of how I am currently using Kodi that I am trying that dual boot alternative. You guys don't happen to know anything about it, do you?

 

Even if it'd mean run android on eMMC and Linux from the sdcard, it'd still be very helpful!


If things keep running as they are, I think I can turn this into a product soon enough - and then help with donations! ^^

Expand  

Running android from eMMC and Linux from sdcard is very possible, LibreELEC does that, but also the multitool works that way also.

Armbian images are not provided in that way for very specific reason:

  • support is more difficult since we can't know what kind of software (bootloader version, ddrbin, etc...) booted the box
  • extended boot features (like USB boot or network boot) are impossible to implement
  • plenty of outdated binary blobs are involved (you don't know what happens in that code)
  • limited speed for DDR ram memories in mainline kernel

Since Armbian is intended for general and stable usage and work is done towards the mainline kernel, the "dual boot" choice has been dropped almost instantly.

 

1
RaptorSDS

RaptorSDS

Posted
Posted

i do not know if something change in last apt upgrade for rk332x root or image but i got today kernel faults and emmc problem

 

emmc problems like the one i report when i config emmc in armbianEnv.txt

 

my box tell me 398% CPU usage

 

kernel panic

 kernel:[  519.498786] Internal error: Oops: 805 [#1] PREEMPT SMP ARM

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.645677] Process kworker/0:3 (pid: 1159, stack limit = 0x6b325425)

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.652911] Stack: (0xb38ffc80 to 0xb3900000)

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.657808] fc80: 200e0013 00000001 b38ffcac b38ffc98 b103e600 b01879f4 b1d04938 00000001

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.667000] fca0: b38ffcd4 b38ffcb0 b089a0d0 b103e5f0 ffffffff b0899f80 00000001 b38ffd08

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.676192] fcc0: b1d11824 00000000 b38ffd04 b38ffcd8 b014ba44 b0899f8c b1d05b40 b1d11800

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.685385] fce0: b1780e90 b1c05e40 b1606808 00000001 00000000 b4737080 b38ffd3c b38ffd08

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.694577] fd00: b088ce80 b014b9d8 b1d05b40 23c34600 30a32c00 d4a8b198 b088f660 b1c05e40

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.703770] fd20: b1c05e40 00000000 00000001 b1c05300 b38ffd5c b38ffd40 b088cf4c b088ce04

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.712962] fd40: b1c05e40 b1c05240 00000000 00000001 b38ffd7c b38ffd60 b088cf10 b088ceb0

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.722155] fd60: b1c05240 b1c05300 00000000 00000001 b38ffd9c b38ffd80 b088cf10 b088ceb0

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.731348] fd80: b1d1ca80 b1606808 30a32c00 30a32c00 b38ffddc b38ffda0 b0892dd4 b088ceb0

Message from syslogd@rk322x-box at Jun 17 21:45:02 ...
 kernel:[  519.740539] fda0: 30a32c00 00000000 ffffffff 30a32c00 b1d04000 d4a8b198 b38ffddc b30fadc0

 

 

 

 

 

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.592688] [<b0892e54>] (clk_set_rate) from [<b0c21ae0>] (dev_pm_opp_set_rate+0x28c/0x588)

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.602072]  r5:30a32c00 r4:b81ae800

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.606113] [<b0c21854>] (dev_pm_opp_set_rate) from [<af0970a4>] (set_target+0x38/0x3c [cpufreq_dt])

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.616380]  r10:00000000 r9:00000000 r8:00000001 r7:00000000 r6:b18a0a8c r5:b1606808

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.625174]  r4:b48c2200

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.628042] [<af09706c>] (set_target [cpufreq_dt]) from [<b0c277d8>] (__cpufreq_driver_target+0x1bc/0x540)

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.638895] [<b0c2761c>] (__cpufreq_driver_target) from [<b0c2b7d0>] (cs_dbs_update+0xd8/0x14c)

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.648674]  r10:b1800a20 r9:00000000 r8:b4a6f5c0 r7:b4a73600 r6:000cd140 r5:b48c2200

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.657469]  r4:b4a73100

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.660334] [<b0c2b6f8>] (cs_dbs_update) from [<b0c2bd44>] (dbs_work_handler+0x3c/0x64)

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.669333]  r9:00000000 r8:b17c03e0 r7:b48c2200 r6:b4a73104 r5:00000000 r4:b4a73148

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.678047] [<b0c2bd08>] (dbs_work_handler) from [<b0142bc4>] (process_one_work+0x224/0x60c)

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.687535]  r9:00000000 r8:00000000 r7:eedd7d00 r6:eedd4980 r5:b1fcd280 r4:b4a73148

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.696254] [<b01429a0>] (process_one_work) from [<b0143018>] (worker_thread+0x6c/0x584)

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.705354]  r10:eedd4980 r9:b1604900 r8:eedd49a4 r7:00000008 r6:eedd4980 r5:b1fcd294

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.714151]  r4:b1fcd280

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.717017] [<b0142fac>] (worker_thread) from [<b014a12c>] (kthread+0x19c/0x1b4)

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.725335]  r10:b1de1e68 r9:00000000 r8:b1fcd280 r7:b0142fac r6:b3096000 r5:b1fe7000

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.734130]  r4:b1fcd200

Message from syslogd@rk322x-box at Jun 17 22:03:33 ...
 kernel:[   63.736993] [<b0149f90>] (kthread) from [<b0100148>] (ret_from_fork+0x14/0x2c)

0
jock

jock

Posted
  • Author
Posted

@RaptorSDS No particular updates recently. If you're on legacy kernel, it is the same 4.4.194 kernel as it was long ago.

Mainline kernel still should be a subversion of 5.10

 

Can't say anything about, I just see a kernel panic but can't say if it is related to emmc.

Maybe it is just a "common" stability issue of the board due to crap quality.

0
RaptorSDS

RaptorSDS

Posted
Posted

i am on mainline kernel 5.10

 

i had befor set cpu from 400MHz to limit 1.2GHz max  -> to limit thermal output

after that kernel panic i switch back to 600Mhz to 1.39GHz ( after kernel panic armbian-config has no 400Mhz option) now its little bit better

(could a app like php3 , nginx, mariadb do a kernel panic  like above ? )

 

but i hope i will not be get worse

 

 

0

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept