Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Tue Jan 24, 2017 4:08 Post subject:
phoenix127 wrote:
One last thing, can you confirm the number under the "Vietnam" on the label at the bottom. I think it will be the 272-12475-03 like @gogoroute has given that both are Vietnam manufactured routers.
My made in China router shows has 272-12465-03.
Hi Phoenix127, thanks for kepping this thread alive.
My Vietnam Router model # is: 272-12473-02.
I will post the log once I open and connect serial port to my router.
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Tue Jan 24, 2017 4:57 Post subject: Here is my checkBC output
CFE> checkBC
check bootcode nvram settings...
boardflags2 value found: 0x00000000
boardflags value found: 0x00000110
boardnum value found: 32
boardrev value found: 0x1101
boardtype value found: 0x072F
boot_wait value found: off
clkfreq value found: 1400,800
et0macaddr value found: 00:00:00:00:00:00
et0mdcport value found: 0
et0phyaddr value found: 30
lan_ipaddr value found: 192.168.1.1
lan_netmask value found: 255.255.255.0
landevs value found: vlan1 wl0 wl1 wl2 wl0.1 wl1.1 wl2.1
sdram_config value found: 0x014B
sromrev value found: 8
vlan1hwname value found: et2
vlan1ports value found: 1 2 3 4 5 7 8*
vlan2hwname value found: et2
vlan2ports value found: 0 8u
wait_time value found: 3
wandevs value found: et2
watchdog value found: 2100
xtalfreq value found: 25000
gpio0 value found: usbport1
gpio16 value found: usbport2
check OK..
*** command status = 0
Hey, @labo, can U give me some keywords to search for how to get boot log or console log of R8500?
I'm using a TTL2USB adapter connected to my pc, and use PuTTY with 115200、8、N、1 options to show the console log.
But I can't see anything in the screen when the route is booting.
But when the route was loaded completely . I unplug my TTL2USB adapter and re-plug it than restart PuTTY, the log was print automatically.
logs as below:
BusyBox v1.7.2 (2016-12-12 21:53:18 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
#
#
# ********error host is null ******
update get public ip error
**********netgear ddns update end*************
********error host is null ******
Thx. a lot.
labo wrote:
When I update to dd-wrt firmware I only see this in serial log:
fileSize = 24006714
..................................................
...................................................
4366C0 HW only supported since V1.0.2.34_1.0.45
@lobo Never mind about my previous post. I'm already got the boot log.
@phoenix127 I'll post my unit's information as below:
1)Netgear firmware version: V1.0.2.86_1.0.75
2)Made in Vietnam.
3)On the bottom of my router,There is a number above the serial number: 272-12475-03
4)Model:R8500-100PRS
5)I never try to downgrade to the earlier NetGear firmware.
6)boot log and upgrade to Kong's dd-wrt.K3_R8500_4 version ( from http://www.desipro.de/ddwrt/K3-AC-Arm/ with the date of 2017-01-1 log pls check the attachment, important information :
So, there is a second hardware rev (MP2), which goes against what @labo was told when he called Netgear previously (30 Dec posting). Whats odd is that Netgear doesn't have any "V1" or "V2" designations on their downloads like they normally do when a device has been updated. I guess this means its a small change that can be covered in software only ?
I've not gone through the logs in detail, I will do that in a bit.
Obviously this shows that the views of hardware defect on some routers is wrong, its all just the MP2 flavour. (will the next one be mp3 and play music ??)
Clearly this is why the firmware upgrade fails from stock and I expect the change is related to a roboswitch change, hence the kernel panic's others are seeing.
There are different regions in the different devices
malachi
hwtype=R8500<,hwrev=MP1
read_board_data(662) region_num=1 2 (NA) - North America ?
Labo
hwtype=R8500<,hwrev=MP2
read_board_data(682) region_num=1 2 (NA) - North America ?
gogoroute
hwtype=R8500<,hwrev=MP2
read_board_data(682) region_num=4 2 (PR) - PR China ?
The CheckBC output is identical across @labo and my router, other than different LAN IP addresses and a couple more wireless devices on @labo's. Its interesting that boarnum, boardrev and boardtype are identical between them given the different hwrev's.
Malachi has a hardware problem (a missing radio) and some upgrade issues. I think this is a different issue, given that its hardware rev MP1 which normally works for most. Can you confirm the exact error you are getting and where its happening. I can't find this in the thread, only the stock boot logs.
Last edited by phoenix127 on Tue Jan 24, 2017 15:42; edited 1 time in total
Yes, I think PR stand for PR China, Mine actually is the china version. There is Chinese characters on the box.
And NA stand for North America, I guess.
I was learn from Netgear engineer when I wanted to apply RMA of my R8500 on December 10,2016. They told me that there was a BOOT LOOP issue of my unit, the same batch (or Lot?) has the same problem. They told me I will got the PR China version
Which was no BOOT LOOP issue. My last unit was the North America version, my first unit was PR China version too. So now I'm using my 3rd R8500 after applied twice RMA...
Thanks god, I can use my R8500 now, just after I paid TWO months ago...
I looked at the Broadcom community portal. Well, you get a pile of T&C's which if signed doesn't give you the ability to release source code or datasheet info, so there is no point signing up and being bound by their terms.
Surely guys you would sell more product if people could use and integrate your products at will - a bit like people did with 74 series and 4000 series. I hope the cypress buy-out will fix this in the near term.
So, I looked elsewhere, the linux source is here
https://github.com/torvalds/linux/tree/master/drivers/net/dsa. There are a number of updates from 5 months ago, 4 months ago, 2 months ago and 16 days ago. I don't know what the updates were yet, but if there are changes, then I'm wondering if any of those are relevant to our problem and if dd-wrt is using the latest drivers for the roboswitch.
Kong - can you confirm what driver version is in the current build and if its not the latest, can it get updated to see if this fixes the driver issue ?
Looks like your inbox is full or you are not reading your pms, since you have serial, you can try the new 8500 build in test folder, it most likely works. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Tue Jan 24, 2017 19:06 Post subject:
<Kong> wrote:
labo wrote:
Yes, mine looks pretty much the same...
Looks like your inbox is full or you are not reading your pms, since you have serial, you can try the new 8500 build in test folder, it most likely works.
Thanks a lot!, Kong.
I just tried it from WebGui, same error firmware not compatible error code -2.
log pls check the attachment, important information :
