Thanks for the suggestion. Unfortunately I have some specific packages on my build, so I didn't use yours. Instead I also pulled some of the changes from the 3Gv2 patch into my build, more specifically, some parameters on the DTS file.
I didn't touch the "ralink,group" on the pinctrl section because it didn't seem relevant (and anyway I don't really know what that part is for and the meaning of the different parameters), but changed some addresses and the SPI frequency.
Let's see how this goes. Already flashed my device with this new build and looking good so far, but too soon to see if it's more stable.
Should anyone be curious, here's a patch (to apply from openwrt/master lastest commit) with the changes I made to try merging Roger's patch and the 3Gv2 currently proposed patch:
If it looks good, @rogerpueyo you can use this in your repo Also, can you make a pull request for integrating the support on the official openwrt tree?
So far, so good, with uptime of about 2 days. For now just one minor hiccup on the IP camera connection to the NVR, of a few seconds (meanwhile I've also configured NVR to send emails when that happens, which gives me additional precision to detect failures), but no error messages on the kernel ring buffer of the router.
But I think I'll wait some more time until considering it a full success. I'll be happy when the uptime is of a few weeks with no video losses, like with the other camera on the other side of the house which is connected to other (mt7628) weaker AP
6 days of uptime and no kernel messages indicating errors. In terms of WiFi stability, not 100% but about 95% - still have some breaks now and then, of some seconds, but way less. Meanwhile I've also fine tuned some parameters (e.g. disabled short gi to try to improve communications across a wall), but that's more related to my environment that anything else.
So in my experience, the patch I referred has been performing better. Should anyone have issues, feel free to try it.
Hello my spi/uart usb Interface arrived. Opend the router it did not looked the pics (no SPI chip). With the uart connected i noticed that i dont have a R4A I have an R4 and from what I can read its a nand device.
I got access to CLI and uart. It had the 5 sec bootdelay from factory so problem accessing the CLI to enable uart.
I know this might be a bit of topic but how to compile the firmware for the R4, is it possible ? Can I use same image ?
Hi, thanks to this great contribution. I've purchased an Xiaomi 4A Gigabit edition and flashed the version from @rogerpueyo's branch. All is fine except that I can't install openvpn or wireguard (not even from the additional compiled ipk's) because of a kernel version being older that the required one.
I'm wondering if there's an easy way to upgrade the kernel only or should I get a latest snapshot and apply the same commit on it?
@Gingernut Thanks, I'll try it out at home. I actually did select the packages but for some reason I ended up with the normal snapshot build without additional changes, luci wasn't in there as well. Maybe my new try will have them included now. I didn't have to build openwrt image before so most probably I did something wrong there.
Nope didn't work. I even got the latest openwrt original master and applied the changes there. Both luci and openvpn are nowhere to be found on the image. It did compile the separate ipk versions but they are not included in the build. Installing them manually gives the same error. I must be doing something wrong with adding luci and openvpn in there.
ubuntu tftp using the service xinetd.
I think that the problem is my image, would be fine to get the @ rogerpueyo image to be sure that the procedure works.
hm, I've built my image yesterday and has kernel 4.14.143 for R3Gv2 (what is pretty much the same device), yours has 4.19.57, maybe its really your image has a problem.
Also, can you make a pull request for integrating the support on the official openwrt tree?
