• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  General Category / General Discussion / Re: Globalscale Technologie's one year warranty on: August 25, 2010, 12:42:15 AM
Sorry to resurrect a 'dead' thread, but just to follow up on this - I received a replacement PSU courtesy of New IT last week, and the Sheevaplug is up and running again.

It took about 6 months more than I think it should have done, but New IT were quite helpful - from what I understand the delay lay with Globalscale.

Also, if this happens to any other plug owners, replacing the PSU is a very easy job, so don't be worried about doing it yourself to save a few quid!
2  General Category / General Discussion / Re: Globalscale Technologie's one year warranty on: April 21, 2010, 08:20:41 AM
The Contact at Globalscale that is handling all power supply issues under warranty is Grace Wu gwu@globalscaletechnologies.com





Thanks! I have tried sending her an e-mail just now. We will see where that gets me.
3  General Category / General Discussion / Re: Globalscale Technologie's one year warranty on: April 21, 2010, 07:39:04 AM
I have just found this thread, and have been reading it with interest.

I bought a plug from New IT last October (on eBay - it was shipped to me on 9th October 2009, to be exact) and on Sunday (18th April 2010) it gave up the ghost, exhibiting symptoms of the all-too-common power supply issue. I never had it connected to a hard drive without external power, and instead had the sheeva's USB port connected to a powered D-Link USB 4-port hub, to which a powered HDD was attached, as well as a webcam.

I e-mailed New IT, explaining the situation, and they referred me to Globalscale, as per this page (http://www.newit.co.uk/index.php?id=14) on their website. I subsequently tried e-mailing Globalscale, and, same as the original poster, have received no reply, not even an acknowledgement.

It sounds like chasing Globalscale is a lost cause - does anyone know if there are any other avenues of hope open to me? I feel a little cheated considering I followed all the guidelines, it had very light use, and I believed I was covered by a years guarantee, yet it still died, and now I am being referred to a company who seems to have no intention of answering my e-mails.

Anyone got any ideas?
4  General Category / General Discussion / Re: sheevaplug can't start on: November 11, 2009, 03:20:02 AM
I believe that means it cannot find the serial device - so nothing has been written to the device.

Not totally sure, but I would start by ensuring that you can connect to the plug via the mini-USB connector. Then, close up PuTTy and then try running the installer again.

Maybe someone more experienced will come along soon and be able to give more specific instructions!
5  Linux Stuff / General Linux questions / Re: USB printer on: November 10, 2009, 08:41:17 AM
So can I access the CUPS management web from a different machine? So I type from my PC in my web browser for example (http://192.168.1.17:631)?

A very late reply, but just in case you were still wondering, yes, this is correct.

You will need to make sure that you are allowing connections from wherever you are, by checking in cupsd.conf.
6  General Category / General Discussion / Re: Where to buy in Europe? on: November 10, 2009, 08:37:29 AM
Another vote for New IT. I bought mine off them via eBay - flawless.
7  General Category / General Discussion / Re: sheevaplug can't start on: November 10, 2009, 08:36:30 AM
I am not sure whether it is related, but I had the same error message after trying to put the rootfs on the SD card.

My thread is here.

The long and the short of it was, I re-flashed using the Sheevaplug Installer, and all was fine again.
8  Hardware and U-Boot firmware / U-Boot stuff / Re: Sheevaplug: Verifying Checksum ... Bad Data CRC on: October 15, 2009, 01:04:44 AM
Hi birdman,

Thank you for the advice. Actually, just after I posted that reply, I read this.

So I changed my bootargs_root to match that, and now it boots from the SD card no worries. Good times! Funny how some nights I can get anything to work for the life of me, and then other nights I'm on a roll.

Thanks,

Matt
9  Hardware and U-Boot firmware / U-Boot stuff / Re: Sheevaplug: Verifying Checksum ... Bad Data CRC on: October 14, 2009, 02:32:26 PM
OK! So thanks to the instructions on the wiki and in the README, I have managed to reflash the plug with Sheevaplug Installer 1.0. I had quite a lot of hurdles to jump while I was trying to get it to work, but I think a lot of it stemmed from my inexperience with almost all aspects of the process.

In case it helps anyone else, I bought my Sheevaplug from New IT in the UK, and I did not need to change the vid and pid in the conf file (in fact, as it mentioned 'newer plugs', I changed them and it didn't work, so i had to change them back) to run the installer. I tried it on my girlfriends Vista laptop, but it was much easier to do everything on my Ubuntu box. I (stupidly) kept trying to connect to ttyUSB0 to see the console, then realised the port I wanted was ttyUSB1. Once I realised all the mistakes I was making, it went great!

But all good news - it works again. I will no doubt try and move the rootfs to the sd card again sometime, but for the moment I'll stick with 512Mb and see what I can do.
10  Hardware and U-Boot firmware / U-Boot stuff / Sheevaplug: Verifying Checksum ... Bad Data CRC on: October 14, 2009, 04:53:01 AM
Hi Everyone,

Just to warn everyone, having only been introduced to Linux within the last 2 years, and coming to the plug from the NSLU2, which (at least at the moment) seems a bit simpler, I am very much a beginner with this type of thing, so please be patient!

I bought a Sheevaplug from New IT off eBay the other day, and it arrived yesterday. My NSLU2 has been overloaded beyond belief and it is just too slow, so I was looking for something with a bit more grunt to act as a home server running things like CUPS, Transmission, Samba, Apache and maybe a webcam.

I was worried about the relatively small amount of space on the plug when it arrived. I decided to move the root file system to an SD card I had (Sandisk 4Gb card) so I followed the guide on the wiki here.

When I got to the part to do with UBoot, as per the guide, I changed the bootargs using the command (I did check that my bootargs were initially set the same as those in the guide, and they were, so I thought it would be fine):

Code:
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
And then checked it using printenv bootargs. All looked well, so I typed 'boot' and the plug booted. I watched it boot, and a couple of [failed] notices came up, but Debian (mine has Debian on it as standard? I am not sure) booted, I logged ina dn all was fine. I also SSHd in to prove to myself that it wasn't broken. All worked well.

I then repeated the process (shut down, got into UBoot, setenv bootargs etc) and included saveenv at the end, as I figured the changes I made were good.

That seemed to go well. Then I typed 'boot'. I got this:

Code:
Marvell>> boot
NAND read: device 0 offset 0x100000, size 0x400000
Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-03-19   9:18:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2106696 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

This seems to happen without fail every time I turn it on. I tried setting the bootargs back to what I had originally, with this line:

Code:
setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none

But it still does the same thing upon boot.

So I have a couple of questions - first of all - did I go wrong anywhere obvious? I would love to fully understand what caused this, as well as how to fix it.

Second - how can I fix it? I have found a couple of other threads which sound similar, and they suggested restoring via USB - so this would mean following these instructions?

I would be grateful for any help anyone can offer - as I say, I am a bit of a newbie, but eager to learn from my mistakes!

Thanks,

Matt
Pages: [1]