Search the Community
Showing results for tags 'nanopi-r6s'.
-
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 got Armbian 23.8.2 Bookworm with Linux 5.10.160-legacy-rk35xx successfully running on a couple of NanoPi R6S boxes. So far so good. Now I would like to use Wifi dongles (USB sticks) that I have on these machines. They use the `ath9k_htc` kernel driver. I have used this successfully on ARM-based machines earlier. However, Armbian does not provide this module. So I need to compile it myself (either obtain the exact sources that were used in the kernel I'm currently running, so I can recompile this single module or, perhaps more realistically, start a custom tree with the Armbian patches and config, from which I can rebuild on my own). I'm familiar with Linux kernel compilation from the mainline kernel sources (and cross-compilation is no issue here since I can run the compilation on the ARM box itself), but not the way Armbian does it. So my question is: how do I obtain a copy of the sources (and config file!) that were used to compile the precise kernel that I installed? I read on https://docs.armbian.com/Developer-Guide_Build-Preparation/ that one can regenerate the Armbian kernel by cloning https://github.com/armbian/build and then running something like this: ./compile.sh BRANCH=legacy BOARD=nanopi-r6s kernel However there are a number of issues with this: first it requires root access which is something making me quite uneasy¹ (I just want to recompile a kernel), second it proceeds to the full build without letting me stop to examine the config, review the patches; third, I'm not even sure the parameters I passed are the exact right ones to recreate the kernel that's currently running on my system. So, question: how can I produce an Armbian kernel tree for 5.10.160-legacy-rk35xx for the nanopi-r6s board with the patches and config that are running on my system, and then pause so I tweak the config and do whatever I feel necessary before starting the compilation? And if possible, in a way that does not require root access. Many thanks in advance! Footnote: 1. Just to be clear, my uneasiness is not about security issues per se (I'm running Armbian anyway, so of course I have to trust the Armbian devs), but once something starts running as root, there's no telling what it modifies where. For example, I just discovered it had written lots of junk in /root/.cache which has very little storage place, and I'd like to avoid this sort of problems.
-
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.
-
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?
-
Hi all, For most Nanopi devices there are packages in the registry which contain the u-boot files, for example: https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-u-boot-nanopi-r4s-current/ Is there a reason these packages aren't present for the Nanopi R6S? The reason behind this question is that I used to extract the u-boot from these packages to experiment with other OS'es which have no official release for a certain device. Of course I can get the u-boot from the downloadable images its first couple bytes, but downloading just the package is way smaller. If there is another source to obtain the u-boot blobs I am all ears. I found that I can build them myself from the armbian/build repository with something like this but this isn't as lean as just downloading a package: ./compile.sh \ BUILD_ONLY=u-boot \ BOARD=nanopi-r6s \ BRANCH=legacy \ RELEASE=focal \ BUILD_MINIMAL=yes \ BUILD_DESKTOP=no \ KERNEL_CONFIGURE=no Hopefully someone could point me in the right direction, thanks for all the time in getting support to these ARM devices ♥️
-
Hi there, I'm using the latest version of armbian to run the linuxptp for the ieee1588v2 clock. When I check the timestamp status, the 1Gbps port which is the RTL8122 is no problem, but the 2.5G ports RTL8125BG are only supporting the software timestamp. However, when I checked the Realtek website, it says that the 8125BG also supports the IEEE1588 clock. I tried to install the driver, but it did not work. As a beginner in Linux, I probably don't have the knowledge to compile drivers, in this case I sincerely hope that armbian could officially support the hw ptp timestamp in 8125 NIC. Thank you very much! nanopi-r6s:~:# ethtool -T end0 Time stamping parameters for end0: Capabilities: software-transmit software-receive software-system-clock PTP Hardware Clock: none Hardware Transmit Timestamp Modes: none Hardware Receive Filter Modes: none nanopi-r6s:~:# ethtool -T end1 Time stamping parameters for end1: Capabilities: hardware-transmit software-transmit hardware-receive software-receive software-system-clock hardware-raw-clock PTP Hardware Clock: 0 Hardware Transmit Timestamp Modes: off on Hardware Receive Filter Modes: none all ptpv1-l4-event ptpv1-l4-sync ptpv1-l4-delay-req ptpv2-l4-event ptpv2-l4-sync ptpv2-l4-delay-req ptpv2-event ptpv2-sync ptpv2-delay-req
-
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 ?
-
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
-
I just wrote the Armbian Ubuntu Jammy Desktop image to an SD HC card and booted up fine with it (although I can only boot if I disconnect the HDMI cable -- when boot up is finished, I can plug it in and use the desktop. That's another story, but I have the same issue with official NanoPi Ubuntu images. Next, I transferred the Armbian OS to the eMMC and indicated that I wanted both the boot and system to be on the eMMC. After transferring the rootfs and getting the Power Off prompt, I powered off, then removed the SD HC card, then attempted to boot. However, when I tried to power on again, the NanoPi went into a reboot loop. Armbian will not boot without the SD card inserted. I just get a splash screen and a few lines of text and then it cycles all over again. I booted up again with the SD card looking at the "df" command, I can see that the OS is actually on the eMMC, but the /boot partition is still on the SD HC card. I attempted to update the bootloader with the armbian-install command -- it only gives a single option to update the bootloader on SD/eMMC (doesn't give a way to choose between those two devices). That didn't solve my booting problem. I still needed to have the SD HC card inserted too boot. Then I tried the OS transfer again and that didn't work either. Is there a solution to this? It seems the Armbian installer just can't properly update the eMMC so that I can boot from there.
-
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
-
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/^://' }
-
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
-
-
Hello, I don't know if I'm posting in the right section, if I'm wrong, please excuse me and move the topic to the correct section or tell me which section to write in. I will soon be the proud owner of a NanoPi R6S and would be happy if I could help create a working image for it. I don't have positive experience with compiling a kernel for SoC, but I can test images Regards,