Openmoko - User contributions [en]

Openmoko Local Groups: Duesseldorf

2009-05-26T11:40:50Z

Emdete: /* 9.6.2009 */

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:Samon007|Lix]]
|System Administrator, Scripting
|I've ordered a GTA01Bv4 together with a friend from University. I like to pimp it to a network tool, showing CDP messages, doing pings and telnet maybe a sniffer if that will not be banned by law in a few weeks
|Düsseldorf
|willing to organize stuff i.e. meeting location/whatever. [[User_talk:Samon007|talk to me]].
|
|
|-
| [[User:Risto|Risto]]
| Assembler, C, C++
| Learning how OpenSource software works, contributing to OpenSource
| Bocholt
|
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
| [[User:klinux|Klinux]]
| Assembler, C, C++, shell scripting, Linux
| Would like to contribute to the project, interested in getting basic phone functionality working from UI and maybe help integrating a web browser.
| Düsseldorf
| Just received my Neo and successfully made a phone call :-)
|
|
|-
|[[User:emdete|emdete]]
| Developer; C, Python, Shellskripting, Java skills
| Will test low-level services like gsm daemon with a different application
| Düsseldorf
| Interested in apps using directfb, different mobile phone software aproach, Openmoko on the greenphone.
| [[Image: Moko.jpg|center]]
|
|-
| [[User:Mac2k|mac2k]]
| linux user
|
| Gerresheim
|
|align=center|[[Image: Moko.jpg]] GTA02
|
|-
| [[User:l0ll|L0ll]]
| a little bit Pascal and Linux
| Learn a bit about open-source and of course i want to have a nice phone
| Woppenroth
| waiting for the FreeRunner :)
|
|
|-
| [[User:Quix0r|Quix0r]]
| PHP5, Linux (since 1999), Bash scripting, ...
| Want to replace his prohibitory against a free one.
| [[Openmoko_Local_Groups:_Krefeld|Krefeld]]
| Waiting for the FreeRunner. :-)
|
|
|-
| [[User:MoR4euZ|MoR4euZ]]
| linux user
|
| Essen
| Waiting for the FreeRunner
|
|
|-
| [[User:Zem|Zem]]
| 'sysadmin' 'linux' 'softwarepackaging' 'placeholder'
| Many Ideas, and to many projects. ;-)
| Neandertal
| Jabber: zem at jabber.ccc.de
| GTA01 und GTA02
| Debug Board v2
|-
| [[User:daswaldhorn|Daswaldhorn]]
| Linux user (Ubuntu, SuSE)
| first: basic phone functionality, second: GPS, etc...
| Voerde
| Jabber: daswaldhorn@jabber.ccc.de
| GTA02
|
|-
|...
|
|
|
|
|
|
|}

=== Meetings, Events ===
Meeting language is German ;-)
{|border=1
!Date
!Location
!Topic
!Who
|-
|[[OMLG-Duesseldorf_Meeting_20070823|23.08.2007, 17:00 UTC (19:00 CEST)]]
|[http://www.destille-duesseldorf.de/ Destille Düsseldorf]
|First GTA01Bv4 impressions for P1 owners and those who have no Neo yet. Giving each other a helping hand getting started.
|[[User:Samon007|Lix]], [[User:emdete|emdete]], [[User:Risto|Risto]], ...
|-
|somewhere in 2008...
|to be done
|Is there any interest to meet again and talk about news?
|
|-
|2009
|to be done
|Would be great if a new meeting will be there...
|[[user:daswaldhorn|Daswaldhorn]]
|}

=== Planung Usertreffen 2009 ===

Ich habe alle Nutzer auf dieser Seite angeschrieben, bisher haben grundsätzlich Interesse bekundet:
*emdete
*mac2k
*Risto
*Carsten
Ich schlage einfach mal den 9.6. vor. Treffen wir uns irgendwo zwischen Bocholt und Düsseldorf... mmh, Voerde wäre da nicht schlecht. ;-)

Grüße, [[User:Daswaldhorn|Daswaldhorn]] 20:15, 24 May 2009 (UTC)

==== 9.6.2009 ====

termin okay:

* Carsten
* mac2k (Julian) - aber wo?

termin passt nicht:

* emdete (lieber in der woche davor oder danach)

[[Category:Openmoko Local Groups]]

Qi

2009-05-18T23:02:33Z

Emdete: /* Kernel Commandline Generation */

[[image:Screenshot-Qi.png|frame|Qi Boot messages]] Qi ( [[http://zh.wikipedia.org/wiki/气| '''氣''' ]] ) is a lightweight replacement for the [[Uboot|uBoot]] bootloader with everything that doesn't assist "loading" and "booting" Linux stripped out.

Its advantages comparing to [[Uboot|u-boot]] are:
* actively developed (u-boot on GTA02 is deprecated)
* easier configuration, more robust and predictable
* SD and SDHC cards supported properly with partitions of any size
* kernel size is detected by checking the start of the kernel image, so large (>2M) kernels are supported without tweaking or loading more than needed
* Very fast, simple boot direct to Linux

==About Qi==
===Requirements===
There is a [[Neo1973|GTA01]] build of Qi, but using it without a debug board is not recommended because Qi itself does not support DFU, so updating or going back to U-Boot is a difficult process.

[[Freerunner|GTA02 Hardware]] has NOR U-Boot always available, so updating to Qi is safe to try it out.

===Download===

*GTA01 -> qi-s3c2410
*GTA02 -> qi-s3c2442

====New Versions====

These are the versions we are getting ready for release

Download from either the Neo1973 or NeoFreerunner directory.

http://downloads.openmoko.org/distro/testing

====Unstable and Experimental Versions====

These are the lastest versions from svn.

Download from either the Neo1973 or NeoFreerunner directory.

http://downloads.openmoko.org/distro/unstable

http://downloads.openmoko.org/distro/experimental

====Older Versions====

The download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
Use the file appropriate to your device:

===Installation===
The installation should be flashing like (do it in DFU mode of NOR u-boot):
# dfu-util -a u-boot -R -D qi-s3<version>.udfu
depending on the file you downloaded. The file you use for flashing is depending on the hardware (see section 'Download'). In detail you have to go through the following procedures:

* Connect Freerunner (e.g GTA02 Hardware) with USB-cable
* download [[dfu-util]] via package manager (e.g. YAST with OpenSuse)
* start uBoot by pressing AUX and Power-On at the same time.
* download Qi image (e.g. for GTA02 which is 'qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu')
and start
# dfu-util -a u-boot -R -D qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu
See [[Flashing the Neo FreeRunner]] for more details on flashing your phone.

===Features===
* booting from primary SD partitions (1st, 2nd or 3rd) in /boot directory
* booting from NAND (compatible with U-Boot's dynparts scheme)
* configuration per rootfs, by files in /boot in the rootfs
* automatically choose correct kernel for device hardware so rootfs can be used on multiple device types
* automatically tell kernel correct root= for rootfs kernel image came from, simplifying update
* ext2/3 are supported
* symlinks are supported
* parses identity partition and appends kernel commandline with device identity information
* zero "environment" or private persistent state - operation is completely deterministic
* You can always boot from NOR menu http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash

===Use Case===
If you want to install [[Android]] on you OpenMoko you can use Qi. The [[Android on Freerunner]] kernel image can be more than 2MB in size. The UBoot environment that comes with your FreeRunner is only able to boot a kernel 2MB in size or less. Qi support kernel images greater than 2MB out of the box.

===Limitations===
* no DFU-Mode - USB is not initialized at all (but you can always boot from NOR http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash )
* no boot menu (but you can always boot from NOR http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash )
* FAT partitions are ignored

Both the lack of DFU and the boot menu are planned to be addressed by the backup / recovery rootfs.

FAT is not supported because it can't provide a rootfs, and Qi wants the kernel to come from the rootfs.

===Defaults===
If the kernel is found on uSD, Qi assumes the rootfs to be on the same partition as the kernel. In case of boot from NAND, it assumes that rootfs is also on NAND (just as u-boot does). See [[#/boot-Partition|below]] for help with an extra /boot-partition. The default rootdelay is 1 second.

===Files===
; /boot/uImage-GTA0[123].bin
: Kernel images, Qi will look for (can be in either uImage (u-boot image) or zImage format, file name should still be uImage-GTA0[123].bin)
; /boot/append-GTA0[123]
: Additional kernel arguments. All arguments should be on the first and the only line separated by spaces, for example: "<tt>loglevel=8 rootdelay=5 </tt>" . Make sure you have an extra space after the last argument (space is no longer needed if the version is from 31 Jan or older)!
; /boot/noboot-GTA0[123]
: make Qi skip this partition

===Speed up kernel resume for SHR===
Since SHR (and perhaps other distributions as well) ouput log messages during resume which slow down the resume process by ca. 3 seconds it make sense there to append the following settings to /boot/append-GTA0[123]:
: loglevel=1 quiet
The disadvantage of this speedup is that you won't see any lifesign of your phone until it starts the graphical user interface after adding these files, though.
===Boot Order===
[[image:Qi-drawings-bootsequence.png|frame|Qi GTA02 Booting order]]
# SD Partition 1
# SD Partition 2
# SD Partition 3
# NAND
# Memory Test

Qi will try to mount each SD partition as ext2 / 3, if that succeeds it will look for the kernel as /boot/uImage-GTA02.bin. If that is found, it'll be fetched, its CRC is checked and then it's booted into with a generated kernel commandline.

===Kernel Commandline Generation===
[[image:Qi-commandline-composition.png‎|frame|Qi commandline composition]] Because Qi has no private stored state, it infers and composes a suitable kernel commandline on each boot.

One of its tasks is to scan NAND memory using the U-Boot dynparts rules to determine the start offset of the NAND partitions on this device, from that it forms the mtdparts kernel parameter that sets Linux's view of NAND partitioning.

The other thing it does is mount the "identity" partition and get from there the globally unique MAC address for the USB over Ethernet function instead of the random one that is otherwise used (If this doesn't work (like with a GTA01) you may use kernel-commandline parameters g_ether.dev_addr= and g_ether.host_addr= for the mac in device and host mode of the usb-ether module).

===LED and Vibrator Signals===
* AUX LED is turned on either on:
** Successful partition mount
** Successful kernel pull
** Successful initramfs pull
* AUX LED is turned off and vibrator runs briefly either on:
** Fail of kernel pull
** Fail of initramfs pull
** Fail of mount partition
** Skipping of current boot possibility
* AUX LED is turned off either on:
** Start of the kernel
** Start of the mem test
** Start of the kernel pull
** Start of the initramfs pull
* One Blue shine every ~10 second: did not find any valid kernel to boot
* About four RED shines per second: kernel panic.

===Booting===
A short press on the power button is enough to make Qi start booting. In a few seconds the backlight will be lit, but the kernel will not spew any console messages unless something is wrong. It may take up to 2 minutes (depends on distribution) until X is started during which there will be no visual feedback. Please be patient.

You can force debug messages on the LCM console by holding in the power button before Linux starts.

===Choosing a Kernel===
If a user presses the AUX button after successful partition mount and
before start of the kernel pull (that is, while the red LED is on),
this boot possibility is skipped (and GTA02 owners can feel
vibration).

On versions newer than Jan 18 if a user holds the POWER button just before start of the kernel,
debugging parameters are added to the kernel command line and a lot of information is output to the screen.

===Boot Menu===
Qi's concept is to leave everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. This should rather be implemented by a minimal Kernel, initramfs and menu system. It may be more comfortable for some users and may get them to switch from uboot to Qi. This does not exist yet (it's already implemented for some Angstrom-supported devices and for Zaurus, so porting should be relatively easy).

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

===README===
The latest README file can be found in the git as well:http://git.openmoko.org/?p=qi.git;a=blob;f=README;hb=HEAD

==Tips, Tricks, Tweaks==
===General troubleshooting===
Qi does not bring up the LCD backlight. If the backlight is lit, it means you have succeeded to boot into Linux.

If nothing else is happening or there is a panic, enable debugging messages as described below.

===Enabling console messages===

You can just hold in the power button, this automatically appends verbose debugging to the kernel commandline (loglevel=8).

If you always want verbose "dmesg" type debugging messages, you can do it like this:

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
loglevel=8
and you'll see the messages on boot. If it's NAND right now you need to edit the default commandline in Qi for gta02.

===/boot-Partition===
If you have a separate partition for /boot, so that your kernel and rootfs are not in fact on the same partition, you will need to append a root= entry on the kernel commandline to override the default action of trying to use the partition where the kernel came from as the rootfs.

Add this in /boot/append-GTA0[123]:
root=/dev/mmcblk0p2
for a rootfs on the second partition.

Note that a default Debian installation puts the kernel straight in the root of /dev/mmcblk0p1, not in a boot subdirectory, expecting u-boot to mount it as /boot. In order for Qi to recognise this, create a boot subdirectory with a symlink to the kernel.

===SD Initialisation===
If you don't specify loglevel=8 in append-GTAXX, and booting fails with a "VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)", the SD card needs a little bit more time to initialise.

Put a "rootdelay=5" in append-GTAXX like so:
rootdelay=5

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

[[Category:System Developers]]

User talk:Emdete

2009-05-16T21:48:12Z

Emdete: Replacing page with 'See my project http://pyneo.org/'

See my project http://pyneo.org/

Talk:Qi

2009-02-26T09:29:47Z

Emdete: /* simplify nand partitions */

== will it boot jffs2 on flash ? ==
--kd8ikt

'''Install Qi on you NAND flash. You can still boot whatever distro you've got on internal flash using the NOR bootloader.'''[http://wiki.openmoko.org/wiki/Android_on_Freerunner from here]
So I think it should still be able to do jffs2, but I'm not sure. [[User:Bram|Bram]]

== dmesg output ==

With ''`uname -a`'' = ''"Linux om-gta02 2.6.24 #1 PREEMPT Tue Dec 2 15:02:59 CST 2008 armv4tl unknown"'', dmesg outputs '''s3c2440''' on GTA02 Revision: 0360.
'''qi-s3c2442-master''' works fine on it.

== post-init booting stuff is faster? ==

21 October 2008, [[User:MinhHaDuong|MinhHaDuong]] wrote:
:"Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot"
How many times was this experiment done, by how many different people? For empirical stuff, more data is invariably better. [[User:Sm|Sm]] 22:04, 7 January 2009 (UTC)

== large uSD cards support ==

How large does "large uSD cards support" mean? Is there any accurate information available on this?

== Choosing a Kernel, difficult as described ==

What I found difficult was "If a user presses the AUX button after successful partition mount and before start of the kernel pull (that is, while the red LED is on), this boot possibility is skipped (and GTA02 owners can feel vibration)".
Using Qi qi-s3c2442-master-hist_1665e43677c005a8.udfu (downloaded today Feb22) and with only one usable partition on the card, the red led flashed very quickly twice, and slower once. No amount of pressing AUX during the led flashes enabled the defective item on the partition to be bypassed. However pressing AUX as soon as I was physically able after pressing POW to start worked. It was in the time before any flashes, and I held it till after the 3 flashes. At that point I saw a familiar response, Great Relief. (Clare).

== Simplify nand partitions? ==

With Qi all the different partitions in nand are not needed, could these be put together to allow one larger rootfs? There is config, kernel and splash which could be merged into the rootfs partition. It should also be possible to shrink the the partition of u-boot. If this is a suitable suggestion is someone able to write a short HOWTO how to accomplish that for GTA01 and GTA02?

Talk:Qi

2009-02-26T09:26:08Z

Emdete: add question on nand partitions

== will it boot jffs2 on flash ? ==
--kd8ikt

'''Install Qi on you NAND flash. You can still boot whatever distro you've got on internal flash using the NOR bootloader.'''[http://wiki.openmoko.org/wiki/Android_on_Freerunner from here]
So I think it should still be able to do jffs2, but I'm not sure. [[User:Bram|Bram]]

== dmesg output ==

With ''`uname -a`'' = ''"Linux om-gta02 2.6.24 #1 PREEMPT Tue Dec 2 15:02:59 CST 2008 armv4tl unknown"'', dmesg outputs '''s3c2440''' on GTA02 Revision: 0360.
'''qi-s3c2442-master''' works fine on it.

== post-init booting stuff is faster? ==

21 October 2008, [[User:MinhHaDuong|MinhHaDuong]] wrote:
:"Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot"
How many times was this experiment done, by how many different people? For empirical stuff, more data is invariably better. [[User:Sm|Sm]] 22:04, 7 January 2009 (UTC)

== large uSD cards support ==

How large does "large uSD cards support" mean? Is there any accurate information available on this?

== Choosing a Kernel, difficult as described ==

What I found difficult was "If a user presses the AUX button after successful partition mount and before start of the kernel pull (that is, while the red LED is on), this boot possibility is skipped (and GTA02 owners can feel vibration)".
Using Qi qi-s3c2442-master-hist_1665e43677c005a8.udfu (downloaded today Feb22) and with only one usable partition on the card, the red led flashed very quickly twice, and slower once. No amount of pressing AUX during the led flashes enabled the defective item on the partition to be bypassed. However pressing AUX as soon as I was physically able after pressing POW to start worked. It was in the time before any flashes, and I held it till after the 3 flashes. At that point I saw a familiar response, Great Relief. (Clare).

== simplify nand partitions ==

Qi makes all the partitions in nand useless, could these be put together to allow one larger rootfs? There is config, kernel and splash which could be merged into the rootfs partition. It should also be possible to shrink the the partition of u-boot. If this is a suitable suggestion is someone able to write a short HOWTO how to accomplish that for GTA01 and GTA02?

User:Emdete

2009-02-17T17:13:37Z

Emdete: Replacing page with '== pyneo.org == all documentation about my initiatives with the Neo1973 and the Freerunner are collected under http://pyneo.org/ .'

== pyneo.org ==

all documentation about my initiatives with the Neo1973 and the Freerunner are collected under http://pyneo.org/ .

Distributions

2008-12-18T20:04:26Z

Emdete: /* Others / unreleased */

{{Languages|Distributions}}

{|align=right
|__TOC__
|}

= About distributions =
Openmoko distributions are designed to run on various mobile devices, with the primary aim of supporting Openmoko Inc.'s [[GTA01:Neo 1973|Neo 1973]] and [[Neo FreeRunner]] phones. They are GNU/Linux distributions -- complete operating systems with more or less user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed.

While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below).

For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].

=== Which distribution should I use ?===
* Most new users find [[FDOM]] the most comprehensive and functional distribution.
* If you want "just a phone", try [[Qtopia]].
* If you want to develop anything that last, your platform is [[FSO]] (and the choice between EFL, GTK+, Qt, Java, Python or whatever is open).
* [[SHR]], [[Debian]], [[Gentoo]] and [[Android]] are for people who do not need to ask which distribution they should use.
* Tracking the "base image" by updating daily from testing/unstable is a different game either.

===Status as of November 9th, 2008 ===
* The phones ship with [[Om 2007.2]]. It is not supported by Openmoko Inc. anymore. But community developpers continue to work on its phone stack in the [[SHR]] project.
* The branch currently supported by Openmoko Inc. is [[Om 2008.9 Update]], which is a minor upgrade of [[Om 2008.8]] (formerly named ASU). Based on that, the community made the [[FDOM]] distribution by adding lots of fixes and applications to it.
* The trunk tip is a "base image" on which the next major release should be based. This next release can be previewed by installing milestones of the [[FSO]] - Free Smartphone.Org project. The [[Debian]] packaging team also track that branch.
* The FreeRunner is a reference platform for TrollTech's Qt Extended (formerly [[Qtopia]]) distribution.
* The Android port is work-in-progress.

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2008.9 Update]]
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[OpenmokoFramework|FSO]]
* Community
** [[SHR]]
** [[FDOM]]
* Other
** [[Qtopia]]
** [[Debian]]
** [[Gentoo]]
** [[Android]]
** [[Hackable:1]]
</div>
|-
|}

=== Warnings ===

* Stable in the FreeRunner world does not mean the same thing as stable in Debian world.
* Most distributions use the same bootloader, kernel, drivers and hardware. Therefore, the same low level bugs are commonly found in all distributions. The latest and greatest software usually has most bug fixes, plus a whole set of new fresh bugs.
* Most of these distributions also have package repositories. It is a BAD idea to feed from another distribution's repository.
* Upgrade path between these distributions are mostly not tested, thus updating by changing the feeds will most likely end in broken packages or even an unbootable system. It is advisable to reflash the whole filesystem with [[dfu-util]] to switch between the different distributions, with the reminder that a dual-boot setup (e.g. via sdcard or NFS) can be used.

= Openmoko Inc. driven release targets =

These different 'release targets' are built out of different branches of the [[OpenEmbedded]] metadistribution source tree.

=== Om 2008.9 ===

The Om 2008.9 Update is the first point release after the initial Om 2008.8 release. Openmoko recommends that all existing installations of Om 2008.8 should be updated to that version. Quality-wise, we are still far from the goal, but this version includes general stability enhancing operating system improvements and a new splash screen. No applications were added or removed. Users with basic telephony needs will find it tolerable as an everyday phone.

{{Main|Om 2008.9 Update}}

=== Om 2008.8 ===

Om 2008.8 was released on August 8, 2008, to replace 2007.2. Prior to that, its codename was ASU (April/August Software Update). This is still the name of the branch in the version control system. This distribution integrates the [http://trolltech.com/products/qtopia Qtopia] phone stack with a set of new Openmoko applications based on the Enlightenment Foundation Libraries. Qtopia being a more mature product than the GNOME Mobile stack, the standard phone applications (dialer, contacts, calculator, calendar) work better than in 2007.2. The Qtopia used in 2008.8 was ported to run on X11, contrary to standard Qtopia which uses the framebuffer. This allows non-Qt applications to safely share the screen with Qt applications. This is a .0 release, many unresolved issues remain in the lower layers (kernel power management, sound, wifi drivers...).

{{Main|Om2008.8}}

=== Om 2007.2 ===

[[Om 2007.2]] is the base-system which is installed on FreeRunner when it leaves the factory. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand. There is a community effort (see [[SHR]]) to port the GTK based telephony applications to the future middleware from [[FSO]].

{{Main|Om 2007.2}}

=== FSO Milestone IV ===

FSO is an abbreviation for FreeSmartphone.Org. Openmoko is working on a stable system services back-end. Focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. The framework will be used in forthcoming Openmoko distributions. FSO is all about middleware, but if one stacks a bootloader+kernel under it and telephony applications on top, one gets a functional distribution. These are made available as FSO-image milestones. Openmoko Framework Image milestone IV was released on November 11th, 2008 and named 'Homework'. People report that despite its infancy, the phone server part in FSO is already more solid than anywhere else. The kernel under it is a Linux 2.6.24 with modules packaged separately. The telephony application on top of it is Zhone. This is a basic Python dialer/homescreen designed as scaffolding to test the FSO functionalities (even if Zhone is pretty, code path coverage is more critical to it than user-friendliness).

{{Main|FSO}}

= Openmoko Community driven release targets =

=== SHR - Stable Hybrid Release ===

SHR is a community driven distribution. It contains some basic GTK+ based applications which make use of the FSO. There currently is a EFL (with elementary) dialer, messages and contacts application programmed in C. As of November 9th, 2008, there is no stable release of this distribution yet, as the SHR team doesn't feel it to be good enough. You can find images though on the [http://shr.bearstech.com/shr-testing SHR buildhost].

{{Main|Stable Hybrid Release}}

=== FDOM (FAT and Dirty Openmoko) ===

[[FDOM]] is a distribution based on Openmoko's currently supported image, updated with many ready-to-use applications and with fixes posted in the mailing lists. A combination of applications (everything goes) 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.

{{Main|FDOM}}

== Non-Openmoko distributions ==

These are not Openmoko (and OE) based distributions. These are alternatives you can run on your Openmoko phones.

=== Qt Extended ===

The Qt Extended distribution was formerly known as Qtopia up to version 4.3.x included. It comes from [http://www.trolltech.com Trolltech], a Nokia company, the makers of the Qt cross-platform application framework. This distribution aims to provide a ready-to-use image for Openmoko devices. It features a noticeably robust telephony stack. Recent release 4.4.2 also sports a webkit-based web browser and Gtalk support.

{{Main|Qtopia / Qt Extended on FreeRunner}}

=== Debian ===

Debian is "the universal operating system". It comes with thousands and thousands of packages (most of them designed for desktops or servers so far). So in the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team, this is not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the Stable Hybrid Release software in our archive. So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)

{{Main|Debian}}

=== Gentoo ===

Gentoo is all about choices. When installing Gentoo, this is made clear to you several times -- you can choose how much you want to compile yourself, how to install Gentoo, what system logger you want, etc. Gentoo is a fast, modern metadistribution with a clean and flexible design. Gentoo is built around free software and doesn't hide from its users what is beneath the hood. Portage, the package maintenance system which Gentoo uses, is written in Python, meaning you can easily view and modify the source code. Gentoo's packaging system uses source code (although support for precompiled packages is included too) and configuring Gentoo happens through regular textfiles. In other words, openness everywhere.

{{Main|Gentoo}}

=== Android ===

Android is a mobile phone platform by Google, and later the Open Handset Alliance (OHA). Openmoko is fully supporting Android running on the Freerunner. Details along with images are being constructed at the moment. Visit the user web page for [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] for further details. And you can download kernel and image [http://people.openmoko.org/sean_mcneil/ here].

{{Main|Android}}

=== Hackable:1===
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and implements the GNOME mobile platform.
{{Main|Hackable:1}}

=== Others / unreleased ===

* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovating yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Mickey Lauer used most of the technics & architecture, library & language choices of pyneo in fso. ''Status: still active, ask around on #neo1973-germany ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: it does not have its own kernel so a Freerunner distribution waits for a solid basis and an arm-linux-gnueabi toolchain that runs natively on Mac OS X is currently lacking.''

= Features by distribution/release target =

Generally, distributions can differ on one or more of the following components:
* The bootsplash screen image. This is purely decorative.
* The bootloader. Theoretically, any version of ''uboot'' could be used with any distribution. In the future ''Qi'' will replace ''uboot''.
* The kernel. GNU/Linux kernels versions 2.6.24, 2.6.26 or 2.6.28 can be found. Some have modules compiled in, others have modules compiled separately. If compiled separately, modules can be distributed in the same package file as the kernel or separately.
* Middleware: daemons to handle GSM calls or GPS, sound system, personal information storage and so on. Qt and Android have their own subsystems, FreeSmartphone.Org (FSO) is working towards a standard-based Free Software one.
* Display driver. The original ''Qt Extended'' uses the framebuffer, most other distributions today use ''X11''.
* Libraries and application framework (widget toolkit and and graphical environment) : EFL, Qt, Gtk+ or Java ?
* Basic telephony applications: voice calls, SMS, alarm clock...
* Smartphone applications: GPS, media player, simple games, web browser...
* Open source applications: more games, scientific, you name it...

=== Hardware Support ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=9%|Om 2008.9 !! width=9%|Om 2008.8 !! width=9%|Om 2007.2 !! width=9%|FSO !! width=9%|SHR !! width=9%|FDOM !! width=9%|Qt Extended !! width=9%|Debian !! width=9%|Gentoo !! width=9%|Android
|-
| GTA01 || {{No}} || ?? || ?? || ?? || {{Yes}} || ?? || {{Yes}} || {{Yes}} || ?? || ??
|-
| GTA02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
|}

=== Connectivity ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=9%|Om 2008.9 !! width=9%|Om 2008.8 !! width=9%|Om 2007.2 !! width=9%|FSO !! width=9%|SHR !! width=9%|FDOM !! width=9%|Qt Extended !! width=9%|Debian !! width=9%|Gentoo !! width=9%|Android
|-
| Telephony || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| SMS || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| [[GPRS]] || ?? || Not through UI || Not through UI|| Not through UI || Not through UI || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| [[WiFi]] || {{Yes}} || {{Yes}} (*) || {{Yes}} || Not through UI || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ?? || {{Yes}}
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || {{Yes}} || {{Yes}} (1) || {{Yes}} || ?? || {{no}}
|-
| Bluetooth || ?? || {{Yes}} || {{Yes}} || {{No}} || ?? || {{Yes}} || {{Yes}} || {{Yes}} || ?? || {{Yes}}
|-
| GPS (1) || ?? || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
|}

=== Power ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=9%|Om 2008.9 !! width=9%|Om 2008.8 !! width=9%|Om 2007.2 !! width=9%|FSO !! width=9%|SHR !! width=9%|FDOM !! width=9%|Qt Extended !! width=9%|Debian !! width=9%|Gentoo !! width=9%|Android
|-
| Suspend || ?? || ?? || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || ?? || ?? || ??
|-
| Resumes on Event || ?? || ?? || ?? || ?? || ?? || {{Yes}} || {{No}} || ?? || ?? || ??
|-
| Functions after Resume || ?? || ?? || ?? || ?? || {{Yes}} || {{No}} || {{No}} ||?? || ?? || ??
|-
|}

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=9%|Om 2008.9 !! width=9%|Om2008.8 !! width=9%|2007.2 !! width=9%|FSO !! width=9%|SHR !! width=9%|FDOM !! width=9%|Qt Extended !! width=9%|Debian !! width=9%|Gentoo !! width=9%|Android
|-
| Stylus friendly || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ?? || {{Yes}}
|-
| Finger friendly || ?? || Partially || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || ?? || {{Yes}}
|-
| Accelerometer || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{Yes}} [[Gestures|(1)]] || {{No}} || {{No}} || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

=== Applications ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=9%|Om 2008.9 !! width=9%|Om2008.8 !! width=9%|2007.2 !! width=9%|FSO !! width=9%|SHR !! width=9%|FDOM !! width=9%|Qt Extended !! width=9%|Debian !! width=9%|Gentoo !! width=9%|Android
|-
| Terminal || ?? || {{Yes}} (1) || Basic (2) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ?? || ??
|-
| PIM || ?? || {{Yes}} || {{Yes}} || {{No}} || N/A || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || ??
|-
| Phonebook || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Dialer || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Web Browser || ?? || {{Yes}} (1) || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Mail Client || ?? || {{Yes}} || ? || ? || ? || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| XMPP Client || ?? || {{Yes}} [[Instant Messaging|(1)]] || {{Yes}} (1) || ? || ? || {{Yes}} || {{Yes}} || {{Yes}} (1) || || ??
|-
| Media Player || ?? || {{Yes}} (1) || {{Yes}} || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
|}

=== Toolkits / Runtimes ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"
! width=10%| !! width=9%|Om 2008.9 !! width=9%|Om2008.8 !! width=9%|2007.2 !! width=9%|FSO !! width=9%|SHR !! width=9%|FDOM !! width=9%|Qt Extended !! width=9%|Debian !! width=9%|Gentoo !! width=9%|Android
|-
| GTK+ || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || ?? || ??
|-
| Qt/Qt Extended || ?? || {{Yes}} || {{No}} || {{Yes}} ? || {{Yes}}? || {{Yes}} || {{Yes}} || {{Yes}} || ?? || ??
|-
| Middleware || ?? || qtopia-x11 || gsmd/neod || FSO || FSO || qtopia-x11 || Qt Extended || FSO || ?? || ??
|-
| [[Java]] || ?? || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes}} || ?? || {{Yes|CacaoVM, JamVM}} || ?? || ??
|-
| [[Python]] || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ?? || ??
|-
| [[Mono]] || ?? || {{Yes}} (1) || {{Yes}} (1) || ?? || {{no}} || ?? || ?? || {{Yes}} (1) || ?? || ??
|}

=== Images ===
Latest and stable combinations for Neo FreeRunner gta02
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"
| || OM || FDOM || Qt Extended || Android
|-
| current bootloader || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/daily/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/daily/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/daily/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] ||
|-
| future bootloader || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu ||
|-
| splash || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz ||
|-
| kernel || [[Linux]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest uImage.bin || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest uImage-gta02-mwester-stable.bin or from [http://downloads.tuxfamily.org/3v1deb/openmoko/ treviño] latest uImage-gta02-stable-3v1n0.bin || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest uImage-gta02-mwester-stable.bin or from [http://downloads.tuxfamily.org/3v1deb/openmoko/ treviño] latest uImage-gta02-stable-3v1n0.bin || [[Linux]] from [http://wiki.openmoko.org/wiki/User:Seanmcneil3 McNiel] version [http://people.openmoko.org/sean_mcneil/uImage-android 2.6.26-android]
|-
| modules || ? || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz ||
|-
| rootfs || [[Main_Page|OM]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest rootfs.jffs2 || [[FDOM]] from [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/ TuxBrain] version [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/Fat_and_Dirty_OM.200809_20081023.rootfs.jff2 200809_20081023] || [[Qtopia_/_Qt_Extended_on_FreeRunner|QtExtended]] from [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 TrollTech] latest qtextended-gta02-flash.tgz or from [http://other.lastnetwork.net/OpenMoko/ Hypnotize] latest qtextended-gta02-rootfs-release-working.jffs2 || [[Android]] from [http://wiki.openmoko.org/wiki/User:Seanmcneil3 McNiel] version [http://people.openmoko.org/sean_mcneil/androidfs.jffs2 android]
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters. [[Switching_Keyboards#Matchbox_keyboard|Various fixes available.]]

(*) unstable

==Quick download page==

[[Download]]

== See also ==

* Mickey Lauer's post "[http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!]" describes the differences between distributions 2007.2, ASU and FSO.

[[Category:Distributions|*]]

Tichy

2008-09-03T10:37:32Z

Emdete: fixed typo "pygame_s_"

{{Languages|Tichy}}

<pre>
_ _
_ (_) | |
_| |_ _ ____| |__ _ _
(_ _) |/ ___) _ \| | | | A Python Applets Manager
| |_| ( (___| | | | |_| |
\__)_|\____)_| |_|\__ | For Openmoko
(____/
</pre>

[[Image:Tichy-main.png|thumb|tichy main window]]
[[Image:Tichy-drawing.png|thumb|tichy drawing app]]
[[Image:Tichy-style.png|thumb|tichy style app]]
[[Image:Tichy-Media.png|thumb|tichy freedesktop app]]
[[Image:Tichy-Keyboard.png|thumb|tichy keyboard app]]

== About ==
Tichy is a python applets manager for embedded devices.

The goal of the project is to make it easy to write many kind of applications for openmoko using the python language.

Tichy provides the following things :
* Graphics User Interface widgets
* Services registering and Requesting (for example an application that wants to send a message will request for an application implementing the message sending service)
* Tasklets system (This allow to write callback waiting process as if they were threads)
* Abstraction of Item / View
* A plug in system that make it easy to add new functionalities / applets to tichy

== How to write an applets / plug-ins for tichy ? ==
Unfortunately There is currently no documentation.

Fortunately it is very easy to do. If you want to write a new applet, you just need to create a new directory in tichy/test/plugins/apps/. You can have a look at the other plug-ins to get an idea of how to do it. A basic app look like this :

<pre>
import tichy
import tichy.gui as gui
import tichy.item as item
from tichy.application import Application

class MyApp(Application):
name = "My Application"
icon = 'icon.png' # to be found in the app directory

def run(self, parent):
w = gui.Window(parent, modal = True) # We run into a new modal window
# Create a new frame with a "back" button on top
frame = gui.ApplicationFrame(w, self, back_button=True)

# This box is used to store the widgets
box = gui.Box(frame, axis=1)

# Create a text item
text = item.Text('click to edit', editable = True)
# Put a view of the item on the screen
text.view(box)

# Add a button
button = gui.Button(box)
gui.Label(button, "click me")

def on_click(b):
# "yield" means "block until the tasklet returns"
yield gui.Message(w, you just clicked the button)
button.connect('clicked', on_click)

yield Wait(frame, 'back') # Wait until the back button is clicked
w.close() # Don't forget to close the window
</pre>

== Authors ==
* Guillaume "Charlie" Chereau, main developer
* Michael "Goodwill"

== Sources ==
The sources can be found from svn repository on project.openmoko :
svn checkout svn://svn.projects.openmoko.org/svnroot/tichy

== Running on the desktop ==
Thanks to the service system, that allows to provide several version of the same service, Tichy can run as well on a desktop computer as on the neo. When run on a desktop, tichy will simulate phone functionalities, when run on the neo, it will use the [[OpenmokoFramework | Framework]].

To run it on the desktop, make sure you have python-pygames installed
sudo apt-get install python-pygame

Then just download the sources, then go into test, and run
./tichy

== Running on neo ==
You will need to compile some files, see the README for more information on how to do it.

== Dependencies ==
You need python 2.5 and some libraries installed :
* python-pygame
* python-dbus
* python-yaml
* python-gst
* python-gobject

== ipkg package ==
We don't have a package for tichy yet...

[[Category:Applications]]
[[Category:Guides]]

Talk:MokoMakefile

2008-08-05T10:52:50Z

Emdete: /* Ubuntu Edgy: Update git-1.4.x to 1.5.x! */

== MokoMakefile won't work on Ubuntu Hardy Heron ==
Hello, there!

Since my upgrade to Hardy Heron MokoMakefile seems to be broken on my ubuntu box. I already tried several times to download a new Makefile into a fresh directory - without success. What I get is always:

:~/moko$ make image
( cd build && . ../setup-env && \
( bitbake openmoko-devel-image u-boot-openmoko ) )
ERROR: Openembedded's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

/proc/sys/vm/mmap_min_addr is not 0. This will cause problems with qemu so please fix the value (as root).

make: *** [openmoko-devel-image] Error 1

For another report on this problem see also: http://lists.openmoko.org/pipermail/community/2008-May/017545.html

When trying to compile the april software update (ASU) this error doesn't occour, though.

=== solution ===

<pre>
$ sudoedit /etc/sysctl.conf
</pre>

And add 'vm.mmap_min_addr = 0' (without quotes) to that file.

== The paths that are mentioned on this page are partially wrong ==
I am not sure enough what the paths should be, but - two things have changed since the section "developing with mokomakefile/How to add your own shiny new application" of this page was created:
- The path where the packages are kept, and
- Where to add the information that we have added a new package.

== Update git to 1.5! ==

Version git-1.4 does not work, check your version with the command

<pre>
git --version
</pre>

and install at least git version 1.5 if not already present.

== Fails on a 32bit machine - try again without ccache? ==

<pre>/bin/sh ./libtool --mode=compile ccache gcc -DHAVE_CONFIG_H -I.... -W... -O2 -c -o libbfd.lo build/tmp/work/armv4t-linux/binutils-cross-2.17-r0/binutils-2.17/bfd/libbfd.c
ccache gcc -DHAVE_CONFIG_H -I... -W... -O2 -c /usr/local/oe/build/tmp/work/armv4t-linux/binutils-cross-2.17-r0/binutils-2.17/bfd/libbfd.c -o t shift count >= width of type
make[5]: *** [libbfd.lo] Error 1
</pre>

Any insight here? --[[User:Adam|Adam]] 23:10, 15 May 2007 (CEST)
: Try without ccache (did you get it compiled meanwhile or can we remove this?) --[[User:BernhardKaindl|BernhardKaindl]] 23:05, 19 September 2007 (CEST)

== Facing Problems with ogg libraries ==
just get the path and delete the .bb file that causes the problem
== Building on Fedora Core 6 ==

Install stuff needed for OpenMoko:
# yum install python m4 make wget curl ftp cvs monotone subversion \
tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html \
diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds \
docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git \
quilt groff linuxdoc-tools patch compat-gcc-34 lynx netpbm
(notice ''compat-gcc-34'' wich was needed for FC6 (gcc 4 installed), and ''lynx'' which is needed by ''qemu'' (no fallback to ''wget'', ''curl'', or ''links'' at the moment and no check for it, resulting in strange "sleep" errors when trying to build without ''lynx'').

Build it:
$ make setup
$ make openmoko-devel-image
$ unset LD_LIBRARY_PATH
$ make update-makefile && make update && make setup && make openmoko-devel-image

I have also done a
$ unset LD_LIBRARY_PATH; make update-makefile && nice make update && nice make setup && nice make all
(This takes several hours)

Build qemu:
$ make qemu

Run it:
# echo 1024 > /proc/sys/dev/rtc/max-user-freq
$ make run-qemu
This will bring up the OpenMoko :) Use SPACE for AUX and ENTER for POWER.
Not quite the same as holding a Neo1973 in your hands I would guess, but this is the best we can do for now. Thanks!

== Building on Ubuntu Feisty ==

MokoMakefile requires more than 512 MB of RAM + Swap space (around 1GB?).

If you need swap, please '''check that its size under Feisty is not null'''!

[https://bugs.launchpad.net/ubuntu/+bug/105490 Bug #105490] describes the current issue and offers a workaround (23 Jul 07).

== Fails trying to build bluez-utils ==
on Gentoo Linux, it fails compiling bluez-utils (I've tried also "make clean-package-bluez-utils" before the following command)

do a "make build-package-libusb; make clean-package-bluez-utils" and it should continue (the bluez-utils .bb is missing the libusb dependency)

== openSUSE 10.1 and 10.2 workarounds ==

ltrace package fails to build with error:
<pre>
...
checking for pid_t... yes
checking for getopt... yes
checking for getopt_long... yes
checking gelf.h usability... no
checking gelf.h presence... no
checking for gelf.h... no
configure: error: ***** gelf.h not found *****
FATAL: oe_runconf failed
</pre>

'''FIX: '''
edit ''/home/moko/build/tmp/work/armv4t-linux/ltrace-0.4-r0/ltrace-0.4/configure.ac''
at line 44: remove the following block:
<pre>
for path in /usr/include/elfutils /usr/local/include/elfutils \
/usr/include/libelf /usr/local/include/libelf; do
if test -f ${path}/gelf.h; then
CPPFLAGS="$CPPFLAGS -I ${path}"
fi
done
</pre>
( it adds /usr/include/elfutils to path, which causes cross-compile badness error )

=== QEMU build fails to compile USB code ===
<pre>
/usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user' declared void
/usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c: In function `usb_host_handle_control':
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:103: error: invalid application of `sizeof' to incomplete type `usbdevfs_ctrltran
sfer'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c: In function `usb_host_handle_data':
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:120: error: storage size of 'bt' isn't known
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:132: error: invalid application of `sizeof' to incomplete type `usbdevfs_bulktran
sfer'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:120: warning: unused variable `bt'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c: In function `usb_host_device_open':
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:199: error: storage size of 'ctrl' isn't known
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:202: error: invalid application of `sizeof' to incomplete type `usbdevfs_ioctl'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:199: warning: unused variable `ctrl'
make[2]: *** [usb-linux.o] Error 1
</pre>

'''FIX: '''
edit ''/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c''
at line 29 add the following (before ''#include <linux/usbdevice_fs.h>'')
<pre>
#include <linux/compiler.h>
</pre>
hint: there is a copy of the file in ''/home/moko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/usb-linux.c''

''see: http://osdir.com/ml/emulators.kvm.devel/2007-01/msg00101.html''

== Cannot satisfy fstests ==
<pre>
make openmoko-devel-image
...
| Collected errors:
| ERROR: Cannot satisfy the following dependencies for task-openmoko-debug:
| fstests
NOTE: Task failed: /no-backup/Moko/build/tmp/work/fic-gta01-linux/openmoko-devel-image-1.0-r0/temp/log.do_rootfs.25036
NOTE: package openmoko-devel-image-1.0-r0: task do_rootfs: failed
ERROR: TaskFailed event exception, aborting
</pre>
Failed on debian etch 2007-07-20
Solution from mailing list post from hardskinone, report of an irc chat
<pre>
I got help in IRC channel. I do following steps
* remove fstest from oe/packages/tasks/task-openmoko.bb ,
* increase PR field by one
* make openmoko-devel-image
</pre>

== conflicting types for 'futimens' ==

if you encounter the following error:

| In file included from utimecmp.c:40:
| utimens.h:2: error: conflicting types for 'futimens'
| /usr/include/sys/stat.h:370: error: previous declaration of 'futimens' was here

a patch is needed because your glibc is too new. grab & enable the patch as follows

cd openembedded/packages/coreutils
mv coreutils_5.3.0.bb coreutils_5.3.0.orig
wget http://www.openembedded.org/repo/org.openembedded.dev/packages/coreutils/coreutils_5.3.0.bb
cd -
cd openembedded/packages/coreutils/coreutils-5.3.0
wget http://www.openembedded.org/repo/org.openembedded.dev/packages/coreutils/coreutils-5.3.0/futimens.patch
cd -

== Workaround for problems compiling mtd-utils ==

Change the line on <code>openembedded/packages/mtd/mtd-utils_1.0.0+git.bb</code> which reads:

SRC_URI = "git://git.infradead.org/mtd-utils.git;protocol=git;tag=master \

to:

SRC_URI = "git://git.infradead.org/mtd-utils.git;protocol=git;tag=a6fa706fe9e7696b4b2045edf9698c3bac07e3e3 \

which forces the recipe to use an older revision (the one which worked last time I built the image on my computer).

Be sure to remember to undo the change later, or else you will not get any new changes to that package. --[[User:CesarB|CesarB]] 04:48, 25 July 2007 (CEST)

Note: these patches should be updated - the lzo patch is included in the current version, so backing off to the previous version and repatching seems silly. I was able to make it through this part of the build by applying the remaining patches manually. --[[User:Mellon|Ted Lemon]] 15:44, 29 July 2007 (CDT)

== Monotone segfaulting on Ubuntu Feisty Fawn/PPC ==
If you are running Ubuntu Feisty Fawn on a PowerPC computer you will experience problems running monotone. To fix this issue you need to install monotone as well as the libboost packages from Gutsy. The easiest way to accomplish this is to add the gutsy repositories to your sources.list
and change the preferences to look like this:

Package: *
Pin: release a=feisty
Pin-Priority: 700

Package: *
Pin: release a=gutsy
Pin-Priority: -100

Package: libc6 libc6-dev tzdata util-linux libgcc1 libstdc++6 monotone
Pin: release a=gutsy
Pin-Priority: 800

Package: libboost-*
Pin: release a=gutsy
Pin-Priority: 800

After doing this install monotone in this way:
apt-get -t gutsy install monotone.
That should install monotone 0.35 with updated (and working) boost libraries.

== Fails on ncurses install in Fedora 7 with a "tic -x" message ==
Adjust the following command to your system, then run it:
export LD_LIBRARY_PATH=/home/moko/build/tmp/work/x86_64-linux/ncurses-native-5.4-r8/ncurses-5.4/lib
Then start make again and it should pick up where it left off.

You can get a list of potential paths to use with the following command from you main moko directory:
find . | grep libncurses

The basic problem is that it is linking against your main system libraries instead of the OpenEmbedded ones.

There's probably a cleaner way of handling this - please update this entry if you know it.

This has been fixed in Openembedded, see [http://bugs.openembedded.org/show_bug.cgi?id=2554 Openembedded Bug #2554] for further details.

== uboot-gta01 fails to build ==
Changes in the GIT of U-Boot make the OpenMoko patches unapplyable. For the use of Revision ''cc3023b9f95d7ac959a764471a65001062aecf41'' and everything will be fine for now.

== Perl fails to build ==
After following every bit of advice I can find to 'make clean' and nuke the perl build directories, every build comes up with:

| make[1]: Entering directory `/src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/perl-5.8.7'
| make[1]: *** No rule to make target `<command-line>', needed by `miniperlmain.o'. Stop.
| make[1]: Leaving directory `/src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/perl-5.8.7'
| FATAL: oe_runmake failed
NOTE: Task failed: /src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/temp/log.do_compile.19531
NOTE: package perl-native-5.8.7-r3: task do_compile: failed

Solution turned out to be editing
/src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/perl-5.8.7/makedepend.SH and at line 169 change the regexp to eat references to "<command.line>" to catch what was leaking through.

== glibc fails to build ==
If you see an error like

<pre>

NOTE: package glibc-2.6.1: started
NOTE: package glibc-2.6.1-r10: task do_configure: started
ERROR: function do_configure failed
ERROR: log data follows (/home/alex/moko/build/tmp/work/armv4t-angstrom-linux-gn
ueabi/glibc-2.6.1-r10/temp/log.do_configure.11446)
| NOTE: Running /home/alex/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/gli
bc-2.6.1-r10/glibc-2.6.1/configure --build=i686-linux
--host=arm-angstrom-linux-gnueabi --target=arm-angstrom-linux-
gnueabi --prefix=/usr --exec_prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --li
bexecdir=/usr/libexec --datadir=/usr/share --sy
sconfdir=/etc --sharedstatedir=/usr/com --localstate
dir=/var --libdir=/usr/lib --includedir=/usr/in
clude --oldincludedir=/usr/include --infodir=/u
sr/share/info --mandir=/usr/share/man --enab
le-kernel=2.4.0 --without-cvs --disable-profile --disable-debug --without-gd
--enable-clocale=gnu --enable-add-ons=ports,nptl,libidn --with-headers=/hom
e/alex/moko/build/tmp/staging/arm-angstrom-linux-gnueabi/usr/include --without
-selinux --without-fp --without-fp ...
| configure: loading site script /home/alex/moko/openembedded/site/endian-little
| configure: loading site script /home/alex/moko/openembedded/site/common-linux
| configure: loading site script /home/alex/moko/openembedded/site/common-glibc
| configure: loading site script /home/alex/moko/openembedded/site/arm-common
| configure: loading site script /home/alex/moko/openembedded/site/arm-linux
| configure: loading site script /home/alex/moko/openembedded/site/common
| configure: loading site script /home/alex/moko/openembedded/site/common
| checking build system type... i686-pc-linux-gnu
| checking host system type... arm-angstrom-linux-gnueabi
| checking add-on ports for preconfigure fragments... am33 arm hppa m68k mips
| configure: running configure fragment for add-on nptl
| configure: running configure fragment for add-on libidn
| checking sysdep dirs... ports/sysdeps/arm/elf ports/sysdeps/unix/sysv/linux/ar
m/eabi/nptl ports/sysdeps/unix/sysv/linux/arm/eabi sysdeps/unix/sysv/linux/arm/e
abi ports/sysdeps/unix/sysv/linux/arm/nptl ports/sysdeps/unix/sysv/linux/arm sys
deps/unix/sysv/linux/arm ports/sysdeps/unix/sysv/linux nptl/sysdeps/unix/sysv/li
nux nptl/sysdeps/pthread sysdeps/pthread sysdeps/unix/sysv/linux sysdeps/gnu sys
deps/unix/common sysdeps/unix/mman sysdeps/unix/inet ports/sysdeps/unix/sysv npt
l/sysdeps/unix/sysv sysdeps/unix/sysv ports/sysdeps/unix/arm ports/sysdeps/unix
nptl/sysdeps/unix sysdeps/unix sysdeps/posix ports/sysdeps/arm/eabi ports/sysdep
s/arm/nptl ports/sysdeps/arm sysdeps/wordsize-32 sysdeps/ieee754/flt-32 sysdeps/
ieee754/dbl-64 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
| checking for a BSD-compatible install... /home/alex/moko/build/tmp/staging/i68
6-linux/usr/bin/install -c
| checking whether ln -s works... yes
| checking for arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc
-march=armv4t -mtune=arm920t
| checking for suffix of object files... o
| checking whether we are using the GNU C compiler... yes
| checking whether arm-angstrom-linux-gnueabi-gcc -march=armv4t -mtune=arm920t a
ccepts -g... yes
| checking for arm-angstrom-linux-gnueabi-gcc -march=armv4t -mtune=arm920t optio
n to accept ANSI C... none needed
| checking for gcc... gcc
| checking how to run the C preprocessor... arm-angstrom-linux-gnueabi-gcc -E
| configure: error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E" fails san
ity check
| See `config.log' for more details.
| FATAL: oe_runconf failed
NOTE: Task failed: /home/alex/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-2.6.1-r10/temp/log.do_configure.11446
NOTE: package glibc-2.6.1-r10: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package glibc-2.6.1: failed
ERROR: Build of /home/alex/moko/openembedded/packages/glibc/glibc_2.6.1.bb do_co
nfigure failed
ERROR: Task 7 (/home/alex/moko/openembedded/packages/glibc/glibc_2.6.1.bb, do_co
nfigure) failed
NOTE: Tasks Summary: Attempted 448 tasks of which 440 didn't need to be rerun an
d 1 failed.
ERROR: '/home/alex/moko/openembedded/packages/glibc/glibc_2.6.1.bb' failed
NOTE: build 200808041052: completed

</pre>

Try

cd source
rm glibc*2.6.1*
cd ../build
. ../setup-env
bitbake -crebuild glibc

if this doesn't help, you have to do this

cd build
. ../setup-env
bitbake -f -c fetch gcc-cross-initial && bitbake gcc-cross-initial && bitbake -crebuild glibc

== Gettext fails to build ==
Gettext's build is broken unless you have emacs installed. Crazy though it seems. You will see an error like:

<pre>

| WARNING: Warnings can be ignored. :-)
| if test "no" != no; then \
| set x; \
| list='po-mode.el po-compat.el'; for p in $list; do \
| if test -f "$p"; then d=; else d="./"; fi; \
| set x "$@" "$d$p"; shift; \
| done; \
| shift; \
| EMACS="no" /bin/bash ../../config/elisp-comp "$@" || exit 1; \
| if test "no" != no; then \
| set x; \
| list='po-mode.el po-compat.el'; for p in $list; do \
| if test -f "$p"; then d=; else d="./"; fi; \
| set x "$@" "$d$p"; shift; \
| done; \
| shift; \
| EMACS="no" /bin/bash ../../config/elisp-comp "$@" || exit 1; \
| else : ; fi
| mv: cannot move `elc-temp' to `elc-stamp': No such file or directory
| make[5]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools/misc'
| make[5]: *** [elc-stamp] Error 1
| make[5]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools/misc'
| make[4]: *** [po-mode.elc] Error 2
| make[4]: *** Waiting for unfinished jobs....
| make[4]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools/misc'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1'
| FATAL: oe_runmake failed

</pre>

The solution is simple - install emacs (example below for debian/ubuntu) and try again:

<pre>

sudo apt-get install emacs
make clean-package-gettext-native-0.14.1-r5
make openmoko-devel-image

</pre>

== Building OpenMoko with chroot ==

There may be hundreds of issues which may cause that OpenMoko fails to build on your system, so it might be more straightforward to just install a standardized build environment in which the openmoko build runs in chroot, independent of your distribution.

There is now a (not fully working) script which is able to set up a 32-bit openSUSE 10.3 build environment for building OpenMoko posted on distro-devel: [http://lists.openmoko.org/pipermail/distro-devel/2007-November/000076.html]

On gentoo and debian-like distribution, you can use debootstrap to quickly setup a base chroot.

Please note that in addition to the common /dev, /sys and /proc, /dev/shm should also be mounted with --bind option. It is at least required to build a qtopia-x11 image. (Otherwise you will get some semaphore 'function not implemented' errors at qtopia-x11 installation stage).

== Fails compiling binutils-cross on Gentoo/AMD64 and openSUSE/x86_64 ==

make setup works fine, but when running make openmoko-devel-image it fails with the following:

<pre>
| make[4]: Entering directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi/libiberty/testsuite'
| make[4]: Nothing to be done for `install'.
| make[4]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi/libiberty/testsuite'
| make[3]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi/libiberty'
| make[2]: Nothing to be done for `install-target'.
| make[2]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi'
| make[1]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi'
| rmdir: build/tmp/cross//home/techiem2/Moko/build/tmp/cross/lib/gcc-lib: No such file or directory
| rmdir: build/tmp/cross//home/techiem2/Moko/build/tmp/cross/lib: No such file or directory
| rmdir: build/tmp/cross//home/techiem2/Moko/build/tmp/cross: No such file or directory
| mv: cannot stat `build/tmp/cross/lib/libiberty.a': No such file or directory
NOTE: Task failed: build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/temp/log.do_stage.9730
NOTE: package binutils-cross-2.18-r0: task do_populate_staging: failed
ERROR: TaskFailed event exception, aborting
NOTE: package binutils-cross-2.18: failed
ERROR: Build of openembedded/packages/binutils/binutils-cross_2.18.bb do_populate_staging failed
ERROR: Task 1641 (openembedded/packages/binutils/binutils-cross_2.18.bb, do_populate_staging) failed
NOTE: Tasks Summary: Attempted 107 tasks of which 107 didn't need to be rerun and 1 failed.
ERROR: 'openembedded/packages/binutils/binutils-cross_2.18.bb' failed
make: *** [openmoko-devel-image] Error 1
</pre>

The final reason why the build cannot continue is:
mv: cannot stat `/home/techiem2/Moko/build/tmp/cross/lib/libiberty.a': No such file or directory

=== The lib64 issue ===

Likely, Gentoo/AMD64 uses lib64 instead of lib as the library directory for x86_64 libraries. It's l likey that many (or all?) AMD64 distributions do for their 64-bit binaries. On openSUSE-x86_64, the same happens. Debian/x86-64 seems to either not use lib64 or is somehow supported by the openmoko distribution.

On multilib/lib64 platforms like Gentoo/x86_64 and openSUSE-x86_64, the openmoko build runs into a final problem at the end of build: It tries to use fakeroot which uses LD_PRELOAD to fake a different root directory and in the final stages, after hours of compiling, fakeroot execution causes warning messages because on multilib/lib64 systems as they have two versions of many libraries, the 64-bit libraries are in /lib64, /usr/lib64 and oder lib64 paths, while the 32-bit libraries are in /lib, /usr/lib and other lib paths. Some tool on these lib64 distributions are adapted to install 64-bit libraries to lib64, but this seems to fail when cross-compiling.

At least on openSUSE-10.3 the missing libiberty.a was installed to build/tmp/cross/lib64/libiberty.a, which looks wrong, and it is if this libiberty.a file contains 32-bit arm objects. If it contains 64-bit x86_64 objects, it's fine, but openembedded/openmoko is not expecting it in a lib64 directory. I am not sure what is the case.

The lib64 fakeroot issue requires to change the openembedded build scripts, which is doable. But it's not very easy to find the correct script and patch it correctly. If you feel adventourus, go ahead and try to build openmoko on a lib64 distribution, but it's easyer to set up a complete 32-bit chroot environment and run a normal build in it.

After seeing this, I assumed that openmoko/openembedded was clearly not tested with lib64 build hosts and since that would mean that even if I'd fix that error, many others could follow, and as I was not interested to fix the lib64 bugs but rather wanted to see something running first, I decided to make openmoko/openembedded think that it was running on a normal 32-bit non-lib64 machine.

There are several ways to do that:
* You install an 32bit x86-Linux somewhere and use that for building:
** Do a native install and dual-boot the 32bit x86-linux (That's for dummies which do not know the other tricks)
** Install 32bit x86-Linux in a virtual machine (Takes powerful hardware and has some overhead too). Use [http://gentoo-wiki.com/VirtualBox VirtualBox], for example.
* you can install a 32-bit development system in to a chroot jail and compile there (also quite some setup and inconvinience). See [http://www.gentoo.org/proj/en/base/amd64/howtos/chroot.xml the gentoo guide]

=== Building on SuSE Linux 10.3-AMD64 with -m32 (not finished) ===

Install the following packages for the 32-bit C/C++ compiler target option -m32 to work and to compile what is needed

gcc42-32bit gcc42libgcc42-32bit glibc-devel-32bit libstdc++-devel-32bit ncurses-devel-32bit zlib-devel-32bit (maybe also gtk2-devel-32bit)

The openSUSE 10.3-AMD64 has no libopenssl-devel-32bit, but you can install the 32-bit rpm from the i586 10.3 rpm tree:

libopenssl-devel

You should also make sure that gdbm-devel is not installed.
The multilib support in ld has an issue which surfaces when it is called from perl's Configure script to complile a test program with -Lgdbm. If gdbm-devel is installed, it finds /usr/lib64/libgdbm.so, but since it's not compatible with 32-bit, it skips it, but also does not search the specified -Lpath where the OpenEmbedded-built libgdbm.so is already installed. To work around this, uninstall /usr/lib64/libgdbm.so with:
rpm -e gdbm-devel

Note these need to be the 32-bit cpp33 and gcc33 rpms as the 64-bit gcc33 rpms for openSUSE do not support the 32-bit target.

To make the OpenMoko build think that its running on 32-bit i686, use linux32 (changes uname -m to i686 in the new shell):

linux32 bash

And set up gcc scripts which force the use of gcc-3.3 (it can only generate 32-bit assembly) for all compilation:

mkdir bin;cd bin
echo '/usr/bin/${0##*/}-3.3 -m32 "$@"' >gcc
echo '/usr/bin/${0##*/} -m elf_i386 "$@"' >ld
echo '/usr/bin/${0##*/} --32 "$@"' >gas
sed -i '1i#!/bin/sh' gcc gas ld
chmod 755 gcc gas ld
ln -s gcc cc
ln -s gcc c++
ln -s gcc g++
ln -s gas as
echo PATH=\""$PWD":\$PATH\" >.setup-gcc-m32
cd -

Then set the path and test it:

source bin/.setup-gcc-m32
type gcc

== More package requirements ==

On my system (Kubuntu 6.10) build failed with message "ERROR: QEMU requires SDL or Cocoa for graphical output" because package <tt>libsdl-image1.2-dev</tt> was missing. Use <tt>apt-get install libsdl-image1.2-dev</tt> to install. Additionally I had to install packages <tt>cvs</tt> and <tt>diffstat</tt>. I was also asked to install Psyco JIT Compiler (package <tt>python-psyco</tt>) to increase performance. Nevertheless <tt>make flash-qemu-local</tt> took some hours, but now I finally can get an impression of the phone that I am looking for! -- [[User:Nichtich|Nichtich]] 00:26, 20 September 2007 (CEST)

== pango-directfb failed to build due to missing Glib 2.14.x ==

The latest(as of Sept. 25, 2007) build started to fail with the following error:

| checking for GLIB... no
| configure: error:
| *** Glib 2.14.0 or better is required. The latest version of
| *** Glib is always available from ftp://ftp.gtk.org/.
| FATAL: oe_runconf failed
NOTE: Task failed:
/media/sdc1/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/\
pango-directfb-1.18.1-r0/temp/log.do_configure.19927
NOTE: package pango-directfb-1.18.1-r0: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package pango-directfb-1.18.1: failed
ERROR: Build of /media/sdc1/moko/openembedded/packages/pango/\
pango-directfb_1.18.1.bb do_configure failed

The Glib included in the build tree seems to be only 2.12.12, so looks like something
is broken in term of dependency.

This had happened on both of Fedora 7 and Debian Etch. I am running the latest
MokoMakefile with OM-2007.2. The funny thing is that the build had worked only
couple nights ago. Any idea? I will update anything I find here and also on my blog(see my user profile).
[[User:ttz|ttz]] Wed Sep 26 12:17:33 CDT 2007

pango-directfb had been removed from OE for now due to the report of it breaking builds like OpenMoko.

[[User:ttz|ttz]] Thu Oct 4 10:20:12 CDT 2007

== uicmoc4 failes to compile ==

This is solved by installing libz-dev

Or, look at [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=747 Bug #747]

== svn: REPORT request failed on '/repos/tasks/!svn/vcc/default' ==

osiris$ make update
...
Fetching external item into 'trunk/src/target/OM-2007.2/applications/openmoko-today2/libkoto'
svn: REPORT request failed on '/repos/tasks/!svn/vcc/default'
svn: REPORT of '/repos/tasks/!svn/vcc/default': 200 OK (http://svn.o-hand.com)
make: *** [update-openmoko] Error 1

osiris$ cd openmoko/trunk/src/target/OM-2007.2/applications/openmoko-today2//libkoto/
osiris$ svn up -r HEAD
svn: REPORT request failed on '/repos/tasks/!svn/vcc/default'
svn: REPORT of '/repos/tasks/!svn/vcc/default': 200 OK (http://svn.o-hand.com)

Anyone know about this one?
--[[User:Blackh|Blackh]] 00:11, 12 October 2007 (CEST)

== bootparam_prot.h fails to install in glibc-intermediate-2.5 package (Debian sid) ==

| install: cannot stat
`/home/blackh/src/openmoko/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-intermediate-2.5-r7/glibc-2.5/sunrpc/rpcsvc/bootparam_prot.h'
No such file or directory
NOTE: Task failed: /home/blackh/src/openmoko/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-intermediate-2.5-r7/temp/log.do_stage.3940

For some reason, on Debian, the rpcgen command needs "-Y /usr/bin" added to the end of it or it won't work ("cannot find any C preprocessor (cpp)"). This can be fixed by hand...

cd /home/blackh/src/openmoko/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-intermediate-2.5-r7/glibc-2.5/sunrpc/rpcsvc
for f in *.x ; do rpcgen -h $f -o ${f%%.x}.h -Y /usr/bin ; done

This command will generate the right files and you can resume the build with

make openmoko-devel-image

Here is a better fix - put this script, calling it rpcgen, somewhere in your PATH before /usr/bin:

#!/bin/sh
exec /usr/bin/rpcgen -Y /usr/bin "$@"

--[[User:Blackh|Blackh]] 05:17, 12 October 2007 (CEST)

== Cannot find SVN openmoko-terminal2 ==
I'm having an issue when building MokoMakeFile where it is unable to find http://svn.openmoko.org/trunk/src/target/OM-2007.2/applications/openmoko-terminal2. Any ideas on how to fix this?

--[[User:cartera|cartera]]

== problem with make openmoko-devel-image ==

when i try to do my first make openmoko-devel-image I obtain this error:

<pre>
NOTE: Running task 844 of 5445 (ID: 671, /home/xraver/moko/openembedded/packages/linux/linux-openmoko_2.6.24+git.bb, do_fetch)
NOTE: package linux-openmoko-2.6.24+git20080422: started
NOTE: package linux-openmoko-1_2.6.24+git20080422-r0: task do_fetch: started
NOTE: fetch http://downloads.openmoko.org/sources/git_git.openmoko.org.git.kernel.git_4194.tar.gz
--08:47:41-- http://downloads.openmoko.org/sources/git_git.openmoko.org.git.kernel.git_4194.tar.gz
=> `/home/xraver/moko/sources/git_git.openmoko.org.git.kernel.git_4194.tar.gz'
Risoluzione di downloads.openmoko.org in corso... 88.198.93.219
Connessione a downloads.openmoko.org|88.198.93.219:80... connesso.
HTTP richiesta inviata, aspetto la risposta... 404 Not Found
08:47:41 ERRORE 404: Not Found.
</pre>

In this location http://downloads.openmoko.org/sources/ the file git_git.openmoko.org.git.kernel.git_4194.tar.gz does not exist.
Any solutions?

--[[User:xraver|Giorgio Ravera]]

== Wishlist: Make qemu optional ==

Hi,

I’ve just set up MokoMakefile, and after <tt>make setup</tt> I tried to get a package with <tt>make build-package-openmoko-messages2</tt>, but it’s spending a lot of time and disk space on building native libraries and qemu – something that I have not asked for. It would be nice if I could build packages for my phone without having to build unneccessary stuff.

Thanks,
Joachim

== SVN Certificate issues for Gentoo users ==

Note for Gentoo users: I think Portage creates a ~/.subversion directory as root if you've ever compiled a svn ebuild via "sudo emerge". If this happens, certificates won't be saved, so you have to take back ownership of the directory:

<pre>
chown -R $USER ~/.subversion
</pre>

Before running a svn co from the openmoko svn server to accept the certificate, otherwise the authentication information will not be saved.
[[User:Kelvie|kelvie]] 06:05, 18 July 2008 (UTC)

Talk:FreeRunner GPS antenna repair SOP

2008-07-14T14:01:04Z

Emdete:

Does it really fix the problem?

I think there are more than this problem:
[http://pyneo.org/gps-nofix/gps_2684.sized.jpg]
while my connector looks like this:
[http://pyneo.org/gps-nofix/gps_2688.sized.jpg]. please see also https://docs.openmoko.org/trac/ticket/1542

From the descriptions people give (like: works perfect sometimes, but on other days doesn't get a fix at all) it really could be bad soldering or bad antenna connector. Though I didn't chek my FR yet. Btw. the soldering on my antenna looks the same, but unbelievably there's no short-circuit ;)

Talk:FreeRunner GPS antenna repair SOP

2008-07-14T13:59:58Z

Emdete:

Does it really fix the problem?

I think there are more than this problem:
[http://pyneo.org/gps-nofix/gps_2684.sized.jpg]
while my plug looks like this:
[http://pyneo.org/gps-nofix/gps_2688.sized.jpg]. please see also https://docs.openmoko.org/trac/ticket/1542

From the descriptions people give (like: works perfect sometimes, but on other days doesn't get a fix at all) it really could be bad soldering or bad antenna connector. Though I didn't chek my FR yet. Btw. the soldering on my antenna looks the same, but unbelievably there's no short-circuit ;)

Emdete: neo1973 first stats...

neo1973 first stats...

User:Emdete

2007-12-08T19:21:30Z

Emdete:

2007-12-04T23:22:36Z

Emdete: /* Strange effects */

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

All purchased phones do not include the GPS binary driver. [http://lists.openmoko.org/pipermail/community/2007-July/008466.html]
But finally, as described in [[November_29%2C_2007_Community_Update]], the binary driver is available to the community now.

In the very early shipment to 50 Phase 1 developers, a binary-only program for talking to the the GPS was accidentally included
in /home/root/DM2/gps, (and presumably, the same binary would function on a P0 device).

There is an ongoing effort to write a Free Software
program that could be used instead of this binary-only program. See
[[Hammerhead/Protocol]] for details and the latest status.

== Binary Daemon GLLIN ==

For those few with the binary driver in the meantime, Pavel Machek
[http://pavelmachek.livejournal.com/39229.html provides] the
following script for recording an NMEA stream from the binary program.

#!/bin/sh
echo 1 > /sys/class/leds/gta01\:vibrator/brightness
killall gllin cat
sleep 1
echo 0 > /sys/class/leds/gta01\:vibrator/brightness
mknod /tmp/nmeaNP p
cat /tmp/nmeaNP >> /tmp/gps.nmea &
/home/root/DM2/gps/gllin -low 5
/home/root/DM2/gps/gllin -periodic 3

The binary program was compiled to OABI format which now is obsolete as OM2007.2 builds are in EABI format. You can still run the binary with ''chroot''. [[user:Zdanek|Bartek Zdanowski]] wrote an [http://www.openmoko.org.pl/node/55 aticle] how to run GPS receiver. Alternativly ld-linux can be used to do the trick:

==The ld-linux trick==

you need the following files:

bin/gllin
bin/gllin.sh
lib/ld-linux.so.2
lib/libc.so.6
lib/libgcc_s.so.1
lib/libm.so.6
lib/libnss_dns.so.2
lib/libnss_files.so.2
lib/libpthread.so.0
lib/libresolv.so.2
lib/librt.so.1
lib/libstdc++.so.6
lib/libutil.so.1

the file bin/gllin.sh contains:

#!/bin/sh
`pwd`/lib/ld-linux.so.2 --library-path `pwd`/lib `pwd`/bin/gllin -low 5
test -p /tmp/nmeaNP || ( rm -f /tmp/nmeaNP && mknod /tmp/nmeaNP p )
`pwd`/lib/ld-linux.so.2 --library-path `pwd`/lib `pwd`/bin/gllin -periodic 3

be shure to start at least a `cat /tmp/nmeaNP` somewhere.

another aproach (chroot) is described in [[Gllin]] - here is also a link to a archive with all needed shared libraries in the right format.

==Strange effects==

the message

Stack size 8864 bytes (9 KB)

means, nobody is reading on the pipe /tmp/nmeaNP, you probably forgot to start the `cat ...`.

the message

gllin: early exit(3) in halInit()/681

is issued by the low-level hardware test but gllin works fine afterwords.

do not use the option

+daemon

because gllin writes all files to /tmp then which is a bad idea. because /tmp is ram it is lost. because ram is limited the logfile will eat up your memmory.

== Bluetooth GPS ==

He also [http://pavelmachek.livejournal.com/39659.html succeeded]
at getting the Neo1973 to act like a bluetooth GPS with the following
script: (Note that this script has bad problems if you run it more than once. You can get a "time traveling GPS" effect, with the GPS showing you your past position).

#!/bin/sh
killall rfcomm tail
mknod /dev/rfcomm0 c 216 0
echo 1 > /sys/devices/platform/s3c2410-i2c/i2c-0/0-0008/gta01-pm-bt.0/power_on
sleep 1
hciconfig hci0 up name linuxgps
sleep 1
sdpd
sleep 1
sdptool add SP
(
while true; do
rfcomm listen /dev/rfcomm0 1
sleep 1
done
) &
(
while true; do
tail -f /tmp/gps.nmea > /dev/rfcomm0
echo 1 > /sys/class/leds/gta01\:vibrator/brightness
sleep 1
echo 0 > /sys/class/leds/gta01\:vibrator/brightness
done
) &

== Using UDP ==

gllin sends a udp packet per nmea sentence on port 6000. this is a much cleaner aproach because using files will fill up memory or rootfs (the latter will result in the need for reflashing).

i switch off writing to /tmp/nmeaNP with

-np

the following python script reads the nmea sentences:

import socket
s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
s.bind(('127.0.0.1', 6000))
while True:
line = s.recv(1024)
print line

the program just prints those to stdout but other methods are possible (i feed them into a NMEA parser).

benefits are that both programs can be started and stopped at will. none needs the other. gllin will not terminate if /tmp/nmeaNP is not there or not read from. the `cat /tmp/nmeaNP | gzip > gps.gz` is a useless idea any because the files in log/ (current directory) contains the NMEA data already.

== NMEA ==
The ouput from the binary driver seems to follow the NMEA standard.

Some information about it is available at [http://gpsinformation.org/dale/nmea.htm gpsinformation.org] and on [http://en.wikipedia.org/wiki/NMEA Wikipedia].

[[Category:GPS]]