Just got the Buffalo stock firmware successfully upgraded to 13972 on my WZR-G300N.
Haven't used it for long now but so far everything seems to work OK apart from the WIRELESS LED, which I heard hasn't been working with previous DD-WRT builds either. Would be nice to have this fixed.
Joined: 22 Jun 2008 Posts: 2440 Location: Am now Dark_Shadow
Posted: Mon Mar 01, 2010 22:25 Post subject:
Kaltsu wrote:
Just got the Buffalo stock firmware successfully upgraded to 13972 on my WZR-G300N.
Haven't used it for long now but so far everything seems to work OK apart from the WIRELESS LED, which I heard hasn't been working with previous DD-WRT builds either. Would be nice to have this fixed.
Just tried to update my old WRT54G v.5 (with 16MB upgrade) from build 13832 to this 13972 using the Broadcom micro_generic .bin without success - unit reports the update failed and provides a 'Continue' button that returns me to the firmware update page (I perform an 'erase nvram' command before each upgrade attempt which has always worked well for me).
Having the same issue here (WRT54G v5) with the micro build. Tried different browsers, and cleared the caches just to be sure.
Just tried to update my old WRT54G v.5 (with 16MB upgrade) from build 13832 to this 13972 using the Broadcom micro_generic .bin without success - unit reports the update failed and provides a 'Continue' button that returns me to the firmware update page (I perform an 'erase nvram' command before each upgrade attempt which has always worked well for me).
Having the same issue here (WRT54G v5) with the micro build. Tried different browsers, and cleared the caches just to be sure.
Same here, I also tried different browsers (IE8, Firefox and Opera) and cleared the caches. Same result in all 3 browsers with the WRT54GS v7.0. Can load the older firmware versions (r13968 or earlier) back in ok but not the new r13972 dd-wrt.v24_micro_generic.bin firmware.
Joined: 22 Jun 2008 Posts: 2440 Location: Am now Dark_Shadow
Posted: Tue Mar 02, 2010 2:21 Post subject:
Pip96 wrote:
pvanb wrote:
sumbuddie wrote:
Just tried to update my old WRT54G v.5 (with 16MB upgrade) from build 13832 to this 13972 using the Broadcom micro_generic .bin without success - unit reports the update failed and provides a 'Continue' button that returns me to the firmware update page (I perform an 'erase nvram' command before each upgrade attempt which has always worked well for me).
Having the same issue here (WRT54G v5) with the micro build. Tried different browsers, and cleared the caches just to be sure.
Same here, I also tried different browsers (IE8, Firefox and Opera) and cleared the caches. Same result in all 3 browsers with the WRT54GS v7.0. Can load the older firmware versions (r13968 or earlier) back in ok but not the new r13972 dd-wrt.v24_micro_generic.bin firmware.
Follow the wiki install for your models. _________________ The New Me
Just got the Buffalo stock firmware successfully upgraded to 13972 on my WZR-G300N.
Haven't used it for long now but so far everything seems to work OK apart from the WIRELESS LED, which I heard hasn't been working with previous DD-WRT builds either. Would be nice to have this fixed.
Would have been nice if he had done a gpio test to find out which gpio pin is connected to the wireless LED and included the result in the bug report..
You can not assume that the developers has the router in question so the problem may not be solved until one of the users gives this feedback. _________________ Kernel panic: Aiee, killing interrupt handler!
Just got the Buffalo stock firmware successfully upgraded to 13972 on my WZR-G300N.
Haven't used it for long now but so far everything seems to work OK apart from the WIRELESS LED, which I heard hasn't been working with previous DD-WRT builds either. Would be nice to have this fixed.
Would have been nice if he had done a gpio test to find out which gpio pin is connected to the wireless LED and included the result in the bug report..
You can not assume that the developers has the router in question so the problem may not be solved until one of the users gives this feedback.
I could do that if somebody gave me some instructions, since I'm not that experienced with the hardware of these devices. I assume I need to open my router and see where the wireless LED is being connected to?
Joined: 22 Jun 2008 Posts: 2440 Location: Am now Dark_Shadow
Posted: Tue Mar 02, 2010 11:52 Post subject:
LOM wrote:
Would have been nice if he had done a gpio test to find out which gpio pin is connected to the wireless LED and included the result in the bug report..
You can not assume that the developers has the router in question so the problem may not be solved until one of the users gives this feedback.
Would have been nice if he had done a gpio test to find out which gpio pin is connected to the wireless LED and included the result in the bug report..
You can not assume that the developers has the router in question so the problem may not be solved until one of the users gives this feedback.
Ok, I did the test and here are the results (also posted in the bug report):
gpio disable 0 - All WAN/LAN port LEDs on
gpio disable 1 - BRIDGE LED on
gpio disable 2 - No visual effect
gpio disable 3 - No visual effect
gpio disable 4 - No visual effect
gpio disable 5 - No visual effect
gpio disable 6 - AOSS LED on
gpio disable 7 - DIAG LED on
gpio disable 8 - No visual effect
gpio enable 0 - All WAN/LAN port LEDs off
gpio enable 1 - BRIDGE LED off
gpio enable 2 - No visual effect
gpio enable 3 - No visual effect
gpio enable 4 - Resets DD-WRT to default settings
gpio enable 5 - No visual effect
gpio enable 6 - AOSS LED off
gpio enable 7 - DIAG LED off
gpio enable 8 - No visual effect
So nothing affected the Wireless LED. What should I do next, open up the router and see where the LED is connected to?
So nothing affected the Wireless LED. What should I do next, open up the router and see where the LED is connected to?
Nah, that is asking to much from you and it is usually not possible to see which pin a LED is connected to.
You did a good attempt even if the result was negative! _________________ Kernel panic: Aiee, killing interrupt handler!
Nah, that is asking to much from you and it is usually not possible to see which pin a LED is connected to.
You did a good attempt even if the result was negative!
I had some spare time so I did it anyway and took some pics. Sorry for the bad quality but the my phone's camera was the only one I could get in my hands. Hopefully the pic will be helpful.
Joined: 22 Jun 2008 Posts: 2440 Location: Am now Dark_Shadow
Posted: Sun Mar 07, 2010 21:41 Post subject:
BasCom wrote:
can someone validate the errors described in ticket 1417 ?
You should try to validate errors before posting a trac ticket.
As far as the word error showing up, 99.9% of the time it is due to a hard reset not being performed as should be do be for and after flashing. _________________ The New Me
