New Device Issues

[penjuin]

Juanisan, is it a gigabit ethernet adapter? 10/100 works fine on the guruplug.

[Juanisan]

Gigabit USB?

Is there such a beast?

sheevaplug-debian:~# ethtool eth2
Settings for eth2:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 16
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pg
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes

I have had problems with the original Sheeva plug ethernet port in a NAT setup.  These USB/Ethernet adapters saved my patootey.  The original adapters gave me many kernel errors.  These adapters saved me big time.

[penjuin]

While I don't doubt that you had errors, these particular ones surface only when using a gigabit ethernet switch. It could potentially be the interaction between the wireless drivers and the drivers responsible for gigabit ethernet that is the problem.

For the record, when I plug in gigabit ethernet, I see this over and over and over:

Code:

U-Boot 2009.11-rc1-00602-g28a9c08-dirty (Feb 09 2010 - 18:15:21)
Marvell-Plug2L

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MB
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
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
No link on egiga1
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 02 3A 00
1 Storage Device(s) found

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.32-00007-g56678ec
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2789756 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[mzdaniel]

As others pointed out, it seems there is a faulty interaction between the ethernet connecting at 1G and the custom drivers on the debian root filesystem that come by default in guruplug. As having 1G connectivity is most important for me, I simply commented  the last line in /etc/rc.local to avoid loading the wireless driver, and now the guruplug is stable.

Code:

#/root/init_setup.sh

[Yrch]

Hi there!
I'm also having this 1G-LAN  issue. I have two cables plugged in, where eth0 is 100MBit and eth1 is 1000MBit. When the 1000MBit one is plugged in while booting the plug just resets. Plugging it in after booting is working fine.
I hope this will be fixed soon.

I simply commented  the last line in /etc/rc.local to avoid loading the wireless driver, and now the guruplug is stable.

Now I tried this too. After that it resets when inserting the 1000MBit one even when finished with booting.

[tno]

I am pretty sure this is a heat problem and nothing else.
I did some tests with the following results:

• The plug can boot and operate with both 1 GBit and Wifi for several minutes if the device starts at room temperature (not plugged in before)
• The difference in energy consumption between 100Mbit and 1000Mbit is approximately 1 Watt
• If you deactivate Wifi energy consumption drops by approximately 0,7 Watt
• while running stable it is not as hot as while crashing/rebooting
• After crashes/constant reboots there is a very faint smell of burned electronics if you put your nose right next to the openings
  

In conclusion I assume that cooling is just not good enough for stable operation when using the more energy extensive features at the same time (Wifi, Gigabit).