Proper support for IcyBox NAS6210 & NAS6220

Install Arch Linux ARM on other devices.

Proper support for IcyBox NAS6210 & NAS6220

Postby oreggin » Fri May 11, 2012 5:13 pm

Hy!

I use an IB-NAS6220 for some month and is works perfectly with archlinuxarm and with "arcNumber=1680" u-boot environment variable. However some basic function is missing from kernel, like Power LED, and Linux kernel poweroff function.

I have found on the net this description: http://simon.baatz.info/raidsonic-icy-box-ib-nas6210-my-new-sheevaplug/
This descripbe how to patch the kernel to make works PowerLED and Linux kernel poweroff function on NAS6210.

I was modified the patch to works for NAS6220.

Cheers,
oreggin
Last edited by oreggin on Fri May 11, 2012 5:22 pm, edited 1 time in total.
oreggin
 
Posts: 8
Joined: Fri May 11, 2012 4:20 pm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby oreggin » Fri May 11, 2012 5:22 pm

Here are the patches.
Attachments
nas6220_patches.tar.gz
patches for linux v3.1.10, v3.2.16, v3.3.4 kernels
(2.63 KiB) Downloaded 900 times
oreggin
 
Posts: 8
Joined: Fri May 11, 2012 4:20 pm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby WarheadsSE » Fri May 11, 2012 5:53 pm

Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby kmihelich » Fri May 11, 2012 5:54 pm

We already support the NAS6210, which uses the exact same board file you supplied for the 6220 with the exception that it uses its own ID number, not re-purposing another device's ID. You need to set your arcNumber to 3104, save, reset, and you'll be good to go.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby oreggin » Fri May 11, 2012 6:11 pm

$this->bbcode_second_pass_quote('kmihelich', 'W')e already support the NAS6210, which uses the exact same board file you supplied for the 6220 with the exception that it uses its own ID number, not re-purposing another device's ID. You need to set your arcNumber to 3104, save, reset, and you'll be good to go.


I think you did't read my whole post. Current kernel in archlinuxarm is not support PowerLED and kernel shutdown in nas62x0:
- on fully booted up box the PowerLED is blinking forward
- the box don't poweroff when I issue "halp -p"

With patches what I uploaded, the kernel do this. So developers need to make a kernel for nas62x0, not for nas6210 only, as - you wrote - the two box is differs only in the arcnumber.

regards,
oreggin
oreggin
 
Posts: 8
Joined: Fri May 11, 2012 4:20 pm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby kmihelich » Fri May 11, 2012 6:20 pm

I think you didn't understand a word I said. I'll break it down.

Your patch is the exact same thing that we already have, except that instances of "6210" have been replaced with "6220."

Your problem stems from the fact that you were booting with the arcNumber 1680 and not the correct ID of 3104. Using 3104 will boot your board with the NAS6210 that is already in our kernel.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby oreggin » Sat May 12, 2012 11:49 am

sorry for misunderstanding but in my opinion I should not need hacking u-boot environment variables to handle arhlinux kernel my device. Kernel maintainer should write a proper code to archlinux kernel recognize my device arcnum 527 and than runs the same code on both NAS6210 and NAS6220.

cheers,
oreggin
oreggin
 
Posts: 8
Joined: Fri May 11, 2012 4:20 pm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby xenoxaos » Sat May 12, 2012 3:18 pm

Actually, the Icybox did the wrong thing and just modified the kernel source of the generic Marvell Dev Board. ArcNumber 1680 (http://www.arm.linux.org.uk/developer/m ... hp?id=1680) is NOT for the IcyBox. The CORRECT arcNumber is 3104 (http://www.arm.linux.org.uk/developer/m ... hp?id=3104). These are the proper kernel arcNumbers. The only one that 'hacked' the kernel u-boot environment is IcyBox.
Arch Linux ARM exists and continues to grow through community support, please donate today!
xenoxaos
Developer
 
Posts: 323
Joined: Thu Jan 06, 2011 1:45 am

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby kmihelich » Sat May 12, 2012 4:27 pm

Yep, the proper code actually resides in our kernel. This is the actual device registered to 527, and as you can see it's very much not a Raidsonic or even a Marvell Kirkwood device: http://www.arm.linux.org.uk/developer/m ... php?id=527
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: Proper support for IcyBox NAS6210 & NAS6220

Postby oreggin » Sat May 12, 2012 4:53 pm

I don't see 3104 or 527 archumber in the vanilla kernel tree:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=blob;f=arch/arm/tools/mach-types;h=f9c9f33f8cbe2f651277793400d8287eec0073c9;hb=dd775ae2549217d3ae09363e3edb305d0fa19928

In the linux kernel tree, the arm arcnumbers is changing continuously and for example 527 removed a year ago:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=6f82f4db80189281a8ac42f2e72396accb719b57

BTW, I'm a customer and one of NAS6220 users and we bought our boxes with 527 arcnumber and not 3104 or any. We don't care marvell or icybox or anyone else stupidity. What we want is to our boxes are working properly, but I think I'll don quijote if I continuing this pointless conversation :(
oreggin
 
Posts: 8
Joined: Fri May 11, 2012 4:20 pm

Next

Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 43 guests