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
jfharper, No, there is no log from the install script. Usually we just copy/paste the screen to a text file. Without that log, I could not figure out when your entire mtd0 went bad! So my suggestion is you should keep this U-boot and continue using Arch rootfs. That would be the easiest and safest way. If you really want to install newer u-boot, then I would get a serial console connectedby bodhi - uBoot
@sigma, Let me take a look at the UART build size to see if it is even smaller. These 2 versions were both built as NAND binaries.by bodhi - uBoot
@sigma, Do your downloaded binaries look like this? -rw-r--r-- 1 root root 312828 Aug 29 22:12 uboot.2013.10-tld-1.nsa325.uart.kwb -rw-r--r-- 1 root root 393216 Aug 30 01:28 uboot.2013.10-tld-1.nsa325.mtd0.kwb Your serial connection might be slow or noisy. I've booted this image many times without failing to load 100%: uboot.2013.10-tld-1.nsa325.uart.kwb When you see xmodemby bodhi - uBoot
davidedg > 45%, but no farther. This sounds to me that your serial connection is probably not full speed? > What I've noticed, though, is that I have to use > "-p" switch even with uart image, otherwise it > blocks at 0% with > "xmodem: Bad message" True, because it is also NAND version, not UART built version. This is small enough to boot wiby bodhi - Debian
Very puzzled, your entire mtd0 is bad. I'm looking for this section: [ 5.197563] Bad eraseblock 0 at 0x000000000000 [ 5.202061] Bad eraseblock 1 at 0x000000020000 [ 5.206560] Bad eraseblock 2 at 0x000000040000 [ 5.211114] Bad eraseblock 3 at 0x000000060000 [ 5.215611] Bad eraseblock 4 at 0x000000080000 [ 5.220125] Bad eraseblock 5 at 0x0000000a0000 [ 5.2246by bodhi - uBoot
sigma Wrote: ------------------------------------------------------- > I cant kwboot the uart.kwb, at 94% is always an > xmodem error, somehow i thought the watchdog is > disabled with this new uboot. Yes, the watchdog is disabled when u-boot starts. But UART booting is before that! so the binary must be loaded completely and then u-boot starts. That was the reason we've beeby bodhi - uBoot
InfoScav, Ah! I thought you want to use USB so that you can unplug it easily. However, you can do the same with HDD label using the mount command, instead of pmount. The reason I prefer partition label over the UUID: it is more flexible, you can even swap disks as long as the label is used for mounting, while UUID is fixed to that physical disk. And I don't put the entry in fstab becauby bodhi - Debian
@Davide, QuoteAs I understood from your reply to sigma, new Uboot has different location for its env and won't touch the stock one. But, since it's new uboot, I may as well create a new more powerful environment (scripting), correct? Also, did you include EFI partition support? Yes, it has all the good stuff: EFI, Hush shell scripting, boot with Ext4, >2TB HDD … I mentioby bodhi - Debian
InfoScav, The simplest solution is using pmount. Always label the HDD to something meaningful, e.g. MUSIC. pmount will take care of the mounting the disk to /media. So even if you don't want to automount (this is another subject), pmount is going to work well for it. That disk partition is always going to be /media/MUSIC regardless which Linux box you plug it in. pmount /dev/sda1 /mby bodhi - Debian
@jfharper, QuoteMy assumption is I don't have a filesystem on the GF base, so the red blinking occurs...is it looking fo boot files and cannot find them? No, the blinking red in this case means your envs are not define properly (due to bad blocks). The end result is, yes, u-boot could not find the boot files, but likely not because they are not there, it probably just searching in theby bodhi - uBoot
@jfharper, You're lucky the flashing did not mess up mtd0 too badly:) you got 4 bad blocks on mtd0 !!! There is no space left for envs. For now, you can boot into Arch, this is the best you can hope for. Don't try anything else, it might brick it for good :) Let me think about it a bit and get back to you.by bodhi - uBoot
sigma Wrote: ------------------------------------------------------- > i flashed uboot.2013.10-tld-1.nsa325.mtd0.kwb on > nsa325 with 3.16.0-tld-2. Now the new uboot is > coming up, but it dont read the envs from mtd1, > right? > can i copy the envs from mtd1 or have i to kwboot > with uart? Cool! right, the new u-boot uses diferent location: 0xC0000. So you can cut/paby bodhi - uBoot
@davidedg, Have you tried the test U-Boot? I'm running NAND version and it has been very stable. @WarheadsSE BTW, I have tried to see if I can chainload stock U-Boot from the new U-Boot. I could not get it to load, it just hang. It seems like stock U-boot is old, but not old enough to do this successfully. But there is a path to stock after you've installed new U-Boot: we can UARTby bodhi - Debian
jfharper, Have you rebooted? or still in Arch? > flash_erase /dev/mtd0 0 4 > nandwrite /dev/mtd0 > uboot-mtd0-orig-goflexhome.kwb If your above flashing of the original U-Boot was successful, then you're back to stock upon reboot. What the ouput of these comands look like? you can post the log here. Quote> Is the above uBoot the one I got from Jeffs > tutorial?by bodhi - uBoot
InfoScav Wrote: ------------------------------------------------------- > thanks a lot bodhi for that! clears it up well for > me. option no. 4 it is for me then! > > and i just took the risk & flashed the new uBoot > too successfully! :) Excellent!by bodhi - Debian
sigma, This bootcmd should be: bootcmd='run bootcmd_linux' And to_stock and to_linux should be: to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset BTW, you can post in this NSA325 thread to get help quicker: http://forum.doozan.comby bodhi - Debian
@sigma, Your envs look odd: to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock'\; saveenv; reset to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux'\; saveenv; reset bootcmd='run bootcmd_linux\; saveenv; reset Have you tried to set it back to stock and back to linux again? in serial console: run to_stock run to_linuxby bodhi - Debian
sigma, Try this: fw_setenv machid 118fby bodhi - Debian
InfoScav, If the main use is general purpose and perhaps involved with compiling sources code then I would use the HDD rootfs. OTOH, I would choose option 4 for media-storage & occasional downloads. All my media NAS servers boot from USB flash, this has many advantages over a single HDD drive: easier to backup rootfs image, portable HDD drive that you can unplug and carry. And I have a sinby bodhi - Debian
sigma Wrote: ------------------------------------------------------- > i got this error with 3.16.0-kirkwood-tld-2: > > Error: unrecognized/unsupported machine ID (r1 = > 0x0000020f). > ... > ... > Please check your kernel config and/or > bootloader. > > installed the new kernel over > 3.16.0-kirkwood-tld-1 Which box did you install this kernel onby bodhi - Debian
Both 3.16.0-kirkwood-tld-2 kernel and rootfs have been uploaded. Please see 1st post for download links.by bodhi - Debian
Me neither. I just thought about it because I came across the mcc module in stock kernel while browsing around. This module reads the temperature (pull down and pull up those 3 GPIO pins).by bodhi - Debian
InfoScav, > that! it makes sense that perhaps may be that's > why the HDD is not showing up. don't know. Not likely the reason. The GFNet u-boot works fine for GFHome. It's only different in other minor thing specific to GFHome such as LEDs. > > i tried interrupting the boot-process when it > gives the prompt 'hit any key to stop autoboot', &gby bodhi - Debian
InfoScav, Yeah, I forgot that you have the GoFlex Home! only one available SATA port (there are 2 supported by the SoC). But it should work with the U-Boot that you are running without problem. You are actually running the GoFlex Net version, not the GFHome version (work the same for booting, but not exactly support GH Home specifics in Debian kernel). You could interrupt netconsole and tryby bodhi - Debian
InfoScav, > UPDATE: attaching the boot flash-drive to > the USB-hub not working. the hub is anyway a > non-powered one. can't fathom why attaching the > HDD to the SATA port is not working. USB flash boot drive should work with the hub (it does not matter power or not). Look at netconsole output for the USB drive detection, see if anything strange during boot. [ 2by bodhi - Debian