Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3604 - ath9k firmware is 0 bytes on Fritzbox 7430 #8636

Open
openwrt-bot opened this issue Feb 1, 2021 · 1 comment
Open

FS#3604 - ath9k firmware is 0 bytes on Fritzbox 7430 #8636

openwrt-bot opened this issue Feb 1, 2021 · 1 comment
Labels

Comments

@openwrt-bot
Copy link

openwrt-bot commented Feb 1, 2021

RENErica:

Supply the following if possible:

  • Device problem occurs on Fritz!box 7430
  • Software versions of OpenWrt/LEDE snapshot r15642+2-eb11cd9ea3
  • Steps to reproduce

Firmware for wifi ath9k in the directory /lib/firmware/ is 0 bytes.

Changing the parameter -s 0x1e000 to -s 0x1e800 results in the firmware
being created with 4096 bytes.

The ssid is now displayed, but wifi is very unstable and the connection
is quickly lost.

Here, too, the parameter -l 4096 was changed to -l 5120, which means
that the connection remains stable.

The file /etc/hotplug.d/firmware/12-ath9k-eeprom was locally changed to:

/usr/bin/fritz_cal_extract -i 1 -s 0x1e800 -e 0x207 -l 5120 -o /lib/firmware/$FIRMWARE $(find_mtd_chardev "urlader")

Attached the completely changed file 12-ath9k-eeprom.

@openwrt-bot
Copy link
Author

openwrt-bot commented Oct 7, 2021

doesnotcompete:

I have two FRITZ!Box 7430 devices (identical except for that one of them was shipped more recently) and can confirm that this issue is present on one of them. For the other, the firmware extraction appears to succeed with the default options.
I've attached a boot log showing how the kernel fails to configure the ath9k device with the empty firmware file on OpenWrt 21.02.0.
The fix suggested above succeeds in allowing the system to recognize the device, however it is not configured correctly. The MAC address (and published BSSID) seems to be stuck to "00:02:03:04:05:08", although fritz_tffs_nand can extract the correct MAC address from /dev/mtd1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant