Rockchip

Has anyone made WiFi adapter MT7601u to work with Rockchip64 as AP? I'm unable to compile the driver. I've tried: https://github.com/muratdemirtas/MT7601u https://github.com/Vyacheslav-S/mt7601u-AP https://github.com/Anthony96922/mt7601u-ap I've installed current headers, build-essential libncurses-dev bison flex libssl-dev libelf-dev. Any help appreciate it.

Hi, I'm a user of nanoPC T4( RK3399), now i'm using offical ubuntu release. did Armbian for nanoPC T4 support it's MIPI dual camera? ISP? and other media function? thank you!

Hi all, I am running armbian bookworm on a nanopi r6c (rk3588). At boot, wireguard does not resolve the endpoint (strange, because it runs after network-online.target) and instead of keep trying, it gives up. If I manually restart it, all is good. Attached screenshots show the different behaviour in a raspberry pi (rpi4 as hostname) running raspios, where it keeps trying to resolve the endpoint, and nanopi r6c not retrying. I will recompile kernel to enable wireguard debug (or is there a quicker way?)

Hi, I have armbian image with kernel 4.4.184-rockchip64. Now I want to connect with Wifi using commands but I dont know how to connect using commands. I am able to connect with WiFi using Graphical tool. Below are my observations: a) Instead of wlan0, p2p0 interface is used to connect with wireless network. b) I am able to scan with wlan0 using below command: iw dev wlan0 scan c) iw dev p2p0 scan gives output associated interface( the one connected using Graphical Tool). d) I created wpa_supplicant.conf file and executing below command shows wpa_supplicant initialized but does not get IP address. wpa_supp…

OS: Armbian_22.11.0 (5.15.71) for RockPi-4C HW: RockPi-4C I would like shared my eth0 connection via integrated wlan0 adapter. I have do all steps stated here: https://linuxhint.com/create-wifi-hotspot-linux-mint/ but when I try to connect my notebook to the hotspot wlan, notebook does not get proper IP address and so a internet sharing does not work . Any ideas to solve this problem?

I'm trying to install wiringpi by following the instruction given here https://github.com/Pavelectric/WiringPi_M4. Most of the steps that I followed worked fine but when I do the very last command below, I get a following error, I googled how to deal with this kind of error, and some people tell that 'ContextualZipFile' in archive_util.py doesn't have to be installed so I just need to comment that out. Although, I couldn't find '/usr/local/lib/python3.6/dist-packages/setuptools-33.1.1-py3.6.egg/setuptools/archive_util.py', I did that comment out solution to the all files below, which I got by doing find-command-research Now I d…

Anyone know the plans to get the HDMI outputs active on Rock 5B and the 6.x kernels? I thought it was working on one 6.2rc2 build earlier but lately I have not been able to get any visuals out from Armbian builds using edge kernels.

at the first launch, I ran into the problem that the board cannot connect to the lan Internet via cable, it writes permanent connection and disconnection in the admin console. therefore, I cannot find out the ip address and understand what to connect to. Please help me if someone knows or has solved this problem.

I connect the rockpi 4 to a Samsung display whose normal resolution is 1680x1050 via a hdmi to dvi line, but the maxium resolution I can choose is 1280x1024. And when I connect it to a 4K tv via hdmi, the maxium resolution is 1920x1080, not 3840x2160. The legacy kernel (4.4.210) works perfectly in both cases.

I originally installed Armbian witk Kernel 4.4 on my Nanopi.m4 and later upgraded it to 5.10 via armbian-config. Things work fine but whenever I got a new update via apt update, things get messed up a bit the /boot/Image got linked to vmlinux-4.4.213-rk3399 instead of vmlinuz-5.10.35-rockchip64 while others uInitrd -> uInitrd-5.10.35-rockchip64 dtb -> dtb-5.10.35-rockchip64 The result's the board couldn't boot-up, when I restarted it. And, I need to correct the Image -> vmlinuz-5.10.35-rockchip64 and doing mkimage -C none -A arm -T script -d boot.cmd boot.scr from another linux machine to the SDCard. It works fine …

I had compiled the Armbian image: Buster server. It shows like: Linux version 5.4.35-rockchip64 (root@ubuntu-bionic) ??? uname -r 5.4.35-rockchip64 If I download the linux headers it downloads them, but version 5.4.32-rockchip64. If I do : apt-get source linux-source-$(uname -r) Reading package lists... Done E: You must put some 'source' URIs in your sources.list root@rockpi-4b:~# I can't compile the device drivers, since the headers are different.

Installed the image Armbian_20.08.1_Rockpi-4b_buster_current_5.8.6.img.xz . Then, in armbian-config -> Software, I had installed linux headers + source. I got two new directories: linux-headers-5.7.15-rockchip64 linux-source-5.7.15-rockchip64 If I execute: uname - r I get: root@pi:~# uname -r 5.8.6-rockchip64 The kernel version and installed source/headers are not the same, so they are useless. How to get the correct source/headers? EDIT: When first boot, the OS asked for locale/timezone settings, I did hit ENTER as default and it set the locale language to Slovene. When doing apt-get up…

The images Debian Bookworm "Minimal/IOT images with Armbian Linux v6.12" generate what I understand is bad partition information. Once flashed to the SD card, the partition won't be recognised by Linux hinted by the message "couldn't find valid filesystem superblock", therefore they can't be mounted. The desktop image is fine though and the partitions generated after flashing into the SD card are recognised by the "disks" application. I've also tried with the Ubuntu-rockchip image which also generates correct/mountable partition information. I've tested this for the minimal images for OrangePi Max as well as OrangePi 5 Plus. The images were flashed with…

Hi all! There's a dedicated RTC chip in Rock3A (HYM8563TS), but unfortunately it doesn't work right with the standard Armbian image. The chip is correctly identified, but the problem is with the RK809 PMIC, which also contains an RTC. During boot RK809 is labeled as rtc0, and HYM8563TS as rtc1, and by default kernel uses rtc0 for hwclock manipulations. Since RTC battery is connected to HYM8563TS, after power cycle RK809 is reset to 2017-08-05 09:00:00. | _ \ ___ ___| | __ |___ / / \ | |_) / _ \ / __| |/ / |_ \ / _ \ | _ < (_) | (__| < ___) / ___ \ |_| \_\___/ \___|_|\_\ |____/_/ \_\ Welcome to Armbian 23.11.1 Bookwo…

I’m using an Android TV Box X96 X6. Right now, I want to find a way to install Armbian on it, but I haven’t been able to figure it out yet. I’d appreciate any help or guidance from the community.

After a recent update to non-kernel stuff, my Helios64 will no longer boot. When attempting to, I get this error: [ 32.425508] xhci-hcd xhci-hcd.3.auto: Host halt failed, -110 [ 35.019496] xhci-hcd xhci-hcd.3.auto: Host halt failed, -110 [ 35.020028] xhci-hcd xhci-hcd.3.auto: Host controller not halted, aborting reset. I had been using the eMMC on board to boot with the SD card as a backup, but now neither one is working. Anyone know if there's a way to fix this? Here's more, using verbosity=4 in the armbianEnv.txt. Spoiler DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x7…

Would like to be running fail2ban but missing an important kernel module -> xt_multiport Any ideas on obtaining this? modprobe: FATAL: Module xt_multiport not found in directory /lib/modules/6.12.22-current-rockchip64

Just wonder if there is a good guide how to make dri work and allt the supported code´s work in wayland / xorg or other / Thanks

Hi, I have major issues with my helios64 / ZFS setup - maybe anyone can give me a good hint. I'm running the following system: Linux helios64 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux I have a three WD 4TB Plus disk - on each disk is encrypted with luks. The three encrypted disks are bundled into a raidz1 zpool "archive" using zfs. Basically this setup works pretty good, but with rather high disc usage, e.g. during a scrub, the whole pool degrades due to read / crc errors. As example: zpool status -x pool: archive state: DEGRADED status: One or more devices are faulted in response to persisten…

Hey, I think a dedicated topic for ZFS on Helios 64 is needed. Many people want to have it As we know, and many of us playing with dev builds for helios ,it is no easy to work with ZFS I wrote few scripts maybe someone of You it can help in someway. Thanks @jbergler and @ShadowDance , I used your idea for complete it. The problem is with playing with OMV and ZFS plugin. then dependencies remove our latest version of ZFS. I tested. everything survived but ZFS is downgraded to latest version from repo for example: root@helios64:~# zfs --version zfs-0.8.4-2~bpo10+1 zfs-kmod-2.0.0-rc6 root@helios64:~# uname -…

Hi All, I am on my Helios64 (already have a Helios4). I am running 2 x 8TB, 1x 256 M2, OMV5 debian etc. I have ZFS running (from the wiki instructions) in a basic mirror format, and if I add a few drives I think it would still be a mirror, however I have the following question. It seems far more complicated than MDADM, and potentially more unstable (not in terms of the underlying technology, but in terms of changing these kernals etc every week). Do you think for an average home user that this is really worth it or will constantly need work? To change it would mean starting again, but I do not want to change the setup every month and wo…

Hi! Does anyone have experience comparing ZFS performance on different operating systems on the same hardware. It is very interesting to compare the performance on FreeBSD and Linux.

Hi, i have successfully installed my new helios64 and enabled zfs. Everythings works so far, but it seems I'm missing something "important" in regards to ZFS. I did the following tests: I took one of my WD 4TB Plus drives (in slot 3) and formatted the disk with a) ext4 (mkfs.ext4 /dev/sdc) b) btrfs (mkfs.btrfs /dev/sdc) and c) zfs (zpool create test /dev/sdc). Based on these 3 formats I did a "dd if=/dev/zero of=test2.bin bs=1GB count=5" to measure write performance and a "dd if=test2.bin of=/dev/null" to get the read performance (all tests were done 3 times, results averaged) The results I got look like this: a) ext4 ...…

To continue discussion from Helios64 Support Noted, we will enable ZFS support after Armbian 20.11 released. I will need your help to test since i don't have system with ZFS.

Hey, posting this in hopes that someone might have an ideas as to why this is happening. I've been dealing with an issue with my ZFS pool for a while now where the pool gets suspended but there are no other error indicators. WARNING: Pool 'rpool' has encountered an uncorrectable I/O failure and has been suspended. I'm using ZFS on top of LUKS and used to have problems with my drives resetting due to SATA errors, but I haven't really seen that issue since I started using my own SATA cables and limiting SATA speed to 3 Gbps. My working theory for last week has been that it's a problem with the CPU, perhaps some handover between big.LITTLE. So I've t…

I'm trying to understand the role of zram and having some difficulties with it. I've looked in several places and my understanding is this: - It's a block device in RAM that uses compression - It functions similar to swap I notice that mine is set to about 2 Gb: wurmfood@helios64:~$ cat /proc/swaps Filename Type Size Used Priority /dev/zram0 partition 1945084 0 5 My questions: 1. Does that mean 2 Gb of the device RAM is used for the zram swap device? 2. I can understand this on devices with slower storage, b…