Firmware compatible to Wireless Space?

[coelhonet]

Hey!

So, I tested with newer version, and same behavior as before (log attached).

This time, I setup a local router (Linksys E900), between my notebook and LaCie Wireless Space. I cannot see any request to DHCP Server running on the router (besides my own notebook).

Also, besides you telling that "Sending discover..." should last 5 times, I can see it never ends.

Something interesting I can see from logs (besides I think it's not related to IP configuration):
[ 23.013362] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
[ 23.025402] Scanning device for bad blocks
[ 23.032918] Bad eraseblock 41 at 0x000000520000
[ 23.049598] Bad eraseblock 192 at 0x000001800000
[ 23.054557] Bad eraseblock 197 at 0x0000018a0000
[ 23.067256] Bad eraseblock 298 at 0x000002540000
[ 23.079483] Bad eraseblock 393 at 0x000003120000
[ 23.089922] Bad eraseblock 466 at 0x000003a40000
[ 23.100529] Bad eraseblock 541 at 0x0000043a0000
[ 23.109282] Bad eraseblock 593 at 0x000004a20000
[ 23.114000] Bad eraseblock 595 at 0x000004a60000
[ 23.133524] Bad eraseblock 781 at 0x0000061a0000
[ 23.154978] Bad eraseblock 991 at 0x000007be0000
[ 23.159873] Bad eraseblock 995 at 0x000007c60000
[ 23.166944] Creating 4 MTD partitions on "orion_nand":

Is it normal?

Also, I pushed a smaller HD SATA there for our tests. When reseting LaCie Wireless Space, it dumps its own firmware and filesystem partitioning there, so it's kind of a way to restore to factory defaults, if someone want this in future.

Thanks!

[fvdw]

about the NAND I will have look
this evening I will make a standalone kernel taht doesn't start a dhcp client and only uses the static ones

[fvdw]

ok another kernel with only using static ip addresses (only 192.168.1.252 and 192.168.0.252)

[coelhonet]

Hi,

New test executed with latest version and still not able to access Wireless Space after kernel is in place.

I have attached current network I set, so you can have a better view how things are setup here. Everything is running via static IPs. I have connected 2 network cables to Wireless Space, because there's WAN port (also works as recovery port) which one has a different MAC address. While running stock firmware, I'm able to ping both networks, and so, I can access IPs on both NICs.

On my notebook, eth0 has 192.168.1.251 as primary IP address and 192.168.0.251 and also 172.20.0.2 as IP aliases.

Something I have found, is that NIC order is different from fvdw firmware and LaCie one.

IP Config while running LaCie firmware (eth0 is WAN/Recovery port):
$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:4B:8F:93:E2
inet addr:172.20.0.1 Bcast:172.20.0.15 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:35 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:3993 (3.8 KiB) TX bytes:7392 (7.2 KiB)
Interrupt:15

eth1 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
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:91 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:0 (0.0 B) TX bytes:21850 (21.3 KiB)
Interrupt:11

IP Config while running LaCie firmware (eth1 is WAN/Recovery port):
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:274 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:27554 (26.9 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

eth1 Link encap:Ethernet HWaddr 00:D0:4B:8F:93:E2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:15

When fvdw firmware is up, I tried to ping from my notebook and no luck. When trying to ping from Wireless Space, I got no response and shell didn't accept any new command.

Hope you have more ideas on what can be done next. :roll:

Thanks for trying it hard!

[fvdw]

very odd, apparently the lacie kernel has a driver running that enables the wireless space to run as router and set up the lan ports accordingly. From that output it seems that in one setup (eth0 wan/recov) eth0 is the "internet port" on the back side and eth 1 is the LAN1 port. and in the other setup it is the otherway around. This I conclude from the output of the lacie firmware on the mac address (HWaddr) of the ethernet interfaces eth0 and eth1, notice that they are swapped when you have either eth0 or eth1 set as wan/recovery port.
Ps how do you set that , which interface to use as wan/recovery port ?
Also it puzzles me that we have 4 ports (1 wan and 3 lan ) and only two ethernet interface. This looks like that there is something in between the ethernet ports and the connectors on the back (a port multiplier or switch) and for which a driver must be loaded.

But first let check out some thing more as now with the dhcp client disabled you can use the serial console to access the standalone kernel when it is running and give command line commands. It seems you have already done that because in the log you posted I see this

Code: Select all

pass control to sh shell
/bin/sh: can't access tty; job control turned off
~ # ifconfig
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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:274 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:27554 (26.9 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

~ # ifconfig -a
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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:274 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:27554 (26.9 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

eth1      Link encap:Ethernet  HWaddr 00:D0:4B:8F:93:E2
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:15

ipddp0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          BROADCAST NOARP MULTICAST  MTU:585  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          LOOPBACK  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

tunl0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

~ #

From this output it seems that eth0 is setup ok, it has an ip and, it has also sent bytes but not it seems that it did not receive any bytes, so something is still wrong.

Let now first see if the telnet daemon is running and find out which other processes are running
Give following command on the serial console after the standalone kernel is loaded and running.

Code: Select all

ps-ef

If this command doesn't workt then try

Code: Select all

busybox pse -ef

or

Code: Select all

bin busybox -ef

This should give a list which processes are running.
PS Also you could give on the command line the command "ping ip-address" (or busybox ping) to ping a ip in your Lan

We can also try eth1
use these command
/sbin/ifconfig eth1 192.168.1.253 up

now also eth1 should be up and you could try if that is accessible or ping-able (try all the connectors on the back)

Later this afternoon I will check again the output of the lacie kernel boot log to see if we can find traces of loading another driver used to controle the ethernet connectors on the back

[coelhonet]

Hello!

So, I tried once again and as before, I tested network cable on all ports on Wireless Space back.

I'd say that LAN ports are acting as a switch.

WAN/Recovery port is set when you select mode that Wireless Space should work. So, on AP mode, WAN is your uplink to your Internet Provider. When setting as NAS+Switch, it's used as recovery port. Important to say that we also have Wireless NIC inside.

On this test I can see telnet is running. I have set IP on eth1 (WAN/Recovery port). I cannot ping any of them from my notebook after FVDW is running (works fine when stock firmware is running).

When trying to execute ping, I got no reply back on stdout, and I cannot escape/break that command.

Log attached.

Thanks!

[fvdw]

ok the all the required processes are runing the only thing not yet working is the ethernet connection
so we can concentrate on that

in the log you posted I see this after you have activate eth1

Code: Select all

eth1      Link encap:Ethernet  HWaddr 00:D0:4B:8F:93:E2
          inet addr:192.168.1.253  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:4bff:fe8f:93e2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1143 (1.1 KiB)  TX bytes:468 (468.0 B)
          Interrupt:15


It has sent and received bytes so there must have been a communication with your PC
I expect that eth1 is in this case LAN1 port (or LAN2, 3) did you try those connection while eth1 was up

Funny is also that eth0 has no received bytes but relative high sent bytes, on eth1 sent bytes is relative low.

In on of the logs you sent from lacie kernel we see this

Code: Select all

Port 2: Link-up, Full-duplex, Speed-1000Mbps.


This seems to be the second port on the backsite where you have plugged in the ethernet cable (LAN1)

In the standalone kernel probably eth1 is connected with that port

Howvere with the standalone kernel running it seems to be set to half duplex 10 Mb/s
This indicates that on your lan auto negotiation is failing or disabled.
If the the router doesn't have the same setting as the ethernet card then communication will fail.
In the standalone kernel we have limited possibilities to setup the ethernet card because it contains only a few programs are present, if we want to set up it manually I need to add some but the kernel may not become to big otherwise it won't load. another route is trying to compile the ethernet driver used by marvell in their kernels. I will have look at the first option first

Can you do some checks on the connection setting (speed, duplex) witht he lacie kernel but also (if possible) with the standalone kernel by setting it on the router to this 10Mb/s half duplex

[fvdw]

attached a new standalone kernel, it is stripped and cannot be used for installtion of the firmware but it has a program to get info fromand setup the ethernet interfaces in more detail then ifconfig, the program is ethtool

When the kernel is running set again eth1 as given in one of my previous post.
Now give these commands to see what the setup of the interfaces is:

Code: Select all

ethtool eth0
ethtool eth1

on a nwsp2 you get this as output (for comparison)

root@(none):/ # ethtool eth0
Settings for eth0:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 8
Transceiver: external
Auto-negotiation: on
Link detected: yes
root@(none):/ #

to set parameters to 1000 Mb/s and full duplex do this

Code: Select all

ethtool -s eth0 speed 1000 duplex full

of course replace eth0 by eth1 when setting up eth1

If autoneg is off then you could switch it on by using

Code: Select all

ethtool -s eth0 autoneg on

to get a list of possible commands use

Code: Select all

ethtool --help

;) by the way a nice challenge to get this working !

[coelhonet]

Well, new round of tests... results on log attached.

So, something to help you on this debugging. Since I started using Linksys E900 as a switch between my notebook and Wireless Space ports (WAN and LAN) all connections cannot go above 100Mbits, since this E900 doesn't have any 1Gbit port.

I tried setting eth options via ethtool, but couldn't make it.

So, here are tests I tried:
1. Connected my notebook to E900 and Wireless Space WAN and LAN ports to E900 as well.
Results:
~ # ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes:
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
~ # ethtool eth1
Settings for eth1:
Supported ports: [ MII ]
Supported link modes:
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes

As you can see, 10Mbits half-duplex. My notebook NIC was set to 100Mbits full-duplex.

2. Forced my notebook NIC to 10Mbits half-duplex.
Results are same as 1.

3. Took off connections from E900 and connect Wireless Space WAN to my notebook and after that Wireless Space LAN.
Results are same as 1.

4. Leave Wireless Space with no network cable.
Results are same as 1... interesting enough Link detected is set to yes even when I took off network cable.

Between each test, I tried to ping 192.168.1.252 and 192.168.0.252.

As you can see, MII is only port supported.

Still challenging!

Thanks!

[fvdw]

:scratch mmm..apparently still something wrong with the ethernet drivers setup

I tried setting eth options via ethtool, but couldn't make it.

what errors did you get ? or did it leave the settings unchanged even after giving the commands to change settings ?

ps this will be followed up tomorrow evening, now it is time to go to bed