how do you tell which revision we have? the only info on the back is the sn# (left panel) and to the right is the SSID and key. just above the SSID(same label) is an A0 and A3.
The FCC ID is FDI-0910560-0
IC 6102A-021
can you check yours, if yours is the same I'll upgrade to the 1.72 and flash it again
TIA
Although I don't suspect any change on those labels, I will check when I get home. Will post back then.
Ok, I just got home and checked the labels. There is a difference. The letters above SSID is "A0 D0" instead of "A0 A3"
Then there could be hardware difference since that label is different? I guess it is the batch number, anyway. Now it explained why some of the users had the problem.
Ok, I just got home and checked the labels. There is a difference. The letters above SSID is "A0 D0" instead of "A0 A3"
Then there could be hardware difference since that label is different? I guess it is the batch number, anyway. Now it explained why some of the users had the problem.
Thank you, that would explain it for me. maybe the dd-wrt gods could create another flash for the different rev?
maybe the dd-wrt gods could create another flash for the different rev?
Do you really think that the information given here (changed batch number from A3 to D0) is enough info for the developers to know what they have to change? _________________ Kernel panic: Aiee, killing interrupt handler!
But, is it true that DD-WRT developers should already get in touch with Buffalo to make a fully compatible and stable firmware?
Remember the announcement from Buffalo?
maybe the dd-wrt gods could create another flash for the different rev?
Do you really think that the information given here (changed batch number from A3 to D0) is enough info for the developers to know what they have to change?
LOM, there was no disrespect intended. That said keep in mind the wiki indicated this was a straight-forward upgrade. That doesn’t appear to be the case, in fact it still says “As of Feb 2010, the WZR-HP-G300NH can be flashed with DD-WRT directly from the Buffalo web GUI”
It seems like OpenWRT wouldn't run at all if there were some sort of hardware change that is causing DD-WRT to not load. Does anyone know if there's a jtag interface in the unit at all? I have not opened mine in case I have to RMA it, but it seems like that would be the place to start if we need logs and nvram dumps.
maybe the dd-wrt gods could create another flash for the different rev?
Do you really think that the information given here (changed batch number from A3 to D0) is enough info for the developers to know what they have to change?
LOM, I personally don't appreciate your condescending tone and feel your comments are in poor taste. In case you haven't noticed, a number of dd-wrt enthusiasts have found out the hard way that their newly purchased router that they had thought was dd-wrt compatible truly is not. The lack of information from official sources leaves us with trying to figure things out the best we know how. Most of us here are enthusiasts, not experts!
Your expertise would be a much better asset to the dd-wrt community if you would simply explain why batch numbers aren't sufficient in diagnosing the problem and point us in the direction we need to go to collect useful information so we can help get this problem solved. Cheers!
-sj
My router has A0 D0 and I haven't had any problems. I have been able to flash from original to dd-wrt, openwrt and x-wrt and every other combination of the three. I will tell you that I have had problems when flashing via the web interface. I strictly use tftp now and it works every time.
maybe the dd-wrt gods could create another flash for the different rev?
Do you really think that the information given here (changed batch number from A3 to D0) is enough info for the developers to know what they have to change?
LOM, I personally don't appreciate your condescending tone and feel your comments are in poor taste. In case you haven't noticed, a number of dd-wrt enthusiasts have found out the hard way that their newly purchased router that they had thought was dd-wrt compatible truly is not. The lack of information from official sources leaves us with trying to figure things out the best we know how. Most of us here are enthusiasts, not experts!
Your expertise would be a much better asset to the dd-wrt community if you would simply explain why batch numbers aren't sufficient in diagnosing the problem and point us in the direction we need to go to collect useful information so we can help get this problem solved. Cheers!
-sj
Only giving the batch number without telling the technical differences between them is the same as throwing an empty bone to Brainslayer, not useful at all.
Posts in another thread in the meantime has shown that it is not related to the batch number so you'll have to dig a bit deeper.
Problems like this is usually caused by the boot loader
and can then easily be seen in a serial log of the boot sequence.
If it is a hardware revision difference in cpu, radio, or switch ic's , then it will also show up in a serial log.
I see two ways of solving the problem:
a) You, the users of the free dd-wrt software provide enough information to Brainslayer so that he has a chance to understand what he needs to change
or
b) Someone send him a failing router so he can find out by himself.
Just don't expect that he is gonna hoover the market to find a problematic version and then buy it with his own money in order to support a free dd-wrt version. _________________ Kernel panic: Aiee, killing interrupt handler!
maybe the dd-wrt gods could create another flash for the different rev?
Do you really think that the information given here (changed batch number from A3 to D0) is enough info for the developers to know what they have to change?
LOM, I personally don't appreciate your condescending tone and feel your comments are in poor taste. In case you haven't noticed, a number of dd-wrt enthusiasts have found out the hard way that their newly purchased router that they had thought was dd-wrt compatible truly is not. The lack of information from official sources leaves us with trying to figure things out the best we know how. Most of us here are enthusiasts, not experts!
Your expertise would be a much better asset to the dd-wrt community if you would simply explain why batch numbers aren't sufficient in diagnosing the problem and point us in the direction we need to go to collect useful information so we can help get this problem solved. Cheers!
-sj
Only giving the batch number without telling the technical differences between them is the same as throwing an empty bone to Brainslayer, not useful at all.
Posts in another thread in the meantime has shown that it is not related to the batch number so you'll have to dig a bit deeper.
Problems like this is usually caused by the boot loader
and can then easily be seen in a serial log of the boot sequence.
If it is a hardware revision difference in cpu, radio, or switch ic's , then it will also show up in a serial log.
I see two ways of solving the problem:
a) You, the users of the free dd-wrt software provide enough information to Brainslayer so that he has a chance to understand what he needs to change
or
b) Someone send him a failing router so he can find out by himself.
Just don't expect that he is gonna hoover the market to find a problematic version and then buy it with his own money in order to support a free dd-wrt version.
I have found the batch numbers to be pretty tell tale.
A0 A3s seem to have the most issues. Anything after A0 A3 seems to be fine.