[ARMedslack] Fwd: Re: iOmega iConnect
Dave Dowell
dowelld at netscape.net
Mon Sep 26 08:21:00 UTC 2011
Hi Greg,
I'm using the default environment arcNumber of 1682, in fact here's the
complete default environment, as it comes out of the box.
I did have problems trying to run the install on a Gbe switch, sometimes
it wouldn't tftpboot. I used a 100Mb switch to work around that and it
works without any problems on the same Gbe switch now that it's installed.
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
usbstart=usb start
run_diag=yes
console=console=ttyS0,115200
mtdparts=nand_mtd:0xc0000 at 0(uboot)ro,0x1ff00000 at 0x100000(root)
CASset=min
MALLOC_len=1
bootargs_root=root=/dev/nfs rw
bootargs_end=:::orion:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console)
root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end)
$(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
eth1addr=00:50:43:5a:1a:2d
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
iomega=123
nandEcc=1bit
ethprime=egiga0
ethact=egiga0
ipaddr=192.168.100.97
serverip=192.168.100.91
arcNumber=1682
uboot_start=0x0
uboot_size=0xc0000
env_start=0xa0000
env_size=0x20000
kernel_start=0x100000
kernel_size=0x300000
initrd_start=0x540000
initrd_size=0x300000
boot_start=0x980000
boot_size=0x1f400000
bootcmd=run flash_load
flash_load=run make_boot_args load1 load2 boot
load1=nand read.e 0x2000000 $(kernel_start) $(kernel_size)
load2=nand read.e 0x4500000 $(initrd_start) $(initrd_size)
boot=bootm 0x2000000 0x4500000
krn=run a b c
rd=run d e f
a=tftp 0x2000000 zImage
b=nand erase $(kernel_start) $(kernel_size)
c=nand write.e 0x2000000 $(kernel_start) $(kernel_size)
d=tftp 0x4500000 initrd
e=nand erase $(initrd_start) $(initrd_size)
f=nand write.e 0x4500000 $(initrd_start) $(initrd_size)
flashall=run krn rd
make_boot_args=setenv bootargs console=ttyS0,115200
mtdparts=orion_nand:;setenv bootargs
$(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs
$(bootargs)$(env_size)@$(env_start)(env),;setenv bootargs
$(bootargs)$(kernel_size)@$(kernel_start)(zImage),;setenv bootargs
$(bootargs)$(initrd_size)@$(initrd_start)(initrd),;setenv bootargs
$(bootargs)$(boot_size)@$(boot_start)(boot)
ethaddr=00:D0:B8:0D:B5:DD
make_bootsetenv=make_boot_args setenv bootargs console=ttyS0,115200
mtdparts=orion_nand:;setenv bootargs
$(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs
$(bootargs)$(env_size)@$(env_start)(env),;setenv bootargs
$(bootargs)$(kernel_size)@$(kernel_start)(zImage),;setenv bootargs
$(bootargs)$(initrd_size)@$(initrd_start)(initrd),;setenv bootargs
bootargs=setenv bootargs console=ttyS0,115200
boot_starsetenv=boot_start 0x980000
boot_sizesetenv=boot_size 0x1f400000
MAPOWERENV=Ver. 1.1.27 English
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
hddPowerCtrl=no
enaAutoRecovery=yes
pcieTune=no
Thanks
Dave
On 26/09/2011 08:04, Davide wrote:
> 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.
>
> Regards David
> ------------------------------------------------------------------------
> *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
>
> Dave,
>
> 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
>
> -Greg Lim
>
>
>
>
> On Wed, Jul 20, 2011 at 11:42 AM, Dave Dowell <dowelld at netscape.net
> <mailto:dowelld at netscape.net>> wrote:
>
> Hello again,
>
> OK I've started putting some information about this up now.
>
> http://www.dowelld.net/viewtopic.php?f=1&t=3
> <http://www.dowelld.net/viewtopic.php?f=1&t=3>
>
> Thanks
> Dave
>
> -------- Original Message --------
> Subject: Re: [ARMedslack] iOmega iConnect
> Date: Fri, 01 Jul 2011 21:49:04 +0100
> From: Dave Dowell <dowelld at netscape.net>
> <mailto:dowelld at netscape.net>
> To: armedslack at lists.armedslack.org
> <mailto: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.
>
> Thanks
> Dave
>
> 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 <mailto:ARMedslack at lists.armedslack.org>
>> http://lists.armedslack.org/mailman/listinfo/armedslack
>
>
> _______________________________________________
> 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 <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/20110926/201c5212/attachment-0001.html>
More information about the ARMedslack
mailing list