Search the Community
Showing results for tags 'nanopineo2'.
-
Armbian 6.6.16-sunxi64 (bookworm) on NanoPi NEO2 NanoHatOLED fails: - GPIO devices are missing; 2024-03-29 23:04:55 root@M-DNS:~# uname -a Linux M-DNS 6.6.16-current-sunxi64 #2 SMP Fri Feb 23 08:25:28 UTC 2024 aarch64 GNU/Linux Seems regression of earlier issue that had been solved: Would appreciate as GPIO will restored in kernel.
-
Today I did update my 3 NanoPi Neo2 via apt update/upgrade, but only one is accessable via ssh after the update. (without SSH/SSL-conect also no conection via SFTP/WinSCP because if the timeout) The one which is accessable has after the update Welcome to Armbian 23.02.2 Bullseye with bleeding edge Linux 6.7.12-edge-sunxi64 ( Machine model: FriendlyARM NanoPi NEO 2) The two other do show prompts for user/password but doesnt login via ssh - and after some time they time out and I can reenter user/password After connecting via TTL-serial I can also enter user/password and then the Neo2 shows me: _ _ ____ _ _ _ ____ | \ | | _ \(_) | \ | | ___ ___ |___ \ | \| | |_) | | | \| |/ _ \/ _ \ __) | | |\ | __/| | | |\ | __/ (_) | / __/ |_| \_|_| |_| |_| \_|\___|\___/ |_____| Welcome to Armbian 23.8.1 Bullseye with bleeding edge Linux 6.7.12-edge-sunxi64 No end-user support: community creations System load: 266% Up time: 2 min Memory usage: 22% of 982M IP: 192.168.6.24 CPU temp: 73°C Usage of /: 54% of 15G storage/: 56% of 458G storage temp: 41°C RX today: 4.2 GiB [ General system configuration (beta): armbian-config ] Last login: Tue Dec 27 14:13:30 +03 2022 from 192.168.6.17 on pts/0 After prssing Ctrl-C: ^C Armbian 23.8.1 bullseye ttyS0 npi-neo2-24 login: For non-existing users I do get a timeout at the serial-TTL-Port: npi-neo2-24 login: maxandmoritz Password: Login timed out after Armbian 23.8.1 bullseye ttyS0 npi-neo2-24 login: but nothing more - and this time the login doenst time out. But the armbian seems to boot up correctly, because the SAMBA-server on the Neo2 is available/useable. So the only way to change something in the system will be to make modifikations to the SDCard - but which change have I to do? Maybe its something between the Neo2 Revisions 1&2 (not/no Black Revision). Does anyone got a glue/idea for me? Thanks in advance Guido
-
Hello, I try build kernel for NanopiNeo board with user kernel patch, but I don't understand with path needed put my patch. In previous version armbian's builds I just put files to userpatches/kernel/sunxi-current how it described in docs. But now with current version Armbian build system it's not working. I put my custom linux-sunxi-current.config to userpatches folder, my patch to userpatches/kernel/sunxi-current and try build kernel with command: ./compile.sh BOARD=nanopineo BRANCH=current kernel I see that linux-sunxi-current.config found and applied but not patch isn't.
-
As per the Subject, the I2C bus 0 is enabled and detected, but I don't see an addresses being returned when I try the i2cdetect -y 0 command. I have a single PCF 8574A connected with address 0x38. and have double checked the wiring. The PCF8574A did respond on the I2C bus on another SBC. Thanks John
-
Hello, I try to enable audio linein, controls with alsamixer are the following. Is it possible to redirect audio input to output directly or with audio equalizer ? I actually have sound with a speaker test, but I can't listen to the audio line-inActually I have sound with speaker test, but I can't listen audio linein Best regards
-
Hi, I finally have time to get back to my little project. I've been trying to get a working display with tinydrm for an ILI9341 base lcd. My setup works on OpenWrt with the older fbtft driver, but now I'd like to go back and try Armbian (current release is Jammy) on it. My first try with devicetree overlay seems functional but not correct. The display just show garbled data (see attached). What could be the problem with it? This is my env. verbosity=1 bootlogo=false console=both overlay_prefix=sun50i-h5 overlays=usbhost1 usbhost2 spi-spidev param_spidev_spi_bus=0 rootdev=UUID=e0ed80c4-a252-4d96-ad61-78b7834d6b8d rootfstype=ext4 user_overlays=spilcd usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u and this is my overlay /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <&spi0>; __overlay__ { #address-cells = <1>; #size-cells = <0>; display: display@0 { compatible = "adafruit,yx240qv29", "ilitek,ili9341"; reg = <0>; rotation = <270>; reset-gpios = <&pio 0 6 0>; /* GPIOA 6 */ dc-gpios = <&pio 0 3 0>; /* GPIOA 3 */ }; }; }; };
-
Hello I'm using armbian on a Neo 2 board and I wanted to use a Quectel EM05 or EC25 LTE modem with it. Actually only need the serial port to send AT-commands. My question is, are Quectel modems natively supported by armbian (QMI? MBMI? ), or do I need to add the driver manually and rebuild the image??? Thank you (Yeah, it's a noob question ) Edit: Ok, I connected to modem to the board and realized that a wwan0 interface was created. That's fine, but I actually needed the serial port ttySx in order to sen AT-commands, but there is not one available... that's actually very strange.
-
Since volatile journald logging is done in-memory in /run/log/journal, and made persistent in /var/log.hdd/journal, the rsync of /var/log/journal in nand-sata-install no longer works because it is a symlink to /var/log.hdd/journal in the live system, and will create a circular symlink when booting from NAND. On the target image /var/log is the folder that is directory-mounted to /var/log.hdd during boot. I propose to exclude /var/log from the rsync, and rsync /var/log.hdd to /var/log on the target image. Another solution could be to exclude only /var/log/journal from the rsync, and create an empty /var/log/journal in the target image. Kind regards, Dennis
-
Hi, I owe a fritzbox 5530 which is configured for both IPv6 and IPv4. My armbian ( debian 11 ) SBC ( neo2 running kernel 5.19.1 ) shows: root@armbian:~# ip a |grep inet6 inet6 ::1/128 scope host inet6 2a02:a45f:b977:1:3383:1a4e:38e2:733f/128 scope global dynamic noprefixroute inet6 2a02:a45f:b977:1:a05d:7fc7:a5d0:d647/64 scope global dynamic noprefixroute inet6 fe80::3383:1a4e:38e2:733f/64 scope link noprefixroute However I am unable to resolve the IPv6 address while for another debian box it is working fine: root@armbian:~# ping debian.fritz.box PING debian.fritz.box(debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0)) 56 data bytes 64 bytes from debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0): icmp_seq=1 ttl=255 time=4.12 ms 64 bytes from debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0): icmp_seq=2 ttl=255 time=3.34 ms ^C root@armbian:~# ping armbian.fritz.box PING armbian.fritz.box (192.168.10.6) 56(84) bytes of data. 64 bytes from armbian.fritz.box (192.168.10.6): icmp_seq=1 ttl=64 time=0.999 ms 64 bytes from armbian.fritz.box (192.168.10.6): icmp_seq=2 ttl=64 time=2.51 ms ^C Any thoughts please?
-
Dear all, I occasionally have a full /var/log at startup on various boards, probably because the logs are not rotated /vaccuumd at boot (we had a thread about this in the old opi1 forum). The rotating /vaccuum is currently done every 15 minutes, so I figured why not do it directly at boot as well? For this purpose I updated /etc/cron.d/armbian-truncate-logs with an extra @reboot line: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */15 * * * * root /usr/lib/armbian/armbian-truncate-logs @reboot root /usr/lib/armbian/armbian-truncate-logs I rebooted several times, and didn't get a full /var/log anymore. All subsequent problems like failing networking when filesystem full also vanished;-) Kind regards, Dennis
- 14 replies
-
1
-
- Orange Pi Zero
- Nanopi Neo 3
-
(and 2 more)
Tagged with:
-
Sorry for my stupid question. If I connect by TTL to USB adapter, after setting up login/password, terminal is freezing. Board is Nanopi NOE2. I think this is due to the fact that my adapter is warm or not of poor quality. While I order a new one, is there a way to enable ssh access over the lan network?
-
Hi all. I'm new, so don't hit too hard. I'm interested in how the NAS Dock for NanoPi Neo2 is defined in the system. I want to install OpenWRT, because I need a NanoPi based router. Armbian seems to me too complicated for such tasks. If you put OpenWRT on NEO2, then NAS Dock is not detected in the system. At that time Armbian determines, I can easily open the HDD or connect devices to the dock's USB port. Please tell me. Which module or driver is responsible for the dock to be defined in the system? The Openwrt forum has not yet been able to help me, so I'm writing here. Help as you can.