MeeGo wiki - User contributions [en]

Local Build Without OBS Needed

2011-09-04T08:43:59Z

Ali1234: Note about RPM keys.

This page is for people who want to avoid any connection with any [[OBS]] backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using 'build' ==

=== Install 'build' ===

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

* If your host is MeeGo, you need to install one more package 'perl-XML-Parser'

zypper install build perl-XML-Parser

=== Setup ===

After you install it, you can run “build –help” to get help info. You need to run 'build' as root.

* Proxy
If your network needs proxy, please export proxy environment variables, for example:
<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers
<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

* Conf file
You may also need to set correct default distro target, or use the "build --dist=/usr/lib/build/configs/meego-1.1.conf" option:
<pre>
cd /usr/lib/build/configs
sudo ln -sf meego-1.2.conf default.conf
</pre>

* GPG Key
build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages

You can get its public key for http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/noarch/meego-release-1.2.0-2.1.noarch.rpm

If you are building MeeGo packages on same MeeGo version you may already have the key, in which case importing will fail.

<pre>
$ wget http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/noarch/meego-release-1.2.0-2.1.noarch.rpm
$ rpm2cpio meego-release-1.2.0-2.1.noarch.rpm | cpio -idmv
$ rpm --import ./etc/pki/rpm-gpg/RPM-GPG-KEY-meego02
</pre>

=== Build a package ===

* Build from src [[rpm]]
This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

* Build from Spec file
Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/ --arch i686 cpio.spec
</pre>

* Build with multiple repository
build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 cpio-2.11-2.meego.src.rpm
</pre>

* Specify cache dir
The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm

== Development your package using build ==

=== Unpack & make change ===

If you want to modify packages, such as add/modify/remove patches, you need unpack src.rpm first. Then development can be based on source code.

This command would unpack src.rpm to current directory, and your work can be in this directory.

rpm2cpio XXX.src.rpm | cpio -idmv

#If you want to add a patch, you just need copy the patch to current directory and add this patch in spec file.
#If you wan to remove patches, you just need to remove them in spec file.
#If you want to modify exist patch, you can modify the special patch and spec file need not to modify.

=== Build the package ===

Once you development work is done, you can use ‘build’ command to generate new RPM based on you changes. Command as follows:

build --repository http://YYY/repos/oss/ia32/packages/ --arch i686 XXX.spec

binary RPM package can be found in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.

== Troubleshooting ==

=== rpm verify failed ===

If you meet below error, please import GPG key first, if the issue still exist and you are using Ubuntu10.04, you may have a try to workaround the issue by installing the "rpm" package for 10.10, there seems to be a bug for "rpm" in 10.04 which fails to verify package signature.
<pre>
downloading http://linux-ftp.jf.intel.com/pub/mirrors/MeeGo/releases/1.2.0/repos/oss/ia32/packages/noarch/autoconf-2.68-1.3.noarch.rpm ...
rpm verify failed
</pre>
Steps to fix:
1. add 10.10 repo to /etc/apt/sources.list
<pre>
deb http://cn.archive.ubuntu.com/ubuntu/ maverick main restricted
deb http://cn.archive.ubuntu.com/ubuntu/ maverick-updates main restricted
</pre>

2. remove old rpm and install new one
<pre>
$ sudo apt-get update
$ sudo apt-get remove rpm
$ sudo apt-get install rpm
</pre>

3. comment out 10.10 repo to avoid upgrade other packages

=== Exec format error ===

You may have such issue when using 'build' to create a armv7l rpm package, please see detailed solution for the distro

* Fedora13
Try command:'file /usr/bin/qemu-arm', and its output should show "statically linked", if not, you can re-install the qemu package(the package maybe changes, you can go the web address to get it, then install it).
$file /usr/bin/qemu-arm
$sudo rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm

* Ubuntu10.04
Please install 'qemu-arm-static'
$sudo apt-get install qemu-arm-static

* Debian
Please install 'qemu-user-static' from Squeeze (Debian 6.0) and later.

=== rpm error ===

This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
'Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory'
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===

This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm, modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf, change armv7el to armv7l in these files, maybe /usr/lib/build/Build.pm also need change.
If problem persist, see [https://bugs.meego.com/show_bug.cgi?id=18905 bug 18905]

===RPM key import failed===

If you are running the instructions on same version of MeeGo as the repository you are trying to build from, you probably already have the GPG key. In this case trying to import it again will fail but won't say why.

== Another language version of this page ==

* [[不需要obs的本地build-_简体中文]]

User:Ali1234

2011-02-26T17:45:57Z

Ali1234: /* Set Up OBS */

Talk:Quality/Compliance primer 1.0

2011-02-20T20:06:20Z

Ali1234:

Community hardware adaptations are not mentioned here at all. It is all "products, products, products". Although I do not argue with the fact that products and their compliance should be a primary concern for MeeGo, community hardware adaptations and the community in general should not be ignored. It just leads to problems, frustration, misunderstandings or in the worst case lawsuits and I hope we all can agree that this is not a desireable outcome.

There has to be a common roof under which community work can happen and that does address the specific needs of community work.

--[[User:Dm8tbr|Dm8tbr]] 10:59, 12 February 2011 (UTC)

'''Response:'''
Dm8tbr, can you please define what you mean by hardware adaptation? Can you provide some concrete examples?

--[[User:Bdub|Bdub]] 21:22, 14 February 2011 (UTC)

Bdub, see http://wiki.meego.com/ARM/MSMQSD and http://codex.xiaoka.com/wiki/meego:archos

--[[User:Ali1234|Ali1234]] 01:18, 15 February 2011 (UTC)

@[[User:Dm8tbr]]: There are 2 levels of compliance:

* Device & stack compliance ("I can put a MeeGo sticker on my device", or "I have respun the MeeGo stack to include some extra stuff, to cater to a new UX, etc, and I want to call it MeeGo School Edition" (or whatever)) - this is roughly equivalent to Android platform compliance. This is where Suse MeeGo would fit in, and potentially (when they conform to the compliance requirements) Linpus. This is also where Smeagol and Debian MeeGo port have trouble.
* Application compliance ("My app is a MeeGo application") - this is an application bundle that is certified for a given version of MeeGo, and installs stand-alone, like a Mac app or an Android package. And this is where community apps that want to pull in upstream dependencies have trouble.

So a community hardware adaptation should install a MeeGo compliant stack to be able to call itself a MeeGo device. If there are any compliance rules preventing me from (say) installing the MeeGo stack on an N900 or an O2 Joggler and having that be called the MeeGo Joggler edition or whatever, then I would say that that's a bug in the compliance rules & needs to be fixed.

Can you give an example of a situation where the current compliance rules would prevent a community hardware adaption from using the MeeGo name?

--[[User:Dneary|Dneary]] 13:44, 15 February 2011 (UTC)

Example: When a community hardware adaptation has just begun, and has not yet achieved compliance, it cannot use the MeeGo trademark on development versions of it's software, because they are not compliant. Therefore it won't be able to distribute testing versions to developers and beta testers, or possibly even tell anyone about the goals of the project. This will make it impossible for a community project to attract any developers and so compliance is unlikely to ever be achieved. The only legal and realistic option is to strip all references to MeeGo from the code - essentially creating an unencumbered fork (like CentOS) - before beginning any adaption work.

--[[User:Ali1234|Ali1234]] 20:28, 17 February 2011 (UTC)

see also: https://bugs.meego.com/show_bug.cgi?id=13516

--[[User:Ali1234|Ali1234]] 20:06, 20 February 2011 (UTC)

Talk:Quality/Compliance primer 1.0

2011-02-17T20:28:06Z

Ali1234:

Talk:Quality/Compliance primer 1.0

2011-02-15T01:18:57Z

Ali1234:

MeeGo Desktop/Changing Desktops

2011-01-05T02:52:43Z

Ali1234: /* Assumptions */ - just adding a link to the ideapad page...

==Background==
At the 2010 MeeGo Conference in Dublin, the question of how to switch from the Netbook to the Handset desktop was asked during the MeeGo Handset UX Roadmap session. The context of the question had to do with using the Lenovo S10-3t Netbooks given away at the conference as platforms for MeeGo Handset development. [[User:Sabotage|Sabotage]] pipped up and offered up his experience as proof that it can be done, and some '''very''' basic instructions on how to do so. Since the question continues to come up in Mailing lists and IRC, the specifics on how to switch between desktops are being documented for ongoing reference.

If it proves useful and interesting to others, maybe these will spawn the development of a desktop "switcher" applet/tool... hint, hint ;)

==Pre-work==
===Assumptions===
# Using a supported Netbook, such at the [[Devices/Ideapad|Lenovo S10-3t]] that was given away at the 2010 MeeGo Conference
# You have root and/or sudo rights on the above device
# You have an installed and running MeeGo 1.1 or later Netbook image ([http://download.meego.com/trunk-daily/builds/trunk/ Daily images])

===Install Handset Packages===
====Add the Handset repos====
You need to add the appropriate repos to your zypper configs so you can install the Handset packages. This will be different depending on:
# Your architecture (ARM, ia32, etc.)
# Your desired stability (Daily vs. Weekly vs. Release repos)
So, for example, to add the daily handset repos for the ia32 architecture, you could do this as root:
cat << EOF > /etc/zypp/repos.d/handset.repo
[handset]
name=handset
enabled=1
autorefresh=0
baseurl=http://repo.meego.com/MeeGo/builds/trunk/daily/handset/repos/ia32/packages/
type=rpm-md
gpgcheck=1
gpgkey=file:/etc/pki/rpm-gpg/RPM-GPG-KEY-meego
EOF

====Refresh the packages list====
sudo zypper refesh
====Install the Handset Desktop packages====
sudo zypper in -t pattern meego-handset-base-support meego-handset-desktop
==How-To==
Now that you have the needed packages installed, we must tell uxlaunch (process that controls the user session startup environment and auto starts configured user session daemons and apps)
===Change uxlaunch configuration===
Edit the /etc/sysconfig/uxlaunch file and comment out the following, existing, entry
sudo sed -i.BAK -ne 's/$^#$$session=.*mcompositor.*$$/\2/g; s/$^session=.*mutter.*$$/#\1/g; p' /etc/sysconfig/uxlaunch
Add a new, Handset specific, entry that will start the windomanager used (mcompositor)
sudo sh -c "echo 'session=/usr/bin/mcompositor' >> /etc/sysconfig/uxlaunch"
===Restart user session===
# $ sudo reboot
#: OR
# $ sudo telinit 3; sleep 3; sudo telinit 5;
===Get correct resolution on IdeaPad===
Change the default target configuration by editing a gconf key:
gconftool-2 --set /meegotouch/target/name --type=string "slate"
The reset session as above

==TODO==
* Development of a single, cross-MeeGo, desktop switcher?
*: This would need to be Qt/Gnome agnostic or independent, since, today at least, the Netbook desktop is Gnome based, while the Handset one is Qt based.
*: Here's a simple script for starters that simply toggles between the Netbook and Handset desktops:

#!/bin/bash

NETBOOK_CMD="/usr/bin/mutter"
HANDSET_CMD="/usr/bin/mcompositor"
UXLAUNCH_CONF="/etc/sysconfig/uxlaunch"

CURRENT=$(grep -e "^session=" ${UXLAUNCH_CONF}|cut -d' ' -f1|sed -ne "s/^session=$.*$$/\1/p")

function sethandset {
sudo sed -i -ne 's/$^#$$session=.*mcompositor.*$$/\2/g; s/$^session=.*mutter.*$$/#\1/g; p' ${UXLAUNCH_CONF}
}

function setnetbook {
sudo sed -i -ne 's/$^#$$session=.*mutter.*$$/\2/g; s/$^session=.*mcompositor.*$$/#\1/g; p' ${UXLAUNCH_CONF}
}

[ $nocasematch ] || nocasematch=1
case "${CURRENT}" in
"${NETBOOK_CMD}" )
echo "Switching to Handset Desktop"
sethandset
;;
"${HANDSET_CMD}" )
echo "Switching to Netbook Desktop"
setnetbook
;;
*)
echo "Unknown desktop: \"$CURRENT\""
exit
;;
esac

Devices/Ideapad

2010-12-01T18:46:23Z

Ali1234: /* Accelerometer */

The Lenovo S10-3t IdeaPads were given to attendees of the [[MeeGo Conference 2010]] (Thanks Intel and Nokia!). This page aims to collect issues, solutions and hacks by the MeeGo Community for this device. It is mostly collected from the [http://forum.meego.com/showthread.php?t=1995 Lenovo S10-3t improvements] thread on MeeGo Forums.

== Major issues ==

It seems that some users get their wifi (and bluetooth) disabled and/or the battery status. There is some talk going on these two links, with work around that may or may not work. For the atheros folks it worked but the ones with broadcom it didn't.

* Problem: BROADCOM based wifi: No way to enable WiFi after switching it off using the switch
** Workaround: http://www.proli.net/2010/11/19/hidden-wifi-switches/
** Workaround: boot, BIOS setup, Load factory defaults, Save and exit
** Solution: Waiting for some help from Intel or BIOS updates from Lenovo.
* Problem: ATHEROS workaround: No way to enable WiFi after switching it off using the switch
** Workaround: http://forum.meego.com/showthread.php?p=13321
** Solution: Waiting for some help from Intel or BIOS updates from Lenovo.
* Problem: [http://bugs.meego.com/show_bug.cgi?id=3276 Resume from suspend to RAM does not work every time]
** Workaround:
** Solution:

== Minor issues ==
* Headphone jack doesn't work [http://bugs.meego.com/show_bug.cgi?id=10289 Bug report]
** Workaround: Add <code>options snd-hda-intel model="olpc-xo-1_5"</code> to <code>/etc/modprobe.d/alsa-base.conf</code> and reboot
** Solution: none yet

== Using the Ideapad with MeeGo ==

=== Finger scrolling with Chromium ===

The [https://chrome.google.com/extensions/detail/ncegfehgjifmmpnjaihnjpbpddjjebme ChromeTouch] extension enables kinetic scrolling with the browser and the touch screen.

=== Finger scrolling with Firefox ===

Firefox has a similar add-on: [http://addons.mozilla.org/firefox/addon/1250/ Grab and Drag]

=== On-screen keyboard ===

See the following resources
* [[Input Method Framework/MeeGo 1.1]]
* [http://blog.neteril.org/2010/11/19/turning-your-meego-lenovo-s10-3t-into-a-real-slate/ Turn your Lenovo into a real slate]
* [http://forum.meego.com/showthread.php?t=1803 forum thread]

=== Software Setup ===

The [[MeeGo 1.0 Netbook FAQ]] has resources on
* Application installation
* Dropbox
* Skype
* Codecs
* Changing keyboard layout post-install (since some of us accidently set it to US rather than UK)

*fennec-qt (Firefox Mobile)
** For fullscreen run: <code>fennec -target slate</code>

== Hardware Configuration ==

[http://consumersupport.lenovo.com/ie/en/DriversDownloads/drivers_list.aspx?CategoryID=45252 Chipset listing (for Windows Drivers)]

=== Touchpad ===

Taps are accepted as mouse presses but not the bottom left and right clicks, see [http://bugs.meego.com/show_bug.cgi?id=4807 bug report]

To enable RMB in the RightBottom corner of the touchpad issue the following command:
synclient RBCornerButton=3

To make it permanent edit /etc/X11/xorg.conf.d/10-input-synaptics.conf to:
Section "InputClass"
Identifier "synaptics"
MatchIsTouchpad "true"
Driver "synaptics"
Option "RBCornerButton" "3"
EndSection

=== Accelerometer ===

The Ideapad has a two axis accelerometer located in the keyboard part. Under Windows it is accessed through the APS software and used for screen rotation and parking the hard-drive under shock conditions. APS is widely used on Thinkpads and the Ideapad appears to have the same type of accelerometer. Accelerometer values are read through an "embedded controller" interface. Linux support for this device is normally provided by the [http://www.thinkwiki.org/wiki/Tp_smapi tp_smapi] driver, however, it has [http://www.thinkwiki.org/wiki/Tp_smapi#SL_series_and_IdeaPad no support for the Ideapad embedded controller].

=== 3G ===

[http://www.netbooks.ph/forums/viewtopic.php?f=56&t=2220 See this article about adding a 3G modem.]

Devices/Ideapad

2010-12-01T18:33:17Z

Ali1234:

The Lenovo S10-3t IdeaPads were given to attendees of the [[MeeGo Conference 2010]] (Thanks Intel and Nokia!). This page aims to collect issues, solutions and hacks by the MeeGo Community for this device. It is mostly collected from the [http://forum.meego.com/showthread.php?t=1995 Lenovo S10-3t improvements] thread on MeeGo Forums.

== Major issues ==

It seems that some users get their wifi (and bluetooth) disabled and/or the battery status. There is some talk going on these two links, with work around that may or may not work. For the atheros folks it worked but the ones with broadcom it didn't.

* Problem: BROADCOM based wifi: No way to enable WiFi after switching it off using the switch
** Workaround: http://www.proli.net/2010/11/19/hidden-wifi-switches/
** Workaround: boot, BIOS setup, Load factory defaults, Save and exit
** Solution: Waiting for some help from Intel or BIOS updates from Lenovo.
* Problem: ATHEROS workaround: No way to enable WiFi after switching it off using the switch
** Workaround: http://forum.meego.com/showthread.php?p=13321
** Solution: Waiting for some help from Intel or BIOS updates from Lenovo.
* Problem: [http://bugs.meego.com/show_bug.cgi?id=3276 Resume from suspend to RAM does not work every time]
** Workaround:
** Solution:

== Minor issues ==
* Headphone jack doesn't work [http://bugs.meego.com/show_bug.cgi?id=10289 Bug report]
** Workaround: Add <code>options snd-hda-intel model="olpc-xo-1_5"</code> to <code>/etc/modprobe.d/alsa-base.conf</code> and reboot
** Solution: none yet

== Using the Ideapad with MeeGo ==

=== Finger scrolling with Chromium ===

The [https://chrome.google.com/extensions/detail/ncegfehgjifmmpnjaihnjpbpddjjebme ChromeTouch] extension enables kinetic scrolling with the browser and the touch screen.

=== Finger scrolling with Firefox ===

Firefox has a similar add-on: [http://addons.mozilla.org/firefox/addon/1250/ Grab and Drag]

=== On-screen keyboard ===

See the following resources
* [[Input Method Framework/MeeGo 1.1]]
* [http://blog.neteril.org/2010/11/19/turning-your-meego-lenovo-s10-3t-into-a-real-slate/ Turn your Lenovo into a real slate]
* [http://forum.meego.com/showthread.php?t=1803 forum thread]

=== Software Setup ===

The [[MeeGo 1.0 Netbook FAQ]] has resources on
* Application installation
* Dropbox
* Skype
* Codecs
* Changing keyboard layout post-install (since some of us accidently set it to US rather than UK)

*fennec-qt (Firefox Mobile)
** For fullscreen run: <code>fennec -target slate</code>

== Hardware Configuration ==

[http://consumersupport.lenovo.com/ie/en/DriversDownloads/drivers_list.aspx?CategoryID=45252 Chipset listing (for Windows Drivers)]

=== Touchpad ===

Taps are accepted as mouse presses but not the bottom left and right clicks, see [http://bugs.meego.com/show_bug.cgi?id=4807 bug report]

To enable RMB in the RightBottom corner of the touchpad issue the following command:
synclient RBCornerButton=3

To make it permanent edit /etc/X11/xorg.conf.d/10-input-synaptics.conf to:
Section "InputClass"
Identifier "synaptics"
MatchIsTouchpad "true"
Driver "synaptics"
Option "RBCornerButton" "3"
EndSection

=== Accelerometer ===

The Ideapad has a two axis accelerometer located in the keyboard part. Under Windows it is accessed through the APS software and used for screen rotation and parking the hard-drive under shock conditions. APS is widely used on Thinkpads and the Ideapad appears to have the same type of accelerometer. Accelerometer values are read through an ACPI/BIOS interface. Linux support for this device is normally provided by the [http://www.thinkwiki.org/wiki/Tp_smapi tp_smapi] driver, however, it has [http://www.thinkwiki.org/wiki/Tp_smapi#SL_series_and_IdeaPad no support for the Ideapad BIOS].

=== 3G ===

[http://www.netbooks.ph/forums/viewtopic.php?f=56&t=2220 See this article about adding a 3G modem.]

Devices/Ideapad

2010-12-01T18:30:34Z

Ali1234:

The Lenovo S10-3t IdeaPads were given to attendees of the [[MeeGo Conference 2010]] (Thanks Intel and Nokia!). This page aims to collect issues, solutions and hacks by the MeeGo Community for this device. It is mostly collected from the [http://forum.meego.com/showthread.php?t=1995 Lenovo S10-3t improvements] thread on MeeGo Forums.

== Major issues ==

It seems that some users get their wifi (and bluetooth) disabled and/or the battery status. There is some talk going on these two links, with work around that may or may not work. For the atheros folks it worked but the ones with broadcom it didn't.

* Problem: BROADCOM based wifi: No way to enable WiFi after switching it off using the switch
** Workaround: http://www.proli.net/2010/11/19/hidden-wifi-switches/
** Workaround: boot, BIOS setup, Load factory defaults, Save and exit
** Solution: Waiting for some help from Intel or BIOS updates from Lenovo.
* Problem: ATHEROS workaround: No way to enable WiFi after switching it off using the switch
** Workaround: http://forum.meego.com/showthread.php?p=13321
** Solution: Waiting for some help from Intel or BIOS updates from Lenovo.
* Problem: [http://bugs.meego.com/show_bug.cgi?id=3276 Resume from suspend to RAM does not work every time]
** Workaround:
** Solution:

== Minor issues ==
* Headphone jack doesn't work [http://bugs.meego.com/show_bug.cgi?id=10289 Bug report]
** Workaround: Add <code>options snd-hda-intel model="olpc-xo-1_5"</code> to <code>/etc/modprobe.d/alsa-base.conf</code> and reboot
** Solution: none yet

== Using the Ideapad with MeeGo ==

=== Finger scrolling with Chromium ===

The [https://chrome.google.com/extensions/detail/ncegfehgjifmmpnjaihnjpbpddjjebme ChromeTouch] extension enables kinetic scrolling with the browser and the touch screen.

=== Finger scrolling with Firefox ===

Firefox has a similar add-on: [http://addons.mozilla.org/firefox/addon/1250/ Grab and Drag]

=== On-screen keyboard ===

See the following resources
* [[Input Method Framework/MeeGo 1.1]]
* [http://blog.neteril.org/2010/11/19/turning-your-meego-lenovo-s10-3t-into-a-real-slate/ Turn your Lenovo into a real slate]
* [http://forum.meego.com/showthread.php?t=1803 forum thread]

=== Software Setup ===

The [[MeeGo 1.0 Netbook FAQ]] has resources on
* Application installation
* Dropbox
* Skype
* Codecs
* Changing keyboard layout post-install (since some of us accidently set it to US rather than UK)

*fennec-qt (Firefox Mobile)
** For fullscreen run: <code>fennec -target slate</code>

== Hardware Configuration ==

[http://consumersupport.lenovo.com/ie/en/DriversDownloads/drivers_list.aspx?CategoryID=45252 Chipset listing (for Windows Drivers)]

=== Touchpad ===

Taps are accepted as mouse presses but not the bottom left and right clicks, see [http://bugs.meego.com/show_bug.cgi?id=4807 bug report]

To enable RMB in the RightBottom corner of the touchpad issue the following command:
synclient RBCornerButton=3

To make it permanent edit /etc/X11/xorg.conf.d/10-input-synaptics.conf to:
Section "InputClass"
Identifier "synaptics"
MatchIsTouchpad "true"
Driver "synaptics"
Option "RBCornerButton" "3"
EndSection

=== Accelerometer ===

The Ideapad has a two axis accelerometer located in the keyboard part. Under Windows it is accessed through the APS software and used for screen rotation and parking the hard-drive under shock conditions. APS is widely used on Thinkpads and the Ideapad appears to have the same type of accelerometer. Accelerometer values are read through an ACPI/BIOS interface. Linux support for this device is normally provided by the [http://www.thinkwiki.org/wiki/Tp_smapi tp_smapi] driver, however, it has [http://www.thinkwiki.org/wiki/Tp_smapi#SL_series_and_IdeaPad no support for the Ideapad BIOS].

MeeGo Conference 2010/Unconference/ARM

2010-11-09T12:12:39Z

Ali1234:

== When ==

This will happen as a BoF at http://conference2010.meego.com/session/bof-meego-arm

== Intents & Purposes ==

I plan to get together with like minded individuals at the unconference part of the MeeGo conference 2010 and talk about [[ARM|MeeGo on ARM]]. The idea is to sit down and discuss current state of the port of the MeeGo platform to the ARM architecture, problems, lessons learnt and future directions of MeeGo ARM and everything surrounding it (tool support, ecosystem, quality, documentation, etc.)

Chipset and SoC vendors, hobbyists, end-user product developers, OEM, ODMs, ISVs, porting engineers, toolchain engineers - everyone with an interest is more than welcome. - indicate your interest below!

== Like Minded Individuals ==

(Form: Name, IRC nickname if any, Affiliation, discussion topic)

* Carsten Munk, Stskeeps, Imogen Software - MeeGo Nokia N900 hardware adaptation team member - Topics: The above!
* Tomasz Sterna, smoku, hobbyist - MSM/QSD adaptation team member
* Randall Arnold, texrat - General interest in broad platform support
* Till Harbaum, harbaum - MeeGo on Beagleboard and similar plattforms
* George Ioakimedes, GeorgeIoak - Mostly TI OMAP based boards but open to other ARM solutions
* Jeremiah C. Foster, jeremiah, Pelagicore / GENIVI - ARM and Qemu, Integrating Linaro bits, integrating MeeGo IVI, GENIVI, etc.
* Timo Härkönen, timoph, Digia Plc - MeeGo QA-tools team member, general interest
* Jari Palojärvi, jpal, Nokia, MeeGo Porting Guide
* Jan-Simon Möller, dl9pf, The Linux Foundation, Toolchain/Qemu/OBS, broad platform support.
* Christian Daudt, csdb, Broadcom, ARM & MeeGo overall.
* Sivan Greenberg, sivang - Toolchain, quality, cross OS porting and general interest.
* Tero Kojo, tekojo, Nokia - Community interest, general interest
* Marko Saukko, Sage, Cybercom - MeeGo Nokia N900 hardware adaptation team member
* Mats Bergström, MatsBergstrom, ST-Ericsson, Community interest
* Tony Månsson, ST-Ericsson, MeeGo on ARM interest.
* Alison Chaiken, Alison_Chaiken, soon-to-be-Nokia, interests same as Möller
* Alistair Buxton, ali1234, - N900 adaption (dual boot etc) and broad platform support
<add your indication of interest here>

User:Ali1234

2010-09-26T02:48:30Z

Ali1234: /* MeeGo Proper */

= Finding SSSE3 Instructions in a Binary =

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep "$psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$"

= Emulating Missing Instructions in the Kernel =

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

= The Rules =

* Rule 1. You cannot use any MeeGo binary RPM
* Rule 2. You can use any binary RPM from any other distro you want
* Rule 3. You cannot edit anything on the OBS server after the build starts. The build must be completely automated from start to finish.

= Notes on Setting Up Private OBS (WIP) =
== Install OBS Appliance inside a VM ==
=== VM Config ===
Configure VM with two virtual disks. Primary 20GB for the appliance image and /home, secondary 100GB for OBS LVM partitions.

=== Install Appliance ===
Boot it with your favourite Linux live CD and write the appliance image to the first virtual disk:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.x86_64-2.0.5-Build1.8.raw.bz2
bunzip2 -c obs-server.x86_64-2.0.5-Build1.8.raw.bz2 > /dev/sda

=== Configure LVM ===
The Appliance system will search for OBS volumes, and if found it will use them for server storage and cache. If you create volumes for the workers, it will start worker processes too, all on the same system.

Use fdisk to make one big partition on /dev/sdb, type 8e:
fdisk /dev/sdb
Make LVM partition for server:
pvcreate /dev/sdb1
vgcreate "OBS" /dev/sdb1
lvcreate -L 70G -n "server" /dev/OBS
vgscan
mkfs /dev/OBS/server
For cache:
lvcreate -L 20G -n "cache" /dev/OBS
vgscan
mkfs /dev/OBS/cache
For two workers:
lvcreate -L 4G -n "worker_root_1" /dev/OBS
lvcreate -L 512M -n "worker_swap_1" /dev/OBS
lvcreate -L 4G -n "worker_root_2" /dev/OBS
lvcreate -L 512M -n "worker_swap_2" /dev/OBS
vgscan
mkfs /dev/OBS/worker_root_1
mkfs /dev/OBS/worker_root_2

Now eject the virtual CD device and reboot the VM into the appliance system.

== Customize the Appliance System ==

To login to the appliance hit enter on the console. Login is root, no password.

Install a sensible editor:

zypper in nano

Enable sshd:

chkconfig --add sshd

Tip: Don't bother trying to set the server to use a static IP address, it won't work. You have to set a static lease in your DHCP server instead.

== Set Up OBS ==

In order to build anything in OBS you need packages to build against. In theory you would be able to use the MeeGo repositories when they go public. However, you won't be able to use them unless your OBS server is Core 2 or better. In any case, since we need to bootstrap everything from scratch, it does not matter what we use for the initial builds. The simplest way to get started is to link to the openSUSE build service.

Log in to the OBS web interface running on port 80. Login is Admin, password is opensuse. Click "Setup OBS" to connect your OBS to the openSUSE public build service.

User:Ali1234

2010-09-26T02:48:17Z

Ali1234: /* Bootstrap MeeGo Toolchain */

User:Ali1234

2010-08-20T16:40:28Z

Ali1234:

User:Ali1234

2010-08-20T14:17:29Z

Ali1234:

= Finding SSSE3 Instructions in a Binary =

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep " $psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$ "

= Emulating Missing Instructions in the Kernel =

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

= The Rules =

* Rule 1. You cannot use any MeeGo binary RPM
* Rule 2. You can use any binary RPM from any other distro you want
* Rule 3. You cannot edit anything on the OBS server after the build starts. The build must be completely automated from start to finish.

= Notes on Setting Up Private OBS (WIP) =
== Install OBS Appliance inside a VM ==
=== VM Config ===
Configure VM with two virtual disks. Primary 20GB for the appliance image and /home, secondary 100GB for OBS LVM partitions.

=== Install Appliance ===
Boot it with your favourite Linux live CD and write the appliance image to the first virtual disk:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.x86_64-2.0.5-Build1.8.raw.bz2
bunzip2 -c obs-server.x86_64-2.0.5-Build1.8.raw.bz2 > /dev/sda

=== Configure LVM ===
The Appliance system will search for OBS volumes, and if found it will use them for server storage and cache. If you create volumes for the workers, it will start worker processes too, all on the same system.

Use fdisk to make one big partition on /dev/sdb, type 8e:
fdisk /dev/sdb
Make LVM partition for server:
pvcreate /dev/sdb1
vgcreate "OBS" /dev/sdb1
lvcreate -L 70G -n "server" /dev/OBS
vgscan
mkfs /dev/OBS/server
For cache:
lvcreate -L 20G -n "cache" /dev/OBS
vgscan
mkfs /dev/OBS/cache
For two workers:
lvcreate -L 4G -n "worker_root_1" /dev/OBS
lvcreate -L 512M -n "worker_swap_1" /dev/OBS
lvcreate -L 4G -n "worker_root_2" /dev/OBS
lvcreate -L 512M -n "worker_swap_2" /dev/OBS
vgscan
mkfs /dev/OBS/worker_root_1
mkfs /dev/OBS/worker_root_2

Now eject the virtual CD device and reboot the VM into the appliance system.

== Customize the Appliance System ==

To login to the appliance hit enter on the console. Login is root, no password.

Install a sensible editor:

zypper in nano

Enable sshd:

chkconfig --add sshd

Tip: Don't bother trying to set the server to use a static IP address, it won't work. You have to set a static lease in your DHCP server instead.

== Set Up OBS ==

In order to build anything in OBS you need packages to build against. In theory you would be able to use the MeeGo repositories when they go public. However, you won't be able to use them unless your OBS server is Core 2 or better. In any case, since we need to bootstrap everything from scratch, it does not matter what we use for the initial builds. The simplest way to get started is to link to the openSUSE build service.

Log in to the OBS web interface running on port 80. Login is Admin, password is opensuse. Click "Setup OBS" to connect your OBS to the openSUSE public build service.

== Bootstrap MeeGo Toolchain ==

Create a new project under your home: project called "bootstrap" and check it out using osc:

osc -A http://localhost:81 co home:Admin:bootstrap
cd home\:Admin\:bootstrap/

Import toolchain source rpms:

osc importsrcpkg -c ../binutils-2.20.51.0.2-17.2.src.rpm
osc importsrcpkg -c ../gcc-4.4.2-12.8.src.rpm
osc importsrcpkg -c ../glibc-2.11.90-18.7.src.rpm

Back on the OBS webpage, add Fedora_13 to "build repositories".

The OBS will think for a while, and then decide to compile binutils and gcc, and then glibc (hopefully) using the binutils and gcc it just built. But note that the gcc and binutils are still linked against the Fedora_13 glibc, so we rebuild them in the next step.

== MeeGo Proper ==

Create a new Project at home:Admin:MeeGo and check it out. Load in *all* the MeeGo source rpms. Tell it to use the home:Admin:bootstrap project as build repository. Now let the OBS do it's stuff. A long while later everything should have built. (In theory.)

User:Ali1234

2010-08-18T20:31:04Z

Ali1234: /* Bootstrap MeeGo Toolchain */

= Finding SSSE3 Instructions in a Binary =

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep " $psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$ "

= Emulating Missing Instructions in the Kernel =

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

= Notes on Setting Up Private OBS (WIP) =
== Install OBS Appliance inside a VM ==
=== VM Config ===
Configure VM with two virtual disks. Primary 20GB for the appliance image and /home, secondary 100GB for OBS LVM partitions.

=== Install Appliance ===
Boot it with your favourite Linux live CD and write the appliance image to the first virtual disk:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.x86_64-2.0.5-Build1.8.raw.bz2
bunzip2 -c obs-server.x86_64-2.0.5-Build1.8.raw.bz2 > /dev/sda

=== Configure LVM ===
The Appliance system will search for OBS volumes, and if found it will use them for server storage and cache. If you create volumes for the workers, it will start worker processes too, all on the same system.

Use fdisk to make one big partition on /dev/sdb, type 8e:
fdisk /dev/sdb
Make LVM partition for server:
pvcreate /dev/sdb1
vgcreate "OBS" /dev/sdb1
lvcreate -L 70G -n "server" /dev/OBS
vgscan
mkfs /dev/OBS/server
For cache:
lvcreate -L 20G -n "cache" /dev/OBS
vgscan
mkfs /dev/OBS/cache
For two workers:
lvcreate -L 4G -n "worker_root_1" /dev/OBS
lvcreate -L 512M -n "worker_swap_1" /dev/OBS
lvcreate -L 4G -n "worker_root_2" /dev/OBS
lvcreate -L 512M -n "worker_swap_2" /dev/OBS
vgscan
mkfs /dev/OBS/worker_root_1
mkfs /dev/OBS/worker_root_2

Now eject the virtual CD device and reboot the VM into the appliance system.

== Customize the Appliance System ==

To login to the appliance hit enter on the console. Login is root, no password.

Install a sensible editor:

zypper in nano

Enable sshd:

chkconfig --add sshd

Tip: Don't bother trying to set the server to use a static IP address, it won't work. You have to set a static lease in your DHCP server instead.

== Set Up OBS ==

In order to build anything in OBS you need packages to build against. In theory you would be able to use the MeeGo repositories when they go public. However, you won't be able to use them unless your OBS server is Core 2 or better. In any case, since we need to bootstrap everything from scratch, it does not matter what we use for the initial builds. The simplest way to get started is to link to the openSUSE build service.

Log in to the OBS web interface running on port 80. Login is Admin, password is opensuse. Click "Setup OBS" to connect your OBS to the openSUSE public build service.

== Bootstrap MeeGo Toolchain ==

Create a new project under your home: project called "bootstrap" and check it out using osc:

osc -A http://localhost:81 co home:Admin:bootstrap
cd home\:Admin\:bootstrap/

Import toolchain source rpms:

osc importsrcpkg -c ../binutils-2.20.51.0.2-17.2.src.rpm
osc importsrcpkg -c ../gcc-4.4.2-12.8.src.rpm
osc importsrcpkg -c ../glibc-2.11.90-18.7.src.rpm

Back on the OBS webpage, add Fedora_13 to "build repositories".

The OBS will think for a while, and then decide to compile binutils and gcc, and then glibc (hopefully) using the binutils and gcc it just built. But note that the gcc and binutils are still linked against the Fedora_13 glibc, so we rebuild them in the next step.

== MeeGo Proper ==

Create a new Project at home:Admin:MeeGo and check it out. Load in *all* the MeeGo source rpms. Tell it to use the home:Admin:bootstrap project as build repository. Now let the OBS do it's stuff. A long while later everything should have built. (In theory.)

User:Ali1234

2010-08-17T04:54:29Z

Ali1234: /* TODO */

= Finding SSSE3 Instructions in a Binary =

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep " $psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$ "

= Emulating Missing Instructions in the Kernel =

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

= Notes on Setting Up Private OBS (WIP) =
== Install OBS Appliance inside a VM ==
=== VM Config ===
Configure VM with two virtual disks. Primary 20GB for the appliance image and /home, secondary 100GB for OBS LVM partitions.

=== Install Appliance ===
Boot it with your favourite Linux live CD and write the appliance image to the first virtual disk:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.x86_64-2.0.5-Build1.8.raw.bz2
bunzip2 -c obs-server.x86_64-2.0.5-Build1.8.raw.bz2 > /dev/sda

=== Configure LVM ===
The Appliance system will search for OBS volumes, and if found it will use them for server storage and cache. If you create volumes for the workers, it will start worker processes too, all on the same system.

Use fdisk to make one big partition on /dev/sdb, type 8e:
fdisk /dev/sdb
Make LVM partition for server:
pvcreate /dev/sdb1
vgcreate "OBS" /dev/sdb1
lvcreate -L 70G -n "server" /dev/OBS
vgscan
mkfs /dev/OBS/server
For cache:
lvcreate -L 20G -n "cache" /dev/OBS
vgscan
mkfs /dev/OBS/cache
For two workers:
lvcreate -L 4G -n "worker_root_1" /dev/OBS
lvcreate -L 512M -n "worker_swap_1" /dev/OBS
lvcreate -L 4G -n "worker_root_2" /dev/OBS
lvcreate -L 512M -n "worker_swap_2" /dev/OBS
vgscan
mkfs /dev/OBS/worker_root_1
mkfs /dev/OBS/worker_root_2

Now eject the virtual CD device and reboot the VM into the appliance system.

== Customize the Appliance System ==

To login to the appliance hit enter on the console. Login is root, no password.

Install a sensible editor:

zypper in nano

Enable sshd:

chkconfig --add sshd

Tip: Don't bother trying to set the server to use a static IP address, it won't work. You have to set a static lease in your DHCP server instead.

== Set Up OBS ==

In order to build anything in OBS you need packages to build against. In theory you would be able to use the MeeGo repositories when they go public. However, you won't be able to use them unless your OBS server is Core 2 or better. In any case, since we need to bootstrap everything from scratch, it does not matter what we use for the initial builds. The simplest way to get started is to link to the openSUSE build service.

Log in to the OBS web interface running on port 80. Login is Admin, password is opensuse. Click "Setup OBS" to connect your OBS to the openSUSE public build service.

== Bootstrap MeeGo Toolchain ==

Create a new project under your home: project called "bootstrap" and check it out using osc:

osc -A http://localhost:81 cs home:Admin:bootstrap
cd home\:Admin\:bootstrap/

Import toolchain source rpms:

osc importsrcpkg -c ../binutils-2.20.51.0.2-17.2.src.rpm
osc importsrcpkg -c ../gcc-4.4.2-12.8.src.rpm
osc importsrcpkg -c ../glibc-2.11.90-18.7.src.rpm

Back on the OBS webpage, add Fedora_13 to "build repositories".

The OBS will think for a while, and then decide to compile binutils and gcc, and then glibc (hopefully) using the binutils and gcc it just built. But note that the gcc and binutils are still linked against the Fedora_13 glibc, so we rebuild them in the next step.

== MeeGo Proper ==

Create a new Project at home:Admin:MeeGo and check it out. Load in *all* the MeeGo source rpms. Tell it to use the home:Admin:bootstrap project as build repository. Now let the OBS do it's stuff. A long while later everything should have built. (In theory.)

User:Ali1234

2010-08-17T03:54:30Z

Ali1234: /* Notes on Setting Up Private OBS (WIP) */

= Finding SSSE3 Instructions in a Binary =

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep " $psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$ "

= Emulating Missing Instructions in the Kernel =

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

= Notes on Setting Up Private OBS (WIP) =
== Install OBS Appliance inside a VM ==
=== VM Config ===
Configure VM with two virtual disks. Primary 20GB for the appliance image and /home, secondary 100GB for OBS LVM partitions.

=== Install Appliance ===
Boot it with your favourite Linux live CD and write the appliance image to the first virtual disk:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.x86_64-2.0.5-Build1.8.raw.bz2
bunzip2 -c obs-server.x86_64-2.0.5-Build1.8.raw.bz2 > /dev/sda

=== Configure LVM ===
The Appliance system will search for OBS volumes, and if found it will use them for server storage and cache. If you create volumes for the workers, it will start worker processes too, all on the same system.

Use fdisk to make one big partition on /dev/sdb, type 8e:
fdisk /dev/sdb
Make LVM partition for server:
pvcreate /dev/sdb1
vgcreate "OBS" /dev/sdb1
lvcreate -L 70G -n "server" /dev/OBS
vgscan
mkfs /dev/OBS/server
For cache:
lvcreate -L 20G -n "cache" /dev/OBS
vgscan
mkfs /dev/OBS/cache
For two workers:
lvcreate -L 4G -n "worker_root_1" /dev/OBS
lvcreate -L 512M -n "worker_swap_1" /dev/OBS
lvcreate -L 4G -n "worker_root_2" /dev/OBS
lvcreate -L 512M -n "worker_swap_2" /dev/OBS
vgscan
mkfs /dev/OBS/worker_root_1
mkfs /dev/OBS/worker_root_2

Now eject the virtual CD device and reboot the VM into the appliance system.

== Customize the Appliance System ==

To login to the appliance hit enter on the console. Login is root, no password.

Install a sensible editor:

zypper in nano

Enable sshd:

chkconfig --add sshd

Tip: Don't bother trying to set the server to use a static IP address, it won't work. You have to set a static lease in your DHCP server instead.

== Set Up OBS ==

In order to build anything in OBS you need packages to build against. In theory you would be able to use the MeeGo repositories when they go public. However, you won't be able to use them unless your OBS server is Core 2 or better. In any case, since we need to bootstrap everything from scratch, it does not matter what we use for the initial builds. The simplest way to get started is to link to the openSUSE build service.

Log in to the OBS web interface running on port 80. Login is Admin, password is opensuse. Click "Setup OBS" to connect your OBS to the openSUSE public build service.

== TODO ==

* Compile MeeGo's gcc and binutils against openSUSE
* Compile MeeGo's libc, gcc, binutils with the toolchain made in the previous step
* Compile all the rest of MeeGo against the packages created in the previous step

User:Ali1234

2010-08-17T03:47:51Z

Ali1234: /* Install Appliance */

= Finding SSSE3 Instructions in a Binary =

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep " $psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$ "

= Emulating Missing Instructions in the Kernel =

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

= Notes on Setting Up Private OBS (WIP) =
== Install OBS Appliance inside a VM ==
=== VM Config ===
Configure VM with two virtual disks. Primary 20GB for the appliance image and /home, secondary 100GB for OBS LVM partitions.

=== Install Appliance ===
Boot it with your favourite Linux live CD and write the appliance image to the first virtual disk:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.x86_64-2.0.5-Build1.8.raw.bz2
bunzip2 -c obs-server.x86_64-2.0.5-Build1.8.raw.bz2 > /dev/sda

=== Configure LVM ===
The Appliance system will search for OBS volumes, and if found it will use them for server storage and cache. If you create volumes for the workers, it will start worker processes too, all on the same system.

Use fdisk to make one big partition on /dev/sdb, type 8e:
fdisk /dev/sdb
Make LVM partition for server:
pvcreate /dev/sdb1
vgcreate "OBS" /dev/sdb1
lvcreate -L 70G -n "server" /dev/OBS
vgscan
mkfs /dev/OBS/server
For cache:
lvcreate -L 20G -n "cache" /dev/OBS
vgscan
mkfs /dev/OBS/cache
For two workers:
lvcreate -L 4G -n "worker_root_1" /dev/OBS
lvcreate -L 512M -n "worker_swap_1" /dev/OBS
lvcreate -L 4G -n "worker_root_2" /dev/OBS
lvcreate -L 512M -n "worker_swap_2" /dev/OBS
vgscan
mkfs /dev/OBS/worker_root_1
mkfs /dev/OBS/worker_root_2

Now eject the virtual CD device and reboot the VM into the appliance system.

== Customize the Appliance System ==

To login to the appliance hit enter on the console. Login is root, no password.

Install a sensible editor:

zypper in nano

Enable sshd:

chkconfig --add sshd

Tip: Don't bother trying to set the server to use a static IP address, it won't work. You have to set a static lease in your DHCP server instead.

== Set Up OBS ==

In order to build anything in OBS you need packages to build against. In theory you would be able to use the MeeGo repositories when they go public. However, you won't be able to use them unless your OBS server is Core 2 or better. In any case, since we need to bootstrap everything from scratch, it does not matter what we use for the initial builds. The simplest way to get started is to link to the openSUSE build service.

Log in to the OBS web interface running on port 80. Login is Admin, password is opensuse. Click "Setup OBS" to connect your OBS to the openSUSE public build service.

User:Ali1234

2010-08-17T00:22:25Z

Ali1234: /* Configure LVM */

= Finding SSSE3 Instructions in a Binary =

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep " $psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$ "

= Emulating Missing Instructions in the Kernel =

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

= Notes on Setting Up Private OBS (WIP) =
== Install OBS Appliance inside a VM ==
=== VM Config ===
Configure VM with two virtual disks. Primary 20GB for the appliance image and /home, secondary 100GB for OBS LVM partitions.

=== Install Appliance ===
Boot it with your favourite Linux live CD and write the appliance image to the virtual disk:
wget http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.x86_64-2.0.5-Build1.8.raw.bz2
bunzip2 -c obs-server.x86_64-2.0.5-Build1.8.raw.bz2 > /dev/sda

=== Configure LVM ===
The Appliance system will search for OBS volumes, and if found it will use them for server storage and cache. If you create volumes for the workers, it will start worker processes too, all on the same system.

Use fdisk to make one big partition on /dev/sdb, type 8e:
fdisk /dev/sdb
Make LVM partition for server:
pvcreate /dev/sdb1
vgcreate "OBS" /dev/sdb1
lvcreate -L 70G -n "server" /dev/OBS
vgscan
mkfs /dev/OBS/server
For cache:
lvcreate -L 20G -n "cache" /dev/OBS
vgscan
mkfs /dev/OBS/cache
For two workers:
lvcreate -L 4G -n "worker_root_1" /dev/OBS
lvcreate -L 512M -n "worker_swap_1" /dev/OBS
lvcreate -L 4G -n "worker_root_2" /dev/OBS
lvcreate -L 512M -n "worker_swap_2" /dev/OBS
vgscan
mkfs /dev/OBS/worker_root_1
mkfs /dev/OBS/worker_root_2

Now eject the virtual CD device and reboot the VM into the appliance system.

== Customize the Appliance System ==

To login to the appliance hit enter on the console. Login is root, no password.

Install a sensible editor:

zypper in nano

Enable sshd:

chkconfig --add sshd

Tip: Don't bother trying to set the server to use a static IP address, it won't work. You have to set a static lease in your DHCP server instead.

== Set Up OBS ==

In order to build anything in OBS you need packages to build against. In theory you would be able to use the MeeGo repositories when they go public. However, you won't be able to use them unless your OBS server is Core 2 or better. In any case, since we need to bootstrap everything from scratch, it does not matter what we use for the initial builds. The simplest way to get started is to link to the openSUSE build service.

Log in to the OBS web interface running on port 80. Login is Admin, password is opensuse. Click "Setup OBS" to connect your OBS to the openSUSE public build service.

User:Ali1234

2010-08-16T23:16:01Z

Ali1234: /* Set Up OBS */

User:Ali1234

2010-08-16T23:01:43Z

Ali1234: /* Notes on Setting Up Private OBS (WIP) */

User:Ali1234

2010-08-16T22:52:07Z

Ali1234: /* Notes on Setting Up Private OBS (WIP) */

User:Ali1234

2010-08-16T21:16:39Z

Ali1234: /* Notes on Setting Up Private OBS (WIP) */

User:Ali1234

2010-08-16T02:07:48Z

Ali1234:

User:Ali1234

2010-08-14T22:14:30Z

Ali1234: Created page with "== Finding SSSE3 Instructions in a Binary == I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions objdump --disassemble-all <binary> | grep " \(psign[…"

== Finding SSSE3 Instructions in a Binary ==

I came up with this using http://en.wikipedia.org/wiki/SSSE3#New_Instructions

objdump --disassemble-all <binary> | grep " $psign[bwd]\|pabs[bwd]\|palignr\|pshufb\|pmulhrsw\|pmaddubsw\|phsub[wd]\|phsubsw\|phadd[wd]\|phaddsw$ "

== Emulating Missing Instructions in the Kernel ==

arjan: you can emulate instructions your cpu does not have quite well
ali1234: i didn't know there was such a patch... link please?
arjan: either via a kernel hack or an ld preload library
arjan: http://lkml.indiana.edu/hypermail/linux/kernel/0206.3/0631.html <-- old kernel hack that google found for me
arjan: doing it as ld preload isn't too hard .. SIGILL is sent when an instruction is executed that the cpu does not grok
ali1234: ah so you don't know that it exists specifically for ssse3?
arjan: for ssse3? not that I know of
arjan: but you could add the ssse3 instructions if you want
arjan: shouldn't be too hard

Build Infrastructure/Sysadmin Distro/OBS1.8 setup openSUSE112

2010-08-13T01:31:08Z

Ali1234: Add missing ">" in example command

<p>
These steps are to setup Open Build Service 1.8 on an openSuSE 11.2 installation. Currently this document describes how to setup an evaluation/test setup and is not meant as a production setup.
</p>
<p>
Most users won't need to install their own OBS and can just use an account on a publicly accessible OBS. Once public access is allowed to the global MeeGo OBS, there will be a link to obtain access.
</p>
<p>
There are cases where vendors may rather have full control of their builds and keep source private due to licensing restrictions, etc. These instructions are for these special cases.
</p>
<p>
MeeGo will switch to [http://lists.opensuse.org/opensuse-buildservice/2010-05/msg00094.html version 1.8] of the Build Service which is now released. These instructions cover the new 1.8 release.
</p>

<h2>Add Repositories</h2>

First, we have to add the openSUSE:Tools and OpenSUSE:Tools:Meego repository to zypper.

<code>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
wget http://download.opensuse.org/repositories/openSUSE:/Tools:/MeeGo/openSUSE_11.2/openSUSE:Tools:MeeGo.repo
zypper ref
</code>

Accept the trust key.
change priority to avoid installing obs 2.0:

<code>
zypper mr -p 60 openSUSE_Tools_MeeGo
zypper mr -r openSUSE_Tools_MeeGo
zypper ref
</code>

<h2>Setup the Client</h2>
<h3>Install the Client Packages</h3>

*For obs worker:
<code>
zypper in obs-worker qemu-devel mount-static bash-static
</code>

<h3>Point To The Server</h3>
<p>
Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server. (The example server is 192.168.1.1)
</p>
<code>
# vi /etc/sysconfig/obs-worker
OBS_SRC_SERVER="192.168.1.1:5352"
OBS_REPO_SERVERS="192.168.1.1:5252"
</code>

<h3>Start the Client</h3>
<p>Start the worker service
</p>
<code>
chkconfig --add obsworker
rcobsworker start
</code>

<p>
This is enough to build packages, but there are security concerns of running just qemu for builds. You can setup the build machines to use either KVM or Xen. Chose one and follow the instructions below. Most people use KVM.
</p>

<code>
# yast2
</code>
<p>
Within YaST2 Control Center, there is a <b>Virtualization</b> option on the left which makes available an <b>Install Hypervisor and Tools</b> option on the right. Install the tools and setup a bridge ethernet device. Be suer to change the default route to use br0.
</p>
<h3>KVM</h3>
<p>
Only install KVM or Xen, not both. Only one will be used at a time.
</p>
<code>
# yast -i kvm virt-manager
# chkconfig libvirtd on
</code>
<p>
Reboot. If you run <b>ps aux|grep bs_worker</b>, the worker should now have a <i>--kvm</i> option within the command.
</p>
<h3>Xen</h3>
<p>
Only install KVM or Xen, not both. Only one will be used at a time.
</p>
<p>
Reboot the machine and be sure to select the Xen kernel in the grub menu. If you run <b>ps aux|grep bs_worker</b>, the worker should now have a <i>--xen</i> option within the command.
</p>
<h2>Setup the server</h2>

<h3>Install the Server packages</h3>

*For server:
<code>
zypper in obs-server obs-signer obs-utils createrepo nfs-client obs-api memcached lighttpd
</code>

<h3>MySQL Setup</h3>
Start daemon by default:
<code>
chkconfig --add mysql
rcmysql start
</code>

Secure the installation
<code>
/usr/bin/mysql_secure_installation
</code>

Create the databases:
<code>
mysql -u root -p
mysql> create database api_production;
mysql> create database webui_production;
</code>

Add the obs user for these databases (substitute the correct password in):

<code>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</code>

Now, configure OBS to use MySQL, first the API server.

<code>
vi /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</code>
And setup the webui to use MySQL...
<code>
vi /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</code>

Populate the database
<code>
cd /srv/www/obs/api/
RAILS_ENV="production" rake db:migrate

cd /srv/www/obs/webui/
RAILS_ENV="production" rake db:migrate
</code>
If this fails, check /srv/www/obs/api/config/environments/production.rb and /srv/www/obs/webui/config/environments/production.rb for configuration of the SOURCE_HOST and FRONTEND_HOST.

<h3>Setup lighttpd for webui</h3>
Make sure vhosts are enabled by uncommenting the following line:
<code>
# vi /etc/lighttpd/lighttpd.conf
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</code>
Setup the regular webui on 80, api on 81, and 82 is the repository.
<code>
vi /etc/lighttpd/vhosts.d/obs.conf
$SERVER["socket"] == ":80" {
rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/webui/log"
include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":81" {
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":82" {
server.name = "192.168.1.1"
server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}

</code>
<p>
lighttpd requires some extra modules to be enabled: mod_access, mod_rewrite, mod_magnet, and mod_fastcgi. Do so by editing /etc/lighttpd/modules.conf:
</p>
<code>
# vi /etc/lighttpd/modules.conf
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</code>

<p>
You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:
</p>
<code>
# vi /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "192.168.1.1"
FRONTEND_PORT = 81
FRONTEND_PROTOCOL = 'http'
BUGZILLA_HOST = nil
DOWNLOAD_URL = "http://192.168.1.1:82"
ICHAIN_MODE = "off"
BASE_NAMESPACE = nil
</code>

<p>
Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:
</p>
<code>
# vi /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "192.168.1.1"
</code>

<p>
Add the server to start by default.
</p>
<code>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed
</code>

<p>
ligthttpd user and group need to be the onwer of api and webui dirs (as well as log and tmp):
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>

<h3>BSConfig.pm</h3>
<p>
The file <i>/usr/lib/obs/server/BSConfig.pm</i> is used to configure several settings for the Build Service. One of the major components is setting up the $hostname variable to the correct value. Currently I have this set to the IP address of the server.
</p>

<code>
my $hostname = '192.168.1.1';
</code>

<p>
The list of directories in /srv/obs/repos/ is the repositories, so I changed the $repodownload:
</p>

<code>
our $repodownload = "http://$hostname:82/";
</code>

<h3>Verification</h3>
<p>
Start the lighttpd server.
</p>
<code>
rclighttpd start
</code>
<p>
At this point you should be able to open a browser and go to your server and login to OBS. Port 80 should be the webui, port 81 should be the api, and port 82 should be the repository directory. The default username/password is Admin/opensuse.
</p>
<h3>Start By Default</h3>

<p>The OBS should start automatically, so they should be added to chkconfig to do so:</p>
<code>
chkconfig --add obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher obswarden obssigner obsapidelayed obswebuidelayed
</code>

<h2>Setting up Cross Compile</h2>
<h3>Configure build types</h3>
<p>
To setup cross compile, add the appropriate machine types to /etc/sysconfig/obs-server. For example, the following will enable ARM builds.
</p>
<code>
# vi /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 armv5el armv7el“
</code>

<h2>Cloning Repositories</h2>

<h3>prj and prjconf</h3>
<p>The project settings and the project config is an important part of the project and should be copied to the local project setup.</p>
<p>
The prj and prjconf settings are available from [http://meego.gitorious.org/meego-developer-tools/obs-project-config the git tree] or directly from the OBS server:
</p>
<code>
osc -A <remote API URL> meta prj <repository name> > prj.txt
osc -A <remote API URL> meta prjconf <repository name> > prjconf.txt
</code>
<p>
To clone Trunk off MeeGo's api server: <remote API URL> is http://api.meego.com and <repositor name> is Trunk, for example.
</p>
<p>
Modify the prj.txt file to name valid users in the userid fields. Once modified, the settings and configuration can be applied to the local project.
</p>
<code>
osc -A <local API URL> meta prj <repository name> -F prj.txt
osc -A <local API URL> meta prjconf <repository name> -F prjconf.txt
</code>
<p>
In this setup page, the <local API URL> is http://192.168.1.1:81. Continuing on with the previous example, the <repository name> would be Trunk again.
</p>
<h3>Mirror</h3>
<p>
obs_mirror_project (/usr/sbin/obs_mirror_project) is used to copy an external OBS project. The script needed to be modified to use build.meego.com as apposed to the hard coded download.opensuse.org site. You need an login to build.meego.com to execute this script.
</p>
<code>
/usr/sbin/obs_mirror_project <repository name> <type> <arch>
</code>

<h3>Rescan Repository</h3>
<p>Once the download of the project is complete, you have to rescan the local repository.</p>
<code>
/usr/lib/obs/server/bs_admin --rescan-repository <repository name> <type> <arch>
</code>

<h2>Troubleshooting</h2>
<p>
Here are common issues that have been seen and how to resolve them.
</p>

<h3>HTTP Error 500</h3>
<p>
Check <b>/srv/www/obs/api/config/environments/production.rb</b>
and <b>/srv/www/obs/webui/config/environments/production.rb</b> for configuration of the
<b>SOURCE_HOST</b> and <b>FRONTEND_HOST</b>.
</p>
<h3>Cannot load person data for Admin in application_helper</h3>
<p>
Make sure you set the permissions on the api and webui directories.
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>
<p>
If this doesn't work then try to recreate the databases:
</p>
<code>
# mysql -u root -p
mysql> drop database api_production;
mysql> drop database webui_production;
</code>
<p>
Rerun the mysql database setup from above and re-run rake.
</p>
----
<h2>External Links</h2>
<p>
<ul>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Installation Maemo OBS Installation]
</li>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup Maemo Fremantel Setup]
</li>
</ul>
</p>
----
[[User:Liam | Liam]]

[[User:Dl9pf | Dl9pf]]

[[Category:Build Infrastructure]]

Devices/nonSSSE3

2010-08-12T15:06:30Z

Ali1234: /* Interested Parties */

=MeeGo on nonSSSE3 x86 Hardware=

This page was inspired by a discussion on #meego ([http://mg.pov.lt/meego-irclog/%23meego.2010-08-11.log.html#t2010-08-11T21:17:58 log@21:17]) regarding MeeGo support of nonSSSE3 based hardware.

lbt added to the discussions with a timely blog post he had been working on http://mer-l-in.blogspot.com/2010/08/are-intel-subverting-meegocom.html.

=Tasks=

* Requirements
** Proof of concept - create prjconf on maemo OBS to build gcc,binutils, rest of core and bring up on x86 hw/vbox/vmware
** Build daily, weekly, release builds of MeeGo core,netbook,extra packages for nonSSSE3 based hardware
** Create repos of the built packages
** Generate kickstart file for common x86 target(s)
** Generate images from kickstart files
** Create a repository in OBS for appdevs to build against
* Implementation
** OBS
** IMG
** BOSS
* Testing
** http://wiki.meego.com/Quality/NetbookTestReport/NetbookSanity20100810

=Release Kickstart Files=

*Links to kickstart files
**Daily
**Weekly
**Releases

=Release Images=

*Links to images for x86 target(s)
**Daily
**Weekly
**Releases

=Interested Parties=

Add your #meego IRC nick below :-

*vgrade
*lcuk
*CosmoHill
*slaine
*lbt
*w00t/w00t_
*jmc93739653
*ali1234