Yes, its 115.200 Baud 8N1 noFlow-Control like on the Sheevaplug.
I also can confirm the Gigabit-Switch-Problem after getting yesterday
a DLINK igabit-Nway-Switch my Guru+ did also reboot...back to my old
100MBit Switch the Ethetnet-Port does work like before.
For me it seems to be a driver-issue not a power-supply problem...but
Gigabit uses more lines inside the CAT5-Ethernet cable than 100MBit does

Normally your Guruplug should catch a DHCP-Adress via Lan if you do conenct him to the upper port (eht0)
(if you got an active DHCP-Server.. e.g. in your Router?)
Otherwise you should see a open WLAN calles Plug-and something of the MAC-Address of your Guruplug.

You could find the Quickstartguide at the URL
http://code.google.com/p/guruplug/downloads/list

Iam also find it curios to put the URL in the Quickstartguide which cant be found without the guide :-)
But Google and the homepage of the manufacturer of the Guruplug is your friend:
http://www.globalscaletechnologies.com/t-downloads.aspx

The login is root/nosoup4u

because of the fact that I didnt own a Gigabit-Switch I used my 10/100 Switch and my Network Interfaces do work also...no reboot....

I did use another ethernet-cable.... a 1:1 CAT5 yellow color

I disconnected the cable from eth0 and connected it to eth1, but I didnt get an IP-Adress from my router.
So I reconnected the cable back to eth0 and did get the DHCP-Address and voila I can Login via SSH.

PS: I now that it would be silly to connect booth ports to the same switch/hub :-)

Got no problem (Ok the heat of around 38 degree celsius) with a
- GuruPlug Plus
- 220V/50Hz (Voltmeter reads 216/217V)
- connected to the Ethernet at eth0 (upper port)

Did you connect the eth1 to the same switch/hub like the eth0?

Did you read something about the boot-sequence in this message:
http://plugcomputer.org/plugforum/index.php?topic=1647.msg9966#msg9966

My Mac is conneted via WLAN to the Guru+ and the Guru+ itself is connected via eth0 (Upper Port) to
a switch which is connected to my Fritz!Box Router.

In this combination the Guru+ is runnign now for 21Hour (around 76.000 seconds in /proc/uptime)

But has the Sheevaplug a bigger cooling system as the Guru+ ? Or is it the little bigger case with more
air in itself because there are less components?

In some cases if have seen USB-WLAN-Sticks getting real hot....so could it be possible that the heat isnt from the cpu
but from the WLAN-Chip?

So if anyone knows how to disable the WLAN (and then when its really getting no mor power) we should take a
look at the temperatur..... I have never seen a hot Bluetooth-Stick.

I attached a weather sensor for temperature on the Guru+ and it has now 37.8 degree celsius -
but feels much warmer/hot than my SheevaPlug with 27.9 degree celsius (both at around 220V/50Hz)

This day my Guru+ is running around 9 Hours (very hot for a plugcomputer) but
it still running:
sheevaplug-debian:/proc# uname -a
Linux sheevaplug-debian 2.6.32-00007-g56678ec #1 PREEMPT Mon Feb 8 03:49:55 PST 2010 armv5tel GNU/Linux
sheevaplug-debian:/proc# more uptime
30692.69 30546.20

The question is...will it run cooler if it is running on 110-120V....how about a stepdown-converter 220->110V?
Could this be a prolblem like on the Sheevaplug? (with or without external devices...where the WLAN/Bluetooth are the new (intern) external devices)?

I ordered my GuruPlug Plus in March and did get it now. They sent it at the 05/10/2010 from the U.S. and here in Germany
arrived me at the 05/12/2010...but I could pickup it yesterday at FedEx...

The last month I did get a email from them regrading some FCC-problems, after that they will ship. And here it is now :-)

Here in Germany my "power-meter" tells something about 216-217V 50Hz and my GuruPlug Plus is getting really warm and does a little
smell like very warm electronics :-((
My SheevaPlug which is running some weeks isnt hot as the GuruPlug :-(

Hope my GuruPlug doesnt die while he is getting so hot....

Iam running my Sheeva at 220/20V here in Germany.
But only with SD-Card and a USB-Soundcard (low Power Device).
An external USB-HardDisk should use his own power-supply.

Iam using the "old" iMic USB-Soundcard which I had from my old Apple Cube....
it working fine with debian

http://www.cartoonsupplies.com/product_info.php/cPath/38/products_id/74

Hi,
I installed  my SheevaPlug with debian 5.0.2 and the U-Boot for booting from
SDHC-card. This configuration is working fine, but now I got a thing that I didnt understand:

After booting from SDHC-Card (and without any USB-Stick) I got a mount-point which is
named /dev/sda1 and mounted at /
But I think at / should the SDHC-Card be mounted which resides at /dev/mmcblk0(p1/p2)

The problem with this sda-Mountpoint is, when I insert a USB-Stick it also will be mounted as
/dev/sda1

I could see with "fdisk -l" the USB-Stick at /dev/sda1 with the right size,
but when I try to use /dev/sda1 together mit /dev/sdb1 as a mdadm-RAID
the stick doesnt seem to be recognized as /dev/sda1

So how can I tell debian/the sheevaplug to start the FIRST USB-Stick counting at /dev/sdb1 or
mounting (in the mountlist) / at /dev/mmcblk0(p1/p2) ?

For this time my way around the problem is to put at first a not-used USB-Stick in my external 4 Port-USB-Hub (which doesnt do anything as /dev/sda1) and then I do put my (at this time) 2
4GB USB-Sticks for a RAID as /dev/sdb1 and /dev/sdc1


With this configuration I could create and use my USB-Flashstick-RAID at the SheevaPlug USB-Port
which gives me a 8GB /dev/md0-Device:

fdisk -l

Disk /dev/mmcblk0: 8068 MB, 8068268032 bytes
233 heads, 20 sectors/track, 3381 cylinders
Units = cylinders of 4660 * 512 = 2385920 bytes
Disk identifier: 0x00000000

         Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1   *           1        3100     7222990   83  Linux
/dev/mmcblk0p2            3101        3381      654730   82  Linux 
swap / Solaris

Disk /dev/sda: 259 MB, 259522560 bytes
255 heads, 63 sectors/track, 31 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

    Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          32      253386    b  W95 FAT32
Partition 1 has different physical/logical endings:
      phys=(1023, 254, 63) logical=(31, 139, 63)

Disk /dev/sdb: 4007 MB, 4007624704 bytes
32 heads, 63 sectors/track, 3882 cylinders
Units = cylinders of 2016 * 512 = 1032192 bytes
Disk identifier: 0x740f1bbe

    Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3882     3913024+   b  W95 FAT32

Disk /dev/sdc: 4007 MB, 4007624704 bytes
32 heads, 63 sectors/track, 3882 cylinders
Units = cylinders of 2016 * 512 = 1032192 bytes
Disk identifier: 0x14e965e0

    Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        3882     3913024+   b  W95 FAT32

Disk /dev/md0: 8013 MB, 8013742080 bytes
2 heads, 4 sectors/track, 1956480 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table


BTW: I dont know why the partition-tabel at /dev/md0 shouldnt be OK.
A fsck for this device did show that the device is clean.

Anybody else try to use a (USB-Stick)-Software-RAID on the Sheevaplug?

Bye
Guido

Hi,

the easyiest Way to do that (only Text-Mode) could be a cheap litte VGA-RS232-Controller:
Link
and 2nd Link

Additionally there is Keyboard In and TV-Out....great for Msgs/RSS or Instant Messaging :-))

Got the same problem with the USB-Port. The USB doesnt seem to "snap-in" like on USB-Port on other devices.
All my USB-cables doesnt click-snap-in like on my mobile-phone ror card reader.
But one of my cables fits a bit better, so that I can use the serial port.
From my point of view the usb is a bit to much recessed into the case.
The connector itself seems to be completly fine soldered to the pcb.

Hi,
did you try to use the settings/instructions from the Webpage from Martin Michlmayr?
His boot-arg's seems to be the same you used before, but you could check if the USB-Stick is created properly.

My best thing was to update the internal-flash ubuntu to a working one (getting updates, installing wget via apt-get)
and create the partitions with the sheevaplug (incl. unpacking the tar).

You could try to completly reset the enviroment with the detaila on this page

Or try another USB-Stick...some are not so "good"....which type do you got...?