Don't know if it was worth the effort rather buying a new one, but a colleague still had a PSU from which he cut the cables/connector from a GuruPlug. He built in a fan so he needed the space which was occupied but the plug's PSU and he replaced it with an external one.

Thus I had to unsolder the connectors off my broken one and solder them back to his PSU: and it works :-)))

At least it was some fun doing some crafting again ;-)

PS: there's a BOM at http://www.openplug.org/index.php/us/resources/downloads?func=fileinfo&id=82, however I'm not sure if it fits to my Plug as the BOM may be valid first the first HW revison, only? I have that bigger gap between the USB and Eth port (BTW: is that free space between those two ports an option to solder in an eSATA connector?  )

And I just noticed that we can order spare PSUs at either Globalscale [1]  (or NewIT [2]). But isn't that a shame that we'd have to pay for it!! 

Sounds a bit like the theme of the following (German) Limerick:

Ein Uhrmacher aus Wesselburen
verschenkte en gros seine Uhren.
Er erntet den Lohn
seiner Investition
und lebt jetzt von Reparaturen !

However Globalscale didn't give their Plugs for free ...

[1] http://www.globalscaletechnologies.com/p-36-sheevaplug-power-supply.aspx
[2] http://www.newit.co.uk/shop/proddetail.php?prod=SheevaPlugPSU

Agree, I'd like to. Would you or sb else can tell me which are the problematic parts to replace?
At least the capacitor (1) looks a bit fried, but also that other part (2) also marked with a red rectangle in the attached jpg.
thx!

Think I got it somehow and somewhat working, now.
However I don't fully understand what's going on during the devices initialization phase:

[ 7545.111094] usb 1-1: new high speed USB device using orion-ehci and address 2
[ 7545.261502] usb 1-1: New USB device found, idVendor=9022, idProduct=d660
[ 7545.268241] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 7545.277552] usb 1-1: configuration #1 chosen from 1 choice
[ 7545.371008] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 7545.379562] usb 1-1: firmware: requesting dvb-usb-s660.fw
[ 7545.403096] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 7545.409572] dw2102: start downloading DW210X firmware
[ 7545.437008] usb 1-1: USB disconnect, address 2
[ 7545.541109] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 7545.548959] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 7545.558031] DVB: registering new adapter (TeVii S660 USB)
[ 7555.801088] dvb-usb: MAC address: 40:40:40:40:40:40
[ 7555.871079] Invalid probe, probably not a DS3000
[ 7555.876041] dvb-usb: no frontend was attached by 'TeVii S660 USB'
[ 7555.883975] input: IR-receiver inside an USB DVB receiver as /devices/platform/orion-ehci.0/usb1/1-1/input/input0
[ 7555.899307] dvb-usb: schedule remote query interval to 150 msecs.
[ 7555.905488] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 7555.914371] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
[ 7555.925346] usbcore: registered new interface driver dw2102
[ 7556.221092] usb 1-1: new high speed USB device using orion-ehci and address 3
[ 7556.371495] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
[ 7556.380857] usb 1-1: New USB device found, idVendor=9022, idProduct=d660
[ 7556.387611] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7556.394791] usb 1-1: Product: DVBS2BOX
[ 7556.398560] usb 1-1: Manufacturer: TBS-Tech
[ 7556.405274] usb 1-1: configuration #1 chosen from 1 choice
[ 7556.414425] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 7556.422954] usb 1-1: firmware: requesting dvb-usb-s660.fw
[ 7556.439905] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 7556.446422] dw2102: start downloading DW210X firmware
[ 7556.571101] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 7556.577307] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 7556.586625] DVB: registering new adapter (TeVii S660 USB)
[ 7566.831087] dvb-usb: MAC address: 00:18:bd:5c:4a:f0
[ 7566.951085] DS3000 chip version: 0.192 attached.
[ 7566.955725] dw2102: Attached ds3000+ds2020!
[ 7566.955730]
[ 7566.962037] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
[ 7566.971447] input: IR-receiver inside an USB DVB receiver as /devices/platform/orion-ehci.0/usb1/1-1/input/input1
[ 7566.982359] dvb-usb: schedule remote query interval to 150 msecs.
[ 7566.988489] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 7677.281117] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 7677.289164] usb 1-1: firmware: requesting dvb-fe-ds3000.fw
[ 7677.335611] ds3000_firmware_ondemand: Waiting for firmware upload(2)...

"Luckily" bought two SheevaPlugs from Globalscale back in Sep 09, of one was more or less sitting idle at my desk as a spare (if the first would fail).
The "production" plug was sitting in the somhow cool basement running 24/7 as a NAS.
As I made my "development" work switching from Ubuntu to Debian on the spare plug the productive one got replaced the spare plug a few weeks ago as just replaced them during the OS swap to minimize the "downtime".
Thus I noticed that the as by then productive plug starts to show the PSU symptons.
Luckily it still boots, but it takes up to three minutes till it becomes stable: http://www.youtube.com/watch?v=OgCVQIBcmeQ

I guess it is, though my actual findings are based on Debian Squeeze (Linux Sheeva 2.6.32-5-kirkwood #1 Sat Dec 11 05:09:52 UTC 2010 armv5tel) to which I recently switched:

HTS Tvheadend (SVN-R5780) couldn't find the TeVii S660 DVB-S2 device neither, but I recalled, that as I still had a TerraTec Cingery DVB-T USB-adapter in my drawer (because -T coverage/signal strength is very poor where I live ).

However attaching it to the SheevaPlug I can see it, now :-) (thou no channels as to the above issue).

root@Sheeva:~# lsusb
Bus 001 Device 002: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T² DVB-T Receiver
root@Sheeva:~# dmesg|grep usb
[   23.721107] usb 1-1: new high speed USB device using orion-ehci and address 2
[   23.871492] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[   23.880415] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[   23.889859] usb 1-1: New USB device found, idVendor=0ccd, idProduct=0038
[   23.896610] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   23.903796] usb 1-1: Product: Cinergy T²
[   23.907819] usb 1-1: Manufacturer: TerraTec GmbH
[   23.913714] usb 1-1: configuration #1 chosen from 1 choice
[   30.794180] dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm state.
[   30.806476] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   30.840589] input: IR-receiver inside an USB DVB receiver as /devices/platform/orion-ehci.0/usb1/1-1/input/input0
[   30.855847] dvb-usb: schedule remote query interval to 50 msecs.
[   30.862727] dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully initialized and connected.
[   30.872657] usbcore: registered new interface driver cinergyT2

So I might have 'simply' a driver issue with the S660 which I have to nail down as my next task ...

Hm, same with 2.6.35.10 #2

Device is attached

root@Sheeva:~# lsusb
Bus 001 Device 002: ID 9022:d660
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

However not recognised?!

root@Sheeva:~# dmesg | grep usb
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usb 1-1: new high speed USB device using orion-ehci and address 2
root@Sheeva:~# dmesg | grep dvb

cbxbiker61 et al.,

I saw folks had set up their SheevaPlug with DVB-* USB-device as e.g. streaming servers. [2,3]

I thought giving it a try with a TeVii S660 DVB-S2 box [3], but though I think I got HTS TVheadend [1] properly compiled and installed on the plug, it can't find any "TV card".

Is that kernel suitable for this exercise (compared to the settings in [5]) or should I use another one?
--
thx & cheers

[1] http://lonelycoder.com/hts/tvheadend_overview.html
[2] http://plugcomputer.org/plugwiki/index.php/Webcams
[3] http://plugcomputer.org/plugwiki/index.php/DVB-T
[4] http://www.linuxtv.org/wiki/index.php/DVB-S2_USB_Devices
[5] http://crichton.homelinux.org/~marc/downloads/sheeva-config-2.6.32.2

James, interesting. Is this a special USB hub (or would "any typical" powered USB do)?

sorry, u*x noob question:

I tried to follow the instructions given in the Readme.txt and here, however I ran into the following error trying to build wxWidgets under Debian Squeeze (2.6.32.5) on my SheevaPlug.


Any idea what went wrong and how to overcome this? - thx

As a delay of 5 worked for me so far (former Ubuntu), I just kept it the same for the Debian boot for now, (though still configured as an option in u-boot, but more or less obsolete, now.)

setenv bootargs_sd 'console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw ip=a.b.c.253:a.b.c.1:a.b.c.1:255.255.255.0:Sheeva:eth0:none'
setenv bootcmd_sd 'setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x8000000'
setenv bootcmd 'run bootcmd_mmc; run bootcmd_nand; run bootcmd_sd'

However I had another issue lately, thou I don't know if it's related to the delay value (as far as I can recall I at least never had these kind of issues on the plug running with Ubuntu).

I found the throughput to be very bad lately (log-on/off with the Windows Roaming Profiles was really a pain). I first suspected my network causing these problems, but in the end I found the I/O to the USB-HDD too small and I guess it was just mounted via USB1.1 (when I ran "dmesg | grep usb" I think think I saw a message telling me something like the USB-HDD could do better and I should use an highspeed USB-Hub?).

So I rebooted this morning and the issue seems to be gone for now.


However it leave me with two questions:

i) which tool / command shall I use to monitor the "link state" of my USB connection?
ii) may I use the newer kernels compiled and hosted by ctxbiker on my Squeeze install or is this a bad idea?

http://www.plugcomputer.org/plugwiki/index.php/Installing_Debian_To_Flash#Convert_internal_flash_root_partition_to_UBIFS !?

Hi birdman,

On the weekend I amended the bootcmd_mmc u-boot environment variable given her http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html with an "usb start"

setenv bootcmd_mmc 'mmcinit; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd; usb start'

but it does not mitigate the situation:

Last login: Sun Nov 21 16:51:42 2010
root@Share:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mmcblk0p2          746848    607824    101088  86% /
tmpfs                   257788         0    257788   0% /lib/init/rw
udev                    254952        76    254876   1% /dev
tmpfs                   257788         0    257788   0% /dev/shm
/dev/mmcblk0p1          124743     22009     96078  19% /boot
root@Share:~# mount -a
root@Share:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mmcblk0p2          746848    607860    101052  86% /
tmpfs                   257788         0    257788   0% /lib/init/rw
udev                    254952        76    254876   1% /dev
tmpfs                   257788         0    257788   0% /dev/shm
/dev/mmcblk0p1          124743     22009     96078  19% /boot
/dev/sda1            1922858352 1424940752 478382444  75% /mnt/sda1

But of course your hint was worthwhile a new try (in the meantime I also saw some of your post where you ran into a similar situation :-)

Thus I modified the u-boot variables as follows:

setenv bootargs_console 'console=ttyS0,115200 rootdelay=5'
setenv bootargs_mmc 'mmcinit; ext2load mmc 0:1 0x01100000 /uInitrd; ext2load mmc 0:1 0x00800000 /uImage'
setenv bootcmd_mmc 'setenv bootargs $(bootargs_console); run bootargs_mmc; bootm 0x00800000 0x01100000'
setenv bootcmd 'run bootcmd_mmc; run bootcmd_nand; run bootcmd_sd'

And indeed, looks better, now :-)

BTW: as my plug's in the basement I always have to pick it up and bring it to my PC to have access to the u-boot environment.
So I though being lazy and considered the use of the sheeva-uboot-tools (https://code.google.com/p/sheeva-uboot-tools/), dl them and compiled my own version.

However, though the sheeva-ubootenv-print worked OK, sheeva-ubootenv-save seem to have screwed the config, as another print claimed about CRC? errors and the plug didn't came after reboot. When I picked it up I could access u-boot, but it just had default settings. Luckily I had a backup at hand and could restore my previous settings, so got it working again (though there was another small intermezzo with the kernel complaining about an unknown Manufacturer ID, but I can't recall exactly how did overcome this ;-)

Hi, already had look here http://plugcomputer.org/plugforum/index.php?topic=1083.0, but as this is too old I dare to open a new thread.

I recently switched from Ubuntu 9.04 to Debian Squeeze with my SheevaPlugs (booting from a 1GB SD).
Attached to the plug is also a 2TB Hitachi USB HDD, which contains my data, e.g. shared via cfis/samba.

Debian's working quite well, however when rebooting the plug, the attached USB drive usually doesn't get mounted. That's new to me as it worked fine using Ubuntu.

This is the entry in /etc/fstab:

#/dev/sda1 /mnt/sda1 ext3 rw,usrquota 0 0
UUID=<USB's ID> /mnt/sda1 ext3 rw,usrquota 0 0

Mounting it on the CLI "mount /dev/sda1 /mnt/sda1 works.

Strangly if I power cycle the plug the drive gets mounted.

Any idea what this might be. Haven't tried it yet, but may an "usbstart" during the u-boot initialization improve the situation?

Just migrated my setup from Ubuntu 9.04 to Debian Squeeze during last weekend (planned for longer but it took me while to carry over my samba PDC config as I'm not too familiar with U*X).
So far everything seems to be running smoothly though I still have to tidy my smb.conf (which originally comes from an unslugged NLSU2).