Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Fri Apr 02, 2021 14:20 Post subject:
Sorry, have been busy lately, but I did update BrainSlayer on the status of this. I haven't checked to see if any commits have been made since yesterday yet. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Apr 02, 2021 15:04 Post subject:
StillBlue wrote:
r46220 Alpha and Beta are both the same
MD5 Hash
8EA9C790515DAC050B541595CDB9B6FA
I have tried adding 'insmod ext2' at the start of my startup script, but no difference, still not showing the card details in the GUI and not mounting.
r46220 does contain ext2. so whats the point? _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Hi,
In 46177 when I reported the issue, I found that if I extracted the firmware with the Firmware Modification Kit, added ext2.o into /lib/modules/2.4.37/ and then rebuilt it, the image then worked fine with the SD card mod.
Somewhere in the revisions since, another issue has occurred, presumably either or all of
Now in 46220 and 46239 although the ext2.o module is now in /lib/modules/2.4.37, something else has now caused the card not to mount (now card info is not visible in the GUI, even though it was in 46177, even before adding ext2.o into /lib/modules/2.4.37/
The original fault appears to have just been the lack of the module, and one of the new revisions appears to have broken something else.
Please let me know if you need any logs etc, I am just setting up an environment so I can try and narrow down which revision has caused the new issue.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Fri Apr 02, 2021 17:46 Post subject:
Have you tried using 46239 without your startup script and then adding to it until something breaks? Or does this mod not auto-mount the SD card automagically? _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I have tried it after erasing the NVRam, and there is nothing. The Card Info doesn't show from the moment you enable the MMC, and that is as far as you get, no auto mount, not sign of it even setting up MMC in the logs I have previously uploaded.
I have also tried manually putting in the GPIO values incase it was that. Still no joy.
In the first set of serial logs I uploaded, you can see the MMC get recognised and the GPIO details are filled in.
In the versions after 46177, this no longer happens.
Thanks again for all the help with this.
I am still setting up an environment at the moment with the intent of hopefully being able to work out which revision added the new issue. Unfortunately my computer is slower than the speed of dark, so it's taking a while building the necessaries.
I'll be honest, I have ran out of time at the moment to do much more with this.
For what ever reason, I am finding that the toolchains currently available appear to be too out of date, I attempted to build my own, but no joy (the speed of my computer is not helping), and unfortunately I do not seem to be able to see the correct toolchain available anywhere already built. DD-WRT certainly seems to be hard to compile to test.
As I have stated here, the original problem was nothing more than the ext2.o module missing. The other revisions made, have caused a problem that wasn't there before.
If I find more time I will have another go at building the toolchain as it appears the ones used are not available.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sun Apr 04, 2021 22:15 Post subject:
I guess I forgot to ask, did you enable the mmc mod, save, add insmod ext2 to startup, save, and then reboot or? Seems like I figure the implied questions are obvious _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
To give you an idea of how slow my computer is, it took 12 hours to compile GCC 10.2.0
I think in all honesty I am fighting a loosing battle trying to narrow down which of a few lines of code caused the new issue from this end.
That is indeed rather slow I have a 6 core Zen 3600X so not state of the art and even using virtual box it gets the job done for my R6400 in one and a half hour
T7800 Core 2 Duo. Been a long time since I have needed to use a computer in anger as you can tell.
kernel-panic69 wrote:
I guess I forgot to ask, did you enable the mmc mod, save, add insmod ext2 to startup, save, and then reboot or? Seems like I figure the implied questions are obvious
Yes, yes and yes. Unfortunately the current revisions to fix the issue have put the ext2.o module back in, which is obviously good, but have broken something else.
Currently the MMC mod still only works without modification to the firmware in versions up to 19342, and with the ext2.o added to /lib/modules/2.4.37/ in versions up to 46177. Since then one of the revisions has broken something else.