cvxx
-
Posts
48 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by cvxx
-
-
Hi,
on latest Armbian 23.11.1 Bookworm with PINE64 board I noticed those warnings in journal:
Feb 12 10:00:45 pine64 systemd[1]: /lib/systemd/system/systemd-journal-upload.service:33: Unknown key name 'RestartSteps' in s> Feb 12 10:00:45 pine64 systemd[1]: /lib/systemd/system/systemd-journal-upload.service:34: Unknown key name 'RestartMaxDelaySec>I suspect the `systemd-journal-upload.service` is not in tact with systemd daemon version installed.
-
Sorry for bumping, but I have just tried Armbian_23.02.2_Pine64_jammy_current_5.15.93.img and there is rpcbind started on boot and listening on all interfaces:
root@pine64:~# netstat -atnp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 694/rpcbind tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 695/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1426/sshd: /usr/sbi tcp6 0 0 :::111 :::* LISTEN 694/rpcbind tcp6 0 0 :::22 :::* LISTEN 1426/sshd: /usr/sbiI think this is a security risk
-
added:
console=bothnow I have a shell!
Thanks!
-
This is armbianEnv.txt:
verbosity=1 bootlogo=false rootdev=UUID=30b36fce-65d1-44c4-bcec-3677c9fe01bd rootfstype=ext4 -
No, I meant, on HDMI everything is ok, it boots and I can login. But the serial stays quiet
-
Hi,
when booting Armbian Sid minimal rolling 6.1.11, there is no serial console login.
Console output:
Found U-Boot script /boot/boot.scr 1993 bytes read in 146 ms (12.7 KiB/s) ## Executing script at 12000000 93 bytes read in 94 ms (0 Bytes/s) 38318 bytes read in 2603 ms (13.7 KiB/s) 33621022 bytes read in 3482 ms (9.2 MiB/s) 11215360 bytes read in 1257 ms (8.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 33620958 Bytes = 32.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c5ad Starting kernel ...Is there a way to enable console login to use the device headlessly?
Thanks
-
I haven't yet tried to build my own image, but I tested few other dongles. Surprisingly, `0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n` also did not work because of missing firmware `htc_9271-1.4.0.fw`. So, I think that build has issues with not only missing RTL8188EUS.
-
Flashed the latest Jammy 5.15.48 image and the device went offline
After connecting to HDMI I found out that RTL8188EUS is no longer available. Previous Focal image worked fine in headless mode with a `0bda:8179` dongle.
Anyone knows why the driver has been removed?
Thanks
-
I had to downgrade to last known working Armbian 20.05.1 Bionic version with this 8189fs module version:
$ modinfo 8189fs filename: /lib/modules/5.4.43-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko version: v4.3.24.8_22657.20170607 author: Realtek Semiconductor Corp. description: Realtek Wireless Lan Driver license: GPL srcversion: 782ED5E387B69B8750A9E7F alias: sdio:c*v024CdF179* depends: cfg80211 intree: Y name: 8189fs vermagic: 5.4.43-sunxi SMP mod_unload ARMv7 thumb2 p2v8Now all works fine like previously
-
Armbianmonitor:
Hi,
I have been running Armbian on OrangePi Lite for more than a year just fine. Then I decided to upgrade and flashed the latest version. Now with the latest version the device looses wifi every few days no matter which wifi device I use.
In order to investigate I have plugged additional USB wifi. Some time both wifi work. Then built-in may disconnect and stop working, but USB keeps working. Or vice versa, USB stops working, but the built in keeps working.
I have been able to send syslog to an external machine and here what it showed
Connection works fine:
QuoteApr 21 16:22:38 wpa_supplicant[631]: wlx0013ef665843: SME: Trying to authenticate with 77:e3:27:b8:37:5f (SSID='XXXXXXX' freq=2412 MHz)
Apr 21 16:22:38 kernel: wlx0013ef665843: authenticate with 77:e3:27:b8:37:5f
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.5169] device (wlx0013ef665843): supplicant interface state: ready -> authenticating
Apr 21 16:22:38 kernel: wlx0013ef665843: send auth to 77:e3:27:b8:37:5f (try 1/3)
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.5172] device (p2p-dev-wlx0013ef665843): supplicant management interface state: ready -> authenticating
Apr 21 16:22:38 wpa_supplicant[631]: wlx0013ef665843: Trying to associate with 77:e3:27:b8:37:5f (SSID='XXXXXXX' freq=2412 MHz)
Apr 21 16:22:38 kernel: wlx0013ef665843: send auth to 77:e3:27:b8:37:5f (try 2/3)
Apr 21 16:22:38 kernel: wlx0013ef665843: authenticated
Apr 21 16:22:38 kernel: wlx0013ef665843: associate with 77:e3:27:b8:37:5f (try 1/3)
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.6228] device (wlx0013ef665843): supplicant interface state: authenticating -> associating
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.6230] device (p2p-dev-wlx0013ef665843): supplicant management interface state: authenticating -> associating
Apr 21 16:22:38 kernel: wlx0013ef665843: RX AssocResp from 77:e3:27:b8:37:5f (capab=0x431 status=0 aid=2)
Apr 21 16:22:38 wpa_supplicant[631]: wlx0013ef665843: Associated with 77:e3:27:b8:37:5f
Apr 21 16:22:38 kernel: wlx0013ef665843: associated
Apr 21 16:22:38 wpa_supplicant[631]: wlx0013ef665843: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 21 16:22:38 wpa_supplicant[631]: wlx0013ef665843: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=LT
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.6953] device (wlx0013ef665843): supplicant interface state: associating -> 4-way handshake
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.6955] device (p2p-dev-wlx0013ef665843): supplicant management interface state: associating -> 4-way handshake
Apr 21 16:22:38 wpa_supplicant[631]: wlx0013ef665843: WPA: Key negotiation completed with 77:e3:27:b8:37:5f [PTK=CCMP GTK=CCMP]
Apr 21 16:22:38 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlx0013ef665843: link becomes ready
Apr 21 16:22:38 wpa_supplicant[631]: wlx0013ef665843: CTRL-EVENT-CONNECTED - Connection to 77:e3:27:b8:37:5f completed [id=0 id_str=]
Apr 21 16:22:38 wpa_supplicant[631]: bgscan simple: Failed to enable signal strength monitoring
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.9426] device (wlx0013ef665843): supplicant interface state: 4-way handshake -> completed
Apr 21 16:22:38 NetworkManager[592]: <info> [1619011358.9429] device (wlx0013ef665843): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "XXXXXXX"The next day one of the connections stops working and complains that the WPA key may be wrong:
QuoteApr 22 12:26:34 wpa_supplicant[613]: wlx0013ef665843: SME: Trying to authenticate with 77:e3:27:b8:37:5f (SSID='XXXXXXX' freq=2412 MHz)
Apr 22 12:26:34 kernel: wlx0013ef665843: authenticate with 77:e3:27:b8:37:5f
Apr 22 12:26:34 kernel: wlx0013ef665843: send auth to 77:e3:27:b8:37:5f (try 1/3)
Apr 22 12:26:34 NetworkManager[591]: <info> [1619083594.0185] device (wlx0013ef665843): supplicant interface state: ready -> authenticating
Apr 22 12:26:34 NetworkManager[591]: <info> [1619083594.0187] device (p2p-dev-wlx0013ef665843): supplicant management interface state: ready -> authenticating
Apr 22 12:26:34 kernel: wlx0013ef665843: send auth to 77:e3:27:b8:37:5f (try 2/3)
Apr 22 12:26:34 kernel: wlx0013ef665843: send auth to 77:e3:27:b8:37:5f (try 3/3)
Apr 22 12:26:34 wpa_supplicant[613]: wlx0013ef665843: Trying to associate with 77:e3:27:b8:37:5f (SSID='XXXXXXX' freq=2412 MHz)
Apr 22 12:26:34 kernel: wlx0013ef665843: authenticated
Apr 22 12:26:34 kernel: wlx0013ef665843: associate with 77:e3:27:b8:37:5f (try 1/3)
Apr 22 12:26:34 NetworkManager[591]: <info> [1619083594.2418] device (wlx0013ef665843): supplicant interface state: authenticating -> associating
Apr 22 12:26:34 NetworkManager[591]: <info> [1619083594.2419] device (p2p-dev-wlx0013ef665843): supplicant management interface state: authenticating -> associating
Apr 22 12:26:34 kernel: wlx0013ef665843: associate with 77:e3:27:b8:37:5f (try 2/3)
Apr 22 12:26:34 kernel: wlx0013ef665843: associate with 77:e3:27:b8:37:5f (try 3/3)
Apr 22 12:26:34 wpa_supplicant[613]: wlx0013ef665843: Associated with 77:e3:27:b8:37:5f
Apr 22 12:26:34 kernel: wlx0013ef665843: RX AssocResp from 77:e3:27:b8:37:5f (capab=0x431 status=0 aid=2)
Apr 22 12:26:34 kernel: wlx0013ef665843: associated
Apr 22 12:26:34 wpa_supplicant[613]: wlx0013ef665843: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 22 12:26:34 NetworkManager[591]: <info> [1619083594.5312] device (wlx0013ef665843): supplicant interface state: associating -> 4-way handshake
Apr 22 12:26:34 NetworkManager[591]: <info> [1619083594.5313] device (p2p-dev-wlx0013ef665843): supplicant management interface state: associating -> 4-way handshake
Apr 22 12:26:34 wpa_supplicant[613]: wlx0013ef665843: WPA: Key negotiation completed with 77:e3:27:b8:37:5f [PTK=CCMP GTK=CCMP]
Apr 22 12:26:34 wpa_supplicant[613]: wlx0013ef665843: CTRL-EVENT-CONNECTED - Connection to 77:e3:27:b8:37:5f completed [id=0 id_str=]
Apr 22 12:26:34 wpa_supplicant[613]: bgscan simple: Failed to enable signal strength monitoring
Apr 22 12:26:34 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlx0013ef665843: link becomes ready
Apr 22 12:26:38 kernel: wlx0013ef665843: deauthenticated from 77:e3:27:b8:37:5f (Reason: 2=PREV_AUTH_NOT_VALID)
Apr 22 12:26:38 wpa_supplicant[613]: wlx0013ef665843: CTRL-EVENT-DISCONNECTED bssid=77:e3:27:b8:37:5f reason=2
Apr 22 12:26:38 wpa_supplicant[613]: wlx0013ef665843: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Apr 22 12:26:38 NetworkManager[591]: <warn> [1619083598.6352] sup-iface[0xbccac0,wlx0013ef665843]: connection disconnected (reason 2)
Apr 22 12:26:38 wpa_supplicant[613]: wlx0013ef665843: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="XXXXXXX" auth_failures=1 duration=10 reason=WRONG_KEYObviously, nothing has changed, the hotspot is still the same and WPA key has not been changed. Both wifi connections are using the same key, and one works fine.
Rebooting resolves the issue, but after few days it is back again.
Anyone have seen this behavior?
Before downgrading to a version prior 2020 I'd like to check as much as possible if this is some bug
Thanks
-
UPDATE
I have set up a fresh sd card to investigate and collect logs, but this time `ifupdown` worked
Probably it was some typo I made in /etc/network/interfaces during setupAlso, a note for future myself when I visit this thread again, there is a way to create the connection through `armbian_first_run.txt`. I tested and it worked. So, probably, better to switch to this way to have less conflicts between Network Manager and ifupdown
-
Armbian_21.02.3_Orangepilite_focal_current_5.10.21
-
The `ifupdown` method to connect a headless device no longer works with the latest Armbian 21.02.3. For some reason the interface remains down and requires manual `sudo ifup -v wlan0`
`rc.local` does not start as there is root password change prompt blocking it
Anyone knows what do I need to change to start wlan0 on boot? Or any other way to configure network on a device without HDMI?
Thanks
-
Hi,
I have connected Orange Pi Lite over serial UART, but looks like the default settings are to not output the boot log to serial. You can only see U-Boot messages, then "Uncompressing Linux kernel" and after some time the login prompt comes.
What exactly do I need to change/configure to get the classic kernel boot log to serial console?
Quote$ cat /proc/cmdline
root=UUID=b5b787c1-ea46-43ab-9140-7e7440f6d48a rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=71a680ab-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1Quote$ uname -a
Linux orangepilite 5.4.45-sunxi #20.05.4 SMP Sun Jun 14 21:46:20 CEST 2020 armv7l armv7l armv7l GNU/LinuxThanks
-
There was a critical vulnerability found in Realtek wireless drivers:
The vulnerability has been assigned CVE-2019-17666 and a patch proposed: https://lkml.org/lkml/2019/10/16/1226
I would like to get some statement if Armbian users are affected and if yes when is the patch going to be released
Thanks
-
I am successfully using this cron script every 1 minute to detect wifi failure and reload the module:
#!/bin/bash status=`/sbin/ifconfig wlan0 | grep "inet 192"` if [ ! -z "$status" ]; then exit 0; fi echo "Detected wifi failure" dmesg | grep __cfg80211_connect_result | mail -s "Wifi failure" root@localhost sudo rmmod 8189fs sudo modprobe 8189fs sleep 3 nmcli connection up id mynetworknameHTH
-
Note that the script reports it's 26 C, but kernel reports different:
Quote$ cat /sys/class/thermal/thermal_zone0/temp
56144
-
Hi,
as it is quite hot now in Europe, one of my boards is experiencing overheat and shuts down automatically:
Jun 25 16:52:27 localhost kernel: [74505.568246] thermal thermal_zone0: critical temperature reached (90 C), shutting down
Who is initiating this shutdown?
Is it possible to:
1. Change the temperature value that triggers the shutdown
2. Hook a script instead of direct shutdown so I can handle the overheat
Thanks
-
Thanks for the idea
I found this solution to be more compatible: /etc/NetworkManager/NetworkManager.conf
Quote--- /etc/NetworkManager/NetworkManager.conf.bak 2019-02-10 04:57:51.988000067 +0000
+++ /etc/NetworkManager/NetworkManager.conf 2019-04-16 11:14:51.616145076 +0000
@@ -4,7 +4,7 @@
plugins=ifupdown,keyfile[ifupdown]
-managed=true
+managed=false[device]
wifi.scan-rand-mac-address=noSource: https://wiki.debian.org/NetworkManager#Wired_Networks_are_Unmanaged
-
Hi,
I have few boards that were once connected to wifi manually, but now are headless. I would like now to upgrade Armbian and put wifi connection during sd card flash.
Tried the classic way: /etc/network/interfaces
Quoteauto wlan0
iface wlan0 inet dhcp
wpa-ssid wifi
wpa-psk 12345678When the board boots it connects to the wifi, I see few pings and then it goes offline
After taking one of the boards for troubleshooting using serial console I found that NeworkManager starts right after the network is up and screws everything:
QuoteFeb 10 04:59:33 orangepilite wpa_supplicant[526]: wlan0: Trying to associate with f8:d1:11:11:ee:c4 (SSID='wifi' freq=2412 MHz)
Feb 10 04:59:33 orangepilite wpa_supplicant[526]: wlan0: Associated with f8:d1:11:11:ee:c4
Feb 10 04:59:33 orangepilite wpa_supplicant[526]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb 10 04:59:33 orangepilite wpa_supplicant[526]: wlan0: WPA: Key negotiation completed with f8:d1:11:11:ee:c4 [PTK=CCMP GTK=TKIP]
Feb 10 04:59:33 orangepilite wpa_supplicant[526]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:d1:11:11:ee:c4 completed [id=0 id_str=]...snip...
Feb 10 04:59:36 orangepilite NetworkManager[669]: <info> [1549774776.5293] supplicant: wpa_supplicant running
Feb 10 04:59:36 orangepilite NetworkManager[669]: <info> [1549774776.5297] device (wlan0): supplicant interface state: init -> starting
Feb 10 04:59:36 orangepilite wpa_supplicant[665]: ctrl_iface exists and seems to be in use - cannot override it
Feb 10 04:59:36 orangepilite wpa_supplicant[665]: Delete '/run/wpa_supplicant/wlan0' manually if it is not used anymore
Feb 10 04:59:36 orangepilite wpa_supplicant[665]: Failed to initialize control interface '/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.Feb 10 04:59:36 orangepilite wpa_supplicant[665]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Feb 10 04:59:36 orangepilite NetworkManager[669]: <error> [1549774776.7041] sup-iface[0x1ff0890,wlan0]: error adding interface: wpa_supplicant couldn't grab this interface.
Feb 10 04:59:36 orangepilite NetworkManager[669]: <info> [1549774776.7052] device (wlan0): supplicant interface state: starting -> downExecuting sudo ifdown wlan0 && sudo ifup -v wlan0 restores the connection
My question is: what is the correct way to put wifi configuration on the sd card of a headless Armbian installation?
Thanks
-
One more update
I found that reloading the kernel module helps to restore wireless interface:
Quotesudo rmmod 8189fs
sudo modprobe 8189fs -
Yes, stock antenna
-
Hi,
I have two OrangePi Lite running side by side. After working fine for about 8 months both started to experience same issue with wireless:
Quote[ 20.283685] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 52.018851] ------------[ cut here ]------------
[ 52.019030] WARNING: CPU: 2 PID: 5 at net/wireless/sme.c:752 __cfg80211_connect_result+0x256/0x2c8 [cfg80211]
[ 52.019033] Modules linked in: lz4 lz4_compress zram uvcvideo ir_lirc_codec snd_usb_audio snd_hwdep snd_usbmidi_lib videobuf2_vmalloc snd_rawmidi videobuf2_memops snd_seq_device lirc_dev videobuf2_v4l2 videobuf2_core evdev sunxi_cir sun8i_codec_analog sun4i_gpadc_iio snd_soc_hdmi_codec sun4i_i2s snd_soc_simple_card snd_soc_simple_card_utils snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore w1_therm w1_gpio wire uio_pdrv_genirq uio sch_fq_codel g_serial libcomposite 8189fs cfg80211 rfkill ip_tables x_tables dw_hdmi_cec dw_hdmi_i2s_audio sun8i_dw_hdmi dw_hdmi cec sun4i_tcon sun8i_mixer sun4i_drm
[ 52.019146] CPU: 2 PID: 5 Comm: kworker/u8:0 Not tainted 4.14.65-sunxi #12
[ 52.019149] Hardware name: Allwinner sun8i Family
[ 52.019210] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
[ 52.019237] [<c010dacd>] (unwind_backtrace) from [<c010a0b5>] (show_stack+0x11/0x14)
[ 52.019251] [<c010a0b5>] (show_stack) from [<c086b7fd>] (dump_stack+0x69/0x78)
[ 52.019264] [<c086b7fd>] (dump_stack) from [<c011a1cf>] (__warn+0xaf/0xc0)
[ 52.019273] [<c011a1cf>] (__warn) from [<c011a291>] (warn_slowpath_null+0x19/0x1c)
[ 52.019332] [<c011a291>] (warn_slowpath_null) from [<bf89256b>] (__cfg80211_connect_result+0x256/0x2c8 [cfg80211])
[ 52.019442] [<bf89256b>] (__cfg80211_connect_result [cfg80211]) from [<bf8744fd>] (cfg80211_process_wdev_events+0xb4/0xe0 [cfg80211])
[ 52.019544] [<bf8744fd>] (cfg80211_process_wdev_events [cfg80211]) from [<bf87454f>] (cfg80211_process_rdev_events+0x26/0x50 [cfg80211])
[ 52.019645] [<bf87454f>] (cfg80211_process_rdev_events [cfg80211]) from [<bf8701d3>] (cfg80211_event_work+0x16/0x1c [cfg80211])
[ 52.019702] [<bf8701d3>] (cfg80211_event_work [cfg80211]) from [<c012d4d1>] (process_one_work+0x155/0x37c)
[ 52.019711] [<c012d4d1>] (process_one_work) from [<c012e073>] (worker_thread+0xff/0x408)
[ 52.019721] [<c012e073>] (worker_thread) from [<c0131b3d>] (kthread+0xfd/0x104)
[ 52.019733] [<c0131b3d>] (kthread) from [<c01066f9>] (ret_from_fork+0x11/0x38)
[ 52.019778] ---[ end trace b84df9c56982a79d ]---
[ 52.242651] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not readyThe board works randomly for few hours or few days and then looses wireless connection. When this happens reboot does not help as then issue occurs immediately after the boot. Unplugging and replugging power source resolves that for a while and then happens again
I suspect it may not be related to a hardware issue or wireless hotspot, as I have at least 3 other clients that continue to work fine. Searching for it on the internet brought this issue with Raspberry Pi: https://github.com/raspberrypi/linux/issues/1988. Raspberry uses different wireless chipset either. All that makes me think this may be an issue in the kernel itself
Any ideas or thoughts?
Workaround also appreciated
Thanks
-
I followed instruction of adding overlay at http://linux-sunxi.org/1-Wire
QuoteLinux kernel 4.14
You don't have to edit the fex-file, but the /boot/armbianEnv.txt and add the lines:
overlays=w1-gpio
param_w1_pin=PB10 # desired pin
param_w1_pin_int_pullup=1 # internal pullup-resistor: 1=on, 0=off
This resulted in an error during boot and non functional 1-wire:
Quote## Executing script at 44000000
tmp_bank=A # desired pin
tmp_pin=10 # desired pin
Sorry, I could not convert "A # desired pin 10 # desired pin 0>"Removing "#" comments from armbianEnv.txt resolved the issue
Can you please confirm if comments are allowed in armbianEnv.txt?
Thanks
How to match GPIO number for export?
in Amlogic meson
Posted · Edited by cvxx
Hi,
Armbian_21.02.3_Odroidc1_focal_current_5.10.21
how do I find out which number do I need to provide to gpio export command?
Let's say I have physical pin 16, which is labeled by the manufacturer as `GPIOX.5` or `102`.
But that doesn't work with Armbian:
echo 102 > /sys/class/gpio/export[ 1602.030617] export_store: invalid GPIO 102How do I know the value to provide for /sys/class/gpio/export?
# cat /sys/kernel/debug/gpio gpiochip1: GPIOs 413-428, parent: platform/c8100084.pinctrl, aobus-banks: gpio-416 ( |TF_IO ) out lo gpio-417 ( |usb-hub-reset ) out hi gpio-426 ( |c1:blue:alive ) out hi ACTIVE LOW gpiochip0: GPIOs 429-511, parent: platform/c1109880.pinctrl, cbus-banks: gpio-456 ( |regulator-tflash_vdd) out lo gpio-470 ( |PHY reset ) out hi ACTIVE LOW gpio-482 ( |cd ) in hi ACTIVE LOW gpio-492 ( |reset ) out hi ACTIVE LOWThanks