Dandaman46

Hello @Aknot, better late than never? This is likely because USB OTG support is on out of the box now. You used to have to add an overlay to get it to work. You will need to modify the the overylays to change this.

I found my NanoPi Neo Air's could not list or connect to some wifi networks. Some investigating found this was because channel 12/13 are disabled by default. Nothing in runtime had any effect on the output of iw reg get as it should have. Patching in some firmware fixes worked for me. wget http://ftp.be.debian.org/pub/software/network/wireless-regdb/wireless-regdb-2025.02.20.tar.xz tar xf wireless-regdb-2025.02.20.tar.xz sudo cp wireless-regdb-2025.02.20/regulatory.db /lib/firmware/ sudo cp wireless-regdb-2025.02.20/regulatory.db.p7s /lib/firmware/ sudo iw reg set AU #Australia I can now connect to wifi channel 13. Now for my question: I read in this old thread that armbian-firmware-full is required for wifi. would that mean that the full firmware package is desirable for the Nanopi Neo Air? When running apt-get install armbian-firmware-full it states it will consume an additional 1gb of disk space. Hardly desirable for a little device. VERSION v25.5.1 for NanoPi Air running Armbian Linux 6.12.30-current-sunxi

Hi Dan, how did you go with this one. Any luck? I didn't know these chips supported sleep and hybernate modes.

Has anyone had success turning off the wifi chip completely from user space? I would like to turn it off for periods of time then turn it back on. I've tried figuring the GPIO pin, but of course it can't be exported as it's in use. I'm thinking of creating a device overlay to give me manual control of the pin.

@Igor I'll have a look through that thanks! I'll report back my findings if they are substaintial. To anyone finding this thread in future feel free to leave your comments.

Hello, Do you guys have some tips on reducing power consumption to an absolute minimum? I've made some progress and reduced it to about 500mW on idle. with some CPUs shut off. I would like to get it lower for battery saving. I'm currently building a custom image with as much of the functions I don't need (SPI, i2c, bluetooth etc) turned off hoping that I will get some more power savings. Not sure if this will make a difference yet. Ideas would be appreciated!

@Sma ads7846 is a touch screen driver module.

Hmmmmm interesting. You are using ads7846 right? I'ved Confirmed the Linux 5.15.93-sunxi works, and the latest doesn't. If we could work backwards to different version of the kernel we might be able to find the offending code change.

I haven't been able to get it working on the nanopi neo air yet.

The only notable difference I could see was this line from dmesg Not working 6.6.12 ads7846 spi0.1: touchscreen, irq 80 5.15.63 working ads7846 spi0.1: touchscreen, irq 113 Perhaps there is a mapping issue going on.

Thanks for sharing your journey. I've got to the exact same spot with the new kernel. SPI ADS7846 device connected and recognized with evtest, just no interrupt is trigger when pressing the screen. I am using a custom build of 6.6.12-current-sunxi. with all else being identical to my previous working build of 5.15.63. I compared the the output of gpioinfo and all the gpio connections seem to be configred correctly. root@nanopiair:~# evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: ADS7846 Touchscreen Select the device event number [0-0]: 0 Input driver version is 1.0.1 Input device ID: bus 0x1c vendor 0x0 product 0x1ea6 version 0x0 Input device name: "ADS7846 Touchscreen" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 100 Max 4095 Event code 1 (ABS_Y) Value 0 Min 100 Max 4095 Event code 24 (ABS_PRESSURE) Value 0 Min 0 Max 4095 Properties: Testing ... (interrupt to exit) ..... more crickets Perhaps an update in the kernel has broken something? Any tips would be great I've been stuck for a while on this one!

The build system is in a bit of flux at the moment. The documentation hasn't caught up all the way. Can you use the docker build process instead? Ensure you have docker installed, download the git repo and run the following. ./compile.sh build BOARD=nanopiair BRANCH=current BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm

Are you using nmcli to create your access point? If not, what is your process for setting up the access point?

Is this still the case with the debian build?

Thanks for the clarification!

The release blog for Suni mentioned Fast and Safe Updates Is this referring to the streamlining of the apt-get or apt packages, or is there a new update to be used? I looked through the release notes and other sources and couldn't find anything. https://www.armbian.com/newsflash/armbian-23-05-suni/ Fast and Safe Updates: Our streamlined system allows for fast and safe updates, ensuring that users can easily stay up to date with the latest improvements and security patches.

Just bumping this, delighted to see boot splash start working after an apt-get update, would like to change the image though, any advice anyone?