Nice mod Joey :) I like the possibility of using a 120mm, wisper quiet fan without having to drill/cut.by bodhi - Off-Topic
Preacher Wrote: ------------------------------------------------------- > Simular problem here. > I have Pogoplug V4 and booting Debian from top USB > connector. > Meanwhile latest U-Boot with latest Envs > installed, was the same with former U-Boot. > > It works flawlessly with a cheap unbranded 4GB > stick. > I wanted to have a larger and compact stick thatby bodhi - Debian
Richard Wrote: ------------------------------------------------------- > Ah - I see what I was doing wrong. I was trying to > extract the files from the .deb file using ar, but > we need to use dpkg because it does a whole load > of post-processing on those files and generates > the init image. > > Was a bit chicken-and-egg for a while as my pogo > fs has put itsby bodhi - Debian
Here is where to find howtos: Sticky thread: http://forum.doozan.com/read.php?2,23630by bodhi - Off-Topic
And do the same but reverse the direction (pull): time cp /mnt/samba/server/share/bigfile . #where /mnt/samba/server/share = your mounted share time cp /mnt/nfs/server/share/bigfile . #where /mnt/nfs/server/share = your mounted share Lastly, these 4 tests should be performed in a Gigabit network, with only a Gigabit switch in the middle of the 2 computers.by bodhi - Debian
Your best approach: 1. Create Debian 4.4 rootfs on USB from: http://forum.doozan.com/read.php?2,12096 You need to append the pogo e02 DTB to uImage. 2. Boot, interrupt serial console and copy the list of current envs, adjust envs (but dont save) to boot with USB rootfs. Boot into Debian. Verify this can be repeated a couple times. 3. In Debian, flash new uboot and default envs imageby bodhi - uBoot
All, I'd like to gather the various threads that reported Samba and/or NFS performance benchmarks for the latest kernels (3.16 or newer). I want to track these comparing to stock OS on various Kirkwood boxes. Please provide the links to such posts in this forum that you are aware of.by bodhi - Debian
To install rescue system, best to install Debian on USB first (you also need to adjust u-boot envs to boot USB, since you are booting with stock u-boot): http://forum.doozan.com/read.php?2,12096. And then install rescue system. 1. With that said, usually we just install latest Debian (mentioned above) and new u-boot: http://forum.doozan.com/read.php?3,12381. And boot from USB or SATA. 2.by bodhi - Rescue System
I forgot to address the questions in this post. Better late than never! so here is: Emdebbian is no longer supported. So to install a simple Debian system on NAND, you could install one of rescue systems in this forum: http://forum.doozan.com/read.php?4,7915 http://forum.doozan.com/read.php?4,3896 If you want a more recent kernel then perhaps OpenWrt is better: http://forum.doozan.com/by bodhi - Rescue System
Courtesy from our LeggoMyEggo https://drive.google.com/file/d/0BxqgSgMIwvUZN21mZnp5WWZzQlU/view?usp=drivesdk This Pogo V3 NAND rootfs file was dumpped with: nanddump --noecc --omitoob -f mtd1.stock_pogo_v3_rootfs /dev/mtd1 It should be 114M in size.by bodhi - Debian
vibskk Wrote: ------------------------------------------------------- > An Update: > > Debian-3.14 rootfs in USB option didn't work, but > using Debian-3.18 rootfs worked to some extent in > mmc card. Now I could ssh into it(used putty). Then you are back to normal, if you can ssh into it. > The > led sequence remains the same (the device boots up >by bodhi - Debian
armless, > Ok, and do you recommend I use your u-boot rather > than the OpenWRT (1st stage) u-boot one? You could stay with that u-boot since it is relatively new. However, iirc, it is missing a lot of new features comparing to my u-boot images, so you might as well flash the newer u-boot. The only bad thing with installing any u-boot in Pogo E02 is that it does not have a recovery mby bodhi - uBoot
I've moved the last post to Rescue System subforumby bodhi - uBoot
vibskk, > > Now the status is that with mmc inserted, the > device boots up with blinking green light for a > while then a yellow light for 2-3 secs and then > the green light stablizes. This indicated that the kernel has been loaded and running. The problem is with mounting rootfs. 1. You are running u-boot-2014.07, but I'm not sure what your u-boot envs looks likby bodhi - Debian
kofec Wrote: ------------------------------------------------------- > I have question. Is it possibile to prepare this > /boot/uEnv.txt to start original os from nand No. Stock Zyxel OS is no longer bootable after you installed new uboot. I have not worked on this so dont know if it is possible to make this happen.by bodhi - uBoot
notoneofmyseeds, > Anyone here with experience setting up autofs? I > think I'm done with this for now. I'm beginning to > suspect it's my version of Ubuntu. But then again, > the pogo won't mount the SAMBA share either. Go ahead and google autofs, or start here. This Ubuntu tutorial is basically the same as used on any Debian distro: https://help.ubuntu.by bodhi - Debian
sambo Wrote: ------------------------------------------------------- > Thank you very much...pogo is booting again. > What about step B. Flashing default u-boot envs > image New default envs is always recommended, to make setting up easier. > C. Add uEnv.txt to /boot directory, > which I left out when I updated u-boot. Not necessary. Only when you need to tailor theby bodhi - Debian
armless, > > bootcmd=nand read.e 0x800000 0x100000 0x200000; > setenv bootargs $(console) $(bootargs_root); bootm > 0x800000 > > This the actual bootcmd which loads the kernel. > So is it a case that the chainloaded OpenWRT > u-boot is missing its own set of env variables? Yes. However, as I mentioned, don't set up chainloading. Just boot the Opeby bodhi - uBoot
However, looks like the chainloading was not set up correctly also. No where in your envs that I can find a "go" command, Is there?by bodhi - uBoot
Chainloading from older u-boot (1.1.4) to a modern u-boot such as 2014 or newer is not going to work. You might as well install new u-boot on mtd0 and not having to worry about it at all: http://forum.doozan.com/read.php?3,12381by bodhi - uBoot
Mount this rootfs on another Linux box. And restore uImage using the uImage.orig saved in step 4b.by bodhi - Debian
Your mtdparts env is correct in u-boot, but wrong in kernel bootargs. Look at your uEnv.txt in the rootfs /boot, it might contain wrong mtdparts env that has overwritten the correct one in uboot envs.by bodhi - uBoot
Re 1. That is not the entire boot log. I want to see uboot banner, everything. Re 3. You have installed kernel 4.6 incorrectly. Look at the instruction again. Don't append the DTB to uImage. Your uboot envs were set up to boot with separate DTB.by bodhi - Debian
1. Post the entire serial boot log. 2. Which u-boot were you running before installing u-boot-2016.05? 3. do you keep the log of the kernel 4.6 installation? the most interesting part is whether you appended the DTB to uImage (see step 4).by bodhi - Debian
devonian Wrote: ------------------------------------------------------- > Yes, I 'power read' the thread and cherry picked > the bits I needed and thought I'd contribute a > little as a way of giving back something and not > just taking. > > I've fought this little box 'bout enough as it is > ;-) Hey I appreciated the gesture :) However, Iby bodhi - Debian
Please post the entire boot log. If you have serial console log then post that. If not, post dmesg ouput.by bodhi - uBoot
Thanks for your contribution. I guessed you have not read this thread? We are running kernel 4.6 and u-boot 2016.05 on this box!by bodhi - Debian
Fix mtdparts first: fw_setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)'by bodhi - uBoot
Thanks Rainer! I've added this to the Wiki thread also.by bodhi - Debian