• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / Linux distributions / Re: Clone USB rootfs to internal flash - Is this right? on: April 06, 2010, 05:21:38 PM
I was a Gentoo lover for years till they got to a period of not properly testing their releases of big things like libc which meant whole systems went down for days till someone came up with a patch, at that point I moved to a mix of Arch and Debian. I'd probably not try Gentoo on the Sheeva just because I imagine that compile time must be a killer but I would be interested to hear the way you set it up, it is always good to have more ideas even if they aren't used in the way they were originally explained.

As for patches, my job is security auditor/penetration tester so I'm one of the good guys who is always looking for security holes to squeeze through for clients so the thought of leaving an unpatched box on my own network isn't one I can consider! I've got into too many companies through small unpatched boxes in the corner that people had forgotten about to be able to ignore it.
2  Linux Stuff / Linux distributions / Re: Clone USB rootfs to internal flash - Is this right? on: April 06, 2010, 03:53:17 PM
So basically what you are saying is build the device, fix it to a purpose and then don't really touch it. That is kind of what I was thinking of, mine is just going to be a cheap NAS with a couple of USB disks hung off it.

My only worry is that at the moment it is looking like I'll mostly fill the NAND just installing the basic packages such as Samba and NFS. If I do then when patches come out and things need upgrading then it might quickly come to a point of needing to reflash just to get the new stuff on.

I think I might go for a half way solution, install most of it to NAND but keep /var on the SD, that way I've got space to play with on the NAND and spare space on the SD in case I want to drop anything else on it. Does that sound like a reasonable option?
3  Linux Stuff / Linux distributions / Re: Clone USB rootfs to internal flash - Is this right? on: April 06, 2010, 11:32:31 AM
Ye, there may be a bit of space left but as soon as I download a couple of packages the already compressed tarballs will fill the disk.

I don't see the point of moving from a 4G SD card to a 512M internal memory unless you are then supposed to map the SD card back in through mount points and if so then why copy the whole of its contents off onto internal rather than just the bits that are better ran from the internal disk.
4  Linux Stuff / Linux distributions / Re: Clone USB rootfs to internal flash - Is this right? on: April 06, 2010, 10:13:30 AM
I've just checked and the copy won't work as there isn't enough space

Code:
root@xx:/tmp/rootfs# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p2        1.8G  472M  1.3G  28% /
tmpfs                 251M     0  251M   0% /lib/init/rw
udev                   10M  120K  9.9M   2% /dev
tmpfs                 251M     0  251M   0% /dev/shm
/dev/mmcblk0p1         89M   19M   66M  23% /boot
ubi0:rootfs           462M   16K  457M   1% /mnt

That is with /var/cache/apt/archives/ emptied out.
5  Linux Stuff / Linux distributions / Clone USB rootfs to internal flash - Is this right? on: April 06, 2010, 09:54:52 AM
Finally got the Sheeva booting and got a base Debian installed and I'm coming to the end of these notes
http://www.openplug.org/plugwiki/index.php/Installing_Debian_To_Flash#Convert_internal_flash_root_partition_to_UBIFS
and I've got to this bit "Clone USB rootfs to internal flash"

Reading through this it reformats the internal 512M disk and then mounts it on /mnt, it then binds / to /tmp/rootfs to remove unwanted device files etc and copies all the files from /tmp/rootfs to /mnt.

Is this really the right thing to do, to copy all the files from the root on the SD card onto the internal disk including all the files in /var/cache/apt and any other bits that have been left around from the setup that aren't needed any more.

And what does this mean for the SD card that I installed on to, this now seems irrelevant as it isn't being mounted any more and isn't being used. Isn't the point of installing to SD card that you are running from a nice 4G card rather than the internal 512M.

I can kind of understand what is going on but it seems either to be missing an explanation as to why the way it is being done is better than leaving it on the SD card or some explanation as to what the role of the SD card is after all this or even why use the SD card at all, why not just install to the internal disk from the start?
6  Hardware and U-Boot firmware / Hardware / Re: Poll: Sheeva Plug Power Supply failures - does the mains voltage matter? on: April 06, 2010, 03:05:52 AM
I was going for a replace under warranty so didn't pop the lid, if this one goes though I'll pop it, take the photo then probably take a hammer to it and buy something more reliable next time.
7  Hardware and U-Boot firmware / Hardware / Re: Poll: Sheeva Plug Power Supply failures - does the mains voltage matter? on: April 05, 2010, 05:01:11 PM
The power supply in my first Sheeva died after a few months, plugged it in one day and it went bang and smelt of burnt electronics.

I called Globalscale to see what I could do and finally got permission to send it back. They acknowledged receiving it and then confirmed the power supply was dead then it took 2 months of me calling and emailing and then cc'ing in the sales and marketing departments before they got back to me again to say that they were sending out a replacement.

The new one has been OK so far but whenever I plug in the power lead there is usually a small spark which is a bit worrying.
8  Hardware and U-Boot firmware / Hardware / Re: Problem with system on sdhc-card on: April 05, 2010, 04:57:46 PM
I'm getting the same error when trying to install Debian to a 4G Lexar SDHC disk. I've got the partition type set to ext2 as I read that ext3 made this problem worse but it didn't help. Tried installing 3 times tonight.

I'll try another install tomorrow but before the installer starts I'll set the options from the bottom of this page to see if it makes a difference.

http://www.plugpbx.org/?p=350
9  Linux Stuff / Linux distributions / Re: latest debian kernel (2.6.32.11) fails to boot on: April 05, 2010, 03:07:47 PM
OK, worked like a charm. I'm sure I did exactly the same last night but hey, computers aren't the logical things that they are supposed to be and neither are humans at that time in the morning!

I'll see if I can find someone to report the missing reset to to get the wiki updated.

Thanks
10  Linux Stuff / Linux distributions / Re: latest debian kernel (2.6.32.11) fails to boot on: April 05, 2010, 02:43:39 PM
I tried it both with and without the reset as the set of instructions above that set in the howto don't include the reset. Both times it failed.

I'll give it another try now and see if it does it again though.
11  Linux Stuff / Linux distributions / latest debian kernel (2.6.32.11) fails to boot on: April 04, 2010, 04:12:31 PM
I'm following these instructions http://www.openplug.org/plugwiki/index.php/Installing_Debian_To_Flash and am trying to use the 2.6.32.11 kernel from here http://sheeva.with-linux.com/sheeva/ .

When I get to the bootm command I get:
Code:
Marvell>>    bootm 0x0400000 0x0800000
## Booting image at 00400000 ...
   Image Name:   Debian kernel
   Created:      2010-04-04  10:27:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1431196 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00800000 ...
   Image Name:   debian-installer ramdisk
   Created:      2010-04-04  10:27:18 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2616636 Bytes =  2.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0000020f).

Available machine support:

ID (hex)        NAME
00000690        Marvell DB-88F6281-BP Development Board
00000691        Marvell RD-88F6192-NAS Development Board
00000692        Marvell RD-88F6281 Reference Board
00000831        Marvell SheevaPlug Reference Board
0000085b        QNAP TS-119/TS-219
000009c6        QNAP TS-41x
00000915        Marvell OpenRD Base Board
00000939        Marvell OpenRD Client Board

Please check your kernel config and/or bootloader.

Reading other mentions of this error it says that their hardware isn't in the list but I'm using a normal SheevaPlug which I assume is the line with ID 831 in the supported list. If not the how can I tell what ID my device has and how can I get it to boot?
12  Linux Stuff / Linux distributions / Re: different distros and falling back on: November 02, 2009, 11:51:49 AM
Thanks, I'm not in a position to try it yet but I'll give it a go when I get round to dual booting and see what happens.
13  Linux Stuff / Linux distributions / different distros and falling back on: November 01, 2009, 11:29:44 AM
I've been looking at the howtos on installing different distros on the Sheeva, especially this one http://www.cyrius.com/debian/kirkwood/sheevaplug/install.htm and they all talk about modifying the boot parameters so the device boots from either USB or SD card by default. But I was wondering, is it possible though to set it up so that when I have the SD card plugged in then it will boot the distro on there but if I remove it it will fall back to booting the distro on the flash?

If not then the flash becomes a bit redundant if you have a large SD card as there isn't much point storing things on the flash when they can be stored on a removable device which can easily be removed to be backed up and updated remotely. What are people using the flash for after installing other distros?
Pages: [1]