Yeah, I saw it and eagerly flashed it yesterday but unfortunately it's the same behaviour in regards to DHCP not working and no access to the router with fixed IP either, no wireless network and so on. I just didn't have the time to post here.
If someone with UART access is following this thread, it would be great if you could flash 10-15-2024-r58568 and send the log.
Meanwhile, I've purged a previous log sent by di@mond of the spamming 'cannot open /dev/nvram' to see what else is going on and I can see more problems but I don't want to speculate much at this point. I'll just say that the 29 MTD partitions found have nothing to do with those on `src/linux/universal/linux-6.6/arch/arm64/boot/dts/qcom/ipq8174-mx4200.dtsi` and that there is a 'board data failed' error which you would imagine is a critical one. I have edited the partitions `ipq8174-mx4200.dtsi` for other stuff on OpenWRT and the kernel log will always match what you put on the DST file so that's odd going with my experience.
EDIT: Just to elaborate a bit more on the partitions problem. On the UART log provided by di@mond:
[ 1.061974] 29 cmdlinepart partitions found on MTD device qcom_nand.0
On OpenWRT:
[ 1.076760] 29 fixed-partitions partitions found on MTD device qcom_nand.0
Success at last. I've managed to boot DD-WRT 'tempering' with the U-boot environment variable partbootargs. Something I tried before but it was not going to work, I think, because of the issue with the nvram offset.
Since this is what di@mond's log says;
[ 1.061974] 29 cmdlinepart partitions found on MTD device qcom_nand.0
And I know cmdlinepart comes from the U-boot variable `partbootargs` for partition 1 and `partbootargs2` for partition 2, I flashed the OEM's firmware to partition 2 and OpenWRT to partition 1. From OpenWRT I set `partbootargs` to
Which are the partitions on `ipq8174-mx4200.dtsi` for DD-WRT. Then went back to the OEM and flashed factory-to-ddwrt.img.
So this time it worked because U-boot passed the partitions as they are expected. The problem is that the partitions passed by U-boot should be ignored and 'fixed-partitions' on the DTS used instead.
Can you pass this information to BrainSlayer please? I obviously can provide more info as required.
I don't think you would need every mtd listed in yours, but you got it working so who am I to say?
Quote:
So this time it worked because U-boot passed the partitions as they are expected. The problem is that the partitions passed by U-boot should be ignored and 'fixed-partitions' on the DTS used instead.
And this may be why you needed every partition listed in the partbootargs2 env. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
From what I can tell, OpenWRT didn't touch those. The DTS can append arguments to the cmdline but it's not changing partbootargs or partbootargs2. That's quite risky in my opinion because in principle you've got to restore them as they were to boot OEM. And that's done with mtd flashing directly to kernel or alt_kernel so I am almost 100% positive those are default values (on my model).
Either way, I still think that the issue at hand is that it should be ignored and 'fixed-partitions' used. That is what it's there for on the DTS. But I don't know the mechanics of how OpenWRT is doing it or if that's the correct approach to be honest.
It would help if someone else flashed the latest version to compare.
I'll try at some point to remove mtdparts=... altogether but as I said I think that's the default so it might fix my problem but it won't fix others'.
I don't think DD-WRT changes anything in the uboot variables. The partbootargs that I posted were captured from OEM the first time I connected serial to it. I also just compared them with DD-WRT flashed and they are unchanged. Sure, we are talking about two slightly different routers here, but the only differences are RAM and FLASH size, according to everything I have read anyway. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
If I remove mtdparts from partbootargs, DD-WRT, which is installed on partition 1, boots and the logs around partition change and it uses 'fixed-partitions'.
However, if I do it on partbootargs2, OEM which is installed on partition 2 doesn't boot. It's an indication that mtdparts was there all along and required but I need to run this test more carefully to confirm it's not something else at play and I am jumping to the wrong conclusion.
The question about why OpenWRT can ignore this would still remain and it'd be the way forward.
The without-mtdparts.txt looks more like my boot log. Except I do not have sysdiag and ddwrt is the last mtd partition. I have 30 partitions total whereas you have 31. Weird. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
the router boots normally. Furthermore, there are these U-boot environment variables that might have been used at some point to put partbootargs and partbootargs2 together:
All things considered, I am reasonably confident partbootargs and partbootargs2 include mtdparts and its long string by default at least on some MX4200v2. If DD-WRT can easily ignore it and use 'fixed-partitions' is another story.
@lexridge these devices have more differences than the community enthusiastic consensus would make you believe. It's possibly motivated by the understandable desire to get support for the MX4300 merged into OpenWRT, by inferring that if the MX4200 is supported, and the MX4300 is the same, it should be done. They've got different nand (size and model), RAM, MX4200 has bluetooth, different partition layouts, different U-boot environment variables it seems and other hacks that I can see on the PR that are needed to actually boot it. So, at some point, this argument that it's basically the same device doesn't hold water for me. It's a personal opinion for what it's worth it, and entirely debatable how many changes between two devices makes them different.
these devices have more differences than the community enthusiastic consensus would make you believe. It's possibly motivated by the understandable desire to get support for the MX4300 merged into OpenWRT, by inferring that if the MX4200 is supported, and the MX4300 is the same, it should be done. They've got different nand (size and model), RAM, MX4200 has bluetooth, different partition layouts, different U-boot environment variables it seems and other hacks that I can see on the PR that are needed to actually boot it. So, at some point, this argument that it's basically the same device doesn't hold water for me. It's a personal opinion for what it's worth it, and entirely debatable how many changes between two devices makes them different.
I cannot argue with that. Thanks for the information.
kernel-panic69 wrote:
So, you are going to discount that yours is an ISP-branded device that could have a modified u-boot? There IS always that factor. Without an actual non-branded v2 in hand, I can only speculate.
Also a very good point. @TopMandolin What happens if you flash the original ISP fw? Do the uboot variables change? It's a shame you cannot report your uboot version. Pretty sure you would need a serial connection for that. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
