From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: [SIG-ARM] iomega iconnect wireless
Date: Thu, 29 Mar 2012 13:17:11 +0000 [thread overview]
Message-ID: <36a93a6a59ecb4ad022704b623882c29@mail01.ipfire.org> (raw)
In-Reply-To: <CAMyVLOnA-xE3gC60nR6CakUHO+jtDrYGPPbNdtbr8pT24oxUCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
The official Release (based on kernel 2.6.32.45) has no support for the
Iomega iConnect. This will added with the next kernel update. You have
to use a testrelease with newer kernel.
http://people.ipfire.org/~arne_f/testing/armv5tel/kernel-update/
and you have to change the u-boot environment as described here:
http://wiki.ipfire.org/en/hardware/arm/kirkwood#iomega_iconnect_wireless_data_station
Arne
On Wed, 28 Mar 2012 18:46:20 +0200, LanPlanet LanPlanet
<lanplanet2011(a)gmail.com> wrote:
> Hi All,
>
> I have enabled ssh access to my iomega iconnect
> I have unpack the last ipfire image on usb drive wit zcat command ..
>
> http://downloads.ipfire.org/releases/ipfire-2.x/2.11-core57/ipfire-2.11.2gb-ext2-scon.armv5tel-full-core57.img.gz
> [1]
>
> Could someone help me to find the way to boot from the usb?
> At the moment I dont have a console cable so is it possible to go on
> with
> ssh connection?
>
> following this tutorial :
> http://archlinuxarm.org/forum/viewtopic.php?t=1472 [2]
> I should be able to boot a usb drive from my iomega
>
> Links:
> ------
> [1]
> http://downloads.ipfire.org/releases/ipfire-2.x/2.11-core57/ipfire-2.11.2gb-ext2-scon.armv5tel-full-core57.img.gz
> [2] http://archlinuxarm.org/forum/viewtopic.php?t=1472
parent reply other threads:[~2012-03-29 13:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMyVLOnA-xE3gC60nR6CakUHO+jtDrYGPPbNdtbr8pT24oxUCw@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36a93a6a59ecb4ad022704b623882c29@mail01.ipfire.org \
--to=arne.fitzenreiter@ipfire.org \
--cc=sig-arm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox