[OpenWrt-Devel] MV88E6060 switch

Sergey Ryazanov ryazanov.s.a at gmail.com
Tue Oct 10 19:07:00 EDT 2017


On Mon, Oct 9, 2017 at 1:58 AM, Nerijus Baliunas
<nerijus at users.sourceforge.net> wrote:
> On Mon, 9 Oct 2017 01:31:29 +0300 Sergey Ryazanov <ryazanov.s.a at gmail.com> wrote:
>
>> > Just tried:
>> > # ifconfig eth0 192.168.0.10 up
>> > ifconfig: SIOCSIFFLAGS: Out of memory
>> > # dmesg|grep eth
>> > [    0.998445] eth0: MII PHY 32 on NPE-B
>> > [    1.005134] eth1: MII PHY 1 on NPE-C
>> > [    6.540687] eth0: link up, speed 100 Mb/s, full duplex
>> > [    9.323993] eth0: link down
>> > [   36.266247] device eth0 entered promiscuous mode
>>
>> Check please, is there any new kernel messages after 'ifconfig ... up'
>> failure (may be not directly related to eth0). Just run dmesg without
>> grep.
>
> I don't see anything suspicious. The full serial console log (dmesg included) is here -
> https://paste.fedoraproject.org/paste/P5sDjdpJr1hFZ-hp~Prwcw
>
>> It is also stranger that something bring eth0 up and then putting it
>> back to down. Is these strings (eth0: link up/eth0: link down) appear
>> in the kernel log during preinit procedure?
>
> Seems so:
> [    4.981198] init: - preinit -
> [    6.473760] random: jshn: uninitialized urandom read (4 bytes read, 10 bits of entropy available)
> [    6.544511] random: jshn: uninitialized urandom read (4 bytes read, 10 bits of entropy available)
> [    6.761251] NPE-B: firmware's license can be found in /usr/share/doc/LICENSE.IPL
> [    6.768796] NPE-B: firmware functionality 0x2, revision 0x2:1
> [    6.776745] eth0: link up, speed 100 Mb/s, full duplex
> Press the [f] key and hit [enter] to enter failsafe mode
> Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
> [   10.310754] mount_root: jffs2 not ready yet, using temporary tmpfs overlay
> [   10.359891] urandom-seed: Seed file not found (/etc/urandom.seed)
> [   10.492841] eth0: link down
>

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 [f] key and hit [enter]" line will be printed
on serial console then press the "f" and hit [enter] :)
3. You could check which IP address configured on eth0 with ifconfig
and if there are not address, then configure it manually
4. Try to pinging in order to check switch functioning

Another guess is to try to disable bridge before bringing eth0 up:
1. Boot your router in normal mode
2. Check whether eth0 is added to the bridge or not:
  # brctl show
3. Disable the bridge and configure eth0 for standalone working:
 # brctl delif br-lan eth0
 # ifconfig br-lan down
 # ifconfig eth0 192.168.0.10 up
4. Try to pinging

-- 
Sergey
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list