Technical Frequently Asked Questions: Installation
FAQ » Index » Installation
How do I replace Redboot with rgloader.img?
Please refer to our IXP425 Installation Guides,
where you will find detailed instructions for replacing the rgloader.img.
Another option is using our online Evaluation Wizard where you will find guidance for any downloaded image.
How can I restore the Redboot image on my board that now runs OpenRG?
To replace OpenRG's RGLoader with Redboot, follow the instructions below:
Click on one of the following links, according to your hardware, to download the redboot image file to your PC: Coyote Redboot image Intel® IXDPG425 Redboot image Place the Redboot image to be burnt into the /tftpboot directory (or any directory you set the server with) on your PC. Execute the following command from OpenRG's CLI:
OpenRG> load -u tftp://192.168.1.10/redboot.img -r 0
Note: This operation may take a few minutes. Download is completed after the message 'Download completed successfully' appears. If you encounter an error message such as 'No route found by openrg to ip 192.168.1.10' -- disregard it. Power-cycle the board. The Redboot greeting will appear on the serial modem console screen. Execute:
Redboot> fis init -f
This may take about 2 minutes. Wait until the init operation is complete and then reset the board.
I am booting an IXP425 development platform and downloading Jungo's image via
TFTP, but the image is not loaded at startup. I have followed the
instructions but the only thing I can see is the Redboot prompt.
We would like to refer you to our
download page.
By selecting the appropriate version and platform, you will be able to download the matching evaluation image. You can also view our step-by-step instructions regarding OpenRG development platforms' Installation Guides, according to the matching OpenRG version you are using.
I downloaded the evaluation version of OpenRG (rg_sdk_install) and successfully
installed it on my RedHat 9.2 server.
When I try to compile OpenRG's version, I receive the following message:
'Detecting flex found 2.5.4 Expected version 2.5.31'
Our IPv6 feature requires an up-to-date Flex version (2.5.31 and up).
You will need to upgrade your Linux distribution with a newer flex version that
could be retrieved from sourceforge.net.
Download the source code package (flex-2.5.31.tar.gz), compile it and install
it on your PC. This should resolve the issue.
I am using a central compilation server.
A common user is not entitled to use the command 'mknod' and will never have the root password. Is there a way to generate the Jungo cramfs without 'mknod' and without using the root password?
Since the problem seems to be the running of applications that require root
permissions (without changing ANY root data), a utility called fakeroot may
be a possible solution.
Installing fakeroot on a debian system:
# apt-get install fakeroot
If your system is not a debian system - Download the following tarball:
# wget http://ftp.debian.org/debian/pool/main/f/fakeroot/fakeroot_1.5.5.tar.gz
Extract the tarball:
# tar -zxvf fakeroot_1.5.5.tar.gz
Change directory to fakeroot_1.5.5:
# cd fakeroot_1.5.5
Run configure:
# ./configure
Compile the source:
# make
Install the application:
# make install
For compiling OpenRG, do the following - Run a new bash with fakeroot permissions:
# fakeroot /bin/bash
Change directory to the root source directory:
# cd ~/rg-4.0/rg
Compile the source tree:
# make
Exit the shell with fakeroot permissions
# exit
NOTE: fakeroot WILL NOT allow users with no root permissions to change any
files that have root permissions.
I receive an error when I try to load openrg.img via HTTP.
The openrg.img is used for loading via the CLI (Command Line Interface), using
TFTP.
In order to load an OpenRG image via HTTP, use OpenRG's Web-based management to load the openrg.rmt file.
Please refer to our downloads section,
specifically to the pre-built images section, where you will find a
step-by-step procedure to guide you through burning your board with our most
up-to-date evaluation images. Also, in our
documentation section, you will find a handy Operational and Management Guide, which will
provide you general information regarding various evaluation scenarios.
Can I load OpenRG's bootloader (rgloader.img) to the RAM without burning it to
the Flash?
OpenRG's bootloader (rgloader.img) does not support loading to the RAM.
By executing a load command, the image will be burned to the Flash. However, most of the available evaluation platforms, such as Intel Coyote IXP425, support dual-image configuration. This will allow you to load an image to one section, run it, and then switch back to the other section.
I receive the following TFTP error when I try to burn the Flash with an OpenSMB
image:
OpenRG boot> TFTP Error. Bad 0ACK response
The ST ATM Card on my Board is not Working.
If your ST MicroElectronics Mt. Ararat ADSL2+ Asynchronous Transfer Mode (ATM)
card is not working after loading the OpenRG image, make sure you are using an
ATM image:
The Monte Jade ATM Image is Stuck after Soft Reboot.
When executing reboot from the CLI, if your image is stuck after the ATM card
is up, perform a hard reset. This is a known issue of ST, the Monte Jade ATM
can only be hard reset.
I was Asked for the Factory Settings File.
After burning an image, the boot process may stop to ask for the factory
settings file. The factory settings can be found under:
/rg/build/pkg/main/rg_factory
OpenRG Halts in RGLoader instead of Running Image.
In the case where after burning an image from RGLoader, you reboot, and
OpenRG halts in RGLoader instead of running the image you have just loaded,
you should restore the defaults in the RGLoader.
The reason for this is a problem in consistency of the counters of each section
on the flash.
How do I perform multiple installations of OpenRG on a single download?
In order to perform multiple installations of OpenRG on a single download, do the
following:
|