sel
8926
I tried from openwrt firmware
in my case from robi's openwrt firmware
Ansuel
8928
well we need to understand if it's possible to use the same instructions from stock and then we can merge the changes in robi repo
Well, fact for me is. I've reverted to stock after 1st brick. Flashed xioami firmware 2 times to make sure everything is in right place and did short setup. Gained ssh access and flashed the ubi image. For dimfishs ubi image I've got a brick (was not able to flash 2nd partition) and for ansuels image it booted directly into stock firmware after 1st flash (no brick). I did this two times. More I cannot say about this. I cannot say whats going on because my unit is still closed therefor no uart.
And I know the difference between nvram and fw_printenv/setenv well.
Beside that there is an error in the instruction manual what I was using:
_https://github.com/Ansuel/openwrt/commit/4b22dff58a0aabbd68c4102c05e2c9f0bf1c9121
- use the artifact nand-initramfs-factory.ubi and flash the bin from the
running system using the following steps: (thanks dimfish for the
following instructions)
- Upload the ubi image to /tmp on the router
- Find active rootfs
For stock fw: nvram get flag_last_success
For openwrt fw: nvram get flag_last_success
3.1 If point 2 result is "0"
For openwrt it has to be ... oO . 
EDIT: Just to make clear. It might be that i still did sth. wrong because it was late and I was tired already. So I would encourage others to prove that I'm wrong and failed. 
I'm testing this because I want this expansion happen and in-tree. I will give this another try comming weekend. 
1 Like
xabolcs
8930
As @anon54515283 wrote it has a typo!
dimfish's instructions doesn't have that typo in step 2.
@dimfish, @Ansuel: how about setting (to be sure) flag_ota_reboot to 0 too (with the other flag_ env variables) in the installing section and in platform_do_upgrade() in target/linux/ipq807x/base-files/lib/upgrade/platform.sh?
If flag_ota_reboot is 1 then uboot tries to do an A/B switch.
I use (only) this flag when I install robimarko's images initially.
Interesting.
While trying again: please note down all flag_ environment parameters! I'm interested in flag_ota_reboot and others too.
It's very interesting to me that the device rebooted to stock firmware after the first (initramfs-factory.ubi) flash.
1 Like
I did this with dimfishs Version 2 times from Stock firmware succesfully.
Question for me is: Is it possible to upgrade from dimfishs Version to your version? Both use the same partition layout as I understand it.
Ansuel
8932
if they are the same partition layout yes sysupgrade should work without any problem
then can't understand why @xabolcs can't manage to update o.O
dimfish
8933
We had only 1 question here - is new @Ansuel method for creating initramfs ubi workng fine?
And anwser is definitely yes. That's all.
I've already built 4 versions with extended partitions and more than 20 people already using without problem on ax3600 and ax6.
Maybe colorful instructions are more user friendly? See on 4pda forum...
2 Likes
Ansuel
8934
well yes user will use wiki to migrate and not the commit... the commit is really just for devs
1 Like
Could someone give a kmod-tun to the image robimark? I can't install vpn on xiaomi ax3600. I mean a file ready for the OpenWrt installation.
This would be great on the AX3600 Page...
1 Like
equid0x
8937
I reported a similar issue earlier on... I think it's physical layer issue. I was having the problem with a hard wired Roku TV and have since found the cable might be a little flakey.
equid0x
8938
It's easy to change the governor... Just look up standard Linux instructions they work here. I toyed with the governor myself and didn't see any notable performance increases for my use case... Might make a difference on something that requires CPU but I saw no difference on strongswan VPN but my uplink is slow.
I agree on this. This device has issues with certain cables/devices. I had issues in the past with an older 100MB switch (sorted it out) and with some older cat5 cables (nothing used on this device atm).
The big but here is I have two AX3600 and on both I had the same error. And robimarko saw the error later also. And I didn't have the issue before and after revert.
But I do not want to rule out that it is an pyhsical layer issue. As soon robimarko is integrating this patches again I will test it again.
Well, I was thinking about the whole thing also. What I did wrong. What could be the cause. Do I have to reset device before I start flashing again. And so on. I don't know if others did modify bdata also? Could this be the cause? As I said I will test this again with stock fw. Maybe today in the afternoon already.
regarding changing the ax3600 device to one partition... any plans to follow suit with the qnap + dynalink ? as in the ax3600 the additonal partitions are unusable happy to help with testing
Ansuel
8943
why? other device have acceptable rootfs size AFAIK
RobertP
8944
Well ... I'd say on AX9000 the situation is very similar to what was on ax3600 before changes
# df -h
Filesystem Size Used Available Use% Mounted on
mtd:ubi_rootfs 35.0M 35.0M 0 100% /rom
tmpfs 391.9M 5.8M 386.0M 1% /tmp
/dev/ubi0_2 5.5M 76.0K 5.1M 1% /overlay
overlayfs:/overlay 5.5M 76.0K 5.1M 1% /
ubi1_0 42.7M 16.2M 24.2M 40% /data
ubi1_0 42.7M 16.2M 24.2M 40% /userdisk
overlayfs:/overlay 5.5M 76.0K 5.1M 1% /userdisk/data
ubi1_0 42.7M 16.2M 24.2M 40% /etc
ubi1_0 42.7M 16.2M 24.2M 40% /ini
tmpfs 512.0K 4.0K 508.0K 1% /dev
root@XiaoQiang:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "0:SBL1"
mtd1: 00100000 00020000 "0:MIBIB"
mtd2: 00080000 00020000 "0:BOOTCONFIG"
mtd3: 00080000 00020000 "0:BOOTCONFIG1"
mtd4: 00300000 00020000 "0:QSEE"
mtd5: 00300000 00020000 "0:QSEE_1"
mtd6: 00080000 00020000 "0:DEVCFG"
mtd7: 00080000 00020000 "0:DEVCFG_1"
mtd8: 00080000 00020000 "0:APDP"
mtd9: 00080000 00020000 "0:APDP_1"
mtd10: 00080000 00020000 "0:RPM"
mtd11: 00080000 00020000 "0:RPM_1"
mtd12: 00080000 00020000 "0:CDT"
mtd13: 00080000 00020000 "0:CDT_1"
mtd14: 00080000 00020000 "0:APPSBLENV"
mtd15: 00100000 00020000 "0:APPSBL"
mtd16: 00100000 00020000 "0:APPSBL_1"
mtd17: 00080000 00020000 "0:ART"
mtd18: 00080000 00020000 "bdata"
mtd19: 00080000 00020000 "crash"
mtd20: 00080000 00020000 "crash_syslog"
mtd21: 03800000 00020000 "rootfs"
mtd22: 03800000 00020000 "rootfs_1"
mtd23: 00100000 00020000 "cfg_bak"
mtd24: 07d80000 00020000 "overlay"
mtd25: 005ef000 0001f000 "kernel"
mtd26: 0231e000 0001f000 "ubi_rootfs"
mtd27: 007df000 0001f000 "rootfs_data"
mtd28: 03013000 0001f000 "data"
The total flash size is 256M...
thx @robertP here's the dynalink
Filesystem Size Used Available Use% Mounted on
/dev/root 13.0M 13.0M 0 100% /rom
tmpfs 434.2M 3.5M 430.7M 1% /tmp
/dev/ubi0_2 63.7M 484.0K 60.0M 1% /overlay
overlayfs:/overlay 63.7M 484.0K 60.0M 1% /
tmpfs 512.0K 0 512.0K 0% /dev
dev: size erasesize name
mtd0: 00100000 00020000 "0:sbl1"
mtd1: 00100000 00020000 "0:mibib"
mtd2: 00080000 00020000 "0:bootconfig"
mtd3: 00080000 00020000 "0:bootconfig1"
mtd4: 00300000 00020000 "0:qsee"
mtd5: 00300000 00020000 "0:qsee_1"
mtd6: 00080000 00020000 "0:devcfg"
mtd7: 00080000 00020000 "0:devcfg_1"
mtd8: 00080000 00020000 "0:apdp"
mtd9: 00080000 00020000 "0:apdp_1"
mtd10: 00080000 00020000 "0:rpm"
mtd11: 00080000 00020000 "0:rpm_1"
mtd12: 00080000 00020000 "0:cdt"
mtd13: 00080000 00020000 "0:cdt_1"
mtd14: 00080000 00020000 "0:appsblenv"
mtd15: 00100000 00020000 "0:appsbl"
mtd16: 00100000 00020000 "0:appsbl_1"
mtd17: 00080000 00020000 "0:art"
mtd18: 06100000 00020000 "rootfs"
mtd19: 00900000 00020000 "0:wififw"
mtd20: 06100000 00020000 "rootfs_1"
mtd21: 00900000 00020000 "0:wififw_1"
mtd22: 01600000 00020000 "ubifs"
mtd23: 00080000 00020000 "0:ethphyfw"
mtd24: 00280000 00020000 "certificate"
