Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Peter Lewis <pllewis72@gmail.com>
Cc: cerowrt-users <cerowrt-users@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-users] [Cerowrt-devel] WNDR3800CH varient doesn't load WNDR3800 firmware
Date: Sat, 2 Aug 2014 11:01:56 -0400	[thread overview]
Message-ID: <CAA93jw7vDwUTnmSy2LOcriyxz=EOwJbWb41WxVWKoYR2zbtuJQ@mail.gmail.com> (raw)
In-Reply-To: <CAE5_cQ7JOh2Qf7=jn73uSuF9APdmvmfoEiiKHnG=5ndfrKa13A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5189 bytes --]

I submitted the patch to openwrt-devel, it is in
http://patchwork.openwrt.org/patch/6047/

hopefully someone will pick it up.


On Fri, Aug 1, 2014 at 4:30 PM, Peter Lewis <pllewis72@gmail.com> wrote:

> Flashed it and it works fine.  Seems like that was one of the easier
> support adds to a build.
>
> openwrt-ar71xx-generic-wndr3800ch-squashfs-factory.img via tftp was the
> image I tested.  I have not done the jffs2 or sysupgrade image.
>
> Cheers and if you're ever in central VA, I'll buy you a beer or alternate
> frosty beverage.
>
> Keep up the good work,
> Pete
>
>
>
> On Fri, Aug 1, 2014 at 3:47 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> I just put test images up for the wndr3800CH up at:
>> http://snapon.lab.bufferbloat.net/~cero2/test-wndr3800ch for squashfs
>> and jffs2.
>>
>> It is otherwise the same as the 3.10.50-1 release. If it works for you
>> two I'll fold the 2 line patch into the build or pester someone at openwrt
>> to get it in there.
>>
>>
>> On Sat, Jul 26, 2014 at 10:44 AM, Sam Chessman <sam.chessman@gmail.com>
>> wrote:
>>
>>> Top reply?  Well, anyway I bought a refurbished WNDR3800 from amazon
>>> $40.00 to run cerowrt.  I was hoping to get a compatible model but it
>>> turns out I got a version with model change to WNDR3800-1CHNAS which
>>> cause the firmware upload to fail gracefully.    I found out about
>>> this at openwrt.org, see
>>> https://forum.openwrt.org/viewtopic.php?id=49390
>>>
>>> The above referenced thread refers to an openwrt developer (zloop) who
>>> says he built a version with a different model string WNDR3800CH.
>>> See https://forum.openwrt.org/viewtopic.php?id=51025
>>>
>>> "according to GPL fw sources the router is called "WNDR3800CH"
>>> (MODEL_NAME)
>>>
>>> so adding a line
>>>
>>> Makefile:$(eval $(call
>>>
>>> SingleProfile,Netgear,64kraw,WNDR3800CH,wndr3800ch,WNDR3700,ttyS0,115200,$$(wndr3700v2_mtdlayout),0x33373031,WNDR3800CH,"",-H
>>> 29763654+16+128))
>>>
>>> and modify the WNDR3800CH model to the Multiprofile line
>>>
>>> $(eval $(call MultiProfile,WNDR3700,WNDR3700V1 WNDR3700V2 WNDR3800
>>> WNDR3800CH WNDRMAC WNDRMACV2))
>>>
>>> should create an image that can be flashed from factory firmware
>>>
>>> PS: it's all untested - no guarantee it will work
>>>
>>> feel free to test and send to the mailing list
>>> "
>>>
>>> I'm going to try patching the image header to have the model name
>>> "WNDR3800CH" and see if it will load.
>>>
>>> It would be a good idea for the developers who understand the above to
>>> add this model to the makefiles so it also gets built.  I bet a lot of
>>> WNDR3800-1CHNAS series routers are out in the wild and if someone
>>> picks one up to run wrt or cerowrt they will be stymied.
>>>
>>> Sam
>>>
>>>
>>> > Hi Eric,
>>> >
>>> > I can answer the first question: yes, that's the one. I'm running on
>>> > exactly this since more than a year now.
>>> >
>>> > Best regards,
>>> > Maciej
>>> >
>>> > On Tue, Jul 15, 2014 at 7:37 PM, Eric S. Johansson <esj at eggo.org>
>>> wrote:
>>> >> is this the right box for cerowrt?  I figure a refurb should work as
>>> well as
>>> >> new for this project.
>>> >>
>>> http://www.newegg.com/Product/Product.aspx?Item=N82E16833122523&cm_re=WNDR3800-_-33-122-523-_-Product
>>> >>
>>> >> btw, as a funding mechanism, have you considered teaming up with
>>> Netgear to
>>> >> sell refurbished boxes loaded up with cerowrt?  set up inexpensive
>>> for fee
>>> >> support forum you have two revenue streams.
>>>
>>
>> We had had several discussions with netgear's CTO about various options
>> for a relationship. Towards the end, it seemed like my communications were
>> being sent directly to /dev/null.
>>
>> Doesn't mean that they can't resume talks, but I'd rather get a RFP
>> together for the next generation and see who might care enough about it to
>> want to participate.
>>
>>
>>> >> _______________________________________________
>>> >> Cerowrt-users mailing list
>>> >> Cerowrt-users at lists.bufferbloat.net
>>> >> https://lists.bufferbloat.net/listinfo/cerowrt-users
>>>
>>>
>>> --
>>>    Sam Chessman                                     sam.chessman (a)
>>> gmail.com
>>> "That's how we are, we are descendants of molecules formed a million
>>> years ago because they figured out how to replicate themselves. We
>>> have a name for things that don't copy themselves: dead." -- Cory
>>> Doctorow
>>> _______________________________________________
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>
>>
>>
>>
>> --
>> Dave Täht
>>
>> NSFW:
>> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
>>
>> _______________________________________________
>> Cerowrt-users mailing list
>> Cerowrt-users@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-users
>>
>>
>
>
> --
> Peter Lewis
> pllewis72@gmail.com
>



-- 
Dave Täht

NSFW:
https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

[-- Attachment #2: Type: text/html, Size: 8169 bytes --]

      reply	other threads:[~2014-08-02 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26 14:44 [Cerowrt-users] " Sam Chessman
2014-08-01 19:47 ` [Cerowrt-users] [Cerowrt-devel] " Dave Taht
2014-08-01 20:30   ` Peter Lewis
2014-08-02 15:01     ` Dave Taht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7vDwUTnmSy2LOcriyxz=EOwJbWb41WxVWKoYR2zbtuJQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt-users@lists.bufferbloat.net \
    --cc=pllewis72@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox