WRT54G v1.1

Discussion in 'Tomato Firmware' started by cfdfireman, Oct 1, 2006.

  1. cfdfireman

    cfdfireman Network Guru Member

    Any hope of this ever making it to the v1.1 hardware?
  2. envoid

    envoid Network Guru Member

    I was curious as to the technical why's the v1.x aren't liked by tomato. Anyone have any input?
  3. Disman_ca

    Disman_ca Super Moderator Staff Member Member

    From what I remember there where a lot of hardware changes in the 1.1. Linksys changed chips and such during production so there is a large range of different 1.1 versions out there. That about the best I can offer. As for hope, trust in Jon's skills and eventually he'll get it figured out.
  4. myersw

    myersw Network Guru Member

    I am sure he will. He has asked me for some info regarding my wrt54g v1.1. Provided him with things like a complete nvram listing so he could see what the hardware config was. Have also tested an attempt by Jon to get something that works. So I know this is on his radar so to speak. Since this is not his first attempt of a fw (Hyperwrt+tofu) for the wrt54g I am sure he will figure it out. Just not top priority when this is still beta code and there are some issues to be resolved.
    keep in mind that this is beta. For beta I think it is pretty darn good.
  5. cfdfireman

    cfdfireman Network Guru Member

    Thanks for letting me know. I look forward to hopefully trying out Tomato soon.
  6. shadow2k6

    shadow2k6 LI Guru Member

    Tomato Version 0.08 and later now supports wrt54g v1.x. There have been several reported success stories on this as well as on my own v1.1 router.
  7. myersw

    myersw Network Guru Member

    Info on wrt54v1's not running Tomato.

    Here is what Jon emailed regarding what he found. This is not detailed but will give you the Idea as to what the problem was with Tomato and v1's

    Clip from email from Jon:
    It turned out to be a bad combo of the v1 not having a serial console and Tomato's early use of the nvram. It was basically trying to close the console's handle that doesn't exist so it ends up closing the nvram handle instead.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice