Search the Community

@ag123, @c0rnelius, and anyone else that has interest in sound on these devices. I have been able to put together a patch that enables audio for H161/H618 devices. So far only audio on HDMI works. Analog audio is still generating an error on startup. The patches were taken from a git repository by warpme: https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.6/files , and probably came from the Zunlong SDK. A lot of the code was written by Allwinner. @pixdrift generated a version of the patches for Armbian and I continued to work on them. I have built a few images and have a git repository if anyone would like to test, particularly on boards other than orangpizero3, on which I have tested. zero3 desktop: https://drive.google.com/file/d/1jIMTIqKc6y_uuG7lRyXXhIWQ_fvo0XgI/view?usp=drive_link zero3 server: https://drive.google.com/file/d/1r-yn-ooeYoz1yROEJ-yx01_KhErKN_p8/view?usp=drive_link zero2 server: https://drive.google.com/file/d/1XQ9zzw_Bz-rZancDWuzGwMjHHn_4U8SE/view?usp=drive_link repository: https://github.com/stephengraf/armbian_build_sg.git There is another repository mentioned in the Armbian Forum: https://github.com/NickAlilovic/build If anyone has interest and skills to debug the analog audio, the dmesg errors are: [ 7.125509] ahub_dam-snd-soc-dummy-dai: substream ahub_dam-snd-soc-dummy-dai has no playback, no capture [ 7.125539] sunxi-snd-mach soc:ahub_dam_mach: ASoC: can't create pcm ahub_dam-snd-soc-dummy-dai :-22 [ 7.125780] sunxi-snd-mach: probe of soc:ahub_dam_mach failed with error -22

Hi guys, its the first time im gonna post here so bear with me, i am a recent user of orange pi zero 3, one with 4GB RAM and i have been able to run the latest community release on it, things work besides audio thru hdmi, but i have noticed that the video encoding and decoding is not working, albeit 3d acceleration works thru panfrost and Mesa. I have been digging this topic and i wanted to share what i found and maybe validate if im right or perhaps i am not getting this well. 1. Video encoding and decoding in G31-MP2 is something separated from what Mesa and panfrost would do, so even if those work i cant get video acceleration with h.264 etc. 2. It is possible because the android 12 TV version from the manufacturer can do it in a very easy way, but as far as i understood this is because it is using some kind of closed source driver, that the SoC manufacturer provided (that almost all the boards made with the allwinner H616/H618 would run, so it isnt like orange pi dedicated developers to create the android being offered but it is a stock stuff that Allwinner has available for whoever buys their chips) 3. There are efforts to reverse engineer this properly called CEDRUS but there is kind of a lack of information about them since 2019, it is supposedly present in the kernel, but as many others have said and tried for some reason is not working with H616//h618. Anyone knows if it is still being developed? In conclusion the state of things with hardware decoding and encoding of video in ARM is like a wasteland, at least for linux, these chips, ARM chips we get are mostly developed for android TV boxes or TVs or tablets, but they do not develop for linux, that maybe transferring the necessary code to make it work could be trivial, but with thin resources and doing the bare minimum and being closed source the SoC manufacturer has no interest in creating this support and it is left to open source volunteers to find a way. Which means that support for the H616/H618 might come several years into the future perhaps never. Am I interpreting reality right?, i had some hopes to create something like a jellyfin box with accelerated hardware coding and decoding but nothing might be possible, there is maybe some hope, i read somewhere in the LibreELEC forums that someone made it possible to run it with video decoding (if i am not mistaken) with no audio, so perhaps someone found a way?, thanks in advance.

has anyone ordered and/or played with this https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/ https://liliputing.com/orange-pi-zero-3-is-a-cheap-tiny-single-board-pc-with-up-to-4gb-ram-gigabit-ethernet-and-allwinner-h618/ http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html even the linux images is very 'fresh' as in that they are just released *yesterday* 😄

Dear All, I get frequent and random disconnection from orangepizero3 onboard wifi with armibian community (self-built) both trunk and 24.02 current kernel, 6.6.26 and 6.6.28 message is always [21738.338021] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21848.116072] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21915.426734] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection sm_state (5), status: (2)! [21915.426817] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection Vodafone-CSC failed status code:1! [21919.477424] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [[21738.338021] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21848.116072] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21915.426734] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection sm_state (5), status: (2)! [21915.426817] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection Vodafone-CSC failed status code:1! [21919.477424] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it Full logs available at armbianmonitor -u Any help/hint/solution deeply appreciated

Yesterday, I tried to use the digital IO in my opi zero3, with the Python GPIO package from https://opi-gpio.readthedocs.io/en/latest/ by Richard Hull It depends on having sysfs files in /sys/class/gpio/ My original opi zero has these files and it works, but my opi zero3 doesn’t have these files I learned that /sys/class/gpio is created if the linux kernel is configured with a specific option ON, as suggested in the documentation: https://github.com/rm-hull/OPi.GPIO https://linux-sunxi.org/GPIO Also, a developer has made a change on the opi.GPIO project to support opi zero3 https://github.com/rm-hull/OPi.GPIO/issues/79 I will have time to try this tomorrow... but I want to ask: is anyone using GPIO in its most basic way? As reference: I saw this older thread about zero3's GPIO... https://forum.armbian.com/topic/31493-how-to-enable-i2c3-on-orange-pi-zero-3/ It is using leebobby's "armbian" image, with raspi-config, and wiringpi Using my original opi-zero, I never needed to use armbian-config to enable basic gpio and the python opi.gpio just worked as documented Note: the opi.gpio only claims to support basic gpio, not i2c. Update: these are interesting potential solutions and discussions (but they are all from before there was armbian for opiz3) https://www.reddit.com/r/OrangePI/comments/16vfa4g/orange_pi_zero_3_gpio_python_library/ https://github.com/eutim/OPI.GPIO https://www.reddit.com/r/OrangePI/comments/16ioyri/gpio_python_library_for_orange_pi_zero_3/ https://www.reddit.com/r/OrangePI/comments/18iveo3/how_to_control_gpio_pins_in_android_orange_pi/

Hi, what are currently the options of controlling 433Mhz sender/receiver devices from an orange Pi zero 3? Currently the gpios are no longer exposed via sysfs but you could re-enable that feature by compiling a new kernel with the proper configuration. Then wiringpi would work again and you could use 433Utils. But what would be the options without compiling a new kernel? What 433Mhz library exists that uses the new way of controlling the gpios? I am a bit confused about the current state of affairs, please enlighten me...

Just installed armbian on an Orange Pi Zero 3. Right of the bat, had it apt updated and tried to install armbian-config. The package is unavailable, though. me@orangepizero3:~$ apt search armbian-config Sorting... Done Full Text Search... Done me@orangepizero3:~$ apt policy armbian-config armbian-config: Installed: (none) Candidate: (none) Version table: me@orangepizero3:~$ cat /etc/apt/sources.list.d/armbian.list deb [signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com bookworm main bookworm-utils bookworm-desktop Having checked the beta.armbian.com, I don't see the `main` pool. Mirrors do have it, though. Very odd!

Is this the right place to post this type of content? I have a board for Orange Pi. Since I'm usually using windows, it's very inconvenient to burn u-boot. I'll post it to github later if you guys are interested! （Machine translated, English not so good, don't know if the description is apt or not.）

I'm trying to flash the armbian image onto my orange pi zero 3 but it doesn't boot, no red or green light, I've tried both images (jammy and bookworm) but no success, I'm using Balena Etcher to flash the images.

Hi, I am having problems connecting my orange pi zero 3 to my TV via hdmi: No matter what I try the TV reports "no signal". Before I came to armbian I have tried the vendor-supplied debian and arch images and could not get hdmi output on any of them, so it might be that my micro-hdmi adapter is faulty or that the hdmi-port on the device itself is faulty, but over the weekend I cannot replace any hardware so I thought I try here to see if anyone has an idea on what to try. The image I am currently running is Armbian_community_24.5.0-trunk.58_Orangepizero3_jammy_current_6.6.17_gnome_desktop.img. When I log into the device I can see that an Xorg process is running. xrandr produces this output: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 HDMI-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 When I disconnect the hdmi-cable xrandr reports "HDMI-1 disconnected", so at least a little bit of hdmi-functionality is there... The device is connected via an micro-hdmi adapter and a hdmi-cable, I have checked the hdmi-cable but I do not have another adapter nor do I have another micro-hdmi device, so unfortunately I cannot test the adapter. What I have noticed is that (at least sometimes) the device seems to lose network-connectivity (ethernet) when the hdmi-cable is connected - and regains connectivity as soon as the hdmi-cable is disconnected, so there seems to be some conflict between hdmi and ethernet. I do not know where the display modes come from that xrandr displays as the TV is a 4k model that supports a lot more modes. So my question is: Is there anything I could try to get hdmi working or at least to narrow down the problem?

Hi! So the problem is when I configure wifi hotspot using hostapd, isc-dhcp-server, and ifupdown, I'm able to start the AP, connect to it, and ping. However, the moment any device connects to the AP the serial console gets spammed with this message around once a second: protocol 0000 is buggy, dev wlan0 This happens on the unofficial Armbian build (from the Armbian OrangePi Zero3 page), DietPi, and the official OrangePi Debian build. The wireless band doesn't matter. Kernel version: 6.1.31-sun50iw9. I tried to set up the AP with NetworkManager, but couldn't manage to connect to it. Probably DHCP issues that I couldn't resolve. I haven't run the AP for a prolonged period, only like 1hour. So I'm not sure if this has any effect on the performance and stability. Could somebody suggest if this is something to worry about or just a harmless warning?

I did not find the build for Orange Pi Zero 3 Vice versa I found the build for Orange Pi Zero2 Both SBCs are equipped with Allwinner H6 CPU (H618 for the board Zero 3 and H616 for the board Zero2). Is the build for Orange Pi Zero2 compatible with Orange Pi Zero 3 as well?

Hi, I am having a problem getting the graphical login to work... What I run is an ubuntu jammy image with gnome, however when I boot with my tv connected via hdmi it seems to work at first but finally I end up with a screen just displaying the above error. armbianEnv.txt contains the line "disp_mode=1920x1080p60" (a mode my TV supports), yet when the device starts it uses the 4k mode - could this be part of the problem? So how could I get this working and how would I ensure that my device only uses fhd resolution, even though my tv can also do 4k? Many thanks!

Hi, I'm new to Armbian and this is my first time ever compiling any Linux system. I'm sorry to bother you with such a basic question, but I just don't understand. I want to enable a kernel module. Upon browsing the kernel configuration utility menus, I don't see this functionality anywhere. But if I run search with '/', I find this, this is the module I want: How do I now proceed to enable it? Or make sure that it's enabled (if present by default)? Also, what's the meaning of =y and =m? It's listed in the resulting .config file as =y, just as the search shows.

Hello i use armbian on my orange pi and have a problem about the wifi connection. I have my orange pi near my 3D printer. When i plug it in, to boot the armbian it works great. But the orange pi will (SOMETIMES) not connect to my wlan. When i change the room and put it nearly my pc, it will connect without any problems... So i check the wifi quality: - near my pc i have a link quality 70/70 - near my 3d printer i have a link quality 64/70 and signal level: 46dBm is this to low for a easy connection?? thank you

Hi, I am new here so please apologize if I am asking already asked question, but I couldn't find the solution. I am trying to install docker on my orange pi zero 3 which is running Armbian (24.2.0-trunk.519) aarch64, kernel version 6.6.15-current-sunxi64. I have found this post, but I was not able to install docker because I found 2 problem that I don't know how to solve. 1. Installing docker using armbian-config does not work. I install armbian-config, run it as su/sudo, choose docker and install. The installer does something and after it's done it returns me to the same screen where I have chosen docker to be installed. So, no confirmation that I have installed the software, even star is omitted near docker(if you know what I mean). 2. Following the instructions from docker page, I follow every single step, but when it comes to the command svarog@orangepizero3:~$ sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin Reading package lists... Done Building dependency tree... Done Reading state information... Done Package docker-ce is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source Package docker-ce-cli is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'docker-ce' has no installation candidate E: Package 'docker-ce-cli' has no installation candidate E: Unable to locate package containerd.io E: Couldn't find any package by glob 'containerd.io' E: Couldn't find any package by regex 'containerd.io' E: Unable to locate package docker-buildx-plugin E: Unable to locate package docker-compose-plugin this is the response that I get. Maybe I am missing something or I am total noob, but I am pretty sure that the installer is done correctly(I mean the documentation) and the only thing that could be wrong is me... Can you please help me to figure out why I cannot install docker and what am I doing wrong in the process? thanks

Problem I created a Bridge Access Point using Orange Pi Zero 3 with the Ubuntu OS. However, after going through a fairly lengthy configuration, there is an issue when trying to connect to my Orange Pi Zero 3 Access Point. The problem is: it gets stuck at 'authenticate,' and there is no pop-up to enter the password on my smartphone. Configuration Setting file system /etc/network/interfaces # Network is managed by Network manager #auto lo #iface lo inet loopback # #Eth Static Configuration #auto eth0 #iface eth0 inet dhcp # HiBob Configuration # address 192.168.6.55 # netmask 255.255.255.0 # gateway 192.168.6.254 # dns-nameservers 8.8.8.8 # #Wlan0 Static Configuration #auto wlan0 #allow-hotplug wlan0 #iface wlan0 inet manual #wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf #iface default inet static # address - # netmask 255.255.255.0 # gateway 192.168.6.254 # #Access Point Configuration auto lo iface lo inet loopback # Eth0 Configuration auto eth0 allow-hotplug eth0 iface eth0 inet manual # Wlan0 Configuration auto wlan0 allow-hotplug wlan0 iface wlan0 inet manual #wireless power off # Br0 Configuration auto br0 iface br0 inet static address 192.168.6.55 netmask 255.255.255.0 gateway 192.168.6.254 bridge_ports eth0 wlan0 bridge_fd 0 bridge_stp off Setting file system /etc/hostapd.conf # # orangepi hostapd configuration example # # nl80211 mode # ssid=HBGateway interface=wlan0 hw_mode=g channel=40 bridge=br0 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 wpa=2 preamble=1 wpa_psk=66eb31d2b48d19ba216f2e50c6831ee11be98e2fa3a8075e30b866f4a5ccda27 wpa_passphrase=6666666666 wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP auth_algs=1 macaddr_acl=0 ### IEEE 802.11n ieee80211n=1 ht_capab=[SHORT-GI-20][SHORT-GI-40][HT40+] country_code=ID ieee80211d=1 ### IEEE 802.11n ### IEEE 802.11a hw_mode=a ### IEEE 802.11a ### IEEE 802.11ac ieee80211ac=1 #vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3] vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=42 ### IEEE 802.11ac # controlling enabled ctrl_interface=/var/run/hostapd ctrl_interface_group=0 Result Configuration ifconfig result br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.6.55 netmask 255.255.255.0 broadcast 192.168.6.255 inet6 fe80::a84f:ff:fec0:5cc8 prefixlen 64 scopeid 0x20<link> ether aa:4f:00:c0:5c:c8 txqueuelen 1000 (Ethernet) RX packets 8075 bytes 1468199 (1.4 MB) RX errors 0 dropped 2 overruns 0 frame 0 TX packets 1316 bytes 162441 (162.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 02:00:08:3d:19:71 txqueuelen 1000 (Ethernet) RX packets 8118 bytes 1588035 (1.5 MB) RX errors 0 dropped 41 overruns 0 frame 0 TX packets 1316 bytes 162441 (162.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 43 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 10 bytes 1612 (1.6 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 10 bytes 1612 (1.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether f8:b4:76:a0:3d:7b txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1687 bytes 276151 (276.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Question I have used this configuration on Orange Pi Zero 2, and it worked successfully. There are around 100 devices running in production using this setup. However, when I tried to apply the same configuration to Orange Pi Zero 3, it failed, and I haven't found many forums discussing it yet. Could it be because Orange Pi Zero 3 is still relatively new? How can I resolve this issue? I've heard there are quite a few bugs in the Ubuntu OS for Orange Pi Zero 3. OS Ubuntu Download : https://drive.google.com/drive/folders/1CJYrhHyyje9dEY4-t7JhcZBJfdAFBJro?usp=drive_link Orangepizero3_1.0.2_ubuntu_jammy_desktop_xfce_linux6.1.31

I recently picked up an Orange Pi Zero 3 and have been trying to figure out how to get the i2c pins working on the GPIO. The pinout shows pins 2 and 3 (229 and 228 according to the orange pi version of wiringPi) being used to i2c-3. The downloadable images seem to be hodge-podge with the orange-pi-os version based on arch linux. But their instructions appears to be based on earlier orange pi models that had an Orange Pi OS based on armbian which included a 'orangepi-config' command similar to raspi-config. There is no orangepi-config in the arch-based Opi-OS. A third party image from leeboby includes a current buster version of Raspbian but while it contains raspi-config, it doesn't seem to enable i2c-3 and the i2c-0 does not seem to be showing any devices I connect to pins 2 and 3. After some armwrestling with their 'support' contact, he finally confirmed their new OS doesn't include the orangepi-config (big help - duh) but said I might want to check out their ubuntu and debian images (I'll try one of those later tonight). In the meantime, i've already done quite a bit of configuring of a RaspAp install and some other tools such as wireguard and the like for the application I hope to put the thing to, serving as a remote-gateway when I'm in my RV. I want to be able to use the i2c to monitor the 12v battery power and solar panels on the roof, hopefully so i can keep the remote connection powered when I leave the RV set up somewhere but head back downstate to work. dmesg shows that it detects an mv64xxx based i2c and a axp20x (AXP313a) i2c. I'm assuming the latter is used by the HDMI as running i2cdetect -l shows i2c-0 as the mv64xxx_i2c adapter and i2c-1 as DesignWare HDMI. But, as mentioned, connecting i2c devices to pins 2 and 3 as per the gpio pinout diagram (it's rotated 180 degrees on this board) doesn't wind up showing any of my connected devices in i2cdetect. So I think the raspbian image is trying to use whatever the OEM raspberry bcm chip config uses. the opi wiringpi gpio readall shows GPIO 229 - wPi 0 as SDA.3 on the second pin (physical 3) and GPIO 228, wPi 1 as SCL.3 on the third pin (physical 5) The /boot/config.txt was either non-existent or empty as after running raspi-config to try enabling i2c within it, the only line in the file was dtparam=i2c_arm=on and there is no cmdline.txt in that directory either. I tried this config.txt setup also with no changes after rebooting: dtparam=i2c_arm=off dtparam=i2c-gpio=on #dtoverlay=i2c-gpio,bus=3,i2c_gpio_sda=2,i2c_gpio_scl=3 dtoverlay=i2c-gpio,bus=3,i2c_gpio_sda=229,i2c_gpio_scl=228 (the commented out line being another variation I tried) This computer uses a H618 chip similar to the banana pis. I should note their wiringpi doesn't have an H618 configuration within it's source code, but detects it as H616. (I do not know if this effects how the command works or not) Any help getting i2c working is appreciated

[root@lalaki ~]# journalctl -p4 Sep 16 14:27:11 lalaki kernel: watchdog: watchdog0: watchdog did not stop! Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 0 Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 1 Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 2 Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 3 Sep 16 14:26:51 lalaki kernel: KASLR disabled due to lack of seed Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 0 Sep 16 14:26:51 lalaki kernel: axp20x-regulator axp20x-regulator: DCDC frequency on AXP313a is fixed to 3 MHz. Sep 16 14:26:51 lalaki kernel: axp20x-regulator axp20x-regulator: Error setting dcdc frequency: -22 Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-ph not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: debugfs: Directory '1100000.mixer' with parent 'regmap' already present! Sep 16 14:26:51 lalaki kernel: debugfs: Directory '1100000.mixer' with parent 'regmap' already present! Sep 16 14:26:51 lalaki kernel: sun8i-dw-hdmi 6000000.hdmi: supply hvcc not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pc not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: sun50i-cpufreq-nvmem: will use speed0 CPU OPPs Sep 16 14:26:51 lalaki kernel: OF: /thermal-zones/gpu-thermal/cooling-maps/map0: could not get #cooling-cells for /soc/gpu@1800000 Sep 16 14:26:51 lalaki kernel: thermal_sys: Add a cooling_device property with at least one device Sep 16 14:26:51 lalaki kernel: thermal thermal_zone0: binding zone gpu-thermal with cdev cpufreq-cpu0 failed:-2 Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pg not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pf not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: usb_phy_generic usb_phy_generic.4.auto: supply vcc not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: usb_phy_generic usb_phy_generic.4.auto: dummy supplies not allowed for exclusive requests Sep 16 14:26:51 lalaki kernel: mmc0: host does not support reading read-only switch, assuming write-enable Sep 16 14:26:51 lalaki kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. Sep 16 14:26:51 lalaki kernel: WCN_ERR: dts node for bt_wake not found Sep 16 14:26:53 lalaki kernel: sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned. Sep 16 14:26:53 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pi not found, using dummy regulator Sep 16 14:26:53 lalaki kernel: dwmac-sun8i 5020000.ethernet: Current syscon value is not the default 58000 (expect 0) Sep 16 14:26:53 lalaki kernel: wifi ini path = /lib/firmware/wifi_2355b001_1ant.ini Sep 16 14:26:53 lalaki kernel: sprdwl:sprdwl_get_fw_info length mismatch: len_count=83, r_len=89 Sep 16 14:26:53 lalaki kernel: sprdwl:sprdwl_get_fw_info, drv_version=1, fw_version=2, compat_ver=0 Sep 16 14:26:53 lalaki kernel: sprdwl:chip_model:0x2355, chip_ver:0x0 Sep 16 14:26:53 lalaki kernel: sprdwl:fw_ver:0, fw_std:0x7f, fw_capa:0x120f7f Sep 16 14:26:53 lalaki kernel: sprdwl:mac_addr:a0:67:20:f1:db:fb Sep 16 14:26:53 lalaki kernel: sprdwl:credit_capa:TX_WITH_CREDIT Sep 16 14:26:53 lalaki kernel: sprdwl:ott support:0 Sep 16 14:26:53 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: mixed HW and IP checksum settings. Sep 16 17:10:16 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: sprdwl_start_xmit drop msg due to TX Err Sep 16 17:10:17 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: sprdwl_start_xmit drop msg due to TX Err Sep 16 17:10:17 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: sprdwl_start_xmit drop msg due to TX Err ... Is part of the content merely informative? Should some of the parameters be corrected? for example: default_syscon_value = 58000, should it be changed to 0?