This iconnect setup script can also install Arch Linux on your USB storage device; if you omit this step, you can perform the installation by running the script again later (possibly with --no-uboot option) or install Arch (or even debian) on your USB device manually.
The installation log will be saved into /var/log/iconnect-install.log.
1. Enable ssh on your Iomega iConnect
If you have not done so, you will need to enable ssh on the stock iConnect, which can be done from Iomega's "hidden" Web UI screen. Open https://<iconnect's_IP_or_hostname>/support.html in your browser and you'll see a page like this one: http://imageshack.us/f/35/iconnect1.png/. Click on "Support Access", check "Allow remote access for support" and click "Apply": http://imageshack.us/f/18/iconnect2.png/
2. ssh into the box.
You should now be able to ssh to your iConnect using the same IP/hostname you use to access Iomega's web interface. The username is "root" and password is "soho" followed by the admin password you use in Iomega's web interface. That is, if your iConnect web interface admin password is Foo, ssh to iConnect as user "root" with password "sohoFoo".
Windows user can use putty or their favorite ssh client. Linux and OS X users presumably already know what to do.
3. Download and run the setup script
- Code: Select all
wget --no-check-certificate https://raw.github.com/igors/iconnect_usb_boot/master/iconnect_install.sh
chmod +x iconnect_install.sh
If installing Arch to a hard drive (as opposed to a USB flash drive), replace the last line above with
- Code: Select all
Follow the prompts - the script is fairly verbose and will ask you a bunch of questions.
4. What you'll get if you install Arch
Wireless works fine
Arch's stock fw_printenv/fw_setenv work fine.
LEDs don't work - you'll end up with the permanently blinking power LED. I'm working on it.
The default root password is "root" - change it! And don't forget to updrade to the latest packages (pacman -Syu).
If you're new to Arch Linux, take a look at http://archlinuxarm.org/support/guides/ ... irst-steps
5. Some gory details
The script will perform the following steps.
- a. Update your iConnect's uboot environment variables to make it boot from the attached USB device (unless run with --no-uboot option). The environment is set up to attempt booting from all attached USB devices until the boot attempt is successful. It will first try to load /boot/uImage from /dev/sdX1 (Arm Arch's standard one-partition setup) and then /uImage from /dev/sdX2 (which seems to be the standard debian setup, e.g., if you followed the guide at http://www.kroonen.eu/wiki/Install%20Debian). The end result is that your iConnect should be able to boot either Arch or debian from USB devices. If the attempts to boot from the attached USB devices are not successful, you will boot from NAND into Iomega's stock kernel.
- b. Optionally format the attached USB device as ext2 (or ext3 if run with --ext3) and download and install Arch linux on it (you will be prompted for both unless run with --no-arch option). If you choose to install Arch, this script will also create /etc/fw_env.conf (the stock fw_setenv/printenv will work in Arch!).
6. Further reading
- Troubleshooting installation problems
- Updating arcNumber. You need to do this to make full use of iConnect features, i.e., LEDs, OTB/reset buttons, temperature sensor.
- Post-install customizations - how to control LEDs, OTB/reset buttons and temperature sensor.
- Recovering bricked iConnect. You'll also have to follow this guide if you need to boot Iomega stock kernel after changing the arcNumber to 2870.