Hello Adrian, On 1/29/20 2:57 PM, Adrian Schmutzler wrote: > Hi, > >> -----Original Message----- >> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On >> Behalf Of David Bauer >> Sent: Dienstag, 28. Januar 2020 21:05 >> To: drvl...@gmail.com; achte...@googlemail.com; openwrt-devel <openwrt- >> de...@lists.openwrt.org> >> Subject: [OpenWrt-Devel] Netgear R6260 EEPROM location >> >> Hi, >> >> while testing my shiny new NETGEAR R6260 with OpenWrt, i was experiencing >> very bad >> reception as well as throughput. Upon closer inspection, it turns out that >> the >> EEPROM >> is read from an incorrect offset. The Offset positions here are: >> >> - 0x28000 for 5GHz >> - 0x20000 for 2.4GHz > > Have you checked partitioning? This might just be a wrong position for the > factory partition as well.
Yes, I've checked the partitioning (and it is off). However, I still opted to push the other fix, as I'm unsure whether or not the partition mapping is off for all boards or only my specific R6260, as the partition map seems to stored on the device in the SC_PART_MAP partition instead of the kernel. So it could be entirely possible, that this differs between different models, thus we would never have a "correct" partition mapping. However, in this case WiFi would have been broken for the beginning. But as the R6260 was introduced as "Same board, different labling", i count the chance of WiFi being broken from the beginning as high, especially as the Radio transmits, but VHT modes are nonsense and throughput is abysmal. See /proc/mtd below - partitions are in order: # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "Bootloader" mtd1: 00100000 00020000 "SC_PART_MAP" mtd2: 00400000 00020000 "Kernel" mtd3: 02800000 00020000 "Rootfs" mtd4: 00200000 00020000 "English UI" mtd5: 00220000 00020000 "ML1" mtd6: 00200000 00020000 "ML2" mtd7: 00200000 00020000 "ML3" mtd8: 00200000 00020000 "ML4" mtd9: 00200000 00020000 "ML5" mtd10: 00200000 00020000 "ML6" mtd11: 00200000 00020000 "ML7" mtd12: 00200000 00020000 "ML8" mtd13: 00200000 00020000 "ML9" mtd14: 00200000 00020000 "ML10" mtd15: 00200000 00020000 "ML11" mtd16: 00200000 00020000 "Factory" mtd17: 00220000 00020000 "SC Private Data" mtd18: 00200000 00020000 "POT" mtd19: 00200000 00020000 "Traffic Meter" mtd20: 00200000 00020000 "SC PID" mtd21: 00200000 00020000 "SC Nvram" mtd22: 00200000 00020000 "Ralink Nvram" mtd23: 00200000 00020000 "Reserved Block1" mtd24: 00200000 00020000 "Reserved Block2" mtd25: 00200000 00020000 "Reserved Block3" mtd26: 00200000 00020000 "Reserved Block4" mtd27: 00200000 00020000 "Reserved Block5" mtd28: 02140000 00020000 "Reserved Block6" So I'm waiting on feedback from other owners of these boards and using this (more or less) strange fix in the meantime. Best wishes David > > Best > > Adrian > >> >> Can someone confirm these offsets on their boards? Maybe this is wrong not >> only on >> the R6260, but also on the R6350 and R6850. >> >> Best wishes >> David >> >> _______________________________________________ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
