Problem is that probably I have some new hardware revision, where ethernet doesn't work with current openwrt .fip builds, so I can't tftp'd system to router via ethernet.
but you should be able to do it with stock fip, right? Also you can boot with uart only(with proper uboot).
Stock you mean that the one that router was shipped with? Unfortunately I don't have any copy.
Can you give me an idea how I can boot with uart only? Only thing I can do is to use mtk_uartboot to boot into .fip, then loadb 0x46000000 and send kernel with c-kermit. There I have access to basic openwrt without any drivers that I could use.
you should have asked others for stock fip from new revision...
Do you have stock kernel? We can fix the problem after looking into stock DTS from your router.
1 Like
@harjasqs
can you upload stock fip and kernel from device with ethernet problem?
1 Like
i think it's another hardware change by xiaomi
i experienced the same thing, downgraded an ax3000t shipped with 1.0.84 and lost all ethernet ports
xaiomi still only pushing 1.0.64 firmware via gui admin update, so until 1.0.84 (or a newer ROM) is made available then our borked devices are restricted to wireless repeaters
there is one thing that worries me, when trying to backup the nand flash i get 12 ECCs on one chip, probably just firmware related, seems unlikely that we get the same behaviour if they were individual hardware faults
tftp works on mine, it also works as a switch - but tcp/ip is completely borked, wont serve or allocate IPs on any ethernet port on any version of firmware oem, openwrt, immortal even winbond builds
Xiaomi AX3000T version 1.0.84 was downgraded to 1.0.47, and the wired network port became a switch. It was so disgusting that U-Boot could not access it.
After the exchange, it will be version 1.0.47, which is in place at once and is much more comfortable.
I don’t know what mechanism was added in version 1.0.84 to prevent downgrading.
I know that CPU usage might be lower with hw offloading, but why is the max bandwidth achieved slightly different? Does hw offloading introduce any kind of bottleneck?
I recently reverted to the stock firmware, and without any specific configuration, I was able to achieve 947 Mbps using iperf3 between two wired PCs (just like in OpenWRT with sw offloading).
Maybe new ethernet switch.
Guys, someone who have got that new one, could you please take a photo of the chips, board. It's strange that they haven't announced anything.
A difference of 1%, I would write off as benchmark to benchmark variation since there are many factors which could influence the results (time of day, the traffic of devices on the network, etc).
Stock firmware uses an older version of OpenWRT with vendor things hacked in. Since Xiaomi engineers have access to data sheets and such, stock firmware will always be hard to beat performance wise since things have to be reverse engineered by the FOSS community.
1 Like
Yeah, I can upload the kernel- just not sure how to. I ended up keeping the AX3000T and am using it as a wireless repeater- as Fangio10 rather accurately said, because Aliexpress gave me 70 percent off my order. For 15 USD its not a bad repeater at all.
I think it is probably a new hardware revision- because after all the ethernet did work with TFFP for me.
I will try to upload the stock kernel next weekend , around Sep 8th but someone will have to guide me on how to do it. (Currently running 1.0.47- I can update to 1.0.84 but will lose SSH access so guessing I'll need to do UART shenanigans?)
@roblad I'm happy to take pictures today though, just give me a couple of hours
In fact, switching the pins and making it match TX/TX and RX/RX doesn't echo in PuTTY.
I've ordered new adapters in hope to solve this .. but still, it's very weird that I'm unable to nagivate through the uboot menu.
Any way to go back to the factory fw, taking into account that I can't connect to the router with SSH anymore ?
Sorry for the inconvenience.
The values that I mentioned are not from a single test; they are an average from about 50 tests conducted on different days, in various scenarios, with different cables, computers, etc.
My assumptions and doubts are intended to help me gain an understanding.
Anyway, I appreciate your answers to this foolish question. Thanks
heres what dmesg is reporting when trying to bring up ethernet ports
[ 2.350836] mt7530-mdio mdio-bus:1f: reset timeout
[ 2.355662] mt7530-mdio: probe of mdio-bus:1f failed with error -110
Sorry, I do not know.
1 Like
I suspect the difference may lie in the u-boot image, since I know the units shipping with 1.0.84 (and 1.0.85, which I don't think is in the wild yet) have fresh u-boot images as well. (Build dates of May 29 and later if I recall)
1 Like
Use the xaoimi recovery tool
As long as you haven’t replaced the uboot their tool will recover back to stock
1 Like