[ARMedslack] iOmega iConnect

Dave Dowell dowelld at netscape.net
Fri Jul 1 20:49:04 UTC 2011

I was right about the kernel code for making the leds work, I have 
managed to get it working. It creates an object for each led in 
/sys/class/leds and each led contains a brightness object which can be 
manipulated to change turn the leds on and off... now I just have to 
work out how to automate that with udev. The same code also includes the 
objects for the onboard button, but I'll be buggered if I know where to 
start with that one yet. I can see it has been found and that the 
interrupts are being detected when it's pressed though :-)

I'll knock up a page with some information / downloadable files and put 
up for this, once I've moved this all forward a bit.


On 01/07/2011 20:19, Greg Lim wrote:
> Dave, this is great work. You've inspired me to purchase one of these.
> -Greg Lim
> Sent from my VT102
> On Jul 1, 2011, at 5:18 AM, Dave Dowell <dowelld at netscape.net 
> <mailto:dowelld at netscape.net>> wrote:
>> Hello everyone,
>> I've installed ARMedslack onto one of these now.
>> http://go.iomega.com/en/products/network-storage-desktop/wireless-data-station/network-hard-drive-iconnect/
>> *Specification*
>>     * Desktop, compact form factor
>>     * Marvell 6281 CPU at 1.0GHz with 256MB RAM
>>     * 1 x RJ45 10/100/1000Mbps (GbE) Ethernet port
>>       LAN standards: IEEE 802.3, IEEE 802.3u
>>     * Wireless (802.11b/g/n)
>>     * 4 x USB 2.0 ports (to connect external HDD, printers)
>>     * AC Voltage 100-240 VAC
>>     * Power consumption – 5 Watts
>>     * Documentation localized for 18 languages, including; English,
>>       German, Spanish, French, Italian, Brazilian Portuguese, Chinese
>>       Simplified, and Russian
>> It doesn't mention the onboard flash memory there, but it also has 
>> 512MB of flash built in.
>> It's a Marvell Orion board inside, complete with the header for a TTL 
>> to USB serial console.
>> The console can be rigged like this http://doip.org/iconnect_console
>> I've recompiled the kernel to include the following options: (Could 
>> these be added into the standard ARMedslack kernel config please ?)
>> > CONFIG_RT2800PCI=m
>> > CONFIG_RT2800PCI_RT33XX=y
>> > CONFIG_RT2800PCI_RT35XX=y
>> However it probably only requires the first of them. This has made 
>> the onboard Ralink wireless adapter available.
>> I'm trying to hack the mapower architecture code changes into the 
>> kernel code to get the pretty LEDs working, but have had varying 
>> degrees of success with that so far, I think I've got the code in and 
>> working, however I've yet to figure out how to control the LEDs. So 
>> I'm hacking away at the default (flash) image (debian 5) to try and 
>> figure out how they've done it. It looks like they're controlling it 
>> with a closed source binary atm.
>> The Sheeva Plug install instructions work for the install.
>> Anyway, other than that it works well, and it's a cheap device :-)
>> Thanks
>> Dave
>> _______________________________________________
>> ARMedslack mailing list
>> ARMedslack at lists.armedslack.org <mailto:ARMedslack at lists.armedslack.org>
>> http://lists.armedslack.org/mailman/listinfo/armedslack
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20110701/110aeed3/attachment.html>

More information about the ARMedslack mailing list