OpenWrt 18.06.1 Don't show wifi wireless network and don't work

what should I do?

I have exactly the same problem on my DSL-2740B. Additionally I flashed back to the original firmware and Wifi is working there.
I also tried some older Versions of OpenWRT and LEDE, but nothing did bring up Wifi again :frowning:
Anything bad seems to be happend in the past.

I did some further resarch on this topic and analyzed the bootlog of OpenWrt and the original firmware.

Interessesting are the lines
[ 0.522826] pci 0000:01:00.0: invalid calibration data
from OpenWrt, whereas the original firmware tells us

ar5416EepromAttach: Read calibration data from FLASH fail 
ar5416EepromAttach: Read calibration data from IMAGE successfully

If this is the problem can anybody tell how to get the calibration data from the image to the nvram that OpenWrt can use it?

I returned back from 18.06.1 to chaos calmer 15.05.1

I did not want to spent rest of my life with not working wifi

I have orange pi zero, also problems

Luci scans wifi correct but kernel not using it, "wifi status" is empty though luci scans wifi-s in the air!?

OpwnWrt 15.05.1 did not work for me :roll_eyes:

Hi, I got the same problem with different device; for what I can say, it seems that ath9k in 18.06.1 overwrites portion of wifi card memory, resulting in broken PCI device ID. Details in Wifi AR922x not detected after upgrade 18.06 .

Hi, can you please help me replicate the issue (I'v got similar one)?

Please post output of:

lspci -nn

(this should output something like 02:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:ff1c] (rev 01)).

Now, there should be a directory under /sys/devices/pci*/*/THE_NUMBER_BEFORE_NETWORK_CONTROLLER ; in my case
/sys/devices/pci0000:01/0000:01:00.0/0000:02:00.0 . Does this directory hold entry 'driver' (should be symlink)?

furthermore, does

lsmod | grep owl

print anything? if so, try invoking

rmmod owl-loader

and then reinsert owl-loader with

modprobe owl-loader

now, check output of dmesg for atheros (ath)-related keywords.

dmesg | grep ath

Btw, do you use either extroot or overlay on usbstick, or, perhaps, customized image?

I have the same problem with [https://openwrt.org/toh/zte/zxhnh108n](ZTE H108n).

It only works with 15.05.1 If I try with 18.06.1, even with 17.01.6, there is no wifi recognized. It really catches my attention that there's no iw command available. (image attached)

2018-11-30%2015_41_28-Clipboard

The firmware I'm using is openwrt-18.06.1-brcm63xx-generic-96328avng-generic-squashfs-cfe-8M.bin

Somewhere I read it had to do with open source drivers not supporting Broadcom chipset (BCM43225), but not finding iw command baffles me.

Hi, I'm not familiar with your model, however - can you please post output of your dmesg? What happens if you install iw and wpad-mini? Also, have you tried checking whether the driver for your wireless isn't in one of the kmod-b43, kmod-brcm-wl or kmod-brcmfmac packages, that were not installed?

As far as I understand, wlan0 gets in openwrt created by netifd, if it has both wifi configuration, drivers and hostapd. If you're missing one of theese, it will not be created.

1 Like

Hi, thanks for your reply.

Yes that was the problem. It seems that the image is missing all wireless related files, for space constraints I guess.

To make it work I had to install all these packages:

With b43 driver:

opkg install kmod-b43 kmod-mac80211 kmod-bcma kmod-cfg80211 iw wpa-supplicant

In my case It also worked with brcmsmac:

opkg install kmod-brcmsmac kmod-mac80211 kmod-bcma kmod-lib-cordic kmod-lib-crc8 kmod-brcmutil kmod-cfg80211

What doesn't work is multiple SSIDs with none of these drivers, (one AP and one STA) but I guess I have to open another issue for that.

If you can, please update the documentation at openwrt.org for this router with the above listed packages. It will help other users wuth the same problem.
I have used some devices myself which wouldn't work with multiple SSIDs and the cause seems to be the limited support for drivers. One of the devices had brcm43217 wifi chip.

1 Like

Hello!

I have the same problem as in the first post. Same device (D-Link DSL-2740B type F1), same openwrt/luci firmware: 18.06.1.

Following the posts I too:

  • get nothing from iw list
  • have no wireless config file in /etc/config/
  • have all the 5 kernel packages indicated installed
  • get [ 0.433619] pci 0000:01:00.0: [168c:ff1c] type 00 class 0x020000 from dmesg

Then I don't know how Axsus got to the point he posted, as I still can't get any wifi/wireless page...

I did what luksoft suggested and if I ls the /sys/devices/... folder I see:

  • broken_parity_status
  • class
  • config
  • consistent_dma_mask_bits
  • device
  • devspec
  • dma_mask_bits
  • driver
  • driver_override
  • enable
  • other ten entries from irq to resource0
  • subsystem
  • subsystem_device
  • subsystem_vendor
  • uevent
  • vendor

Continued with owl-loader procedure and got these errors:

  • [12.337343] owl-loader 0000:01:00.1: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2
  • [12.884419] firmware ath9k-eeprom-pci-0000:01:00.0.bin : firmware_loading_store: map pages failed
  • [2874.060082] owl-loader 0000:01:00.1: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2
  • [2874.169412] firmware ath9k-eeprom-pci-0000:01:00.0.bin : firmware_loading_store: map pages failed

Can anyone tell me what to do to solve this problem? As the n00b I am, I couldn't figure out nothing...

Thanks in advantage to everybody!

You need b43 drivers for the wifi chip. You may also need the b43-legacy drivers instead. Try to experiment with those listed above.

According to wikidevi, the correct kernel modules are indeed ath9k. I'd start with a factory reset, to check if the firstboot scripts now manage to extract the correct EEPROM data from flash, to feed into owl-loader. If not, you may have to investigate deeper and check the source what other (similar) devices do to extract it and experiment manually.

Factory Reset did nothing even on multiple resets.

What should I do to investigate and experiment manually?
Should I try to install some packages from other similar devices? Or should I try out this (ImageBuilder) first?
Or should I try to create a Wireless config file similar to some of them and put it into the /etc/config folder?
Where can I find what other devices do to extract the EEPROM data?

Thanks again, btw.

On my device the commands deliver the following results:

root@OpenWrt:/# lspci -nn
00:00.0 PCI bridge [0604]: Broadcom Limited Device [14e4:6328]
01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR5008 Wireless Network Adapter [168c:ff1c] (rev 01)
root@OpenWrt:/# lsmod | grep owl
owl_loader              2032  0
root@OpenWrt:/# rmmod owl-loader
root@OpenWrt:/# modprobe owl-loader
[ 1329.982231] owl-loader 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2
[ 1329.993106] owl-loader 0000:01:00.0: Falling back to user helper
root@OpenWrt:/# [ 1330.091135] firmware ath9k-eeprom-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[ 1330.100545] owl-loader 0000:01:00.0: no eeprom data received.

root@OpenWrt:/# dmesg | grep ath
[   12.281234] owl-loader 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2
[   12.831320] firmware ath9k-eeprom-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[  497.055627] owl-loader 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2
[  497.164431] firmware ath9k-eeprom-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[ 1329.982231] owl-loader 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2
[ 1330.091135] firmware ath9k-eeprom-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed

I get almost the same results as Unkissedfrog: the difference is that I get nothing from

  • rmmod owl-loader
  • modprobe owl-loader

Reading somewhere, I found out that Atheros ath9k does not require firmware but it does require calibration data, and from dmesg I get:

  • [ 0.552124] pci 0000:01:00.0: invalid calibration data

which is exactly the same address I get from the error of firmware loading:

  • [2874.060082] owl-loader 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2

Someone knows what is needed to get the right calibration data?

Hello, i have same issue with wireless network. After resetting on OpenWrt , wireless network not listen on Interface section and have a invalid calibration data on log...
How can resolve it? I stucked on from 2019
I just posted issue here: https://github.com/openwrt/openwrt/issues/7135
I just try to revert original fw (old 2.02 or other versions) wifi works but when load any version of OpenWrt (included last version 21.02.2) wifi network interface disappears....
Only first time that i load OpenWrt wifi work... after reset to factory default, wifi wireless not showed
Please help me
Thanks

ok i resolved the issue with this steps:

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