CSC Armbian for RK322X TV Boxes


Recommended Posts

vor 7 Stunden schrieb ArkhanLK:

But I am struggling with videos. I tried using Focal Legacy but it is not worth it, it's just too slow.

  1. Is there a way to use your media framework on Debian legacy? I tried but it doesn't install.
  2. Also, if it is not too much to ask, is there a trusty tutorial on overclocking the CPU/GPU/RAM? It may not be worth it nor make a significant difference, but then again it might!

</questions><tip>
I even might have something to add: running the rk322x-config is a MUST to enable the ssv6051p. However, regardless of what I choose, it will always force me back to a "UUID=xxx does not exist Dropping to a shell" boot error (and I tried a shit ton of combinations...). Yet, I figured out that if I edit "/boot/armbianEnv.txt" right after running rk322x-config and delete whatever "overlays" line is there, I "fix" it: Wi-Fi works and I can boot normally! Not a single clue as to why it happens, but hope this can help someone...</tip>

 

for 2 i do other way i underclock the cpu because of my opinion too hot cpu

@jock i got my box to a 100% load on all 4 cores  from bug webservice its run at 85 degree stable with 1.2Ghz ( i dont know why last time ( first time with linux after switch from android) at 75 degree the box freeze and short after black screen maybe it wasnt a thermal problem .

 

for 3.

i have same problem with UUID , but for me its was only to delete the emmc or nand or emmc-nand part from the armbianENV, the rk3229 and the ledconfig1  parts work great.

 

 

 

 

 

 

 

 

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

8 hours ago, ArkhanLK said:

<thanks>

Hey @jock, let me start by saying I love you. Thank you so much for this. I know it is not only you, but still: huge thanks!</thanks>

Thanks a lot, this makes the job worth it ^_^ You're right, that's not just me behind this, so I share the greetings with all the people that helped in this thread!

 

8 hours ago, ArkhanLK said:

But I am struggling with videos. I tried using Focal Legacy but it is not worth it, it's just too slow.

You can still use Focal Legacy and configure icewm desktop manager even if the image comes preinstalled with xfce, performance should be the same as debian.

8 hours ago, ArkhanLK said:

Is there a way to use your media framework on Debian legacy? I tried but it doesn't install.

Unfortunately I didn't try on debian. Roughly it should be possible to make it run on, but the package names to resolve the library dependencies changes, so the media packages should be adapted. It was a bit hard to find and fix dependencies, I'm no .deb specialist at all.

Also Debian Buster comes with some very old packages that should be recompiled and installed manually... it's a bit of headache <_<

You can extract the script and install each .deb packages manually using apt-get (apt-get install ./the-package.deb), but I don't really know if it brings you anywhere.

The new developments on the mainline kernel brings new life to hardware decoding and acceleration, but things are still settling down, as you may notice with the release of the first beta versions of LibreELEC 19 and Kodi Matrix: actually I managed to get hardware acceleration work fine on mainline kernel, but the process still requires patching and manual compilation of ffmpeg and Kodi, so there still is some time to wait for.

8 hours ago, ArkhanLK said:

Also, if it is not too much to ask, is there a trusty tutorial on overclocking the CPU/GPU/RAM? It may not be worth it nor make a significant difference, but then again it might!

Ah, no there is not any tutorial I know about for that, but IMHO it does not really worth it.

CPU and GPU can be overclocked easily editing the device tree, finding the opp tables (OPerating Points), and modifying frequency and voltages. I don't recommend it, the improvement is very modest at the expense of much greater heat production.

Unfortunately the CPU is a Cortex-A7, a very old 32 bit only architecture made to do cheap tv boxes. The SoC has dedicated hardware decoding blocks, which are nice, but the hardware specs are minimal for the current standards. It is perfect for some home server things although (network router, NAS, VPN endpoint, dns cache/hole, etc...)

 

edit: about the boot issue, follow the @RaptorSDSadvice to remove the emmc word from overlays= line in /boot/armbianEnv.txt, or just select emmc-nand in rk322x-config.

Link to post
Share on other sites
23 minutes ago, RaptorSDS said:

@jock also emmc-nand produce the error ,  i can boot only    without any of the 3 settings

Yeah, you're right, the emmc-nand overlay also enables the DDR mode... I forgot I added that thing there too.

Need to fix that in rk322x-config to be more clear about.

Link to post
Share on other sites
Posted (edited)

Hello again @jock! Sorry to bother you, but I think I need your help.

I am now trying to compile a Legacy image of Focal from a Hirsute installation. I followed the steps on https://docs.armbian.com/Developer-Guide_Build-Preparation/ and also on the readme.md after cloning it from github.

 

Yet, I am hitting a wall:

 

Displaying message: Writing U-boot bootloader /dev/loop7 info
Displaying message: ERROR in function write_uboot image-helpers.sh:103 err
Displaying message: U-boot bootloader failed to install @host err
Displaying message: Process terminated  info
Displaying message: Unmounting /home/vfc/build/.tmp/rootfs-9076d4b8-0752-4066-a923-83663ba0dd49/ info
Displaying message: ERROR in function unmount_on_exit image-helpers.sh:65 err
Displaying message: debootstrap-ng was interrupted  err
Displaying message: Process terminated  info


If you'd like the whole log, https://drive.google.com/file/d/1xJJeDkvJchjWXxXu7hWdi9G-yyDeMQYM/view?usp=sharing (sorry it's on gdrive, I wasn't sure on how to do this properly).
 

Thanks once more!

 

P.S.: @Igor, first of all, thanks a lot for the work you've done. I see you helping people all the time, too. I noticed that this is "your tool", so maybe I should ask you about the error? Thanks in advance! 

Edited by ArkhanLK
Link to post
Share on other sites

Hi,

I am sorry if it was already answered, but I've searched the forums and couldn't find an answer.

I'm trying to burn Armbian for the first time, but i cant flash it for some reason. 

 

My device is MXQ 4k Pro 5G (RK3228A, eMMC).

 

I've burned the image of Multitool on an SD card, then i placed the image of Armbian in the "images" folder, and then i placed the SD card in my box and connected it to the electricity. Multitool loaded fine, and i can see the main blue menu with options such as backup/restore/erase/etc 

 

When choosing the "Burn image to flash" in Multitool, i get a message saying:

"There are no eMMC devices suitable for image burn".

I actually get this message also when trying the Erase option or any other option in Multitool.

 

How do i overcome this?

 

Much appreciated 😊

 

20210512_232802.jpg

Link to post
Share on other sites
35 minutes ago, fabiobassa said:

@gnusmag45 

read again the 3ad , all infos, you will see that  some boards came with NAND and not EMMC and I guess this is your case.
You should follow the STEP-NAND instructions instead and see if this fits to you

Thanks,

 

I've opened the box and looked at the memory chip and googling it shows it is eMMC (Micron Part number 4QA98 JWA60).

 

I read everything multiple times, and the instructions for NAND say to first use the Erase option in Multitool, but this option doesn't work for me either (even if we assume mine has NAND), so im not sure how to progress from here.

 

* I apologize in advance if i overlooked or missed understand any of the instructions as English is not my native language

 

20210512_234242.jpg

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

Hello again @jock! Sorry to bother you, but I think I need your help.

I am now trying to compile a Legacy image of Focal from a Hirsute installation. I followed the steps on https://docs.armbian.com/Developer-Guide_Build-Preparation/ and also on the readme.md after cloning it from github.

 

Yet, I am hitting a wall:

 


Displaying message: Writing U-boot bootloader /dev/loop7 info
Displaying message: ERROR in function write_uboot image-helpers.sh:103 err
Displaying message: U-boot bootloader failed to install @host err
Displaying message: Process terminated  info
Displaying message: Unmounting /home/vfc/build/.tmp/rootfs-9076d4b8-0752-4066-a923-83663ba0dd49/ info
Displaying message: ERROR in function unmount_on_exit image-helpers.sh:65 err
Displaying message: debootstrap-ng was interrupted  err
Displaying message: Process terminated  info


If you'd like the whole log, https://drive.google.com/file/d/1xJJeDkvJchjWXxXu7hWdi9G-yyDeMQYM/view?usp=sharing (sorry it's on gdrive, I wasn't sure on how to do this properly).
 

Thanks once more!

 

P.S.: @Igor, first of all, thanks a lot for the work you've done. I see you helping people all the time, too. I noticed that this is "your tool", so maybe I should ask you about the error? Thanks in advance! 

Hello @ArkhanLK, be aware of this:

Quote

The officially supported compilation environment is Ubuntu Focal 20.04.x amd64 only!

 

so everything else is a moving target. The tools may work differently on other distributions, with subtle bugs or even build failures, so it is preferable to support a single distro and support it well.

Personally, I have my 100Gb Ubuntu Focal 20.04 Server virtual machine to do such jobs.

Link to post
Share on other sites
45 minutes ago, gnusmag45 said:

After 20 tries i finally managed to select the Erase option from the Multitool and it actually let me select the eMMC partition, but afterwards i restarted the box and now it doesn't boot anymore :/ wth

Hi @gnusmag45, I'm sorry you are having issues with your board. I hope the multitool still boots after you erased the flash :(

Unfortunately your board has an eMCP, which is a chip that contains both the eMMC and the DDR memory. I never had the chance to test a board with such chip by myself, so it is totally guesswork.

 

The multitool has a dtb which is usually very compatible because it does not use any "advanced" features of the board, and also uses lower operating frequencies to maximize compatibility at the expense of performance. Something does not work for your board although.

 

I edited the device tree of the multitool to provide more current strength to the eMMC pins and also some other configuration that may be of some benefical effect for your board.

 

This is the dtb: rk322x-box-emcp.dtb.

Put it in the root directory of the multitool, then edit the the file extlinux/extlinux.conf and change the existing rk322x-box.dtb with this rk322x-box-emcp.dtb.

Save the conf file and try again to boot the multitool. Check if after some reboots the flash memory is detected consistently, maybe make a backup to "stress" it and see if the backup is completed correctly, but don't install any armbian image yet.

 

I suggest you to first try to burn an Armbian image directly on the sdcard and boot armbian from sdcard. This may let you upload a full set of logs (via armbianmonitor -u) to the internet and let us inspect them before proceeding to install the image on the eMMC.

Also check if the eMMC is correctly detected within Armbian after some reboots: it is important that the kernel detects it otherwise even if you install Armbian on eMMC it won't boot anyway.

Link to post
Share on other sites
11 minutes ago, jock said:

Hi @gnusmag45, I'm sorry you are having issues with your board. I hope the multitool still boots after you erased the flash :(

Unfortunately your board has an eMCP, which is a chip that contains both the eMMC and the DDR memory. I never had the chance to test a board with such chip by myself, so it is totally guesswork.

 

The multitool has a dtb which is usually very compatible because it does not use any "advanced" features of the board, and also uses lower operating frequencies to maximize compatibility at the expense of performance. Something does not work for your board although.

 

I edited the device tree of the multitool to provide more current strength to the eMMC pins and also some other configuration that may be of some benefical effect for your board.

 

This is the dtb: rk322x-box-emcp.dtb.

Put it in the root directory of the multitool, then edit the the file extlinux/extlinux.conf and change the existing rk322x-box.dtb with this rk322x-box-emcp.dtb.

Save the conf file and try again to boot the multitool. Check if after some reboots the flash memory is detected consistently, maybe make a backup to "stress" it and see if the backup is completed correctly, but don't install any armbian image yet.

 

I suggest you to first try to burn an Armbian image directly on the sdcard and boot armbian from sdcard. This may let you upload a full set of logs (via armbianmonitor -u) to the internet and let us inspect them before proceeding to install the image on the eMMC.

Also check if the eMMC is correctly detected within Armbian after some reboots: it is important that the kernel detects it otherwise even if you install Armbian on eMMC it won't boot anyway.

 

Thank you for your time jock,

 

I tried the method you've described, but unfortunately the box doesn't boot yet., what a bummer :D

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

Hello @ArkhanLK, be aware of this:

 

so everything else is a moving target. The tools may work differently on other distributions, with subtle bugs or even build failures, so it is preferable to support a single distro and support it well.

Personally, I have my 100Gb Ubuntu Focal 20.04 Server virtual machine to do such jobs.

HI @jock! I will try that, but I'd like to mention the following from https://github.com/armbian/build#what-do-you-need-to-get-started

 

"Ubuntu Hirsute 21.04 x64 for native building" + "If building for LTS releases.. ex: Focal, Bionic, Buster, it is possible to use Ubuntu 20.04 Focal, but it is not supported" 

 

So that's a bit contradictory, no? 

I thought the Readme.md on github was more up-to-date, so I followed it. But I will try focal now. Thanks for the help! 

Link to post
Share on other sites
4 minutes ago, gnusmag45 said:

 

Thank you for your time jock,

 

I tried the method you've described, but unfortunately the box doesn't boot yet., what a bummer :D

Well, that's odd and unfortunate.

If you have a USB male-to-male cable try to connect it to the USB OTG port (without connecting the power cable, just the USB cable) and see if your computer shows the device in maskrom mode. As usual, the serial adapter is useful for debug.

It is very odd, because an empty eMMC will always trigger the sdcard boot, so I wonder what really happened when you did the flash erase...

Link to post
Share on other sites
19 minutes ago, ArkhanLK said:

HI @jock! I will try that, but I'd like to mention the following from htt

ps://github.com/armbian/build#what-do-you-need-to-get-started

 

"Ubuntu Hirsute 21.04 x64 for native building" + "If building for LTS releases.. ex: Focal, Bionic, Buster, it is possible to use Ubuntu 20.04 Focal, but it is not supported" 

 

So that's a bit contradictory, no? 

I thought the Readme.md on github was more up-to-date, so I followed it. But I will try focal now. Thanks for the help! 

 

Hmmm... yes, it is indeed contradictory... The "native" building should be referred to building armbian on the board itself, but there is an "x64" there which adds more contradiction confusion.

By the way, I'm using Focal to build Focal, Buster and Bullseye images and it works fine. Historically the supported distribution for x86-64 building was the latest Ubuntu LTS. There is only a bug in the build system that I don't know if it has been fixed yet, but you may need to install some packages manually (like libfdt), but then it should go on without any more issues

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

By the way, I'm using Focal to build Focal, Buster and Bullseye images and it works fine.

Just got the same error :( "ERROR in function write_uboot [ image-helpers.sh:103 ]"

Any suggestions?! Attaching the log here.

So, @jock, if you try to troubleshoot and generate this image successfully, can you post it for me? A rk322x-box minimal server Focal legacy... It's just I'm trying since Sunday and nada.

 

It'd REALLY help me... I'd appreciate it.

But it's OK if you can't. I will try to ask around.

Thanks again!
 

output.log

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

Just got the same error :( "ERROR in function write_uboot [ image-helpers.sh:103 ]"

Any suggestions?! Attaching the log here.

So, @jock, if you try to troubleshoot and generate this image successfully, can you post it for me? A rk322x-box minimal server Focal legacy... It's just I'm trying since Sunday and nada.

 

It'd REALLY help me... I'd appreciate it.

But it's OK if you can't. I will try to ask around.

Thanks again!
 

output.log 34.53 kB · 0 downloads

 

Here it is!

It's still weird you have building issues with Focal too, in a step (write uboot) that is mostly just bash scripting...

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

hello I have a v88 which works with the previous versions. but the last ones do not work after restarting it gets black screen some solution please

Please be more specific: did you upgrade via apt or install a new pristine image using the multitool from scratch?

Do you have a serial adapter with some logging output?

Do the multitool boot from sdcard or it does not boot anymore too?

Are you running legacy or mainline kernel?

Are the front led blinking or steady? And are they bright or dim?

What is your board and what CPU, RAM, flash memory does it mount? (photos are welcome)

 

Link to post
Share on other sites

Hi there,

 

  hope everyone is ok. I have learned a lot from this forum, and think its time to help/share on something. Just got new boxes and want to share info with you and im open to try/test whatever is needed. So:

MXQ Pro 4K 5G Android TV Box, 4Gb Ram, 32Gb Rom, 20 USD

Board: R329Q_V8.1 2020.06.15

Processor on stick: RK3229, under the heatskin: RK3228A

RAM: 4Gb, 4x Hynx H5TC2G43BFR-H9A (DDR3L 1333 Cl9-9-9) (it is supposed that each one should be 2Gb is what SK Hynx tells about this serial, each 4x512Mb)

ROM: 32Gb, RQueenston K9GCGD8U0F (cant find anything about it, seems like Samsung NAND PN, stick says eMMC)

Wifi: SV6256P, Dual Band 802.11 a/b/g/n

Will try to play with it today, and see what i can do, will post about it later.

Images (cant attach them):

https://ibb.co/6s2kpFQ
https://ibb.co/dW9TqwZ
https://ibb.co/YNJcZBh
https://ibb.co/4fdf3BY
https://ibb.co/5GwK1HP
https://ibb.co/w4M12HJ
https://ibb.co/W6SfX9t
https://ibb.co/9hHPGDd
https://ibb.co/F4MnfH6

Link to post
Share on other sites

@beretas

I definetly LOVE this chinos :D
As @jock said in a past post is quite improbable that will be 4 gb RAM but more realistic only 2 such as it will be a 16 gb ROM.
But apart of this.... it is android 11 and the kernel is yet a 3.10.104 that is the same used for android 6 :D

If you have uart and other tools your infos will be absolutely welcome

 

Link to post
Share on other sites

Hi @beretas, thanks for sharing all those infos and photos!

Your board should be very well supported, but unfortunately the flash memory seems to be a NAND, which is limiting somehow. I can't find any reference about the queenston manufacturer, I guess that's another chinese copycat company.

 

The RAM memory of your board is one gigabyte. Each memory chip is 2 gigabits (and not gigabytes), you have 4 of them, so it's a total of 8 gigabits, which is 1 gigabyte. Memories are always reported in terms of bits by datasheet manufacturers because of the DRAM production process (1 bit = 1 transistor).

 

The NAND is unknown: the product name is easily a fake one, taken from a common samsung 32 gigabytes chip and printed there to fool someone. Once you boot the multitool or armbian you will have some probably real values.

 

Link to post
Share on other sites

Hi,

@jock Multitool and Libreelec boot correctly, and both show 980MB RAM, so yes, it has 1GB available.

rdkdeveltool detects NAND as SAMSUNG with 7301MB.

@fabiobassa just tell me what can be helpfull and will do and post about it. Need to look for any of the USB-Uart devices i should have somewhere

 

 Im unable to boot Armbian.

Multitool boots but any option says that eMMC is not detected, so nothing to do there.

I used Usb OTG option, so i went and wrote u-boot img to 0x4000 with rdkdeveltool (i made a backup before), and tried different armbian images (focal and buster with 4.4 and the one with 5.10) to boot, on SDCard reader, on OTG usb with reader, but nothing boots. Still multool boots ok, but no eMMC detected, stock android is no more loading. Original Firmware and/or NAND data is not important for me, i would like to boot from SD and work there, as i'm looking for cheap low power simple task server (No UI, no GPU, no wifi, just ethernet, cpu and ram), but dont know what else to try.

 

Any suggestions ? Maybe i should try to 

 

Best Regards,

Beretas

Link to post
Share on other sites
On 5/13/2021 at 2:26 AM, jock said:

 

Here it is!

It's still weird you have building issues with Focal too, in a step (write uboot) that is mostly just bash scripting...

Much love, my friend, much love!!!

This minimal image has helped me immensely! Minimal 4.4 + tasksel with lubuntu = FLYING. I am SO happy with the performance! And I haven't even removed unnecessary things yet!!!

Yet, the media server still bugged. My opinion is that the armsoc driver is getting in the way, somehow, of the xorg. If i try to run it with any other system, it breaks the start and lightdm does not turns on ever again. Sometimes I can start with startx, but sometimes it just doesn't let me have GUI at all!

I will edit your install.sh to remove this part. But I just realized one thing: lots of the packs are lightdm oriented, yes? Meaning lubuntu may have issues with it since it's sddm... Still, I am finding it so good I am not even considering changing it. In lubuntu the media framework only installs halfway: it fails when it gets to ffmpeg|rkmpp. I will try installing the packages one by one, probably. Unless you have a suggestion?

 

to be fair, my hope is that I can use the system as is for office-like purpose, and if I want video, use kodi.  That is if kodi>>>armbian. For example, in armbian firefox is running youtube nicely at 360p, somewhat doable at 480p, so it's non-existent... If I can 720p videos + stream on kodi, I will be VERY happy!

 

Anyways, @jock, thanks a lot. You have been amazing. I'm hoping to repay you someday!

Link to post
Share on other sites
13 hours ago, beretas said:

Hi,

@jock Multitool and Libreelec boot correctly, and both show 980MB RAM, so yes, it has 1GB available.

rdkdeveltool detects NAND as SAMSUNG with 7301MB.

@fabiobassa just tell me what can be helpfull and will do and post about it. Need to look for any of the USB-Uart devices i should have somewhere

 

 Im unable to boot Armbian.

Multitool boots but any option says that eMMC is not detected, so nothing to do there.

I used Usb OTG option, so i went and wrote u-boot img to 0x4000 with rdkdeveltool (i made a backup before), and tried different armbian images (focal and buster with 4.4 and the one with 5.10) to boot, on SDCard reader, on OTG usb with reader, but nothing boots. Still multool boots ok, but no eMMC detected, stock android is no more loading. Original Firmware and/or NAND data is not important for me, i would like to boot from SD and work there, as i'm looking for cheap low power simple task server (No UI, no GPU, no wifi, just ethernet, cpu and ram), but dont know what else to try.

 

Any suggestions ? Maybe i should try to 

 

Best Regards,

Beretas

Well that's very strange the Multitool does not detect the NAND: it would be worth investigating, but that would many of trials and time.

The serial adapter would be very useful to read the messages log and would give important hints about, but NAND memories are always often very annoying,

 

Anyway, if you are not interested at all in NAND, you can run rkdeveloptool ef to erase the NAND completely, so the board will always boot from sdcard.

 

Once there you can do follow two different stategies:

  • Put the multitool on a sdcard and see if the NAND is detected requires zero effort. If NAND is detected, you think that you can follow the "Upgrade NAND bootloader" procedure from first page to upgrade the first-stage bootloader on NAND to the latest version, then run again the multitool and install armbian directly on NAND
  • Otherwise just put armbian on sdcard, plug the sdcard into the sd slot and run Armbian from sdcard.

 

I suggest you to give a shot to the first point, at least to see if NAND is detected from Multitool: it may seem an useless try, but actually when you erase the NAND, the board is forced to look for the proprietary first-stage bootloader from the Multitool, which is surely the most up-to-date. I have noticed that the bootloader can have an effect on NAND detection, so you may give a try at least to be aware of this. If you report here I'm interested too in the result.

 

Second option is very straightforward: you don't actually need the multitool at all and the kernel should detect (after configuring the board with rk322x-config) the NAND that you can use as a normal storage device (but only if you use an image with legacy kernel!).

Link to post
Share on other sites
13 hours ago, ArkhanLK said:

Much love, my friend, much love!!!

This minimal image has helped me immensely! Minimal 4.4 + tasksel with lubuntu = FLYING. I am SO happy with the performance! And I haven't even removed unnecessary things yet!!!

Yet, the media server still bugged. My opinion is that the armsoc driver is getting in the way, somehow, of the xorg. If i try to run it with any other system, it breaks the start and lightdm does not turns on ever again. Sometimes I can start with startx, but sometimes it just doesn't let me have GUI at all!

I will edit your install.sh to remove this part. But I just realized one thing: lots of the packs are lightdm oriented, yes? Meaning lubuntu may have issues with it since it's sddm... Still, I am finding it so good I am not even considering changing it. In lubuntu the media framework only installs halfway: it fails when it gets to ffmpeg|rkmpp. I will try installing the packages one by one, probably. Unless you have a suggestion?

 

to be fair, my hope is that I can use the system as is for office-like purpose, and if I want video, use kodi.  That is if kodi>>>armbian. For example, in armbian firefox is running youtube nicely at 360p, somewhat doable at 480p, so it's non-existent... If I can 720p videos + stream on kodi, I will be VERY happy!

 

Anyways, @jock, thanks a lot. You have been amazing. I'm hoping to repay you someday!

 

@ArkhanLK you're too kind :beer:

Well the media framework was compiled with a Focal of one year ago or so... maybe the packages have been updated in the meantime and now they are not compatible anymore - that's the only thing I can think about.

Actually nothing is really tied to lightdm, armsoc is a general driver for X.org and maybe something changed in X.org with latest Focal packages that made it not work anymore.

It is very curious rkmpp does not install though, as far as I remember it had no very important dependencies.

Did you install the packages via apt-get install or via dpkg? The script uses apt-get install to solve automatically the dependencies and that would be the only sensible way.

 

To be honest, the box is quite capable to run x264 and x265 1080p streams in Kodi with ffmpeg + rkmpp.

I should try lubuntu, Armbian is historically tied to xfce but I'm not very fond of. Also it is always suggested to disable window compositing for xfce because the desktop will feel very sluggish with it on, but the media framework should disable it by itself.

Link to post
Share on other sites

Hey @jock, my bad: I meant the ffmpeg. It mentions rkmpp and I got them mixed up.

Now, I have tried installing the files slowly and, unless rkmpp in fact has some issues, I'm having the error because of the drivers! 

I have an img with lububtu working fine. Installed rkmpp and Mali, had an error with some depencies on Mali, fixed it and tried again. It went fine, I reboot, and this happens and I cannot login, switch tty... Just gotta redo the install. 

So, I will skip Mali drivers and armsoc... Let's see what I get! 

Unfortunately the verbose was not on so whatever is written there doesn't say much. But if you'd like to read the last lines, they're attached! 

Well, wish me luck...! 

VID_20210516_203256_exported_2319.jpg

Link to post
Share on other sites
On 5/14/2021 at 2:54 PM, jock said:

Please be more specific: did you upgrade via apt or install a new pristine image using the multitool from scratch?

Do you have a serial adapter with some logging output?

Do the multitool boot from sdcard or it does not boot anymore too?

Are you running legacy or mainline kernel?

Are the front led blinking or steady? And are they bright or dim?

What is your board and what CPU, RAM, flash memory does it mount? (photos are welcome)

 

 

Quote

Did you upgrade via apt or install a pristine new image using the multitool from scratch? Install the new image Armbian_21.05.1_Rk322x-box_focal_legacy_4.4.194_xfce_desktop.img the same with the two previous versions

 

Do you have a serial adapter with any log output? Not

 

Does the multitool boot from sdcard or does it no longer boot? if it works normal

 

Are you running main or legacy kernel? Armbian_21.05.1_Rk322x-box_focal_legacy_4.4.194_xfce_desktop.img

 

Is the front LED blinking or solid? Are they bright or dim? if it blinks

What is your board and what CPU, RAM, flash memory do you mount? (photos are welcome) Yes, I'll go up more as soon as possible

 

https://drive.google.com/file/d/1oFkpX8hLAXHoTHbaD8CU1NliFLoTq2yf/view?usp=sharing

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

 

 

Link to post
Share on other sites