【Orange Pi Zero 3】Is the content of the error or warning output by the kernel of a serious nature?

[lalakii is]

[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?

 

 

[Werner]

Armbian does not provide images for this board nor does it support it (yet). The OS you are using comes from a 3rd party. So I suggest to ask for support where you got the image from.

[lalakii is]

 

After a few days of trying to get rid of these annoyances by modifying the kernel source code as well as the device tree, I've finally gotten rid of them, and now there are only a few inconsequential warnings

[lalakii is]

dtbs fixed!

 

kernel: https://drive.google.com/drive/folders/1EwbvUz_T67aveOomDhaL-y-YQ856dkYZ?usp=drive_link

dtbs.tgz

[going]

13 минут назад, lalakii is сказал:

dtbs fixed!

Usually provide a difference file.
Please, if you want to share the results of your work, make a set of patches as the output of the "git format-patch" command.

Or a more time-consuming but faster way to make a pull request directly to the project on github.

[lalakii is]

@going Since I didn't find an actively maintained kernel branch (for orangepizero3), I would have done this otherwise.

[ag123]

hi, just like to join this discussion in a 'development' sense

it seemed there are some works in the head Linux v6.5-rc1

https://groups.google.com/g/linux-sunxi/c/p64EM9m9inY

https://linux-sunxi.org/Xunlong_Orange_Pi_Zero3

https://linux-sunxi.org/Linux_mainlining_effort

 

they seemed to be continued works on H616 mainlining efforts, but that those are working on H618 e.g. Orange Pi zero 3 etc

it could be good to look at the head revisions e.g. v6.5 when we 'backport' codes into e.g. v6.1.31 that is used with armbian.

that could save a lot of rework if at some point we (armbian) decide to move on and use a new kernel e.g. v6.5

and accordingly, i read a post that say things like the wifi drivers as different vendors tried to implement their own drivers, it creates a 'problem' for the mainlining efforts to attempt to reconcile 2 different versions of the 'same driver'.  Hence, it may be good to look at head revisions e.g. v6.5 while 'porting' them back into v6.1.31. it would likely allow us to have 1 version of drivers e.g. from mainline that possibly works on different boards using the same wifi chips etc.

 

 

Edited September 18 by ag123

[ag123]

I'd just like to put a note that for wifi, even the propietary drivers seemed 'unstable', I'm not sure if it is just the drivers itself or something else

 

Edited September 18 by ag123

[going]

4 часа назад, lalakii is сказал:

Since I didn't find an actively maintained kernel branch (for orangepizero3),

@lalakii is In Armbian for chips, allwinner uses only a branch with kernel.org . There is no special branch for a separate chip.

 

There is a series of patches that were taken from different places or made by different users and added to the series file.

The binary files that you kindly provided are useless for the build system.
Links to download from Google drive are also not useful.
All you need is to apply a series of patches to the corresponding kernel branch as a "git am" command.
Then make your comments on top with explanations and an indication of the author. Then extract these last commits using a script.

cp armbian/build/tools/mk_format_patch $USER/bin; chmod +x $USER/bin
mkdir -p $USER/tmpwork/patches.armbian
cd /path/to/linux-stable
mk_format_patch . HEAD~7..HEAD $USER/tmpwork/patches.armbian

I think that you have guessed where they need to be placed, make a commit in the build system itself and make a pull request.

[lalakii is]

@ag123 I am going to try 6.6-rc2😀