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
@WarheadsSE, Do you have any plan to implement the NSA325 MCU status readout in the kernel? perhaps a module?by bodhi - Debian
mxhdrm, Did you keep the log of your attempt to flash U-boot? It's always good to include that, too. Your bad block is right within the first 1M of NAND, and to be precise it is in first 512K, which is where U-Boot is. The instruction in the blog mentioned above, with both the flash_erase and nandwrite commands must have failed, resulted in a bricked Pogoplug. So don't shutdown orby bodhi - uBoot
davidedg, It is defined in mtd nands part: cat arch/arm/mach-kirkwood/nsa325-setup.c.orig | grep -5 MTD static struct mtd_partition nsa325_nand_parts[] = { { .name = "uboot", .offset = 0, .size = SZ_1M, .mask_flags = MTD_WRITEABLE }, { This write flag was masked, and must be removed to allow wby bodhi - uBoot
sunfire, > When will 3.16.0-tld-2 be released? Not sure when exactly, could be a next few days. > I need a new u-boot, because the watchdog does not > support a cold start with debian. Boot with a fast USB thumb drive would help a little. But if the HDD is needed to be fsck then it would be too slow to survive the watchdog. > I hope i can fix it with a new submarine :)by bodhi - uBoot
# By default this script does nothing. ethtool -K eth0 tso off # turn on LEDby bodhi - Debian
jst818 Wrote: ------------------------------------------------------- > Do i need to enter this command every time debian > arm device is restarted ? Yes. So you can add it to /etc/rc.local so that it will executed during kernel start up.by bodhi - Debian
InfoScav, > nc -lup 6666 192.168.1.50 6666 > nc: cannot assign requested address nc has many variations on different platforms, so check the man page on Ubuntu to see if the command options are the same as on Debian wheezy. You might need to change the command above.by bodhi - Debian
sunfire, > root@nsa325:/home# dmesg | grep -i 'bad' > [ 21.769430] Scanning device for bad blocks > [ 21.779256] Bad eraseblock 100 at > 0x000000c80000 > [ 21.789546] Bad eraseblock 200 at > 0x000001900000 > These bad blocks are OK. They are far in other regions, not in first 1M. > 2. flash_erase u-boot in debian as root > > root@by bodhi - uBoot
zzbao, > are these bad blocks in the first 1M? Can I flash > the new uboot? Block 67 and the rest, they are way up in other area in NAND. Please be extremely careful, because the Pogo E02 does not have UART booting. If you have a typo in your commands, you will have a brick :) and the only way to recover is JTAG.by bodhi - uBoot
InfoScav, > 1. am getting 2 IP addresses for the same MAC > address of the dock, ie, 'debian' gets an IP addr > 192.168.1.50, and the dock gets another IP addr > (no name), 192.168.1.60. Your u-boot env ipaddr is the address used for netconsole. So it was good until Debian starts booting. After that, if your /etc/network/interfaces uses DHCP then a different IP addrby bodhi - Debian
@shv, uboot.2014.07-tld-1.goflexnet.bodhi.tar is the latest U-Boot and I'm running it on my GoFlex Net. Did you keep the log? I can take a look to see if you've missed anything. I hope you did not flash the archive itself?by bodhi - uBoot
davidedg, Thanks! the code base for this u-boot (u-boot-kirkwood) is pretty solid. And I'm done testing new code that WarheadsSE added for the NSA325 (I'm running from NAND). So the general tests remain are regression tests. If you like, you can boot with UART, and set the envs (cut/paste) to the values you have right now, see if you can boot into your Debian rootfs. The regressby bodhi - uBoot
Hi twinclouds, Thanks for the link to the Debian image. It is the best among all the images I've tried. However, I found out the hard way that Adobe does not provide Flash player for ARM !!! dmn… I've also tried gnash, but it did not play flash movies correctly. So now I'm back to stock Android.by bodhi - Allwinner A10
Updated test U-Boot for NSA325: http://forum.doozan.com/read.php?3,12381,17420#msg-17420by bodhi - Debian
NSA325 users, Here is the latest NSA325 U-Boot-2013.10 for testing. There are 2 files in this tarball. Both are NAND version from the same build. The mtd0 version is ready to flash. The uart version is used for uart booting. Successful UART booting with serial console is required, especially for flashing to NAND. This is very important so that the envs can be adjusted (due to the differencby bodhi - uBoot
dfarning, Quote> I have also created a step by step set of > instructions at > http://zyxel.nas-central.org/w/index.php?title=Debian_on_325 . Very nicely done! it will be a great help to people who start hacking. Typo correction: QuoteOperating System For this project we will download a prebuilt copy of Debian Wheezy for NSA325. This is minimal Debian Wheezy image with a fewby bodhi - Debian
Sounds good! I always have 2 serial console adapters. Got them for 2.5 bucks a piece so you'd never know when it goes bad :)by bodhi - uBoot
renojim, > Yep, that seems to work! I compared the output of > ethtool -k under 3.15 and 3.16 and the only > difference was the tx-tcp-segmentation setting > (off by default under 3.15 and on under 3.16). I > guess it would be interesting to see if changing > the setting under 3.15 causes the same data > corruption, but I don't know how useful that > inforby bodhi - Debian
InfoScav, > but, i got stuck in the netconsole itself, ie, > typing the 'killall nc' command in the ubuntu > terminal didn't do anything. LoL. had to > physically restart the dock. If you used the single command I mentioned above, just Ctrl-C to terminate. > > below is what prompt i got in the > command-terminal, after typing the netconsole >by bodhi - Debian
dfarning, Quote> On my setup, I need to disconnect both the power > cable and the serial cable from the nas before > rebooting and disconnect the usb-serial adapter > from the computer before rebooting otherwise there > are random failures. I agree with WarheadsSE. It sounds like you have either a faulty or incorrectly connected serial console?by bodhi - uBoot
dfarning, Quote> 4 out of 4 time successful upload with the smaller > test file with ext2 /boot and ext4 rootfs on a USB > stick. > 4 out of 4 time successful upload with the smaller > test file with ext2 /boot and ext4 rootfs on a > SATA drive. > > Does this seem stable enough to flash to nand and > do another round of testing with ext4 /boot? Ok, thanksby bodhi - uBoot
Various users have confirmed serious problem with files transfer using Samba (could also effect other protocols while transfering large files). If you are running kernel 3.16.x, it is recommended to implement a simple tweak to prevent data corruption during file transfering (thanks to ebbix for this tweak): Turning off TCP segmentation offload on kernel 3.16.0: apt-get install ethtoolby bodhi - Debian
I've posted test results at Arch forum: http://archlinuxarm.org/forum/viewtopic.php?f=9&t=7692&p=42160#p42163 Update: Turning off TCP segmentation offload on kernel 3.16.0 seems to work great, thanks to ebbix for the tip: ethtool -K eth0 tso offby bodhi - Debian
InfoScav, Your u-boot envs looks good. To run netconsole: 1. The Ubuntu VM (192.168.253.128) network NIC should be set in bridge mode (so it has visibilty both ways to the other machines). 2. On the Ubuntu VM, open a terminal and run nc -lup 6666 192.168.1.50 6666 3. Power up the GF Home, or reboot if you are running: shutdown -r nowby bodhi - Debian
@theliquid, Please install this release and let me know if PPP is working: linux-3.16.0-oxnas-tld-2-bodhi.tar.bz2 md5sum 892337daf4986390cc034d8be3ce56deby bodhi - Debian
InfoScav, Cool! glad you got it working. It's not all wild goose chase :) it's good learning experience. Except that you did not give up easily when seeing the problem! so you endd up spending a little more time than if you had just gone to the rootfs installation path sooner. And to set up netconsole, see Jeff's instruction: http://forum.doozan.com/read.php?3,14 In thisby bodhi - Debian
renojim, > Processing triggers for initramfs-tools ... > update-initramfs: Generating > /boot/initrd.img-3.16.0-kirkwood-tld-1 > Kernel suffix 1 does not match any of the expected > flavors (kirkwood), therefore not writing it to > flash. This is normal if you have flash-kernel package installed in your system. During kernel upgrade by dpkg, if flash-kernel is currentby bodhi - Debian
zzbao To tell u-boot to select the correct rootfs on the USB drive. Do these: 1. Boot without the HDD, in Debian, name the partition label for the USB drive rootfs: tune2fs -L rootfs /dev/sda1 2 .Change usb bootargs to: fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10' 3. Shutdown sync shutdown -h now 4. Plug in tby bodhi - uBoot