Firmware compatible to Wireless Space?

[coelhonet]

:punk
Yeah, interface eth0 is replying ICMP and accepting telnet connections!
Log attached.
Thanks!

[fvdw]

:bananadance
at least some progress, but still something is not right, seems the switch is not initialized, see this output

Code: Select all

   23.302570] Register Driver 'dsa'
[   23.306021] Distributed Switch Architecture driver version 0.1
[   23.312201] eth0[0]: could not detect attached switch
[   23.317234] eth0[0]: couldn't create dsa switch instance (error -22)

The fact that eth0 now works is probably that besides trying to initialize the switch I also have setup the interface parameters like duplex and speed
Autoneg seems to be off but I think I can add that as well
Could you try if now the ethtool command works to set up the interface, for example enabling auto negotiation, or changing speed ?
Also can you tell which LAN (WAN) connectors on the back are now working

ps if you can open the wsp and have a look at the motherboard and see if you can find a chip with 88E61xx (I expect xx=61). If such a chip is present then there is a switch

ps2 this evening i will be not available until later this evening

[coelhonet]

Hello,

So, for what you asked for, here you are:

1. ethtool works for eth0 (change duplex, speed, autoneg)
No, not working at all

Code: Select all

~ # ethtool -s eth0 speed 100 duplex half
Cannot set new settings: Invalid argument
  not setting speed
  not setting duplex
~ # ethtool -s eth0 speed 100 duplex full
Cannot set new settings: Invalid argument
  not setting speed
  not setting duplex
~ # ethtool -s eth0 speed 1000 duplex full
Cannot set new settings: Invalid argument
  not setting speed
  not setting duplex
~ # ethtool -s eth0 autoneg on
Cannot set new settings: Invalid argument
  not setting autoneg


2. What ports are working on network connection?
All LAN ports are working find for replying ICMP packets. WAN/Recovery port is not working, but it's expected, it's on eth1 on your firmware.

3. What is 88E61xx chip on Wireless Space board?
88E6161-LG02

Attached picture from the board and also serial output log.

Thanks!

[fvdw]

:thumbup thanks for testing

ok , I will only keep the driver in for this switch.

attached two kernels, both have initialization of eth0 with speed =0, that should enable auto negotiation. This will be needed to get a kernel that can works as well on a 100Mbits/s and 1000Mb/s network

kernel 212 has a extra code related to initializing the switch
kernel 213 has the initialization code as kernel 211

kernel 212 and 213 have a print statement in the driver for the switch to see if it is actually called by the kernel and when this is the case what the response of the mainboard is when the kernel tries to identify the switch type.

[coelhonet]

Hello,

Tests results attached.

This turn neither firmwares worked to accept ICMP or Telnet.

Thanks

[fvdw]

mmm..it doesn't want to go into autoneg mode , you could communicate with it by setting your router port to 10mb/s full duplex
I can restore 1000 mb/s full duplex in the kernel setup but it is not ideal if we can not adapt it. So this one is still to solve

About the driver for the switch, in kernel 213 we see this

Code: Select all

[   23.444164] Distributed Switch Architecture driver version 0.1
[   23.450153] probe 88e6123_61_65 sw_addr=0 ret=65535
[   23.455052] eth0[0]: could not detect attached switch
[   23.460083] eth0[0]: couldn't create dsa switch instance (error -22)

So a failure to load the driver.
But in kernel 212 we can see this

Code: Select all

[   25.036788] Distributed Switch Architecture driver version 0.1
[   25.043119] probe 88e6123_61_65 sw_addr=10 ret=5650
[   25.048023] eth0[0]: detected a Marvell 88E6161 (A1) switch
[   25.156250] libphy: dsa slave smi: probed

:punk succes, and driver loaded, seems the software address was the trick needed.
next is how to use it in combination with the ethernet driver. :thinking

[fvdw]

another kernel 214, this with a different call for initialization of the switch, it should link a gpio pin to an irq, I copied this from another setup file of marvell board with the same chip.
Lets see what happens (likely a kernel oops because of using a wring GPio pin)

kernel 215 is same as 212 but with different phy address

[coelhonet]

Hello,

Tested both firmwares and still not able to get ICMP reply.

Logs attached.

My trip will last for 2 weeks, so in between, will not be able to test anything new. When back I'll be at full load again.

Thanks!

[fvdw]

hello and thanks for testing , it is strange that it doesn't react on on ping as in the ifconfig output it can be seen that bytes are sent and received, but it also mentions a high error level in the packets, this was also the case in the kernel 211 where you did get a response. Something wrong in your LAN ?
I see no change in the output related to the dsa switch. So attached a 2 kernels taking out step by step change compared to kernel 211 to see if we can go back to that state with working eth0 and work from there
Hopefully you can them check them before your trip ;)

kernel 214

Code: Select all

add some extra ip's
eth0      Link encap:Ethernet  HWaddr 00:D0:4B:8F:94:AA
          inet addr:192.168.1.252  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:4bff:fe8f:94aa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:283 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1687 (1.6 KiB)  TX bytes:28426 (27.7 KiB)
          Interrupt:11

eth0:1    Link encap:Ethernet  HWaddr 00:D0:4B:8F:94:AA
          inet addr:192.168.0.252  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:11

kernel 215

Code: Select all

add some extra ip's
eth0      Link encap:Ethernet  HWaddr 00:D0:4B:8F:94:AA
          inet addr:192.168.1.252  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:4bff:fe8f:94aa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:284 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:648 (648.0 B)  TX bytes:28516 (27.8 KiB)
          Interrupt:11

eth0:1    Link encap:Ethernet  HWaddr 00:D0:4B:8F:94:AA
          inet addr:192.168.0.252  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:11


files removed: 27dec14

[coelhonet]

Hey! Happy New Year!

Have been a long time since my trip, but now I'm back!

I'll test those files and provide feedback later today.

Thanks!