JeffS, You are not registered user so you can't edit post. Perhaps you should consider installing the latest Debian rootfs on USB or HDD: http://forum.doozan.com/read.php?2,12096 Using stock OS as a main system is not fun or safe. That kernel is very old.by bodhi - Off-Topic
arin, Create a new 4.4 rootfs on USB : http://forum.doozan.com/read.php?2,12096 QuoteUpdated 20 Feb 2016: This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1. Basic minimal Debian Kirkwood rootfs for most Kirwood plugs: You need to do section 4, since you are booting with an old u-boot: Quote4. Create uImage with emby bodhi - uBoot
I'm afraid I'll spoil the mood by posting what's going on for me the last few months :)by bodhi - Off-Topic
SiliCAT, Post the entire serial boot log so I can see why uInitrd is not working.by bodhi - uBoot
arin, > This is my Pogoplug dissected by my friend: > http://imgur.com/lnan8pu > > He told me that: > * he identified a serial port and connected to it > through a usb adapter; > * he found the baud rate (115200) and he saw a > boot screenshot. Nothing happened apart a prompt: > http://imgur.com/kevW7LK At this u-boot prompt, get the listing of u-boot enby bodhi - uBoot
Gravelrash Wrote: > > @Bodhi - cant be as bad as the Brexit vote fallout > was for us brits..... Are you sure now? :))by bodhi - Off-Topic
SiliCAT Wrote: ------------------------------------------------------- > I have to use tftp to load the uImage > > setenv net_boot 'tftp 0x1c00000 $net_tftp_dtb; > tftp 0x800000 $net_tftp_kernel; echo; echo ** > Kernel Boot Arguments: $bootargs; echo;if tftp > 0x1100000 $net_tftp_initrd; then bootm 0x800000 > 0x1100000 0x1c00000;else bootm 0x800000 - > 0x1c0by bodhi - uBoot
Cool! glad it's unbrick. Now you should install the new u-boot and set up netconsole.by bodhi - uBoot
dancyran Wrote: ------------------------------------------------------- > Hi and thank you for the great work you've done. > I've used it as a road map, but I realized a few > problems near the end. > I have a pogo-v4-a3-01 I've read your work and > also Qui's (7/2014 blog.qnology.com) and Jack > i.t. (2014 pogoplug4.blogspot.com) > got yby bodhi - uBoot
Last post moved here: http://forum.doozan.com/read.php?3,30888by bodhi - uBoot
ouchyoung Wrote: ------------------------------------------------------- > Thank you for your attention and please forgive my > poor English. > > I installed ArchLinux ARM on my goflex home, well, > it ran well but it's slower and slower recently, > so I wanted to go back to the stock firmware. I > followed the instructions from doozan.com as the > followingby bodhi - uBoot
> > It seems the nfs v2 is disabled. That would be a really bad decision. Hope you can set it. If it is not controlled by users, hope the LEDE developers has correct it.by bodhi - uBoot
Make sure you are running version 3 or version 2 NFS for this. Our u-boot actually run version 2, but it can access version 3 NFS (the NFS server version 3 can provide version 2 file system). /srv/nfs/hosts/PogoplugV4 172.16.16.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_check) Which version does this installs? opkg install nfs-kernel-serverby bodhi - uBoot
ShapeShifter499 , > Is it safe to run this pogoplug > with this damage? Only you will be the judge of this, whether it is safe. ------ As whether it is still working, I agree with "The Grave" ;) it sounds like you've fried the serial port only.by bodhi - Off-Topic
desmond Wrote: ------------------------------------------------------- > My Stora started to boot up without pressing power > button right after I flashed you u-boot and > environment variables from image. > > I thought it's your magic :) > Ah, that's not intentional :) perhaps some settings in that u-boot image caused this behavior. It is really the coby bodhi - uBoot
JT, [ 5.730994] Scanning device for bad > blocks > [ 5.790733] Bad eraseblock 723 at > 0x000005a60000 > [ 5.854769] Bad eraseblock 1496 at > 0x00000bb00000 > Is that bad? So it had nothing to do with the > kernel update? I just noticed the original ECC > errors were on mtdblock1 and these are mtdblock0. > I never noticed the mtdblock0 ECC errorby bodhi - Debian
> I'm a bit scared and fear lean times could > happen, and two little devices like that would > ease my fears. Hunker down. Stock market future is down big time. A harbinger? But this forum is free, and Linux is free :))by bodhi - Off-Topic
arin Wrote: ------------------------------------------------------- > Some time ago (maybe two or three years) I have > (quasi) bricked a Pogoplug E02 Model attempting to > install Debian on it. I leave it as I was since I > haven't the skill to "repair" it. Now a friend of > mine who is very competent has disassembled it and > he has told me that the devicby bodhi - uBoot
asterix Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > asterix , > > > > Do you still have problem installing? > > My B01 bricked, bought a serial to USB cable, > connected, but don't know which file I should use > to flash nand, frustrated!by bodhi - Debian
renojim Wrote: ------------------------------------------------------- > Update: After completing the kernel and dist > upgrade, I still get the ECC errors:[ > 23.932658] __nand_correct_data: uncorrectable ECC > error > [ 23.938095] blk_update_request: I/O error, dev > mtdblock0, sector 2040 > [ 23.944841] __nand_correct_data: uncorrectable > ECC error >by bodhi - Debian
SiliCAT, You are making it too complicated! From Wiki thread: QuoteNFS NFS - HowTo set up NFS shares (and boot NFS rootfs) http://forum.doozan.com/read.php?2,28351 Quote"Section Three" Boot from NFS share The following link gives the steps necessary to configure your u-boot to boot from the NFS share. Please note though that although it discusses using TFTP in tby bodhi - uBoot
asterix , Do you still have problem installing?by bodhi - Debian
Those who do this should be slapped silly :)) char* x, y, z; // why? because it could be a coding error This is more acceptable: char *x, *y, *z; Below is the best style, imo. Because it left no doubt about the intention and easier to remove/change individual variable: char* x; char* y; char* z; or char *x; char *y; char *z; Disclaimer: I've written a C compiler inby bodhi - Off-Topic
feas, > ERROR: "foo * bar" should be "foo *bar" > ERROR: "foo* bar" should be "foo *bar" This is the kernel coding standard. For example, "foo * bar" must be "foo *bar". Because if foo is a struct, then the 1st line would not make sense to be multiplication. The 2nd line is OK, but coding standard make the codeby bodhi - Off-Topic
Joey, Becareful, one might be USB 2.0? I've only seen the Ultra Fit with black casing and red letter (USB 3.0). There is an Ultra version with a typical USB thumb drive case. FWIW, the only flash drive that I carry on my key chain is the Extreme 64GB. It's faster than spinning rust :)by bodhi - Off-Topic
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Like a Solid State Drive? One of you mentioned > not long ago, some SanDisk 64GB had the same wear > leveling chip as their SSD products. > > With that in mind, there are sales at Best Buy > this week, SD 32GB UltraFit for $9.99, but > $15 for 64 GB. And if this affects reliability,by bodhi - Off-Topic
All, This is easy to solve once I can get my hand on the GPL source code from Zyxel, or have some time to boot it up with serial console. I have some ideas now, but it's just guessing so out of precaution I'm hesitate to recommend them.by bodhi - Debian
JT, Yes. That will happen sometime when the older mainline kernel is still installed. That linux-image-kirkwood was triggering the update. So it is best to remove both after you got 4.8.3 booting. linux-image-3.16.0-4-kirkwood linux-image-kirkwood And use "dpkg --purge" to remove it so that all remnant of the old kernel are also removed (i.e. init scripts,...) While you at thiby bodhi - Debian
desmond, > After I flashed your environment variables, my > Stora changed behavior on power loss. If I plugged > power cable it started automaticaly. > > Unfortunately, after I flashed part part of mtd0 > with environment variables, Stora lost this > feature. > > Can I restore this behavior via some environment > variables? Or I need something bigger aby bodhi - uBoot
SiliCAT, > I’ve read "Booting process in multiple drives > configuration", but still I have no idea how to > set the bootcmd to support NFS and other devices > in the load chain for the new uBoot. Did you set up as describe in the Wiki thread: QuoteNFS NFS - HowTo set up NFS shares (and boot NFS rootfs) If you did, post your envs here and I'll help.by bodhi - uBoot