wollik

@cOrnelius YES I know how to maintain the current system manualy, but with the next release I' l have to do it again. @Igor, your PR modification looks like the right solution adding the missing group T H A N K S! P L E A S E can you also point me where I will find the right spot where I can define the right owner for the some specified directories like the: /sys/class/gpio ? Is there a list for mapping the right owner to a directory? that can be modified? Regards Wolfgang

Hi Members, I'm setting and reading the GPIO PINs for different BPI's frequently only by bash by maintaining the /sys/class/gpio/xxx values. The only problem is that all these files belong to root :root and I have to use the sudo command in my scripts. I've read about putting a non root user to the gpio group will fix that. But on Armbian there is no "gpio" group ;( That seems the reason why the directory /sys/class/gpio is not prepared as root:gpio Please has someone an idea when this will be implemented? Regards wollik

@eselarm, YES, just edit the /boot/armbianEnv.txt file. See my example for the PIN 7 of an BPI M1 below. @Ryzer, your provided link has no mapping of the GPIO Pins to there PIN Names only there PIN Funktions are listed. But these PIN Names must be specified in as a parameter to use the 1w Protokoll. LeMarker Docu: PIN: Function:--> Needed PIN Name as parameter in /boot/armbianEnv.txt: 7 GPCLK --> PI03 11 IO-0 --> PI19 13 IO-2 --> PI18 15 IO-3 --> PI17 Hi All, I got my DS1820 (temp sensor) now running. My plan was to use the Pin 7 of CON3 (26 Pin connector) and tried with PA6 and others, but always got the dmesg errors "pin xx already requested by 1c50000.ethernet; cannot claim for onewire@0" That was why I asked for a PIN mapping of the CON3 on the BPI M1. After long searching I found a list in the freebsd.org forum with the right pins! Now with these settings in the /boot/armbianEnv.txt I got my DS1820 connected to the physical pin 7 to function!!! overlay_prefix=sun7i-a20 overlays=w1-gpio param_w1_pin=PI03 I'll try to get the PIN Names of all my other BPIxx models and will post it here. Many thanks for your support. wollik

Hi all, I've updated my BPI M1 to Armbian 24.11.1 bookworm and still get the same problems to use the PA6 pin for 1-Wire. dmesg | grep -i "onewire" [ 6.685838] sun4i-pinctrl 1c20800.pinctrl: pin PA6 already requested by 1c50000.ethernet; cannot claim for onewire@0 [ 6.685884] sun4i-pinctrl 1c20800.pinctrl: pin-6 (onewire@0) status -22 [ 6.686020] w1-gpio onewire@0: Error applying setting, reverse things back I've activated the w1 via armbian-config under: System -> SY017 - Manage device tree overlays -> first only sun7i then only sun4i and also both sun7i plus sun4i but always got the same error after the reboots. I'm wondering why dmesg points to sun4i even when I have only selected/activated sun7i in the device tree overlays. Any idea? Regards wollik

Hi Forum Members, I need have to activate a 1-wire thermal sensor DS1820 on al old BPI M1. I've had these type of sensors allready runing on a BPI M2Zero under Buster (Armbian Kernel: 5.10.60-sunxi) wih these settings in /boot/armbianEnv.txt: overlays=w1-gpio param_w1_pin=PA6 dmesg | grep -E 'w1|wire' [ 6.806929] Driver for 1-wire Dallas network protocol. [ 6.847601] gpio-6 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 6.875871] w1_master_driver w1_bus_master1: Attaching one wire slave 28.0121121d29c5 crc 9a [ 7.020059] w1_master_driver w1_bus_master1: Attaching one wire slave 28.0121115aaa65 crc c1 [ 7.115896] w1_master_driver w1_bus_master1: Attaching one wire slave 28.012111456c5b crc 23 [ 7.212969] w1_master_driver w1_bus_master1: Attaching one wire slave 28.0121121afabf crc 5b [ 7.299832] w1_master_driver w1_bus_master1: Attaching one wire slave 28.01211165dfbf crc a7 [ 8.527889] Bluetooth: HCI UART protocol Three-wire (H5) registered and is also shown via: sudo cat /sys/kernel/debug/gpio as: gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-6 ( |onewire@0 ) out hi gpio-7 ( |sysfs ) out lo gpio-8 ( |sysfs ) out lo gpio-9 ( |sysfs ) out lo gpio-10 ( |sysfs ) out lo gpio-21 ( |sysfs ) out lo gpio-166 ( |cd ) in hi gpio-203 ( |host-wakeup ) in lo IRQ gpio-204 ( |shutdown ) out hi gpio-205 ( |device-wakeup ) out lo gpiochip1: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl: gpio-353 ( |vdd-cpux ) out hi gpio-355 ( |power ) in hi IRQ ACTIVE LOW gpio-356 ( |sysfs ) out lo gpio-358 ( |usb0_id_det ) in hi IRQ gpio-359 ( |reset ) out hi ACTIVE LOW gpio-362 ( |bananapi-m2-zero:red) out lo Now on the BPI M1 also under Buster (Armbian Kernel: 5.10.16-sunxi) it is not possible to use this pin PA6. I got these errors: dmesg | grep -E 'w1|wire' [ 6.641667] Driver for 1-wire Dallas network protocol. [ 6.666672] sun4i-pinctrl 1c20800.pinctrl: pin PA6 already requested by 1c50000.ethernet; cannot claim for onewire@0 [ 6.666696] sun4i-pinctrl 1c20800.pinctrl: pin-6 (onewire@0) status -22 [ 6.666717] w1-gpio onewire@0: Error applying setting, reverse things back [ 6.666750] w1-gpio: probe of onewire@0 failed with error -22 I've tried also other PA's but allways the same problems. I know that the Buster Kernels are no longer supported, but have the general question about the GPIO Pin naming/mapping to the physical Pins for the 26 and 40 Pin Headers used by Armbian for what SOC's please. Thands in advance wollik

Hi All, I''m using a BPI M2 Zero, where a 100 MBit ethernet Interface is implemented on the board. Since I'm using DHCP for this interface, I found that the MAC Address of this eth0 interface changes on every boot. The MAC Address of the wlan0 interface is permanent and don't changes during boots. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Di 30. Jun xx:xx:xx CEST 2020 Debian GNU/Linux 10 (buster) 5.4.45-sunxi ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 17:42:11 up 25 min, 2 users, load average: 0,00, 0,00, 0,05 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 8a:aa:ea:69:67:50 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) 17:46:04 up 0 min, 2 users, load average: 2,48, 0,70, 0,24 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 5e:af:c0:93:75:72 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) 17:47:07 up 0 min, 2 users, load average: 1,92, 0,44, 0,14 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 56:e7:62:af:35:55 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) 17:48:23 up 0 min, 2 users, load average: 1,69, 0,39, 0,13 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 96:57:7c:ed:85:e0 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) Is there a way to set the MAC address of the eth0 interface to a fix value ? Regards WolliK