Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: Accidently set arcNumber=, now wont boot. - 13 years ago
@restamp & kraqh3d, Well, it is my turn :-) I've made the same mistake with the GoFlex Net (used but working perfectly). I've installed UBoot and booted with an old Dockstar Debian USB image (arch number 2097). Next, I set arc number to 3089 (bad move), and then was interrupted so did not start installation for the new Debian kernel immediately (I blame the wine!). Murphy'by bodhi - Rescue System
Re: Automount NTFS on Dockstar Debian - 13 years ago
kraqh3d Wrote: ------------------------------------------------------- > Hey Bodhi, I thought you would find this > interesting... I was more than happy with the > performance with the sync option so I never looked > at async mode. Until very recently, I'd only had > USB attached discs. This time I was using a flash > media (ie conforming to the USB Mass Storage sby bodhi - Debian
Re: Accidently set arcNumber=, now wont boot. - 13 years ago
restamp & kraqh3d, I'm intrigued by the idea! Take it a step further, let' say I have a mipsel-based device with an older UBoot, and I want to run mipsel Debian on it (with rootfs on a USB stick). Is this doable? I understand that will be a lot of works, but it would a good learning experiment that I'm interested in. bodhiby bodhi - Rescue System
Re: Accidently set arcNumber=, now wont boot. - 13 years ago
@restamp, It would be nice to be able to "restore the initial OS onto the device's internal NAND memory" :-) I've always been wondering at the point where Jeff's UBoot is checking for the rescue system, can the original Pogoplug be restored using the attached USB device? pardon my ignorance here, perhaps it's not possible to do that in some instances? U-Bootby bodhi - Rescue System
Re: Accidently set arcNumber=, now wont boot. - 13 years ago
restamp Wrote: ------------------------------------------------------- > Just curious: The original *nix that comes with > the Dockstar (and its associated devices) doesn't > require an arcNumber. (Does it?) I wonder if you > could put that kernel on a thumb drive and boot > that up, at least far enough to log in and reset > the arcNumber. > > And, when yby bodhi - Rescue System
Re: Latest Dockstars Deals, Post your findings here! (Updated 01 Jan 11) - 13 years ago
mycorunner, I have not set up the Pogoplug to go orange during booting. I only have the LED go green after Debian is running, and turn off when I shutdown. Likewise for a cold boot, it turns green after Debian finished the start up. You can see in the post above. For the Dockstar, I have the arch number set to 2998. And the LED files are in the /sys/class/leds directory as "dockstar&quby bodhi - Debian
Re: Pogoplug pink system command reduced - 13 years ago
kraqh3d Wrote: ------------------------------------------------------- > ... But it's not going to be > perfect because you've shoehorned a pre-compiled > custom kernel with modules into Debian. Ideally, > you should get the oxnas kernel source tree so you > can compile it and install it under Debian. ... --------------------------------------------------------by bodhi - Debian
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
oddballhero, Thanks for the well written instructions! without reading the completed description in that link, I'm leaning toward the first approach. It sounds like a pretty safe approach, since the fallback is using ArchLinuxARM, or going back to the original system to try again another day :-) I would be happy using ArchLinuxARM with a strong support community for it already. -bodhiby bodhi - uBoot
Re: Latest Dockstars Deals, Post your findings here! (Updated 01 Jan 11) - 13 years ago
@David, fw_printenv arcNumber If that does not work, then you have some path problem, so use the full path: /usr/sbin/fw_printenvby bodhi - Debian
Re: Latest Dockstars Deals, Post your findings here! (Updated 01 Jan 11) - 13 years ago
davidnewton Wrote: ------------------------------------------------------- > Bodhi: > > Thanks a lot. I will try this. > > BTW, I use the backup flash drive from my dockstar > to boot the pogoplug pink. Because of this, there > is no file/directory as > /sys/class/leds/plug:green:health/trigger, > instead, the it is > /sys/class/leds/dockstar:green:healtby bodhi - Debian
Re: Pogoplug pink system command reduced - 13 years ago
I think it's most likely one of the new pink Pogoplugs which are ARMv6 POGO-B03 - New Pink POGO-B04 - New Pink According to the Overview on Arch Linux ARM site: http://archlinuxarm.org/platforms/armv6/pogoplug-provideov3 If it's one of these new pink Pogoplug, don't install Jeff's Uboot, it's for these "normal" pink Pogoplug (ARMv5): POGO-E02 POGOby bodhi - Debian
Re: Latest Dockstars Deals, Post your findings here! (Updated 01 Jan 11) - 13 years ago
davidnewton Wrote: ------------------------------------------------------- > I got a pink Pogoplug and installed uboot on it > then use a backup flash drive for my dockstar > debian to boot it up (with the change for the > 70-per* and 75-persi* files described by many > here, btw, thanks all at lot). It works very well > as replacement of the old dockstar with 128MB moreby bodhi - Debian
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
restamp Wrote: ------------------------------------------------------- > Great news indeed! > > Thanks for being the guinea pig in this > experiment, bodhi, but hey, being a successful > guinea pig ain't all that bad, is it! > > Hope you get many years of use out of your > Pogoplug. restamp, not bad at all being a successful guinea pig, indeed! with yourby bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
Great news :-) It works as we hoped and expected. I modified the uBoot envs, setup netconsole on the Pogoplug Pink, started netconsoles from my Windows laptop, and then put in the Debian USB stick (backup image for the Dockstar), and rebooted. Also note that previously, I've missed one of the netconsole setenv statements. Caught that thanks to restamp diff listing above! Pogopluby bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
restamp, thanks for verifying the settings! I will try this tonight and report back.by bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
kraqh3d Wrote: ------------------------------------------------------- > @bodhi > > *After* writing the uboot environment to nand, you > need to set ethaddr, arcNumber, and then the > netconsole stuff. Your netconsole config doesn't > exist because you did it before writing the > environment. And it won;t work without ethaddr. kraqh3d, Thanks for the tby bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
... Continuing the post above with the verification of uBoot file! It does seem that the uBoot was successfully written to blocks 1-3 and 5. Pogoplug:/tmp$ /usr/sbin/nanddump -nof /tmp/uBoot1.dump -l 0x60000 /dev/mtd0 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00060000... Pogoplug:/tmp$ /usr/sbin/nanddump -nof /tmp/uBoot2.dump -by bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
@restamp, I have a chance to continue on with my pink Pogo today! Here is what I've done so far, and some questions arised, hope you can shed light to these :-) The following log shows these steps: Download the uboot.environment. Setup netconsole to get ready. And then flash uboot.environment. Do a fw_printenv to list all env variables. #download uboot environment Pogoplug:/tby bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
Thanks restamp! I'll keep you posted. - bodhiby bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
restamp, Looks like I was not successful in the attempt to do a force uboot installation. I'm getting closer to brick my pink pogoplug :-) I'm leaving box on for rescue if needed. The results so far: The force install was not successful: /tmp/install_uboot_mtd0.sh --noprompt --no-uboot-check parameter -bash-3.2# wget -P /tmp http://jeff.doozan.com/debian/uboot/install_ubooby bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
Thanks restamp! I will proceed with the override and report back. I'll keep my fingers crossed :-)by bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
Thanks, restamp! It's good advises. Hopefully, others will chime in with more. Suppose if I go ahead and force the override with the new UBoot, and then find out that the box is bricked. Can I recover in that case? or will it be bricked for good? Will the Nokia CA42 cable let me go back in and restore the Pogoplug FW?by bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
@restamp, I found some of your posts about how you dealt with this problem at http://forum.doozan.com/read.php?3,2417,2417#msg-2417 It seems the problem is exactly as yours before. Could you advise: should I rerun the installer using the prameter --no-uboot-check ? Below are the outputs of various commands that I've tried to verify if this is the same problem in your post. Thankby bodhi - uBoot
Re: Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
I've rebooted back into Pogoplug and ran dmesg. Is it the classic problem with bad block on mtd0 ? what can I do to proceed? Thanks -bash-3.2# dmesg [ 0.000000] Linux version 2.6.22.18 (bdietrich@brad-ux) (gcc version 4.2.1) # 44 Mon Aug 10 12:57:36 PDT 2009 [ 0.000000] CPU: ARM926EJby bodhi - uBoot
Pogoplug Pink fails in Validating Existing Uboot - 13 years ago
Guys, I'm installing Debian on a new Pogoplug Pink (it's an E02 version). I've opened the box to double check, making sure that it's actually an E02 (no SATA). I got the often reported error "Unknown uBoot detected on mtd0" when Jeff's script is validating the UBoot version and detected an unknown UBoot. Any idea how to proceed? perhaps I got a bad block onby bodhi - uBoot
Re: Latest Dockstars Deals, Post your findings here! (Updated 01 Jan 11) - 13 years ago
restamp Wrote: ------------------------------------------------------- > ...Heck, it is supposed to do what I'd > like to use it for, after all... Anyone have any > comments on using the Pogoplug as a, um, > Pogoplug? ROTFL! Seriously, from what I've learned, really the only thing it does is allow you to access files on your Pogoplug box away from home. Pogo serby bodhi - Debian
Re: Latest Dockstars Deals, Post your findings here! (Updated 01 Jan 11) - 13 years ago
restamp Wrote: ------------------------------------------------------- > ... > One question: The rooting doc on archlinuxarm.org > doesn't include the Dockstar warning about not > booting the Pogoplug on an internet accessible > network until you have deactivated the hbwd > process. Is that not necessary with the Pogoplug? > (It will save me some time and effby bodhi - Debian
Install HDD inside PogoPlug Pink - 13 years ago
Anybody tried to put a 2.5" HDD inside a Pogoplug Pink/Gray box? I'm wondering if it will fit?by bodhi - Debian
Re: Dockstar Debian USB does not boot after power failure - 13 years ago
restamp, You're right, of course! I've misread it, sounds like erez's problem is different than mine after a power failure. erez's system boots to pogoplug OS. Mine just hung :-). I tried pulling out the stick to let it boot back to pogoplug OS, and then replug the stick and do a warm boot, it still hung. So I just restore the USB image to recover (even though I assume fscby bodhi - Debian
Re: Dockstar Debian USB does not boot after power failure - 13 years ago
@restamp, I'm confused. Isn't it true when you pull out the USB Debian stick, the Dockstar will boot to PogoPlug (for those of us who have a simple Debian installation using Jeff's script)? so it is the Debian system that was corrupted by power failure. -bodhiby bodhi - Debian