The Ctera CloudPlug product (http://www.ctera.com/home/ctera-cloudplug.html) has been out for awhile now, but yesterday smallnetbuilder.com made mention of Ctera's press release unveiling new services and firmware updates to the CloudPlug (http://smallnetbuilder.com/nas/nas-news/31118-ctera-rolls-out-new-cloud-storage-service-appliance-features). When I went to the manufacturers site and saw references to the NEXT3 filesystem which enables snapshots, I was intrigued. A quick Google turned up this:

http://sourceforge.net/apps/mediawiki/next3/index.php?title=Main_Page

Looks like they have working on this for a while.

I do not work for Ctera, just found this and thought it would be interesting to share

If I am not mistaken, the newest Apple Airport Extreme could be included on the list. According to this review:

http://www.smallnetbuilder.com/wireless/wireless-reviews/30972-extremely-disappointing-new-apple-airport-extreme-briefly-reviewed

It has the same processor as the Sheevaplug...

I am just saying that the processor in the photo in the smallnetbuilder review looks like it says Marvell, not Samsung...

I don't think the iConnect is based on a Samsung processor...

http://smallnetbuilder.com/nas/nas-reviews/31094-iomega-iconnect-wireless-data-station-reviewed

That's the only review I have found that opened the unit. It is hard to tell by the board photo, but it looks like their may be a pin header for the console port as well in the lower right-hand corner.

Interesting thread about this device here (although with a comment from the author of the blog post):

http://ubuntuforums.org/showthread.php?p=8969498

So the mystery is solved. If it wasn't for the poor exchange rate to the U.S., I would have already ordered one from you :-)

The drivers for Windows are here:

http://www.ftdichip.com/Drivers/VCP.htm

Couple of questions...

What distro are you using?

If you tail /var/log/messages after you plug the Sheeva in via USB do you see anything that indicates it is detected? Sometimes the cable isn't fully seated into the plug itself...

The device connects to regular POTS lines to provide connectivity to the traditional phone network. If you want to plug a regular analog phone into a voip network, you need an ATA (analog telephone adaptor).

A more elegant solution if you want to use regular analog phones would be this:

http://rowetel.com/ucasterisk/

It is an embedded device that runs Asterisk and can have either FXO of FXS modules installed (FXO is for phone lines, FXS is for phones). Uses about the same power as the Plug and is open hardware and software.

Shameless plug for myself, I wrote about it a little while back for LWN.net:

http://lwn.net/Articles/357809/

I posted about this device a while back:

http://sangoma.com/products/hardware_products/analog_telephony/usb_fxo.html

http://www.telephonyware.com/telephonyware/products/sangoma-usbfxo-u100.html

Perhaps a new section of the forum is needed for commercial products to announce availability?

I believe Martin's instructions are correct:

"Please note that you may have to replace /uInitrd and /uImage with /boot/uInitrd and /boot/uImage depending on the way you installed Debian. By default, Debian will create a separate boot partition, so the full path to the kernel is /uImage. However, if you choose to put everything on the same partition, you have to use /boot/uImage."

As this is the exact behavior I saw when I used the installer. It did in fact create a separate boot partition formatted as ext2 with the rest of the filesystem in another ext3 partition.

Perhaps then you have the uboot parameters incorrect?


 

Just throwing my own two cents in...

Have you tried checking the usb cable itself and maybe trying a different one? Many people have had issues with the cable coming loose or not connecting securely. I didn't have the issue with my plug, but another one I setup had a 'loose' connector. Swapping the cable solved my issue there.

Just a thought :-)

I would leave the stick formatted as FAT32.

Following these instructions from the Installer package:

5.  Copy the following to the USB stick root directory:
      a. Root file-system (packed into rootfs.tar.gz)
      b. Kernel (named uImage)
      c. Kernel modules (packed into modules.tar.gz)
      d. Init ramdisk (uImage.initrd)

You should only have those four files in the root of the thumb drive. Looks like you might have been missing one...might want to re-try with the original USB stick first before swapping one out needlessly.

Just a guess, but try another thumb drive? Looks like the plug has problems reading from it...you are trying to install to a USB stick, correct?