Xiaomi mi wifi 3 support

Thanks! Installed NATCAP build 20180126. Will provide feedback in ~48 hours.

Be patient, will be fixed soon
https://github.com/openwrt/mt76/commit/3968dae910786852f5d1787459ae934c14a3294c

2 Likes

I finally had time to connect to the serial console. Seems like the kernel was somehow screwed.

U-Boot 1.1.3 (Apr 15 2016 - 17:46:32)

Board: Ralink APSoC DRAM:  128 MB
Power on memory test. Memory size= 128 MB...OK!
relocate_code Pointer at: 87fb8000
enable ephy clock...done. rf reg 29 = 5
SSC disabled.
!!! nand page size = 2048, addr len=4
..============================================
Ralink UBoot Version: 4.2.S.1
--------------------------------------------
ASIC 7620_MP (Port5<->None)
DRAM_CONF_FROM: Auto-detection
DRAM_TYPE: DDR2
DRAM component: 1024 Mbits
DRAM bus: 16 bit
Total memory: 128 MBytes
Flash component: NAND Flash
Date:Apr 15 2016  Time:17:46:32
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

 ##### The CPU freq = 580 MHZ ####
 estimate memory size =128 Mbytes

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   9: Load Boot Loader code then write to Flash via TFTP.
 0

3: System Boot system code via Flash.
Booting System 2
..ranand_erase_write: offs:40000, count:20000
.Done!
done
## Booting image at bc600000 ...
   Image Name:   MIPS OpenWrt Linux-4.9.70
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1363442 Bytes =  1.3 MB
   Load Address: 80000000
   Entry Point:  80000000
.....................   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
commandline uart_en=1 factory_mode=0 mem=128m
No initrd
## Transferring control to Linux (at address 80000000) ...
## Giving linux memsize in MB, 128

Starting kernel ...

The front LED is purple and i see no further output on console. What can i do to recover it?

Been a few days now. Have not noticed a single WiFi dropout! Thanks!

1 Like

Just set up as a repeater, i'm noticing some dropout from the client connection (61 dbm - 69 dbm reported in web ui)

A post was merged into an existing topic: Xiaomi WiFi Router 3G

Just finished recovering from LEDE...

It might just work, but not for my needs. I needed a DUAL band repeater (which it isn't yet) and flashed it with hopes I can make it work. Not long it pleased (until I ran iw list).. No support for WDS whatsoever, although LUCI states it switches mode and even config says 'option wds '1' '..

ptpt52
In case it can be something done about it, please draw some attention to this matter.
Also, the "wide" channel selection for CN (and others) works only in AP mode. Switching to anything else gives BIG limitations (20dBm for both 2.4GHz and 5GHz; also 2.4GHz misses channels 12 and 13). I've read that some time ago people changed some 'regulations' database before compilation, but then again, since LEDE those have been hidden somewhere deeper than just cldr folder. If by any chance You could fix this as well, please contact me, I have some details for the signal strength that I would like to implement.

After all this done, would gladly install LEDE. Untill then - PROMETHEUS does the best job so far.

Good Luck and looking forward to hearing from You all soon.

Regards,
Z1ldj1an

Dear all,

how can i go back to Stock from NETCAP ?
i tryed "fw_setenv flag_last_success 0" without success ......

Many thx

LuFi

Ok, I did a stupid thing. I try to merge the pulls of @ptpt52 to lede-17.01 branch not the master. https://bitbucket.org/shibajee/lede-source . Flashed it, now getting a constant boot loop with yellow led. Is there anything to do before getting a serial console ?

I'm having some issues with 5 GHz wifi. Can't get my pc connected with ac, just a at 54Mbps and with 2.4 Ghz n is just at 72Mbps.
Is it solvable in someways?

new version failed to connect to bandwidth to 2,4 gz, connected with no network
Please check fix mir3

I flashed the router as listed and it worked perfectly. Thank you!

There is a problem with mt76 and 7603
https://github.com/openwrt/mt76/issues/145

1 Like

Hi
I could install NATCAP but while trying to login I get "no supported authentication methods available (server send: publickey)" and via the website I also cannot login....

What step did I miss?
I did

mtd write natcap-kernel1 kernel1
mtd write natcap-rootfs0.bin rootfs0
nvram set flag_last_success=1
nvram commit
reboot

Thanks for help!

EDIT:

OK managed to get on it finally! :slight_smile: However now the whole system is running in Chinese ... I hope I can find a setting for that lol

Edit 2: OK i can login via Website but not via SSH :frowning:

EDIT. OK got that to work now too... Just Mesh ain't working yet :smiley:

1 Like

If you are interested, we have just begun to sell the Xiaomi Mi 3 router with the latest version of LEDE / Openwrt.
Xiaomi-Mi-Router-3-cz

1 Like

how to log in trhu ssh

I had to activate that but I in the mean time installed OpenMesh as Firmware anyway.
Also it seems you cannot currently install updates for that model - it ain’t finding one of the packages.gz files.

00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.087577] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.097027] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.106469] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.115912] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.125355] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.134799] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.144243] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.153686] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.163140] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.172593] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.182037] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.191492] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:35 2018 kern.err kernel: [  282.200942] ieee80211 phy1: rt2x
00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2        
Mon Feb 19 15:43:44 2018 kern.err kernel: [  285.114537] mtk_soc_eth 10100000
.ethernet eth0: transmit timed out                                           
Mon Feb 19 15:43:44 2018 kern.info kernel: [  285.120868] mtk_soc_eth 1010000
0.ethernet eth0: dma_cfg:80000065                                            
Mon Feb 19 15:43:44 2018 kern.info kernel: [  285.127031] mtk_soc_eth 1010000
0.ethernet eth0: tx_ring=0, base=06c57000, max=128, ctx=17, dtx=17, fdx=16, n
ext=17                                                                       
Mon Feb 19 15:43:44 2018 kern.info kernel: [  285.137613] mtk_soc_eth 1010000
0.ethernet eth0: rx_ring=0, base=05b6b000, max=128, calc=5, drx=6            
Mon Feb 19 15:43:54 2018 kern.err kernel: [  288.526425] mtk_soc_eth 10100000
.ethernet eth0: transmit timed out                                           
Mon Feb 19 15:43:54 2018 kern.info kernel: [  288.532754] mtk_soc_eth 1010000
0.ethernet eth0: dma_cfg:80000065                                            
Mon Feb 19 15:43:54 2018 kern.info kernel: [  288.538917] mtk_soc_eth 1010000
0.ethernet eth0: tx_ring=0, base=05b6b000, max=128, ctx=17, dtx=17, fdx=16, n
ext=17                                                                       
Mon Feb 19 15:43:54 2018 kern.info kernel: [  288.549498] mtk_soc_eth 1010000
0.ethernet eth0: rx_ring=0, base=06c57000, max=128, calc=1, drx=2            
Mon Feb 19 15:44:04 2018 kern.err kernel: [  291.944232] mtk_soc_eth 10100000
.ethernet eth0: transmit timed out                                           
Mon Feb 19 15:44:04 2018 kern.info kernel: [  291.950562] mtk_soc_eth 1010000
0.ethernet eth0: dma_cfg:80000065                                            
Mon Feb 19 15:44:04 2018 kern.info kernel: [  291.956731] mtk_soc_eth 1010000
0.ethernet eth0: tx_ring=0, base=06c57000, max=128, ctx=17, dtx=17, fdx=16, n
ext=17                                                                       
Mon Feb 19 15:44:04 2

Mir3

Here is my own firmware based on latest LEDE snapshot:
Xiaomi-Mi-Router-3-firmware

can you post the firmware sir...so that i can test it...