Search the Community
Showing results for tags 'nanopiair'.
Found 5 results
-
Hi Folks, I have a NanoPi NEO Air with Armbian Bookworm. Previously I was running Armbian 23.11.1 Bookworm with Linux 6.1.63-current-sunxi, but after an apt upgrade I am now with Armbian 24.2.1 Bookworm with Linux 6.6.16-current-sunxi. With this latest upgrade I completely lost the USB console feature which for my application is a MUST. How can I fix it? Have a nice day, Mattia
-
Hi, I am using my armbian board to create an access point. I have noticed that WPS is always active by default and users are, especially on WIndows, prompted to enter the WPS PIn in order to connect to the WIFI instead of the pass phrase. I have checked wpa_supplicant.conf which looks like is controlled by dbus <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <policy user="root"> <allow own="fi.w1.wpa_supplicant1"/> <allow send_destination="fi.w1.wpa_supplicant1"/> <allow send_interface="fi.w1.wpa_supplicant1"/> <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/> </policy> <policy group="netdev"> <allow send_destination="fi.epitest.hostap.WPASupplicant"/> <allow send_interface="fi.epitest.hostap.WPASupplicant"/> <allow send_destination="fi.w1.wpa_supplicant1"/> <allow send_interface="fi.w1.wpa_supplicant1"/> <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/> </policy> <policy context="default"> <deny own="fi.w1.wpa_supplicant1"/> <deny send_destination="fi.w1.wpa_supplicant1"/> <deny receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/> </policy> </busconfig> HOw can I disable this WPS option to kick in? thank you, Tibibs
-
Hello. Can't run x11 on Debian 11. I am using Nano Pi AIR (Allwiner h3). Since the board is not officially supported, I built the image on debian 11 myself. root@nanopiair:/# uname -a Linux nanopiair 5.15.44-sunxi #trunk SMP Wed Jun 8 08:41:04 UTC 2022 armv7l GNU/Linux The LCD is connected via SPI, chip is ili9486. Device tree file has been created, I can see the loading process and the console on the screen. I'm trying to start the X-server by "startx" from ssh session, but for some reason it ends immediately after the start. I tried using fbdev or fbturbo as driver. I also tried to remove the config with the driver in general (section "Device"). Here is the X server log when starting without explicitly specifying a driver: https://pastebin.com/zMXaQngf The only error is: [403138.174] (EE) modeset(0): glamor initialization failed I try to use fbturbo driver. root@nanopiair:# cat /etc/X11/xorg.conf.d/50-fbturbo.conf Section "Device" Identifier "Allwinner A10/A13 FBDEV" Driver "fbturbo" Option "fbdev" "/dev/fb0" Option "SwapbuffersWait" "true" EndSection I get Xorg.log with errors "FBTURBO(0): FBIOPUTCMAP: Invalid argument". Full log - https://pastebin.com/UfgT1K8U I try to use fbdev driver: root@nanopiair:/etc/X11/xorg.conf.d# cat /etc/X11/xorg.conf.d/50-fbdev.conf Section "Device" Identifier "Allwinner A10/A13 FBDEV" Driver "fbdev" Option "fbdev" "/dev/fb0" # Option "SwapbuffersWait" "true" EndSection I get Xorg.log with errors "FBDEV(0): FBIOPUTCMAP: Invalid argument". Full log - https://pastebin.com/EqDCEGLf Why X server terminating after start? I have a second such board, it also has armbian, but on debian 10 and everything works fine without Xorg config.
-
Hi, I am having an issue with my system running a nanopi Air. After boot, my system won't detect my rtc (i2cdetect doesn't show it) nor my USB device. The problem must come from my SD card or is software related. Indeed, when I am booting from another SDcard, with aembian installed, everything is detected normally. Does anyone has a clue? Thank you, Tibibs
-
Does anyone know what sort of latency there is using mainline hw accelerated video encoding on Allwinner H3(H.264/265)? How about latency of mjpeg(if it is supported)? I'm trying to build a system with lowest possible latency.
