Frank Wunderlich

@ryderlee1110 does your ref-board use MT7975N too for 2g4?

So we maybe need different offset or calculation for this chip https://github.com/openwrt/mt76/blob/master/mt7915/init.c#L55 https://github.com/openwrt/mt76/blob/master/mt7915/mcu.c#L3108 When looking at the graph above,offset/command is right,but value itself seems not millicelsius or need some other...

i guess more the eeprom (which maybe sets the temp value offset) is wrong... i see function mt7915_eeprom_name in mt7915/eeprom.c which selects the eeprom, but this function seems not to...

same output with disabled eeprom-data in dts root@bpi-r3:~# cat /sys/class/ieee80211/phy*/hwmon*/temp1_input 43000 23000 my debug shows now that MT7975_DUAL_ADIE (MT7986_EEPROM_MT7975_DUAL_DEFAULT) option is used after first eeprom-load (mt7915_eeprom_load) fails now in mt7915_eeprom_init...

I loaded the eeprom which is available in linux-firmware git https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek But yes,it can be wrong

@ryderlee1110 any idea how to get further here?

What is hardware revision and can you look on the frontend chip if this is still a mt7975?

Or at least detect the problematic firmware (or invalid calibration data) from driver to handle it there (maybe off-tree for affected boards to hold mainlinedriver clean for this)?

if it helps in my repo all pci work for me (basicly same code daniel has in his WIP tree) https://github.com/frank-w/BPI-Router-Linux/blob/6.9-rc/arch/arm64/boot/dts/mediatek/mt7988a.dtsi#L891 https://github.com/frank-w/BPI-Router-Linux/blob/6.9-rc/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4.dts but maybe driver is different in 6.1

do you have enabled any kind of hardware-acceleration (flowoffload,wed)? if yes, can you try without this?