@beeryourself, Make a clone of your stick and change it back to Ext2 file system. Try booting with it first to make sure everything works. With Jeff's script, UBoot env for the rootfs type is set to Ext2. Afer you booted successfully into Debian, you can see that with fw_printenv. You can change the UBoot rootfs type to Ext3 and change your USB stick file system to Ext3. But I wouldby bodhi - Debian
@cyb, Concurred with what Davy said, I'd suggest that you label the rootfs that you want to boot with, and set the UBoot env to find it. # fw_setenv usb_init "run usb_scan; setenv usb_root LABEL=rootfs"by bodhi - uBoot
Assuming you have multiboot , a menu would be presented and wait for input, you have to select which system to boot anyway. So what is the benefit of not having to physically remove the USB stick? is there a use-case that you can describe?by bodhi - uBoot
Thanks Davy!by bodhi - uBoot
davygravy Wrote: ------------------------------------------------------- > NAND-flash uboot.kwb file, for flashing to NAND > Tested extensively on a Pogoplug Series 4. Works > well for me, but use at your own risk. > > Don't use on a Pogoplug Mobile. It will > require a slightly different setup. > > Will post full patch set in the coming weeks, andby bodhi - uBoot
Thanks gnexus! can you believe it's already sold out?!by bodhi - Allwinner A10
Take a look at this thread: http://forum.doozan.com/read.php?2,5775,page=1by bodhi - Debian
Debian method of upgrading (in summary): 1. Specify in apt sources.list what distribution to get the packages from. Below is "wheezy" example. Currently your 2.6.x is stable and it's "squeeze". So you should see the mirror name URL and "squeeze" in /etc/apt/sources.list # cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian wheezy main 2. Runby bodhi - uBoot
6pack Wrote: ------------------------------------------------------- > Q1 - Migrating old disk to new one > I have installed debian on a sandisk 4GB usb disk. > The debian partiton is 2GB and swap is 512MB i > think. > I want to move this to a larger 1TB usb hdd. I > made a 2Gb partition for rootfs with label rootfs, > 512MB saw with no label and rest might be ntfs/by bodhi - uBoot
I think you can just run Jeff's Wheezy install script and it should work. But I have not tried it (I have never used the UBit install scripts), so I can't say if it will detect the old installtion and deal with it successfully.by bodhi - uBoot
Kurlon has submitted this patch for 3.5.1: https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-kirkwood/archlinuxarm.patchby bodhi - Debian
I digged out an old spared SATA HDD, and put my current Debian rootfs on it. This is the info from my GoFlex Home booting with SATA as the boot drive (and the only drive). I shutdown and cold started several times (more than 5 times just to be sure). Hope this helps. netconsole output: U-Boot 2010.09 (Oct 23 2010 - 11:53:10) Marvell-GoflexNet by Jeff Doozan, Peter Carmichael Hit any keyby bodhi - Debian
Could you post your UBoot envs? I'm going to dig out the log when I still boot the GFHome with SATA. Hope I can find it :-)by bodhi - Debian
Snerler Wrote: ------------------------------------------------------- > Figured out how to use "fw_printenv." I had to put > this line in my /etc/fw_env.config: > > /dev/mtd0 0xa0000 0x20000 > 0x20000 > > This is the what I get by running fw_printenv: > > > baudrate=115200 > loads_echo=0 > ipaddr=169.254by bodhi - uBoot
@floodo, I looked at the kirwood initialization code briefly. Running the GF Home with GF Net initialization code could cause problem during SATA device registration (i.e. the GoFlex Net has 2 ports, the GF Home has only 1 port). Since 2nd device's data structure could contain garbage at some point, it's possible that the kernel choke while trying to register the 2nd SATA device. Jusby bodhi - Debian
Yeah, I got that from your other posts, you're actually running the GF Net using the GF Home hardware! I think that's why the heartbeat LED is available. EDIT: strange, I don't see the heartbeat in GoFlex Net LEDs, either!by bodhi - Debian
floodo, One thing I've noticed that both you and Sagitarius have arcNumber 3089, which is the GoFlex Net, not GoFlex Home (they are supposed to work for both boxes but there are differences ). You could try to set it to the correct one, which is 3338. I'm running the GoFlex Homes with Jeff's UBoot, arcNumber 3338, and a self compiled kernel (3.2.18), with USB flash as bootby bodhi - Debian
Which Debian version are you using (uname -a)? what is your arcNumber ? also, is your UBoot the latest (Davy's) or Jeff's?by bodhi - Debian
If you're using Ext2 for the SATA drive, then I would plug the SATA drive into a USB interface, connect it to another Linux box and check the file system with e2fsck to see if it was corrupted.by bodhi - Debian
What is your archNumber? is it 3338 ?by bodhi - Debian
To turn on the green LED, add controls statements to end of your /etc/rc.local, right before exit 0, as shown below: if [ -d /sys/class/leds/status:green:health ]; then echo default-on > /sys/class/leds/status:green:health/trigger fi if [ -d /sys/class/leds/dockstar:green:health ]; then echo default-on > /sys/class/leds/dockstar:green:health/trigger echo none > /syby bodhi - Debian
Vlad, I ran into the same problem with that patch compiling 3.2.18. And I could not find any patch that works. So I went back to the Arch Linux ARRM July 2011 patch for goflex Net and goflex Home (it does not have the Pogoplug V4, though). It would be nice to have a good up-to-date patch for Wheezy we can all use! I've attached the file here in case you want to take a look. Updateby bodhi - Debian
arcNumber 3119 Iomega StorCenter ix2-200by bodhi - Debian
@floodo1, Use the information about seting rootfs label and UBoot envs in optim's post (read a few posts before that). It's foolproof, you'll never worry about booting the wrong drive again! Besides, this rootfs label convention is used widely, good to follow it. -bodhiby bodhi - uBoot
That's really strange! the Dockstar is 2998. I'm wondering whether you have somehow inadvertenly flashed an incorrect UBoot?by bodhi - Debian
I saw you're booting OK now with 2998?. The last unsuccessful reboot could have been something to do with the network udev rules after you've done apt-get upgrade (I am guessing). If you're curious, you could mount the stick on a different box and look at the log files or the udev rules to see if it was reset or messed up.by bodhi - Debian
@funtoy, As optim said, your kernel probably does not have LED supports. arcNumber 2998 for Dockstar requires a kernel with LED supports. What is the output of uname -a and the content of your apt source list ? -bodhiby bodhi - Debian
cyb, You could download davygravy's kernel deb for 3.1.9 and use his config http://ppl.ug/cnl1R63ZOBM/ Note: In the linked post, I compiled natively on the Pogoplug E02. And leaving out "-arch armel" parameter works OK as mentioned. -bodhiby bodhi - Debian
Daniel, That's the expected behavior. Once you installed new UBoot and boot with USB/HDD drive with ALARM on it, it's a basic Linux system you're running. So you will need to install SAMBA to make the shared folders appear in the local network. You could now try the Debian rootfs provided by Dave (posted in this forum, username davygravy). Just create a USB stick in the sameby bodhi - uBoot
Daniel, iirc, with ALARM fresh rootfs, the login is user: root, password: root. You can ssh in using root/root. After logged in, change root password to something else, and to verify to make sure the success installation: do a reboot (warm start): shutdown -r now and then later shutdown: shutdown -h now then power up (cold start) -bodhiby bodhi - uBoot