Thank you for update. With this network on NSA310 works. It complains about firmware (firmware: requesting rtl_nic/rtl8168d-2.fw), which can be fixed with installing firmware-realtek package from non-free (but probably we don't need this firmware, becouse without this network works without problem).

After I got network working I could start testing Debian on NSA310 with your kernel. LEDs are working, network LEDs are not (I don't mind that). Another missing module is lm85 (CONFIG_SENSORS_LM85), which we need for fan control (fan is full speed now).

Tom62,

Dang! the NSA310 is really different from its big brothers :) I did not recall anybody reported that for NSA320, or perhaps I missed it?

Thanks for testing Tom. I will be on the road in a few days, but will get you the updated kernel to fix the fan before that.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> @bertc3p0,
>
> Glad you've sorted it out!
>
> So I see you've installed Emdebian following
> Jeff's instruction. And your rootfs is emdebian,
> but you also updated the kernel with
> Linux-3.12.0-kirkwood-tld-3 ? how large is your
> rootfs now? I assume it fits the Dockstar
> remaining 255MB NAND without problem? did you have
> to remove any module?

I've installed Debian-3.12.0-kirkwood-tld-3-rootfs-bodhi.tar.bz - remaining 21% capacity on
the LZO compressed ubifs. Still need to mount some parts of /var to ramfs ...
Hopefully everything fit into the ubifs (need some kind of lamp - grrrr ). Otherwise
I'll make a embedian system with multistrap and take your your kernel.

Again, thanks for your fantastic work, bodhi !

BTW: Does the latest uBoot builds 2013.10 also run on Dockstar ?

bertc3p0,

uBoot has to be built for a specific box. So far I've uploaded only 3 uBoot images: GF Home, GF Net, and Pogo E02. I have built the Dockstar uBoot, and running it, but have not tested it with the large HDD. I would take request, but nobody has asked for it yet, so did not have motivation to complete the testing :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Kernel 3.12.0-kirkwood-tld-5 package was uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> bertc3p0,
>
> uBoot has to be built for a specific box. So far
> I've uploaded only 3 uBoot images: GF Home, GF
> Net, and Pogo E02. I have built the Dockstar
> uBoot, and running it, but have not tested it with
> the large HDD. I would take request, but nobody
> has asked for it yet, so did not have motivation
> to complete the testing :)

Would it be possible to build a uboot image for the zyxel nsa325?

Im haveing some trouble with your latest rootfs that you uploaded bodhi anytime i create a new user their home directory is not getting created and even if i create it its not used on next login?

this is on a fresh install with a brand new usb on the nsa325.

Buttzy10169 Wrote:
-------------------------------------------------------
> Im haveing some trouble with your latest rootfs
> that you uploaded bodhi anytime i create a new
> user their home directory is not getting created
> and even if i create it its not used on next
> login?
>
> this is on a fresh install with a brand new usb on
> the nsa325.

Thanks Buttzy, was it Ok with the older rootfs or does it behave the same way too?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Guys,

I have a Pogoplug Pro thats booting directly off SATA and has Squeeze running in it. Since its not booting off NAND, can I directly deploy rootfs? Will that work? There is no plan to goback to booting using USB. SATA is permanent. I was hoping to use new kernel 3.12.

I'm nearly sure this rootfs was working for me.(tld-3) unless I'm getting mixed up but it did work before.

I'm trying to install paragon ntfs drivers but in order to install it, I need kernel source. What should I do. I'm getting the following error message

Quote
configure: error: "Can't find kernel source files"

I'm using
root@debian:/tmp/p# uname -a
Linux debian 3.12.0-kirkwood-tld-3 #3 PREEMPT Wed Nov 27 16:10:53 PST 2013 armv5tel GNU/Linux

Almaz,

The kernel patch is in the tarball for 3.12.0-kirkwood-tld-3 in the first post. And you can download the kernel source tree for 3.12.0 from kernel.org.

But why Paragon? ntfs-3g should work fine.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/01/2014 10:37AM by bodhi.

Thanks for a quick reply. Paragon NTFS driver should be much faster compared to ntfs-3g from what I can read. I'd like to test it out.

Would you be kind enough to point me to the right directions installing Paragon driver or build Paragon NTFS driver for us? I already spent a few hours and just can't get it right. Paragon NTFS driver should 2-3 times faster than ntfs-3g

Here is the install log error I'm getting.

https://www.dropbox.com/s/z9yu65536yn79qv/paragon-ufsd-install.log



Edited 1 time(s). Last edit at 01/01/2014 05:04PM by Almaz.

Almaz,

I'm not familiar with Paragon driver. May be others here can give you a hand. I'm on the road so can't help you build it. I could help doing that in a few weeks if you still need it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I may be misinformed, but I thought that the paragon driver was closed source.

Hi guys,

I had a strange problem the past few days with kernel 3.12.

During this christmas break, I decide to install some new packages on my Goflex Net.
I came back to this forum and see that a recent kernel is available (I was still using 3.3.2 booting from usb).So before doing anything else, I decided to update the UBoot and the kernel. Everything went smoothly by following the instructions (thanks guys for the hard work :))

But when I started to install new packages, the Goflex was sloooooww. So I interrupted the install and run some test (dd from /dev/zero)
On the USB and the SATA disk, write speed was averaging 60KB/s o_O (read speed was normal)

I restore the USB drive back to 3.3.2 (with the new uBoot) - no problem
I tried the rootfs-3.12.0 - no problem (but I lost all my packages and conf. So that wasn't a proper solution for me)

Back to 3.3.2, I then downloaded every major version of the kernel in this thread and installed them :
3.8.11 - no problem
3.9.11 - no problem
3.10.4 - no problem
3.11.1 - no problem
3.12.0 - write speed issue

So it seems something is broken in the kernel 3.12 with a certain configuration (3.12 rootfs wasn't affected) on the Goflex Net.

Personally, I'm going to stay with version 3.11.1 :p
But if you have question or want me to test something, I will be happy to help :)

Again thanks for the hard work
MG

MG,

Thanks for reporting your observation. Did all kernel 3.12.0 versions tld-1, 3, 4, and 5 behave the same way with low write speed in your test? did you install each one from version 3.3.2 or just progressively going from 3.3.2 to 3.12.0-tld1, tld-3,….?

And could you post the commands and outputs in your tests here?

Thanks!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Bodhi,

I tried 3.12.0 tld1,3 & 5 : same result.
For that particular test, I installed them progressively. But during my first update, I went straight from 3.3.2 to 3.12.0 tld5 and had the same issue.

Basically, i just dd if=/dev/zero of=/test count=50000

I included a bunch of log from differents versions with the dd command outputting on USB/SATA (aka /media/disk1) & dmesg

quick note :

- When in kernel 3.12.0 if I "mkimage" uImage and uInitrd based on kernel 3.11 (that takes a few minutes) and reboot. Write speed is back to normal.
- I also include the result for 3.12.0 tld1 rootfs. No issue there.
- I forgot to “count=5000” in the 3.3.2 test but you get the point.

Tell me if you need something else :)

MG

Thanks MG :) very interesting results! I will take a closer look at this.

Especially it's a little puzzling why the basic 3.12.0-tld-1 rootfs test shows normal write speed? but kernel 3.12.0-tld-1 installed on a different rootfs shows slow write speed. I could try the same test on my 3.12.0-tld-5 on the Dockstar to see if it behaves differently. For GoFlex Net, I will have to wait till I'm back home.

On a cursory glance, the only thing that stands out in dmesg is:

[   38.807693] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Yeah I saw that but that shouldn't affect SATA speed.
Anyway, I fsck it and the speed issue are still there ...

Hi Bodhi,

How do I use GPIOs with your kernel on the NSA320?
I was using davygravy's kernel so far and my buttons worked well with the use of input-event-daemon. After the change to your newer kernel 3.12.0-kirkwood-tld-1 the gpios are claimed by the gpio-keys module but the input-event-daemon in monitoring mode does not see any button clicks.

Input-event-daemon is monitoring /dev/input/event0 which of course exists.
When I unload the gpio-keys module I can see the changing value of /sys/class/gpio/gpio37/value from 1 to 0 (yes, opposite) when I press the copy button, after exporting it naturally.

------------------------------------------------------------------
# cat /sys/kernel/debug/gpio
GPIOs 0-31, orion_gpio0:
gpio-12 (nsa320:green:hdd2 ) out lo
gpio-13 (nsa320:red:hdd2 ) out lo
gpio-15 (nsa320:green:usb ) out lo
gpio-28 (nsa320:green:sys ) out lo
gpio-29 (nsa320:orange:sys ) out hi

GPIOs 32-49, orion_gpio1:
gpio-36 (Reset ) in hi (act lo) - IRQ edge (clear )
gpio-37 (Copy ) in hi (act lo) - IRQ edge (clear )
gpio-39 (nsa320:green:copy ) out lo
gpio-40 (nsa320:red:copy ) out lo
gpio-41 (nsa320:green:hdd1 ) out lo
gpio-42 (nsa320:red:hdd1 ) out lo
gpio-46 (Power ) in lo (act hi) - IRQ edge (clear )
gpio-48 (power-off ) out lo
-------------------------------------------------------------------------------------

What could be causing this problem?

BR
Włodek

Włodek,

I dont have access to the NSA320, and also away from home. Others who have the NSA320 should answer your question.

Also see this thread:
http://forum.doozan.com/read.php?2,14351

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/07/2014 10:42PM by bodhi.

@MG,

Tested my Ext3 USB thumb, mounted on the Dockstar running 3.12.0-kirkwood-tld-5:

root@dockstar:/# dd if=/dev/zero of=/media/HOME/test count=50000
50000+0 records in
50000+0 records out
25600000 bytes (26 MB) copied, 1.24842 s, 20.5 MB/s

root@dockstar:/# mount | grep HOME
/dev/sdb1 on /media/HOME type ext3 (rw,nosuid,nodev,noexec,noatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@MG,

Running kernel 3.12.0-kirkwood-tld-5, if the HDD is mounted at sda1, what's your output of

hdparm -C  /dev/sda
udevadm info --query=all --name=/dev/sda1
mount

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Done.

/dev/sda is USB
/dev/sdb is SATA

I did the whole thing in 3.12 & 3.11.

Logs are in the zip ...

Hello,
I have a NSA325 and I can't seam to find a set of comprehensive installation instructions.
To date I have chrooted my original zyxel with debian 6. I would ideally like to move this into a full environment as I have exhausted the abilities of the stock kernel.
I have tried to install your rootfs using the download 'Debian-3.12.0-kirkwood-tld-3-rootfs-bodhi.tar.bz2' and using the script I found on archlinux made some modifications to use this instead. all ran as expected except when the system tried to boot it hung at 'Waiting for root device...'
after this I successfully installed and booted into arch. What am I doing wrong?
the script I was using is from http://archlinuxarm.org/platforms/armv5/zyxel-nsa325
The only line I changed from arch install script was
tar -xjf /mnt/parnerkey/Debian-3.12.0-kirkwood-tld-3-rootfs-bodhi.tar.bz2 -C /tmp/rootfs/

Cheers,
Mark

mgazza try following my instructions here:

http://forum.doozan.com/read.php?2,14351

Ah I see the bootcmd needs to change.
fw_setenv bootcmd_linux 'setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr) /uImage; ext2load ide 0:1 0x01100000 /uInitrd; bootm $(loadaddr) 0x01100000'

I'll give that a go :)
thank you!