Looks like you're running Jeff's Rescue system. I think the quickest way to boot your Dockstar and get it running is to use Davy's Zyxel NSA320 rootfs from this post: http://forum.doozan.com/read.php?2,7806 Put this rootfs on a USB stick and I'm positive it will boot into Debian. After that, you can create Arch rootfs on another sitck and boot with it. Addendum: Itby bodhi - Rescue System
Aso helpful to post your output of: # cat /lib/udev/rules.d/75-persistent-net-generator.rules # cat /etc/udev/rules.d/70-persistent-net.rules Note that 75 and 70 will vary depending on your installation.by bodhi - Rescue System
Try install Squeeze first, and then apt-get update and apt-get dist-upgrade to Wheezy.by bodhi - Debian
moonman Wrote: ------------------------------------------------------- > I might have found an issue with this uBoot: > Either there's something wrong with the kernel > patch or uBoot doesn't pass proper arcNumber to > the kernel on some devices. There's was a post in > this where somebody could boot the kernel and the > arcNumber wasn't what he set iby bodhi - uBoot
@ian, I'm a little bit confused reading your post, do you still have problem? It sounds like installing "Squeeze, apt-get update, apt-get dist-upgrade" works for you on USB.by bodhi - Debian
Flooreus Wrote: ------------------------------------------------------- > Dudes, I am getting stuck with 'Gave up waiting > for root device'. It seems the fix is to set > rootdelay to 90 perhaps...but I can't find where > to do this? > > Any help is much appreciated :) > > Regards, > > Flooreus Root delay can be set with fw_setenv whilby bodhi - Debian
@TJ, Congrats! great to hear a successful recovery :)by bodhi - uBoot
Andre, The reason is udev persistent net rules. See this post: http://forum.doozan.com/read.php?2,10934,10935#msg-10935by bodhi - uBoot
Glad the problem was that trivial:) fstab is more suitable for fixed installation. On these plugs, I avoid that and rely on udev to automount all secondary partitions.by bodhi - Debian
@Keith, Did you set up 2 nc commands per Jeff's instruction? some of us needs to change the 2nd command slightly to get it working: nc -l -u -p 6666 & nc -up 6666 192.168.1.100 6666by bodhi - uBoot
TJ, dont power down or reboot if you don't have serial console. How far did it go when you run install install_uboot_mtd0 ? do you have the log you can post it here? Addendum: I did recover from this before, here is the thread - starting form this post: http://forum.doozan.com/read.php?3,5728,5748#msg-5748. I did a no-uboot-check installation knowing that it could brick the E02, andby bodhi - uBoot
@TJ, - What's your cat /proc/cpuinfo and uname -a show? ceboardver=PPV2 indicates that it is an E02. - dmesg will show if there are bad blocks. If it is indeed a Pogo E02 then if there is no bad block, you can run install_uboot_mtd0 with option "no-uboot-check".by bodhi - uBoot
Here is my guess (without seeing the original installation log) : there was some problem saving the original uBoot during the first time that you installed ALARM. IIRC, the orginal uBoot image is about 500 KB. Your console output showing the original uBoot image was loaded, but only about 18KB. Can you stop serial/net console during the countdown, and then try: run pogo_bootcmd See whby bodhi - uBoot
@Keith, Everything looks good to me except the size of the original uBoot image, it seems too small: ### JFFS2 load complete: 18084 bytes loaded to 0x800000 I would run the uBoot installation again (it won't hurt). And keep the installation log so you an go back to it and verify the installation activities related to pogo_bootcmdby bodhi - uBoot
The easiest tool to use for this that I've tried is Acronis. If you have Windows VM (which I did) or Windows box, you can clone the entire HDD boot drive to a USB stick and shrinking it at a same time. Of course the HDD has to be taken out and plugged into a Goflex USB base or a HDD dock.by bodhi - Debian
floodo1 Wrote: ------------------------------------------------------- > So, please, anyone that reads this thread, NEVER > EVER set to MTU to 4000 :) you wouldn't believe > how slow/laggy/buggy it made this thing! Yup, not just 4000, don't set MTU to anything other than 1500 on these plugs.by bodhi - Debian
Let see what's in your uBoot environment with the output of #fw_printenvby bodhi - uBoot
To use the delay_on delay_off, turn on timer first echo timer > /sys/class/leds/status\:green\:health/trigger after the timer is on, both delay_on and delay_off will be created and the durations can be adjusted. See this post above http://forum.doozan.com/read.php?2,1764,10787#msg-10787by bodhi - Debian
@maihoamv, Hey :-) we're never stop learning and helping each other in some way. Nice script! I'm sure I will use it someday.by bodhi - Debian
Are you sure the GoFlex Home NIC suports jumbo frame? (I don't recall coming across this info before). If indeed it does not have jumbo frame support, then it's typical that you would get worse performance using any setting other than 1500.by bodhi - Debian
floodo1 Wrote: ------------------------------------------------------- > CONFIG_NETCONSOLE=m > CONFIG_NETCONSOLE_DYNAMIC=y > > what does 'm' mean? 'm' means module. That indicates netconsole was turned on in Davy's image. Which plug are you booting this image with?by bodhi - Debian
Looks like you're booting with Davy's NSA320 image now? you can take a look at his config file and see if netconsole and netconsole dynamic flags are on. The kernel must be compiled with those 2 flags for the update-initramfs command to work properly.by bodhi - Debian
You can use Davy's NSA320 rootfs image (link in his signature), or here: https://www.dropbox.com/sh/nwt2kbvetvgvroo/aFClwe7aav/Kirkwoodby bodhi - Debian
What if you log in throu ssh and start it as background proc with the same command? Also, You can always daemonize the ezstream at certain run level you like, too. A quick test: ar a run level you want, creating Sxx script (cloning another Sxx script) and run ezstream from this script.by bodhi - Debian
Yes, after installing with Jeff's script, uBoot installation is done for the Pogo E02. You would need to setup netconsole with the above setenvs. After booting with the cloned rootfs, only arcNumber is need to be set if you have a rootfs that supports the Pogo E02. If your rootfs does not have Pogo E02 supports, then leave it as 2097. On the Pogo E02, the LED light can be controlled witby bodhi - uBoot
wilbert-vb Wrote: ------------------------------------------------------- > Would it be safe to use Bodhi's magical script to > install the netconsole enabled uboot on another > device, like the > PogoPlug-0E, which has the same cpu as > the > pink PogoPlug? For the Pogo Pink (E02), you don't need to do these manual steps! just run Jeff's install_uboot_mby bodhi - uBoot
toysareforboys Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > @Ron, > > > > It's unusual that your prompt is "ubit0-6:". > Did > > you run installation script from Pogoplug stock > OS > > ? how did you begin? Booting without USB, lby bodhi - uBoot
@Ron, It's unusual that your prompt is "ubit0-6:". Did you run installation script from Pogoplug stock OS ? how did you begin? Booting without USB, loged in with SSH? .... Also, why did you use the option "--no-uboot-check"? what happened before that caused you've decided to run the installation with this option? Normally, this option is not needed.by bodhi - uBoot
Yeah, wheezy install is having problem. You could install squeeze instead, and then apt-get update and apt-get dist-upgrade to wheezy.by bodhi - Debian