I used the "build" script from linux tv git repo here:

http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

derdigge Wrote:
-------------------------------------------------------
> I used the "build" script from linux tv git repo
> here:
>
> http://linuxtv.org/wiki/index.php/How_to_Obtain,_B
> uild_and_Install_V4L-DVB_Device_Drivers

Thanks for the link.

-- deleted



Edited 2 time(s). Last edit at 06/11/2013 04:35PM by bodhi.

Kernel 3.8.11 version 2 was uploaded. See 1st post for download link.

Can I use this kernel with Zyxel NSA 310 only replacing current kernel?

esc0bar Wrote:
-------------------------------------------------------
> Can I use this kernel with Zyxel NSA 310 only
> replacing current kernel?

I'm not sure whether it will work. Looking at the Arch Linux ARM patch file (May 07, 2013), there are 2 different patches for NSA310 and 320. I have not compared these 2 to see how different they are.

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

I have uploaded a basic Debian Kirkwood wheezy rootfs with kernel 3.8.11. See 1st post.

Thanks bodhi. That will be useful to many people.

But I can not find your patches for Kernel 3.8.11 package version 2.

-syong

syong Wrote:
-------------------------------------------------------
> Thanks bodhi. That will be useful to many people.
>
> But I can not find your patches for Kernel 3.8.11
> package version 2
syong,

Sorry I totally forgot about it, I usually create a unified patch after build and test the kernel!

First post was updated to include the patch file for version 2 in the corresponding section. Enjoy!

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

bodhi,

Great! Need your patches as I just got a nsa320.

Installed davy's kernel. Everything works except temp sensor.

The sensor works at the beginning, but jumps to 102C after a while.

-syong

syong,

It is strange that the NSA310 has one-bay but usually cost more than the NSA320. As far as I can tell the only other different in configuration is the eSATA port on the NSA310. Is there any other difference that you're aware of?

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

bodhi,

Besides pogo e02, NSA320 is the only other kirkwood device I have. Do not know NSA310. Here is what I think of e02 comparing with NSA320.

e02 is more compact although NSA320 is compact enough. No power brick and consumes less energy(5w vs 18w). Also needs no fan, totally quiet.

NSA320 has more features. It has RTC and eSATA and more leds and buttons. It also has temp sensors but not working right for me now. As a NAS, NSA320 exceeds e02 in power management. When I shut them down, I found the power is cut for NSA320 while e02 still consumes energy although not much. Wake_on_lan works for NSA320 while not for e02.

So I turn e02 all time on while use NSA320 mainly as backup server which I turn on/off remotely only when making backup.

-syong

@bodhi,

thank you very much for providing the tarball dated June 19th. I "germanized" it and tried it on all types of machines I have (Dockstar, GoFlex Net/Home, Pogoplug, NSA320) and all worked very well. I especially like the fact that on most of the machines the LED flashes during boot and will be solid green when fully booted. On the Zyxel, things seem a bit different, but since I do not have time and you do not have the machine, I can very well live with the way things are.

There is one serious point for improvement, though. This concerns DHCP. With the client you have installed, the IP-address is not released upon shutdown / reboot (at least here in my environment). A side effect of this is that the terminal from which one ssh'ed in will be left hanging and has to be killed.

The latter effect can easily be avoided by editing the nice .profile you set up and adding another pair of aliases as a workaround:

alias reboot="reboot && exit"
alias halt="halt && exit"

However, the problem about the release of the IP remains. Therefore, I installed an alternate dhcp-client, since the problem never occured with my former rootfs:

apt-get install isc-dhcp-client
apt-get remove dhcpcd

This takes care of both effects: the ssh-session will be closed before the shutdown / reboot, so the workaround is not necessary any more (although it will be faster in making the terminal available). Most importantly, the IP-address is released as it should be.

So, maybe, you might swap out dhcpcd for isc-dhcp-client if you ever have reason to provide another rootfs-tarball.

Another thing concerns those of us who (like me) use a separate boot partition. Here, installation is a bit different. Assuming the ext2-boot-partition is on /dev/sdx1 and the ext4-root-partition is on /dev/sdx2 and we have a directory /stick, here is how it goes:

sudo mount /dev/sdx2 /stick
# if not empty: sudo rm -rf /stick/*
sudo mkdir /stick/boot
sudo mount /dev/sdx1 /stick/boot
# if not empty: sudo rm -rf /stick/boot/*
sudo tar --strip-components=1 -xjf Debian-3.8.11-kirkwood-rootfs-bodhi.tar.bz2 -C /stick
#
# symlink (necessary for correct boot!)
cd /stick/boot
sudo ln -s . boot

Hopefully, this is useful for somebody.

Finally, a question, out of interest: what changes did you make compared with version 2 of your kernel (since I see that now it ends in "tld-3", while the one we used in our discussion before ended in "tld-2"; I am asking, because meanwhile I noticed something strange there and wanted to try your new package before I actually reported that ...)

---
Standart ist der Standardfehler



Edited 2 time(s). Last edit at 06/23/2013 02:37PM by chessplayer.

@chessplayer,

Thanks for point out that dhcpd behavior. I will take a look. This client is what we got from squeeze after running Jeff's debootstrap script, and then upgraded to wheezy, along with everything else. The only extra packages were what listed in the 1st post.

I've since built another kernel after I discovered that I missed a small patch regarding to the automatic trigger LED when there are SATA disk activity. I guess that what you saw in the LED behavior for the NSA320 :) This kernel is installed in the roofts as version tld-3.

Once I created a unified patch I will upload this kernel.

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

I had a disk image of my dockstar debian installation. Unfortunately, I deleted it by accident.
Tried your rootfs, its working!
You made me save a lot of time, thanks bodhi!

Kernel 3.8.11 version 3 was uploaded. Please see 1st post for download link.

@chessplayer,

> On the Zyxel,
> things seem a bit different, but since I do not
> have time and you do not have the machine, I can
> very well live with the way things are.

Did kernel tld-3 patch help solved this problem? is there any thing else you've found ?

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

@syong & chessplayer,

For your NSA320, do you use Davy's uBoot:
https://www.dropbox.com/sh/nwt2kbvetvgvroo/e-pNtdMhCC/Kirkwood/rootfs_images/NSA320quickstart
or do you use the stock uBoot? if you use Davy's uBoot, could you post that uBoot version number here.

Thanks,

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

Bodhi,

I use Davy's uBoot. Here is the output of the netconsole:

U-Boot 2011.12 (May 03 2012 - 17:04:23)
ZyXEL NSA320 2-Bay Power Media Server
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  9 

NSA320>

-syong

Thanks Syong,

Have you tried UART booting? Perhaps you could try my Goflex Net uBoot build to see if you see the same Netconsole problem?

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

Bodhi,

Never tried.

How to do that?

-syong

See Davy's post:
http://forum.doozan.com/read.php?3,7852,7852

The NSA320 has the boot ROM version that supports UART booting. So if you have serial console, you can boot in UART mode, it will not execute your installed uBoot. The kwboot tool mentioned in Davy's post is pretty good.

I can boot a Pogo E02 uBoot image on a GoFlex Net for sanity check. Of coure it won't complete booting , but you can stop it at the count down and do various things to see if it is running OK.

To try it out, you can use your saved Pogo E02 uBoot image and boot it on both your Pogo E02 and NSA320.

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



Edited 1 time(s). Last edit at 06/29/2013 10:22PM by bodhi.

Bodhi,

Thanks for the link. Will try.

So the motivation for UART booting is to test uBoot before committing to NAND?

-syong

Bodhi,

Seems UART booting working right here now.

Where is your Goflex Net uBoot build and what is the Netconsole problem?

-syong

Syong,

I've attached the uBoot image in this post.

Basically, netconsole is broken for me in that whenever I try to run a command, the 2nd character is lost. For example, printenv becomes pintenv. If I run prrintenv then it would work OK.

Since we have uBoot envs scripted as several chained commands, this causes other boot commands envs to abort. So you can't boot with netconsole running.

It would be good to know if you or others will see the same problem I'm seeing. I suspect there is a race condition, because when I turned on uBoot debug mode, I did not see the problem with loosing 2nd character, but it still won't boot.

BTW, I'm testing this uBoot image this way:
- On a Dockstar, use kwboot to start serial console and load uBoot image to boot the GoFlex Net with UART.
- Interrrupt uBoot in serial console.
- Start netconsole to connect to the Goflex Net from the Dockstar on another terminal.
- On serial console, start netconsole client (i.e. preboot env)
- Back to netconsole server on the Dockstar and execute various commands to test.

Thanks,

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

Bodhi,

I have tried your uBoot image. I can not get NSA320 network initialized with this uBoot. Here is the output:

(%5)(07:42)(pis)/mnt/tftp> ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2013.07.goflexnet.mtd0.kwb -p                                                                    
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
...
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2013.07-rc1 (Jun 29 2013 - 02:09:32)
Seagate GoFlex Net

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
88E1116 Initialized on egiga0
Using egiga0 device
ping failed; host 192.168.0.56 is not alive
Hit any key to stop autoboot:  0 
u-boot>> 
u-boot>> run preboot
Using egiga0 device
ping failed; host 192.168.0.56 is not alive
u-boot>>

So the uBoot for GoFlex can not initialize the egiga0 device on NSA320. uBoot for E02 could not initialize the NSA320 network either.

I also tried uBoot for NSA320 from Davy and netconsole worked.

-syong

Syong,

Thanks for trying, too bad I was hoping it would work pass that point! But thanks to your test I know my setup is not a problem.

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



Edited 1 time(s). Last edit at 06/30/2013 03:45PM by bodhi.

Header package linux-headers-3.8.11-kirkwood-tld-3 was uploaded. Please see 1st post for Dropbox link.

I'm a bit of noob, but...I gave this a go on my TonidoPlug2.

I have yet to be successful. Here is what I did:

1) made a fresh stock tondo install on a usb stick (that's squeeze),
2) added the wheezy package sources to /etc/apt/sources.list,, apt-get update, and the installed the mkimage tools
3) pulled down the 3.8.11 image, installed it as per this post, using the instructions for 3.6.11, and subbing the file name

now here we go:

the second mkimage command failed, like this:

Quote
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.8.11-kirkwood-tld-3 -d /boot/initrd.img-3.8.11-kirkwood-tld-3 /boot/uInitrd
mkimage: Can't open /boot/initrd.img-3.8.11-kirkwood-tld-3: No such file or directory

so i booted it anyways, (just because i'm trying to learn), and saw this on my serial console:

Quote
## Booting image at 00800000 ...
Image Name: Linux-3.8.11-kirkwood-tld-3
Created: 2013-07-01 7:08:34 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1806280 Bytes = 1.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0000020f).


Available machine support:


ID (hex).NAME

00000690.Marvell DB-88F6281-BP Development Board
00000691.Marvell RD-88F6192-NAS Development Board
00000692.Marvell RD-88F6281 Reference Board
0000078c.Marvell 88F6281 GTW GE Board
00000831.Marvell SheevaPlug Reference Board
00000bb6.Seagate FreeAgent DockStar
00000c11.Seagate GoFlex Net
00000d0a.Seagate GoFlex Home
00000b36.Iomega iConnect Wireless
00000f78.Pogoplug V4
00000dd6.Pogoplug E02
0000085b.QNAP TS-119/TS-219
000009c6.QNAP TS-41x
00000b44.Marvell OpenRD Ultimate Board
00000939.Marvell OpenRD Client Board
00000915.Marvell OpenRD Base Board
00000f74.ZyXEL NSA320 2-Bay Power Media Server


Please check your kernel config and/or bootloader.
(I removed the double-spaces)

Wondering if:
a) this means I need the topkick board ID added to a future build, and
b) if so, can I make that request here?
c) if not, then any advice greatly appreciated.

thanks much

@postman,

Before installing kernel, what do you have? can you ssh in?

What's your output when you run dpkg -i to install? if you got error and didn't not generate initrd.img, then you can't boot Debian.

And I guess you've determined that you have Topkick? (according to Arch site there are 2 variations). The Topkick patch is available in Arch Linux ARM master patch file, so yes, it is possible to include it in the next build. But it will take some works to extract the patch.

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



Edited 1 time(s). Last edit at 07/01/2013 04:08AM by bodhi.