• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / Kernel / Re: GuruPlug Server Plus and 2.6.35 on: August 22, 2010, 10:40:46 AM
Apparently the bad block detection code is busted in 2.6.35.
Quite some fixes have landed for that since 2.6.35 was released:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/mtd/nand/nand_base.c;h=a3c7473dd409c51f9dd1b215eb09673a3fd858e8;hb=HEAD

I haven't tried them all yet, and I don't know yet whether the tip of linux-2.6.git does work for the GuruPlug's NAND chip again.

But does that mean that apart from this bug kernel.org kernels can be used on the GuruPlugs?

Thanks...

    Dirk
2  General Category / Marvell PlugIN - Free Your Imagination / Re: A more robust digital archive: ZFS on plugs on: August 15, 2010, 02:08:18 AM
The combination of:
- large data collections
- error rate of typical HD
- file system not designed for robustness

creates the need for a device providing better data survivability than current NAS at a reasonable operating cost.
(my own testing shows 45 W/h for ATOM based 2 HD NAs and 115 W/H for Core2Duo 6HD NAS, translating to as many $ or Euro/year, ergo 45 $/y or 115$/y in electricity)

Tonido and Dockstar/Flexstar cloud approach work a lot like QNAP/Synologic backup-over-network systems (don't know about thecus offer).
but do not address data quality.

The only one Filesystem i am aware of that provide much better data survivability is ZFS.
EDIT: from either HD failure or from operator error (through snapshot)
The other one is btrfs (ZFS may be a small step ahead, though Wink).

Quote
Can any plug (including the annonced 2.0 Ghz part) run ZFS (either Freebsd 9.0 or a light Opensolaris distribution such as EON) ?
Well, FreeBSD folks suggest to run ZFS preferably on 64-bit machines with enough RAM. So while it could be possible, it most likely isn't fun.

BTW: My plug happily runs Linux from btrfs formatted ESata.

Bye...

    Dirk
3  Linux Stuff / Kernel / Re: Kernel SD root device with/without attached eSATA on: June 15, 2010, 12:01:11 AM
Any ideas how to reference the SD card independently  from eSATA?

What you want is to reference the filesystem on the SD card, which can be achieved by using filesystem labels. See http://www.ibm.com/developerworks/linux/library/l-boot-rootfs/index.html.

HTH...

    Dirk
4  Linux Stuff / Kernel / Re: Cannot tftp-boot custom kernel, but only factory default kernel on: May 23, 2010, 02:47:31 AM
Didn't really recognize this right away:

Quote
To hack around the problem, I edited include/generated/mach-types.h and swapped the entries for 2659 and 2601.
That gave me an uImage I can boot Smiley

This resulted in a booting kernel for me, too. So the question remains: Would upgrading U-Boot solve that problem?

Bye...

    Dirk
5  Linux Stuff / Kernel / Re: Cannot tftp-boot custom kernel, but only factory default kernel on: May 22, 2010, 08:29:05 AM
Two things to add:

1) I didn't use a cross compiler, I compiled the kernel directly on the plug.
2) Just saw there's also another thread (only a couple of hours older) about this: http://plugcomputer.org/plugforum/index.php?topic=1669.0. Maybe we should switch to this one.

Bye...

    Dirk
6  Linux Stuff / Kernel / Re: Cannot tftp-boot custom kernel, but only factory default kernel on: May 22, 2010, 08:23:40 AM
I'm facing the same problem just now. Here's my command sequence:

Code:
Marvell>> setenv serverip 192.168.1.1
Marvell>> setenv ipaddr 192.168.1.90
Marvell>>  tftp 0x6400000 /tftpboot/uImage
Using egiga0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.90
Filename '/tftpboot/uImage'.
Load address: 0x6400000
Loading: #################################################################
         #################################################################
         #######################################
done
Bytes transferred = 2480660 (25da14 hex)
Marvell>> setenv bootargs console=ttyS0,115200 root=/dev/sda2 rootfstype=btrfs rootflags=subvol=root
Marvell>> bootm 0x6400000
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.33.2-dirty
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2480596 Bytes =  2.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Note that I have attached an external HD via eSata and formatted it with btrfs (hence the custom kernel, the preinstalled only has it compiled as module). That's also the reason for using root=/dev/sda2 (sda1 is swap).

Bye...

    Dirk
7  General Category / Success stories / Why Samba? on: May 05, 2010, 11:57:51 PM
Another aspect worth mentioning here is that both plugs have Samba installed and access my NAS devices directly to save and read files across a gigabit network. In other words, both plugs have Debian installed on NAND (not SD or USB) and save torrent data or read FLAC (or whatever else) solely across my network to my NAS devices.

You didn't mention any Windows client so I'm curious as to why you're using Samba instead of NFS, which would be the "natural" choice in a pure Unix environment. Do your NAS devices not provide NFS?

Bye...

    Dirk
8  Linux Stuff / General Linux questions / Re: Jabber Server on: May 01, 2010, 12:14:21 AM
Has anyone managed  to get an xmpp/jabber server working on their plug?

I know this is a bit late (just registered to this forum) and maybe more than what you want, but anyway: http://www.citadel.org is a comlete, easy to use groupware solution with builtin xmpp server. Debian has packages for it, even for ARM.

Bye...

     Dirk
Pages: [1]