JMCC

I can see some reference to x11vnc in the log, is that so? If you are trying to play a streamed video through vnc, it will cause all kind of problems, even more on such a weak CPU.

With the changes you pointed above, you are doing two things: first, changing the device tree from XU4 generic to the specific for HC1. The second one, setting some kernel parameters for USB storage. The main benefits of changing to the hc1 device tree is that you don't have unnecessary nodes, and most of all, the thermals adapted to passive-only cooling. It will for sure not have any effect on the MOTD board name shown, and most probably neither in the disk problems. The USB storage quirks may or may not help with your disk problem. My advice, after almost three years of using a HC1 as a home cloud and media server, is switch to legacy. It is absolutely rock-solid, and it is not that old (4.14 is supported until Jan 2024). IMO 5.4.y is not ready for production yet.

Did you try different SD cards? It is usually a problem with bad quality cards. Try something like Sandisk Ultra at least Enviado desde mi moto g(6) plus mediante Tapatalk

We can only help you if you are using the official Armbian kernel, from the stable legacy branch. If you choose to use some other kernel, then you are on your own. Please try on a fresh Armbian image, with the official kernel. Make sure you use a buster legacy desktop image, namely this one: https://redirect.armbian.com/rock64/Buster_legacy_desktop.torrent. I am telling you to start over with a new image, because from the logs above I suspect there was a problem with the installation of some desktop packages.

Vaapi will do nothing, there is no vaapi support in Rockchip Legacy In order to help you with your problem, you need to provide information about your system. Start with the output of 'sudo armbianmonitor -u' Enviado desde mi moto g(6) plus mediante Tapatalk

As I said above, you should consider some SBC with Armbian support. You can get something rockchip-based with 2gb RAM for about $40-$60, or if you don't need 4K video play, go for the Odroid XU4 for $50.

Yeah, I bought to my mother one of those Chinese CHUWI laptops, tried to use the adapter, but probably the USB-C port was not compliant and broke it. That is my punishment for cheaping out on my mother's laptop gift

BTW, anybody stepped it as a maintainer for the Pinebook Pro? It seems to be out of stock since some months ago, so it may be hard even to get a unit.

Sorry, my USB-C to DP/HDMI converter is broken, and I have no plans to make room in my budget for a new one, at least for now. So I cannot debug or fix this problem. TBH, I am very surprised there is people using the Helios64 as a desktop device, I always considered it a NAS

Corrected

You can perform both 1. and 2. with almost any Android tv box, using Android. From the practical point of view, that you a your best option IMO. Now, if you want to experiment the use of Linux, in order to learn about it, I think the device that best suits your goals is some box based in the RK3328 SoC. You can find some very cheap ones. Some search in the forums will reveal you which models are most popular to work. With that RK3328 device, you can get Kodi and 4k video play with the Legacy Kernel Multimedia Framework: But remember, the TV boxes are not meant to work with Linux, they just happen to work, more or less reliable. If you want stability in Armbian, I recommend going for some true Single Board Computer, instead of a TV Box (check in the download page). And for Multimedia, Rockchip is the way to go as of today (devices based on RK3328, RK3288 or RK3399, in increasing order of price and performance)

Can you share the models?

I tried to reproduce on my NanoPC-t4, but USB-C DP out does not work out of the box, at least with my adapter. I'll need to debug and fix that before getting into the mali issue.

Yes, that was my guess. But I wanted the user to do some homework and check it for himself. I personally don't own any surround audio equipment, so if he cares for the feature, he will need to contribute some effort. Otherwise, I won't care either to implement it.

Please "armbianmonitor -u" of the basic installation and also after installing the multimedia integration

Arre you talking about the tweaked kernel I linked above? That was just for testing. Now, the relevant changes are merged into the build script. So, if you are still using the testing version, just install a recently built kernel: either build your own debs with the build script, download it from beta, or wait for the next stable release. The errors you show are not critical, it seems like probably EXT4 debug was enabled on that kernel. If after switching to the official kernel the problem persists, we'll look into it.

New release in the repos: Fixed Chromium showing images in indexed color, and other limitations. Fixed OpenCL broken in last update Improved X performance under glamor (by 100%, in gtkperf tests) Fixed rkcamsrc plugin for using the ISP MIPI-CSI camera. Added the Rockchip RGA library (also enabled in the kernel).

New release in the repos: Fixed Chromium showing images in indexed color, and other limitations. Fixed OpenCL broken in last update Improved X performance under glamor (by 100%, in gtkperf tests) Fixed rkcamsrc plugin for using the ISP MIPI-CSI camera (ov5647 still needs some kernel work for rk3399). Added the Rockchip RGA library (also enabled in the kernel).

The SoC only supports OpenGL-ES. You are testing OpenGL. For OpenGL, we include a GLES-GL wrapper "gl4es" , but it is only installed as an optional dependency. If you followed the instructions above, that is, adding the swtich "--install-recommends", the wrapper should be installed. Otherwise, it is not. You can also install it manually, with "apt install gl4es".

ARMbian If you take out the ARM part, it loses its purpose, doesn't it? You've got all the programs and features of Armbian available for x86 and many more, in plenty of distros, ppa's etc.. You

It's OK, the chat log works. I really wanted to be there, but for some reason I had in my mind it was later in the month. Even though late, here is an update about my work, and what I can contribute after seeing the chat log: Right now, I am brushing up the last fixes to RK legacy multimedia. Only the camera fix for RK3399 is missing, and it should be done. After that, I need to document the XU4 multimedia framework, which is also there already, and equal or more interesting than RK. When I finish with it, I would like to focus on mainline desktop/multimedia. I have done some experiments already with X11 3D acceleration, so I guess I could help with that. Besides that, there are a few other points I think I could implement easily, and would be useful: Adding some help pages to armbian-config. Docs are there already, it would be a matter of making them appear in the script. I will explain this more in detail in some other post. Some fixes to XU4 boot. I can further explain this somewhere else too. And for last, I have a couple questions too: Regarding the CSC boards available in the build script, there are some that we offer images to download, and some others that we don't. It would be nice to clarify what is the criteria about that. Even if it is just "we offer CSC downloads for a board if someone cares enough to ask for the image to be there", or something alike. Not every board supporting overlays has the "Hardware" option in armbian-config (e.g. nanopc-t4 legacy doesn't). Is that supposed to be so for a reason, or it is a bug?

Darn it, I totally missed the meeting. Christmas season is so hectic, I didn't even notice. @Werner Is the log available somewhere?

What are the steps you follow in Libreelec to enable that feature? Can you do the same in our Kodi? You should test with a media file that works in Libreelec, and try to repeat the same procedure you. Also, make sure you have installed the necessary codecs. Install the package "kodi-addons-full", restart, and then in Kodi go to My add-ons and check if there is some audio decoder you need to enable.

I recently configured the build script to create a Buster Desktop image for all Rockchip boards, so with next Armbian update it should appear in the download page. In the meantime, as @TonyMac32 said, you can download the server image and use "armbian-config" to install the Desktop easily (it's under System -> Default Desktop).

Miqi has RK3288, which has 32 bit architecture. On the other hand, RK3328 is a different SoC, with 64 bit architecture. That is why it is not present in the same repos as 32-bit RK3288. To avoid confusion between similar numbers, I called the RK3288 package "media-buster-legacy-tinkerboard", that is the one you should use for your board. However, it is even more complicated. Some variants of Miqi have a different version of the SoC, named RK3288W, which needs special mali packages for GPU acceleration. I made no package for that variant, since Miqi is unsupported already. But if you find that the standard package does not work, I can help you get the right library for your board.