I have installed Debian squeeze on my Seagate dockstar,a while ago then successfully upgraded with apt-get to wheezy (7.1) last July. Now I'm trying to upgrade to 7.3. There about 40 packages that need to be upgraded. Things go smoothly through the first several of them, but after it upgrades libapt-pkg4.12 nothing works. Except for some bultin bash commands, any command I type at the shby egstern - Debian
So it really seemed as if uboot was unable to read the uboot-original-mtd0.kwb file even though it was readable from the Debian system. While booted in Debian, I copied the files to my desktop, made them into a jffs2 image which I copied back to the Dockstar. I erased the mtd2 flash and then flashed the jffs2 image to it. The Dockstar now comes up in Pogoplug mode when I remove the USB driveby egstern - uBoot
I have a Seagate dockstar on which I successfully installed Debian on a USB flash drive about a year ago. It has been working fine and I haven't booted the original firmware in a long time. My impression from a year ago was that I could boot the original Pogoplug firmware just by removing the USB drive and resetting the power. That no longer seems to work. The good news is that at the tiby egstern - uBoot
I have Debian reliably booting on my dockstar with netconsole enabled so I can see the uBoot messages. I'm familiar with passing arguments to the kernel with regular desktop linux installs, so I'm wondering where or whether the kernel receives boot arguments. I recongnize the root= option as a kernel parameter. The generic linux kernel may support a netconsole parameter netconsole paby egstern - uBoot
I went ahead and reinstalled the system. It took a long time after the reboot before it appeared on the network, but it finally became available.by egstern - Debian
The first time I tried it with the interface file unmodified, I couldn't even ping it. My router is set up so that if a DHCP request comes in from that MAC address it always gets a particular address, so I know where it is. This works fine when booted in the pogoplug system. It appears that when booted to Debian it wasn't completing the DHCP request. That's why I set it to a stby egstern - Debian
I could tell that my newly installed debian system had booted from the netconsole logs, but I couldn't ssh into it. I finally ran nmap on the static IP address I had configured it to use. It said all 1000 ports were closed. The device responds to ping. I am about to boot back to pogoplug and examine this with chroot, but could the default installation have forgotten to install a server?by egstern - Debian
The usb stick has partition 1 ext2 and partition 2 swap. If I can unwind the environment variables, what is happening is that the first attempt is a force_rescue_boot which attempts to load a rescue system from an EXT2 partition, then FAT16/32 partition. After that it tries a UBIFS partition. When that fails, goes to load the regular kernel from ext2. This is from fw_printenv: bootcmd=usby egstern - uBoot
I just installed Debian on a Centon 16 GB usb flash drive for use on an older generation Dockstar. When I went to reboot into the new install, it became clear that Debian hadn't booted, it was the original Pogoplug system. I activated the netconsole to observe the boot process and it looks like uBoot doesn't like the partition although the partition looks fine from the Pogoplug systemby egstern - uBoot