But the Beryl’s access point is not visible to my phone. (Other access points are visible to the phone, so I know the phone is working.) Luci says “Wireless is not associated”, but I can’t find anything on the Web to tell me what that really means. (Sorry, I’m only allowed one attached file, so I can’t provide a screenshot.)
I noticed that the Wi-Fi hardware was configured for China, rather than the UK, and so I changed it, but that made no difference. Here’s the current setting:
I forget the exact details, but there was some sort of key error in the upgrade path in the 3.0 versions. If you upgrade all of them sequentially (instead of jumping from where you are straight to 3.215) you should be able to upgrade.
I would do that and then power straight through to the 4.0 beta, as the wifi drivers have changed in the newest release.
Thanks for the tip. That’s potentially disruptive, and I can’t be without Internet access during the working week, so I’ll have to wait for next weekend before attempting the upgrade.
Are there any solutions that don’t involve running beta code?
Thanks for coming back to me, @alzhao. @jdub has suggested upgrading one step at a time, so I’ll try that this coming weekend, when downtime will be less of a problem.
The Wi-Fi was already non-functional when I changed the country code from CN to GB. That change was an attempt to fix the problem. I’m in the UK, and I don’t know whether a phone in the UK is compatible with a Wi-Fi access point configured for China.
I’ve set the 2.4GHz access point to channel 11, because a Wi-Fi analyser on my phone tells me that nothing else is transmitting anywhere near that channel. I’ve left the 5GHz channel at auto for now.
The MT1300’s Wi-Fi SSID is not visible to my phone.
iw list doesn’t display any wireless devices, and so I wonder whether we’re using the right driver. I see this in syslog:
[ 19.821413] mt7615_init()-->
[ 19.824302] Use the default ePAeLNA bin image!
[ 19.828725] Use the default /etc_ro/wlan/MT7615E_EEPROM1.bin bin image!
[ 19.835351] <--mt7615_init()
I just had the same thing with the Beryl plugged into a USB socket that I found on the source router for power. When I plugged the Beryl into a regular USB power source the wifi started working fine.
The Wireless admin panel showed the exact same display both times, and I had a solid white light. So I suspect that if the Beryl is slightly underpowered, it still looks like it is working but the wireless circuit isn’t live.
I figured I would try a different power source before completely resetting the unit, and I lucked out.
If you mean USB socket on power strips etc. that could be the reason.
Usually these USB power has very big noice. Don’t use these for your phone as well.
You should use the original power adapter for Beryl or use one charging your phone.
Sorry for my long absence. I can’t be without the MT1300, and so I haven’t dared upgrade to beta software.
I’ve bought a second MT1300 to isolate an untrusted laptop from my network, and it’s developed the same problem: no Wi-Fi. In both cases, I use the power supply that came with the MT1300.
I noticed this evening that the gl_init script is disabled on both machines. I didn’t disable it myself. /etc/init.d/gl_init looks as if it helps to set up Wi-Fi. Should that startup script be enabled?
