About Netgear WNDR4300v1 5GHz missing problem

-
After flashing OpenWRT to Netgear WNDR4300v1, I surprisingly found that 5GHz wireless card was missing. And I tried to flash back to OEM version but ended up in dead loop rebooting.

The 5GHz wifi of WNDR4300 is provided by AR9580 which is connected by the PCI interface. I used dmesg to inspect the log of openwrt and found that PCI found nothing when starting.

Was the chip broken? I nearly gave up and tried to disconnect the router with its power and went to dinner. After the dinner, I powered up the router and -- it just worked! Here is the log from dmesg.


[    0.391671] PCI host bridge to bus 0000:00
[    0.396044] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
[    0.403409] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.409340] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.416575] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.425036] pci 0000:00:00.0: [168c:0033] type 00 class 0x028000
[    0.425047] pci 0000:00:00.0: invalid calibration data
[    0.430556] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]
[    0.430610] pci 0000:00:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    0.430691] pci 0000:00:00.0: supports D1
[    0.430702] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.430929] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[    0.430958] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit]
[    0.438759] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
[    0.446485] pci 0000:00:00.0: using irq 40 for pin 1


PCI worked well.

Why? According to OpenWRT WNDR4300 project page:(https://openwrt.org/toh/netgear/wndr4300)

Sometimes the 5G wifi interface (a separate AR9580 chip attached on PCIe) will completely disappear, because the PCIE_RC strap bit gets stuck at '0'. This can be checked by running “devmem 0x180600b0” and looking at bit 6:
  • GOOD: 0x002F055A
  • BAD: 0x002F051A
On OpenWrt this causes the kernel to completely ignore the PCIe interface and everything attached to it, so only the onchip 2.4GHz radio will work. On the original firmware it may cause the unit to get stuck in a reboot loop.
If this happens, just power the unit off for about 30 seconds. In fact it might be a good idea to power cycle the unit before OpenWrt's initial boot. 

评论

发表评论

此博客中的热门博文

Openwrt路由器上配置shadowsocks透明代理+gfwlist(PAC)

-
Shadowsocks 服务推荐： Just My Socks 推荐理由：价格便宜，支持月付，安全灵活。 本文配置的前提是已经有shadowsocks服务。你可以通过购买或者自行搭建的方式获得。以下是链接： 直接购买网上的服务，此处推荐 Just My Socks 快速Just My Socks配置Shadowsocks，请点 这里 。 自行搭建，请参考 KVM VPS上配置V2Ray(Shadowsocks mode) + 加速:普通BBR/魔改BBR(测试于Ubuntu 16.04) 本文所使用的环境，仅作参考： OpenWrt 18.06.1/LuCI openwrt-18.06 整体思路： DNS部分： if 访问地址在gfwlist中     DNS请求转发到127.0.0.1:5353的dns-forwarder的监听端口     dns-forwarder转发到8.8.8.8进行解析     8.8.8.8在gfwlist中，通过匹配iptables规则转发到1080端口     ss-redir监听1080端口，通过shadowsocks代理服务器转发请求 else     正常使用公共DNS或者ISP提供的DNS服务器 其他数据： if 访问地址在gfwlist中     通过匹配iptables规则转发到1080端口     ss-redir监听1080端口，通过shadowsocks代理服务器转发请求 else     正常访问 步骤1:依赖包安装（ 非常重要 ） 本文所有的操作都基于SSH和Web管理界面操作。 首先通过SSH添加GPG Key，这样之后添加的源才能通过签名验证： wget http://openwrt-dist.sourceforge.net/packages/openwrt-dist.pub -O /tmp/openwrt-dist.pub opkg-key add /tmp/openwrt-dist.pub 然后在OpenWRT Web管理界面，“系统”>“软件包”>“配置”中，“自定义feeds”最后添加两行源： src/gz openwrt_dist http://openwrt-
阅读全文

Configure shadowsocks transparent proxy + gfwlist(PAC) on OpenWRT Router

-
You must have Shadowsocks services which can be gained in the following way before actually starting to configure. Purchase Shadowsocks Service directly online. Recommendation:  Just My Socks Quick Shadowsocks configuration using Just My Socks, please click here . Build the service yourself. Please refer to  Configure V2Ray(Shadowsocks mode) + 加速:普通BBR/魔改BBR on KVM VPS (Tested on Ubuntu 16.04) . The environment this article used, FYI： OpenWrt 18.06.1/LuCI openwrt-18.06 The Overall Idea: DNS part: if the requested address is in gfwlist     forward DNS request to 127.0.0.1:5353 which is listened by dns-forwarder     dns-forwarder forwards the request to 8.8.8.8 for translating     8.8.8.8 is in gfwlist, so match iptables rules and is fowared to 1080     ss-redir listen on port 1080, foward request to shadowsocks server else     use public DNS servers or the DNS servers provided by the ISP other data: if the requested address is in gfwlist     match ipt
阅读全文

Configure V2Ray(Shadowsocks mode) + 加速:普通BBR/魔改BBR on KVM VPS (Tested on Ubuntu 16.04)

-
First of all, you will need to deploy a VPS with KVM technology as BBR does not support OpenVZ but KVM. I recommend Bandwagonhost and Vultr because of the price. Here is the link to register and deploy: Bandwagonhost Vultr (Or click here to get a big discount, only available for a LIMITED TIME ) Here I suggest you choose Ubuntu 16.04 or later versions as your OS. After everything is ready and you can successfully ping your server from your local environment, connect to your VPS via SSH. Now let's start. Step 1: V2RAY V2RAY is a new generation of software for data proxy. It supports almost all protocols. Here let's choose Shadowsocks as our protocol with which most of us are familiar. Type in the following command in your SSH terminal to install: bash <(curl -L -s https://install.direct/go.sh) Then use your favorite text editor to edit the configuration file located at '/etc/v2ray/config.json'. Here I use vim as my editor and you can use whatever you a
阅读全文