MR3420v1, wifi not detected in 21.02.1

Installing and Using OpenWrt
2

Did you keep settings when you ran the upgrade?

3

Seems it's not compatible between version, so I decide not to keep setting.

4

Did you include the owl-loader? Just a guess

5

I've just re-create image with owl-loader, but seems no effect yet.

Seems ath9k on 21.02.1 unable to recognize the wireless module.

Someone know what file and where to put this file?
Is this art.bin file?

[ 17.781331] ath: phy0: Unable to load EEPROM file ath9k-eeprom-pci-0000:00:00.0.bin

6

When I switch back to lede, wifi is detected.

What is the difference between them?
What part is the source that I need to modify to get wireless detected?

7

This device is not supported on 21.02.1

The last supported version was 17.01.5

8

The old version reads wifi cal data direct from flash every time it boots up. The new version reads the flash once during the first boot and prepares a file in the filesystem, which the driver then reads during subsequent reboots. In a dual band device the file seems like it is in /lib/firmware/ath10k, despite it being data for ath9k. I don't have a single band device running 21.02 to look there.

9

Thank you for this info...
Now I can understand why eth9k is looking the .bin file in the bootlog.

Is there a way to generate the file? or how to reconfigure the wireless when it seems the fw unable generate the file from the art partition?

Maybe, is there a way to use again the art partition during boot?

10

This file is auto generated during first attempt to load eeprom by /etc/hotplug.d/firmware/10-ath9k-eeprom script:

	netgear,wnr1000-v2|\
	netgear,wnr2000-v3|\
	netgear,wnr612-v2|\
	on,n150r|\
	tplink,tl-mr3220-v1|\
	tplink,tl-mr3420-v1|\
	tplink,tl-wr740n-v1|\
	tplink,tl-wr740n-v3|\
	tplink,tl-wr741-v1|\
	tplink,tl-wr743nd-v1|\
	tplink,tl-wr841-v7)
		caldata_extract "art" 0x1000 0x1000
		;;

But if you changed boardname (tplink,tl-mr3420-v1) or incorrectly move art partition eeprom file ath9k-eeprom-pci-0000:00:00.0.bin will be absent or contain incorrect data.
If art partition is correct you can generate the file by command:

dd if=/dev/mtd5 of=/lib/firmware/ath9k-eeprom-pci-0000:00:00.0.bin bs=1 skip=$((0x1000))  count=$((0x1000))

where /dev/mtd5 is mtd-device for art partition.
Or check/correct boardname in scripts and reboot router.

1 Like
11

If you don't need to install additional packages there's OpenWrt 21.02.x ath79 tiny LuCI
Same user have also released ath79 19.07 images OpenWrt 19.07.1 ath79 tiny LuCI

12

How would ath79 19.07.1 or 21.02.x work on a 17.01.5 device?

13

ath79 is smaller, and you can actually fit more/other things (like Luci) into those 4mb.

I obviously haven't tried the image for the specific device, but other 4/32.

14

Still compatible with 17.01.5?

15

they are newer versions, what do you mean by compatible ?

16

The last supported version of OpenWRT for that device was 17.01.5.

17

not specifically 17.0.5, but devices EOLed by 18.06.9 - one of the 4/32 MB tp-link devices.

18

Hardware data (posted above) says 17.01.5

19

I'm aware, but these are community builds, not covered by the wiki.

They lack basic openwrt functionality, like PPP opkg, etc, but are still usable, depending on the use case.

20

I got that it was an OP build...

However, then said it didn't have what the LEDE build had...

Which seemed to be a consequence of trying to run 21.02.1 on an unsupported device.

21

Could be, but it might also be an issue introduced by OP.
Either way, it doesn't hurt to test the ath79 images, IMHO.
If 21.02 doesn't work, 19.07 might.