Search the Community
Showing results for tags 'nanopi-r6c'.
-
Dear Community, This might only be with the NanoPI-r6c images, but the SHASUM contains a temporary path which you don't have an thus fails. Since we cannot change the SHASUM because then the ASC would fail, I have a temporary workaround: sed 's,/.*/,,' armbian.img.sha | sha256sum -c In a script you could either 1. CD into the directory of the image 2. Run the SHASUM there 3. Use $OLDPWD to return or correct the SHASUM inline: sha256sum /path/to/file | sed 's,/.*/,,' > armbian.img.sha Dantes
-
I'm trying to setup disk encryption, but for some reason its not opening devices after installing cryptsetup-bin on the installation image. After typing the password it just hangs and does nothing $ cryptsetup open /dev/sda sda_crypt Anyone?
-
I upgraded from my own-compiled Armbian kernel 6.8.0-rc5 to 6.8.4 and there are now very annoying stall when for example I drag a KDE Konsole window. Also when I play a 1080p50 HEVC video, as son as a move the mouse, the whole video stalls. Besides 6.8.0-rc5, the normal apt provide 6.8.1-edge-rockchip-rk3588 also works OK. 6.8.5 has the same issue as 6.8.4. As indicated, I use KDE, X11, compositor disabled. Enabled makes no difference. OS base is Armbian Bookworm, but I have also used kernels 6.8.1 and 6.8.4 with a rootfs copied from an RaspberryPiOS and Opensuse-Tumbleweed. RPiOs is also Debian Bookworm, Tumbleweed is latest, KDE6. So it is not KDE6. KDE Wayland leaves black screen still (doesn't work), but that is not a showstopper. Is anyone else experiencing the same? PS: I run mainline as the vendor kernel 6.1.43 fails on running KVM (some tag of the Cortex-A55 is unknown) so qemu-KVM don't work/start and running VMs is a key use-case I bought the NanoPi-R6C for.
-
I have Armbian running on a NanoPi R6C 8GB with 32GB eMMC. I made a new Armbian image with the build framework that uses newest linux-u-boot-nanopi-r6s-legacy 23.8.0-trunk linux-dtb-legacy-rk35xx 23.8.0-trunk linux-image-legacy-rk35xx 23.8.0-trunk Booted from microSD this system has an idle power consumption of 0,92w. I can access both the eMMC and microSD storage. When i transfer this system from microSD to eMMC with "nand-sata-install" to boot & OS on eMMC and cold boot without the microSD, the idle power consumption increases to 1,21w. After a shutdown and booting from the microSD again the idle power consumption is back at 0,92w. So far i have not been able to find a reason for this. The only things i noticed was: (microSD) Device Start End Sectors Size Type /dev/mmcblk1p1 32768 557055 524288 256M Linux extended boot /dev/mmcblk1p2 557056 61702144 61145089 29.2G Linux filesystem (eMMC) Device Start End Sectors Size Type /dev/mmcblk0p1 32768 59998207 59965440 28.6G Linux filesystem While microSD uses a vfat partition for /boot and an EXT4 partition for the OS the eMMC has a single EXT4 partition for everything. Does that change how the system is booting? https://github.com/radxa/u-boot/commit/bf47e8171f44804c7f2004f53d3f05801f8dbbb8 Different drive strength settings in u-boot for when eMMC is boot drive or not? Can that really increase the power usage of the eMMC by 0,3w?
-
When I reboot with kernel 6.8.4 (edge) installed by apt upgrade, I noticed my scripts that uses snapper for remove differential backups. It turns out that, if no cleanup algorithm option is used, snapshot is created. Before the reboot, with kernel 6.8.1 version, there was no issue. I on Armbian Bookworm, but also with other Debian Bookworm based OS running those same kernel binaries. Same failure with 6.8.5 Currently I don't know any more, I could run this faulty kernel in a VM as the .config is such that it also boots on virt hardware (virt-7.2 as Bookworm uses). EDIT: Also in a VM, the problem is there: root@armbian64:/tmp# snapper create -d cleantest --cleanup-algorithm number Creating snapshot failed. root@armbian64:/tmp# snapper create -d cleantest root@armbian64:/tmp# uname -a Linux armbian64 6.8.4-edge-rockchip-rk3588 #1 SMP PREEMPT Thu Apr 4 18:25:06 UTC 2024 aarch64 GNU/Linux
-
Is it possible to activate PCIe ASPM L1 substates with the NanoPi R6C / RK3588s Soc in general? > lspci -vvv | grep ASPM LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- My M.2 NVMe SSD supports all L1 substates but setting pcie_aspm.policy to "powersupersave" has no effect. Max is "powersave" to activate ASPM L1 and that works. Is this a limitation of the SoC or just not implemented in the armbian driver / kernel?
-
On my NanoPi R6C I downloaded the Armbian 23.11 Bookworm CLI and booted the machine from the SD card. Then I installed gnome and firefox. Most things works so far, but I get no sound over hdmi (there is no headphone jack). The gnome - settings - sound shows only the dummy device. Youtube videos play ok, but somewhat laggy and with very high processor load (all cores close to 100% on the gnome system monitor).
-
Now I'm no expert but I got Mate working maybe there are some shortcuts I did not take, but it works great. So feel free to point out any flaws or improve it, #!/bin/sh -vx packages=' cryptsetup libblockdev-crypto2 engrampa firefox ffmpeg libavcodec-extra gufw lightdm lightdm-settings slick-greeter ubuntu-mate-wallpapers-common mate-desktop-environment-extras mate-applet-brisk-menu mate-applets mate-calc mate-indicator-applet ayatana-indicator-application ayatana-indicator-bluetooth ayatana-indicator-common ayatana-indicator-display ayatana-indicator-keyboard ayatana-indicator-messages ayatana-indicator-notifications ayatana-indicator-power ayatana-indicator-printers ayatana-indicator-session ayatana-indicator-sound mate-media mate-menu mate-power-manager mate-sensors-applet mate-session-manager mate-settings-daemon mate-screensaver mate-tweak mate-utils eom mpv plank pluma network-manager-gnome software-properties-gtk libcanberra-gtk-module libcanberra-gtk3-module ubuntu-advantage-tools gnome-software gnome-system-tools update-manager xorg ' apt update -y apt upgrade -y apt install -y $packages ##### fix 'Software' desktop file so it shows up in the 'Control Center' sed -i \ 's,^Categories=.*,Categories=System;Settings,g' \ /usr/share/applications/org.gnome.Software.desktop ##### no default wallpaper, set a mate wallpaper to the login screen cat << EOF > /etc/lightdm/slick-greeter.conf [Greeter] background=/usr/share/backgrounds/ubuntu-mate-common/Grey-Jazz.jpg EOF #sudo apt remove zsh openssh-server openssh-sftp-server avahi-autoipd evolution-data-server* #echo net.ipv6.conf.all.disable_ipv6=1 #net.ipv6.conf.default.disable_ipv6=1 #net.ipv6.conf.lo.disable_ipv6=1 #' |sudo tee -a /etc/sysctl.conf mate-install
-
My audio volume was very very low, and very annoyingly I had to boost to 200% 300% which had the problem that the volume buttons were not working properly. You just cant see anything above 100% unless you go into the control panel. Now when it comes to audio I'm the village idiot, but I found a proper solution I think. After some experimentation I found that the module "module-cli-protocol-unix" ( #20 in my case) can be amplified with pactl set-sink-input-volume 20 10db Now YMMV depending on your attached hardware, so change the 10db to whatever suits your situation. After that I made it permanent by adding it to the /etc/pulse/default.pa like this: # Default volume amplification set-sink-input-volume 20 10db Yay!
-
I am unable to play files over SMB, but I can't seem to figure out what the problem is exactly. From what I can tell it *seems* ffmpeg is compiled without networking support, at least this is what smplayer was complaining about: [ffmpeg] Protocol not found. Make sure ffmpeg/Libav is compiled with networking support. Failed to open smb://192.168.1.1/transmission/myfile.mkv. Exiting... (Errors when loading file) But when I look at the ffmpeg switches it was compiled with: --enable-libsmbclient and seems to be present. Now I'm a complete linux n00b, does anyone have an idea ?
-
What Works: - USB2 and USB3 - PCIe2 - GMAC - eMMC on HS200 mode - Cpufreq - User and maskrom buttons Dmesg Output: https://paste.armbian.com/onelomofit You can download them from Rolling releases section on https://www.armbian.com/nanopi-r6s/ page. Images include devicetrees for R6S and R6C. If you have R6C, you must change the devicetree from armbianEnv.txt.
-
As you can see the WAN-port/NIC registers fine with a label from the nanopi-r6c device tree $ grep fe1c0000 /boot/dtb/rockchip/rk3588s-nanopi-r6c.dtb grep: /boot/dtb/rockchip/rk3588s-nanopi-r6c.dtb: binary file matches dmesg: dmesg | grep fe1c0000 [ 7.287277] rk_gmac-dwmac fe1c0000.ethernet: init for RGMII_RXID [ 7.287373] rk_gmac-dwmac fe1c0000.ethernet: User ID: 0x30, Synopsys ID: 0x51 [ 7.287377] rk_gmac-dwmac fe1c0000.ethernet: DWMAC4/5 [ 7.287381] rk_gmac-dwmac fe1c0000.ethernet: DMA HW capability register supported [ 7.287385] rk_gmac-dwmac fe1c0000.ethernet: RX Checksum Offload Engine supported [ 7.287388] rk_gmac-dwmac fe1c0000.ethernet: TX Checksum insertion supported [ 7.287391] rk_gmac-dwmac fe1c0000.ethernet: Wake-Up On Lan supported [ 7.287423] rk_gmac-dwmac fe1c0000.ethernet: TSO supported [ 7.287426] rk_gmac-dwmac fe1c0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 7.287430] rk_gmac-dwmac fe1c0000.ethernet: Enabled Flow TC (entries=2) [ 7.287433] rk_gmac-dwmac fe1c0000.ethernet: TSO feature enabled [ 7.287437] rk_gmac-dwmac fe1c0000.ethernet: Using 32 bits DMA width However the LAN-port does not have such a label in dmesg output. [ 7.932846] pci 0003:31:00.0: [10ec:8125] type 00 class 0x020000 [ 7.932902] pci 0003:31:00.0: reg 0x10: initial BAR value 0x00000000 invalid [ 7.932905] pci 0003:31:00.0: reg 0x10: [io size 0x0100] [ 7.932958] pci 0003:31:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit] [ 7.932993] pci 0003:31:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit] [ 7.933301] pci 0003:31:00.0: supports D1 D2 [ 7.933303] pci 0003:31:00.0: PME# supported from D0 D1 D2 D3hot D3cold [ 7.948845] pci 0003:31:00.0: BAR 2: assigned [mem 0xf3200000-0xf320ffff 64bit] [ 7.948873] pci 0003:31:00.0: BAR 4: assigned [mem 0xf3210000-0xf3213fff 64bit] [ 7.948899] pci 0003:31:00.0: BAR 0: assigned [io 0x1000-0x10ff] [ 7.950294] r8125 0003:31:00.0: enabling device (0000 -> 0003) [ 7.967108] r8125 0003:31:00.0 (unnamed net_device) (uninitialized): Invalid ether addr 00:00:00:00:00:00 [ 7.967112] r8125 0003:31:00.0 (unnamed net_device) (uninitialized): Random ether addr a2:83:9c:9c:cc:e8
-
I have the newest Armbian 28.08.0-trunk image running on a NanoPi R6C with a 4TB NVMe SSD. The NanoPi is only connected to power and 1G ethernet via the 1G WAN port. When using the machine as NAS with Samba and a Windows client connected there is a strange problem when receiving large files. The files are stored on the NVMe SSD with ~450MB/s read/write via PCIe 2.1x1. When transmitting files from the NanoPi to a SMB client the 1G ethernet is maxed out but when receiving files the connection drops down to ~60 MB/s every few seconds. This instantly gets fixed when using the 2.5G LAN port instead of the 1G WAN port. On that port the RX looks exactly the same as the TX. Both with 112MB/s maxed out speed. I noticed that the 1G WAN port is a combination of GMAC in RK3588s SoC and a Realtek RTL8211F Transceiver while the 2.5G LAN port is a dedicated Realtek RTL8125BG. So i suspect there is something wrong with that combination of GMAC and Realtek Transceiver on the 1G WAN port. I already tried changing the rgmii rx settings with an overlay, but that didn't have any effect. Driver problem?!
-
I did a lot of power consumption tests with my NanoPi R6C and noticed something strange when switching from kernel 5.10.110 to kernel 5.10.160. Hardware NanoPi R6C 4GB 32GB Sandisk High Endurance microSD Card Ugreen 18W USB Power Supply Software Armbian 23.5.1 Nanopi-r6s bookworm Default settings (only changing fdtfile=rockchip/rk3588s-nanopi-r6s.dtb to fdtfile=rockchip/rk3588s-nanopi-r6c.dtb in /boot/armbianEnv.txt) Switching between legacy 5.10.160 and legacy 5.10.110 kernels with armbian-config With just 1Gbit Ethernet and the power supply connected in idle (measured at wall): kernel 5.10.110: 0,92W kernel 5.10.160: 1,21W I also tested different M.2 SSD, with ASPM L1 enabled/disabled, HDMI and USB devices connected/not connected. I even tried different usb power supply. In every case the power consumption with kernel 5.10.160 is higher with no apparent benefit. You could argue that it is not a big difference but when running the system from a battery it is! What is causing this increased power consumption? I tried to run a lot of commands to find the difference between the 2 kernels but could not find a significant one. WinDiff between the 2 kernels:
-
-
I think I found a regression: It seems the USB 3.0 port is not working with kernel 5.10.160. It was working with kernel 5.10.110. So I have two questions: 1. How do I file a bug-report ? 2. Linux 6.3 officially supports the rockchip-rk3588 (6.4 is out). When can we expect a kernel update and which kernel version would that be? Thank you
-
This is a HTML5 audio/video tester for web browsers: https://tools.woolyss.com/html5-audio-video-tester/ As you can see .webm is not enabled because frankly I have no idea which package I need to enable that. I have opus and av1 installed: ii libdav1d5:arm64 0.9.2-1 arm64 fast and small AV1 video stream decoder (shared library) ii libopus0:arm64 1.3.1-0.1build2 arm64 Opus codec runtime library I tried gstreamer1.0-ugly and gstreamer1.0-bad but to no avail. Any idea's which package I am missing?
-
Today I decided to update my kernel to 6.3.9 with the mainline ubuntu kernel/ppa https://ubuntuhandbook.org/index.php/2020/08/mainline-install-latest-kernel-ubuntu-linux-mint/ However this does not work if you have disk-encryption . After rebooting and being greeted by enter your password, it did not work claiming its missing the dm_mod module. This is the device-mapper module needed by cryptsetup to create a device in /dev/mapper/ After running unmkinitramfs on the 6.3.9 kernel /usr/lib/modules/6.3.9/kernel/drivers/md/dm-mod.ko was indeed missing. Is this normal for mainline ubuntu kernels ? and does anyone know how to solve this ?
-
I have serious issues with the serial number being exposed in /proc/cpuinfo. Especially when browsers have access to this information. Afaik, its u-boot who passed this information on to Linux. Any idea how to mask this from Linux? Your help is appreciated
-
This was fun but its still a bit flaky/unstable now and then but overall it seems to work. What is it: KODI multimedia player standalone installation script. Features: Boots directly into KODI with KODI standalone service Enabled Hardware decoding by liujianfeng1994 Encrypted rootfs partition with auto-decrypt on boot Encryption key is randomly generated during installation and inserted into initramfs/crypttab Tested with EXT4 only Installed on Minimal CLI Ubuntu/Jammy installation How to: Download Ubuntu-Jammy-Minimal CLI Copy 'kodi-minimal-cli' to sdcard /root chmod +x /root/kodi-minimal-cli boot from sdcard fill out Armbian questionnaire run ./kodi-minimal-cli install to emmc and choose EXIT after fill out wifi details in network manager if you need it reboot #!/bin/sh -vxe # GPLv3 just in case anyone cares # 0. boot from sdcard (ubuntu/jammy) minimal cli # 1. remove Ubuntu Telemetry/Spyware if any cd /tmp apt \ update \ --yes apt \ purge\ --yes \ ubuntu-report \ popularity-contest \ apport \ whoopsie \ apport-symptoms apt-mark \ hold \ ubuntu-report \ popularity-contest \ apport \ whoopsie \ apport-symptoms cat << 'EOF' >> /etc/hosts 127.0.0.1 popcon.ubuntu.com 127.0.0.1 metrics.ubuntu.com EOF # format /dev/mmcblk2p1 ext4 bootfs format(){ case $2 in ext4) mkfs.ext4 -F -L rootfs $1;; btrfs) mkfs.btrfs -f -L rootfs $1;; f2fs) mkfs.f2fs -f -l rootfs $1;; *) false;; esac } #WORKDIR=/mnt #slower running from storage WORKDIR=$(mktemp -d -p /dev/shm) #faster running from memory TARGET=/dev/mmcblk2 FSTYPE=ext4 grep -q "${TARGET}.*/boot" /proc/mounts && { echo "error: not booted from sdcard" exit 1 } # 2. update and install: apt update --yes && apt upgrade --yes apt install --yes cryptsetup-bin gdisk # 3. run armbian-install and install to emmc, when done choose: exit armbian-install || true # 4. backup data mkdir -p ${WORKDIR}/emmcdata mount ${TARGET}p1 ${WORKDIR}/emmcdata rsync \ --archive \ --info=progress2 \ ${WORKDIR}/emmcdata/ \ ${WORKDIR}/backup sync umount ${TARGET}p1 rmdir ${WORKDIR}/emmcdata # 5. create new partition layout and encrypt disk sgdisk -og ${TARGET} sgdisk -n 1:32768:+512M -t 0:8300 ${TARGET} sgdisk -n 0:0:0 -t 0:8300 ${TARGET} ############################################ #NAME SIZE RO TYPE MOUNTPOINTS #mmcblk2 28,9G 0 disk #├─mmcblk2p1 512M 0 part /boot #└─mmcblk2p2 28,4G 0 part # └─rootfs 28,4G 0 crypt /var/log.hdd # / ############################################ # format 1st/boot partition format ${TARGET}p1 ${FSTYPE} bootfs # create encryption key KEYFILE=/dev/shm/rootfs.keyfile dd if=/dev/urandom bs=$((4096/8)) count=1 of=${KEYFILE} chmod u=r,go-rwx ${KEYFILE} # encrypt 2nd/root partition cryptsetup \ luksFormat \ --batch-mode \ --cipher=aes-xts-plain64 \ --key-size=512 \ --hash=sha512 ${TARGET}p2 \ ${KEYFILE} ROOTFS=/dev/mapper/rootfs cryptsetup \ open \ --key-file=${KEYFILE} \ ${TARGET}p2 \ rootfs # format root partition format ${ROOTFS} ${FSTYPE} rootfs # 6. mount partitions ROOT=${WORKDIR}/restore mkdir -p ${ROOT} mount ${ROOTFS} ${ROOT} mkdir -p ${ROOT}/boot mount ${TARGET}p1 ${ROOT}/boot # 7. restore from backup rsync \ --archive \ --info=progress2 \ ${WORKDIR}/backup/ \ ${ROOT} sync # 8. enable network in chrooted environment cd ${ROOT} touch root/.no_rootfs_resize cp -p /etc/resolv.conf etc/resolv.conf cp -p /etc/hosts etc/hosts cp -p /etc/apt/sources.list etc/apt/sources.list cp -p /etc/apt/sources.list.d/armbian.list etc/apt/sources.list.d/armbian.list # 9. update initramfs-modules, crypttab, fstab sed -i "/^rootdev=/s,=.*,=${ROOTFS}," boot/armbianEnv.txt awk '{print $1}' /proc/modules > etc/initramfs-tools/modules cat << EOF > etc/fstab ${ROOTFS} / ${FSTYPE} defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 UUID=$(lsblk ${TARGET}p1 --noheadings -o UUID) /boot ${FSTYPE} defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 2 tmpfs /tmp tmpfs defaults,nosuid 0 0 EOF KEYDIR=${ROOT}/etc/luks mkdir -p ${KEYDIR} chmod u=rx,go-rwx ${KEYDIR} mv ${KEYFILE} ${KEYDIR} cat << EOF > ${ROOT}/etc/crypttab rootfs UUID=$(blkid -s UUID -o value ${TARGET}p2) /etc/luks/rootfs.keyfile luks,discard EOF #10. chrooted environment mount -o rbind /dev dev mount -t proc proc proc mount -t sysfs sys sys CONFIG=/dev/shm/config cat << 'EOF' > ${CONFIG} #!/bin/sh -vxe apt update --yes apt -o Dpkg::Options::="--force-confdef" --yes install cryptsetup-initramfs ### embed keyfile KEYDIR=/etc/luks KEYFILE=${KEYDIR}/rootfs.keyfile echo "KEYFILE_PATTERN=${KEYDIR}/*.keyfile" >> /etc/cryptsetup-initramfs/conf-hook echo "UMASK=0077" >> /etc/initramfs-tools/initramfs.conf update-initramfs -u ### network manager apt install --yes network-manager ufw ### kodi echo kodi >/etc/hostname hostname -F /etc/hostname PPA='https://ppa.launchpadcontent.net/liujianfeng1994/panfork-mesa/ubuntu' GPG='/etc/apt/trusted.gpg.d/liujianfeng1994_ubuntu_panfork-mesa.gpg' LIST='/etc/apt/sources.list.d/liujianfeng1994-ubuntu-panfork-mesa.list' URL='https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x' KEY='0B2F0747E3BD546820A639B68065BE1FC67AABDE' curl -S "${URL}${KEY}" | gpg --batch --yes --dearmor --output "${GPG}" echo "deb ${PPA} $(lsb_release -sc) main" | tee ${LIST} apt update --yes apt install --yes mali-g610-firmware apt install --yes xserver-xorg xinit kodi unzip make useradd kodi --no-create-home --home-dir /var/lib/kodi echo "kodi:kodi" | chpasswd # cec-adapter usermod kodi -a -G dialout mkdir /etc/sysusers.d/ URL=https://codeload.github.com/graysky2/kodi-standalone-service/zip/refs/heads/master wget ${URL} -O /dev/shm/master.zip unzip /dev/shm/master.zip -d/dev/shm cd /dev/shm/kodi-standalone-service-master/ make install systemd-sysusers systemd-tmpfiles --create || true systemctl enable kodi.service # disable the local resolver and use the one provided by DHCP #systemctl disable systemd-resolved # cat << EOF >> /etc/sysctl.conf # # disable ipv6 # net.ipv6.conf.all.disable_ipv6=1 # net.ipv6.conf.default.disable_ipv6=1 # net.ipv6.conf.lo.disable_ipv6=1 # EOF # sed -i '/#ListenAddress 0.0.0.0/s,^#,,' /etc/ssh/sshd_config # network manager to setup wifi nmtui exit EOF chmod +x ${CONFIG} chroot . ${CONFIG} cd ${WORKDIR} #awk -v WD=${WORKDIR} '$0 ~ WD {print $2}' /proc/mounts | sort -r | xargs umount || true kodi-minimal-cli
-
I've been playing around with the 3d hardware acceleration on jammy, so I can use KODI without stuttering. And that works fine although the KODI version is a bit outdated. So I installed it doing this, under root: add-apt-repository ppa:liujianfeng1994/panfork-mesa add-apt-repository ppa:liujianfeng1994/rockchip-multimedia apt update apt dist-upgrade apt install mali-g610-firmware rockchip-multimedia-config but how do I revert: apt purge --yes mali-g610-firmware rockchip-multimedia-config apt autoremove --yes apt dist-upgrade --yes add-apt-repository --yes --remove ppa:liujianfeng1994/panfork-mesa add-apt-repository --yes --remove ppa:liujianfeng1994/rockchip-multimedia I tried this, but its not a 100%, because I'm having issues with firefox playing videos after. If anyone knows, I'm all ears
-
I've been following this thread: https://forum.openwrt.org/t/nanopi-r6s-linux-6-3-arm-soc-updates/153072/14 downloaded the latest version. Decided to do some experimenting and found out that they use u-boot 2023.04. And after some experimenting I found out that it works with Armbian when I flash it to the internal storage. U-Boot 2017.09-armbian (Apr 25 2023 - 04:20:41 +0000) U-Boot SPL 2023.04-OpenWrt-r0-e283eb2 (Jun 12 2023 - 00:36:27 +0000) Whats the reason the armbian u-boot is so far behind ? (i know its WIP, just asking)
-
Hi everyone, i am using NanoPi R6C which is + integrated with a Rockchip RK3588S + running Armbian_23.2.7_Nanopi-r6s_jammy_legacy_5.10.110 image I need to use 3 UARTs (UART1, UART4, UART5) on this board but don't know how to do, can anyone give me some guides please, i have tried armbian-config but in "Hardware" there is no NanoPi R6C option
-
I had a need to change the macaddress of this device, after looking through the bootloader I spotted 2 offsets: 0x380400 macaddress NIC1 0x380406 macaddress NIC2 I would love an option in the installer, but I did it manually now: # dd if=/dev/mmcblk2 bs=16M count=1 of=bootloader 1+0 records in 1+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 0,0736928 s, 228 MB/s # read_mac bootloader 0x380400 9c:d5:dc:b2:ce:1c # write_mac bootloader 0x380400 $(random_mac) write_mac bootloader 0x380400 $(random_mac) # read_mac bootloader 0x380400 b0:3f:1a:83:9a:da After scripting a couple of functions of course: ### Functions read_mac , write_mac and random_mac are hereby licensed under GPLv3 # read_mac file offset # read_mac bootloader 0x380400 # read_mac /dev/mmcblk2 0x380400 read_mac(){ dd if=$1 bs=1 count=6 skip=$(($2)) 2>/dev/null |\ xxd -l 16 -p | sed 's/../:&/g;s/^://' } # write_mac file offset macaddress # write_mac bootloader 0x380400 aa:bb:cc:dd:ee:ff # write_mac /dev/mmcblk2 0x380400 aa:bb:cc:dd:ee:ff write_mac(){ for hex in $(echo $3|tr ':' ' ');do printf "\x$hex";done |\ dd of=$file bs=1 count=6 seek=$(($offset)) conv=notrunc 2>/dev/null } # print a random macaddress random_mac(){ printf "%012x" \ $(( 0x$(hexdump -n6 -ve '/1 "%02X"' /dev/urandom) & 0xFCFFFFFFFFFF )) |\ sed 's/../:&/g;s/^://' }