Ok--all worked well for u-boot: U-Boot 2014.01-tld-1 (Mar 17 2014 - 22:04:15) Seagate FreeAgent DockStar Thanksby lyzby - uBoot
>You already got netconsole set up Well, I'd never used netconsole before. How nice. Here's the starting output: U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvell-Dockstar/Pogoplug by Jeff Doozan Hit any key to stop autoboot: 0 Here's cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xcby lyzby - uBoot
Thanks for the response. fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_installed=0 rescue_set_bootargsby lyzby - uBoot
I have a dockstar with Gorgone's Debian Squeeze Heavy 2.6.37 installed. I'd like to update the u-boot, and the configuration looks correct in accordance with the checks you suggest in post 1. However, I don't have flash_erase installed. So I have two questions. 1. Should I be able to safely install with what I have on the dockstar? 2. How do I install flash_erase (and anyby lyzby - uBoot
Davy, What is the rationale for limiting the flash size to 32mb? Can you make notes on your process for building this available?by lyzby - Rescue System
Ok, my post above may just indicate a hardware problem on that particular Dockstar, as shown by the "Bad Data CRC". I just installed the "2011.12" U-Boot and V3 rescue images on a new Dockstar, and it boots perfectly well into the rescue system. Thanks for this good work.by lyzby - Rescue System
I tried flashing the rescue system, https://dl.dropbox.com/u/1015928/Kirkwood/rescue/RescueV3-for-Major_Tom.tar.gz with the following commands from the thread: flash_erase /dev/mtd1 0 0 nandwrite /dev/mtd1 uImage-mtd1.img flash_erase /dev/mtd2 0 0 ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y All went as expected, but when I reboot, I get the following: U-Boot 2011.12 (Feb 12 20by lyzby - Rescue System
Answering my own question here. I thought DavyGravy had addressed how to deal with this problem of flashing with tftp via serial, and I found where he had. First, "MANUAL Directions for Upgrading U-Boot" here: http://forum.doozan.com/read.php?3,6965 By carefully following these steps, using the uboot for the Dockstar, I was able to reflash my uboot. I was using Ubuntu on a laptby lyzby - Debian
I have a dockstar with the original uboot but a corrupted linux. I have serial access and a tftp server. I tried one method of reflashing to stock with serial cable ( http://archlinuxarm.org/forum/viewtopic.php?f=30&t=1323 ). Flashing worked via tftp, but I get a CRC error upon rebooting. I have copies of the original mtd0, 1, 2, 3, but haven't seen how to restore them. I'vby lyzby - Debian
I flashed this uboot to my dockstar using Jeff's script, and it appeared to flash ok. When I reboot, I get the following message when trying to start the kernel from usb (watching via serial): Loading file "/boot/uImage" from usb device 0:1 (usbda1) 1432436 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 4702937 bytes read ## Booting kernel frby lyzby - uBoot
I tried booting a dockstar which has been running a Doozan debian with the image in post 1. I put it in a 750M partition on a 1G flash drive with a 250M swap partition. There was no uInitrd--is that correct? It gets to the point of "booting the kernal", but then nothing happens. Is there something evident that I am doing wrong? U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvellby lyzby - Rescue System
Yes, I do have serial console, a backed up usb drive, and other dockstars to help in any recovery. I'll reseach some more, but any guidance would be appreciated.by lyzby - Debian
When I try the above I get the following: # dpkg -i linux-image-3.2.0-1-kirkwood_3.2.2-1_armel.deb Selecting previously unselected package linux-image-3.2.0-1-kirkwood. (Reading database ... 15828 files and directories currently installed.) Unpacking linux-image-3.2.0-1-kirkwood (from linux-image-3.2.0-1-kirkwood_3.2.2-1_armel.deb) ... dpkg: dependency problems prevent configuration of linby lyzby - Debian
On a Dockstar I did "apt-get update", "apt-get upgrade", the change to wheezy in sources.list, "apt-get update", "apt-get dist-upgrade", but I still have a 2.x kernel: Linux dock85 2.6.37-dockstar #6 Mon Jan 17 01:55:44 CET 2011 armv5tel GNU/Linux I looked into runing mkimage as in the kraqh3d post above, but have no /boot/vmlinuz or /boot/uInitrd, juby lyzby - Debian
I don't know if it would relate to this hardware, but Peter Gunn posted some software tweaks which cleared up pops and clicks on his system. I don't have the link, but you could search for it.by lyzby - Debian
Or, for gorgone's "heavy" kernel, this works for me (from pogoplug prompt). mount / -rw -o remount cd /tmp wget http://ss4200.homelinux.com/dockstar/gogo-dock.sh chmod +x ./gogo-dock.sh export PATH=$PATH:/usr/sbin:/sbin ./gogo-dock.shby lyzby - uBoot
Thomas,, That looks like the unit I used, and has the right model number. I don't remember if I had to do anything other that what my post said: apt-get install firmware-ralink That and setting up /etc/network/interfaces something like this. auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.2.87 netmask 255.255.255.0 auto wlan0 #iface wby lyzby - Debian
Have you made the pogoplug system read/write before trying what is suggested? mount / -rw -o remountby lyzby - Debian
Be careful with the serial cable. Many PL2303 usb-serial cables that I have had use high voltages which will damage the Dockstar serial connection. You want something like the Nokia CA-42 3.3-volt cable (which does use the pl2303 chip).by lyzby - uBoot
In addition to the 3Com 3CRUSB10075 mentioned above by petergunn, I got the following working today after doing "apt-get install firmware-ralink": TP-LINK TL-WN321G DLINK DWL-G122 No-name brand G Ralink dongle Also NETGEAR WG111 after doing the following: mkdir /usr/local/lib/firmware wget -O /usr/local/lib/firmware/isl3887usb http://daemonizer.de/prism54/prism54-fw/fw-usbby lyzby - Debian
Pardon, but how is the new version from post 157 to be installed on a dockstar running an older build of your implementation? So far I have only installed using http://ss4200.homelinux.com/dockstar/gogo-dock.sh from the pogoplug prompt. I'm glad to see the ch-340 usb serial driver in this version. Thanks for all your work.by lyzby - Debian
Colin--perhaps a new thread would be in order, but ... Are you sure you have a 3.3-volt cable and not a 5-volt one. You obviously have TX from the dockstar wired correctly, since you are getting the Marvell> prompt. 3.3-volt Tx will work on a 5-volt cable, but 5-volt RX will blow the dockstar's receiving circuit. So you can see what the dockstar is sending, but it doesn't see wby lyzby - Debian
Coda: After power cycling my Comcast cable modem, which fixed some other problems, I tried gorgone's script again. Failure. Tried again. Success! So sometimes, persistence may pay off. Thanks to Jeff and Gorgone for their work. The Dockstar is a sweet little device.by lyzby - Debian
I also am having problems and also have Comcast as a provider. Different downloads fail on different attempts. With multiple attempts with Jeff's and Gorgone's scripts I finally got Jeff's to install on one Dockstar and Gorgone's on another, and so far many attempts on another have all failed. Frustrating, but it's clearly not the fault of the scripts when the downloadsby lyzby - Debian
I was running from the pogo bash prompt. I was able to download manually from the site, but the script failed. After I manually downloaded the three files, the script ran for a long time but eventually failed. This morning I ran it again, and it ran to completion, down to asking me to reboot. But it rebooted into pogo system. When I power cycle (several times) it only boots to the pogo sby lyzby - Debian
@gorgone: I tried your gogo-dock.sh script, but got errors in downloading from ss4200.homelinux.com, like the following: # checking for /sbin/mke2fs... # Installing /sbin/mke2fs... Connecting to ss4200.homelinux.com (193.16.217.9:80) wget: server returned error: HTTP/1.1 404 Not Found Connecting to ss4200.homelinux.com (193.16.217.9:80) wget: server returned error: HTTP/1.1 404 Not Fouby lyzby - Debian