• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / Hardware / Re: Does anyone use eSATA via USB on normal Sheeva? on: August 03, 2010, 05:40:22 AM
I don't see a reason why this should not work. It's the same as every USB to SATA converter that is in every USB drive enclosure and I have never heard of any problems with USB drives not being supported.
2  Hardware and U-Boot firmware / Hardware / Re: Sheeva with eSata HUB - Will it work? on: August 03, 2010, 05:37:22 AM
Linux and at least the Guruplug Server Plus support port multipliers, so I think the eSATA Sheeva will probably as well. Unfortunately there is very few documentation about this and Linux needs to support the chipset of the Port Multiplier and I was not able to find a list which chipsets are supported with which kernel version.

I bought a RAID1 enclusure with a Sil5744 chip hoping it would work and in fact it does. http://plugcomputer.org/plugforum/index.php?topic=1738.0 indicates that the SiI3726 of your eSATA hub is supported although the post does not say if it's attached to a Sheeva or Guruplug.

One other thing: If you want to do software RAID5 with a plug you should be aware that RAID5 is computing intensive, so performance might not be that stellar. A RAID5 enclosure should help, but is of course more expensive than just a port multiplier.
3  Hardware and U-Boot firmware / Hardware / Re: How much better are the eSata transfer rates over the USB transfer rates? on: August 03, 2010, 05:21:23 AM
The performance increase should be substantial (depending on the drive, of course). USB maxes out at about 20-25MB/s.  With eSATA you should get nearly the "native" performance of the attached drive. 100MB/s should be no problem.

You can find some eSATA numbers at  http://plugcomputer.org/plugforum/index.php?topic=1783.0 for a RAID1 enclosure.
4  General Category / General Discussion / Re: MPD issues on the Guru on: June 27, 2010, 01:35:33 PM
Mmmh. I have MPD working just fine. Ogg Vorbis and MP3 play without problems.

This is my audio_output section:

Code:
audio_output {
        type            "alsa"
        name            "U0xccd0x77"
        device          "hw:0,0"        # optional
}

My asound.conf also contains those bluetooth settings, but I don't have an entry for pcm.!default or ctl.!default.

Maybe it get's better when you remove the additional settings in mpd.conf and asound.conf.

Good luck,
Lars
5  Linux Stuff / Linux distributions / Re: how can i update to kernal 2.6.33-X-Kirkwood on: June 22, 2010, 03:52:22 AM
It looks like your boot arguments are not suitable for the installed kernel. There are basically two different methods to boot a system. One is to compile every driver you need for booting into the kernel directly. This is ok for fixed hardware like the sheevaplug or if you compile the kernel for you PC at home. Then there is the possibility to just compile basically everything else as a module and generate an initrd (Init RAM disk). After the kernel boots it starts the RAM disk which is loaded by the boot loader into RAM, which needs to contain all drivers necessary. This is a good way for distributions to support nearly every hardware out there.

So, why do I tell you this? Because it seems that your old kernel was using an initrd, but the sheeva.with-linux.com one does not need one, as all drivers necessary to boot should be compiled in. But your boot arguments still load the initrd from the old kernel. You need to drop that part from your boot arguments. Just remove 'ext2load mmc 0:1 0x01100000 /uInitrd;' from bootcmd_mmc and hopefully it should be fine.

Good luck,
Lars
6  General Category / Application ideas and development Q/A / Re: Remote Access to Sheeva (like teamviewer) through Command Line on: June 18, 2010, 08:11:45 PM
I have no experience with teamviewer, as I don't like third parties to have access to my data.

But if you have a computer available that is always on (or at least when you want to access your plug) and it either directly accessible or you have control over the NAT router, you can use some ssh tunneling magic. Let's call this computer 'middleman'.

sheeva# ssh -R 2222:localhost:22 user@middleman
(Leave this running all the time. This opens a tunnel from middleman port 2222 to sheeva 22 (ssh port).

If you want to access your plug:
client# ssh -L 2222:localhost:2222 user@middleman
(This opens a tunnel from your client port 2222 to middleman port 2222.)
Now you can ssh into your plug:
client# ssh -p 2222 user@localhost
(Where 'user' is the username on your plug.)

Port 2222 is just some arbitrary number. Actually it's two arbitrary numbers as you could put the second tunnel on a different port.

The second tunnel is necessary as ssh is configured to only permit access to ssh tunnels from localhost. If you configure your middleman server to permit remote computers to access ssh tunnel you can skip the second step and ssh directly into your plug:
client# ssh -p 2222 user@middleman
(Where 'user' is again the username of your plug.)
But getting your ssh-daemon on middleman to allow this is not trivial IIRC. I tried this once although I don't remember which direction I wanted to tunnel and at least on Debian I would have had to recompile ssh.

Another possibility is to use 'grunt' or something similar if your plug is receiving emails. (See http://www.debian-administration.org/articles/515)

Good luck,
Lars
7  General Category / Success stories / linux-vserver on GuruPlug on: June 10, 2010, 10:27:19 AM
As I want to use my GuruPlug as router and server I tried to partition the OS into several vservers (http://linux-vserver.org/) and much to my surprise it worked fine.

So it's possible to have a secure setup with the root server being the router/firewall and seperating off all internet-accessible services into seperate vservers. Overhead is minimal.

The kernel patch for vs2.3.0.36.30.4 applied without errors even with the guruplug patches on kernel 2.6.34.

Unfortunately the userspace utils (util-vserver) are not in the Debian repository for arm as there is a porting problem with dietlibc which is used by the Debian package. But as dietlibc is optional (though strongly recommended) it is possible to compile the utils without it. The latest stable version did not compile, but version util-vserver-0.30.216-pre2883 did.

Everything works fine so far with two vservers (one with an Asterisk VoIP-PBX and the other one as a test machine) except vserver-stat does not return any data, which is not nice but acceptable.
8  Linux Stuff / General Linux questions / Re: SdCard speed probleme with automount (Guru+) on: June 08, 2010, 07:07:23 PM
What options for the filesystems are in use when you mount it manually or the system mounts it?

You can check the options with cat /proc/mounts
9  General Category / General Discussion / Re: Using the SheevaPlug as a fileserver? on: June 06, 2010, 05:51:26 AM
Yes, you can work on your files on the plug directly. Throughput should be sufficient for almost all documents (Yes, video editing is the one exception that pops into mind. Watching videos should be fast enough.). I haven't tried this personally, but you should be close to the maximum possible USB throughput which should be somewhere between 20 and 25 MB/s if you are using a Gigabit network. I have a guruplug with the HD attached via eSATA but only connected via 100MBit/s ethernet so that's the limiting factor for me and I get a bit over 10MB/s throughput.

If you also want to have a disconnected operation you should have a look an Unison: http://www.cis.upenn.edu/~bcpierce/unison/
With some clever configuration of ifplugd the laptop should be able to sync automatically once plugged into your home network. Then you just have to remember to sync before you disconnect (or sync regularly via cron).

Lars
10  General Category / General Discussion / Re: Strange Boot Happenings on: June 02, 2010, 05:49:30 PM
1.     Setting the system clock.

I'm using chrony (aptitude install chrony). It is an NTP server and client and tries to keep the clock free from drift even if not connected to an NTP server. I don't know what it does diffently, but my boot messages have the right timestamp even after a reboot and with no online connection. So the Guruplug must be able to maintain the time somehow. (Of course, I deleted the hard coded date line from /etc/rc.local)

Quote
2.      ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken failed!

         What is causing this error?

You won't believe it, but the error is caused by the non-zero sized paniclog :-) Just delete the file and you should get rid of the error.

Quote
3.      ping failed; host 192.168.2.1 is not alive

         Why is the plug trying to ping 192.168.2.1 during boot?  BTW, I'm on network 192.168.0.0

I was wondering this as well, but once I removed it the ethernet ports stopped working in Linux. So I guess this ping to an arbitrary address initializes the ethernet ports.

Lars
11  General Category / General Discussion / Re: ehternet devices have no MAC on: June 02, 2010, 05:37:34 PM
Hello,

I don't think the missing MAC addresses are connected to where you boot from. I got hit by the same problem and it started working for me once I initialized the ethernet ports from U-Boot. To do this you have to send a ping from both ethernet ports like the standard bootcmd does:

Code:
setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet};

(with x_bootcmd_ethernet=ping 192.168.2.1) (The IP does not need to be anything sensible.)

Include this into your boot code and the ethernet ports should work within Linux. At least they did for me.

Hope this helps,
Lars
Pages: [1]