Currently, we don't have the NSA325 patch. What are the differences, spec wise, between NSA325 and 320?by bodhi - Debian
WhiteFang, Indeed, most of us forgot to save the orginals, or even thought about doing that. I did look for you, but could not find mine in the archives somewhere :) you probably could get the list, probably from somebody at Arch site? BTW, the Pogo Mobile can be reversed easily to original if installed only Arch. So if somebody is about to do the reversal to factory, it's a perfect tby bodhi - uBoot
WhiteFang, You will need to get the env variables from the orginal Pogo uBoot. If you have installed Arch version of uBoot, or Davy's uBoot then the envs are no longer the same as orginal ones. And work backward from the boot cmd on that version, you will see the chain of cmds that eventually get to booting NAND.by bodhi - uBoot
WhiteFang Wrote: ------------------------------------------------------- > These parameters: > > mmc_bootcmd 'mmc init; run mmc_set_bootargs; run > mmc_boot' > mmc_boot 'mw 0x800000 0 1; ext2load mmc 0:1 > 0x00800000 /boot/uImage; if ext2load mmc 0:1 > 0x01100000 /boot/uInitrd; then bootm 0x800000 > 0x1100000; else bootm 0x800000; fi' > mmby bodhi - uBoot
Debian Kirkwood rootfs 3.10.4 was uploaded. Please see 1st post for download link.by bodhi - Debian
Gaogao, "Still no events from the power button". I don't have the NSA320 so not sure about this. It might not be related to the Config_Marvell_Phy option. As I recalled, iConnect has similar button, and I needed a script to manage the event. I imagine the NSA320 would have the same kind of script that should come with the stock installation. Perhaps others who have set thisby bodhi - Debian
Art Freeman Wrote: ------------------------------------------------------- > majic79 - thanks for confirmation on the pin > numbers. This should help future users with the > same issue. > > bodhi - Yes, I originally followed the Arch ARM > directions to a successful install. Tried getting > a SAMBA server running and, due to excessive > tinkering, ended up hosiby bodhi - Debian
Kernel 3.10.4 Kirkwood package was uploaded. Please see 1st post for download link.by bodhi - Debian
Art Freeman Wrote: ------------------------------------------------------- > scanning bus for devices... 1 USB Device(s) found > scanning bus for storage devices... 0 > Storage Device(s) found > Hit any key to stop autoboot: 3 2 1 0 > It seems either you don't have USB drive attached, or if attached it can not be used. What was the state of yourby bodhi - Debian
Gaogao, Possibly. See this post: http://forum.doozan.com/read.php?2,12096,12987#msg-12987 I will release 3.10.4 with this config option (in a couple days).You can give it a try then!by bodhi - Debian
mindm49907 Wrote: ------------------------------------------------------- > Hello again people, > > bodhi's advice did the trick! > Thank all of you very much for your help! > > Vi > ctory screetch! :)) Congrats !!! glad to hear your NSA320 is alive and well.by bodhi - Debian
What you should do is upgrading your squeeze stick to wheezy. There is no need to reinstall. - backup your stick first in case something goes wrong. - change your apt source list to point to wheezy (use whatever source is appropriate for your location, I'm using my location as example): cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian wheezy main - update and upgradby bodhi - Debian
It turned out that there was indeed a subtle change in the kernel 3.10.x regarding Kirkwood USB devices. The ehci-orion driver was part of the kernel before 3.10.x but now introduced as kernel module to be loaded during boot (I have not looked at the source code, but it seems to be the case). There is a new config option, and I did not notice that with "make oldconfig". The same conby bodhi - Debian
Just tried the kernel build this morning and Debian Kirkwood kernel 3.10.4 is now booting from USB :) Will post the details later.by bodhi - Debian
pbg4 Wrote: ------------------------------------------------------- > @bodhi, > > the zyxel NSA320 has according to its specs: > > "Gigabit jumbo frame support up to 9K bytes" > > best wishes pbg4 > > p.s. I have two of these boxes running under > debian, the only problem ist to silence the fan > inside, > the rest is good value,..by bodhi - Debian
Hi pbg4, Thanks for the info. Actually I've tried the Arch patch before to see if the behavior is different. But the same problem occured! But thanks for reminding me to think about Arch distribution and why they don't have any USB booting problem! and you're running Debian and you don't have problem with HDD booting. Very good clues! I think I am close to solve this. Stayby bodhi - Debian
It seems something has changed in kernel 3.10.x. I'm having problem with mounting rootfs in kernel 3.10.4. Comparing the dmesg log for kernel 3.9.11 and 3.10.4, I noticed that udev did not seem to enumerate the USB devices during loading rootfs (in initrd pre-mount). That caused the classic /dev/root not found problem. I've confirmed this was the problem by looking at /dev while insideby bodhi - Debian
z3bram3n Wrote: ------------------------------------------------------- > DavyGravy tarball. I installed his tarball from > the initial posting and along with his included > new uboot. I was looking at the other methods of > using a stick to run the debian install. I have > the NSA320. After you installed and running, it's the same as any Debian rootfs. Yes, runninby bodhi - Debian
eas Wrote: ------------------------------------------------------- > Thanks. To be clear, I didn't have any sort of > error while generated the initrd.img. Its just > that it couldn't mount the root file system due to > flash-kernel forcing it to look for "/dev/root" > rather than the bootparam I'd configured in > uboot. > > On the upsidby bodhi - Debian
toomyzoom, What brand is your USB stick? that might have something to do with the problem. Ext3 will be OK if you relocate all the log files to /tmp, and use it only for rootfs, and hard drive for data.by bodhi - Debian
Which tarball?by bodhi - Debian
WhiteFang Wrote: ------------------------------------------------------- > Hello, > sorry to bump an old thread but I have the same > problem, and I have set the same parameters, but > still I can't boot from SD (hangs at "Starting > kernel..."), only USB. How can setting these > envs: > usb_init=run usb_scan; setenv usb_root > LABEL=rootfs > hby bodhi - uBoot
I'd like to bring this thread back alive so we can post the latest Kirkwood or other plugs deals :) Also I'm wondering why the Zyxel 310 always costs more than the NSA320? spec-wise, the only difference I can tell is the NSA310 has eSTATA port, but the NSA320 has 2 SATA bays while the NSA310 has only 1 SATA bay. And does either of these Zyxel boxes support Gbit jumbo frame?by bodhi - Debian
@enki, I don't think you need to recycle the power at all. I never did that. Just wait for a while to see if the handshake working or not. If you care to try, since your GoFlex is practically bricked without UART booting, get another plug. Could be a cheap one like the Mobile, install Debian. And connect the Nokia cable to that, and run ARM kwboot. I run my serial console from a Docksby bodhi - uBoot
@enki, To be clear, how do you run your kwboot binary? From an Intel-based 32 Ubuntu laptop/pc? (i.e. what host is your serial console module plugged in)?by bodhi - uBoot
majic79 Wrote: ------------------------------------------------------- > I'll update the thread with instructions for the > GoFlex Net and build you one at the same time - it > will be largely untested (I don't have a GFN to > test with unfortunately) but the instructions > ought to allow you to develop it a little and test > it if we can get you de-bricked. &gby bodhi - uBoot
laprjns Wrote: ------------------------------------------------------- > I use this wire wrap tool > Radio Shack Wire Wrap Tool Thanks laprjns! got one from Radio Shack today. They do have them in many different store locations in US, for $6.99 :) but these store don't have the wirewrap terminals. I guess it will have to be eBay?by bodhi - uBoot
enki, The GoFlex Net works with UART booting. I used UART booting on GoFlex Net to test uBoot builds. I've never seen any report that certain GoFlex Net version has different bootrom. Chance is that your 32 Ubuntu kwboot does not work. It does not hurt to try the 64 version see if you can run it. Too bad you don't have another plug (e.g Pogoplug V2, Mobile,...) , if you do thenby bodhi - uBoot
@enki, You don't need new uBoot image. The one you download should work perfectly. You only need a way to run kwboot to boot UART with this image. Have you tried that Ubuntu 32 kwboot with -p parameter?by bodhi - uBoot
enki, I think if you run your Ubuntu 32 version with the -p option it will work.by bodhi - uBoot