Posted: Wed Jun 20, 2018 19:48 Post subject: Gonna sell this
I'm pretty sure I'm going to sell this stupid r8000p router. It's just collecting dust on my floor. The default Netgear firmware is just awful and unusable. No DD-WRT, so I just need to send it back to Netgear. It's a total joke.
I know this doesn't fix the massive problems with the firmware, but has anyone that owns the router tried plugging the router into a wemo plug or something and put it on a schedule to turn the power off for like 5 min at 3am or some random time when it isn't typically being used? Just curious if the daily reset will stop the issues of having to manually restart the router.
My hope is still there but I must say that it really feels that I'm alone in this dream right now.
I truly hope for happy news before the end of this year.
I do understand that BrainSlayer has "crazy much" on his to do list. We shall all respect him for his time and effort that he's putting down in the developing of DD-WRT.
Thank you BS!!!
Since I'm the last man standing in this thread I'm wondering if this might be a tiny step forward
From MyOpenRouter
Quote:
Ok so the quick explanation is that the R8000P is a more powerful router than the R8000, hence the 1.8ghz cpu on the R8000P vs the 1.0 ghz cpu on the R8000, which means that porting a firmware to it would take a bit on time. Now since both router use the same internal configuration what you could do is download Kong’s R8000, open the file with an Hex editor and change the board id to match the R8000P and that would allow you to try DD WRT for the R8000 on your R8000P. Let me know if you need anymore help.
Not an expert, but I always get the job done and look good doing it.
Since I'm the last man standing in this thread I'm wondering if this might be a tiny step forward
From MyOpenRouter
Quote:
Ok so the quick explanation is that the R8000P is a more powerful router than the R8000, hence the 1.8ghz cpu on the R8000P vs the 1.0 ghz cpu on the R8000, which means that porting a firmware to it would take a bit on time. Now since both router use the same internal configuration what you could do is download Kong’s R8000, open the file with an Hex editor and change the board id to match the R8000P and that would allow you to try DD WRT for the R8000 on your R8000P. Let me know if you need anymore help.
Not an expert, but I always get the job done and look good doing it.
Not an expert, but I decided to do something to make my R7900P a better router.
I got my R7900P from Costco last Black Friday, maybe I'm the lucky one, it is now running the latest stock firmware from Netgear, and pretty stable. I'm pretty happy with its performance.
I think a DD-WRT/OpenWRT/Tomato firmware can make it even better.
The first step is to compile the stock firmware published by Netgear and make it working.
BTW, the Netgear source codes really sucks, it's kind of a miracle they can make it stable on my router
......
/opt/toolchains//crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22-binutils-2.25/usr/bin/arm-buildroot-linux-gnueabi-strip: '/workspace/r7900p/r7900p/targets/R8000P/fs/bin/wget-device': No such file
/opt/toolchains//crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22-binutils-2.25/usr/bin/arm-buildroot-linux-gnueabi-strip:/workspace/r7900p/r7900p/targets/R8000P/fs/lib/ld-linux-aarch64.so.1: File format not recognized
/opt/toolchains//crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22-binutils-2.25/usr/bin/arm-buildroot-linux-gnueabi-strip:/workspace/r7900p/r7900p/targets/R8000P/fs/lib/aarch64/libc.so.6: File format not recognized
/opt/toolchains//crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22-binutils-2.25/usr/bin/arm-buildroot-linux-gnueabi-strip:/workspace/r7900p/r7900p/targets/R8000P/fs/lib/aarch64/libnss_dns.so.2: File format not recognized
/opt/toolchains//crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22-binutils-2.25/usr/bin/arm-buildroot-linux-gnueabi-strip:/workspace/r7900p/r7900p/targets/R8000P/fs/lib/aarch64/libnss_files.so.2: File format not recognized
/opt/toolchains//crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22-binutils-2.25/usr/bin/arm-buildroot-linux-gnueabi-strip:/workspace/r7900p/r7900p/targets/R8000P/fs/lib/aarch64/libresolv.so.2: File format not recognized
cd /workspace/r7900p/r7900p/targets; /workspace/r7900p/r7900p/hostTools/local_install/fakeroot -l /workspace/r7900p/r7900p/hostTools/local_install/lib/libfakeroot.so -f /workspace/r7900p/r7900p/hostTools/local_install/faked ./buildFS_RD
/bin/sh: /workspace/r7900p/r7900p/hostTools/local_install/fakeroot: Permission denied
Makefile:1319: recipe for target 'buildimage' failed
make: *** [buildimage] Error 126
Very close to complete the stock firmware building ...
Almost final, will try to fix this fakeroot permission issue tomorrow ...
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Wed Sep 05, 2018 9:03 Post subject:
OEM Netgear firmware ... oh, mmmmhmmmm. Problematic doesn't begin to describe it. Of course, a lot of more recent OEM firmwares are a little temperamental. For the record, "IamDaveG" is NOT my alter-ego, but I wish you luck.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Wed Sep 05, 2018 20:11 Post subject:
To get support, they'll need serial output and some other info, anyway.... might as well set it up for serial recovery so you can get the serial console output....
To get support, they'll need serial output and some other info, anyway.... might as well set it up for serial recovery so you can get the serial console output....
Thanks, buddy. Did find a video on Youtube about opening the unit, and also some of the CFE source codes in Asus Merlin's repository, which could be a good reference.