feas Wrote: > I would suggest right now that you read through Bo > dhi's guides for u-boot and Debian rootfs each twi > ce and then write out all of the commands you woul > d do for each and have it reviewed before you proc > eed. Do not worry about differences from other or > older post, just use the recent for each. Once you > are good you can do each and thenby haridsv - Debian
bodhi Wrote: ------------------------------------------------------- > The instruction I wrote was for all Kirkwood boxes > (except where it said otherwise for a specific box > such as the HP T5325). So it is quite general and > seems intimidating. But that's is what I can do cu > rrently. Either I have to write 14 different insta > llation instructions, or finalizby haridsv - Debian
Should I perhaps follow this guide from feas as is: Pogoplug E02 Debian Linux Installation Guide ? Would it be OK to start over at the stage where I am yet? I normally prefer to understand what is happening under the surface and don't mind getting my fingers dirty, which is why I started looking at the individual guides such as U-Boot setup, Debian installation and Rescue system separately,by haridsv - Debian
bodhi Wrote: > Again, there is no need to worry about the fw_sete > nv, fw_printenv or fw_env.config. Those are only r > elevant after you you have booted in Debian. As lo > ng as the flashing of u-boot image, and u-boot env > s image are shown without error, then it is all OK Does this mean, I can ignore all the rest of the steps and go straight to the steps for installiby haridsv - Debian
I figured I can start over as long as I don't reboot, so I continued with the below steps. Again, the output of erase is not matching what is expected: -bash-3.2# ./flash_erase /dev/mtd0 0xc0000 1 Erasing 128 Kibyte @ c0000 -- 100 % complete -bash-3.2# ./nandwrite -s 786432 /dev/mtd0 ../uboot.2016.05-tld-1.environment.> Writing data to block 6 at offset 0xc0000 I am not stuck bby haridsv - Debian
bodhi, I am unclear on what the step 8 in section A is talking about here. There is a special note about /etc/fw_env.config having 0xc0000 as the starting address, but I had to set it to 0xa0000 as I had the stock u-boot. You indicated in the other thread that I don't have to change this until it is rebooted but I would like to double confirm please. I ran fw_printenv without changing theby haridsv - Debian
I am flashing u-boot and have some output from erase that is not matching what is expected, so would like to double check. -bash-3.2# ./flash_erase /dev/mtd0 0 4 Erasing 128 Kibyte @ 60000 -- 100 % complete -bash-3.2# ./nandwrite /dev/mtd0 ../uboot.2016.05-tld-1.pogo_e02.mtd0.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 aby haridsv - Debian
I started with a virgin Pogoplug E02. After I created /etc/fw_env.config, fw_printenv gave a CRC error. I then found in another thread that the start address should be 0xa0000 for default u-boot, not 0xc0000, so changed it and got fw_env.config to work. I also validated a few of those (e.g., ethaddr). Next, I ran nanddump which has the length specified as 0x80000 and I am wondering if it is sameby haridsv - uBoot
bodhi Wrote: ------------------------------------------------------- > haridsv, > > I am wondering if I can just follow a debian insta > > llation guide or if I must first enable ssh perman > > ently, using the serial cable method. I don't have > > a cable right now and never did anything like that > > , so it would make my life much easier if that isby haridsv - Debian
feas Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > haridsv, > > > > > I was able to use the below curl hack to hit / > s > > > qdiag/HBPlug for starting dropbear: > > > > Thanks for confirming this curl hack works! ther > e > >by haridsv - Debian
I bought a Pogoplug E02 back in 2013 wanting to do something, but never even got around to do it, so it was lying unused. I now have certain things my mind, like setting up google cloud print and some home automation, so powered it on for the very first time today and activated it. I realized that ssh can no longer be enabled via Pogoplug account, but I was able to use the below curl hack to hitby haridsv - Debian