that could help others understand the issue better. No issue at all, everything is working as expected. If you can, maybe share the key stats or error messages directly in the post text If there is still interest in metrics, you can take a look at the logs that I uploaded in this thread. It's the s...

I'm sorry, no performance logs, as this forum does not allow text attachments.

You need to reinstate the deleted firmware. For mainline firmware with U-Boot as payload it may look like this: dd bs=512 seek=64 conv=notrunc,fsync if=u-boot-rockchip.bin of=/dev/mmcblk2 MASKROM uses sector 64 as the entry point on MMC devices, so the firmware binary must cover at least that range.

Without providing a serial console log collected via the debug UART, no one knows what's going on and no more comprehensive support can be provided.

If the maskrom botton is released while the first firmware messages are displayed on the serial console, the booting system can probe the eMMC and it will be accessible. Of course, the booting system must support eMMC access.

Any assistance would be grateful. The kernel has been supporting such devices for quite some time. If properly wired up in devicetree , the following control codes are supported for /dev/lcd: HEX | ASCII | \-ESC /* description */ 0x08 | <BS> | \b /* go back one char and clear it */ 0x0A | <LF> | \n...

I would appreciate any pointers anyone can provide. The debug UART is wired up directly at the SOC as can be seen by the schematic. The IO is powered by the VDD_SYS_3.3V power domain, so a USB serial adapter operating in the same power range is required. A TTL variant (5.0V) will not work. The VDD_...

to understand why with a kernel 4.xx everything works, but not with a kernel 5.xx The 4.xx kernel is a heavily hacked legacy kernel fork whose additions have never been submitted to mainline. I am currently running 6.0.0-rc1 on my fully flagged Fedora desktop. I have full functional HDMI, analog so...

Kernel 5.14.0-0.rc5 with drm panfrost in-flight patches for 5.15.x shows remarkable graphics improvements. Meanwhile switched to 5.14.0-1, but this commit must be reverted for rk3399 Ethernet to continue to work. Now also applied LibreELEC kernel patches and rebuild ffmpeg with v4l2-request-hwaccel ...

To wire the LK-OLED1 to i2c2 (con1-03, con1-05) only a level shifter is required. LK-OLED1.jpg This overlay /dts-v1/; /plugin/; / { compatible = "friendlyarm,nanopc-t4"; }; &{/i2c@ff120000} { #address-cells = <1>; #size-cells = <0>; lkoled1: oled@3c { compatible = "solomon,ssd1306...

I have built a current kernel with sdhci-of-esdhc as build-in instead of as module to run the HoneyComb without initramfs as well. If there is an interest in using this kernel for my image, I have uploaded it here . Fedora Kernel Team has picked up an in flight fix for proper pcie support already. S...

Sorry, I can no longer claim I have never tested my image with another device. My HoneyComb is now running with the image I composed for the NanoPC-T4. The only precautions for this were a firmware, borrowed from an image provided by the manufacturer, and some small configuration adjustments. And th...

Here it is: This is not the expected log output of my provided u-boot. It starts the same way as the LE. Looks like you have firmware in SPI that takes precedence over emmc and SD card. Disable it as described here . I.e. connect PIN23 and PIN25. Now power cycle with my image on SD card in place an...

Could you also provide the log with my image and my provided u-boot-rockchip.bin in place?

gstreamer1-1.19.1-1 makes use of hardware-accelerated video components for sure.

tony013 wrote:
Partition 1 contains ... extlinux.conf

If u-boot also emits messages on screen from its actions, everything that is needed is already available. Transfer the firmware area to my image as described above and it would have to work. If this is not the case, it is impossible to continue the analysis meaningfully without a serial console log.

tony013 wrote:
Address locations are quite different from LE and your image

From a firmware point of view, the partition layout is insignificant. Since the firmware area for Rockchip ranges from sector 64 to sector 32767, the only requirement for partition layout is not to overlap this area with other use.

I have now a kernel with pcie nvme enabled in place. Now my Samsung SSD 970 EVO Plus is the fastes disk in town. /dev/disk/by-path/platform-f8000000.pcie-pci-0000:01:00.0-nvme-1: Timing buffered disk reads: 2188 MB in 3.00 seconds = 728.87 MB/sec /dev/disk/by-path/platform-fe320000.mmc: Timing buffe...

When I said I don't know what you're doing, it was because of the use of balena. As you can see from the previous conversation with @supergordon, software sometimes does things that the user does not intend. Because you do not have serial console access and thus log messages can not simply roll back...

Do you know, who is resposible to initialize graphic output? For u-boot output u-boot. The provided one should have everything necessary activated. But I'm really not sure what you're doing, I'm not even sure if you put u-boot in. At least you didn't mention it. As long as you don't have serial con...

supergordon wrote:
Could you help me on that?

Gparted probably garbled the partuuid. Check with: If the partuuid has been changed, restore the original, or more simply, replace all partuuid values in /extlinux/extlinunx.conf with the one displayed by lsblk.

So you say, that i.e. taking kodi from LE and copy it to whatever linux image should work? No, we are not talking about user space. We are talking about to make my image bootable for your device. Anyway, I rebuild the uboot-tools for another reason and since your device seems quit identical to mine...

dd is a stupid tool, that copies just blocks, so to me it looks like first and last dd write to the same location, so they overwrite each other. Rockchip's maskrom code starts executing its firmware at sector 64, hence bootloader code has to start there. My commands describe two times the same oper...

Fedora is not device-specific, only architecture-specific. The only device specific for Arm is the bootloader in the firmware area. For Rockchip the firmware area looks like this . To boot my aarch64 image you only need a distro-boot capable u-boot for your device in there. Fedora comes with mainlin...

See this entire thread.
Maybe start with this post.

I have now ffmpeg with these patches applied in place. External libraries providing hardware acceleration: cuda nvdec v4l2_request cuda_llvm nvenc vaapi cuvid opencl vdpau ffnvcodec v4l2_m2m vulkan But as I don't know how to verify the hardware acceleration, I'm not sure if something else is also re...

Running on Wayland gives a nice performance boost. [lxqt@trial-01 ~]$ glmark2 ======================================================= glmark2 2021.02 ======================================================= OpenGL Information GL_VENDOR: Panfrost GL_RENDERER: Mali T860 (Panfrost) GL_VERSION: 3.1 Mesa ...

what kernel source did you take? I only care for mainline. Fedora follows mainline very close, so I'll grab the kernel source package from here , add my modifications, and rebuild. Currently I only carry this two relevant patch sets: add_select_SND_SOC_RT5651 and add-dp-alt-mode-to-PBP. And of cour...

supergordon wrote:
I have like 20 browser tabs open, pdfreader and the terminal and nothing lags. everything is promptly loaded.

The same goes for me, but I'm also building the kernel package on the second desktop at the same time.

Kodi also runs very good. With hardware acceleration of course. But did'nt test 4K yet but I will asap. I doubt that it will be hardware accelerated as I know ffmpeg mainline is missing some support for it. LibreELEC is carrying some patches for it, but they are on some older version. I. e. I am no...

For mainline kernel with ir-keytable in place and friendlyarm_rc-100.toml registered as in rc_maps.cfg the remote control is working for me like a keyboard.

My micro SD card went full, hence I migrated my OS configuration to a new card. Thereby I wondered how my setup would work for someone else. So I also created a trial image and uploaded Fedora-trial-01-aarch64-34-1.2.img . If you like and have a spare micro SD card, put the image on it and report yo...

And... the result is... none. No gpiochip has been detected. If no gpiochip is detected, the kernel is not configured to expose the necessary device nodes. it doesn't work on NanoPi M4 V2 The gpiochip api is device independent, i.e. it is working for all devices in a similar manner as long as the k...

GPIO sysfs interface is deprecated, use libgpiod [1] instead. Usage: gpioset [OPTIONS] <chip name/number> <offset1>=<value1> <offset2>=<value2> ... Set GPIO line values of a GPIO chip and maintain the state until the process exits Options: -h, --help: display this message and exit -v, --version: dis...

I run Fedora on my NanoPC-T4. It didn't run out of the box and I had to change some configurations to meet my needs. For now, it boils down to rebuilding u-boot and the kernel for configuration modification. And rebuilding some other packages for early adoption. IMHO it should also be feasible if yo...