FAQ e NOTE

Here you can find some tips and the FAQ.

Warning CrisOs doesn't have a fixed ip, CrisOS tries to use the DHCP protocol for determining its network address; to change this behaviour please read Network Configuration.

REAL BIG WARNING
OpenWrt snapshot use fixed ip instead!
The fixed ip is: 192.168.1.1 !!

See modify ip/mac of your FoxBoard.

FoxBoard, like any other computer, broadcasts its mac address at boot time. This mac address is received at every computer on the same LAN; you can find the wanted information using the arp -n command in Linux, or arp -a in Windows. An example:

$ arp -n
Address           HWtype  HWaddress           Flags Mask     Iface
192.168.2.102     ether   00:08:27:01:AF:6C   C              eth0
192.168.2.1       ether   00:90:1A:A0:54:CC   C              eth0
192.168.2.145     ether   00:40:8C:CD:00:00   C              eth0

The wanted network address is associated to HWaddress 00:40:8C:CD:XX:XX.

You can easily create a DHCP network using your PC as a DHCP server.

Install dnsmasq (on ubuntu use the command: sudo apt-get install dnsmasq-base) on your Linux box and run the following script:

#/bin/sh
sudo killall -9 dnsmasq
sudo ifconfig eth0 192.168.0.1 netmask 255.255.255.0
sudo dnsmasq --dhcp-range=192.168.0.45,192.168.0.56,255.255.255.0,12h -i eth0 -d

You can also connect your FoxBoard to your (A)DSL modem or router, if it have a DHCP, and then log in to your modem or router and try to find its IP adress there. In Linksys routers it can be found in “Status/lokal network/DHCP-client table”.

Default login is root, password is pass. We suggest to change it using the passwd command. You use SSH to connect to the Fox Board. PuTTY is a good program with SSH to use to login with.

You can insert your command/script inside /etc/init.d/custom-user-startup, remember to end a background command with &. In detail you need to do following steps:

1. Goto subdirectory /etc/init.d and create script file custom-user-startup (e.g using vi)
2. Include your commands into the script, here is an example:

   #!/bin/sh /etc/rc.common
   START=90
   #
   start() {
   #your application (eg. ser2net)
   /usr/sbin/ser2net &
   }
   stop () {
   killall ser2net 
   }
   

3. Make script executable by chmod 755
4. “Register” the script file by running following command: /etc/init.d/custom-user-startup enable
5. After that in /etc/rc.d, there must be a file which references to custom-user-startup e.g.

   lrwxrwxrwx    1 root     root           29 Jan  1 00:03 S50custom-user-startup -> ../init.d/custom-user-startup
   

6. After reboot check by ps, the startup script was executed (for example the process ser2net' must be shown)

Know issues for Etrax on OpenWrt are published on official platform state: https://dev.openwrt.org/wiki/etrax

OpenWrt evolve fastest so read etrax update to keep yourself updated.

Known issues for DarwinFox release.

Due to binutils problem dbus don't compile any more. Please refer to bug trace for a possible workaround.

See bug #10 Fised in Darwinfox 8.09-5

As in Alpha

Known issues for Alpha and AlphaR2 release.

There is a know problem with ttyS0, ttyS2 and ttyS3 for Apha release. When you Personalize your firmware enabling these ports the related device aren't create at boot time.

On this Mailing List\IRC discussion Vittorio Foschi found a good workaround.\\

You can fix it using CONFIG_ETRAX_SYSFS_NODES simbols in make menuconfig. (Many thanks to bgh who discover this feature)

During ext2/3 module load you can get the following error:

ext3: Unknown symbol ext2_test_bit
ext3: Unknown symbol ext2_find_next_zero_bit
ext3: Unknown symbol ext2_set_bit

This problem, related to cris kernel linux architecture can be fixed installing this package kmod-ext2-hack.

During kernel module installation, it could display an error like this:

opkg install kmod-usb-printer 
Installing kmod-usb-printer (2.6.19.2-etrax-1) to root...
Downloading http://download.tuxfamily.org/crisos/repository/alpha/./kmod-usb-printer_2.6.19.2-etrax-1_cris.ipk
Nothing to be done
An error ocurred, return value: 1.
Collected errors:
ERROR: Cannot satisfy the following dependencies for kmod-usb-printer:
         kmod-usb-core

You can force the installation using opkg option -force-depends

opkg -force-depends install <module name>