Make sure you have the newest Flash Rom Available for your Cobalt. There are tons of tutorials about this online so I will not get into great
detail on this. At the time of this writing, the newest available Rom for Cobalt Raq3* and Raq4* is cobalt-2.10.3-ext3-1M.rom. You want the ext3
version and the 1M flat file for any Cobalt Raq3* or Raq4* you intend to put RaqCop on. Since Raqcop like IPCop 2.x.x uses explicit mac address listings in the ethernet config as well as udev rules, using a serial console for final setup is mandatory for Raqcop 2.x.x. You MUST set up networking upon first boot via serial console in ALL Raqcop 2.x.x installations. There is no way around this for first boot.
a)20GB Oem Disk(s) Instructions:
Take out the OEM 20GB hard drive from the cobalt. Put it into a USB to hard drive converter.
Download WinImage and install it. Download our WinImage VM Image of RaqCop and untargzip it. Open WinImage and go to "Disk" then "Restore Virtual Hard Disk Image on
physical drive". Choose the USB HDD that you want RaqCop on. Be very careful you do NOT choose your Windows OS partition or any other important HDD.
Go grab a Snickers as the transfer process can take a while (20mins). This process currently is limited to 20GB RaqCop installs. This image will only use
up 18.6GB (actual usable portion of the 20GB drive) of any drive. Once the WinImage is complete, put the HDD back into the Cobalt as it was. For 20GB Raid installs, download the Raid version of the same and do the same thing as above with hda and hdc images, then put both drives into the machine. With Linux, download the full image version, untargzip it, use the dd if=something.img of=/dev/sdx where x is the actual device node. CAUTION! The full images need 20GB of free space for single, 40GB for RAID! Go to step 3 below.
b)Flash Image Instructions:
Choose the image(s) closest to but <= the size of your flash drive and whether you want raid or not, download and unstargzip it. If standard put a flash disk into a USB connected reader and either use something like Winimage in Windows or the DD command in Linux. This would be dd if=something.img of=dev/sdx where x is the letter of the actual device. If Raid, you will have two images in the tarball. Repeat the above but twice, once for hda and once for hdc. You will need a decent IDE to Flash bridge unless your chosen flash medium has an IDE connector on it such as with a DOM. One option is a Micro SD with an SD caddy or an SD in an Addonics SD/MMC to IDE adapter. This has been demonstrated to work. The Syba SD/MMC adapter has been shown to not work on a Cobalt. Go to Step 3 below.
c)Virtual Machine Instructions:
Dowload the latest iso image, set the VM to boot from that iso. It is very helpful if you can connect USB devices to the VM for two reasons, the install will allow installation directly to the USB connected storage and secondly, if doing a fresh install in the future, the VM can read your backup on a USB stick making a pre-configured fresh install take about five minutes. Once you have installed to the medium(s) of your choosing, install it/them in the Cobalt machine. Note that Raid requires two disks at install. It is soft Raid 1 as is that of the Cobalt rom. Now on to step 3 below.
Setup Instructions: You did follow step 1 before going on right? Good. :)
a)Single Disk Instructions:
The Cobalt's are defaulted to look for /boot on hda1 with Rom settings on the 3000 series (Raq3/4 and Qube3) after a reset or rom flash, on the 550 default is md0. If needed, turn on while holding down the "S"
button. When the menu appears, you can let go of the "S". Click the "S" untill you see boot settings. Look for boot drive in the menu and hit "E".
Select hda1 as the boot drive (On the front panel this actually sets the root drive only, boot must be set in serial rom menu mode). This is very very important or you will get the good ol "Kernel panic" when booting RaqCop. This is also a 1 time
setting unless you clear the CMOS. For a 550 you will have to use the serial console menu to set /boot as hda1. More serial console instructions under Raid below.
If using Raid on a 3000 series or single disk on a 550, you will need to use a nullmodem cable to use the serial console in the rom menu. In Windows, PuTTY which is free, works the best for serial console connection lest you thought it was for SSH only. You have to be quick to get to the rom menu in the console. Have your fingers ready to hit the spacebar when you see the prompt to hit the spacebar to enter the menu. You have one second to catch it. If you miss, hit the power switch before it boots any further and try again. Once in, type boot and hit enter. Type ? and hit enter to see the available commands. For Raid you would type set_boot_disk md0 and set_root_disk md0. For single disks such as in the 550, both would be set to hda1. Now type reboot and then press enter.
Post Boot Network Setup Instructions:
On first boot you WILL see a lot of errors in the serial console, ignore them, they are caused by lack of a network configuration. When you see the login prompt on the serial console type root and hit enter, if using preconfigured images from this site the password is raqcop. Once logged in as root, run depmod and then setup after the depmod. Set up your network as you would with any IPCop install per IPCop instructions in their manual. This is a good time for you to set up your own passwords and hostname if you used pre-configured images from this site. Once out of setup, you may be able to log in via the web gui but I recommend a reboot once after everything is set up.
b)Post Network Setup:
Once installed and running after setup and reboot, you should see a bandwidth meter on the front panel. RaqCop IpCop install defaults to https://your-chosen-raqcop-ip:8443. Beyond this point, IPCop administering applies. The ( I ) in red throughout the web gui is a link to IPCop's online manual.
c) Terminal Settings:
The required settings depending on what method you use to have a serial terminal is:
115200 Baud, 8 Bits, 1 Stop Bit, and Terminal Type is VT100. HyperTerminal in Windows is not recommended. It can work but it just isn't as solid and easy to read or scrollback etc as the free program PuTTY is.