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#3988 - urlader partition no longer available on Fritzbox 7362 SL - wireless broken due to missing caldata #8983

Closed
openwrt-bot opened this issue Aug 22, 2021 · 2 comments
Labels

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Aug 22, 2021

janhoffmann:

The //urlader// partition is no longer accessible with current master on a Fritzbox 7362 SL.

As a result, the wireless caldata cannot be loaded. The file ///lib/firmware/ath9k-eeprom-pci-0000:01:00.0.bin// is created but has a size of 0.

Relevant extract from //dmesg//:

[ 0.569154] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xf1 [ 0.574382] nand: Micron MT29F1G08ABADAWP [ 0.578061] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 0.585742] Scanning device for bad blocks [ 0.658779] 2 fixed-partitions partitions found on MTD device 14000000.flash [ 0.664433] Creating 2 MTD partitions on "14000000.flash": [ 0.669871] 0x000000000000-0x000000400000 : "kernel" [ 0.677067] 0x000000400000-0x000008000000 : "ubi" ... [ 0.706366] spi-nor spi0.4: s25fl008k (1024 Kbytes) [ 0.709836] 2 fixed-partitions partitions found on MTD device spi0.4 [ 0.716236] Creating 2 MTD partitions on "spi0.4": [ 0.721045] 0x000000040000-0x0000000a0000 : "tffs (1)" [ 0.727521] 0x0000000a0000-0x000000100000 : "tffs (2)" ... [ 22.941707] ath9k 0000:01:00.0: enabling device (0000 -> 0002) [ 22.948389] ath9k 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2 [ 22.957623] ath9k 0000:01:00.0: Falling back to sysfs fallback for: ath9k-eeprom-pci-0000:01:00.0.bin [ 23.307603] ath: phy0: Unable to load EEPROM file ath9k-eeprom-pci-0000:01:00.0.bin [ 23.314006] ath9k 0000:01:00.0: Failed to initialize device [ 23.319532] ath9k: probe of 0000:01:00.0 failed with error -22

Maybe this is a side effect of the recent switch to nvmem-cells for reading the MAC address (as this uses the urlader partition)?

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Sep 27, 2021

janhoffmann:

Testing has confirmed that this issue is caused by commit adb3e46 ("lantiq: convert mtd-mac-address to nvmem for Fritz!Box 736x").

Here is the relevant part of the kernel log without this commit (this shows the "urlader" partition being accessible):

[ 11.173721] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xf1 [ 11.178657] nand: Micron MT29F1G08ABADAWP [ 11.182670] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 11.194097] Scanning device for bad blocks [ 11.271593] 2 fixed-partitions partitions found on MTD device 14000000.flash [ 11.277198] Creating 2 MTD partitions on "14000000.flash": [ 11.282787] 0x000000000000-0x000000400000 : "kernel" [ 11.289025] 0x000000400000-0x000008000000 : "ubi" [ 11.302615] spi-lantiq-ssc 1e100800.spi: Lantiq SSC SPI controller (Rev 8, TXFS 8, RXFS 8, DMA 1) [ 11.313868] spi-nor spi0.4: s25fl008k (1024 Kbytes) [ 11.317380] 3 fixed-partitions partitions found on MTD device spi0.4 [ 11.323775] Creating 3 MTD partitions on "spi0.4": [ 11.328466] 0x000000000000-0x000000040000 : "urlader" [ 11.335018] 0x000000040000-0x0000000a0000 : "tffs (1)" [ 11.340288] 0x0000000a0000-0x000000100000 : "tffs (2)" ... [ 29.768174] ath9k 0000:01:00.0: enabling device (0000 -> 0002) [ 29.775022] ath9k 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2 [ 29.784199] ath9k 0000:01:00.0: Falling back to sysfs fallback for: ath9k-eeprom-pci-0000:01:00.0.bin [ 30.477200] ath: EEPROM regdomain: 0x8114 [ 30.477229] ath: EEPROM indicates we should expect a country code [ 30.477247] ath: doing EEPROM country->regdmn map search [ 30.477263] ath: country maps to regdmn code: 0x37 [ 30.477280] ath: Country alpha2 being used: DE [ 30.477293] ath: Regpair used: 0x37 [ 30.493176] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 30.498037] ieee80211 phy0: Atheros AR9300 Rev:3 mem=0xbc000000, irq=144

janh added a commit to janh/openwrt that referenced this issue Mar 16, 2022
Without a partition subnode ofpart_core still parses direct subnodes as
partitions, but it ignores nodes with a compatible property. Due to
this, the switch to nvmem-cells made the urlader partiton inaccessible.
As a result, the wireless network was broken, as the calibration data
is read from that partition by a script.

Fixes: openwrt#8983
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
janh added a commit to janh/openwrt that referenced this issue Mar 16, 2022
Without a partition subnode ofpart_core still parses direct subnodes as
partitions, but it ignores nodes with a compatible property. Due to
this, the switch to nvmem-cells made the urlader partiton inaccessible.
As a result, the wireless network was broken, as the calibration data
is read from that partition by a script.

Fixes: openwrt#8983
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
@janh
Copy link
Contributor

@janh janh commented Mar 16, 2022

Vladdrako pushed a commit to Vladdrako/openwrt that referenced this issue Mar 17, 2022
Without a partition subnode ofpart_core still parses direct subnodes as
partitions, but it ignores nodes with a compatible property. Due to
this, the switch to nvmem-cells made the urlader partition inaccessible.
As a result, the wireless network was broken, as the calibration data
is read from that partition by a script.

Fixes: openwrt#8983
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
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

2 participants