From: Fred Stratton <fredstratton@imap.cc>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 3.10.10-1 development build released
Date: Thu, 12 Sep 2013 17:31:15 +0100 [thread overview]
Message-ID: <E21DB982-2026-44FA-90EE-3ACD0AC35293@imap.cc> (raw)
In-Reply-To: <D89AB2EE-FA93-4C9E-8A98-CB49CC662058@imap.cc>
[-- Attachment #1: Type: text/plain, Size: 4660 bytes --]
Well, it will not, thinking logically. Specific to an earlier kernel version.
On 12 Sep 2013, at 16:55, Fred Stratton <fredstratton@imap.cc> wrote:
> Have forced installation for now. I do wonder if the kmod will load.
>
>
> On 12 Sep 2013, at 16:49, Fred Stratton <fredstratton@imap.cc> wrote:
>
>> Unfortunately, it does not install
>>
>> Installing ppp-mod-pppoa (2.4.5-10) to root...
>> Downloading http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.11-2/packages/ppp-mod-pppoa_2.4.5-10_ar71xx.ipk.
>> Collected errors:
>> * satisfy_dependencies_for: Cannot satisfy the following dependencies for ppp-mod-pppoa:
>> * kernel (= 3.10.11-1-35f34a410a185624e80726cf7cd5a871) * kernel (= 3.10.11-1-35f34a410a185624e80726cf7cd5a871) *
>> * opkg_install_cmd: Cannot install package ppp-mod-pppoa.
>>
>>
>> On 12 Sep 2013, at 01:16, Dave Taht <dave.taht@bufferbloat.net> wrote:
>>
>>> On Tue, Sep 10, 2013 at 11:07:50AM +0100, Fred Stratton wrote:
>>>> sysupgrade -n does not function still.
>>>>
>>>> 'mtd -r write {filename].bin firmware' continues to work nicely.
>>>
>>> Thank you for that. I still have to re-tear apart the serial cable and
>>> see what's going wrong on sysupgrade. As you can possibly tell I'm not
>>> actually in the yurtlab that much so what I can't do by remote control,
>>> I can't do... but if mtd -r can at least give me a fresh install, that's
>>> a start....
>>>
>>> I have added the pppoa modules to the 3.10.11-2 build. you should
>>> be able to do an opkg update; opkg install mod-pppoa # or something like that
>>> to install it and the other module.
>>>
>>> I've made those part of the defaults for the next build, too.
>>>
>>>
>>>
>>>>
>>>> Build 3.10.11-2 functions well so far.
>>>>
>>>>
>>>> On 10 Sep 2013, at 06:14, Dave Taht <dave.taht@gmail.com> wrote:
>>>>
>>>>> I did manage to test 3.10.10-1 briefly. It worked. I note that configuring ipv6 properly is still up in the air vs 6relayd or dnsmasq.
>>>>>
>>>>> Based on that working, I did the very minor upgrade to build 3.10.11-2 (I goofed the first time, thus no -1)
>>>>>
>>>>> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.11-2/
>>>>>
>>>>> Please feel free to give this a shot as a devbuild instead of 3.10.10
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 9, 2013 at 5:28 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>>>> + readlink fix (hopefully fixes sysupgrade)
>>>>> + usual merge with openwrt head (tons of ath9k changes)
>>>>> + dnsmasq 2.67test10
>>>>> + ipv6subtrees back in
>>>>> + the final htb atm patches
>>>>> + eliminated maxpacket check in codel
>>>>>
>>>>> - did not fold in edumazet's new fq code
>>>>> - 100% totally untested. May a braver soul than I give it a shot. I won't be near a cero box til thursday, otherwise.
>>>>>
>>>>> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.10-1/
>>>>>
>>>>> -I'm not sure if I got the "last" of the aqm gui patches in there or not...
>>>>>
>>>>> ...
>>>>>
>>>>> Anyway... I had hopes to get a stable release out in august. I AM very happy about the major stuff that got fixed, instead... but...
>>>>>
>>>>> Since we didn't... I now have a ton of other matters piled up. Not least of which is a pending trip to england and the eu.
>>>>>
>>>>> So for the next month I don't see how I'm going to be able to put more than a day a week into cerowrt. Tops. So I have tagged up this "release" and pushed all the baked portions of the sources to github. I'm still a little dubious of the ipv6 subtrees bit....
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Dave Täht
>>>>>
>>>>> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Dave Täht
>>>>>
>>>>> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
>>>>> _______________________________________________
>>>>> Cerowrt-devel mailing list
>>>>> Cerowrt-devel@lists.bufferbloat.net
>>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>>
>>>
>>>> _______________________________________________
>>>> Cerowrt-devel mailing list
>>>> Cerowrt-devel@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 6936 bytes --]
next prev parent reply other threads:[~2013-09-12 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 0:28 Dave Taht
2013-09-10 5:14 ` Dave Taht
2013-09-10 9:45 ` Fred Stratton
2013-09-10 10:07 ` Fred Stratton
2013-09-12 0:16 ` Dave Taht
2013-09-12 4:27 ` Fred Stratton
2013-09-12 15:49 ` Fred Stratton
2013-09-12 15:55 ` Fred Stratton
2013-09-12 16:31 ` Fred Stratton [this message]
2013-09-12 16:41 ` Fred Stratton
2013-09-11 8:36 ` Sebastian Moeller
2013-09-12 4:10 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E21DB982-2026-44FA-90EE-3ACD0AC35293@imap.cc \
--to=fredstratton@imap.cc \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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