Nighthawk X8 R8500 AC5300 router available $400 msrp.

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... , 15, 16, 17  Next
Author Message
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Thu May 04, 2017 5:32    Post subject: Reply with quote
gogoroute wrote:
But why I can't use ipkg or opkg in shell :

root@DD-WRT:/jffs# ipkg
-sh: ipkg: not found
root@DD-WRT:/jffs# opkg
-sh: opkg: not found
root@DD-WRT:/jffs#

Does there some docs of ddwrt-v3.0 ipkg or opkg description? I can't find in wiki. Thx.


IPKG is not supported anymore and opkg is available on my builds after you ran the preperation script "bootstrap"

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Sponsor
gogoroute
DD-WRT Novice


Joined: 22 Jan 2017
Posts: 25

PostPosted: Thu May 04, 2017 7:02    Post subject: Reply with quote
<Kong> wrote:
gogoroute wrote:
But why I can't use ipkg or opkg in shell :

root@DD-WRT:/jffs# ipkg
-sh: ipkg: not found
root@DD-WRT:/jffs# opkg
-sh: opkg: not found
root@DD-WRT:/jffs#

Does there some docs of ddwrt-v3.0 ipkg or opkg description? I can't find in wiki. Thx.


IPKG is not supported anymore and opkg is available on my builds after you ran the preperation script "bootstrap"


Thx @Kong! got it.
Does we must mount a usb drive to /opt or other dir to run bootstrap.
Thanks for Ur time.
gogoroute
DD-WRT Novice


Joined: 22 Jan 2017
Posts: 25

PostPosted: Thu May 04, 2017 7:14    Post subject: Reply with quote
<Kong> wrote:
gogoroute wrote:
But why I can't use ipkg or opkg in shell :

root@DD-WRT:/jffs# ipkg
-sh: ipkg: not found
root@DD-WRT:/jffs# opkg
-sh: opkg: not found
root@DD-WRT:/jffs#

Does there some docs of ddwrt-v3.0 ipkg or opkg description? I can't find in wiki. Thx.


IPKG is not supported anymore and opkg is available on my builds after you ran the preperation script "bootstrap"


Got a way to run bootstrap:


mkdir /jffs/opt
mount -o bind /jffs/opt /opt

Then I got this;

root@DD-WRT:/jffs# bootstrap
Bootstrap is checking prerequisites...

USB automounter is enabled.
Found a valid partition: /opt.

Proceed with download and install of opkg? (y/n) [default=n]:
y
Connecting to www.desipro.de (212.227.247.157:80)
wget: server returned error: HTTP/1.1 403 Forbidden
Connecting to www.desipro.de (212.227.247.157:80)
wget: server returned error: HTTP/1.1 403 Forbidden
Error opening signature file opkg.ipk.sig
1995932864:error:02001002:lib(2):func(1):reason(2):NA:0:fopen('opkg.ipk.sig','rb')
1995932864:error:2006D080:lib(32):func(109):reason(128):NA:0:
Error: Signature does not match.
djosesolis
DD-WRT Novice


Joined: 02 Feb 2017
Posts: 11

PostPosted: Fri Nov 10, 2017 5:59    Post subject: Reply with quote
After many, many months of waiting. My R8500 is finally working with the latest firmware by <Kong>
DD-WRT Kong Mod for NETGEAR R8500 (2017-11-01 CHK)
Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy
Thank you so much Kong, hope future updates also work for mine.
Officially the only working versions for mine are:
K3_R8500_17-Feb-2016.chk
Nov-01-2017-dd-wrt.K3_R8500.chk (KONG)
ilkinandr92
DD-WRT Novice


Joined: 12 Nov 2017
Posts: 4

PostPosted: Tue Nov 14, 2017 1:47    Post subject: Reply with quote
Hi guys, im thinking of getting R8500 and was wondering if MP2 models work with DDWRT now ?
dance85
DD-WRT User


Joined: 02 Jun 2017
Posts: 188

PostPosted: Wed Nov 29, 2017 18:15    Post subject: Reply with quote
Guys but do you know if anyone is still following the problems that the R8500 has? not much talk. Why? is it not widespread?
sandaja
DD-WRT Novice


Joined: 14 Jan 2013
Posts: 5

PostPosted: Mon Dec 18, 2017 3:23    Post subject: R8500 boot loop MP2 242 12473-02 Reply with quote
Probably beating a dead horse but I'll give it one last try. Dreaded boot loop for netgear R8500. tried a number of netgear FW's including earliest version R8500-V1.0.0.28_1.0.15 and most current R8500-V1.0.2.106_1.0.85. All go thru an extended boot loop cycle that does eventually stop. I've also tried the latest BS and K3 DD wwrt versions - the former appears to lock the system up while the latter just loops.

K3 is reported to work on variant -03 but alas i have -02. For grins I've attached the boots for netgear and K3 as well as nvram show results.



NvramShow2.txt
 Description:

Download
 Filename:  NvramShow2.txt
 Filesize:  47.89 KB
 Downloaded:  954 Time(s)


KongNov2017_boot.txt
 Description:

Download
 Filename:  KongNov2017_boot.txt
 Filesize:  97.87 KB
 Downloaded:  780 Time(s)


TFTPD_load.txt
 Description:

Download
 Filename:  TFTPD_load.txt
 Filesize:  13.85 KB
 Downloaded:  826 Time(s)

skyblaster
DD-WRT Novice


Joined: 30 Jan 2018
Posts: 1

PostPosted: Tue Jan 30, 2018 3:44    Post subject: Reply with quote
A good number of these units are being sold on eBay "as is". I've been successful in recycling improperly flashed routers in the past, so took a chance and bought one for under $50. This R8500 v1 is by far the hottest router I've ever owned and fear it is damaged beyond repair.

Thanks to an old post here, I have the 2.4GHz radio working under firmware V1.0.0.42_1.0.23, but have been unable to get the 5GHz radios to work.

Has anyone had any success fixing these defective units? I don't have a bootlog, but if I remember correctly it almost looks like the PCI-E switch is not being detected or not detecting the 5GHz radios.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Tue Jan 30, 2018 10:35    Post subject: Reply with quote
skyblaster wrote:
A good number of these units are being sold on eBay "as is". I've been successful in recycling improperly flashed routers in the past, so took a chance and bought one for under $50. This R8500 v1 is by far the hottest router I've ever owned and fear it is damaged beyond repair.

Thanks to an old post here, I have the 2.4GHz radio working under firmware V1.0.0.42_1.0.23, but have been unable to get the 5GHz radios to work.

Has anyone had any success fixing these defective units? I don't have a bootlog, but if I remember correctly it almost looks like the PCI-E switch is not being detected or not detecting the 5GHz radios.


I've bought about 5 or 6 in similar condition. Even with serial logs and kong's help, I wasn't able to fix any.

_________________
I am far from a guru, I'm barely a novice.
brianguild
DD-WRT Novice


Joined: 24 Apr 2011
Posts: 3

PostPosted: Thu Feb 01, 2018 19:24    Post subject: Reply with quote
Hey there R8500 users. Any word when or if the Kong builds will fix the issues where the port assignments are not visible in the GUI? For example, Port 5/6 not visible.

Also, any progress on Link Aggregation 802.3ad LACP for the Kong builds? This feature seems to be in the code, but not entirely working in the GUI.
black6spdz
DD-WRT User


Joined: 10 May 2007
Posts: 99

PostPosted: Wed Mar 21, 2018 0:02    Post subject: Reply with quote
maybe onto something as for the r8500's with reboot isues.. I just flashed the latest March build and what I have noticed is that it reboots when connecting to wifi.. so I tried each radio one at a time to see if it was isolated to just one.. what I found is that connecting to the 2.4G WL1 radio is fine, but when I connect to either of the 5G "WL0,2" it instantlay reboots. Wondering if it was a complete crash or something semi graceful I opened it up and connected to the serial port. Here is what it shows when connecting to one of those 5G radios before a reboot:

Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = 80004000
[00000000] *pgd=00000000
Internal error: Oops - BUG: 80000007 [#1] SMP ARM
Modules linked in: shortcut_fe usb_storage sr_mod cdrom sd_mod scsi_mod xhci_plat_hcd xhci_pci xhci_hcd ohci_pci ohci_hcd ehci_pci ehci_hcd usbcore usb_common dhd wl(P) igs(P) emf(P) switch_robo switch_core et(P)
CPU: 0 PID: 317 Comm: kworker/0:1 Tainted: P 4.4.120 #2690
Hardware name: Northstar Prototype
Workqueue: events _254 [dhd]
task: 87be8000 ti: 87bc0000 task.ti: 87bc0000
PC is at 0x0
LR is at _939+0x6c/0xa8 [dhd]
pc : [<00000000>] lr : [<7f45fcac>] psr: 80000013
sp : 87bc1e70 ip : 80440dc0 fp : 87bc1ea4
r10: 00000000 r9 : 00000004 r8 : 00000000
r7 : 00000000 r6 : 87ab9700 r5 : 00000000 r4 : ffffe000
r3 : 87bc1e70 r2 : 00000004 r1 : 87212000 r0 : 87ab9700
Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 10c5387d Table: 0398404a DAC: 00000055
Process kworker/0:1 (pid: 317, stack limit = 0x87bc0190)
Stack: (0x87bc1e70 to 0x87bc2000)
1e60: 00000000 00000000 8651c240 871ed400
1e80: 86395600 873bc000 a0000013 00000000 00000000 8050ba84 87bc1ec4 87bc1ea8
1ea0: 7f45fd24 7f45fc4c 86395620 86395600 0000000c a0000013 87bc1ef4 87bc1ec8
1ec0: 7f461db8 7f45fcf4 87bc1f0c 804f1d08 871ed400 7f45fce8 86395600 87be5700
1ee0: 86bd6480 86bdbe00 87bc1f24 87bc1ef8 8004d3c8 7f461d14 00000000 8050ba84
1f00: 87be5700 86bd6480 86bd6480 87be5718 86bd6494 00000000 87bc1f5c 87bc1f28
1f20: 8004e4e0 8004d220 804fe100 87bc0000 00000000 00000000 87bd7d40 87be5700
1f40: 8004e2e0 00000000 00000000 00000000 87bc1fac 87bc1f60 800527c4 8004e2ec
1f60: 87bc1f8c 00000000 8003bc84 87be5700 00000000 00000000 87bc1f78 87bc1f78
1f80: 00000000 00000000 87bc1f88 87bc1f88 87bd7d40 800526cc 00000000 00000000
1fa0: 00000000 87bc1fb0 80009600 800526d8 00000000 00000000 00000000 00000000
1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 87bc1ff4 00000000
Backtrace:
[<7f45fc40>] (_939 [dhd]) from [<7f45fd24>] (_336+0x3c/0xfc [dhd])
r10:8050ba84 r9:00000000 r8:00000000 r7:a0000013 r6:873bc000 r5:86395600
r4:871ed400
[<7f45fce8>] (_336 [dhd]) from [<7f461db8>] (_254+0xb0/0xbc [dhd])
r7:a0000013 r6:0000000c r5:86395600 r4:86395620
[<7f461d08>] (_254 [dhd]) from [<8004d3c8>] (process_one_work+0x1b4/0x2d8)
r7:86bdbe00 r6:86bd6480 r5:87be5700 r4:86395600
[<8004d214>] (process_one_work) from [<8004e4e0>] (worker_thread+0x200/0x3e4)
r9:00000000 r8:86bd6494 r7:87be5718 r6:86bd6480 r5:86bd6480 r4:87be5700
[<8004e2e0>] (worker_thread) from [<800527c4>] (kthread+0xf8/0x100)
r10:00000000 r9:00000000 r8:00000000 r7:8004e2e0 r6:87be5700 r5:87bd7d40
r4:00000000
[<800526cc>] (kthread) from [<80009600>] (ret_from_fork+0x14/0x34)
r7:00000000 r6:00000000 r5:800526cc r4:87bd7d40
Code: bad PC value
---[ end trace 5c61bf2818e07ae4 ]---
Kernel panic - not syncing: Fatal exception
CPU1: stopping
CPU: 1 PID: 0 Comm: swapper/1 Tainted: P D 4.4.120 #2690
Hardware name: Northstar Prototype
Backtrace:
[<8001b950>] (dump_backtrace) from [<8001bbd8>] (show_stack+0x18/0x1c)
r7:87853f58 r6:60000193 r5:00000000 r4:80510da0
[<8001bbc0>] (show_stack) from [<80163db4>] (dump_stack+0x8c/0xa0)
[<80163d28>] (dump_stack) from [<8001d754>] (handle_IPI+0x110/0x1a8)
r7:87853f58 r6:00000001 r5:00000000 r4:805231a0
[<8001d644>] (handle_IPI) from [<80009394>] (gic_handle_irq+0x78/0x7c)
r7:b0100100 r6:87853f58 r5:b010010c r4:804ffb1c
[<8000931c>] (gic_handle_irq) from [<80009ea0>] (__irq_svc+0x40/0x54)
Exception stack(0x87853f58 to 0x87853fa0)
3f40: 86bdf248 00000000
3f60: 0003beb2 8000a9c0 87852000 804ff8e0 80432868 804eb224 87853fc8 413fc090
3f80: 00000000 87853fb4 87853fb8 87853fa8 80019564 80019568 60000013 ffffffff
r9:413fc090 r8:87853fc8 r7:87853f8c r6:ffffffff r5:60000013 r4:80019568
[<8001952c>] (arch_cpu_idle) from [<8006c2d4>] (default_idle_call+0x30/0x34)
[<8006c2a4>] (default_idle_call) from [<8006c3e0>] (cpu_startup_entry+0x108/0x13c)
[<8006c2d8>] (cpu_startup_entry) from [<8001d40c>] (secondary_start_kernel+0x150/0x158)
r7:80523180 r4:8050d920
[<8001d2bc>] (secondary_start_kernel) from [<00009428>] (0x9428)
r5:00000055 r4:0782c06a
Rebooting in 10 seconds..

_________________
DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n
labo
DD-WRT Guru


Joined: 30 Jan 2015
Posts: 676
Location: Texas, USA

PostPosted: Wed Mar 21, 2018 10:19    Post subject: Reply with quote
@ black6spdz, open up a SVN ticket and report:
http://svn.dd-wrt.com/timeline

_________________
ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
black6spdz
DD-WRT User


Joined: 10 May 2007
Posts: 99

PostPosted: Sat Mar 24, 2018 0:07    Post subject: Reply with quote
I've improved cooling by using copper shims directly from cpu/wifi radios to the heatsink. I also noticed there was no screw in the middle.. wondering if this was an assembly problem and could have caused this router "and others?" to everheat befor I got my hands on it. Now it runs 50-55c on all temps but still reboots connecting to the 0 and 2 5G radios. One more issue is the netgear firmware connects at 1Gb to my old laptop's NIC "realtek" but with dd-wrt only at 100Mb.
_________________
DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n
labo
DD-WRT Guru


Joined: 30 Jan 2015
Posts: 676
Location: Texas, USA

PostPosted: Sat Mar 24, 2018 9:59    Post subject: Reply with quote
@ black6spdz,
This is a known issue in repeater bridge mode.
But as WAPs both 5Ghz Radios should work fine. Are you using it as repeater bridge?
If not, just force the wl0 to higher channels > 144 manually set.
wl2, set it manually to channels < 52
Should work

_________________
ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
black6spdz
DD-WRT User


Joined: 10 May 2007
Posts: 99

PostPosted: Sat Mar 24, 2018 17:56    Post subject: Reply with quote
no, with either of the 5 Ghz radios "Wl0,2" in AP mode as SOON as a client attempts to connect it throws that error I posted earlier and reboots. So I even tried using one of the 5G radios in client mode to connect to my main home AP and it does the same, basically and endless reboot loop as soon as it rebboted and reconnected to the AP. I factory reset it and have it working again but I'm scratching my head why everything else works ok "2g radio, USB/NAS functionality, etc". Are the 5G radios/chips just fubar'd?
_________________
DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n
Goto page Previous  1, 2, 3 ... , 15, 16, 17  Next Display posts from previous:    Page 16 of 17
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum