Enhanced Howto for porting the FSG-3 to openWRT
regarding the links on openfsg.com and openwrt.org
openfsg.com->Install_OpenWRT_on_FSG_from_shell_without_serial_console
https://forum.openwrt.org/ install openwrt on fsg-3
SSH Login as root:
ssh -p 22 admin@fsgIP
admin@fsgIP's password:
mysecretadminpwd
~ $ su
root password:
/ # passwd
Changing password for root
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password:
newrootpwd
Re-enter new password:
newrootpwd
Password changed./ #
install ipkg
from: http://www.openfsg.com/index.php/Install_ipkg
regarding the links on openfsg.com and openwrt.org
openfsg.com->Install_OpenWRT_on_FSG_from_shell_without_serial_console
https://forum.openwrt.org/ install openwrt on fsg-3
SSH Login as root:
ssh -p 22 admin@fsgIP
admin@fsgIP's password:
mysecretadminpwd
~ $ su
root password:
/ # passwd
Changing password for root
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password:
newrootpwd
Re-enter new password:
newrootpwd
Password changed./ #
install ipkg
made Problems with FSGA/v1.7 Firmware v4.2.7
because ipkg comes with the firmware but buggy.
http://www.openfsg.com/index.php/Use_the_Custom_Ipkg_Installer#Installing_Packages
- download current bootstrap and copy it to FSG (if ipkg works type: wget <bootstrap-link>) http://ipkg.nslu2-linux.org/feeds/optware/fsg3v4/cross/stable/fsg3v4-bootstrap_1.2-7_armeb.xsh
- unmount old optware:
umount /opt
- remove optware:
rm -rf /home/.optware
rm -rf /usr/lib/ipkg
- reboot
- run bootstrap:
sh <path to bootstrap file>
http://www.openfsg.com/index.php/List_of_Compatible_ipkgs
stable packages for Firmware v4
http://ipkg.nslu2-linux.org/feeds/optware/fsg3v4/cross/stable/
ipkg for v4 Firmware Workaround to get ipkg working
http://www.openfsg.com/forum/viewtopic.php?p=23547
Install FIS and Fconfig
ipkg install fis
ipkg install fconig
Flash Image System (FIS) from RedBoot User's Guide
- Table of Contents
- fis init -- Initialize Flash Image System (FIS)
- fis list -- List Flash Image System directory
- fis free -- Free flash image
- fis create -- Create flash image
- fis load -- Load flash image
- fis delete -- Delete flash image
- fis lock -- Lock flash area
- fis unlock -- Unlock flash area
- fis erase -- Erase flash area
- fis write -- Write flash area
If the platform
has flash memory, RedBoot can use this for image storage. Executable images,
as well as data, can be stored in flash in a simple file store. The fis command (fis is short for Flash Image System) is used to
manipulate and maintain flash images.
fconfig - redboot config
redboot
http://www.digipedia.pl/usenet/thread/15227/666// # cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "RedBoot"
mtd1: 00180000 00020000 "kern1"
mtd2: 00180000 00020000 "kern2"
mtd3: 00020000 00020000 "RedBoot config"
mtd4: 00020000 00020000 "FIS directory"
FisList
Stock firmware layout, Flash Partitions
RedBoot> fis list
Name FLASH
addr Mem addr Length Entry point
RedBoot 0x50000000 0x50000000 0x00040000 0x00000000
kern1 0x50080000
0x00700000 0x00180000 0x00700000
kern2 0x50200000
0x00700000 0x00180000 0x00700000
RedBoot config 0x503C0000 0x503C0000
0x00020000 0x00000000
FIS directory 0x503E0000 0x503E0000 0x00020000
0x00000000
RedBoot>
/ # fconfig -r -d /dev/mtd3 -n boot_script_data
Low verbosity messages are printed.
fis load kern1
exec -c "console=ttyS0,115200 root=/dev/hda1 mem=64M@0x00000000"
HDD Partitions
hda1 200MB reiserfs
hda2 200MB reiserfs
hda3 150MB linux-swap
hda4 1GB+ reiserfs remaining space