I got this one for 59 USD . With shipping and tax it end up at around $69. It was a one day sale, but thing like this usually come around again on Woot http://computers.woot.com/offers/famous-maker-10-1-16gb-android-tablet-5. It's a HP 10 tabletby laprjns - Off-Topic
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > I'm eyeing the Mate one because > it's based on Debian and that would compliment the > Debian learnin' going on elsewhere (here). > All versions of MInt are based on Debian. I run the XFCE version of Salix on all my machines. Salix is a distribution based on Slackware. See hby laprjns - Off-Topic
Bodhi, First, thank you for all the work, help and advice that you provide to us in this forum. Can't imagine how time you put into this. > Which version do you > have installed? 2014.07-tld-2 > ... create an env > image to be flashed to NAND. This is what I want to do. I have a text file of my old environment, have installed uboot-tools on my Salix (Slackwareby laprjns - uBoot
Recently updated one of my Dockstars with the latest uBoot (2014.07) and also flash the new uBoot environment image. Now I can't boot into the Jeff's rescue system that is installed in flash. I do have a serial cable so I can connect and talk to it . I am able to use setenv to do a line by line reset of the environment variable, but would prefer to avoid typing and copy and paste errorby laprjns - uBoot
codler The env you posted doesn't look correct for a dockstar. Here's an example of a line from your posted env that doesn't appear in my dockstar uboot enviroment bootcmd=run bootcmd_uenv; run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset Also there are no rescue env lines in your uboot enviroment.by laprjns - uBoot
[ 16.043375] Starting init: /sbin/init exists but couldn't execute it (error -13) [ 16.052916] Starting init: /bin/init exists but couldn't execute it (error -13) [ 16.063365] Starting init: /bin/sh exists but couldn't execute it (error -13) Maybe this can help you get to the bottom of this error; http://free-electrons.com/blog/debugging-init-failures/by laprjns - Rescue System
I have a dockstar to which i would like to flash the latest uboot (2014.07). I do have a bad block as shown here; root@ds_167:/tmp# dmesg | grep -i 'bad' [ 16.227821] Scanning device for bad blocks [ 16.366403] Bad eraseblock 1806 at 0x00000e1c0000 Can I go forward with flashing? Thanks EDIT Never mind, figured it out myself and did a successful flash DockStar>by laprjns - uBoot
Quotedistro I have formatted a 4GB pen drive into ext3... Quotefw_printenv usb_rootfstype=ext2 Try setting the usb rootfstype to ext3: fw_setenv usb_rootfstype ext3by laprjns - Debian
Can someone confirm that netconsole is working in uboot.2014.01-tld-1.dockstar? I can't seem to get it to work. I have three dockstars, two running a 2011 daveygravey uboot and the third recently updated to 2014.0.01. I have no trouble connecting to netconsole with the two dockstars with the 2011 uboot, but for the life of me can get the new uboot to connect. It does, however boot into myby laprjns - uBoot
Post output of "cat /proc/cpuinfo". Also, is there a label on the bottom of the pogo's foot? If so what the model number printed on it.by laprjns - Debian
No, you don;t have to read the complete thread, looks like you've got the correct instructions.by laprjns - Debian
Looking back at the opening post, The poster has this uboot installed Quoteuboot U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvell-Dockstar/Pogoplug by Jeff Doozan I don't think the installed uboot can boot the 3.2 kenel. See this thread: http://forum.doozan.com/read.php?3,6965 Uboot needs to be update to the lastest versionby laprjns - Debian
dockstar Wrote: ------------------------------------------------------- > I uncommenting everything in > /etc/udev/rules.d/70-persistent-net.rules, but no > success. > The suggestion was to remove the file, not uncomment lines in it.by laprjns - Debian
Looks like its booting to me. Maybe it's not getting an ip. Try removing the /etc/udev/rules.d/70-persistent-net.rules.by laprjns - Debian
./install_uboot_mtd0.sh: line 82: wget: command not found ./install_uboot_mtd0.sh: line 85: wget: command not found Maybe try this. Edit the install script to change all "wget" to "busybox wget"by laprjns - uBoot
fonsty Wrote: ------------------------------------------------------- > 2. how to setup torrent client (is it possible > start downloading from work place over internet), As bodhi said, transmission. Here's one google hit off a search of transmission torrent command line Note that transmission has a small webserver, which allows you to add, start and stop torrents. &gby laprjns - uBoot
http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3397by laprjns - Debian
I use this wire wrap tool Radio Shack Wire Wrap Toolby laprjns - uBoot
QuotetoomyzoomMy ordering of a factory sealed Dockstar is on its way Interesting, didn't know that you could still buy them QuotetoomyzoomWhat sequence do I need to do? Updating the uboot first http://projects.doozan.com/uboot and install debian http://projects.doozan.com/debian, or the other way around? uboot first QuotetoomyzoomI had read from a few websites and forums that Iby laprjns - Debian
bodhi Wrote: -> :) now for some reason, the kernel is not booting. Are we sure that the kernel is not booting? Maybe it's not getting an IP. I suggest that they try deleting any persistent net rule in /etc/udev/rules.d/by laprjns - uBoot
Try using symbolic links using uImage and uInitrd as the link name. ln -s openwrt-kirkwood-uImage uImage ln -s openwrt-kirkwood-uInitrd uInitrd Of course you need to rename both the default uImage and uInitrd before doing this.by laprjns - uBoot
davidnewton Wrote: ------------------------------------------------------- > -rw-r--r-- 1 root root 4535899 Jun 13 10:30 > initrd.img-2.6.32-5-kirkwood > -rw-r--r-- 1 root root 4738236 Feb 17 2011 > org.uInitrd There appears to be two different uinitrd files. You could try using a symbolic link to boot the uInitrd ln -s boot/uinitrd.img-2.6.32-5-kirkwood boot/uInitrd oby laprjns - uBoot
maybe this http://projects.doozan.com/debian/by laprjns - uBoot
Maybe use this e2fsck.conf in /etc # Automatically added during the installation of the e2fsprogs package # because we detected you were installing on an ARM-Versatile platform. # These options stop e2fsck from erroring/requiring manual intervention # when it encounters bad time stamps on filesystems -- which happens on # the Versatile platform because QEMU does not have RTC (real time cby laprjns - Off-Topic
If you go through the reviews for the Pogo P21 on the J&R site, there are a couple of reviews (dated September 9th, 2012) that say that they received E02s. In fact one of them mentions it as a "Con" saying that the model doesn't match the boxby laprjns - Debian
Now that you mention it, no I bought my two from Buy.com, which is currently selling the P21 for $24.50 with free shipping. http://www.buy.com/prod/pogoplug-personal-cloud-media-sharing-solution-black/221688297.html When you add shipping to the J&R price, Buy.com is actually cheaper (at least for me). J&R 19.99 + 4.83 = $24.82 Buy,com $24.50 IIRC that&by laprjns - Debian
In case your still interested in getting a kirkwood base device, this Pogo P21 (E02) is available at J&R for $19.99 before shipping. This sale end today (Monday, October 8th. http://www.jr.com/pogoplug/pe/PGG_POGOP21/?JRSource=chemail.WeekendSale.1072012by laprjns - Debian
Looks like you need a new uboot. http://forum.doozan.com/read.php?3,6965 Quotedavygravy Kernel 3.2.y introduced a default setting for the kernel that affects kirkwood machines in particular, because of an unintended u-boot behavior with regard to the Level2Cache and decompression of the kernel image. Call it a latent bug in u-boot, a regression in the kernel, or whatever... the defconfig kirkby laprjns - Rescue System
If your still running uboot, either the old uboot ("Marvell>>" prompt) or the new uboot (don't recall what the prompt is) , the correct commands are printenv and setenv, not the ones starting with fw_ Anyway, it shouldn't be a problem if you successfully installed the uboot. Did you get through this instruction ok? QuoteNAND erase: device 0 offset 0x0, size 0x80000by laprjns - Rescue System