Guruplug eth1 defective?

[mabe42]

Hi,

I got my guruplug working using Debian 6 on the SD card and having a HD connected to ESATA. When using eth0 (connected to a gigabit switch) the plug reboots or freezes every now and then although I installed heatsinks and a fan on the chips (the board is remove from the original housing).

Before finally throwing the guruplug into the bin I wanted to try if the same behaviour appears if I connect the network to eth1 instead of eth0. However, I cannot get eth1 working. Did I forget to set any additional variable in u-boot?

Printenv shows:

Code:

U-Boot 2011.12 (Mar 11 2012 - 18:53:15)
Marvell-GuruPlug

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot:  0
Marvell>> printenv
baudrate=115200
bootargs=console=ttyS0,115200
bootargs_console=console=ttyS0,115200
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0
bootcmd1=usb start; sleep 3; ext2load usb 1:1 0x00800000 /uImage
bootcmd2=sleep 3; ext2load usb 1:1 0x01100000 /uInitrd
bootcmd_usb=usb start; ext2load usb 1:1 0x00800000 /uImage; ext2load usb 1:1 0xd
bootdelay=3
eth1addr=00:50:43:01:8A:D3
ethact=egiga0
ethaddr=00:50:43:01:8A:D2
machid=a76
stderr=serial
stdin=serial
stdout=serial
x_bootargs=console=ttyS0,115200
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_ethernet=ping 192.168.2.1
x_bootcmd_kernel=nand read.e 0x6400000 0x100000 0x400000
x_bootcmd_usb=usb start

Environment size: 772/131068 bytes

(some lines are not shown complete. This is due to the terminal program.)

However, Debian does not find eth1. During the boot process I get the following error:

Code:

Failed to bring up eth1.

In my /etc/network/interfaces both eth0 and eth1 are defined.
ifconfig eth0 gives a correct result while ifconfig eth1 results in an error:

Code:

root@johann:/home/matthias# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:43:01:8a:d2 
          inet addr:192.168.2.103  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::250:43ff:fe01:8ad2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2523 (2.4 KiB)  TX bytes:9146 (8.9 KiB)
          Interrupt:11

root@johann:/home/matthias# ifconfig eth1
eth1: error fetching interface information: Device not found

uname -a shows:

Code:

Linux johann 2.6.32-5-kirkwood #1 Sun May 6 16:57:51 UTC 2012 armv5tel GNU/Linux

Does anybody have an idea how I can activate eth1? Or is broken?

Regards,

mabe42.

[ppmt]

Have you tried to switch the port to use 100M rather than 1Gig

It could simply be that it is still too hot and the 1Gig issue is not fixed

[mabe42]

Hi,

at the moment, I don't have a 100MBit switch. Maybe in about a week.
However, the ethernet chip is pretty cool now. But since Debian cannot find eth1 I suspect that some variable in u-boot is not correctly set or that (part of the) ethernet chip is already roasted,

mabe42.

[mabe42]

Hi,
putting a 100MBit switch between the guruplug and the Gigabit switch doesn't change anything.

Code:

root@johann:/home/matthias# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:43:01:8a:d2 
          inet addr:192.168.2.103  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::250:43ff:fe01:8ad2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:97 errors:0 dropped:0 overruns:0 frame:0
          TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10796 (10.5 KiB)  TX bytes:16411 (16.0 KiB)
          Interrupt:11

root@johann:/home/matthias# ifconfig eth1
eth1: error fetching interface information: Device not found

Any ideas?
mabe42.