Dantes

Can't say I know much about X11, but after playing around with the Cinnamon version I did get a desktop by: created file:/etc/X11/xorg.conf Section "Device" Identifier "Device0" Driver "fbdev" Option "Device" "/dev/dri/card0" EndSection So I figure something in the configuration or driver related ?. And that goes for all Debian flavors I tested. All gave the same error.

Taken from desktop Gnome - works Updated the showip alias for those interested.

Screenshot from something working? because everything is black, cursor left upper corner. I have Xorg log, if you need other logs please specify the ones you need. edit: this is from the Armbian 25.8.2 Trixie XFCE 1.3GB image installed to emmc. Xorg.tgz

@SuperKali This is a blast, been going at it all day. There is no board option for the R76S yet and I cannot post an issue without one. Images tested: Armbian 25.8.2 Noble Gnome Seems to work all right Armbian 25.8.2 Trixie Minimal / IOTX Xorg: cannot run in framebuffer mode. (card /dev/dri/card0), cannot open kernel arbiter, no multi-card support. Armbian 25.8.2 Trixie XFCE Xorg: cannot run in framebuffer mode. (card /dev/dri/card0), cannot open kernel arbiter, no multi-card support. It was tremendous fun

Or wait until the end of the year when 6.18 will be the new Linux version, that enables pretty much everything. RK3588 Mainline Linux Status: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md If you really need a bleeding edge working mediaplayer, LibreElec has experimental support for R6S/R6C: Thread: https://forum.libreelec.tv/thread/29953-le13-testing-for-rk3288-rk3328-rk3399-rk3566-rk3568-rk3576-rk3588/ Downloads: https://chewitt.libreelec.tv/testing/

Why? There is experimental support now for arm64/aarch64. It even has .deb packages https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds /<date>/nightly-linux-aarch64/ Can't get closer to the source than that Edit: @c0rnelius: you were 48mins ahead of me

On what kernel version are you ? HDMI Audio was introduced in the Linux Kernel in 6.15-rc1

Are u kidding me? This is freaking awesome Thanks guys, I will be patiently waiting..

Oh right, I forgot about that. Luckily the rk3576 is already maturing in the Linux kernel. In that case we will just hope for the best. Thank you for your time. edit: Could this topic be moved to https://forum.armbian.com/forum/176-other-families/

Hi guys, I would like to make a support request for the: NanoPi-R76S ($49): https://www.friendlyelec.com/index.php?route=product/product&product_id=308 Thank you for considering. Dantes

Finally there is a proper tor-browser available for arm64/aarch64: 1. Goto https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds/ 2. Navigate into: tbb-nightly.<date>/nightly-linux-aarch64/ 3. Download tor-browser-linux-aarch64-tbb-nightly.<date>.tar.xz 4. Unpack with tar -Jxvf and run tor-browser/start-tor-browser.desktop Yay! (I'm sure you can compile it too from their github page)

Happy new year everyone, So I really do not like the stub-resolver in Debian/Armbian , and I do not like forwarding any DNS request to any 3rd party in general. After some searching I found this: https://www.turek.dev/posts/disable-systemd-resolved-cleanly/ . Since we are on Armbian we need also remove the 00-armbian-default-dns.conf which points to cloudflare's 1.0.0.1 . 1. We probably do not need this, but just in case someone does not have it. sudo mkdir -p /etc/systemd/resolved.conf.d/ 2. We set the DNS Stub Listener to no and remove the comment from the line if applicable: sudo sed -i '/DNSStubListener=/s/^#//;s/=.*/=no/' /etc/systemd/resolved.conf 3. We create the needed symlinks, if applicable. sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf 4. We remove the CloudFlare default DNS sudo rm /etc/systemd/resolved.conf.d/00-armbian-default-dns.conf 5. Then we restart the service: sudo systemctl restart systemd-resolved Now I get my router IP as DNS resolver, which is what I like: $ cat /etc/resolv.conf # This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 192.168.1.1 search lan $

@specs: right you are, its better to use dialout

I think you lose the connection because the kernel is loaded. I do not use the friendly elec tools. I just boot from an OpenWRT image. Get a USB-A to USB-C cable Connect USB-A to PC Connect USB-C to DEBUG port Use screen to connect to the NanoPi: (you might need sudo) screen /dev/ttyUSB0 1500000 Get OpenWRT NanoPi-r6c image and write to sdcard Boot from sdcard with maskrom then you can use scp to transfer files and dd to write/erase/backup I think I did something similar here:

This has been a while , so I'm going from memory here: Cryptsetup-initramfs should be installed into the ramdisk (initrd) , thats why it fails. So something goes wrong in step 14. Try execute steps manually (1-16) and check if you have internet in your chroot. It asks for /dev/mapper/rootfs but that device is not there indicates cryptsetup module is not loaded. That's why you did not get the password prompt and thus the disk is still encrypted. ## Something goes wrong here, try executing all the steps manually (1-16). Step by step. ## If the cryptsetup module is not inserted/loaded, you will get that error. #14. chrooted environment cat << EOF > config #!/bin/sh -vx apt update echo 'force-confdef' > /root/.dpkg.cfg apt --yes install cryptsetup-initramfs rm /root/.dpkg.cfg lsinitramfs /boot/initrd.img* | grep 'usr.*cryptsetup' exit EOF chmod +x config chroot . ./config rm config Good luck.