On 10.10.2017 05:26, Florian Fainelli wrote:
Le 10/09/17 à 11:01, Lucian Cristian a écrit :
I'm trying to make a custom image and can't seem to get pass by this
You would have to provide a more complete log, here we just see the make
returning an error back from the directories it descended
On 10.10.2017 05:26, Florian Fainelli wrote:
Le 10/09/17 à 11:01, Lucian Cristian a écrit :
I'm trying to make a custom image and can't seem to get pass by this
You would have to provide a more complete log, here we just see the make
returning an error back from the directories it descended
Hauke Mehrtens wrote:
> On 10/09/2017 01:28 PM, Andrey Jr. Melnikov wrote:
> > Hauke Mehrtens wrote:
> >> On 10/08/2017 01:31 PM, Andrey Jr. Melnikov wrote:
> >>> Arjen de Korte wrote:
> Citeren Hauke Mehrtens :
Hi Hauke,
I've tested kernel 4.9 with my TP-Link TL-WR1043N/ND v1 and everything
seems to work so far.
The only thing I've noticed is that internet speedtests with the build
from your ar71xx staging tree are slower (~130Mbit) in comparison to
the 17.01.3 release with kernel 4.4 (~197Mbit).
On 10/10/2017 02:41 AM, Lucian Cristian wrote:
> On 10.10.2017 05:26, Florian Fainelli wrote:
>> Le 10/09/17 à 11:01, Lucian Cristian a écrit :
>>> I'm trying to make a custom image and can't seem to get pass by this
>> You would have to provide a more complete log, here we just see the make
>>
> (...) Relocate it to a different memory region which is
> still under the 8MB RAM, but in the higher area.
Ok, I can confirm that this is working fine with both, the WRT54GL and
the WL500GP V2 on Linux 4.9.52.
Thanks for debugging and fixing!
Regards,
P. Wassi
mktplinkfw/mktplinkfw2 utilities put JFFS2 EOF market only at 64KB
boundary, this could lead to current device configuration lost during
the sysupgrade on a device, which is equpped with flash with the 4KB
erase block size (e.g. TP-Link Archer C20).
This happens when 64KB and 4KB alignments do
On Mon, Oct 9, 2017 at 1:58 AM, Nerijus Baliunas
wrote:
> On Mon, 9 Oct 2017 01:31:29 +0300 Sergey Ryazanov
> wrote:
>
>> > Just tried:
>> > # ifconfig eth0 192.168.0.10 up
>> > ifconfig: SIOCSIFFLAGS: Out of memory
>> > # dmesg|grep eth
>>