On Wed, 11 Oct 2017 02:07:00 +0300 Sergey Ryazanov
wrote:
> Ok. I am starting to run out of ideas. Let's start guessing.
>
> eth0 works at least during preinit. You could check your switch
> functioning in the failsafe mode:
> 1. Power on router
> 2. When the "Press the
On Wed, Oct 11, 2017 at 12:43 PM, Nerijus Baliunas
wrote:
> This works:
> = FAILSAFE MODE active
> # ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:18:39:21:0D:AE
> inet addr:192.168.1.1 Bcast:192.168.1.255
On Wed, 11 Oct 2017 14:53:16 +0300 Sergey Ryazanov
wrote:
> Ok. At least we know now that the switch functioning (even without a
> dedicated driver). One question left: what happens to the Ethernet
> driver?
>
> Can you boot your router in failsafe mode again, and try
On Thu, Oct 12, 2017 at 12:29 AM, Nerijus Baliunas
wrote:
> On Thu, 12 Oct 2017 00:15:15 +0300 Sergey Ryazanov
> wrote:
>> Can you boot in failsafe mode again, check free memory while the
>> interface is Up, then bring it Down and check
On Thu, Oct 12, 2017 at 2:05 AM, Nerijus Baliunas
wrote:
> On Thu, 12 Oct 2017 01:30:35 +0300 Sergey Ryazanov
> wrote:
>
>> Try this patch, it should reduce the memory demand of the ethernet
>> driver, so it will have the change to get
On Thu, 12 Oct 2017 01:30:35 +0300 Sergey Ryazanov
wrote:
> Try this patch, it should reduce the memory demand of the ethernet
> driver, so it will have the change to get started on your router.
>
> Just put it to target/linux/ixp4xx/patches-4.4 along with the previous
On Wed, Oct 11, 2017 at 11:01 PM, Nerijus Baliunas
wrote:
> On Wed, 11 Oct 2017 22:50:40 +0300 Sergey Ryazanov
> wrote:
>
>> Khm, according to wikidevi your router is equipped with 16MB of RAM,
>> the ethernet driver for xscale SoCs
On Thu, 12 Oct 2017 00:15:15 +0300 Sergey Ryazanov
wrote:
> >> As a quick test, can you unload all kernel modules and try to set eth0 UP
> >> again?
> >
> > Unfortunately rmmod with a list of modules does not work:
> > # rmmod ip_tables ip6_tables ip6t_REJECT ...
> >
On Wed, 11 Oct 2017 23:28:00 +0300 Sergey Ryazanov
wrote:
> > root@LEDE:/# cat /proc/meminfo
> > MemTotal: 12232 kB
> > MemFree: 996 kB
>
> Looks like this ^^^ is the cause of the "ifconfig up" failure. Your
> board really have not free RAM.
>
> As
On Wed, Oct 11, 2017 at 11:44 PM, Nerijus Baliunas
wrote:
> On Wed, 11 Oct 2017 23:28:00 +0300 Sergey Ryazanov
> wrote:
>
>> > root@LEDE:/# cat /proc/meminfo
>> > MemTotal: 12232 kB
>> > MemFree: 996 kB
>>
>> Looks like
On Wed, Oct 11, 2017 at 3:17 PM, Nerijus Baliunas
wrote:
> On Wed, 11 Oct 2017 14:53:16 +0300 Sergey Ryazanov
> wrote:
>> Ok. At least we know now that the switch functioning (even without a
>> dedicated driver). One question left: what
On Wed, 11 Oct 2017 18:53:40 +0300 Sergey Ryazanov
wrote:
> A-ha! The interface survives the down/up circle but does not survive
> the init procedure.
>
> Try to completely avoid bridge usage, e.g.:
> 1. boot in normal mode
> 2. disable bridge usage on "lan":
> #
On Wed, Oct 11, 2017 at 7:17 PM, Nerijus Baliunas
wrote:
> On Wed, 11 Oct 2017 18:53:40 +0300 Sergey Ryazanov
> wrote:
>
>> A-ha! The interface survives the down/up circle but does not survive
>> the init procedure.
>>
>> Try to completely
13 matches
Mail list logo