All Activity

I have checked what hapen when on Ornage Pi Zero v1 with kernel 6.1.63 in armbianEnv.txt use pa14 instead PA14 in log I see [ 9.358693] Driver for 1-wire Dallas network protocol. [ 9.366246] w1-gpio onewire@0: there is not valid maps for state default [ 9.368019] gpio-110 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file and w1-gpio not working and no files in /sys/bus/w1/devices/ but we see marked in red the same information that I have on OZPI v3 when I use pc10 instead of PC10 but on OZPI v3 DS18B20 works and on OZPI v1 it doesn't work when I use the lower case name gpio This looks like some kind of bug in kernel 6.6.30 on OZPI v3

hello luis , try this :https://drive.google.com/drive/folders/1ls4jTIl00CJ3UFQipGdOYmrN0XBnfJlS?usp=sharing

hi wulfy23, the problem is that you cannot use the console because the operating system no longer starts. If I extract the sd card and read it from the computer though, I can see all the OS files.

moved

moved

dts overlay aren't 'perfect' https://elinux.org/Device_Tree_Source_Undocumented#:~:text=Node can be deleted with,%2Fdelete-property%2F directive.&text=If a delete is specified,with the overlay source file. If a delete is specified in an overlay source file, the delete only impacts the files compiled in association with the overlay source file. The delete does not result in an opcode in the resulting .dtb, thus applying the overlay will not delete the node or property in the base tree. and it may take using those 'hacks' described at that page to attempt a 'fix' hence, you may like to just note that those messages are 'benign' and w1-gpio works normally.

Wifi works flawlessly with recent image. Includes Link Quality and Signal Level

@wanasta orange pi zero 3 (and zero 2w) has on board wifi, have you tried them 1st? usb wifi dongles normally if the drivers are built into the kernel, plug them in and check dmesg if they are detected

Attempting Armbian install onto an S905. Hardware specs at https://specdevice.com/showspec.php?id=6653-4ac9-1101-570d0033c587 Kernel begins to boot but gets errors and never completes dropping into initramfs shell. Was able to capture the dtb blob from the Android kernel and decompiled it. Enough differences to the dtb files in the Armbian distribution that I cannot figure out how to create a dtb file that will work. Have looked for other files on the internet but haven't come across something similar yet. Booting gets stuck in a loop of: meson-gx-mmc d0072000.mmc: no support for card's volts mmc0: error -22 whilst initialising SDIO card. mmc0: Card stuck being busy! __mmc_poll_for_busy Any feedback or guidance appreciated.

Description systemctl reload-or-restart ssh prevents botching job if sshd is started by socket How Has This Been Tested? Quite harmless change which broadens systemctl tolerance towards services, no negative impacts expected Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description systemd-resolved is installed and enabled by default - unfortunately a static /etc/resolv.conf nameserver 1.0.0.1 set up during debootstrap phase is preventing systemd-resolved to do its job Removing the file after chroot has been finalized in post-tweaks.sh enables systemd-resolved to symlink /etc/resolv.conf to /run/systemd/resolved/stub-resolv.conf on first boot How Has This Been Tested? [x] Rebuilt an booted an Orangepi5-plus debian trixie image from trunk Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

I have a tp link wn722n wifi adapter on the rtl8188eus chipset and I need to build a driver for the monitoring meter, but I don’t have the kernel headers, how and where can I download and install them?

It works, thanks @ag123, good work ! For some reason the Armbian Image is far slower than the Orange Pi Debian image in UI mode. I am guessing its maybe because the Armbian Image comes only with Gnome which is probably heavier UI framework to run.

Which SoCs and on which branch can have extensions enabled? 4l2loopback-dkms mesa-oibaf here: https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml#L40-L95 Mapping config: https://github.com/armbian/os/blob/main/userpatches/targets-extensions.map

Yes, that's right, I can ignore it when I have a working w1-gpio on OZPI v3, but it would be nice to see how to fix it so that it works correctly. But what's strange to me is that I have to use the gpio name in lower case and not in upper case as it was always described in the w1-gpio examples. I tried to use the name with gpiod, i.e. "gpio74", instead of names like PC10, but it didn't work, so it occurred to me to try writing the name in lower case "pc10" instead of capital letters as usual, and I found that it worked, but I think it's not normal since capital letters have been used so far, I will check on OZP v1 whether it will work if I change to lowercase letters Thank you for exchanging ideas and tips on solving the problem

Yes "no maps for state" is connected with but in all examples .dts is used : pinctrl-names = "default";

rather pinctrl could be related to pinctrl or maybe gpiod. I'm not too sure if that message means that w1-gpio is using that pin so pinctrl cannot use it. if that is the case, I think it is ok if pinctrl don't use it for gpio. that message is likely safe to ignore as long as your w1-gpio works. to 'fix' that it may take editing other dts to exclude that pin from pinctrl which could be a hassle.

But I am not use gpio PC10 by another application etc, I define PC10 only for w1-gpio in armbianEnv.tx but when I use PC10 instead pc10 w1-gpio is not working and I can not read data DS18B20. When I use pc10 all working and I read atat from DS18B20 so info in log: pin PC10 already requested by onewire@0; cannot claim for 300b000.pinctrl:74 give me that w1-gpio is not working

it may help to look in codes https://github.com/torvalds/linux/blob/master/drivers/w1/masters/w1-gpio.c https://github.com/torvalds/linux/tree/master/drivers/w1 [ 4.997793] sun50i-h616-pinctrl 300b000.pinctrl: pin PC10 already requested by onewire@0; cannot claim for 300b000.pinctrl:74 seem to suggest that pinctrl tries to map that pin but onewire@0 is using it, so i guess this is ok as long as you are not using that as normal gpio pin. that "no maps for state" is found here https://github.com/torvalds/linux/blob/cf87f46fd34d6c19283d9625a7822f20d90b64a4/drivers/pinctrl/devicetree.c#L175 ret = ops->dt_node_to_map(pctldev, np_config, &map, &num_maps); if (ret < 0) return ret; else if (num_maps == 0) { /* * If we have no valid maps (maybe caused by empty pinctrl node * or typing error) ther is no need remember this, so just * return. */ dev_info(p->dev, "there is not valid maps for state %s\n", statename); return 0; } my guess is it may be related to pinctrl-names = "default"; some related stuff https://www.kernel.org/doc/Documentation/devicetree/bindings/w1/ https://www.kernel.org/doc/Documentation/devicetree/bindings/w1/w1-gpio.txt as it works as you mentioned, I'd guess that "not valid maps for state default" can be ignored.

But it is interesting most of examples armbianEnv.txt for parameters param_w1_pin=PC10 show name of gpio in use capital letters but when I use name in capital letters is problem and show in demsg info [ 4.997793] sun50i-h616-pinctrl 300b000.pinctrl: pin PC10 already requested by onewire@0; cannot claim for 300b000.pinctrl:74 and 1-Wire not working but when I use name of gpio in lowercase letters pc20 1-Wire works and show temperature from DS18B20 but is info [ 4.994076] w1-gpio onewire@0: there is not valid maps for state default It maybe any bug ?

I was reacting to this comment. No Armbian devs are going to look at this issue because it is reported on an unsupported board. I was just explaining how the various support models work. While it may or may not be a generic issue, the fact is that it is reported on an unsupported board. With very limited resources the volunteer devs can't look into most things that are reported. Thus I was encouraging you to contribute your time to submit a fix. You did provide a workaround, but indicate here that you are looking for an underlying fix. I'm just here saying that unless someone in the community steps up that isn't likely to happen.

Wow 🙂 I have success dmesg | grep -i wire* [ 4.991132] Driver for 1-wire Dallas network protocol. [ 4.994076] w1-gpio onewire@0: there is not valid maps for state default [ 4.994183] gpio-74 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 5.021347] w1_master_driver w1_bus_master1: Attaching one wire slave 28.03165129ecff crc 24 cat /sys/bus/w1/devices/28-03165129ecff/w1_slave 54 01 4b 46 7f ff 0c 10 fd : crc=fd YES 54 01 4b 46 7f ff 0c 10 fd t=21250 What do I change in /boot/armbianEnv.txt Instead of capital letters PC10, I used in lowercase letters pc10 for the gpio name stupid mistake on my part and maybe I suggested examples param_w1_pin=pc10 param_w1_pin_int_pullup=0 user_overlays=w1-gpio So we can now use sensors like DS18B20 etc with w1-gpio on Orange Pi Zero v3 w with w1-gpio.dts: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&pio>; __overlay__ { w1_pins: w1_pins { pins = "PC10"; function = "gpio_in"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { onewire@0 { compatible = "w1-gpio"; pinctrl-names = "default"; pinctrl-0 = <&w1_pins>; gpios = <&pio 2 10 0>; /* PC10 */ status = "okay"; }; }; }; }; I don't know what I need to correct to remove this info: [ 4.994076] w1-gpio onewire@0: there is not valid maps for state default

Due to my oversight, I have not posted the topic in the correct section. I'll help move it to "Software, Applications, Userspace".

I have no complaints about the kernel that comes with the board. And with the fact that the ZFS packages supplied by armbian are not for debian 12 (bookworm). This has nothing to do with my board. I imagine there will be other boards that will have problems with the zfs package that comes from armbian and are using debian 12. As you can see, I have also shared the workaround.

Nevermind, I just erased & installed the latest version and now sequencer works. Sorry for the trouble.