Dantes

I think I found the problem So I compared logs from a working x86-64 system with the R6C aarch64 and as you can see mpv is compiled without --enable-libsmbclient $ grep Configuration aarch64_mpv.log | $ grep Configuration x86-64_mpv.log [cplayer] [cplayer] Configuration: Configuration: ./waf ./waf configure configure --prefix=/usr --prefix=/usr --libdir=/usr/lib/aarch64-linux-gnu | --libdir=/usr/lib/x86_64-linux-gnu --confdir=/etc/mpv --confdir=/etc/mpv --zshdir=/usr/share/zsh/vendor-completions --zshdir=/usr/share/zsh/vendor-completions --enable-cdda --enable-cdda --enable-dvdnav --enable-dvdnav --enable-libmpv-shared --enable-libmpv-shared > --enable-libsmbclient --enable-sdl2 --enable-sdl2 > --enable-sndio --disable-build-date --disable-build-date --enable-dvbin --enable-dvbin $ $ Just to be clear: celluloid depends on mpv which depends on ffmpeg On x86-64 (Ubuntu 22.04 LTS) where it works: * ffmpeg (4.2.7) is compiled without --enable-libsmbclient * mpv (0.32.0) with --enable-libsmbclient On aarch64 (Armbian/Ubuntu 22.04 LTS) where it does not: * ffmpeg (4.4.2) is compiled with --enable-libsmbclient * mpv (0.34.1) without --enable-libsmbclient I hereby humbly request someone with more skills to verify my findings and hopefully we can all enjoy playing files over smb:// in the future

I hate to sound like a broken record, but that 3rd party NanoPI OpenWRT image I suggested in the other thread comes with SMB4 preinstalled. Its real easy to setup (5 mins). If the problem is the same, it could be a driver, dtb-file or something else both have in common. If not, then its something to do with Armbian itself.

There is a thread on OpenWRT, where it show it can be installed on sdcard or emmc. You could try installing those and measuring the power usage between sdcard and emmc. If the problem is the same, I'll bet its somehow related to the emmc driver. link: https://forum.openwrt.org/t/nanopi-r6s-linux-6-3-arm-soc-updates/153072/34 link to images for nanopi: https://github.com/mj22226/openwrt/releases/tag/linux-6.4

Yes, that's how it is done , but "conv=notrunc" only make sense if the output is a file , not if it is a block device. I made the matrix so I could get a clearer picture of what you where asking, but this adds and extra dimension for sure. Did you try disabling CEC, I reckon you are not using a TV with a remote control ? That might be as you said the cause (HDMI-CEC).

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 ?

@Jiff Just curious, do you have the original case or did you make one yourself ?

@Jiff You need to go in over serial, just plug a usb-c into the serial port of the r6s/r6c/t6 , then plug the other end into the usb-a/c into your workstation and setup screen, termux or any other terminal emulator. You can't the serial connection does send and receive. You need send for the keypresses. They use legacy u-boot for stability reasons iirc. Nothing is stopping you from using the newer version. (I tested 2023.05 from OpenWRT in one of the threads and it works fine afaict.) Glad to hear that, happy tinkering Dantes

@Jiff You can check it with this: # dd if=/dev/mmcblk2 bs=16M count=1 | strings | grep -i tftp You will get output that looks something like this: tftp ## TFTP bootm %s at %s size 0x%lx ## TFTP flash %s to partititon '%s' size 0x%lx ... TFTP server died boot image via network using DHCP/TFTP protocol tftpput TFTP put command, for uploading files to a server tftpflash flash image via network using TFTP protocol tftpbootm tftpbootm aosp/uImage/FIT image via network using TFTP protocol download image via network using TFTP protocol boot image via network using BOOTP/TFTP protocol get - try to retrieve a pxe file using tftp TFTP error: TFTP error: '%s' (%d) TFTP %s server %pI4; our IP address is %pI4 1+0 records in 1+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 0,520146 s, 32,3 MB/s then its just setting up the tftp server: https://community.arm.com/oss-platforms/w/docs/495/tftp-remote-network-kernel-using-u-boot So afaict, it does, but you still have to boot into u-boot to verify if the tftp commands are working. Dantes

device emmc-boot sdcard-boot idle updates reboot NanoPi r6c 4GB no-emmc n/a yes 0.92 0.92 0.92 NanoPi r6c 8GB emmc 32GB no yes 0.92 0.92 0.92 yes no 1.21 1.21 1.21 Is the above correct ? The difference afaict is that the OS is running from the *emmc* but you could test if it has something to do with the boot sequence by: 1. Backup and checksum EMMC boot image # dd if=/dev/mmcblk2 bs=16M count=1 > /tmp/emmc-boot.img # sha256sum /tmp/emmc-boot.img | tee emmc-boot.img.sha256sum # strings /tmp/emmc-boot.img | grep 'U-Boot SPL' 2. Backup and checksum sdcard boot image # dd if=/dev/mmcblk0 bs=16M count=1 > /tmp/sdcard-boot.img # sha256sum /tmp/sdcard-boot.img | tee sdcard-boot.img.sha256sum # strings /tmp/sdcard-boot.img | grep 'U-Boot SPL' If the output differs you could transfer the sdcard boot image to the emmc by: 1. Backup EMMC partition table # sgdisk --backup=/tmp/partition-table.original /dev/mmcblk2 2. Copy all created files to the sdcard from /tmp then: 3. Write sdcard-boot.img to EMMC # dd if=/tmp/sdcard-boot.img bs=16M count=1 of=/dev/mmcblk2 1+0 records in 1+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 0,0489076 s, 343 MB/s 4. Restore EMMC partition table # sgdisk --load-backup=/tmp/partition-table.original /dev/mmcblk2 Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. 5. Reboot and test with the power meter If it fails, or if you want to revert, you can boot from sdcard and then write emmc-boot.img back to the emmc: # dd if=emmc-boot.img bs=16M count=1 >/dev/mmcblk2 Good luck, Dantes

@Jiff Thanks again for the elaborate write ups, lately time has not been on my side It all seems very impressive and I will take some time to read it thoroughly. I did a write up for Ubuntu Jammy with MATE (on a r6c) which has video acceleration enabled. It pushes 40°C when playing 1080p with mpv/celluloid with the ambient room temperature around 25°C. This could be a daily driver IF the kernel/security updates were more frequent, but as of now I'm hesitant to do any administrative duties like banking on it. I think I will designate the r6c as a router when OpenWRT is supported. Which means I will buy a T6 to do some more experimenting, yay! I'm very happy that the power consumption is very low for these devices. The internal flash is fast enough around 250MB/s, but 32GB is not much space. So I will be needing a proper size M.2 Thanks for all the feedback, Dantes

Did you check running services ? There might be some extra services installed after the updates. You could use the u-boot bootloader that comes with OpenWRT (unofficial as of yet) to verify, but that requires some tinkering. U-Boot SPL 2023.04-OpenWrt-r0-1f3cc70 (May 21 2023) that can be found here: https://forum.openwrt.org/t/nanopi-r6s-linux-6-3-arm-soc-updates/153072/15

I think it might be related to the USB3.0 port , which does not work in 5.10.160. A fix has been submitted for that and has been accepted, so its waiting on the 170. That Lexar is mighty interesting, but still a bit pricey for the 4TB. Does you 2TB fit properly or did you leave the bottom out ?

Hi Jiff, This is very much appreciated, especially when its a very detailed write up like this. So thank you very much for putting in the time. This unfortunately, means for me that I have part with my money yet again Are there any drawbacks in the T6? That power button I saw is a bit cumbersome for my fingers from what I could see from the images. Do I need to keep a pen around ? Thanks again, Dantes

Running from a battery, very interesting.. I'll be following this thread I'm still on the edge to buy an M.2 because a lot of them are power hogs. So what brand/type M.2 did you use ?

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

Armbian/Jammy is working like a charm, thanks guys. Settings up the encryption was a bit of bitch but its working as you can see. Any chance of adding encryption to the installer?