Mer

The Mer platform is a Linux distribution for mobile devices based on the Maemo platform from Nokia. Mer goals include:


 * Improving and developing parts of Maemo that are of interest to the Maemo community.
 * Making it easier to port existing desktop applications by hildonizing and adjusting them to the tablet form factor.
 * Encouraging third party experimentation and development.
 * Supporting tablet hardware no longer receiving updated OS software by Nokia.
 * Making Maemo a generic platform for all tablet devices, including non-Nokia ones.
 * Focusing Maemo community efforts in platform-related areas

It is -not- a Nokia project, it's a project started by maemo.org community members.

Mer platform development will be done in the open, with public SCM repository, bugtrackers, and Wiki-based blueprint discussion.

We should stop seeing the tablets as strictly under-powered embedded systems, and see them for what they really are: powerful, power-efficient, economical handheld computers.

Historically, the Mer platform came from a discussion on reconstructing Maemo and a desire to make a proof of concept system of the thoughts in this proposal (M-R PoC), which developed into Mer after realization that it was a viable direction of development.

If you would like to participate in and contribute to Mer - participate in the Mer Sprints and read the Mer Documentation

If you want to see documentation for Mer releases - see Mer Releases

Sprint 0.7
Period: until 1 february 2009

Sprint 0.6
Period: - 18 january 2009

Bugs
Bug reports in bugzilla discovered through or related to Mer development in this sprint:

Sprint template
= Sprint January 2009 and before: Basic installable image =

The purpose of this milestone:
 * To provide a basic installable firmware image, both through installer and through flashing, for N8x0 tablets.
 * The image must include a basic user interface and ability to connect to Wi-Fi networks.
 * To provide a installer and image for 770 tablets.
 * To provide initial developer tools so we can start developing for the tablets.
 * Begin initial talks with Nokia and maemo.org on how to distribute full firmware images.
 * Prepare for next milestone in terms of collaborative technologies.

Bugs
Bug reports in bugzilla discovered through or related to Mer development in this sprint:

Activity log
17th January


 * stskeeps: added docpurge to repository, added docpurge to n800 and 770 images, re-running imager. helped meiz get Mer on his x86. prodded andre about 'Mer' product in bugzilla, and got it setup. Reported bug on multiple git repositories per project, personal git repositories to ggit project.

16th January


 * stskeeps: remade Mer blueprint to fit more into maemo.org processes, added mer-generic-x86 to play with at some point, and added nit-kernel-compat to imager. fixed up nokia-770's kernel-modules-770 so we can make images for it in imager. added dsme-tools to repo. got x86 port going.

= Documentation and tasks =

SDK
First, install Fremantle SDK, and add yourself as a user to scratchbox.

As user:
 * wget -c http://stskeeps.subnetmask.net/mer/arm-linux-cs2008q3-72-libtool2_1.0.11_i386.deb
 * sudo dpkg -i arm-linux-cs2008q3-72-libtool2_1.0.11_i386.deb (run as root)
 * wget -c http://stskeeps.subnetmask.net/mer/scratchbox-devkit-mer_1.0.11_i386.deb
 * sudo dpkg -i scratchbox-devkit-mer_1.0.11_i386.deb
 * You can optionally get qemu-arm-eabi and use that here instead. It is very good for your use of the SDK
 * sb-conf setup MER-ARMEL --compiler=arm-linux-cs2008q3-72-libtool2 --devkits=debian-etch:cputransp:perl:mer --cputransp=qemu-arm-cvs-m -f
 * sb-conf reset -f MER-ARMEL
 * sb-conf select MER-ARMEL
 * sb-conf rootstrap MER-ARMEL http://stskeeps.subnetmask.net/mer/mer-armel-rootstrap-v8.tar.gz
 * sb-conf install MER-ARMEL --etc --devkits --fakeroot

ISSUES:
 * You might have to do export PKG_CONFIG_PATH=/usr/share/pkgconfig:/usr/lib/pkgconfig to get some pkg-config stuff going
 * You might have to set cpu right and such to target armv5el (no vfp)
 * You probably need to get EABI cpu transparency target too
 * 'not safe for cross-compilation' warnings (not true, i think)
 * fakeroot apt-get dist-upgrade is good once in a while to keep up to date.

Mer Installer
Make installer for Maemo/Diablo that does the following:


 * Depends on bootmenu (bootmenu with bootmenu.d item), wget, rootsh, zenity, gnutar, binutils, and e2fsprogs
 * Allows simple installation (partition my internal/external MMC to 50mb FAT, 128mb swap, rest linux), or advanced (choose my own partition)
 * Partitions, mkfs.ext3's and unpacks a downloaded tar.gz (built by the imager, uploaded to some http.). Should support resume of dls (wget -c?)
 * Sets up the bootmenu item for Mer.

Straightjacket packages
This is a list of packages that did not compile in Scratchbox, and that we had to build natively:


 * python-osso: http://trac.tspre.org:8000/python-osso_jaunty-armel-1232387331.log (python extension build problem)
 * python-hildon: http://trac.tspre.org:8000/python-hildon_jaunty-armel-sb-1232400294.log (python extension build problem)
 * python-hildondesktop: http://trac.tspre.org:8000/python-hildondesktop=0.0.2-2mer2_armel-0901212232.log (python extension build problem)
 * vte: http://trac.tspre.org:8000/vte=1:0.17.4-0ubuntu1mer2_jaunty-armel-1232381310.log (potential debhelper issue)

qemu-eabi cputransp for Scratchbox
See http://maemogeek.blogspot.com/2007/11/installing-qemu-arm-eabi-patch-into.html

Make a debian package with this binary (for i386), installing into /scratchbox/devkits/cputransp/bin/qemu-arm-eabi-sb2 and adding 'qemu-arm-eabi-sb2' to /scratchbox/devkits/cputransp/etc/cputransp-methods when installing, and removing when removing (sed -i?)

Edit |SDK to make instructions use qemu-arm-eabi-sb2 instead, and getting your .deb package.

Getting your package included in the Repository

 * Make sure it compiles after getting your build dependancies, dpkg-buildpackage.
 * Ideally test both dpkg-buildpackage -S -us -uc, dpkg-buildpackage -b -us -uc, dpkg-buildpackage -B (some packages may not build any arch-dep packages, so that's ok. Microdocument it on Jaiku.)
 * bzr export lp:~yourusername/m-r/ (gives you a checked out version, without metadata)
 * cd
 * dpkg-buildpackage -S -us -uc, to generate a source package
 * Upload the resulting source package (*.changes, *.tar.gz, possibly *.diff.gz) to your ~/incoming on trac.tspre.org.
 * ssh yourlogin@trac.tspre.org /import-new-packages

(This will add the source package to repository, and complain otherwise)


 * You need access to merbuilder & repository upload for the following, ask Stskeeps on Jaiku/IRC for this. Or refer on Jaiku to the source package and some may pick it up
 * On http://jaiku.com/channel/merbuilder, write "build = "
 * You can also save the builder some resources if it's an arch-indep package and do "build-x86 = "
 * You can make a specific rebuild using build-armel-sb (build in scratchbox),
 * Monitor progress at same page (RSS: http://jaiku.com/channel/merbuilder/feed/rss )
 * An LP player notes that it has picked up a package for building at a certain builder
 * A toast means it baked properly on this architecture. And is uploaded to repository.
 * A heart means it built properly on all architectures. And is uploaded to the repository
 * A bomb means it failed to build on an architecture.
 * A shopping wagon means it has noticed your build request and queued it.
 * A straightjacket means that it failed to build on Scratchbox and needed to be built natively. Note this in "Straightjacket packages" when this happens. means there's a bug in SDK.)

Open system sounds
List of wav files from osso-sounds-ui (non-free package):

/usr/share/sounds/ui-recharge_battery.wav /usr/share/sounds/ui-connection_lost.wav /usr/share/sounds/ui-window_open.wav /usr/share/sounds/ui-window_close.wav /usr/share/sounds/ui-information_note.wav /usr/share/sounds/ui-new_email.wav /usr/share/sounds/ui-wake_up_tune.wav /usr/share/sounds/ui-charging_started.wav /usr/share/sounds/ui-confirmation_note.wav /usr/share/sounds/ui-gesture_number_recognized.wav /usr/share/sounds/ui-shutdown.wav /usr/share/sounds/ui-key_press.wav /usr/share/sounds/ui-pen_down.wav /usr/share/sounds/ui-general_warning.wav /usr/share/sounds/ui-thumb_keyboard_launch.wav /usr/share/sounds/ui-battery_low.wav /usr/share/sounds/ui-default_beep.wav /usr/share/sounds/ui-operation_ready.wav /usr/share/sounds/ui-wrong_charger.wav

Using the imager
Grab the imager from bzr (lp:~mer-committers/m-r/imager)

Targets are:


 * targets/mer-770-fs-only - builds a filesystem for Mer on Nokia 770
 * targets/mer-n800-fs-only - builds a filesystem for Mer on N800
 * targets/mer-x86-generic - builds a filesystem for X86 in general

Imager can be run with: sh imager targets/TARGET /path/where/you/want/fs

Look inside the target scripts and work your way back.

Making a x86 Mer bootable
Partition your boot device, make a ext3 partition. In the following, sda1 is your ext3 partition and sda is your boot device. Only install this on a USB stick or whatever that you want to have possibly destroyed.


 * mkdir -p /mnt/mer
 * mkfs.ext3 /dev/sda1
 * mount -t ext3 /dev/sda1 /mnt/mer
 * Grab a release x86-generic tar.gz and put in /mnt/mer, tar pzvxf it from within /mnt/mer OR Use imager from above and sh imager targets/mer-x86-generic-only-fs /mnt/mer
 * grub-install --no-floppy --recheck --root-directory=/mnt/mer /dev/sda
 * chroot /mnt/mer update-grub
 * verify your /mnt/mer/boot/grub/menu.lst looks correct
 * umount /mnt/mer (if you can)

Mer 0.6
Known issues:
 * 770 port has problems with sapwood and may not work from first startup. Grab a USB cable and use rescue mode
 * RX-48 has not yet gotten its bootmenu.deb updated
 * All images of the same target share same openssh server keys
 * jffs2 + kernel mix for N8x0 is untested
 * root password is not set for you or asked in the first boot wizard, in the tar.gz images.
 * Bootmenu does not play well with clone-to-SD systems. You will have to make a bootmenu item yourself (ask on #maemo about this)
 * NetworkManager is broken in .vdi image, dhclient eth0 in it
 * Advanced mode is a bit funky once in a while and creates bad bootmenu items.

If you want to try it out on N8x0, use the installer.

Disclaimer:


 * There is -no- warranty. This may blow up your MMC, steal your wife or cause doomsday to come around. But if you find some bugs, please report them on bugs.maemo.org and we'll try to see what we can do to fix the bug causing it.
 * If anything goes wrong, grab a USB cable, and rescue mode is done through holding down Home key when booting Mer.

Generic x86 - tar.gz image

 * Generic X86 tar.gz rootfs image. Usable both for chroot and actually installing on a machine.

Installation (chroot)
mkdir mer-0.6 cd mer-0.6 && sudo tar xzf mer-x86-generic-image-v0.6.tar.gz sudo mkdir -p tmp/.X11-unix home/$USER/.osso sudo mv usr/bin/maemo-invoker usr/bin/maemo-invoker.real echo -e '#!/bin/sh\nPROG="$1"\nshift\nexec "$PROG" "$@"' | sudo tee usr/bin/maemo-invoker sudo chmod 755 usr/bin/maemo-invoker echo 'assume-connection 1' | sudo tee home/$USER/.osso/hildon-application-manager echo 'nameserver ' | sudo tee -a etc/resolv.conf

Start-up (from within mer-0.6 directory)
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite 2>/dev/null 1>&2 & sudo mount --bind /tmp/.X11-unix tmp/.X11-unix sudo mount --bind /dev/pts dev/pts sudo mount -t proc proc proc sudo mount -t sysfs sysfs sys sudo chroot. export DISPLAY=:2.0 /etc/init.d/dbus start start-hildon

VirtualBox x86 - VDI image

 * VirtualBox VDI image (500mb zipped, 1.2Gb after extraction, beware) [md5sum 8c142b2bc4670a6644e85ec3806096ee]

Installation

 * 1) Unzip zip file
 * 2) Open VirtualBox, create new machine (click *New*):
 * 3) * Name: Mer 0.6
 * 4) * OS type: Linux
 * 5) * Version: Ubuntu
 * 6) * RAM: 128 at least.
 * 7) * Disk: click "existing", find the Mer 0.6.vdi file, select, select
 * 8) * Next
 * 9) * Finish.

Usage

 * Start machine.
 * Root password is 'rootme'

Nokia 770 - tar.gz image

 * Nokia 770 (armel) tar.gz rootfs image

Nokia N8x0 - Installer files (simple)

 * Bootmenu SVN for N8x0, needed to boot from MMC. Utilities -> Install Bootmenu first, say yes to removing test stuff and such, say yes to including bootmenu.conf (important). Reboot when done flashing. This is a special boot menu where boot menu items are made in /etc/bootmenu.d/*.item and refresh_bootmenu.d will flash this to initfs. If you are cloning or booting other OS'es, you'll need to make such .item files]
 * Nokia N8x0 (armel) tar.gz installer (use simple mode), Install second and then in Utilities -> Install Mer
 * Nokia N8x0 (armel) installer source code (not needed)

Nokia N8x0 - Flashable image (untested)

 * Nokia N8x0 (armel) jffs2 rootfs image
 * Nokia N8x0 (armel) zImage kernel image

Nokia N8x0 - tar.gz image

 * Nokia N8x0 (armel) tar.gz rootfs image