Can the computer run entirely on free software which is software you can use, share, modify and redistribute? The question includes firmware, microcode, etc, any piece of software that is running on the computer. If some devices on the computer requires non free software in order to work then what devices are they? And will the computer still work if you choose to not install the pieces of non free software in question? Thank you.

root@modron:/home/luna# apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://deb.debian.org/debian trixie-backports InRelease
Hit:4 http://security.debian.org trixie-security InRelease
Hit:6 https://download.docker.com/linux/debian trixie InRelease
Hit:7 https://github.armbian.com/configng stable InRelease
Get:5 http://armbian.lv.auroradev.org/apt trixie InRelease [62.3 kB]
Err:5 http://armbian.lv.auroradev.org/apt trixie InRelease
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature.
Fetched 62.3 kB in 1s (67.6 kB/s)
10 packages can be upgraded. Run 'apt list --upgradable' to see them.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://armbian.lv.auroradev.org/apt trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature.
Warning: Failed to fetch http://apt.armbian.com/dists/trixie/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature.
Warning: Some index files failed to download. They have been ignored, or old ones used instead.

I've tried to setup the latest Debian 13 (Trixie) for the Renegade board. I can flash the image with no issue. The problem comes it boots up, prompts for root password. I can type in then press enter, and then it goes to login. This only happens on the Debian 13 (Trixie).  I am using the Debian 12 XFCE imange no issue. 

I am not sure if this is a bug or what, but I loved to use Debian 13, I am trying to setup Docker with the latest OS. 

Libre used to host a script for a tool that achieved this but it hasn't been updated since Buster

TIA

make.log:

DKMS make.log for v4l2loopback-0.12.7 for kernel 6.12.32-current-rockchip64 (aarch64)
Sat Jul  5 09:16:17 PM CDT 2025
Building v4l2-loopback driver...
make -C /lib/modules/6.12.32-current-rockchip64/build M=/var/lib/dkms/v4l2loopback/0.12.7/build modules
make[1]: Entering directory '/usr/src/linux-headers-6.12.32-current-rockchip64'
  CC [M]  /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o
/var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c: In function ‘vidioc_querycap’:
/var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c:717:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration]
  717 |         strlcpy(cap->driver, "v4l2 loopback", sizeof(cap->driver));
      |         ^~~~~~~
      |         strncpy
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:229: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.12.32-current-rockchip64/Makefile:1945: /var/lib/dkms/v4l2loopback/0.12.7/build] Error 2
make[1]: *** [Makefile:224: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.12.32-current-rockchip64'
make: *** [Makefile:43: v4l2loopback.ko] Error 2

Edit: 

I had the wrong make.log contents. The old one was after I tried to fix it and failing. The actual build error is missing strlcpy().

I have copied the overlay from the Libre build of Debian for Renegade and it applies correctly on after I manually add it to the overlay directory:

/boot/dtb-6.12.32-current-rockchip64/rockchip/overlay/rockchip-rk3328-pwm2.dtbo

Note that as of today armbian-config is having a general issue with loading overlays via armbianEnv.txt. This can be bypassed by avoiding using armbian-config for overlays and editing armbianEnv.txt directly and adding the overlay name to the overlays=  line minus the "rockchip-" prefix.

FWIW - here's the overlay source:

===========================

/dts-v1/;

/ {
        compatible = "libretech,roc-rk3328-cc\0rockchip,rk3328";

        fragment@0 {
                target = <0xffffffff>;

                __overlay__ {
                        status = "okay";
                };
        };

        __fixups__ {
                pwm2 = "/fragment@0:target:0";
        };
};

logs.txt

This may be related to

and

Before upgrade, 24.11.1 had LEDs working with "firefly:blue:power" and "firefly:yellow:user"
24.11.1 had  /sys/class/leds/firefly:blue:power   pointing to   /sys/devices/platform/leds/leds/firefly:blue:power as shown here:

On this (LED working) installation BEFORE UPGRADE:
 " armbianmonitor -u "  logging output here:    https://paste.next.armbian.com/ucizofikay

Note the pretty names + armbian firmware show 24.11.3, while the other packages held back to 24.11.1 by the setting in armbian-config tool.  LEDs working with these packages:

PRETTY_NAME="Armbian 24.11.3 bookworm"
ARMBIAN_PRETTY_NAME="Armbian 24.11.3 bookworm"
hi  armbian-bsp-cli-renegade-current 24.11.1                             arm64        Armbian CLI BSP for board 'renegade' branch 'current'
ii  armbian-config                   25.2.0-trunk.360.0120.124904        all          Armbian config: The Next Generation
ii  armbian-firmware                 24.11.3                             all          Armbian - Linux firmware
ii  linux-base                       4.9                                 all          Linux image base package
hi  linux-dtb-current-rockchip64     24.11.1                             arm64        Armbian Linux current DTBs in /boot/dtb-6.6.62-current-rockchip64
hi  linux-image-current-rockchip64   24.11.1                             arm64        Armbian Linux current kernel image 6.6.62-current-rockchip64
hi  linux-u-boot-renegade-current    24.11.1                             arm64        Das U-Boot for renegade

=============================================
AFTER UPGRADE:
LEDs don't work and /sys/class/leds is empty after Armbian kernel upgrades enabled in armbian-config and the following installs:
root@renegade:~# apt list --upgradable
linux-dtb-current-rockchip64/bookworm 24.11.3 arm64 [upgradable from: 24.11.1]
linux-image-current-rockchip64/bookworm 24.11.3 arm64 [upgradable from: 24.11.1]

AFTER UPGRADE:
 " armbianmonitor -u "  logging output here:   https://paste.next.armbian.com/arodolamag

I see the trees above show "waiting on supplier" and then some generic "led-0  led-1" stuff and nothing like the  "firefly*" stuff that worked before upgrade.
Note that this seems reproducible whether I started with the "Armbian 24.11.1 Bookworm Minimal" or the  "Armbian_24.11.1_Renegade_bookworm_current_6.6.62-omv_minimal" images.
No issues booting, power is from the board supplier's 2.5A 5v adapter, flashed new SanDisk micro SD, install to eMMC following all the preparations on the armbian Getting Started page.
I've had no luck playing around with this on my own, but please realize I have near-zero skill in this work.   Any help is greatly appreciated, thanks in advance !

// John

Here's the armbianmonitor -u output for the working 6.6.47 kernel: https://paste.next.armbian.com/suporamoqe

And here's the output for the not-quite-so-working 6.12.11 kernel: https://paste.armbian.de/cuxaxoweci

This isn't a huge deal for me, since I usually close my eyes while typing the passphrase anyway, but it means I have to guess when it's ready for me to type the passphrase, and guess how long to wait before concluding that I typed it wrong, and need to try again.  Also, it might bother other people more than it bothers me.

TV: Samsung 43" “The Frame”, model QN43LS03BAFXZA
Firmware T-PTMAKVC-1622.4, BT-S
4K native resolution, but should be able to upconvert

edid-decode (hex):

00 ff ff ff ff ff ff 00 4c 2d 7f 72 00 0e 00 01
01 20 01 03 80 5f 36 78 0a b3 61 ab 4f 46 a8 27
0b 50 54 bd ef 80 71 4f 81 c0 81 00 81 80 95 00
a9 c0 b3 00 d1 c0 04 74 00 30 f2 70 5a 80 b0 58
8a 00 50 1d 74 00 00 1e 56 5e 00 a0 a0 a0 29 50
30 20 35 00 50 1d 74 00 00 1a 00 00 00 fd 00 18
4b 0f 51 1e 00 0a 20 20 20 20 20 20 00 00 00 fc
00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 9f

02 03 51 f0 52 5f 10 1f 04 13 05 14 20 21 22 5d
5e 62 64 07 16 03 12 2f 0d 57 07 09 07 07 15 07
50 57 07 01 67 54 03 83 0f 00 00 e2 00 4f e3 05
c3 01 6e 03 0c 00 30 00 b8 44 20 00 80 01 02 03
04 e3 06 0d 01 e5 0e 60 61 65 66 e5 01 8b 84 90
01 02 3a 80 18 71 38 2d 40 58 2c 45 00 50 1d 74
00 00 1e 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ea

Block 0, Base EDID:
EDID Structure Version & Revision: 1.3
Vendor & Product Identification:
Manufacturer: SAM
Model: 29311
Serial Number: 16780800
Made in: week 1 of 2022
Basic Display Parameters & Features:
Digital display
Maximum image size: 95 cm x 54 cm
Gamma: 2.20
RGB color display
First detailed timing is the preferred timing
Color Characteristics:
Red : 0.6699, 0.3115
Green: 0.2734, 0.6591
Blue : 0.1533, 0.0449
White: 0.3125, 0.3291
Established Timings I & II:
IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz
DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz
Apple : 640x480 66.666667 Hz 4:3 35.000 kHz 30.240000 MHz
DMT 0x05: 640x480 72.808802 Hz 4:3 37.861 kHz 31.500000 MHz
DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz
DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz
DMT 0x0a: 800x600 72.187572 Hz 4:3 48.077 kHz 50.000000 MHz
DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz
Apple : 832x624 74.551266 Hz 4:3 49.726 kHz 57.284000 MHz
DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz
DMT 0x11: 1024x768 70.069359 Hz 4:3 56.476 kHz 75.000000 MHz
DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz
DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz
Apple : 1152x870 75.061550 Hz 192:145 68.681 kHz 100.000000 MHz
Standard Timings:
DMT 0x15: 1152x864 75.000000 Hz 4:3 67.500 kHz 108.000000 MHz
DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz
DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz
DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz
DMT 0x53: 1600x900 60.000000 Hz 16:9 60.000 kHz 108.000000 MHz (RB)
DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz
DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz
Detailed Timing Descriptors:
DTD 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz (1872 mm x 1053 mm)
Hfront 176 Hsync 88 Hback 296 Hpol P
Vfront 8 Vsync 10 Vback 72 Vpol P
DTD 2: 2560x1440 59.950550 Hz 16:9 88.787 kHz 241.500000 MHz (1872 mm x 1053 mm)
Hfront 48 Hsync 32 Hback 80 Hpol P
Vfront 3 Vsync 5 Vback 33 Vpol N
Display Range Limits:
Monitor ranges (GTF): 24-75 Hz V, 15-81 kHz H, max dotclock 300 MHz
Display Product Name: ‘SAMSUNG’
Extension blocks: 1
Checksum: 0x9f

Block 1, CTA-861 Extension Block:
Revision: 3
Underscans IT Video Formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
Native detailed modes: 0
Video Data Block:
VIC 95: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz
VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz
VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz
VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz
VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz
VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz
VIC 32: 1920x1080 24.000000 Hz 16:9 27.000 kHz 74.250000 MHz
VIC 33: 1920x1080 25.000000 Hz 16:9 28.125 kHz 74.250000 MHz
VIC 34: 1920x1080 30.000000 Hz 16:9 33.750 kHz 74.250000 MHz
VIC 93: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz
VIC 94: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz
VIC 98: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz
VIC 100: 4096x2160 30.000000 Hz 256:135 67.500 kHz 297.000000 MHz
VIC 7: 1440x480i 59.940060 Hz 16:9 15.734 kHz 27.000000 MHz
VIC 22: 1440x576i 50.000000 Hz 16:9 15.625 kHz 27.000000 MHz
VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz
VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz
Audio Data Block:
Linear PCM:
Max channels: 6
Supported sample rates (kHz): 192 96 48 44.1 32
Supported sample sizes (bits): 24 20 16
Linear PCM:
Max channels: 2
Supported sample rates (kHz): 48 44.1 32
Supported sample sizes (bits): 24 20 16
AC-3:
Max channels: 6
Supported sample rates (kHz): 48 44.1 32
Maximum bit rate: 640 kb/s
Enhanced AC-3 (DD+):
Max channels: 8
Supported sample rates (kHz): 48 44.1 32
Supports Joint Object Coding
MAT (MLP):
Max channels: 8
Supported sample rates (kHz): 192 96 48
Supports Dolby TrueHD, object audio PCM and channel-based PCM
Hash calculation not required for object audio PCM or channel-based PCM
Speaker Allocation Data Block:
FL/FR - Front Left/Right
LFE1 - Low Frequency Effects 1
FC - Front Center
BL/BR - Back Left/Right
Video Capability Data Block:
YCbCr quantization: No Data
RGB quantization: Selectable (via AVI Q)
PT scan behavior: No Data
IT scan behavior: Supports both over- and underscan
CE scan behavior: Supports both over- and underscan
Colorimetry Data Block:
xvYCC601
xvYCC709
BT2020YCC
BT2020RGB
Reserved MD0
Vendor-Specific Data Block (HDMI), OUI 00-0C-03:
Source physical address: 3.0.0.0
Supports_AI
DC_36bit
DC_30bit
DC_Y444
Maximum TMDS clock: 340 MHz
Extended HDMI video details:
HDMI VICs:
HDMI VIC 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz
HDMI VIC 2: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz
HDMI VIC 3: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz
HDMI VIC 4: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz
HDR Static Metadata Data Block:
Electro optical transfer functions:
Traditional gamma - SDR luminance range
SMPTE ST2084
Hybrid Log-Gamma
Supported static metadata descriptors:
Static metadata type 1
YCbCr 4:2:0 Video Data Block:
VIC 96: 3840x2160 50.000000 Hz 16:9 112.500 kHz 594.000000 MHz
VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz
VIC 101: 4096x2160 50.000000 Hz 256:135 112.500 kHz 594.000000 MHz
VIC 102: 4096x2160 60.000000 Hz 256:135 135.000 kHz 594.000000 MHz
Vendor-Specific Video Data Block (HDR10+), OUI 90-84-8B:
Application Version: 1
Detailed Timing Descriptors:
DTD 3: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (1872 mm x 1053 mm)
Hfront 88 Hsync 44 Hback 148 Hpol P
Vfront 4 Vsync 5 Vback 36 Vpol P
Checksum: 0xea

I understand that Armbian is an experimental build and this combination may simply not work.... but if there's anything I can try to do to help the driver and monitor reconcile with each other, or to help you debug this, please let me know.

(BTW, I don't mind the security timeout/rechecking on this webform, but having it drag focus back to that checkbox is somewhat disruptive.)

sudo armbianmonitor -u

Says:

System diagnosis information will now be uploaded to https://paste.armbian.com/Error adding document.

so I've attached armbian-hardware-monitor.log instead.

armbian-hardware-monitor.log

Unfortunately PCIe always doesn't work on boot, whether it is in u-boot or kernel, with `PCIe link training gen1 timeout` error. 

Just as the following log:

Quote

Trying to boot from SPI

U-Boot 2021.07-rc4-ga2c3fda4-dirty (Jun 21 2021 - 15:28:06 +0800)

SoC: Rockchip rk3399
Reset cause: POR
Model: Firefly ROC-RK3399-PC Mezzanine Board
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Firefly ROC-RK3399-PC Mezzanine Board
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
rockchip_pcie pcie@f8000000: PCIe link training gen1 timeout!

Quote

root@ubuntu-server:/# dmesg | grep pcie
[    3.756325] vcc3v3_pcie: supplied by sys_12v
[   22.150142] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[   22.150185] OF: /pcie@f8000000: Missing device_type
[   22.150203] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[   22.150217] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[   22.150905] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[   22.676881] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[   22.678469] rockchip-pcie: probe of f8000000.pcie failed with error -110
[   33.774070] vcc3v3_pcie: disabling

However, after I manually run these commands, PCIe seems working.

```modprobe -r pcie_rockchip_host
modprobe pcie_rockchip_host

```

Kernel log:

Quote

[  338.208262] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[  338.208315] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[  338.208330] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[  338.209131] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[  338.345743] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[  338.345772] pci_bus 0000:00: root bus resource [bus 00-1f]
[  338.345788] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[  338.345801] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[  338.345853] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[  338.345975] pci 0000:00:00.0: supports D1
[  338.345983] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[  338.350714] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[  338.351105] pci 0000:01:00.0: [197b:0585] type 00 class 0x010601
[  338.351195] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[  338.351206] pci 0000:01:00.0: reg 0x10: [io  size 0x0080]
[  338.351245] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[  338.351253] pci 0000:01:00.0: reg 0x14: [io  size 0x0080]
[  338.351289] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[  338.351297] pci 0000:01:00.0: reg 0x18: [io  size 0x0080]
[  338.351333] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[  338.351342] pci 0000:01:00.0: reg 0x1c: [io  size 0x0080]
[  338.351378] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[  338.351386] pci 0000:01:00.0: reg 0x20: [io  size 0x0080]
[  338.351421] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x00001fff]
[  338.351458] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[  338.351500] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 512)
[  338.351863] pci 0000:01:00.0: PME# supported from D3hot
[  338.352236] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:00.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link)
[  338.356709] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
[  338.356831] pci 0000:00:00.0: BAR 14: assigned [mem 0xfa000000-0xfa0fffff]
[  338.356857] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref]
[  338.356870] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa011fff]
[  338.356893] pci 0000:01:00.0: BAR 0: no space for [io  size 0x0080]
[  338.356904] pci 0000:01:00.0: BAR 0: failed to assign [io  size 0x0080]
[  338.356913] pci 0000:01:00.0: BAR 1: no space for [io  size 0x0080]
[  338.356922] pci 0000:01:00.0: BAR 1: failed to assign [io  size 0x0080]
[  338.356931] pci 0000:01:00.0: BAR 2: no space for [io  size 0x0080]
[  338.356944] pci 0000:01:00.0: BAR 2: failed to assign [io  size 0x0080]
[  338.356956] pci 0000:01:00.0: BAR 3: no space for [io  size 0x0080]
[  338.356969] pci 0000:01:00.0: BAR 3: failed to assign [io  size 0x0080]
[  338.356981] pci 0000:01:00.0: BAR 4: no space for [io  size 0x0080]
[  338.356989] pci 0000:01:00.0: BAR 4: failed to assign [io  size 0x0080]
[  338.357002] pci 0000:00:00.0: PCI bridge to [bus 01]
[  338.357016] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[  338.357335] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[  338.357848] pcieport 0000:00:00.0: PME: Signaling with IRQ 95
[  338.358358] pcieport 0000:00:00.0: AER: enabled with IRQ 95
[  338.434167] ahci 0000:01:00.0: version 3.0
[  338.434209] ahci 0000:01:00.0: enabling device (0000 -> 0002)
[  338.434743] ahci 0000:01:00.0: SSS flag set, parallel bus scan disabled
[  338.434858] ahci 0000:01:00.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f impl SATA mode
[  338.434868] ahci 0000:01:00.0: flags: 64bit ncq sntf stag pm led clo pmp fbs pio slum part ccc apst boh
[  338.442224] scsi host1: ahci
[  338.443217] scsi host2: ahci
[  338.443893] scsi host3: ahci
[  338.445008] scsi host4: ahci
[  338.446838] scsi host5: ahci
[  338.447158] ata1: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010100 irq 96
[  338.447179] ata2: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010180 irq 97
[  338.447188] ata3: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010200 irq 98
[  338.447197] ata4: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010280 irq 99
[  338.447206] ata5: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010300 irq 100
[  338.762463] ata1: SATA link down (SStatus 0 SControl 300)
[  339.073142] ata2: SATA link down (SStatus 0 SControl 300)
[  339.385252] ata3: SATA link down (SStatus 0 SControl 300)
[  339.700894] ata4: SATA link down (SStatus 0 SControl 300)
[  340.013306] ata5: SATA link down (SStatus 0 SControl 300)

Does anyone have any idea about what is going on? Thanks in advance.

$ grep aes /proc/cpuinfo
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid


$ lsmod | grep aes
$

How can one verify that the AES chip is being utilized?

I'm on the Armbian 22.11 Jammy release (Kernel 5.15.y, Release date: Nov 30, 2022).

I think have it enabled (spi-spidev) in armbian-config and I think configured correctly in /boot/armbianEnv.txt:

param_spidev_spi_bus=0
param_spidev_spi_cs=0
param_spidev_max_freq=1000000

Connecting to pins GPIO pin# 19/21/23/24

I still do not see ANY devices matching /dev/spi* - An guidance as to WHY? I have the build framework, but am new to building armbian kernels but could navigate it with some direction.  TIA folks!

[Trying to connect a 240x320 LCD display  using the ST7789-VW controller, not using Arduino IDE]

I have limited experience with XFCE and terminal commands, any help is appreciated thanks.

First you have to enable the rk3328-opp-1.5ghz overlay in armbian-config (System > Hardware > rk3328-opp-1.5ghz) or just add it to the overlays line in /boot/armbianEnv.txt and reboot. Next open the /etc/default/cpufrequtils file and find the MAX_SPEED line. Change the MAX_SPEED to 1512000 and save. Now restart the cpufrequtil service and armbianmonitor -m should show 1512 MHz. If the frequency is still locked then check /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq. If it outputs the lower value then the overlay didn't apply. 

Original post:

Hello, I recently purchased a Libre Renegade (RK3328) and installed the latest Armbian release (Armbian 23.05.1 jammy) from this page. On that same page it lists instructions to adjust the maximum clock speed to 1.5 GHz but they appear to not have any effect as armbianmonitor -m never shows the new maximum clock (I can lower it though, I just can't go above 1296 MHz). I've attempted to enable the  rk3328-opp-1.5ghz overlay using armbian-config but it doesn't appear to be working. Here's my armbianmonitor output: https://paste.armbian.com/iyagokujij (temps are high because I had the fan off, I do have a heatsink and fan)

Thanks in advance for any help you can provide.

TIA

Once the reboot is entered, the console log showed it tried to reboot but stuck with the following info.

The above Armbianmonitor is a zip file, please download it and save as zip file then unzip to get the detail log. I guess it was due to issue in dtb file  but has no clue.

Is there any genius can help on this?

[   97.418882] watchdog: watchdog0: watchdog did not stop!
[   97.672510] reboot: Restarting system
INFO:    PSCI Power Domain Map:
INFO:      Domain Nod State ON (0x0)
INFO:      Doma parent_node 0, State ON (0x0)
e : Level 0, parent_node 0, StatFO:      Domain Node : Level 0, ON (0x0)
INFO:      CPU Node : _node 1, State ON (0x0)
INFO:  0x1, parent_node 1, State ON (0xNFO:      CPU Node : MPID 0x2, pState ON (0x0)
INFO:      CPU N0x3, parent_node 1, State ON (0x␀

journalctl.log lsusb.log

https://libre.computer/products/boards/roc-rk3328-cc/

Pro: 
- yet another RK3328

Cons:

- micro USB powering

Bullseye on hardware viersion v1.0, Focal on v1.3.

They both can't discovery USB3.0 devices through USB3.0  which plug before boot.

I installed openmediavault, setting up share folders on USB3.0 mobile disk, test it can work properly, then reboot. After reboot, Disk can't be discoveryed, light on disk bright but not flash. I keep waiting 30 minutes, no external disk be found. 

And, they can discovery devices on USB3.0 which plug after booted. But sometimes can't, only USB2.0 devices plug in USB3.0 port can be found.

Example, I plug an USB3.0 disk after booted, system auto mount it. But when I unplugged and plug twice ,nothing mounted or shown in fdisk. USB3 to ethernet(MS Model 1663) also, sometimes it can work on USB3.0, and sometimes it cannot work, I need to slow down to plug, to make it work on USB2.0 mode.

I'm using Libre renegade with armbian bullseye minimal.

How can I change splash screen, replacing the armbian logo and 4 penguins, with a personal one?

Has anybody done it eralier?

Thanks in advance

(The first and second images get messed up as I touch on screen, the third image is ok as I don't touch.)

power supply OK, sdcard OK, installed OMV.

For this reason ,https://forum.armbian.com/topic/20237-renegade-aka-roc-rk3328-cc-usb30-not-work-properly/ , I 'freeze' armbian kernal upgrades to make USB-disk work properly.

But, Either poweroff in CLI or in OMV panal, it always reboot.

fw Offical Armbian 22.02.1 Bullseye.

Power Supply 5.5V/3A + microUSB cable, currect Voltage over microUSB port is 5.1V when load 3A.

TF card is Samsung EVO orange.

The node /proc/device-tree/compatible contains the board name roc-rk3328-cc, but the dtb in /boot/dtb/rockchip/ is named rk3288-roc-cc.

Armbian-config queries this node when running "System settings / Dtc" and then looks for roc-rk3288-cc.dtb, but cant find it.

Same with your ROC-RK3399-PC (Renegade Elite): https://libre.computer/products/boards/roc-rk3399-pc/

How do you plan to solve heat dissipation there? And do I get it right that the USB-C in the upper left corner is meant as a generic 12V input?

P.S. I know I could try to bisect between 20.05 and 20.08, but I guess lack of build tag variable for uboot in Armbian 20.05 could cause problems during bisect.

Viewing the instructions under "How to setup and check the RTC module:" https://wiki.52pi.com/index.php/UPS_(With_RTC_%26_Coulometer)_For_Raspberry_Pi_SKU:_EP-0118

The instructions call to use modprobe i2c-bcm2835 however, it doesn't appear that my copy of Armbian 20.08.7 Buster has this driver.

Is there another way to setup an RTC Module? I2C is a completely new topic for me, and not something I have worked with before, thanks in advance

Relevant extracts from serial log:

U-Boot 2017.09-armbian (Nov 19 2019 - 00:09:05 +0100)

Model: Firefly ROC-RK3328-CC
DRAM:  510 MiB

 ____                                 _      
|  _ \ ___ _ __   ___  __ _  __ _  __| | ___ 
| |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \
|  _ <  __/ | | |  __/ (_| | (_| | (_| |  __/
|_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___|
                      |___/                  
Welcome to Armbian Buster with Linux 5.3.11-rockchip64

System load:   0.10 0.14 0.06  	Up time:       2 min		
Memory usage:  22 % of 472MB  	IP:            192.168.11.175
CPU temp:      44°C           	
Usage of /:    5% of 29G    	

[ General system configuration (beta): armbian-config ]

Last login: Sat Nov 23 22:48:50 2019

Using armbian-config I downgraded to kernel 4.4.198 and I now have 919MB of RAM.

U-Boot 2017.09-armbian (Nov 19 2019 - 00:01:47 +0100)

Model: Firefly ROC-RK3328-CC
DRAM:  1022 MiB

 ____                                 _      
|  _ \ ___ _ __   ___  __ _  __ _  __| | ___ 
| |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \
|  _ <  __/ | | |  __/ (_| | (_| | (_| |  __/
|_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___|
                      |___/                  
Welcome to Armbian Buster with Linux 4.4.198-rockchip64

System load:   0.10 0.09 0.03   Up time:       2 min
Memory usage:  8 % of 919MB     IP:            192.168.11.173
CPU temp:      43°C            
Usage of /:    5% of 29G    

[ General system configuration (beta): armbian-config ]

Ray

Thanks a lot!

I was wondering of status of vanilla kernel and linux for ROC-RK3328-CC. I read an article about it being mainlined in 4.17 (http://bbs.t-firefly.com/forum.php?mod=viewthread&tid=2312) but I still see people working through issues on this board. I am mainly interested on ethernet and USB3 support. Not interested in video or sound, although others might. Thought this is the place to ask as there is a lot going on but difficult to scrape all the info on the threads. Thanks!

Getting the bootloop serial getty message on my Libre Renegade OMV4. Logs enclosed. I tried some of the fixes I saw on other threads but to no avail. Those looked like they were for diff devices, but may be CPU specific? 

Any ideas? 

[    6.867997] rk_gmac-dwmac ff540000.ethernet: PTP uses main clock
[    6.868097] rk_gmac-dwmac ff540000.ethernet: Linked as a consumer to regulator.5
[    6.868103] rk_gmac-dwmac ff540000.ethernet: clock input or output? (input).
[    6.868112] rk_gmac-dwmac ff540000.ethernet: TX delay(0x25).
[    6.868118] rk_gmac-dwmac ff540000.ethernet: RX delay(0x11).
[    6.868126] rk_gmac-dwmac ff540000.ethernet: integrated PHY? (no).
[    6.868160] rk_gmac-dwmac ff540000.ethernet: cannot get clock clk_mac_speed
[    6.868780] rk_gmac-dwmac ff540000.ethernet: clock input from PHY
[    6.873799] rk_gmac-dwmac ff540000.ethernet: init for RGMII
[    6.874265] rk_gmac-dwmac ff540000.ethernet: User ID: 0x10, Synopsys ID: 0x35
[    6.874281] rk_gmac-dwmac ff540000.ethernet:         DWMAC1000
[    6.874287] rk_gmac-dwmac ff540000.ethernet: DMA HW capability register supported
[    6.874292] rk_gmac-dwmac ff540000.ethernet: RX Checksum Offload Engine supported
[    6.874295] rk_gmac-dwmac ff540000.ethernet: COE Type 2
[    6.874298] rk_gmac-dwmac ff540000.ethernet: TX Checksum insertion supported
[    6.874302] rk_gmac-dwmac ff540000.ethernet: Wake-Up On Lan supported
[    6.874346] rk_gmac-dwmac ff540000.ethernet: Normal descriptors
[    6.874349] rk_gmac-dwmac ff540000.ethernet: Ring mode enabled
[    6.874356] rk_gmac-dwmac ff540000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    6.888231] rockchip-drm display-subsystem: [drm:rockchip_drm_platform_probe [rockchipdrm]] *ERROR* No available vop found for display-subsystem.
[    6.892100] libphy: stmmac: probed
[    6.892123] rk_gmac-dwmac ff540000.ethernet: No PHY found
[    6.892285] rk_gmac-dwmac ff540000.ethernet: stmmac_dvr_probe: MDIO bus (id: 0) registration failed
[    6.907871] rk_gmac-dwmac ff540000.ethernet: Dropping the link to regulator.5

I tried 4.18 and 4.19, both the ArchlinuxARM package and the armbian packages in beta.armbian.com. I thank you guys for the automated kernel builds! At least I can be up to date on the 4.4 kernel. Shouldn't it be working in mainline after 4.14? Any ideas?

Does anyone have success with this combination?

By reading through topics on the forum, it seems to me that I need to be on the mainline kernel (since it has fbtft and ads7846 drivers), but I'm not finding any packaged images using mainline that will support his board.  

Anyone have a mainline Image for the Renegade? 

I tried the Tinker images which are on Rockchip 3328, but they completely fail to boot.

Only next step I'm seeing is to build a custom kernel, or try to backport the fbtft +  ads7846.  

linux-headers-rockchip64 - Linux kernel headers for 4.4.156-rockchip64 on arm64

do not match the kernel provided by the repository:

linux-image-rockchip64 - Linux kernel, version 4.4.162-rockchip64

This is after updating the cache just now and yes, both packages are installed. Is there some way I can guarantee that the version of my installed kernel and headers always match (apart from compiling them myself)? There is no linux-image-next package for rockchip64 and I'm hesitant to install the nightly release.

I am trying out the latest Armbian image on the Renegade board and after several hours i still do not the analog audio to work. Only the HDMI output is found and used.  

With the Ubuntu images provided by Firefly, the analog audio works fine, so we can exclude that it may be a problem with the hardware.

I have seen in this forums such descriptions for other boards with the 3328 CPU, but from my understanding do that solutions not fit for the Renegade.

May somebody provide me a hint, how to activate the analog output?

Here you can find the Armbianmonitor output:

http://ix.io/1vHd

Here you can find information about the board.

https://www.armbian.com/renegade/

Thank you in advance!

Best Regards,

Jens

When I log in to armbiam temp says 60 but it is in red text.  

This is a new install.

Everything seems to work well enough except DNS.  The browser can't resolve domain names, though it can access the various routers' IP's..

cat resolv.conf shows the head text and nameserver 127.0.0.53

I've tried editing the network connection, adding DNS servers, which had no effect except that systemd-resolve --status shows the correct DNS servers for eth0 (the wired connection).  This cannot be altered by systemd-resolve --set-dns=[DNS Server IP].  It doesn't throw an error but neither does it change anything, even on reboot.

I've tried editing /etc/systemd/resolved.conf with nano, uncommenting and setting the DNS, FallbackDNS, uncommenting and turning LLMNR=no, MulticastDNS=no, Cache=yes, DNSStubListener=no  Saving that and rebooting doesn't change a thing.

I'm on a SOHO LAN and do not have a DNSSEC signed router.

Someone suggested editing ./etc/resolv.conf directly with nano, despite the head text which says it won't work. It doesn't work.

Checking it's local router, there are no error messages.  Apparently, the ROC-RK3328-CC has finished DHCP, is on the MAC and DHCP lists, has the correct IP and can get outside it's local router to the outer routers, just like every other workstation, as long as it uses an IP to get there..

Can anyone PLEASE tell me how to set the DNS server (that actually works)?

Linux indi 4.4.156-rockchip64 #21 SMP Wed Sep 19 13:14:57 CEST 2018 aarch64 aarch64 aarch64 GNU/Linux

I can do the following (as sudo su), but, no voltage on the specified pin (pin 5, Linux pin 4):

echo -n "4" > /sys/class/gpio/export
echo -n "out" > /sys/class/gpio/gpio4/direction
echo -n 1 > /sys/class/gpio/gpio4/value
echo -n 0 > /sys/class/gpio/gpio4/value
echo -n "4" > /sys/class/gpio/unexport

I get no light on my generic LED with a 100k resistor - which lights when I move from pin 5 (Linux pin 4)

MicroSD end of the board ->

[ .   . ]

[ .   . ]

[ .   . ]  <- I'm connected here, pin on left is pin 5/4 (?) and pin 6 is GND

Am I missing a kernel module?

WiringOP and WiringPI libraries aren't working, gpiod (gpioset, gpiodetect, etc) not helping.

This is the pin guide I'm using:

https://docs.google.com/spreadsheets/d/1U3z0Gb8HUEfCIMkvqzmhMpJfzRqjPXq7mFLC-hvbKlE/edit#gid=0

Here is the output of cat /sys/kernel/debug/gpio:

GPIOs 0-31, platform/pinctrl, gpio0:

gpio-0   (                    |vcc_host_5v         ) out hi 

gpio-4   (                    |sysfs               ) out hi  <---- this seems correct to me when /sys/class/gpio/gpio4/value is 1

gpio-30  (                    |vcc_sd              ) out hi    

GPIOs 32-63, platform/pinctrl, gpio1:

gpio-50  (                    |mdio-reset          ) out hi    

gpio-58  (                    |vcc_host1_5v        ) out hi    

GPIOs 64-95, platform/pinctrl, gpio2:

GPIOs 96-127, platform/pinctrl, gpio3:

GPIOs 510-511, platform/rk8xx-gpio, rk8xx-gpio, can sleep:

gpio-510 (                    |?                   ) out hi    

gpio-511 (                    |?                   ) out lo   

Any thoughts would be greatly appreciated, thx

Does armbian perfer ubuntu rootfs for server images now?

and a bit background here: https://github.com/rockchip-linux/kernel/issues/98

Cause I'm not willing to cut out all this stuff from the related threads (this would end in a complete disaster) I try to summarize it here (if something is missing, let me know I'll add it):

• RockChips BSP kernel is not longer an option. Cause it breaks faster that our current resources allow to fix it.
• Having all SoCs under one kernelsource would make it more predictable and decrease the efforts needed to keep them 'reliable working'.
• Ayufans (https://github.com/ayufan-rock64/linux-kernel/tree/release-4.4) tends to be the preferred Kernel at the moment. First attempts to bring up rk3288 boards are made

notify some of the involved people just to make sure they don't miss it (I probably miss some, don't be upset ): @TonyMac32, @JMCC, @tkaiser, @Igor, @zador.blood.stained, @hjc & @ayufan

Some questions which are open for me:

• How can we ensure that the 4.4 kernel we currently use for the RK3288 get at least 'security updates' as long as the switch needs?
• Is someone in touch with ayufan so that he recognizes our idea? (or @ayufan do you read the stuff here )
• Can we 'channel our efforts' to ensure that we don't waste our and others time (e.g. open a transitions branch and make it clear that PRs against the old kernels don't make sense)

I hope this thread doesn't get floated with garbage but on the other side I hope that people write about their plans and 'results' so that we don't do the work twice.  

EDIT: BTW, I'm not sure if this thread fits better in development or here, but I think it's more recognized by the rk-users when we have it here..

@tkaiser From Ubuntu 16.04 image running Rockchip's 4.4 kernel.