[ARMedslack] Fwd: Re: iOmega iConnect
louigi600 at yahoo.it
Mon Sep 26 07:04:26 UTC 2011
I know I'm not the right Dave :-D
I thought that google would have the answer for this bit apparently there's no correct answer:
I got this as an intresting hit form Jeff Doozan's forum
There is no common arcNumber:
- iomega uses 1682
- OpenWRT uses 2870
- Debian <asm/mach-types.h> does not list any reference to the iconnect. So it is "really" unsupported.
None of the kirkwood arcNumbers listed in Debian results in a functional network.
In OpenWRT is a patch that made the GBit network working (arcNumber=2870).
But the OpenWRT kernel is not able to read or write the flash correctly.
My guess is that it depends on the kernel you are using.
Da: Greg Lim <sunsmoke at gmail.com>
A: Slackware ARM port <armedslack at lists.armedslack.org>
Inviato: Domenica 25 Settembre 2011 22:27
Oggetto: Re: [ARMedslack] Fwd: Re: iOmega iConnect
I finally got around to unboxing my iConnect. I can boot into the ArmedSlack installer, but I have no ethernet. I'm guessing that I have the wrong arcNumber.
Can you tell us what the correct arcNumber is for the iConnect running on the ArmedSlack 13.37 kernel so that ethernet works?
Here's what I've tried:
2870 - doesn't boot. added by someone Matrin Michlmayr on May 2010.
1682 - boots. no ethernet once booted into the install system, but ifconfig appears to show the correct ethernet addresses of both the wireless and 1GB-wired interfaces.
2097 - sheevaplug - interface missing. can't bring up
2678 - sheevaplug - esata - interface missing. can't bring up
On Wed, Jul 20, 2011 at 11:42 AM, Dave Dowell <dowelld at netscape.net> wrote:
>OK I've started putting some information about this up now.
>-------- Original Message --------
>Subject: Re: [ARMedslack] iOmega iConnect
>Date: Fri, 01 Jul 2011 21:49:04 +0100
>From: Dave Dowell <dowelld at netscape.net>
>To: armedslack at lists.armedslack.org
>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.
>>Sent from my VT102
>>On Jul 1, 2011, at 5:18 AM, Dave Dowell <dowelld at netscape.net> wrote:
>>>I've installed ARMedslack onto one of these now.
>>> * 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 ?)
>>>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
>>>ARMedslack mailing list
>>>ARMedslack at lists.armedslack.org
ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
>ARMedslack mailing list
>ARMedslack at lists.armedslack.org
ARMedslack mailing list
ARMedslack at lists.armedslack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARMedslack