JMCC

For the CSI connector to work through RK-ISP interface, you need to use legacy kernel. Now, I don't know about the driver for that particular device. That is something you will have to figure out by yourself. But, as I said, the ISP driver is enabled in the legacy kernel.

If you look at the first post, you have the information about the sources for all the packages, pointing at my GitHub repos. Most of them include instructions in the repo's README. If you have some doubt, you can ask and I will try to help. As you can see in the script's post, it is deprecated in favor of this integration. All the features are ported, and the sources info is more complete here, so there is no more use for the script.

type sudo armbianmonitor -u In a working and a failing system

+1

I've been thinking about all this project. I had in mind that it would be best to make armbian-config modular since some time ago, before this project came up. I used to work in such kind of projects a long time ago, I guess I could dust off my knowledge. @tparys @Igor How about creating a Github repo with the new proof-of-concept, to start working on it? I can do that if you agree. @tparys If you have something already, we can start with that. Otherwise, I can start it with a simple structure I have in mind.

What about the status page of the status page of the status page?

I created Kodi packages for v4l2-request, tested on Orange Pi+2e (Allwinner H3) running Armbian Bullseye with the current 5.10.y kernel. So far, HW video playing works fine with MPEG2 and h.264 up to 1080p. Kernel patches are needed to improve resolution and codec support. GUI performance is just enough, but it can probably be also improved with kernel patches. So the userspace part is now working, the kernel improvements remain in the TO-DO list. Packages can be found here: https://users.armbian.com/jmcc/packages/kodi-mainline/ These should still be considered WIP, although fully functional already. Instructions: Download the packages for your architecture, and install them with "dpkg -i". Only kodi-mainline and kodi-mainline-bin are essential, the others are optional. Run "apt -f install" Make sure there is no X server running, and start kodi from console typing "kodi" @balbes150 you may be interested in this. They should also work in Rockchip, but I haven't tested yet.

It's strange, that it only has the filesystem error the first time. Did you use it for a while? Normally, the error appears after some intensive I/O, like using the desktop for a while (e.g.: browsing with Chromium), or installing a big number of packages through APT.

Well, kernel 5.x doesn't have the error with Renegade either. The bug is specific to the 4.4 kernel. NOTE: I moved all the posts to the proper place, in the Renegade thread. Please use this thread for this issue from now on.

You said that Renegade image is corrupting filesystem when used on SD card, didn't you? That is what we want to fix.

That is what we want to do. And that is the reason why I asked you to do the tests above. So if you can please make these tests and post here the results, we can move on to debugging and fixing the problem. If you want to help, please perform the tests indicated in this post:

@NicoD If you get the chance, could you test this kernel on your Nanopi-M4? I want to make sure the fix does not break other boards, before merging.

Okay, NanoPC-T4 can run now dual displays, and GPU 3D acceleration works flawlessly: https://users.armbian.com/jmcc/misc/nanopct4-dual-screen.mp4 @TheGuv It seems like a problem specific to Helios64. @aprayoga Maybe you can shed some light on the problem? This is the post where the user reported failing GPU acceleration: https://forum.armbian.com/topic/16516-rk3399-legacy-multimedia-framework/?do=findComment&comment=116900 [EDIT]: And this is the fix that enabled NanoPC-T4 DP, in case it is helpful to debug the Helios64 problem: https://github.com/armbian/build/pull/2647

Okay, but since I added the "Fix version" tag, will not they be added automatically to next release? Just in case, so there are not duplicates.

Cool. I put as Fix version "20.05" in all the issues mentioned above. As a matter of fact, they are already merged and present in the 20.02 release, but at least they will be documented even though in a later release.

Quick question: I put some bugfixes/improvements in the past on Jira, but they did not make it into the release change log (Examples: https://armbian.atlassian.net/browse/AR-478 https://armbian.atlassian.net/browse/AR-600 https://armbian.atlassian.net/browse/AR-599 https://armbian.atlassian.net/browse/AR-585) Is there any additional step I must take for it to be displayed in the changelog? Well, the changes make it into the binaries anyway, but I'd rather have them documented also in the changelog.

Yes, as I told you a few posts above, Renegade is the commercial name that Libre Computer uses for roc-rk3328-cc I also have the board, and I was very active developing for it in the past when bringing it up as CSC. The problem you mention, about filesystem getting corrupted, also happens in my board. But, since nobody else complained about it, I assumed it was just my defective unit and forgot about it. But now, you mention the same problem, and some other user also recently reported it. So, my first question: ¿Do you have emmc, or only SD card? The quickest workaround is to use a "Current" (5.10.y) image to flash "Legacy" (4.4.y) to the emmc, as described in this post. Also, since you seem to be using a old Rock64 image without problems, please try the new Rock64 image I linked above, and post here the results. If that one does not work, please try the images for Station M1, as @balbes150 adviced above. We will appreciate if you perform these tests and post here the results. It can be helpful not only for you, but also for other users. [EDIT]: And please, post the output of "sudo armbianmonitor -u" for the tests, so we can figure out what is failing.

I suggest building or using a nightly

As @balbes150 pointed out, your model is the Renegade, that is the commercial nickname. You should download a Renegade buster legacy desktop image.

That error was present only in older kernels, it is solved already. I looked at your logs, and for some reason you are using a very old kernel (4.4.194). Try this image instead: https://redirect.armbian.com/region/EU/rock64/Buster_legacy_desktop Notice that Rock64 is not offcially supported by Armbian anymore, due to issues with hardware quality and lack of compatibility between different HW revisions. So I cannot guarantee the image will work for you.

Well, at least you can try that. I have no idea what the problem looks like, so that is something.

Definitely, according to the picture, something went wrong. Can you do the installation again from scratch, and this time copy-paste the installation output? And also "armbianmonitor -u".

Yes, correct. You should move them from the userpatches directory to patch/kernel/rockchip64-legacy, and then make a PR against armbian build repo. You can reference this thread in the PR description.

~/.kodi/temp/kodi.log Enable debug logging as described here: https://kodi.wiki/view/Log_file/Advanced

Okay, you need to provide more information. Output of sudo armbianmonitor -u And also kodi logs, and the failing system logs.