BTW, I am working on adding new feature to this u-boot: SNTP, bootz, large GPT HDD, load envs.by bodhi - uBoot
InfoScav, > 1. many-a-times, when i do 'apt-get update', i get > error linking to the mirror. only after repeatedly > trying (3-4 times) is debian able to successfully > connect to the links and get update-info. should i > change the mirror to the one nearest to my > location, as instructed by Jeff? currently its the > US mirror. Yes, change to the one cby bodhi - Debian
WarheadsSE Wrote: ------------------------------------------------------- > The CPU and RAM clocks are stepped together by > default (without a good amount of jackassery) so > you get a bonus of the RAM clock as well. That is, > by the way, why 950 is unstable. Thanks Warhead! I was wondering about that. I remember distincly you mentioned about you've tried 950MHz.by bodhi - uBoot
mxhdrm, Congrats! it looks good! Now you can setup netconsole ( step 10 in my u-boot installation instruction) before reboot the box with USB attached. Use a USB thumb drive, formatted is as Ext3. Put either latest Arch or Debian rootfs on it and reboot. If you use Debian rootfs, it really does not matter if you have swap or not, otherwise follow Arch instruction to create rootfs if it dby bodhi - uBoot
@shv, That's a nice 19% performance improvement!!! Which kernel are you running? can you change other u-boot envs? This u-boot uses the same env location as the stock env, so it should not change any of the envs. However, steps 8 and 9 flashes a default set of envs, did you do these steps?by bodhi - uBoot
@shv, I found the link to your post from way back! But now I realized that was HDD performance test. However, if you did compile something big like a kernel then it would show the CPU performance increase clearly. I can't remember the CPU benchmark that I've seen. Perhaps Phoronix has something like that.by bodhi - uBoot
@shv, I've flashed this 850MHz u-boot-spl image to NAND and running it currently. I recalled you did performance tests before so it'll be good to see the before and after numbers!by bodhi - uBoot
@shv, I've uploaded the 850MHz u-boot-spl image. Please test and report. Download at Dropbox: uboot.spl.2013.10.ox820.850mhz.bodhi.tar md5sum 69375902be22774f4216b92224c5ae1eby bodhi - uBoot
mxhdrm, Looks good! However, your original attempt for u-boot installation stopped because of bad block, u-boot environment image was not flashed (CRC error when you do fw_printenv). Do this before continue with the rootfs USB creation. You need to flash a default envs set using the instruction in step 8 (section B) of my U-boot installation instruction: Below is a simplified section Bby bodhi - uBoot
@shv, I've rebuilt the u-boot-spl image with 850Mhz clock. Just for my understanding, did you overclock it to 850 Mhz using WarheadsSE's stage1 image for that? And also, are you running the new NAND u-boot with 800Mhz stage1 right now?by bodhi - uBoot
mxhdrm, Everything is great as planned! QuoteAnd there were no pogoplugs harmed by lack of electricity during this work. ;) Phew :) Normally, if this were a UART-enable booting box like other Kirkwood boxes, I would say go ahead and download the latest Debian rootfs and put it n an Ext3 USB thumb drive and reboot. However, this is Pogo E02, so we can't boot with UART. I woulby bodhi - uBoot
@davidedg, Excellent :) thanks for testing. So the remaining tests we need to see before we can declare victory are: 1. bootz 2. Large HDD >2TBby bodhi - Debian
mxhdrm, > Writing data to block 0 at offset 0x0 > Writing data to block 1 at offset 0x20000 > Writing data to block 2 at offset 0x40000 These were successful. > Writing data to block 3 at offset 0x60000 > Bad block at 60000, 1 block(s) from 60000 will be > skipped This is what I expected to see. > Writing data to block 4 at offset 0x80000 > pwrite: Inpuby bodhi - uBoot
@sunfire, Yes, the watchdog is disabled whe u-boot starts.by bodhi - uBoot
Shv, OK. I'll take a look.by bodhi - uBoot
unmesh, Booting Debian looks good, and you've confirmed it. You can't boot into Pogo OS (when there is no USB plugged in) because the mtd partiton that houses the orginal u-boot has error. If you want to do boot Pogo OS, you have to find a original copy of the mtd (rootfs) and the orginal u-boot image copy somewhere, reflash mtd, and copy the u-boot image file back in.by bodhi - uBoot
Shv, This u-boot-spl is for 800Mhz. Is this pogo capable of going up to 850 Mhz? has anybody done this and determined that it is stable? See the instruction (step 3) for how to dump mtd0 to a file, the same command can be used for other mtds.by bodhi - uBoot
unmesh, Please post the whole log captured on serial console. From the 1st line (u-boot banner) til the last (when if failed to boot).by bodhi - uBoot
mxhdrm, > Anyway, this is the output of the two commands > that I was able to run. Once I got the file onto > the device, I've run these commands: > > > Pogoplug:/tmp$ ls -lh > uboot.2014.07.tld-1.pogo_e02.mtd0.kwb > -rw-r--r-- 1 root root 512.0k Jan 8 > 11:46 uboot.2014.07.tld-1.pogo_e02.mtd0.kwb > > > > > Pogoplug:by bodhi - uBoot
I've updated the instruction in the NSA325 u-boot upload post.by bodhi - Debian
davidedg, > It seems there was something wrong with "$(" > variable calling. > New Uboot seems to not always like it - I just > removed the parenthesis. Yes, I forgot to mention this! new u-boot has hush shell scripting. And the parentheses style, iirc, was deprecated. > I can boot my old 3.14 kernel with no problems, > via USB or even loading it from EFIby bodhi - Debian
InfoScav, Quoteone thing - if i run 'apt-get upgrade' sometime, i hope it won't upgrade the kernel, isn't it? asking because i saw an old thread, where the OP had done that, and his kernel got upgraded and then he wasn't able to boot with the USB-stick anymore. he had to re-install debian. though i think it was about dockstar. apt-get upgrade will not update your kerby bodhi - Debian
@sunfire, Looking back to the upload post: QuoteThis is because the envs location this U-Boot uses is 0xC0000. There is nothing in that location yet. Feel free to set the envs to boot into Debian just like you have done for stock u-boot before, but don't save with saveenv. Just cut/paste the old envs to set them here for booting. The reason was stock u-boot is limited in scripting caby bodhi - uBoot
floodo1, You could do fsck from inside rescue system to see if there is any error. If you have trouble doing that, then download the latest rootfs. Extract it a USB thumb drive formatted as Ext3 and plug that in the GFHome. Power up, and stop u-boot at netconsole. Change the bootcmd to boot USB. You also need to change usb_root env, too, so that the correct drive is selected for rootfs (otby bodhi - Debian
@sigma, That's certainly strange. I would look at the serial cable routing, do you route it under the board to the outside? I'm taking wildarse guess here! because I loaded this image many times completely without the watchdog barking.by bodhi - uBoot
jfharper Wrote: ------------------------------------------------------- > Yeah, it works as a linux box right now...I'm > tempted to keep messing with it, just to see if I > can get it fixed, because it is kind of fun to > mess with..besides, it wouldn't be a very big > loss...these bases are pretty cheap. That's cool :) It would be a great example if you caby bodhi - uBoot
sigma Wrote: ------------------------------------------------------- > What can i do against noisieness, bying a new > ftdi? I tried it 10 times always stopped at 94%, > with or without hd. See this post: http://forum.doozan.com/read.php?2,14351,17501#msg-17501. DavideDG had some problem with the serial connection using VM. BTW, the HDD does not affect UART image loading inby bodhi - uBoot
jfharper Wrote: ------------------------------------------------------- > Is there anyway to reset or fix the bad blocks? Not without serial console. I've heard of cases when people scrubbing and let the HW recollect bad blocks. But that might make things worse. Currently you can boot into Arch Linux, and that's is pretty decent given that many blocks were marked as bad.by bodhi - uBoot
@DavideDG, I've been looking at your NSA325 mod page: https://github.com/davidedg/NAS-NSA325-mod/ and I really like a lot of what you've done. In particular: https://github.com/davidedg/NAS-DNS325-mod/blob/master/rootfs-initramfs/rootfs-nand.txt#L268 So do you use EseKeyD to control the buttons currently? Quote## Set up EseKeyD to control NAS buttons sed --in-place -e &by bodhi - Debian
davidedg, > Virtualization ruined it :D :) > Worked at first shot now on native Linux Mint > (with pl2303 usb serial adapter). Awesome. > I did not understand until some minutes ago that > the watchdog is actually still there UNTIL new > u-boot has done booting. To be precise, we shut it down at at the 1st second when U-Boot starts (when HW devices are detecby bodhi - Debian