Turris Omnia Wi-Fi 6 : fw_printenv not working

Software SW help
1

Hi,

I would like to generate some diagnostic export for support.
I found that the fw_printenv command, executed because i checked “firmware” in the list of modules to export, has some issue.

root     18249  0.0  0.0   1364  1052 ?        S    Aug09   0:00 /bin/sh /usr/share/diagnostics/diagnostics.sh -b -o /tmp/diagnostics-2024-08-09-17-11-43_63620226.out certgen cron dmesg dns filesystems firewall fi
root     22426  0.0  0.0   1372   600 ?        S    Aug09   0:00 /bin/sh modules/module.sh ./modules/18_firmware.module run
root     22427 99.6  0.3   7416  6844 ?        R    Aug09 1618:39 tail -n 100000
root     23101  1.8  0.0    940   616 ?        S    Aug09  29:39 fw_printenv

I’m running on latest stable version:

k v
Device Turris Omnia
reForis version 1.5.0
Turris OS version 7.0.2
Turris OS branch HBS
Kernel version 5.15.148

Executing the command display this and never stop:

Warning on /dev/mtd0: Attempted to read 65536 bytes but got 0
Warning on /dev/mtd0: Attempted to read 65536 bytes but got 0
Warning on /dev/mtd0: Attempted to read 65536 bytes but got 0
Warning on /dev/mtd0: Attempted to read 65536 bytes but got 0
Warning on /dev/mtd0: Attempted to read 65536 bytes but got 0
Warning on /dev/mtd0: Attempted to read 65536 bytes but got 0
Warning on /dev/mtd0: Attempted to read 65536 bytes but got 0

Here is the config file (found somewhere on another topic)

root@turris:~# cat /etc/fw_env.config 
/dev/mtd0 0xf0000 0x10000 0x10000

root@turris:~# strings /dev/mtd0 | grep 'U-Boot 20'
U-Boot 2022.10-rc4-OpenWrt-r16653+119-44ce70f0e2 (Sep 15 2022 - 18:21:35 +0000)

I could make an export without firmware, but I think support need it to understand why the official SFP+ module doesn’t work on my device =/

Any help is welcome.

Thanks.

2

This is my config file on Omnia:

 cat /etc/fw_env.config
/dev/mtd2 0x00000 0x10000 0x10000

So seems like you put wrong partition there…

Edit?

I just found out that there is:

/usr/bin/fw_env-config-init.sh

That will do it for you

3

At some point U-Boot was updated and its using its own partition for uboot env vars.

Mtd0 is uboot mtd1 is rescue and mtd2 is uboot vars and you should have point there

4

This works:

Calling the script does nothing =/

/usr/bin/fw_env-config-init.sh
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.