As this seems to be the place for rebel Pi users, I just posted this 'over there'. It does have some Arduino content but it doesn't have a place in 'our' main forum. We'll see if it stays there......
Finally got my Pi which turns out to be one I ordered on-line way back and I thought hadn't 'flagged' with Farnell's site. and I left it. I have one I ordered later apparently coming this week...
Anyway on with the plot. I'm an old Linux hand (12 years +) and I set my Pi emulating a job I presently have a hacked ARM NAS box doing namely pulling data out of an Arduinio, potting graphs and providing a Web interface for my home monitoring system. :http://pluggy.is-a-geek.com
I intend to make a few for other people, and as the said hacked NAS box isn't available anymore I though the Pi would be an ideal replacement. I wouldn't have to hack it and its the right price point.
Its basically a collection of BASH shell scripts running as Cron jobs. I've spent 3 days trying to get it to work reliably, but it crashes constantly.
3 Different power supplies (no cheap nasty Ebay tosh either, one of them is a 2.5 Amp Dlink adapter that once belonged to a router I modified to feed the Pi via the GPIO pins), 2 different 8 GB SD cards (1 Samsung, 1 Sandisk). Its running headless but I have connected a Monitor & Keyboard. Everything works, no problem at least for a time. It reads stuff off the internet and the local network (wired ethernet port) as well as the Arduino which is plugged into on of the USBs.
It will run for a few minutes or maybe an hour and then dies. The lights stay on but it stops responding and stops updating log files at the same time. Sometimes I get a load of stuff in log files suggesting its having problems with the USB and network, sometimes not. Tried Debian
Squeeze, Arch Linux and Debian Wheezy, changing memory mix sizes, done Hexxeth's firmware updates, and all the tweaks I can find. They all do exactly the same on each power supply and SD card. If I leave the Arduino unplugged, it will usually run for several hours before crashing, but it still does. Tweaking the BASH scripts so it doesn't do so much stuff on the network/internet also helps. Not doing much on the network at all seems to keep it alive for extended periods, but that kind of defeats the object of the exercise.
Reading some of the developers comments on Github doesn't exactly inspire me with confidence, the finger seems to point at the (my paraphrase) unholy botch that is the USB/Ethernet hardware system and the closed source patched into opensource (or is it the other way around ) drivers for said hardware. I'm not expecting my next Pi when it arrives to behave any differently. I've tried playing with it with a GUI and browsing the internet and it works, but I generally get fed up of the performance on most sites before it gets around to crashing.
Any pointers ? But I've probably already tried it......