Problem Led support for Iconnect device

[minscof]

Hi,

I have an Iomega Iconnect device, and I have installed archlinux 3.1.4-2 using the usb method described here : http://archlinuxarm.org/forum/viewtopic.php?f=27&t=1472

It works very well, but I can't manage leds because it seems they are not detected during boot. There is a patch for that :
https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux/archlinuxarm.patch included in 3.1.4-2,

but I think my board is not recognized as an Iomega Iconnect board but as a "Marvell RD-88F6281 Reference Board" (cat /proc/cpuinfo), so I think the patch is ignored.

Can someone help me to have my board recognized as an Iconnect board or explain what is wrong with my conf ?

Thanks

[Fatum]

Change environment variable on u-boot

$this->bbcode_second_pass_code('', 'setenv arcNumber 2870
saveenv
reset')

Leds will work ok.

[minscof]

Thank you for your answer. I dont know Uboot, but I read that fw_printenv and fw_setenv commands can be used to list and modify Uboot env variables under Linux. Can you confirm this, and can I use fw_setenv to change the arcNumber ?

Thanks for your help.

[Fatum]

Yes you can change it under linux using fw_setenv. But BIG warning: you can't boot original system with arcNumber 2870. You need to use arcNumber=1682.

[igorert]

I would very strongly advice against doing this unless you have a working serial connection to change it back if things don't work out. 2870 is just a number somebody (probably openWRT folks) registered for iconnect. As far as I can tell, there is no iconnect-specific code in the mainline kernel so I doubt changing the arcNumber will do you much good.

As I mentioned in the main iconnect thread, I actually have working code for controlling iconnect LEDs without changing the arcNumber. If enough people are interested in it, I'll try to clean it up and see if I can get it accepted to archlinuxarm codebase.

[igorert]

Heh, I take it back - it looks like archlinux folks did add support for arcNumber 2870 in 3.1.1-2 even though it's not in mainline. You still won't be able to boot the stock Iomega kernel if you change the acrNumber though so do let me know if there is interest in supporting LEDs on the "stock" arcNumber.

[Fatum]

On arcNumber 2870 we have working leds and gpio-keys but serial cable recommended
There is some info about iconnect and arch linux at polish site : http://openrouter.info/forum/viewtopic.php?f=39&t=1232

[minscof]

Hi, thank you for all these informations. I hesitate now because I would like having led control but I have no serial connection to restore system if needed. I find very interesting to be able to come back to the original system, just taking off the USB key.

Igorert, you seem to be sure that changing the arcNumber will prevent to boot with the original Linux : can you confirm this ? is it totally incompatible ?

I m not a specialist, and I m looking for a solution to use ArchLinux on this board and have the led control : is there any other safe way to do that ?

Thank you for your help.

[igorert]

$this->bbcode_second_pass_quote('', 'I')gorert, you seem to be sure that changing the arcNumber will prevent to boot with the original Linux : can you confirm this ? is it totally incompatible ?

[WarheadsSE]

Does the iConnect's uboot support scripting at all? because it would not be that hard to say:
a) If USB found & labeled "rootfs", set archNumber=YYYY, boot from usb.
b) no "rootfs" found on usb, set archNumber=XXXX, boot from NAND (or whatever)