At last I got the serial connection running, had to swap the tx pin with the rx pin.
I now have one unnecessay line in the uboot configuration storage.
flag_last_succes=0
instead of
flag_last_success=0
because I mistyped and saved the change. Can I get rid of the line somehow?
NVM I had to do "setenv flag_last_succes" without a varaiable.
Now I have build a padavan firmware with the prometheus script on a physically different network/location.
Someone knows how I can flash the trx file manually?
I am also very curious about the wifi stability and performance. Does anyone happen to have iperf3 results over both the 2.4ghz wifi and the 5ghz wifi?
And can someboday explain how to backup the original firmware.
I have read a post from hammer where he explain he don't do the command erase kernel but i am bot sure.
I have followed the tutorial from hammer. and everything work.
But have the same problem for radio 2.4 GHZ
log show daemon.notice hostapd: wlan0: STA XX:XX:XX:XX:XX:XX IEEE 802.11: did not acknowledge authentication response
Go through the wizard to set passwords for the router + wifi
Reconnect to the router using WiFi
Goto http://192.168.31.1
Logon and find the page where you can upgrade the firmware look for a big yellow dot with an “i” inside. You will see the version number of the router and there is a button below where you can browse for a file. Flash miwifi_r3g_firmware_c2175_2.25.122.bin (developer firmware) and wait a few minutes.
Download https://play.google.com/store/apps/details?id=com.xiaomi.router to your phone/tablet (there is also an iOS app)
Open “Mi Wi-Fi” app (and sign-up) and sign-in to your account. Router will be detected and added to your account (assuming you are connected to the WiFi on the router and the routers WAN port is connected to Internet).
On a PC, visit http://d.miwifi.com/rom/ssh and sign-in to you account. You will get to a page that should display your router, the root password and a download button. Hit the button to get miwifi_ssh.bin
Format USB drive using FAT32 and copy miwifi_ssh.bin, lede-ramips-mt7621-mir3g-squashfs-kernel1.bin and lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin to the USB drive
Cut the power the router, put the USB drive in the router, press and hold “reset” button (with a paper-clip), power on the router (while holding reset). When the router starts flashing yellow release the reset button. Wait until router has rebooted and you should (finally…) have SSH access.
Login to the router using SSH using the “root” as username and the (root) “password” from http://d.miwifi.com/rom/ssh
In SSH console
cd /extdisks/sda1 (can be different if you remove and reinsert the usb stick)
reboot
LEDE should be installed and available at 192.168.1.1 (with WiFi disabled I assume)
Upgrading to a newer snapshot can be done using the regular methods (from the command-line using sysupgrade or through LuCI) using lede-ramips-mt7621-mir3g-squashfs-sysupgrade.tar
I would recommend adding the link to download the dev build on step 8, also it would be more clear if download the android app link will be on the next step.
In addition, could you please add a section of known issues and add there the issue which affect some of the users when trying to connect to the 2.4GHz:
daemon.notice hostapd: wlan0: STA XX:XX:XX:XX:XX:XX IEEE 802.11: did not acknowledge authentication response
Per your request I added "Known Issues" section. If there are any other known issues, even if they are temporary it's better to mention them right know to give potential buyers better image of the situation. We can delete them later.
I don't have this device on hand. If you can provide those link you mentioned I will add them to the instruction.
Setting disassoc_low_ack '0’ does not solve the issue for me, below are the settings from my /etc/config/wireless.
As I mentioned before, it appears to be related to the distance from the router and never happens if I'm in the same room as the router, although in the room which this issue is seen is not really far and the signal strength is good (-56dBm according to wifi analyzer).
Also, the connection to the 2.4GHz is stable after I'm already connected even if I move to the room which the issue was reproducing in the 1st place, but if I disconnect than I will probably not be able to reconnect again.
Same problem for me.
Some person have this problem other don't have this problem.
Maybe there is something common (in the configuration/ hardware/ or environment/ snapshot version)
Please if you have this problem reply so we can count how many person have this problem and compare.
For the other (not having the problem)
Do you use the 2.4g ?