Openmoko - User contributions [en]

USB Networking

2008-11-19T09:05:17Z

Miohtama: fixed formatting

= Openmoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to e.g. 192.168.1.(something) might save you a lot of troubleshooting later. A discussion of this is [http://lists.openmoko.org/pipermail/support/2008-August/thread.html#1277 here].

= Simple Manual Linux Configuration =

Try this first (as root on your desktop, with FreeRunner attached via USB cable and booted properly, not at the Boot Menu). If it works, then you can add permanent configuration or use more sophisticated setups below.

<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ip addr add 192.168.0.200/24 dev usb0</pre>

If your Internet connection is also in the range 192.168.0.x then instead you might want to use only:

<pre>ip addr add 192.168.0.200/28 dev usb0</pre>

(This will just map the net from 192.168.0.192 to 192.168.0.207 onto usb0. If you get the error 'Cannot find device "usb0"', double-check that your FreeRunner is turned on and connected by USB. If that doesn't work, try unplugging and replugging the USB cable.)

And in this case you should enable ARP proxy on internet facing interface INSTEAD of using iptables:

<pre>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>ifconfig usb0 up</pre>

Then (ideally, not as root):

<pre>ssh root@192.168.0.202</pre>

The default password is blank.

Due to the fact that in most cases your Neo will use the same dns servers as your computer uses, you can automate the process of writing dns servers to your phone:

<pre>#!/bin/sh
/sbin/route add -host 192.168.0.202/32 dev usb0
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
iptables -P FORWARD ACCEPT
sysctl -w net.ipv4.ip_forward=1
su `whoami` -c "scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf"</pre>

Again if your net already is 192.168.0.0, replace the POSTROUTING statement with
<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/28</pre>

This simple script will set up routing for your Freerunner and than copy resolv.conf with dns addresses straight to the phone.
All you have to do is connect phone to the computer, run the script and enjoy internet connection from your phone.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the

''Device Drivers -> USB support -> USB Network Adapters''

or

''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''.

For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

Masquerading options (tested on Linux 2.6.26.3) are found in:

''Networking --->
Networking options --->''

To see the other options, enable

* CONFIG_NETFILTER (''Network packet filtering framework (Netfilter)'')

Then, from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
Core Netfilter Configuration --->''

You need at least following options enabled as modules:

* CONFIG_NF_CONNTRACK (''Netfilter connection tracking support'')
* CONFIG_NF_CONNTRACK_FTP (''FTP protocol support'')
* CONFIG_NETFILTER_XTABLES (''Netfilter Xtables support'')

Rest of the needed options are found from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
IP: Netfilter Configuration --->''

You need to enable (again, as modules is fine):

* CONFIG_NF_CONNTRACK_IPV4 (''IPv4 connection tracking support (required for NAT)'')
* CONFIG_IP_NF_IPTABLES (''IP tables support (required for filtering/masq/NAT)'')
* CONFIG_NF_NAT (''Full NAT'')
* CONFIG_IP_NF_TARGET_MASQUERADE (''MASQUERADE target support'')

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner.

You should add the IP address of the DNS servers as provided by your ISP. Check your router's or PC's network status for the nameserver IP addresses.

<pre>echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf</pre>

You can also add the public DNS server called openDNS:
<pre>echo nameserver 208.67.222.222 > /etc/resolv.conf
echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

These settings will be lost on reboot. You can set the DNS for the next connect, by adding the following to the end of the usb0 setting in /etc/network/interfaces, right above the bluetooth networking section:
<pre>up echo nameserver 208.67.222.222 > /etc/resolv.conf
up echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"

<pre>udpf-elf -p=53-f=`awk '$1 == "nameserver"{print $2; exit(0);}' /etc/resolv.conf`:53</pre>

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

<pre>iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1</pre>

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
<pre>ping www.google.com</pre>

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= OS or Distro Specific & Automatic Configuration =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.
These instructions should keep you from having to run the Simple Manual Linux Configuration every time you plug in and want to connect to an Openmoko device. One run and then you're done!

If the Simple Manual Linux Configuration does not work for your OS or Distro (MacOS X, MS Windows, etc) there may be instructions here that work for you.

== MacOS X ==
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].

== Windows ==
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].

== FreeBSD ==
You need to load the cdce kernel module (if it is not already linked into your kernel). As root do:

# kldload cdce

The Neo should then show up as cdce0 interface and you can handle the cdce0 interface just like the usb0 device under Linux. For more information see the cdce manpage. An easy way to assign the IP address to the cdce0 interface is using the devd(8) daemon. Create the following two files,

/usr/local/etc/devd/cdce.conf as:

notify 1 {
match "system" "IFNET";
match "subsystem" "cdce0";
match "type" "ATTACH";
action "/usr/local/etc/devd/cdce.sh $subsystem $type";
};

and /usr/local/etc/devd/cdce.sh as:

#!/bin/sh
case $2 in
'ATTACH')
ifconfig cdce0 192.168.0.200 netmask 255.255.255.0
exit 0 ;
;;
esac
exit 0

Then restart the devd(8) daemon with:

# /etc/rc.d/devd restart

If you now plugin the FreeRunner into the USB port the cdce0 interface gets created and the IP addr will be assigned.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &

</pre>

This is more sophisticated than the manual setup. The 'auto usb' stanza ties into the Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

Another possible configuration that adds DNS forward and removes
the iptables changes after unplugging:

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(awk '$1 == "nameserver"{print $2; exit(0);}' /etc/resolv.conf)

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

It is possible to use network-manager to automatically connect to the Freerunner using udev. The process uses udev to run a script when the Frerunner is plugged in. The script uses the ip command to set the mac address of the usb network interface. To begin, create /etc/udev/rules.d/80-freerunner.rules :

<pre>
# This file causes programs to be run on device insertion.
# See udev(7) for syntax.

# rule to assign a fixed mac address specified in /
KERNEL=="usb[0-9]*", DRIVERS=="cdc_ether", ACTION=="add", RUN+="/usr/local/sbin/freerunner-usb-add.sh %k"
</pre>

Next, create the /usr/local/sbin/freerunner-usb-add.sh :

<pre>
#!/bin/sh

(
busNum=$( printf %.2d $( expr match "$1" "usb$[0-9]*$") )

ip link set "$1" address 00:00:22:55:bb:$busNum &> /dev/null

) &

exit 0
</pre>

Finally run "chmod +x /usr/local/sbin/freerunner-usb-add.sh" to make it executable. Now you can use network-manager with mac-address specific settings and get it to automatically connect.

=== Ubuntu Issues ===

Ubuntu 8.10 doesn't work as expected if you used /etc/network/interfaces to automate the connection. Network manager likes to latch onto the network device and add a default route through 192.168.0.202, breaking your network connection. Network manager also says you can't edit or remove this connection from its list. I'm going back to making the connection manually.

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules. Moving the DRIVERS=="*?" out of the top GOTO, to ACTION=="add" line fixes the problem.

<pre>
SUBSYSTEM=="net", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", DRIVERS=="?*", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

LABEL="net_end"
</pre>

The bug is that the DRIVERS variable isn't set at all when the device is unplugged.

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)
:Actually it appears that it's not fixed, but patching that file and disconnecting and reconnecting the phone works perfectly. --[[User:Johndoesacc|Johndoesacc]] 18:37, 20 August 2008 (UTC)

== Mandriva ==

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

<tt>/etc/sysconfig/network-scripts/ifcfg-usb0</tt>:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

<tt>/etc/sysconfig/network-scripts/usb0-routes</tt>:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.0

Now we need to restart the network system to pick up the changes.

service network restart

This didn't work for me (Mandriva 2008.1), giving errors from Shorewall. However, simply using MCC, Network->Sharing Internet Access worked fine. You need to connect Neo when starting it. --[[User:Alih|Alih]] 18:50, 22 September 2008 (UTC)

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart
=== Option C - tested on F9 ===
(seemed to work on FC8 also)

Plug in the usb cable. NetworkManager should detect the phone automatically but you should ignore it.
Open Network Configuration tool (System -> Administration -> Network) and perform following steps:
# Click '''New''' button on top bar
# Click '''Forward'''
# Select OpenMoko from device list
# Click '''Forward'''
# Select 'Statically set IP address:' and enter address: 192.168.0.200, netmask 255.255.255.0 (or use 255.255.255.240 if you want only route ip range 192.168.0.192-192.168.0.207). Leave gateway empty.
# Click '''Forward'''
# Click '''Apply''' to close add dialog
# Select newly added usb0 device from the device list.
# Click '''Edit''' button on top bar
# You might want to remove a tick from 'Activate device when computer starts' check box.
# Click '''Ok''' to close window dialog.
Save settings and close the window.

Open Firewall Configuration (System -> Administration -> Firewall) and enable masquerading:
# Select '''Masquerading''' from left panel
# Check device(s) which you'd like to share internet connection. Typically eth0 or wlan0.
# Click '''Apply''' and close application

Open terminal and perform (as root user):
# ifdown usb0
# ifup usb0
The first command will remove any existing settings given by the NetworkManager and second command brings the device up with appropriate settings.

Now you should be able to ping e.g. 74.125.39.99 [www.google.com] from OpenMoko. Configure /etc/resolv.conf and you should have full a internet access.

==== Troubleshooting ====
If Network Configuration tool cannot see the the usb0 try to unplug the usb cable for a few seconds and wait until the NetworkManager finds it again.

NetworkManager will assign a new ip address for the OpenMoko if link goes down for a while. You can fix this by issuing '''ifup usb0''' again.

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

=== Manual Configuration ===

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

=== Automatic Configuration ===
One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== Slackware (tested with 12.1) ==

Following is based on [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].

Create a new udev rules file <tt>/etc/udev/rules.d/91-openmoko.rules</tt>:

<pre>
SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="1457", ATTRS{idProduct}=="5122", RUN+="/sbin/om-usb $env{INTERFACE} start"
SUBSYSTEM=="net", ACTION=="remove", ENV{INTERFACE}=="usb[0-9]", RUN+="/sbin/om-usb $env{INTERFACE} stop"
</pre>

Then create the script <tt>/sbin/om-usb</tt>:

<pre>
#!/bin/sh
INTERFACE=$1
ACTION=$2

# udev fails silently when the script fails, e.g. due to commands not
# being found
PATH=/usr/sbin:/sbin:/usr/bin:/bin

case $ACTION in
'start')
# Put all your setup here
;;
'stop')
# Put all your tear down here
;;
*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac
</pre>

The <tt>INTERFACE</tt> will be <tt>usb0</tt> in most cases.

== Archlinux ==
Following is based on [http://xenos.altervista.org/blogs/index.php?blog=3&title=openmoko-usb-networking-su-archlinux furester's solution].

Install package [http://aur.archlinux.org/packages.php?ID=20220 openmoko-usb-networking] from AUR:

$ yaourt -S openmoko-usb-networking

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh adding a new line for every ssh host-key to your known_hosts you can add the following to the phone section in ~/.ssh/config (or see the snippet at : [[USB Networking#Changing_host_keys]] bellow)

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

user@host$ ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

root@phone# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

user@host$ scp ~/.ssh/id_rsa.pub root@phone:~/.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt using a command like 'ssh root@phone' from the account user@host because the public key in the file user@host:~/.ssh/id_rsa.pub is contained in the list of keys which have access in the file root@phone:~/.ssh/authorized_keys (since scp is used, only one key exists, but you can grant access to the phone from more than one account, for example user@host, user@laptop).

To make ssh login as root by default, add the following lines to ~/.ssh/config:

Host phone
User root

Replace ''phone'' with the hostname or ip of your phone. You should now be able to ssh into the phone without having to type ''root@'' every time.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts). Now you have set this, you can issue the following command to connect to your moko :

ssh root@moko

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the FreeRunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the FreeRunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process'' #(isn't the "env" redundant here?)

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200

==Automated setup network and mounting partitions==

See [https://bugs.launchpad.net/ubuntu/+bug/289548 Ubuntu bug report in launchpad].

<span id="bottom"></span>
{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Implemented]]
[[Category:Networking]]

FDOM - a Fat and Dirty OM based distribution

2008-11-06T15:51:35Z

Miohtama: /* Download */

{{Languages|FDOM_-_a_Fat_and_Dirty_OM_based_distribution}}
{{Distributions|FDOM}}

=== Description ===
A combination of apps(a lot of) and fixes to demonstrate the capabilities of the Freerunner and to have a functional phone (sort of). This all while retaining the ability to update through the official feeds.

Until now, flashing the phone was the only way to update to the last release of FDOM but since 20081023 version there is a script called FDOMizer able to update to the lastest version of FDOM any older version of FDOM and is able to transform a brand new flashed OM2008.X on the phone to a full bloated FDOM

Any questions can be sent to david at tuxbrain dot com

or at community list or local-openmoko-spain list

See [[Development_resources#Mailing_Lists|mailing lists]]

David-Reyes Samblas Martinez

Co Admins

Armin ranjbar aka [http://zoup.org Zoup]

Nacho Seijo aka himero

=== Download ===
Download from http://www.tuxbrain.com/fdom_en.html.
* Notes:
**If you have updated your kernel, re-flash back to the default [http://downloads.openmoko.org/releases/Om2008.9/Om2008.9.uImage.bin| Om2008.9 kernel] so that your kernels and modules are the same version. Otherwise none of the device drivers load and you have no usb0 or other essential stuff.
* Mirrors:
** old home server
***http://compartida.net/openmoko/FDOM
** TDobson:
*** http://files.tdobson.net/openmoko/freerunner/fdom/
**** Mirror admin contact: www.tdobson.net/contact
** TrueBox:
*** http://openmoko.truebox.co.uk/mirror/compartida.net/
** Universidade de Vigo:
*** http://ftp.uvigo.es/mirror/openmoko/
*** http://ftp.uvigo.es/pub/linux/distribuciones/openmoko

=== Development ===
If you want to come to the script kidding party :) join us at

http://projects.openmoko.org/projects/fdom/

Serious developers are welcome too :) but remember "if it's cool, it works(in some way),doesn't annoying(too much) rest of things and fits on the nand it's in" :) we will let scalability, stability, resource saving and so on to the OM guys :)

The devel list is:
http://lists.projects.openmoko.org/mailman/listinfo/fdom-development

Thanks to armin, we have also a svn server svn://zoup.org/Fdom with the FDOMizer script and auxiliary files ,waiting for you to make it better ;)

=== Warnings ===
Please any warning tip a trick post it in the devel list :)
http://lists.projects.openmoko.org/mailman/listinfo/fdom-development

=== Changelog ===
You can use both the script it self and the svn log to visualice those changes

=== Roadmap ===
* Try to make it more like lastest Raster Image like
* Fix all bugs arised and make it more stable
* Make it even more community driven

=== External Links ===
Some people talking about us ;) thanks a lot

http://openmoko-fr.org/blog/index.php?post/2008/09/16/Test-de-FDOM (FR)

http://www.bunix.de/key/personal-blog/blog_id/533.htm (DE)

http://community.livejournal.com/ru_openmoko/6577.html (RU)

http://www.linuxphone.ru/2008/09/fdom-distributive-for-openmoko-freerunner/ (RU)

[[Category:Distributions]]

Om2008.8

2008-08-06T00:42:18Z

Miohtama: Added download link

__NOTOC__
__NOEDITSECTION__
{{Languages|Openmoko2008.8}}
{{Om 2008.8}}

{{Distributions|Openmoko2008.8}}

'''Openmoko2008.8''' or '''Om2008.8''' is the successor to [[Openmoko2007.2]] and had '''ASU''' as a codename. It launched on August 08, 2008. Om2008.8 uses EFL for the launcher, custom UI applications and [[QtopiaOnX11|Qtopia on X11]] for telephony.
It is the first step from [[GTK+]] on x11 to using multiple toolkits in combination. Om2008.8 now supports [http://www.enlightenment.org/ EFL], [http://trolltech.com/products/qtopia Qtopia] and [[GTK+]] applications.

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om2008 uboot.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om2008 home.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Installer4.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om2008 installer1.png|200px|center]]
|-

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Main.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Edit1.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om locations4.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:List.png|200px|center]]
|}

== What's New ==
Om2008.8 was designed to be as empty as possible, for the very purpose of showcasing your ideas.

Think of our products as museums. We're building the environment. Each one different from the next. You'll get all the free art supplies you could imagine because we want you to add your own meaning. You choose: consume, create, or both.

Either way you create your own meaning. It's about you.

=== Customize ===
Om2008.8 allows you to customize your Neo in many aspects.

* '''Use the Installer''' to find apps and modifications for your Neo.
* '''Re-design themes''' by customizing your own [[Edje]] files.
* '''Source Codes''' are publicly available, allowing for customization all the way down to low level sytems.

=== Share ===
* share your locations ([[Om2008.8_Locations|Locations]])
:you can use splinter to save your location and even send it to friends via sms. how cool is that?!
* share your applications ([[Om2008.8_Installer|Installer]])
:share your ideas with the world by adding packages to the [http://downloads.openmoko.org/community-repository/ Openmoko Repository]. It is a great database for all things openmoko and can easily be accessed by any user through the [[Om2008.8 Installer|Installer]].

== Feature Plan ==

You can see a list of available and planned features at [[Openmoko2008.8 Feature Plan]].

== Download ==

[http://buildhost.openmoko.org/daily/freerunner/200808/ Download images]

== Installing ==
For instructions on how to flash your device, please refer to [[Flashing the Neo FreeRunner]].

[[Category:Openmoko]]
[[Category:Distributions]]
[[Category:Openmoko2008.8]]

Users Repositories

2008-08-06T00:10:50Z

Miohtama: Highlighted the importance of Amstrong

Here you can find prebuilt kernels and root file systems.

=Official downloads=

==Recent/latest builds==
* Framework Testing Images (FSO)
:http://downloads.openmoko.org/framework/
* OM2007.2
:http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D
* OM2007.1 (Obsolete)
:http://buildhost.openmoko.org/OM2007.1/tmp/deploy/images/?C=M;O=D

==Snapshots [http://downloads.openmoko.org/snapshots/]==
* 2007.11 - the latest (2nd Dec) snapshot ([http://lists.openmoko.org/pipermail/community/2007-December/011980.html from Mickey])
:http://downloads.openmoko.org/snapshots/2007.11/images/
* 2007.08 snapshot, as announced by Sean on August 19
:http://downloads.openmoko.org/snapshots/2007.08/images/

==Daily==
* Unstable Daily-builds
:http://buildhost.openmoko.org/daily/

==[[CommunityRepository|Community repository]]==
:http://downloads.openmoko.org/community-repository/

=Unofficial builds=

== Angstrom Repository ==

Angstrong is the base distribution of OpenMoko Linux distribution. It contains the basic set of Linux applications and they should be compatible with OpenMoko. [http://www.angstrom-distribution.org/repo/ The repository package listing].

To add the unstable Angstrom feed, update your ''/etc/ipkg/base-feeds.conf'' to include a line:

<pre>
src/gz base http://www.angstrom-distribution.org/feeds/2007/ipk/glibc/armv4t/base/
</pre>

==[[User:ChooseOpen|ChooseOpen]]==
:http://chooseopen.com/openmoko/build/2007.2/?M=D (2007.2)
:http://chooseopen.com/openmoko/build/qtopia/?M=D (Qtopia)

==[[User:Kevin_Dean|Kevin_Dean]]==
:http://downloads.openmoko.org/recommended/ (only gta01)
:Latest recommended [[Snapshot review|snapshot review]]

==[[User:ScaredyCat|ScaredyCat]]==
:http://buildhost.automated.it/OM2007.2/?M=D

ScaredyCat also has a ipkg repository for 2007.2 where e.g. gpe-filemanager and a lot more (e.g. ntpd) can be installed from. On the Neo do:

cd /etc/opkg
wget http://buildhost.automated.it/scaredycat.conf
opkg update
opkg install gpe-filemanager
opkg install gpe-timesheet
opkg install gpe-todo
opkg install mysql
opkg install mtpaint
opkg install sqlite
opkg install ntp
#(you get the idea)
/etc/init.d/xserver-nodm restart # to make the new applications appear in the menu

=='''mwester''' unofficial builds==
:http://moko.mwester.net/

==celtune==
:http://rabenfrost.net/celtune/?C=M;O=D
:http://rabenfrost.net/celtune/ipk/

Celtune offers Standard-Builds (.jffs2, .tar.gz, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
For more info take a look at http://rabenfrost.net/celtune/1-NEWS-WARNING-INFO
You can find images, kernels and packages for other devices too on http://rabenfrost.net/celtune/ (e.g. HTC-Blueangel, Asus730W ...)
A huge number of packages is located at http://rabenfrost.net/celtune/ipk/
Use the following line to add celtune's feed to your neo:
cd /etc/opkg && wget http://rabenfrost.net/celtune/celtune-rabenfrost.conf

If you want to add a link, it would be nice to enforce a standard format of these feeds so that they can be browsed automatically.

[[Category:Openmoko]]

USB Networking

2008-08-05T23:16:26Z

Miohtama: /* Linux Kernel Support */

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Recent Linux distributions (Ubuntu 8.04 Hardy Heron) support USB Networking out of the box.

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

nameserver 192.168.0.200

Which means that by default it expects your desktop to have a DNS server. On some Linux and Windows systems this is true, especially those configured as servers, but in general it is not. You can install packages such as ''bind9'' or ''dnsmasq''. See the section below on [[USB Networking#More on DNS|More on DNS]] for other solutions.

Test if it works:

ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Testing Your Connection =

Log in with a blank password (press enter). Now, make sure you can ping back to your desktop:

ping 192.168.0.200

This tests the basic network connection.

(Note that some systems like Vista, don't respond to ICMP ping by default)

Or your router, for example (your IP will probably be different):

ping 192.168.1.99

Or to a Google IP:

ping 74.125.19.147

This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

= Make it Permanent =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

The bug is that the LABEL="net_end" is at the wrong position

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= More on DNS =

== Hostnames ==

Instead of using the IP address, instead enter in your desktop's /etc/hosts:

192.168.0.202 openmoko

Then instead type:

ssh root@openmoko

== DNS proxying ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you). There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"

udpf-elf -p=53-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200

<span id="bottom"></span>
{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-05T23:13:54Z

Miohtama: Merged DNS sections to one

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Recent Linux distributions (Ubuntu 8.04 Hardy Heron) support USB Networking out of the box.

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

nameserver 192.168.0.200

Which means that by default it expects your desktop to have a DNS server. On some Linux and Windows systems this is true, especially those configured as servers, but in general it is not. You can install packages such as ''bind9'' or ''dnsmasq''. See the section below on [[USB Networking#More on DNS|More on DNS]] for other solutions.

Test if it works:

ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Testing Your Connection =

Log in with a blank password (press enter). Now, make sure you can ping back to your desktop:

ping 192.168.0.200

This tests the basic network connection.

(Note that some systems like Vista, don't respond to ICMP ping by default)

Or your router, for example (your IP will probably be different):

ping 192.168.1.99

Or to a Google IP:

ping 74.125.19.147

This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

= Make it Permanent =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

The bug is that the LABEL="net_end" is at the wrong position

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= More on DNS =

== Hostnames ==

Instead of using the IP address, instead enter in your desktop's /etc/hosts:

192.168.0.202 openmoko

Then instead type:

ssh root@openmoko

== DNS proxying ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you). There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"

udpf-elf -p=53-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200

<span id="bottom"></span>
{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-05T23:11:10Z

Miohtama: Changed order of the sections for having the shortcut for the happiness

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Recent Linux distributions (Ubuntu 8.04 Hardy Heron) support USB Networking out of the box.

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Testing Your Connection ==

Log in with a blank password (press enter). Now, make sure you can ping back to your desktop:

ping 192.168.0.200

This tests the basic network connection.

(Note that some systems like Vista, don't respond to ICMP ping by default)

Or your router, for example (your IP will probably be different):

ping 192.168.1.99

Or to a Google IP:

ping 74.125.19.147

This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

== Configure DNS ==

Note that step won't help much if you don't have connectivity above. DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

nameserver 192.168.0.200

Which means that by default it expects your desktop to have a DNS server. On some Linux and Windows systems this is true, especially those configured as servers, but in general it is not. You can install packages such as ''bind9'' or ''dnsmasq''. See the section below on [[USB Networking#More on DNS|More on DNS]] for other solutions.

Test if it works:

ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Make it Permanent =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

The bug is that the LABEL="net_end" is at the wrong position

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= More on DNS =

== Hostnames ==

Instead of using the IP address, instead enter in your desktop's /etc/hosts:

192.168.0.202 openmoko

Then instead type:

ssh root@openmoko

== DNS proxying ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you). There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"

udpf-elf -p=53-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200

<span id="bottom"></span>
{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-05T23:07:28Z

Miohtama: /* Linux Kernel Support */

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Recent Linux distributions (Ubuntu 8.04 Hardy Heron) support USB Networking out of the box.

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

== Testing Your Connection ==

Log in with a blank password (press enter). Now, make sure you can ping back to your desktop:

ping 192.168.0.200

This tests the basic network connection.

(Note that some systems like Vista, don't respond to ICMP ping by default)

Or your router, for example (your IP will probably be different):

ping 192.168.1.99

Or to a Google IP:

ping 74.125.19.147

This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

== Configure DNS ==

Note that step won't help much if you don't have connectivity above. DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

nameserver 192.168.0.200

Which means that by default it expects your desktop to have a DNS server. On some Linux and Windows systems this is true, especially those configured as servers, but in general it is not. You can install packages such as ''bind9'' or ''dnsmasq''. See the section below on [[USB Networking#More on DNS|More on DNS]] for other solutions.

Test if it works:

ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Make it Permanent =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

The bug is that the LABEL="net_end" is at the wrong position

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= More on DNS =

== Hostnames ==

Instead of using the IP address, instead enter in your desktop's /etc/hosts:

192.168.0.202 openmoko

Then instead type:

ssh root@openmoko

== DNS proxying ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you). There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"

udpf-elf -p=53-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200

<span id="bottom"></span>
{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

Getting Started with your Neo FreeRunner

2008-08-05T23:06:17Z

Miohtama: Clarified the section so that it explains why this is needed (prerequisitement for SSH'ing into the phone)

{{Languages|Getting Started with your Neo FreeRunner}}
{{Gta02menu}}

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc; width:75% " |
<p align="left">
Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of [[Openmoko]]. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.</p>

<p align="left">
Some Frequently Asked Questions for new owners are featured in the [[Getting Started FAQ]].
</p>

! style="background:#fcfcfc; width:25% " |
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]
|}

== Package Contents ==

[[Image:GTA02ALL.png|left|400px|thumb|Inside the package]]
<br />
: [[Image:Circle２.gif|10px]] Neo FreeRunner
: [[Image:Circle２.gif|10px]] Stylus
: [[Image:Circle２.gif|10px]] Battery
: [[Image:Circle２.gif|10px]] Charger
: [[Image:Circle２.gif|10px]] USB Cable (A -> Mini-B 5-pole)
: [[Image:Circle２.gif|10px]] microSD Card 512MB & SD adapter

<div style="clear: both"> </div>

== Setting up the hardware, getting to know the Neo FreeRunner physically ==

===Installing the Micro-SD card, the SIM card, and the Battery ===

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|Open the case like this.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Opening !|center]]</td>
</tr>
<tr valign="top" style="background: #ffffff">
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here.|center]]</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|Finally, put in the battery.|center]]</td>
</tr></table>
</div>

# Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.
# Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.
# Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.
# Lift up on the SIM card holder.
# The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.
# Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo Freerunner.
# Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.
# Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.
# Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.
# Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.
# Replace the rear cover on the FreeRunner.

[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]

[[http://video.google.de/videoplay?docid=-8343770443102960945 A short video]] is also available. It was shot using the previous version of the Neo, but the installation procedures remains the same.

===Charging the Neo FreeRunner===

When using the Neo FreeRunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger (at 1000mA) or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.

Charging an empty battery at 100mA takes 12~15 hours, at 500mA takes 2,5~3,5 hours, and at 1000mA takes 1.5~2.5 hours. (90%~100%) [to be confirmed]

Make sure that the battery never discharges completely. This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work. Should the battery become completely discharged, your options are:
- Use external stand-alone charger (compatible with the Nokia BL-5C battery)
- Boot the FreeRunner with an alternative battery, or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
- Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.

[[Neo_FreeRunner_(GTA02)_Battery]]

===Buttons and connectors===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Power Button, USB and external GPS Antenna (left to right)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack (left to right)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Power'''
Tapping the power button exits the current application.

Holding the power button brings up a menu allowing you to:
* Power on and off the GPS, wifi, GSM, and bluetooth antennae
* Change power management mode to:
** Dim first then lock
** Dim only, don't lock
** Disabled
* Lock the screen
* Shutdown the device.</td>
<td></td>
<td>'''Aux'''
Tapping the Aux button hides or shows the currently running application.

Holding the Aux button brings up a menu allowing you to:

* Hide and show the title bar (Fullscreen toggle)
* Alternate wide or tall display modes (Swap Orientation)
* Save the content of the screen as an image file (Screenshot)
</td>
</tr>
</table>

Booting time is 2 about minutes overall, so patience is in order. The longest step comes after the Linux boot messages in very small fonts have scrolled by, at the graphical "openmoko" sunrise page.

The phone jack is a 2.5mm connector with four contacts: stereo + MIC. It is compatible with the headsets used by Motorola smartphones (A780,A1200, ...) and the V-360.

To plug regular (i.e. without microphone) headphones commonly used to listen to music, a compatible 2.5mm 4 rings jack to 3.5mm stereo jack adapter is needed. It has been reported that Nokia's 2.5mm -> 3.5mm adapters do not work, but that a 3.5mm Stereo Audio Adapter for Motorola MPx200/E398 works well. You will also want to switch from speaker output to headset, by restoring the appropriate alsa.state-file (usually the mediaplayer should do this for you) or via alsamixer (see below), to enable stereo output in there.

===Unlocking the screen===

When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.

== Navigating menus and applications ==

''Note:'' this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

====Today Page====

[[Image:Todaypage_reduced_true.png|200px|right]] Openmoko starts by displaying the "Today" page, which is your home page. Icons in the top row indicate the status of the phone. The bottom row consists of three tabs. The tab with a home on the left lead to the "Today" page you're viewing now. The central tab lead to the "Launch Task" page, which is the main menu used to start applications. The tab with gears on the right lead to the "Running Tasks" page, which is used to deal with currently open windows and applications.

<br clear=all />

[[Image:Todaypage_reduced_false.png|right|200px|]] The "Today" page is empty, as shown above, when you first start Openmoko. We explain below how to turn on the "full view", displayed to the right. In the full view, a second row of icons give quick links to commonly-used applications such as the dialer, the adressbook, mailbox and calendar. The main body of the screen displays a clock and other useful information.

See [[Today/2007.2]] for more information about the Today page and customization.

<br clear=all />

====Launch Task Page====

{{stub}}

[[Image:LaunchTasks.png|right|200px]] This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Current categories are [[PIM Suite]], [[Applications]], [[Games]], [[Utilities]], and All.

<br clear=all />

====Running Tasks Page====

{{stub}}

[[Image:RunningTasks.png|right|200px]] This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

<br clear=all />

====Exiting from and switching to an Application====

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can cycle through active applications using the AUX button

Clicking the top-left of the screen displays the drop down ''task menu''. This menu lists all active applications and allows to switch directly to any one. ''Note:'' If the task menu is not shown, click and hold the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".

== Using the terminal ==

To start a console from "Today" page, click the middle tab at the bottom of the screen to display the "Launch applications" page, then select Terminal in the "Applications" submenu. The multitaps keyboard slides up (and down) from the bottom of the screen automatically when you touch the screen.

===Setting date and time===

From the terminal, type the following, but replace ''MM'' with the month (01-12); ''DD'' with the day (01-31); ''hhmm'' with the time (0000-2359); ''YYYY'' with the year (optional); and ''.ss'' with the seconds (optional).

date -s ''MMDDhhmmYYYY.ss''

To make the change persist between reboots, sync the hardware clock with the updated system time.

hwclock --systohc

See [[Setting Date and Time]] for more discussion, including synchronizing with an NTP server.

===Adjusting the Volume===

As of this writing, there is no way to adjust the volume from the screen.

For now, run the terminal application or [[USB_Networking|log in via usb]], and run the [[Neo alsamixer]] application (to see all the options, including Mic2, you will need to run ''alsamixer -V all''). The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use
alsactl -f ''path-to-statefile'' store
to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):
:gsmhandset.state
:gsmheadset.state
:gsmspeakerout.state
:headset.state
:stereoout.state

These correspond to the various Sound Profiles accessible in the Debug Tool under Applications.

To manually restore one of the state files,
alsactl -f ''path-to-statefile'' restore

One way to increase the volume of the microphone is to do the following:
# ssh into your Freerunner
# vi /usr/share/openmoko/scenarios/gsmhandset.state
# search for "Mic2"
# change to "value 3"
If people report not being able to hear you when you call, then setting the Mic2 value to 2 or 3 should fix that.

'''Question: I am using headphones but only the right speaker work the left don't work how can I fix this ?'''

R: This should be set correctly by restoring gsmheadset.state.
Pull and replug the headset jack to make sure the correct state-file is restored.
To manually control the switch between Speaker and headset:
Start alsamixer, scroll along to the right until you find "Amp Spk" and mute it (m), the sound will then come out from both channels of the
headphones and not out of the speaker.

[[Freerunner_Hardware_Issues]]

=== Accessing the microSD card ===

Mounted at /media/card by default.

If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc.

== Set up USB-based networking, SSH and update ==

OpenMoko allows TCP/IP-over-USB networking for your phone. The main advantages of this are
* You don't need to set-up GPRS or WLAN network connection for the phone software to reach the Internet
* You can SSH from your computer into the phone shell and comfortably do low-level tasks using your computer's terminal software and real keyboard instead of the tiny screen and touchscreen keyboard

Naturally, the phone must be connected to your computer with USB cable.

===Connect with the Neo FreeRunner===

This is discussed in the [[USB_Networking|USB Networking]] section.

===Update with the package manager===

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intervals.

There are two main methods of doing this:
* upgrading with the package manager '''opkg'''
* or manually flashing the device (see [[Flashing the Neo FreeRunner]]).

There are three layers to the software on the FreeRunner:

* [[uboot|uBoot]]: Think of u-boot as a combination of the BIOS and Grub on a PC.
* Kernel: The Linux kernel
* Root Filesystem: The rest of the system

Note that ''uboot'', the ''kernel'' and the ''root filesystem'' may all be flashed to update them. For uboot, this is the only possibility (see [[Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader]]). The advantage of flashing the kernel manually rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Warning: UPGRADING TO DAILY KERNELS FROM THE DEVELOPMENT BRANCH MAY BREAK THINGS. That said, assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg -test upgrade
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second allows you to see what the package manager wants to do. The third upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.

Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use. Xserver must be updated over ssh to complete succesfully. Dropbear can be updated over ssh with the proper command:
# nohup opkg upgrade dropbear &
Or upgrade it directly in the FreeRunner terminal.
# opkg upgrade dropbear

When updating over ssh, the session will be interrupted, but the command should complete successfully(check nohup.out on your device to verify), and you should be able to reconnect within a few seconds.

Another (better) option is to start a screen session before the upgrade with:

# screen

After loosing the ssh connection and login in again via ssh reconnect to the running screen session with:

# screen -x

Then connect to the FreeRunner via ssh and type:
# opkg upgrade

Recent changes to the usb ethernet support require that you install these two modules, '''before''' you reboot, after updating.
# opkg install kernel-module-g-ether kernel-module-cdc-ether

And run this command :
# depmod

{{Note|http://lists.openmoko.org/pipermail/support/2008-August/thread.html#900}}

Alternatively you can upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal.

If you do your first upgrade in two installments like this, it will go more smoothly.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented.

=== Installing multimedia, web browsing and other applications ===

There are many applications you can install - check out the [[Repositories]] for a list of packages, an example of how to add a repository using scaredy cat as an example can also be found here. A list of pre-installed and available packages with descriptions can be found here - [[Available Packages]].

The calendar can be installed with

opkg install openmoko-dates2

For a Media Player:

opkg install openmoko-mediaplayer2
wget http://abraxa.dyndns.org:81/random/openmoko-mediaplayer-theme.tar.bz2
tar xjf openmoko-mediaplayer-theme.tar.bz2 -C /usr/share/themes/Moko/gtk-2.0
rm openmoko-mediaplayer-theme.tar.bz2

If you want a basic image viewer, have a look at the one from the gpe suite:

opkg install gpe-icons
opkg install gpe-gallery

To obtain the standard web browser, use:

opkg install openmoko-browser2

An alternative browser, minimo, offers many more features.
First download and unpack it on your GNU/Linux host:

wget http://www.ginguppin.de/files/minimo.tar.bz2
tar jvxf minimo.tar.bz2

Copy it over to the FreeRunner:
scp minimo_* root@192.168.0.202:/tmp

Then on the FreeRunner:
opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]

=== Importing contacts ===

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.

==The next steps==

Congratulations for setting up your Neo FreeRunner. There are many more ressources to help free your phone:

===Customize the interface===
home screen clock, keyboard

The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# /etc/init.d/xserver-nodm restart

If you rather have a regular clock instead of the digital one, do this instead:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false
# /etc/init.d/xserver-nodm restart

REMOVE CLICK SOUND VIA /etc/pulse/session

More information about today screen customization at [[Today/2007.2]].

Also, if you prefer having a full keyboard, using matchbox's qwerty keybord, see [[Switching_Keyboards#Matchbox_keyboard|these instructions]]. Then you may also see [http://lists.openmoko.org/pipermail/community/2008-July/021296.html these], which describe a way to add an applet allowing the showing/hiding of that keyboard.

===Use the GPS===

Simple guide to get going with '''GPS''':

# opkg install gpsd
# echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd

and restart gpsd, the gps daemon, with

# /etc/init.d/gpsd restart

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install http://www.tangogps.org/downloads/tangogps_0.9.2-r1_armv4t.ipk

There were critical [[GPS Problems]] earlier that are largely fixed in newest kernels, see the instructions above to install the updates. More information is on the [[GPS]] page.

===Play with WLAN, GPRS and Bluetooth===

There are plenty of development opportunities to integrate these functions in the OpenMoko software.

'''WLAN''': See [[Wireless Networking]]

'''GPRS''': See [[Manually using GPRS]]

'''Bluetooth''': See [[Manually using Bluetooth]]

=== Welcome to the community ===

The release of the Freerunner in the summer 2008 has led the community into a new period of rapid growth. The resources available are summarized on the [[Openmoko:Community_Portal]]. These are always exciting and interesting times to live in when the balance between Chaos and Order tilts towards change.

As an entry point, the [[http://lists.openmoko.org/pipermail/community/ openmoko community mailing list]] is perhaps the most active. As of July 2008, its volume amounts to dozens of messages per day. Openmoko people are there too. You may ask for help on the [[https://lists.openmoko.org/mailman/listinfo/support support mailing list]].

Or if you use IRC, there is always a good group in the channel #openmoko on FreeNode.

The links on the top-right of this page lead to the sister sites in the Openmoko community:
* Home and Wiki lead to the same Main Page on the wiki. It needs cleaning, we know...
* Doc leads to the bug ''Trac''king system.
* Planet goes to the collection of Openmoko-relatd blogs.
* Projects is the GForge, free hosting for application developers.
* Lists is the listing of all the public mailing lists on lists.openmoko.org.

== Annotated references ==

* The [http://quickstart.openmoko.org/ Quickstart guide]. Largely used as a basis for this page.
* [[Neo FreeRunner]]. The top-level view of the specifications.
* [[Neo FreeRunner GTA02 Hardware]]. The detailed specifications.
* [[GTA02 Openness]]. Ultimate chip-level specifications, data sheets and hardware documentation.
* [[Distributions]]. Strengths and weaknesses of the various distributions available for the Neo.
* [[Getting Started FAQ]]. Answers.
* [[GTA02_FAQ]]. More answers

To search this wiki with Google, use the following search term:

<search term> site:http://wiki.openmoko.org/wiki/

[[Category:GTA02 Hardware]]
[[Category:Guides]]

Minimo

2007-05-10T11:08:42Z

Miohtama:

Minimo

2007-05-10T11:07:06Z

Miohtama:

= Installing Minimo web browser =

[http://www.mozilla.org/projects/minimo/develop.html Minimo] is Mozilla based web browser. It features full AJAX support and other goodies. Currently stock OpenMoko build doesn't include Minimo. Here are instructions how to run minimo in Xephyr PC environment and how to use other third party packages too.

* [http://bec-systems.com/web/content/view/59/9/ Instructions for including new OpenEmbedded packages to your project]

== Setup build environment ==

If you have build your OpenMoko using MokoMakefile some of these steps might not be familiar to you.

Assume your OpenMoko root is at ~/workspace/moko

First setup build environment variables:

moo@hacker:~/workspace/moko/build$ . ../setup-env

Then checkout minimo from OpenEmbedded repository:

moo@hacker:~/workspace/moko/build$ bitbake minimo

Edit local.conf and add minimo to build dependencies list.

MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "minimo"

After local.conf has added new packages, one must refresh bitbake tasks.

bitbake task-base -crebuild

Now, you should be able to rebuild root fs using MokoMakefile.

make openmoko-devel-image

The default OpenMoko distribution lacks /etc/resolf.conf file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf

[edit]
In chroot'ed environment

Following instructions in Getting OpenMoko working on host with Xephyr to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start OpenMoko session, minimo can run as is.

/ $ minimo

Retrieved from "http://wiki.openmoko.org/wiki/Minimo"
Views

* Article
* Discussion
* Edi
moo@hacker:~/workspace/moko/build$ . ../setup-env
</pre>

Then checkout minimo from OpenEmbedded repository:
<pre>
moo@hacker:~/workspace/moko/build$ bitbake minimo
</pre>

Edit local.conf and add minimo to build dependencies list.

<pre>
MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "minimo"
</pre>

After local.conf has added new packages, one must refresh bitbake tasks.

<pre>
bitbake task-base -crebuild
</pre>

Now, you should be able to rebuild root fs using MokoMakefile.

<pre>
make openmoko-devel-image
</pre>

The default OpenMoko distribution lacks ''/etc/resolf.conf'' file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

<pre>
moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf
</pre>

== In chroot'ed environment ==

Following instructions in [[Getting OpenMoko working on host with Xephyr]] to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start OpenMoko session, minimo can run as is.

<pre>
/ $ minimo
</pre>

Minimo

2007-05-10T11:05:34Z

Miohtama:

= Installing Minimo web browser =

[http://www.mozilla.org/projects/minimo/develop.html Minimo] is Mozilla based web browser. It features full AJAX support and other goodies. Currently stock OpenMoko build doesn't include Minimo. Here are instructions how to run minimo in Xephyr PC environment and how to use other third party packages too.

* [http://bec-systems.com/web/content/view/59/9/ Instructions for including new OpenEmbedded packages to your project]

== Setup build environment ==

If you have build your OpenMoko using MokoMakefile some of these steps might not be familiar to you.

Assume your OpenMoko root is at ~/workspace/moko

First setup build environment variables:
<pre>Minimo
From OpenMoko
Jump to: navigation, search
[edit]
Installing Minimo web browser

Minimo is Mozilla based web browser. It features full AJAX support and other goodies. Currently stock OpenMoko build doesn't include Minimo. Here are instructions how to run minimo in Xephyr PC environment and how to use other third party packages too.

* Instructions for including new OpenEmbedded packages to your project

[edit]
Setup build environment

If you have build your OpenMoko using MokoMakefile some of these steps might not be familiar to you.

Assume your OpenMoko root is at ~/workspace/moko

First setup build environment variables:

moo@hacker:~/workspace/moko/build$ . ../setup-env

Then checkout minimo from OpenEmbedded repository:

moo@hacker:~/workspace/moko/build$ bitbake minimo

Edit local.conf and add minimo to build dependencies list.

MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "python minimo"

After local.conf has added new packages, one must refresh bitbake tasks.

bitbake task-base -crebuild

Now, you should be able to rebuild root fs using MokoMakefile.

make openmoko-devel-image

The default OpenMoko distribution lacks /etc/resolf.conf file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf

[edit]
In chroot'ed environment

Following instructions in Getting OpenMoko working on host with Xephyr to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start OpenMoko session, minimo can run as is.

/ $ minimo

Retrieved from "http://wiki.openmoko.org/wiki/Minimo"
Views

* Article
* Discussion
* Edi
moo@hacker:~/workspace/moko/build$ . ../setup-env
</pre>

Then checkout minimo from OpenEmbedded repository:
<pre>
moo@hacker:~/workspace/moko/build$ bitbake minimo
</pre>

Edit local.conf and add minimo to build dependencies list.

<pre>
MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "minimo"
</pre>

After local.conf has added new packages, one must refresh bitbake tasks.

<pre>
bitbake task-base -crebuild
</pre>

Now, you should be able to rebuild root fs using MokoMakefile.

<pre>
make openmoko-devel-image
</pre>

The default OpenMoko distribution lacks ''/etc/resolf.conf'' file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

<pre>
moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf
</pre>

== In chroot'ed environment ==

Following instructions in [[Getting OpenMoko working on host with Xephyr]] to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start OpenMoko session, minimo can run as is.

<pre>
/ $ minimo
</pre>

Host-based development with Xoo and Xephyr

2007-05-08T20:41:47Z

Miohtama:

One of good ways to get started developing is getting rootfs working on host machine, since most of us doesn't have real hardware.

Xoo is a graphical wrapper around Xnest, the nested X server. You can make Xnest look like a particular device's display and set up buttons on that device. This is useful for embedded developers who want to simulate a target device on their desktop machine.

Please see [[Getting OpenMoko working on host with Xephyr]] which might contain more up-to-date information.

== Getting rootfs ==
Use the [[MokoMakefile|Building OpenMoko using the MokoMakefile]] to get rootfs, just before make openmoko-devel-image run
# sed -i 's/fic-gta01/x86/' build/conf/local.conf
than just run make openmoko-devel-image. After a while(half of day) you should have in build/tmp/image/ file openmoko-devel-image-x86-$(DATE).rootfs.tar.gz mine is here [http://www.ms.mff.cuni.cz/~kupem6am/openmoko-devel-image-x86-20070227064250.rootfs.tar.gz].

=== Build issues ===

[http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=264 Please see this bug tracker issues] if you have problems getting libelf compiled (do_stage fails).

== Install Xoo on your host ==
For gentoo users run just
# emerge xoo
Debian/Ubuntu
# sudo apt-get install xoo xnest
For Fedora (package has been submitted to Fedora for approval, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236297):
# ftp://ftp.xelerance.com/xoo/

for any other find a way how to do it in your distro.

== Making X cooperate ==
* Make sure your iptables do not prevent you from connecting to port 6000(x11) on localhost

* Make sure your X is listening on port 6000(X11) on localhost (netstat is friend)

* Enable conection from localhost
# xhost localhost
== Preparing rootfs ==
* Unpack rootfs file in any directory and cd to that dir.

* Get dev files in rootfs
# sudo mount --bind /dev/ rootfs/dev/

* Chroot to rootfs
# sudo chroot rootfs /bin/sh
== Getting it up ==
In another term start xoo, good idea is to download [http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2] and run
# xoo --device neo1973.xml
In chrooted enviroment export display to connect to started xoo
# export DISPLAY=localhost:1.0
and start window manager.
# x-window-manager
By this time you should have matchbox running in Xoo window.

Getting OpenMoko working on host with Xephyr

2007-05-08T20:40:03Z

Miohtama: /* Setup the image filesystem */

The goal of this page is to show you how to run an OpenMoko development image on your host x86 development machine in a chrooted environment.

== Build an image ==

First, you should use [[MokoMakefile|Building OpenMoko using the MokoMakefile]] to build an openmoko-devel-image for your host architecture (x86 in our case). Make sure you put the moko makefile in /home/moko/Makefile .

Prior to that, edit your build/conf/local.conf to make it look like this:

MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"

Once you have built the image, you can start working toward running the image.

== Setup the image filesystem ==

Please see the included help script at the bottom of this article. It should make your life much easier.

The filesystem of the image can be found at /home/moko/build/tmp/rootfs . It is that image that we want to run in a chrooted environment.

We will copy that that rootfs directory somewhere so that subsquent builds (using the MokoMakefile for instance) don't overwrite it.

Make sure you have root privileges:
su -

Copy the rootf into a directory called MokoBox. From now on, we will call the chrooted environment a MokoBox.

cp -r /home/moko/build/tmp/rootfs /home/moko/mokobox

make sure /dev and /proc of the host machine are visible from within mokobox

mount --bind /dev /homo/moko/mokobox/dev
mount -t proc none /home/moko/mokobox/proc

start the mokobox

chroot /homo/moko/mokobox /bin/sh

=== In chroot'ed environment ===

set environment variables

DISPLAY=:1
LANG=C
HOME=/home/root
export DISPLAY LANG HOME

Create pango.modules file

pango-querymodules > /etc/pango/pango.modules

Create gdk-pixbuf.loaders file

gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders

Remove touch screen calibrator. Since touch screen hardware is not present, the touch screen calibration prevents X start-up on PC.

rm /etc/X11/Xsession.d/30xTs_Calibrate

== Starting the nested X server ==

=== Supplying fonts ===

You might need to install fonts supplied by OpenMoko to your host system. The easiest way to do is in Gnome is to go Preferences -> Font - > Details -> Go to font folder and then drag and drop TTF font files from build/tmp/rootfs/usr/share/fonts/ in Nautilus.

=== Launching Xephyr ===

In another terminal (not related to mokobox), start Xephyr

Xephyr :1 -ac -2button -host-cursor -screen 480x640

Now, back in chroo'ted environment, start X client:

eval $(dbus-launch)
/etc/X11/Xsession

You should see OpenMoko booting in the Xephyr window.

[[Image:Xephyr.png]]

== A sample script ==

The following script sets up the most of root fs environment automatically

<pre>
#!/bin/bash
#
# Set-up x86 OpenMoko root jail. This script must be run as root.
#
# Root jail is an environment, where the file system root has been
# changed to the OpenMoko root file system folder. Please don't
# use the build/rootfs, but make a copy of it, since build/rootfs
# gets overwritten each time you build openmoko-devel-image
#
# You need to set-up another X server (nested preferably) to
# act as a OpenMoko screen. Otherwise chrooted applications are executed
# as is on the host hardware and the kernel.
#
# See:
#
# http://wiki.openmoko.org/wiki/Getting_OpenMoko_working_on_host_with_Xephyr
#
#
# 2007 Mikko Ohtamaa - Red Innovation Ltd.
# <mikko@redinnovation.com>
#
# Do anything you wish with this script
#
#
#

# Setup required environment variables

# Xephyr must listen to this DISPLAY
DISPLAY=:1

# If we don't have locale, applications refuse to launch
LANG=C

# We are running as root in our chrooted environment

HOME=/home/root
export DISPLAY LANG HOME

# Update pango modules
pango-querymodules > /etc/pango/pango.modules

# Update icon images
gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders

# Mount /dev and /proc file systems
mount --bind /dev ./dev
mount -t proc none ./proc

# Remove touch screen calibration start up app
# It doesn't launch on x86 and prevents X booting
if [ -e /etc/X11/Xsession.d/30xTs_Calibrate ] ; then
rm /etc/X11/Xsession.d/30xTs_Calibrate
fi

# Use host name server information so that
# web browsing works
cp /etc/resolv.conf etc/resolv.conf

# Enter into chroot jail
chroot . /bin/sh

</pre>

Getting OpenMoko working on host with Xephyr

2007-05-08T20:39:31Z

Miohtama: /* Starting the nested X server */

The goal of this page is to show you how to run an OpenMoko development image on your host x86 development machine in a chrooted environment.

== Build an image ==

First, you should use [[MokoMakefile|Building OpenMoko using the MokoMakefile]] to build an openmoko-devel-image for your host architecture (x86 in our case). Make sure you put the moko makefile in /home/moko/Makefile .

Prior to that, edit your build/conf/local.conf to make it look like this:

MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"

Once you have built the image, you can start working toward running the image.

== Setup the image filesystem ==

The filesystem of the image can be found at /home/moko/build/tmp/rootfs . It is that image that we want to run in a chrooted environment.

We will copy that that rootfs directory somewhere so that subsquent builds (using the MokoMakefile for instance) don't overwrite it.

Make sure you have root privileges:
su -

Copy the rootf into a directory called MokoBox. From now on, we will call the chrooted environment a MokoBox.

cp -r /home/moko/build/tmp/rootfs /home/moko/mokobox

make sure /dev and /proc of the host machine are visible from within mokobox

mount --bind /dev /homo/moko/mokobox/dev
mount -t proc none /home/moko/mokobox/proc

start the mokobox

chroot /homo/moko/mokobox /bin/sh

=== In chroot'ed environment ===

set environment variables

DISPLAY=:1
LANG=C
HOME=/home/root
export DISPLAY LANG HOME

Create pango.modules file

pango-querymodules > /etc/pango/pango.modules

Create gdk-pixbuf.loaders file

gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders

Remove touch screen calibrator. Since touch screen hardware is not present, the touch screen calibration prevents X start-up on PC.

rm /etc/X11/Xsession.d/30xTs_Calibrate

== Starting the nested X server ==

=== Supplying fonts ===

You might need to install fonts supplied by OpenMoko to your host system. The easiest way to do is in Gnome is to go Preferences -> Font - > Details -> Go to font folder and then drag and drop TTF font files from build/tmp/rootfs/usr/share/fonts/ in Nautilus.

=== Launching Xephyr ===

In another terminal (not related to mokobox), start Xephyr

Xephyr :1 -ac -2button -host-cursor -screen 480x640

Now, back in chroo'ted environment, start X client:

eval $(dbus-launch)
/etc/X11/Xsession

You should see OpenMoko booting in the Xephyr window.

[[Image:Xephyr.png]]

== A sample script ==

The following script sets up the most of root fs environment automatically

<pre>
#!/bin/bash
#
# Set-up x86 OpenMoko root jail. This script must be run as root.
#
# Root jail is an environment, where the file system root has been
# changed to the OpenMoko root file system folder. Please don't
# use the build/rootfs, but make a copy of it, since build/rootfs
# gets overwritten each time you build openmoko-devel-image
#
# You need to set-up another X server (nested preferably) to
# act as a OpenMoko screen. Otherwise chrooted applications are executed
# as is on the host hardware and the kernel.
#
# See:
#
# http://wiki.openmoko.org/wiki/Getting_OpenMoko_working_on_host_with_Xephyr
#
#
# 2007 Mikko Ohtamaa - Red Innovation Ltd.
# <mikko@redinnovation.com>
#
# Do anything you wish with this script
#
#
#

# Setup required environment variables

# Xephyr must listen to this DISPLAY
DISPLAY=:1

# If we don't have locale, applications refuse to launch
LANG=C

# We are running as root in our chrooted environment

HOME=/home/root
export DISPLAY LANG HOME

# Update pango modules
pango-querymodules > /etc/pango/pango.modules

# Update icon images
gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders

# Mount /dev and /proc file systems
mount --bind /dev ./dev
mount -t proc none ./proc

# Remove touch screen calibration start up app
# It doesn't launch on x86 and prevents X booting
if [ -e /etc/X11/Xsession.d/30xTs_Calibrate ] ; then
rm /etc/X11/Xsession.d/30xTs_Calibrate
fi

# Use host name server information so that
# web browsing works
cp /etc/resolv.conf etc/resolv.conf

# Enter into chroot jail
chroot . /bin/sh

</pre>

Talk:Getting OpenMoko working on host with Xephyr

2007-05-08T20:34:02Z

Miohtama:

I can't get dbus working.

After succesfully evaling dbus-launch, I start getting these errors:

got heredbus-marshal-recursive.c(1186)
got heredbus-marshal-recursive.c(1186)

and applications like web and messages don't launch

--[[User:Miohtama|Moo]] 22:34, 8 May 2007 (CEST)

Talk:Getting OpenMoko working on host with Xephyr

2007-05-08T20:33:46Z

Miohtama:

Getting OpenMoko working on host with Xephyr

2007-05-08T20:31:33Z

Miohtama: /* Launching Xephyr */

Minimo

2007-05-03T00:19:18Z

Miohtama: /* Installing Minimo web browser */

Minimo

2007-05-03T00:00:36Z

Miohtama: /* Setup build environment */

Minimo

2007-05-02T23:55:12Z

Miohtama: /* Installing Minimo web browser */

Getting OpenMoko working on host with Xephyr

2007-05-02T23:36:02Z

Miohtama: /* Launching Xephyr */

Getting OpenMoko working on host with Xephyr

2007-05-02T23:35:29Z

Miohtama: /* In chroot'ed environment */

Getting OpenMoko working on host with Xephyr

2007-05-02T23:30:21Z

Miohtama: /* Launching Xephyr */

File:Xephyr.png

2007-05-02T23:29:31Z

Miohtama:

Main Page

2007-05-02T23:19:27Z

Miohtama: /* Hands-on Guides */

<big>'''Welcome to the [[OpenMoko]] public Wiki'''</big><br>
<small>For other languages see the [[#bottom|bottom]] of this page.</small>

[[Image:FIC-neo1973_small.jpg|200px|right|frontside]]
[[OpenMoko]] is an [http://en.wikipedia.org/wiki/Open_source Open Source] project to create the world's first free mobile phone operating system.

The [[OpenMoko]] project is a community that anyone can join, and help to design their ideal phone.

The [[Neo1973]] from [[FIC]] is the first of many phones that [[OpenMoko]] will run on.

The long term goal of [[OpenMoko]] is that phone software will no longer be tied to one phone. You can buy any compatible phone, and install any software over the whole range of phones. If you upgrade your phone, you don't lose the software. Bugs fixed on one phone are fixed on all.

Please join us in collaborating on the [[OpenMoko | OpenMoko project]] through any of the [[Development resources | project resources]] including the [[Main Page | OpenMoko wiki]]. Please see the [[Help:Contents | wiki editing help page]] for information on making contributions to this wiki. A [[Meet the Core Team | core team of developers funded by FIC, Inc.]] leads the project.

An [[Introduction | introduction page]] is available. The [[Introduction | page]] has both [[Introduction#Photos|photos]] and [[Introduction#Videos|videos]] available. Moreover, the usual [[FAQ | Frequently Asked Questions, FAQ, page]] might be helpful. Developers may find the [[ChangeLog | daily software change log]] an important resource.

The members of the [[OpenMoko]] community would like to thank [[FIC|FIC Inc.]] for showing leadership and initiating the [[OpenMoko]] project.

== [[OpenMoko]] Areas of Interest ==

* [[Basic End-user]] - Information for end users that want basic functionality and no surprises
* [[Advanced End-user]] - Information for advanced end-users that want advanced and experimental functionality but who are not programmers
* [[Development resources | Project Resources]] page provides a centralized location of all resources such as [[Development resources#Mailing_Lists|mailing lists]], [[Development resources#IRC | communication tools]], and other software development oriented resources.
* [[Application Developer]] - Information for application developers, including ideas and specifications for applications, and tools to build them
* [[System Developer]] - Information for system developers, including bootloader, kernel, and libraries
* [[Hardware Developer]] - Information for hardware developers, including hardware specs and debug board
* [[Community Events]] - Information on both [[Community Events#Past Events | past ]] and [[Community Events#Past Events#FIC / OpenMoko at Events | future]] events where FIC or [[OpenMoko]] had or will have a presence.

== Developer's Documentation ==

=== Hands-on Guides ===
* [[Getting Started with your Neo1973]]
* [[MokoMakefile|Building OpenMoko using the MokoMakefile]]
* [[Building OpenMoko from scratch]]
** Old [[Building OpenMoko from scratch (pre-BBT)]]
* [[Migration to bad block tolerant builds]]
* [[Running OpenMoko on PC]]
** [[Getting Openmoko working on host with Xoo]]
** [[Getting OpenMoko working on host with Xephyr]]
** [[How to run OpenMoko Apps on PC]]
** [[OpenMoko under QEMU]]
* [[Booting from SD]]

=== Hardware Reference Documentation ===
* All [[:Category:Hardware|Hardware]] related documentation and specifications are found on the [[:Category:Hardware|Hardware page]].
* The [[:Category:Neo1973 Hardware|Neo1973 Hardware page]] provides an overview of the hardware components used by the [[:Category:Neo1973 Hardware|Neo1973 hardware platform]]. PCB Photographs are also included. A [[Disassembling Neo1973 | photo disassemble story]] may be an interesting starting place.
* [[:Category:Neo1973 Hardware Debugging | Neo1973 Hardware Debugging]] is assisted with the [[Debug Board | Neo1973 debug board]]. A page discussing [[Connecting Neo1973 with Debug Board v2 | debug board and Neo1973 configurations]] are also provided.

=== Software Reference Documentation ===
* Architectural
** [[OpenMokoFramework]] - The OpenMoko Application Framework
* [[neo1973 host software]]
* Device Software
** Low-Level
*** [[u-boot]] - The bootloader we use, including documentation for our modifications
*** [[kernel]] - The Linux kernel we use, including documentation for our modifications
** Userspace
*** [[gsmd]] - the GSM daemon managing the GSM Modem
*** [[gpsd]] - the AGPS (Assisted GPS) daemon

=== OpenMoko===
* [[OpenEmbedded]] - The distribution-building framework
* [[Toolchain]] - The toolchain we use for compilation
* [[OpenMoko]] - The OpenMoko distribution
** [[OpenMoko2007]] - The first intended release of it
** [[Userspace root image]]

==== User Interface Related ====
* [[Look & Feel]]
* [[Applications]]
* [[Widgets]]
** [[Widget Inheritance Graph]]

=== Misc. Development Related ===
* [[Templates]]
* [[PIM Storage]]
* [[Coding Guidelines]]
* [[OpenMoko#Setting_up_an_OpenMoko_SDK|How to setup the OpenMoko SDK]]
* [[License]] - How we license our code
* [[Development resources]] - Describes resources for developers (lists, svn, ...)
* [[Neo1973 Phase 0]] -- Information for Phase 0 device owners
* [[Wishlist:Neo1973 P0 Review]] -- Impressions of the Phase 0 hardware device, also the Phase 0 FAQ

== Administrative / Organizational ==

* [[Shipping Notes]] - Information to help FIC figure out how to ship products to you, and how much it might cost.
* [[My Account]] - Ideas for what sort of account-based services FIC should provide with the phone.

== Miscellaneous ==
* [[WiFi support in OpenMoko]] - Or rather the lack thereof
* [[Neo1973 and Windows]] - If you want to commit that offence ;) (does not work, help!)
* [[Press Coverage]] - What the press says about the OpenMoko project
* [[mFAQ]] - The OpenMoko Misinformation FAQ ('''mFAQ''') - What the press '''''incorrectly''''' says about the OpenMoko project
* [[Wish List]] - A collection of ideas and ideals we'd like to see implemented some day
* [[Wish List - Hardware]] - A collection of ideas we'd like to see in the next Neo release
* [[Wishlist:BuiltInScriptingLanguage|Wish List - Built-in Scripting Language]] - Discussion on a suitable scripting language to be included
* [[Media Content]] - What types of media on the device can we use (that is non-software)?
* [[Testimonials]] - How did you get to OpenMoko?
* [[Buying Interest List]] - (Not official and not a pre-order page) Have you have put money aside for Neo1973? Put your nick here.
* [[iPhone]] - Comparison between Apple iPhone and FIC Neo1973
* [[Translation]] - Translation of OpenMoko
* [[Summer of code]] - Our page with project applications for Googles Summer of Code

<span id="bottom"></span>
{{Languages|Main_Page}}

Main Page

2007-05-02T23:19:10Z

Miohtama: /* Misc. Development Related */

<big>'''Welcome to the [[OpenMoko]] public Wiki'''</big><br>
<small>For other languages see the [[#bottom|bottom]] of this page.</small>

[[Image:FIC-neo1973_small.jpg|200px|right|frontside]]
[[OpenMoko]] is an [http://en.wikipedia.org/wiki/Open_source Open Source] project to create the world's first free mobile phone operating system.

The [[OpenMoko]] project is a community that anyone can join, and help to design their ideal phone.

The [[Neo1973]] from [[FIC]] is the first of many phones that [[OpenMoko]] will run on.

The long term goal of [[OpenMoko]] is that phone software will no longer be tied to one phone. You can buy any compatible phone, and install any software over the whole range of phones. If you upgrade your phone, you don't lose the software. Bugs fixed on one phone are fixed on all.

Please join us in collaborating on the [[OpenMoko | OpenMoko project]] through any of the [[Development resources | project resources]] including the [[Main Page | OpenMoko wiki]]. Please see the [[Help:Contents | wiki editing help page]] for information on making contributions to this wiki. A [[Meet the Core Team | core team of developers funded by FIC, Inc.]] leads the project.

An [[Introduction | introduction page]] is available. The [[Introduction | page]] has both [[Introduction#Photos|photos]] and [[Introduction#Videos|videos]] available. Moreover, the usual [[FAQ | Frequently Asked Questions, FAQ, page]] might be helpful. Developers may find the [[ChangeLog | daily software change log]] an important resource.

The members of the [[OpenMoko]] community would like to thank [[FIC|FIC Inc.]] for showing leadership and initiating the [[OpenMoko]] project.

== [[OpenMoko]] Areas of Interest ==

* [[Basic End-user]] - Information for end users that want basic functionality and no surprises
* [[Advanced End-user]] - Information for advanced end-users that want advanced and experimental functionality but who are not programmers
* [[Development resources | Project Resources]] page provides a centralized location of all resources such as [[Development resources#Mailing_Lists|mailing lists]], [[Development resources#IRC | communication tools]], and other software development oriented resources.
* [[Application Developer]] - Information for application developers, including ideas and specifications for applications, and tools to build them
* [[System Developer]] - Information for system developers, including bootloader, kernel, and libraries
* [[Hardware Developer]] - Information for hardware developers, including hardware specs and debug board
* [[Community Events]] - Information on both [[Community Events#Past Events | past ]] and [[Community Events#Past Events#FIC / OpenMoko at Events | future]] events where FIC or [[OpenMoko]] had or will have a presence.

== Developer's Documentation ==

=== Hands-on Guides ===
* [[Getting Started with your Neo1973]]
* [[MokoMakefile|Building OpenMoko using the MokoMakefile]]
* [[Building OpenMoko from scratch]]
** Old [[Building OpenMoko from scratch (pre-BBT)]]
* [[Migration to bad block tolerant builds]]
* [[Running OpenMoko on PC]]
** [[Getting Openmoko working on host with Xoo]]
** [[Getting OpenMoko working on host with Xephyr]]
* [[Booting from SD]]

=== Hardware Reference Documentation ===
* All [[:Category:Hardware|Hardware]] related documentation and specifications are found on the [[:Category:Hardware|Hardware page]].
* The [[:Category:Neo1973 Hardware|Neo1973 Hardware page]] provides an overview of the hardware components used by the [[:Category:Neo1973 Hardware|Neo1973 hardware platform]]. PCB Photographs are also included. A [[Disassembling Neo1973 | photo disassemble story]] may be an interesting starting place.
* [[:Category:Neo1973 Hardware Debugging | Neo1973 Hardware Debugging]] is assisted with the [[Debug Board | Neo1973 debug board]]. A page discussing [[Connecting Neo1973 with Debug Board v2 | debug board and Neo1973 configurations]] are also provided.

=== Software Reference Documentation ===
* Architectural
** [[OpenMokoFramework]] - The OpenMoko Application Framework
* [[neo1973 host software]]
* Device Software
** Low-Level
*** [[u-boot]] - The bootloader we use, including documentation for our modifications
*** [[kernel]] - The Linux kernel we use, including documentation for our modifications
** Userspace
*** [[gsmd]] - the GSM daemon managing the GSM Modem
*** [[gpsd]] - the AGPS (Assisted GPS) daemon

=== OpenMoko===
* [[OpenEmbedded]] - The distribution-building framework
* [[Toolchain]] - The toolchain we use for compilation
* [[OpenMoko]] - The OpenMoko distribution
** [[OpenMoko2007]] - The first intended release of it
** [[Userspace root image]]

==== User Interface Related ====
* [[Look & Feel]]
* [[Applications]]
* [[Widgets]]
** [[Widget Inheritance Graph]]

=== Misc. Development Related ===
* [[Templates]]
* [[PIM Storage]]
* [[Coding Guidelines]]
* [[OpenMoko#Setting_up_an_OpenMoko_SDK|How to setup the OpenMoko SDK]]
* [[License]] - How we license our code
* [[Development resources]] - Describes resources for developers (lists, svn, ...)
* [[Neo1973 Phase 0]] -- Information for Phase 0 device owners
* [[Wishlist:Neo1973 P0 Review]] -- Impressions of the Phase 0 hardware device, also the Phase 0 FAQ

== Administrative / Organizational ==

* [[Shipping Notes]] - Information to help FIC figure out how to ship products to you, and how much it might cost.
* [[My Account]] - Ideas for what sort of account-based services FIC should provide with the phone.

== Miscellaneous ==
* [[WiFi support in OpenMoko]] - Or rather the lack thereof
* [[Neo1973 and Windows]] - If you want to commit that offence ;) (does not work, help!)
* [[Press Coverage]] - What the press says about the OpenMoko project
* [[mFAQ]] - The OpenMoko Misinformation FAQ ('''mFAQ''') - What the press '''''incorrectly''''' says about the OpenMoko project
* [[Wish List]] - A collection of ideas and ideals we'd like to see implemented some day
* [[Wish List - Hardware]] - A collection of ideas we'd like to see in the next Neo release
* [[Wishlist:BuiltInScriptingLanguage|Wish List - Built-in Scripting Language]] - Discussion on a suitable scripting language to be included
* [[Media Content]] - What types of media on the device can we use (that is non-software)?
* [[Testimonials]] - How did you get to OpenMoko?
* [[Buying Interest List]] - (Not official and not a pre-order page) Have you have put money aside for Neo1973? Put your nick here.
* [[iPhone]] - Comparison between Apple iPhone and FIC Neo1973
* [[Translation]] - Translation of OpenMoko
* [[Summer of code]] - Our page with project applications for Googles Summer of Code

<span id="bottom"></span>
{{Languages|Main_Page}}

User:Miohtama

2007-05-02T23:18:50Z

Miohtama:

Hi,

I am a wild guy from Oulu, Finland.

[http://www.redinnovation.com Please check my company pages]

Running OpenMoko on PC

2007-05-02T23:18:21Z

Miohtama:

= Running OpenMoko on PC =

Thanks to Linux portability, OpenMoko can be run on PC easily, without the need of actual hardware.

== Using QEmu ==

QEmu is full scale emulator which emulates OpenMoko hardware, including ARM CPU. You will have emulator or stub devices which match the actual hardware. There is a lot of performance penalty for emulating non-native CPU like ARM on x86/x64 architecture. Also, setting up ARM tool chain might be difficult.

* [[OpenMoko under QEMU]]

== Running applications natively ==

You can run OpenMoko "as is" on your X desktop. Since OpenMoko applications are GTK based, they can appear like any other application windows on your desktop. Or you might want to run them inside a nested X server, which gives you the ability to emulate OpenMoko screen resolution as well.

This is recommended option if your applications don't need access to actual hardware, but can accept dummy input data e.g. constant power meter value. There is no performance penalty, which might be actually a bad thing, since there is a great different between PC and Neo1973 power. Also, compiling for x86 targets seems to be a bit faster.

Currently, Xephyr documentation is most up-to-date. --[[User:Miohtama|Moo]] 01:18, 3 May 2007 (CEST)

* [[Getting OpenMoko working on host with Xephyr]]
* [[Getting Openmoko working on host with Xoo]]
* [[How to run OpenMoko Apps on PC]]

Main Page

2007-05-02T23:10:27Z

Miohtama: /* Hands-on Guides */

<big>'''Welcome to the [[OpenMoko]] public Wiki'''</big><br>
<small>For other languages see the [[#bottom|bottom]] of this page.</small>

[[Image:FIC-neo1973_small.jpg|200px|right|frontside]]
[[OpenMoko]] is an [http://en.wikipedia.org/wiki/Open_source Open Source] project to create the world's first free mobile phone operating system.

The [[OpenMoko]] project is a community that anyone can join, and help to design their ideal phone.

The [[Neo1973]] from [[FIC]] is the first of many phones that [[OpenMoko]] will run on.

The long term goal of [[OpenMoko]] is that phone software will no longer be tied to one phone. You can buy any compatible phone, and install any software over the whole range of phones. If you upgrade your phone, you don't lose the software. Bugs fixed on one phone are fixed on all.

Please join us in collaborating on the [[OpenMoko | OpenMoko project]] through any of the [[Development resources | project resources]] including the [[Main Page | OpenMoko wiki]]. Please see the [[Help:Contents | wiki editing help page]] for information on making contributions to this wiki. A [[Meet the Core Team | core team of developers funded by FIC, Inc.]] leads the project.

An [[Introduction | introduction page]] is available. The [[Introduction | page]] has both [[Introduction#Photos|photos]] and [[Introduction#Videos|videos]] available. Moreover, the usual [[FAQ | Frequently Asked Questions, FAQ, page]] might be helpful. Developers may find the [[ChangeLog | daily software change log]] an important resource.

The members of the [[OpenMoko]] community would like to thank [[FIC|FIC Inc.]] for showing leadership and initiating the [[OpenMoko]] project.

== [[OpenMoko]] Areas of Interest ==

* [[Basic End-user]] - Information for end users that want basic functionality and no surprises
* [[Advanced End-user]] - Information for advanced end-users that want advanced and experimental functionality but who are not programmers
* [[Development resources | Project Resources]] page provides a centralized location of all resources such as [[Development resources#Mailing_Lists|mailing lists]], [[Development resources#IRC | communication tools]], and other software development oriented resources.
* [[Application Developer]] - Information for application developers, including ideas and specifications for applications, and tools to build them
* [[System Developer]] - Information for system developers, including bootloader, kernel, and libraries
* [[Hardware Developer]] - Information for hardware developers, including hardware specs and debug board
* [[Community Events]] - Information on both [[Community Events#Past Events | past ]] and [[Community Events#Past Events#FIC / OpenMoko at Events | future]] events where FIC or [[OpenMoko]] had or will have a presence.

== Developer's Documentation ==

=== Hands-on Guides ===
* [[Getting Started with your Neo1973]]
* [[MokoMakefile|Building OpenMoko using the MokoMakefile]]
* [[Building OpenMoko from scratch]]
** Old [[Building OpenMoko from scratch (pre-BBT)]]
* [[Migration to bad block tolerant builds]]
* [[Running OpenMoko on PC]]
** [[Getting Openmoko working on host with Xoo]]
** [[Getting OpenMoko working on host with Xephyr]]
* [[Booting from SD]]

=== Hardware Reference Documentation ===
* All [[:Category:Hardware|Hardware]] related documentation and specifications are found on the [[:Category:Hardware|Hardware page]].
* The [[:Category:Neo1973 Hardware|Neo1973 Hardware page]] provides an overview of the hardware components used by the [[:Category:Neo1973 Hardware|Neo1973 hardware platform]]. PCB Photographs are also included. A [[Disassembling Neo1973 | photo disassemble story]] may be an interesting starting place.
* [[:Category:Neo1973 Hardware Debugging | Neo1973 Hardware Debugging]] is assisted with the [[Debug Board | Neo1973 debug board]]. A page discussing [[Connecting Neo1973 with Debug Board v2 | debug board and Neo1973 configurations]] are also provided.

=== Software Reference Documentation ===
* Architectural
** [[OpenMokoFramework]] - The OpenMoko Application Framework
* [[neo1973 host software]]
* Device Software
** Low-Level
*** [[u-boot]] - The bootloader we use, including documentation for our modifications
*** [[kernel]] - The Linux kernel we use, including documentation for our modifications
** Userspace
*** [[gsmd]] - the GSM daemon managing the GSM Modem
*** [[gpsd]] - the AGPS (Assisted GPS) daemon

=== OpenMoko===
* [[OpenEmbedded]] - The distribution-building framework
* [[Toolchain]] - The toolchain we use for compilation
* [[OpenMoko]] - The OpenMoko distribution
** [[OpenMoko2007]] - The first intended release of it
** [[Userspace root image]]

==== User Interface Related ====
* [[Look & Feel]]
* [[Applications]]
* [[Widgets]]
** [[Widget Inheritance Graph]]

=== Misc. Development Related ===
* [[Templates]]
* [[PIM Storage]]
* [[Coding Guidelines]]
* [[How to run OpenMoko Apps on PC]]
* [[OpenMoko under QEMU]]
* [[OpenMoko#Setting_up_an_OpenMoko_SDK|How to setup the OpenMoko SDK]]
* [[License]] - How we license our code
* [[Development resources]] - Describes resources for developers (lists, svn, ...)
* [[Neo1973 Phase 0]] -- Information for Phase 0 device owners
* [[Wishlist:Neo1973 P0 Review]] -- Impressions of the Phase 0 hardware device, also the Phase 0 FAQ

== Administrative / Organizational ==

* [[Shipping Notes]] - Information to help FIC figure out how to ship products to you, and how much it might cost.
* [[My Account]] - Ideas for what sort of account-based services FIC should provide with the phone.

== Miscellaneous ==
* [[WiFi support in OpenMoko]] - Or rather the lack thereof
* [[Neo1973 and Windows]] - If you want to commit that offence ;) (does not work, help!)
* [[Press Coverage]] - What the press says about the OpenMoko project
* [[mFAQ]] - The OpenMoko Misinformation FAQ ('''mFAQ''') - What the press '''''incorrectly''''' says about the OpenMoko project
* [[Wish List]] - A collection of ideas and ideals we'd like to see implemented some day
* [[Wish List - Hardware]] - A collection of ideas we'd like to see in the next Neo release
* [[Wishlist:BuiltInScriptingLanguage|Wish List - Built-in Scripting Language]] - Discussion on a suitable scripting language to be included
* [[Media Content]] - What types of media on the device can we use (that is non-software)?
* [[Testimonials]] - How did you get to OpenMoko?
* [[Buying Interest List]] - (Not official and not a pre-order page) Have you have put money aside for Neo1973? Put your nick here.
* [[iPhone]] - Comparison between Apple iPhone and FIC Neo1973
* [[Translation]] - Translation of OpenMoko
* [[Summer of code]] - Our page with project applications for Googles Summer of Code

<span id="bottom"></span>
{{Languages|Main_Page}}

Minimo

2007-05-02T23:06:40Z

Miohtama:

User talk:Miohtama

2007-05-02T23:00:11Z

Miohtama:

Hi,

I am a wild guy from Oulu, Finland.

[http://www.redinnovation.com Please check my company pages]

Getting OpenMoko working on host with Xephyr

2007-05-02T22:55:24Z

Miohtama: /* Start nested X server */

Getting OpenMoko working on host with Xephyr

2007-05-02T22:44:54Z

Miohtama: /* In chroot'ed environment */

Getting OpenMoko working on host with Xephyr

2007-05-02T22:44:42Z

Miohtama: /* Start nested X server */

Getting OpenMoko working on host with Xephyr

2007-05-02T22:44:11Z

Miohtama: /* Start nested X server */

Getting OpenMoko working on host with Xephyr

2007-05-02T22:41:28Z

Miohtama: /* Setup the image filesystem */

Getting OpenMoko working on host with Xephyr

2007-05-02T22:26:05Z

Miohtama: /* Setup the image filesystem */

Getting OpenMoko working on host with Xephyr

2007-05-02T21:58:27Z

Miohtama: /* setup the image filesystem */

Talk:Getting OpenMoko working on host with Xephyr

2007-05-02T19:59:45Z

Miohtama:

I get the following error:

<pre>
OE Build Configuration:
BB_VERSION = "1.6.7"
OE_REVISION = "<unknown>"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"
DISTRO = "openmoko"
DISTRO_VERSION = ".dev-snapshot-20070502"
TARGET_FPU = ""

NOTE: preferred version 2.12.3 of glib-2.0 not available
...
NOTE: package ltrace-0.4: started
NOTE: package ltrace-0.4-r0: task do_compile: started
ERROR: function do_compile failed
ERROR: log data follows (/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/log.do_compile.11205)
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| NOTE: make ARCH=i586 INSTALL_FILE=$(INSTALL) -p -m 0644 INSTALL_PROGRAM=$(INSTALL) -p -m 0755 INSTALL_SCRIPT=$(INSTALL) -p -m 0755 INSTALL_DIR=$(INSTALL) -p -d -m 0755 LDFLAGS=-L/media/sda3/dump/workspace/moko/build/tmp/staging/i586-linux/lib -Wl,-rpath-link,/media/sda3/dump/workspace/moko/build/tmp/staging/i586-linux/lib -Wl,-O1 LIBS=-lsupc++ -liberty -Wl,-Bstatic -lelf -Wl,-Bdynamic ARCH=i586 INSTALL_FILE=$(INSTALL) -p -m 0644 INSTALL_PROGRAM=$(INSTALL) -p -m 0755 INSTALL_SCRIPT=$(INSTALL) -p -m 0755 INSTALL_DIR=$(INSTALL) -p -d -m 0755
| make[1]: Entering directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4'
| make -C sysdeps/linux-gnu
| make[2]: Entering directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4/sysdeps/linux-gnu'
| make[2]: *** No rule to make target `i586/arch.h', needed by `sysdep.h'. Stop.
| make[2]: Leaving directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4/sysdeps/linux-gnu'
| make[1]: *** [sysdeps/sysdep.o] Error 2
| make[1]: Leaving directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4'
| FATAL: oe_runmake failed
NOTE: Task failed: /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/log.do_compile.11205
NOTE: package ltrace-0.4-r0: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package ltrace-0.4: failed
ERROR: Build of openmoko-devel-image failed
make: *** [openmoko-devel-image] Error 1
</pre>

--[[User:Miohtama|Miohtama]] 21:50, 2 May 2007 (CEST)

ltrace/sysdeps/linux-gnu had i386 folder, but no i586 folder. I created i586 symlink to i386. Let's see if it works. Ubuntu Feisty Fawn is the build host.

--[[User:Miohtama|Miohtama]] 21:59, 2 May 2007 (CEST)

Talk:Getting OpenMoko working on host with Xephyr

2007-05-02T19:52:33Z

Miohtama:

Talk:Getting OpenMoko working on host with Xephyr

2007-05-02T19:50:57Z

Miohtama:

I get the following error:

OE Build Configuration:
BB_VERSION = "1.6.7"
OE_REVISION = "<unknown>"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"
DISTRO = "openmoko"
DISTRO_VERSION = ".dev-snapshot-20070502"
TARGET_FPU = ""

NOTE: preferred version 2.12.3 of glib-2.0 not available
...
NOTE: package ltrace-0.4: started
NOTE: package ltrace-0.4-r0: task do_compile: started
ERROR: function do_compile failed
ERROR: log data follows (/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/log.do_compile.11205)
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/run.do_compile.11205: line 34: INSTALL: command not found
| NOTE: make ARCH=i586 INSTALL_FILE=$(INSTALL) -p -m 0644 INSTALL_PROGRAM=$(INSTALL) -p -m 0755 INSTALL_SCRIPT=$(INSTALL) -p -m 0755 INSTALL_DIR=$(INSTALL) -p -d -m 0755 LDFLAGS=-L/media/sda3/dump/workspace/moko/build/tmp/staging/i586-linux/lib -Wl,-rpath-link,/media/sda3/dump/workspace/moko/build/tmp/staging/i586-linux/lib -Wl,-O1 LIBS=-lsupc++ -liberty -Wl,-Bstatic -lelf -Wl,-Bdynamic ARCH=i586 INSTALL_FILE=$(INSTALL) -p -m 0644 INSTALL_PROGRAM=$(INSTALL) -p -m 0755 INSTALL_SCRIPT=$(INSTALL) -p -m 0755 INSTALL_DIR=$(INSTALL) -p -d -m 0755
| make[1]: Entering directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4'
| make -C sysdeps/linux-gnu
| make[2]: Entering directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4/sysdeps/linux-gnu'
| make[2]: *** No rule to make target `i586/arch.h', needed by `sysdep.h'. Stop.
| make[2]: Leaving directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4/sysdeps/linux-gnu'
| make[1]: *** [sysdeps/sysdep.o] Error 2
| make[1]: Leaving directory `/media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/ltrace-0.4'
| FATAL: oe_runmake failed
NOTE: Task failed: /media/sda3/dump/workspace/moko/build/tmp/work/i586-linux/ltrace-0.4-r0/temp/log.do_compile.11205
NOTE: package ltrace-0.4-r0: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package ltrace-0.4: failed
ERROR: Build of openmoko-devel-image failed
make: *** [openmoko-devel-image] Error 1

--[[User:Miohtama|Miohtama]] 21:50, 2 May 2007 (CEST)

Host-based development with Xoo and Xephyr

2007-04-28T13:00:49Z

Miohtama: /* Getting rootfs */

One of good ways to get started developing is getting rootfs working on host machine, since most of us doesn't have real hardware.

Xoo is a graphical wrapper around Xnest, the nested X server. You can make Xnest look like a particular device's display and set up buttons on that device. This is useful for embedded developers who want to simulate a target device on their desktop machine.

== Getting rootfs ==
Use the [[MokoMakefile|Building OpenMoko using the MokoMakefile]] to get rootfs, just before make openmoko-devel-image run
# sed -i 's/fic-gta01/x86/' build/conf/local.conf
than just run make openmoko-devel-image. After a while(half of day) you should have in build/tmp/image/ file openmoko-devel-image-x86-$(DATE).rootfs.tar.gz mine is here [http://www.ms.mff.cuni.cz/~kupem6am/openmoko-devel-image-x86-20070227064250.rootfs.tar.gz].

=== Build issues ===

[http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=264 Please see this bug tracker issues] if you have problems getting libelf compiled (do_stage fails).

== Install Xoo on your host ==
For gentoo users run just
# emerge xoo
Debian/Ubuntu
# sudo apt-get install xoo xnest
For Fedora (package has been submitted to Fedora for approval, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236297):
# ftp://ftp.xelerance.com/xoo/

for any other find a way how to do it in your distro.

== Making X cooperate ==
* Make sure your iptables do not prevent you from connecting to port 6000(x11) on localhost

* Make sure your X is listening on port 6000(X11) on localhost (netstat is friend)

* Enable conection from localhost
# xhost localhost
== Preparing rootfs ==
* Unpack rootfs file in any directory and cd to that dir.

* Get dev files in rootfs
# sudo mount --bind /dev/ rootfs/dev/

* Chroot to rootfs
# sudo chroot rootfs /bin/sh
== Getting it up ==
In another term start xoo, good idea is to download [http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2] and run
# xoo --device neo1973.xml
In chrooted enviroment export display to connect to started xoo
# export DISPLAY=localhost:1.0
and start window manager.
# x-window-manager
By this time you should have matchbox running in Xoo window.

Talk:Higher level language options

2007-04-27T20:36:44Z

Miohtama:

The 'feature matrix' is, imho, an ill-concieved idea. There is no way you can fit the subtleties and details of programming langauges into a matrix. One of the huge problems is that many languages have a variety of compilers, interpreters, etc, each with its own performance traits.

The matrix concept is salvageable - split it into multiple categories - Interpreted, Just-in-timed, and compiled. The main reason for this is the large variance in difficulty in porting each category. The matrix within each of these categories would be tailored to it. For JIT and interpreted, the core executer size is important. For JIT, the estimated startup time for complex apps is important. Another issue is portage. Many interpreters for major interpreted languages are written in C for this very reason - there's not so much that an interpreter must depend on. Compilers are quite a bit harder to handle, as they must generate quite specific code. JITs will sometimes have a subset which must be rewritten on port - for mono, this is about 5000 lines.

[[User:Mgsloan|Mgsloan]] 09:04, 19 April 2007 (CEST)

It seems Python is the higher level language of choice for [http://www.gnome.org/mobile/ GNOME Mobile & Embedded Initiative] , the [http://www.laptop.org/laptop/software/specs.shtml One Laptop per Child] project and the best supported HLL in Nokias [http://downloads.maemo.org/product/python/ Maemo] platform. So we can probably expect many mobile applications for these platforms will be written in Python, and also that Python bindings for essential libraries will have lots of community support. Things like these should perhaps also be important deciding factors, not only the specifics of the language itself.

--[[User:Anderso|Anderso]] 09:13, 20 April 2007 (CEST)

Also, Nokia has ported Python to its Series 60 platform. It's used for rapid prototyping and some third party apps.

Host-based development with Xoo and Xephyr

2007-04-27T17:27:57Z

Miohtama:

One of good ways to get started developing is getting rootfs working on host machine, since most of us doesn't have real hardware.

Xoo is a graphical wrapper around Xnest, the nested X server. You can make Xnest look like a particular device's display and set up buttons on that device. This is useful for embedded developers who want to simulate a target device on their desktop machine.

== Getting rootfs ==
Use the [[MokoMakefile|Building OpenMoko using the MokoMakefile]] to get rootfs, just before make openmoko-devel-image run
# sed -i 's/fic-gta01/x86/' build/conf/local.conf
than just run make openmoko-devel-image. After a while(half of day) you should have in build/tmp/image/ file openmoko-devel-image-x86-$(DATE).rootfs.tar.gz mine is here [http://www.ms.mff.cuni.cz/~kupem6am/openmoko-devel-image-x86-20070227064250.rootfs.tar.gz].

== Install Xoo on your host ==
For gentoo users run just
# emerge xoo
Debian/Ubuntu
# sudo apt-get install xoo xnest
For Fedora (package has been submitted to Fedora for approval, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236297):
# ftp://ftp.xelerance.com/xoo/

for any other find a way how to do it in your distro.

== Making X cooperate ==
* Make sure your iptables do not prevent you from connecting to port 6000(x11) on localhost

* Make sure your X is listening on port 6000(X11) on localhost (netstat is friend)

* Enable conection from localhost
# xhost localhost
== Preparing rootfs ==
* Unpack rootfs file in any directory and cd to that dir.

* Get dev files in rootfs
# sudo mount --bind /dev/ rootfs/dev/

* Chroot to rootfs
# sudo chroot rootfs /bin/sh
== Getting it up ==
In another term start xoo, good idea is to download [http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2] and run
# xoo --device neo1973.xml
In chrooted enviroment export display to connect to started xoo
# export DISPLAY=localhost:1.0
and start window manager.
# x-window-manager
By this time you should have matchbox running in Xoo window.

Host-based development with Xoo and Xephyr

2007-04-27T17:05:48Z

Miohtama: /* Install Xoo on your host */

One of good ways to get started developing is getting rootfs working on host machine, since most of us doesn't have real hardware.

== Getting rootfs ==
Use the [[MokoMakefile|Building OpenMoko using the MokoMakefile]] to get rootfs, just before make openmoko-devel-image run
# sed -i 's/fic-gta01/x86/' build/conf/local.conf
than just run make openmoko-devel-image. After a while(half of day) you should have in build/tmp/image/ file openmoko-devel-image-x86-$(DATE).rootfs.tar.gz mine is here [http://www.ms.mff.cuni.cz/~kupem6am/openmoko-devel-image-x86-20070227064250.rootfs.tar.gz].

== Install Xoo on your host ==
For gentoo users run just
# emerge xoo
Debian/Ubuntu
# sudo apt-get install xoo xnest
For Fedora (package has been submitted to Fedora for approval, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236297):
# ftp://ftp.xelerance.com/xoo/

for any other find a way how to do it in your distro.

== Making X cooperate ==
* Make sure your iptables do not prevent you from connecting to port 6000(x11) on localhost

* Make sure your X is listening on port 6000(X11) on localhost (netstat is friend)

* Enable conection from localhost
# xhost localhost
== Preparing rootfs ==
* Unpack rootfs file in any directory and cd to that dir.

* Get dev files in rootfs
# sudo mount --bind /dev/ rootfs/dev/

* Chroot to rootfs
# sudo chroot rootfs /bin/sh
== Getting it up ==
In another term start xoo, good idea is to download [http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2] and run
# xoo --device neo1973.xml
In chrooted enviroment export display to connect to started xoo
# export DISPLAY=localhost:1.0
and start window manager.
# x-window-manager
By this time you should have matchbox running in Xoo window.

MokoMakefile

2007-04-24T19:52:33Z

Miohtama: /* Installation */

==MokoMakefile==
MokoMakefile is a fully automated way of setting up an OpenMoko development environment. It is an invaluable tool for getting new developers up and running with a build environment which is configured the same as all the other existing developers. It brings the same repeatability to build environment creation and maintenance as that which OpenEmbedded brings to the main task of actually building embedded software distributions.

Note that MokoMakefile does *not* replace bitbake, or svn, or monotone, or openembedded, or qmake, or anything else. It is a wrapper around all that to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by OpenMoko. Note that you need about 7 GB of available disk space for MokoMakefile to succeed.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of OpenMoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Building_OpenMoko_from_scratch|official OpenMoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

=== Before you begin ===
Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash. Using dash will cause you pain. If you have previously built with dash as your sh shell then your perl compile is probably broken. One symptom is that the build will error and whine about an 'Unterminated quote string' another symptom is a message that says 'You haven't done a "make depend" yet!' If you get these then you need to:
make clean-package-perl
make clean-package-perl-native
and rebuild.

If all else fails then just rm -rf the perl work dir and the perl stamps here's an i686 host example:
rm -rf build/tmp/work/i686-linux/perl-native-5.8.7-r3
rm -f build/tmp/stamps/i686-linux/perl*

=== Installation ===
Here are the steps to use it:

1 - Make sure your build host is set up according to:
http://www.openembedded.org/wiki/OEandYourDistro
2 - Create your $OMDIR directory:
mkdir /home/moko ; cd /home/moko
3 - Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile
4 - Set up the environment:
make setup
5 - Start building. Before starting a lenghty make process, check in Tips section about how to make Make multicore aware:
make openmoko-devel-image

This will set up the recommended directory structure as described in [[Building OpenMoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

===Updating the environment===
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To update the OpenMoko repository checkout and the MokoMakefile patches to the latest version:
make update

3 - To make sure that any recent changes to the build directory structure have been applied:
make setup

A quick way to rebuild a new image with the latest updates:
make update-makefile && make update && make setup && make openmoko-devel-image

===Reporting Problems===

First, make sure that the problem is reproducable after running

make update-makefile ; make update ; make setup

then running

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

then running

make all

If you can get the error to occur three times in a row after running that sequence of commands three times, then feel free to report it to rwhitby in #openmoko on [http://wiki.openmoko.org/wiki/Development_resources#IRC IRC].

===Work-arounds===

Work-arounds for temporary or isolated problems should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

===Tips===
*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. /home/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly.

*If you an encounter an error with monotone similar to the following:
mtn: misuse: database /home/moko/OE.mtn is laid out according to an old schema
Then you need to upgrade OE.mtn Use the following command while in /home/moko:
# mtn --db OE.mtn db migrate

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

*For amd64 host users you need the patch from http://bugs.openembedded.org/show_bug.cgi?id=1765 to build db3-native

===QEMU===
The MokoMakefile now has support for automatically building, flashing, and running [[OpenMoko under QEMU|the new Neo1973 emulator]] (which is based on QEMU).

“make qemu” will build qemu-neo1973, download the latest official OpenMoko images, flash the images into the virtual NAND flash, and run the emulator.

Other targets are “make download-images” (to download the latest official images), “make flash-qemu-official” (to flash those images) and “make flash-qemu-local” (which will flash your latest locally built images), which can then be followed by “make run-qemu” or “make run-qemu-snapshot” to run the emulator with the most recently flashed images.

Make sure you have the “lynx” and “netpbm” packages installed on your build host first.

You're also invited to read more about how to run [[OpenMoko under QEMU]] in the article dedicated to this subject.

===Developing with MokoMakefile===

To make in-tree changes and have them built and used by qemu:

cd /home/moko/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change
(do this for every file you are about to modify)
...make the changes...
quilt refresh
(this creates a file in /home/moko/patches/openmoko-HEAD/ and
updates the quilt series file there)

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

===Testimonials===
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", and "MokoMakefile rocks!".

Project page:
http://mokomakefile.projects.openmoko.org/

{{Languages|MokoMakefile}}

OpenMoko under QEMU

2007-04-24T15:05:30Z

Miohtama: /* Building the environment manually */

QEMU can basically be used in three ways to run [[OpenMoko]]. Depending on the purpose that you are going to use the emulator for, you should decide on the target platform.

*PC - OpenMoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get OpenMoko running if you want to get an impression of how it looks. In this scenario QEMU would only serve for isolating your [[OpenMoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].

*Integrator/CP - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the CPU. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F|FAQ]].

*Neo1973 - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] hardware, although not all of it at this moment. It is a work-in-progress and when it's more mature it is going to be submitted for merging to the main QEMU development tree.

== Neo1973 emulation ==
This target will (obviously) run original OpenMoko rootfs images, but then it should also be able to run the original u-boot and kernel images, the same ones that a real Neo1973 uses. Among other differences you will notice between this approach and the Integrator/CP target is you also get correct screen resolution, some (fake) battery readings, and other goodness. Currently missing parts of the emulator are: [[GSM]] modem, [[Hardware:AGPS|AGPS]] and [[Bluetooth]], as well as the USB slave functionality - these things will still be worked on, as well as general usability. Even with these things missing, QEMU should provide substantial help in debugging kernel and u-boot issues to developers.

What QEMU can *not* be used for, and probably no other emulator can, is speed measures and getting the general feel of OpenMoko performance. Code running in qemu runs with the maximum speed your host computer can provide with an overhead of translating target code to host code, and this overhead is not uniform across different instructions. This means that even if your virtual Neo reports near 100 BogoMIPS (which is the speed of a real Neo), different actions performed in the emulator will not run with the same speed. On most PCs you will notice the virtual Neo running faster than a real one (Audio related operations may be one of the exceptions).

=== What hardware is supported ===

Rough status for each of the components that need emulation, following the outline of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] page.
{|
! Hardware !! Status !! Usage notes
|- style="background-color:#eeeedd;"
! colspan="3"|S3C2410A Processor
|-
|ARM920T core || Works || Already in mainline QEMU.
|-
|Basic guts || Work || This includes GPIO interface, DMA, Interrupt Controller, Timers, NAND controller, MMC/SD host, [[I2C]] and IIS interfaces, Memory & Clock & Power management controllers, RAM.
|-
|Serial ports || Work || Use the "-serial" switch (maybe be specified multiple times) to tell QEMU where serial input/output should go to. GSM module will be connected on UART0.
|-
|RTC || Works || On start QEMU will load it with current time/date - the Neo1973 [[kernel]] doesn't use it for time/date source currently.
|-
|SPI || Works || The guest kernel can drive it using either the SPI interface or raw GPIO bitbanging.
|-
|LCD || Works || The virtual LCD will display as in QEMU window iff "-nographic" is not specified.
|-
|ADC || Works || Mouse events in QEMU window generate what would be touchscreen events on a Neo1973 and are passed to the guest OS through the on-chip ADC.
|-
|OHCI USB || Works || This part is in mainline QEMU. Use the "-usb" switch to enable the controller and "usb_add" in QEMU monitor to attach new virtual or physical USB devices.
|-
|Slave USB
|style="background-color:#ffcccc;"|To Do
|Possibly Linux's dummy HCD in conjunction with gadget filesystem API can make the virtual Neo appear as a real one connected to your computer. Otherwise different host functions (usbtty, usbnet) could be emulated.
|-
|Watchdog
|style="background-color:#ffcccc;"|To Do
|This is one of the less important on-chip peripherals in S3C2410. It is however used by Linux for rebooting the board.
|- style="background-color:#eeeedd;"
! colspan="3"|[[I2C]] bus peripherals
|-
|[[PCF50606]]||Works||(Aka PMU) Fakes the battery charge level (set at 88%), POWER button, etc. Also contains and RTC, also unused by Linux.
|-
|[[LM4857]]||Works
|-
|[[WM8753L]]||Works||The CODEC is also connect to the CPU's IIS port. Basic [[Neo1973 Audio Subsystem|audio functionality]] is supported - see QEMU documentation on getting audio input/output from the emulator. Volume control has no effects.
|- style="background-color:#eeeedd;"
! colspan="3"|Other peripherals
|-
|NAND Flash||Works||However, some pieces are not confirmed to be completely compatible with the real hardware because of lack thereof. Use "-mtdblock flashimagefilenamehere" switch to point QEMU to your flash image. The file should be at least 69206016 bytes big.
|-
|JBT6K74-AS(PI)||Works|| (Aka LCM) Wired to the SPI channel 1
|-
|Buttons||Work||Enter is the AUX button, Space is the POWER button. Wired to on-chip GPIO and PCF50606.
|-
|SD card||Works||This part is already in mainline QEMU. Use the "-sd cardimagegoeshere" switch to point QEMU to the card image. The regular QEMU monitor commands for removable media can also be used. The card works, however the on-chip host controller gave block length errors on heavy I/O despite working as described in specification. I suspect the kernel driver. DMA operation is not tested.
|-
|Bluetooth
|style="background-color:#ffcccc;"|To Do
|Will require implementing the Delta DBFM chip and connecting it to USB. The ROM will likely be replaced with code to translate communication directly to TCP/UDP networking (like Slirp). A real bluetooth dongle can also be attached to the emulator (see USB documentation in QEMU).
|-
|[[GSM]]
|style="background-color:#ffcccc;"|In Progress
|A fake modem will be connected to UART0 with as much functionality as possible (basic AT commands understanding, fake GPRS connections and SMS send/receive). This way all parts of the phone subsystem (CALYPSO, TWL3014, TRF6151) will not have to be emulated. There is a possibility to wire a real GSM modem to QEMU's serial port.
|-
|[[Hardware:AGPS|AGPS]]
|style="background-color:#ffcccc;"|To Do
|There are obvious difficulties emulating the chip, but hopefully it can be made to present the guest OS with some fixed coordinates later when more is known about the chip. Again a real chip could be connected to QEMU's serial port.
|}

== How to get it running ==

=== Using MokoMakefile ===

This is the recommended way since you won't need to deal with the compiling and flashing processes yourself. See [[MokoMakefile#QEMU|MokoMakefile]] for details.

=== Building the environment manually ===
Qemu building requires to have SDL or Cocoa installed.
To obtain the latest source code for the emulator, you will want to do something like the following:
<pre>
$ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973
$ cd qemu-neo1973
</pre>
Now, we're going to configure and build the emulator:
<pre>
$ ./configure --target-list=arm-softmmu --cc=/usr/bin/gcc-3.4 # GCC 3.x will be required
$ make
</pre>
See other available options for the configure script by appending "--help".
Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run OpenMoko you will also need to somehow install OpenMoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First, run
<pre>$ openmoko/download.sh</pre>
which will look up the list of latest available OpenMoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the next command:
<pre>$ openmoko/flash.sh</pre>
which runs the emulator, loads u-boot into it and then uses u-boot's capability to program the Flash memory to install all the necessary parts of the system into the virtual Flash. It will also set up all the bootloading process including a boot menu, splash, u-boot environment and some default kernel parameters. If everything goes OK, the script should print a command which you can use to start using the emulator.

QEMU has *tons* of commandline switches and things that can be configured. You can look them up in [http://www.qemu.org/user-doc.html QEMU user docs]. You will probably want to use the "-snapshot" switch, among other ones.

=== Pre-built binaries ===

Win32 binaries shipped with firmware can be downloaded from [http://mdk.linux.org.tw/~jserv/openmoko/openmoko-emulator-win32-bin-20070416.zip openmoko-emulator-win32-bin-20070416.zip]. Tested on Ms Windows XP.

== Requirements ==
The QEMU tree has only been tested on GNU/Linux. To get graphical and/or audio output from the emulator you will need SDL installed on your computer. To enable audio, see the available switches to the ./configure script.
All of the requirements listed in [http://www.qemu.org/user-doc.html QEMU documentation] apply.

== QEMU and GNU debugger ==
QEMU lets you debug operating system kernels and bootloaders like you debug all other programs. To do this you will need a debugger that speaks the GDB remote debugging protocol - [http://sourceware.org/gdb/ GDB] is the obvious choice. Some cross toolchains come with GDB already set up. Otherwise building cross-GDB yourself is quick and easy (compared to building binutils and cross-gcc).

To debug u-boot, load the file "u-boot" into gdb (not "u-boot.bin") that is produced by "make" when building u-boot. To debug a Linux kernel, load the file "vmlinux" from the main source directory into gdb. These files are in ELF format and contain all the symbol information and are not stripped of debugging data until you run "strip" on them, unlike "u-boot.bin" and "Image"/"zImage"/"uImage". Next, tell QEMU to enable the gdbserver by appending the "-s" switch or issuing "gdbserver" in the monitor. Use the command <pre>(gdb) target remote localhost:1234</pre> to make a connection to the emulator. From there you should be able to use all the usual GDB commands, including stepping instructions, setting breakpoints, watchpoints, inspecting stack, variables, registers and more. If gdb is running in the same directory from which it grabbed the ELF executable, the "edit" command should work so you can jump right to the source line which is executing.