Hi Jean, Both the squeeze and wheezy scripts by Jeff were out of date (with respect to the Debian repo), so they are not working properly anymore. That's why I've released the rootfs mentioned above. This rootfs is a minimal Debian system, much like what you get after you ran one of these scripts. So currently this is the best way to get latest Debian kernel installed for the Dockstaby bodhi - Debian
Hi pbg4, So the behavior is consistent with the NSA310S PHY manual pokes. Everything works, but a minor glitch is some how the Ethernet port LED does not refect the true speed. I'll move this image status up to release thread. We'll look at the LED issue later. Thanks!by bodhi - uBoot
Hi pbg4, > since I am testing at the moment for a new > devicetree description to > let the nsa3xx-hwmon kernel module recognize the > nsa320 mcu I have here two > nsa320 boxes, Any luck in testing this NSA320 DTS change?by bodhi - Debian
I've uploaded a test u-boot for the NSA320. Please see: http://forum.doozan.com/read.php?3,23039by bodhi - uBoot
pratikworld, This is all you need to do (if the sdb1 is the USB drive that you want to create the rootfs on). sudo su mount /media/sdb1 cd /media/sdb1 tar -xjf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 sync And then do the rest of the installation, including modified step 4: Quote4. Create uImage with embbeded DTB (If this is not first time installation, please see Note 2 beby bodhi - uBoot
I've uploaded the Zyxel NSA320 u-boot-2014.07-tld-4 for testing. Download at Dropbox uboot.2014.07-tld-4.nsa320.bodhi.tar md5 22b705ca97eb8e804c69a14e2d2fe798 In this u-boot image, I've incorporated the fix for the network PHY problem. This problem occurs when the box is shutdown, and upon coming up with the Power button, the network link was not brought up properly. So the resby bodhi - uBoot
shivahoj Wrote: ------------------------------------------------------- > Hello, > about two weeks ago i wrote about the > missing/nonfunctional sensors stuff on zyxel > NSA320 (sudo sensors-detect finds no sensors). > I did not understand all of pbg4's and bodhis > messages about this Topic, regarding the > complexity of making this work in a current > keby bodhi - uBoot
pocket, I am not sure how can I help? Which part you of the installation that you had trouble with?by bodhi - Debian
Ah! I see. Fwiw, in the past, I had problem plugging in USB 3.0 to the Pogo E02 USB 2.0 port. It would crash the system. It migh have been the old EHCI driver . I have not attempted to test it again, though. In your case, it is the XHCI driver, so it is diferent problem. It might help googling tor XHCI problem, also for quirks related to this gadget.by bodhi - Debian
grayman4hire Wrote: ------------------------------------------------------- > I'm looking to use the reset button on the back of > the Pogoplug v4 to perform some action in Debian. > Does anyone have experience with this? > > My first thought is a "shutdown -h now" action but > it would be nice to have two actions, one for a > regular press of the buttby bodhi - Debian
grayman4hire, > anyone else noticed an issue with the USB 3.0 > ports on the PPv4 or other Kirkwood devices with a > USB 3.0 port? I do use the port frequently, but only with storage USB 3.0 (Sandisk Ultra Fit and Sandisk Extreme). Never notice any thing unstable either on Pogo V4 or NSA325v2. On the NSA325v2, it is used very heavily for a long stretch (do rsync with massive chanby bodhi - Debian
Jean BRUDER Wrote: ------------------------------------------------------- > Dear Doozan fans, > > I follow this forum since years now, and have to > thank you all so much for all your helps on how to > install Debian on my lovely Seagate Dockstar, > called "Docky" ;-) > > Since two days, because of a dayly used USB stick > since more than 4 yearsby bodhi - Debian
sz3bbylA, > still persist on boot > > [ 0.161017] : > /ocp@f1000000/ethernet-controller@72000/ethernet0- > port@0: local-mac-address is not set > [ 0.166529] No ATAGs? > > i have no explanation > but my nas is running well These are OK. They are not errors, only for information.by bodhi - Debian
Hi Dirk, Please don't double post! But while you are at this, could you verify that the NSA320 uses the Ethernet chip 88E1318 ?by bodhi - Debian
Dannii, It actually looks good, except for the "EHCI timed out on TD" error. Even with this error, it's OK, because your rootfs was not the one that timed out, and you can boot into Debian? To help the USB drives to have more time, set this variable to 15 seconds. You might want to try longer periods until you stop seeing this EHCI timeout (It does not take the whole period fby bodhi - Debian
sz3bbylA, - Ignore the local MAC address warning. No problem there. But don't change anything related to this ethaddr. - rootfstype is what pengu said above. Your USB rootf is using Ext3 file system. But your usb_rootfstype is Ext2, so to fix: fw_setenv usb_rootfstype ext2by bodhi - Debian
Dirk, Try this to see if you can turn it on and off: /bin/echo 44 > /sys/class/gpio/export /bin/echo "out" > /sys/class/gpio/gpio44/direction /bin/echo 1 > /sys/class/gpio/gpio44/value /bin/echo 0 > /sys/class/gpio/gpio44/valueby bodhi - uBoot
notoneofmyseeds, You have to be root user first while doing this. And cd /media/sunnsea/rootfs tar -xjf Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2 sync sync syncby bodhi - uBoot
pratikworld, > Please help. Is this because of the error in step > 3? If so what is the exact command that should be > executed? Yes. The solid greenLED is a good sign (kernel has started). But later the kernel has trouble mounting rootfs (because the errors in step 3). The error in step 3 is usually because you're not root user. You have to be root the entire time while yoby bodhi - uBoot
andr2k, > Looks like the only measure is to use a serial > cable. Not quite there yet! last questions: What was the LED behavior? did it flash green, then stayed orange (green+red) for brief moment and then solid green? please describe the LED sequence. Because you've successfully installed u-boot, have set up netconsole. Booting in to Debian is not difficult at all. Thereby bodhi - Debian
notoneofmyseeds, > But can someone please tell me how to do this: > > #usb_set_bootargs=setenv bootargs console=$console > root=$usb_root rootdelay=$usb_rootdelay > rootfstype=$usb_rootfstype $mtdparts > $usb_custom_params > usb_rootfstype=ext2 > > or: > > set_bootargs_usb=setenv bootargs console=$console > root=$usb_root rootdelay=$rootdelayby bodhi - uBoot
notoneofmyseeds, 1. The user/password credential above is for stock Pogo OS. Stock OS resides in NAND, so to boot that, you have to remove all USB devices attached. 2. If gaining access to the stock Pogo OS is not possible. I've suggested to use the latest Debian rootfs for booting above. And that is the Debian-3.16.0-kirkwood-tld-2 rootfs.. This can be found in the kernel/rootfs threaby bodhi - uBoot
I’ve uploaded the NSA325 u-boot 2014.07-tld-4 image. Please see 1st post for download link.by bodhi - uBoot
notoneofmyseeds Wrote: ------------------------------------------------------- > Many, many years past, I installed Debian Arch on > the Pink pogoplug. > > The USB stick of the install has long been lost. > > I'd like to install Debian again now, but I can't > ssh into the pogoplug. > > It starts and gets an IP, but since I don't know > tby bodhi - uBoot
pratikworld, Ok, so you actually bailed out in the middle of the installation :) Fortunately, the command to set the MAC Address failed, so there is hope. However, the rest of the u-boot envs were not set (arcNumber, machid, and few other envs). The good thing is you've done the step about flashing u-boot envs. At this point, I would try this as a best chance to get it boot Debian (by bodhi - uBoot
Hi Davide, See http://forum.doozan.com/read.php?2,22241,22990,page=10#msg-22990by bodhi - Debian
The good news :) I've switched gear and worked on the NSA325 u-boot today. It now brings the link up right away when u-boot starts. So we know what to do for the NSA3xx series. Now back to the NSA3x0S u-boot!by bodhi - Debian
pratikworld, > Ever since its stuck on a boot loop. I tried > everything from power cycling to fat32 drive with > revert folder. But it doesn't seem to work. What is the LED behavior in the boot loop? does it flash green, then flashing red, then flashing green again? please describe it. And if you have a log of what you've done so far, then post it here, or pastebin itby bodhi - uBoot