Mijzelf Wrote: ------------------------------------------------------- > Your uInitrd has grown too big. 0x1100000 + > 11782486 = 0x1C3C956, so that overwrites the fdt > on 0x1c00000. You can either create a smaller > uInitrd, or change the loadaddress of fdt. (to > 0x1D00000 or higher). And of course in the latter > case you'll also have to change the boot commandby sylvester - Debian
Using UBoot with FDT support. Have done upgrade many times without issues since 4.1. Last version was 5.12.6 Not sure what I did wrong this time. The console shows problem at bootm 0x800000 0x1100000 0x1c00000 Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ST31000524AS Firm: JC45 Ser#: 9VPC55YG Type: Hard Disk Supports 48-bit addressingby sylvester - Debian
bodhi Wrote: ------------------------------------------------------- > > GoflexHome should have 2A power supply. I am using the power supply came with the unit. No good?by sylvester - Debian
bodhi Wrote: ------------------------------------------------------- > sylvester, > > > A bit out off topic: I have experienced disk > > failure twice since I put debian on my goflex > home > > 20 months ago and running it 24x7. I have the > > whole system running off the SATA disk. > > Is it GoFlex Net or GoFlex Home? > > By "disby sylvester - Debian
> > > 1. Is this behaviour normal with Jessie? > > 2. Is the permission for the version in Jessie > > correct? > > Yes. But you can set the sticky bit to allow > normal user to ping > Thanks, bodhi. I thought I may have screwed it up when I restore my system after a disk failure. Good to know my backup and restore are in fact okay. A bit out oby sylvester - Debian
I just noticed I can't do ping as a normal user. Okay with root or sudo. $ ping 127.0.0.1 ping: icmp open socket: Operation not permitted Not too sure when this issues started, however, Permission check: $ ls -l /bin/ping -rwxr-xr-x 1 root root 38840 Nov 9 2014 /bin/ping From my old backup just before upgrading to Jessie: -rwsr-xr-x 270 root root 34936 Apr 13 2011 bin/pby sylvester - Debian
I see. Thanks for the info.by sylvester - Debian
bodhi Wrote: ------------------------------------------------------- > Yes, it is normal. And you do need to regenerate > uInitrd so that the new packages hooks are used. > Old uInird is still usable for booting, but will > point to the older hooks. So does it mean that every time I do apt-get upgrade I need to regenerate uInitrd? In that case I may as well just capture tby sylvester - Debian
I just carried out "apt-get upgrade" the first time after upgrading to jessie. I noticed it regenerated initrd.img in the last step: Setting up php5 (5.6.9+dfsg-0+deb8u1) ... Processing triggers for libc-bin (2.19-18) ... Processing triggers for initramfs-tools (0.120) ... update-initramfs: Generating /boot/initrd.img-4.0.0-kirkwood-tld-1 Is that normal? Should I be worrieby sylvester - Debian
Upgrade completed. Thanks, bodhi.by sylvester - Debian
Yes, I am using your release kernel. Never have flash-kernel in the system. # uname -a Linux goflex 4.0.0-kirkwood-tld-1 #1 PREEMPT Mon Apr 13 17:35:28 PDT 2015 armv5tel GNU/Linux I usually do "apt-get -s upgrade" to get a list of updated packages and do "apt-get install" after that, avoiding the kernel package. So does it mean that I can actually run "apt-getby sylvester - Debian
My goflex home is on the latest 4.0 kernel. I would like to upgrade it from wheezy to jessie. I suppose I can follow bodhi's steps. However, with the custom kernel, "apt-get -s upgrade" always reports a upgrade for "linux-image-3.2.0-4-kirkwood". I suppose "apt-get upgrade" in those steps would attempt to upgrade it. Will it screw up my system?by sylvester - Debian
bodhi Wrote: ------------------------------------------------------- > > To summarize, > > You have a cach-22 here. You can't use fw_setenv > to set arcNumber in Debian. So you need either > netconsole or serial console to change arcNumber! > and you can't setup netconsole in Debian without > fw_setenv. > > So your option are: > > 1.by sylvester - Rescue System
Oh... checking through the script again and I think I found where I went wrong. I didn't notice the last couple of output line of the uboot install script (which is part of kirkwood.debian-wheezy.sh) to do fw_setenv arcnumber and the debian installation script just started right after that. In my situation, since your kernel and rootfs doesn't let me run fw_setenv, does it mean tby sylvester - Rescue System
May be somehow the arcNumber not set correctly? I thought the install_uboot_mtd0.sh script would do it correctly as it detected the correct platform when it was run. I didn't print out the mtdparts before so I can't compare. Anyway, root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage"by sylvester - Rescue System
Thanks for the new rootfs. It boots up no problem. However, fw_printenv still gives me the "Too few good blocks within range" error. In addition, after using nanddump to dump the uboot, I found that the md5sum is different from the one I flashed before (goflexhome davygravy-2012-04-19-current). Why would that be? After flashing, I am sure it reports the correct md5sum the few timby sylvester - Rescue System