I written this script to mount any disk with label after the kernel has booted to rc.local. This is useful to handle the mounting of HDDs that had timed out error during boot. This script should be excuted in /etc/rc.local. cat /etc/rc.local root@Dockstar:~# cat /etc/rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure thaby bodhi - Debian
Olaf, Perfect! download this kwboot and run it from the Raspi: kwboot md5: 0efd011bdb244436e432a8de33e639a1 It's ARM.So it should work whether it's kirkwood or not.by bodhi - uBoot
MG, Thanks for reporting your observation. Did all kernel 3.12.0 versions tld-1, 3, 4, and 5 behave the same way with low write speed in your test? did you install each one from version 3.3.2 or just progressively going from 3.3.2 to 3.12.0-tld1, tld-3,….? And could you post the commands and outputs in your tests here? Thanks!by bodhi - Debian
johnklos, The mtd parts are the same as stock Pogo OS. So the only change is mtd0 where uBoot is. This is so that if you want to restore to stock, only mtd0 is needed to be restored. And the new uBoot should boot stock Pogo OS with correct uBoot envs. Not sure what can you do since I'm not familiar with NetBSD. To verify that the new uBoot works OK, you can use this rootfs on a USB orby bodhi - uBoot
Besides the GoFlex Net, do you have another Kirwood plug? or any ARM 32 based Linux box?by bodhi - uBoot
davidedg, Yes. The 2013.10 uBoot builds for GoFlex Home, GoFlex Net and Pogo E02, that I've uploaded, support GPT booting and other latest features (the official uBoot does provide GPT, I only needed to turn it on). But we don't have the patch for NSAxxx so I can't build one. I hope eventually we will. If the NSA325 V2 ever available in US then I hope to get my hand on one anby bodhi - Debian
The stock uBoot does not have advance scripting capability, so I don't think "if" statement would work, IIRC what WarheadsSE said. However, a limited uBoot envs scripting capability would be able to work for this purpose. If you set it up to look for /boot/uImage on HDD first, and it fails, it will execute the next env to look for /boot/uImage on the USB, and then if it fails, iby bodhi - Debian
StephenR0, I looked at this IDE identification code (to identify the hard disk) a week ago. Very ugly to read (the authors said so :) I put a debug statement in to print out all relevant values and looked at them. They just did not seem right. I'll have to postpone this for a few weeks.by bodhi - uBoot
QuoteGeert I am still curious to learn if anybody ever got booting into the original Pogoplug OS going from Davy's U-boot on the Mobile A1 Not too many people are interested in doing this, I think. QuoteWarheadsSE If the uInitrd does not exist, of course it will also simply be bypassed Thanks, I've recalled incorrectly that my abbreviated instruction did not account for this, aby bodhi - uBoot
Almaz, The behavior you decribed in this post above: http://forum.doozan.com/read.php?2,14617,14634#msg-14634. But since you are using dinjo's version without problem, then I guess you can ignore it.by bodhi - Debian
SOL, There is no sure way to control the device ordering. It is purely depending on which USB/SATA device "spins" up first. Usually SATA always come up first. But if you have more than one USB ports, USB drives assignment is trial-and-error. The only sure way to control the drives selection is using disk label, and uBoot envs to select one you prefer in a certain order.by bodhi - Debian
ACTION=="add", PROGRAM=="/sbin/blkid -o value -s TYPE %E{device}", RESULT=="ntfs", ENV{mount_options}="%E{mount_options},utf8,big_writes,gid=100,umask=002" FYI, regarding big_writes, this should be changed on-the-fly with bind -o remount to optimize the transfer speed, depending on what the usual mode of operation is. Your ntfs-3g behaves very stranby bodhi - Debian
I meant the same log of serial console output as in this post: http://forum.doozan.com/read.php?2,14597,14612#msg-14612 what happen if you did not stop the serial console? You could also try netconsole: http://forum.doozan.com/read.php?3,14 to see if it behaves differently.by bodhi - Debian
Here is how I set up my rootfs to automount USB drives. If you want a true hot-plug that people can just pull the drive out any time, then always use the 'sync' option in pmount. The 'sync' option will result in slower write speed, but it will ensure no corruption: How to automount USB drivesby bodhi - Debian
csspc-pogo Wrote: ------------------------------------------------------- > tried with static ip ... still same issue ... > > might something be messed up on internal flash > that executes before usb thumbnail gets executed? > > > earlier post I asked about -19 error ... might > that be some clue of why it does not boot without > serial cable? > >by bodhi - Debian
Udev solution was posted here (long time ago). I will have to look for it in my bookmarks.by bodhi - Debian
It shouldnot behave differently. But you could try to set up static ip after logging in by serial console to see if you can connect with ssh.by bodhi - Debian
To those who are looking for the orginal mtds for Pogoplug V4. You can download it here: Pogo V4 original mtd backup md5: 064a298c89ae5a1b207061e11b401930by bodhi - Debian
Almaz, I'm not familiar with Paragon driver. May be others here can give you a hand. I'm on the road so can't help you build it. I could help doing that in a few weeks if you still need it.by bodhi - Debian
Geert, Booting ArchLinux is differrent from Debian. Arch does not use uInitrd, Debian does. Look at you uBoot env bootcmd. The procedure set this env to boot Debian, so uBoot will look for uInitrd. To boot Arch, bootcmd must be set to look for uImage only. It should boot either USB or SD card. You could get a listing of your uBoot envs and post here. - in Linux command line: fw_printenvby bodhi - uBoot
Try SSH in to IP address 192.168.1.35 as root. Looks like your router assigned this DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.201 bound to 192.168.1.35 -- renewal in 33496 seconds. done.by bodhi - Debian
Geert Wrote: ------------------------------------------------------- > Could anyone please confirm that Bodhi procedure > sketched above leaves booting > from a USB stick in tact. I am fine booting using > an SD card, but can't get USB to work. > With netconsole I can see the USB device and even > ext2ls files on the first (/dev/sda1) > partition. Running the usbby bodhi - uBoot
Almaz, The kernel patch is in the tarball for 3.12.0-kirkwood-tld-3 in the first post. And you can download the kernel source tree for 3.12.0 from kernel.org. But why Paragon? ntfs-3g should work fine.by bodhi - Debian
Use this latest rootfs, put it on a USB thumb drive and boot with it: http://forum.doozan.com/read.php?2,12096by bodhi - Debian
Regarding questions about NSA325 uBoot, we don't have the patch at the moment, so it is not available, yet.by bodhi - uBoot
Buttzy10169 Wrote: ------------------------------------------------------- > Im haveing some trouble with your latest rootfs > that you uploaded bodhi anytime i create a new > user their home directory is not getting created > and even if i create it its not used on next > login? > > this is on a fresh install with a brand new usb on > the nsa325. Thanks Buttzby bodhi - Debian
cowboyuptx, I'm on the road for a few weeks, so I can only respond to question. The above is not for verification. It's for flashing uBoot to NAND. What it means is in your case, the bad block is block 2, so those 2 command are to erase the necessary 5 NAND blocks (because only 4 blocks are usable in the first 5), and then write uBoot image to these 5 blocks (nandwrite autotmaticaby bodhi - uBoot
Michael, Your installed rescue system does not support the Dockstar machid 0x00000bb6 (arcNumber 2998). You need to set arcNumber to 2097 (machid 0x00000831) to be able to boot.by bodhi - Rescue System
cowboyuptx, No problem :) You're in luck here, it should be straight forward just like in the posts you've linked above. Scanning device for bad blocks [ 1.050000] Bad eraseblock 2 at 0x00040000 [ 1.080000] Bad eraseblock 358 at 0x02cc0000 [ 1.090000] Bad eraseblock 546 at 0x04440000 [ 1.110000] Bad eraseblock 800 at 0x06400000 [ 1.110000] Bad eraseblockby bodhi - uBoot
cowboyuptx, Unfortunately I won't have time to give you a hand since I'm starting a long trip, but if your bad blocks are what we have seen in this forum then I could point you to the thread/posts. Or perhaps restamp will guide you with figuring out the commands. So for starting, while you are still in Pogo OS, pls post the output of: dmesg Note that if you have shutdown the boby bodhi - uBoot