Re: pogoplugV2
On Fri, May 16, 2014 at 06:23:46PM +0100, RichardBown wrote:
> On Fri, 16 May 2014 16:07:17 +0100
> RichardBown <richard@g8jvm.com> wrote:
>
> > Hi Guys
> > Running Arch on my pogopig at the moment , using motion with a webcam.
> > It using a 8GB USB stick, I have, which I dont use, a 150GB HD in a
> > USB caddy.
> > Can I get Deb arm running on that, Arch is OK , but its got some
> > strange behaviour, and I'm reasonably familiar with Debian as I run
> > Mint on both machines here.
> >
> > What I'd like to do is,
> > continue using Motion on it, but also be able to use it for back up
> > from both the other computers, and maybe for my sons, but that would
> > mean some form of FTP, secure, remote access.
> > Am I right that it would run a little faster with a USB HD than using
> > the USB memory stick, I'd be able to a swap partion on it without
> > problems.
> > Or am I dreaming in cloud cuckoo land as normal :)
> > The pogopig is V2 , and running ARM5 arch at the moment.
> >
> > One thing that gave problems with Arch was it would only use 2.7GB of
> > the stick until I upgraded the kernel to later than 3.10.
> >
> > Is the install procedure similar, mount the usb hd and down load a
> > tarball and then unpack,,
> >
> > Some words of wisdom appreciated
> > Thanks
> >
>
> abit more
> I reformatted the HD ext3, with a 49 GB part, a swap and 100 GB partion.
>
> Plugged it in the pogopig
>
> got as far as this:- :(
>
> Pogoplug:/tmp$ ./kirkwood.debian-wheezy.sh
>
>
> !!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!!
>
> This script will replace the bootloader on /dev/mtd0.
>
> If you lose power while the bootloader is being flashed,
> your device could be left in an unusable state.
>
>
> This script will configure your Dockstar to boot Debian
> from a USB device. Before running this script, you should have
> used fdisk to create the following partitions:
>
> /dev/sda1 (Linux ext2, at least 400MB)
> /dev/sda2 (Linux swap, recommended 256MB)
>
>
> This script will DESTROY ALL EXISTING DATA on /dev/sda1
> Please double check that the device on /dev/sda1 is the correct device.
>
> By typing ok, you agree to assume all liabilities and risks
> associated with running this installer.
>
> If everything looks good, type 'ok' to continue: ok
> Connecting to projects.doozan.com (50.116.34.13:80)
> install_uboot_mtd0.s 100% |*******************************| 18406 --:--:-- ETA
> Installing Bootloader
> # checking for /usr/sbin/nandwrite...
> # checking for /usr/sbin/nanddump...
> # checking for /usr/sbin/flash_erase...
> # checking for /usr/sbin/fw_printenv...
> # checking for /etc/fw_env.config...
>
> # Validating existing uBoot...
> Block size 131072, page size 2048, OOB size 64
> Dumping data starting at 0x00000000 and ending at 0x00080000...
> Connecting to jeff.doozan.com (50.116.34.13:80)
> valid-uboot.md5 100% |*******************************| 1133 --:--:-- ETA
> ## Valid uBoot detected: [pinkpogo davygravy-2012-02-20-current]
> ## The newest uBoot is already installed on mtd0.
>
> # uBoot installation has completed successfully.
> mke2fs 1.41.12 (17-May-2010)
> Filesystem label=
> OS type: Linux
> Block size=4096 (log=2)
> Fragment size=4096 (log=2)
> Stride=0 blocks, Stripe width=0 blocks
> 3057824 inodes, 12227465 blocks
> 611373 blocks (5.00%) reserved for the super user
> First data block=0
> Maximum filesystem blocks=0
> 374 block groups
> 32768 blocks per group, 32768 fragments per group
> 8176 inodes per group
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
> 4096000, 7962624, 11239424
>
> Writing inode tables: done
> Writing superblocks and filesystem accounting information: done
>
> This filesystem will be automatically checked every 36 mounts or
> 180 days, whichever comes first. Use tune2fs -c or -i to override.
> Setting up swapspace version 1, size = 524283904 bytes
>
>
> # Starting debootstrap installation
> E: unrecognized or invalid option --no-check-gpg
> debootstrap failed.
> See /tmp/debian/debootstrap/debootstrap.log for more information.
>
> I wonder if this was why I put arch on it about 2 years ago ?????
>
> All the documentation on line is pretty ancient , well for linux it is.
>
> Any ideas, not sure if this list is even still active??
That is odd given the debootstrap version in Debian Wheezy (stable
release) supports that option. Where did it download one that didn't?
--
Len Sorensen
Reply to: