Marcin Juszkiewicz

There will be Linaro Connect Asia next week. Which means: I am going to Hong Kong today. 21-22 hours trip like usual. This time through Helsinki ;)

But recently I started to count and got quite long list of Linaro events I attended so far:

• 2010.05 UDS/M - Brussels, Belgium
• 2010.07 Ubuntu/Linaro sprint in Prague, Czech Republic
• 2010.10 UDS/N - Orlando, FL, USA
• 2011.01 Ubuntu/Linaro sprint in Dallas, TX, USA
• 2011.05 LC + UDS/O - Budapest, Hungary
• 2011.07 Ubuntu/Linaro sprint in Dublin, Ireland
• 2011.10 LC + UDS/P - Orlando, FL, USA
• 2012.02 LC - Redwood City, CA, USA
• 2012.05 LC - Hong Kong, China
• 2012.11 LC + UDS/R - Copenhagen, Denmark

The “Linaro Connect” name is quite young and I do not remember which event got this name first. There will be three of them this year: Asia, Europe, US. But when and where? Do not ask me cause so far it was not announced yet.

So if any of my readers will be in Hong Kong next week — please say hi. And there will be Chromebook hacking session on Tuesday at 15:00 in Fountain 1 room (but please check schedule/ask me if not changed).

That day had to come. It was just a matter of time. Debian bootstrapped new architecture port using just own tools and packages…

It was long trip. During last few years we saw bigger amount of work spent in Debian/Ubuntu on cross building packages. Then were Google Summer of Code projects on bootstrapping Debian and one for multiarch cross toolchains. And we had Wookey with his ideas, knowledge and abilities to get one thing to work on for months in a way that managers were agreeding that it needs another month and another ;)

And today I found an email from Wookey about AArch64 port. I suggest you to read it as it has a lot of information. You can find ready to use rootfs there which (connected with kernel from OpenEmbedded) boots to fresh Ubuntu 13.04:

Ubuntu Raring Ringtail (development branch) localhost ttyAMA0

localhost login: root
Last login: Thu Jan  1 00:07:37 UTC 1970 on ttyAMA0
Welcome to Ubuntu Raring Ringtail (development branch) (GNU/Linux 3.8.0 aarch64)

 * Documentation:  https://help.ubuntu.com/
root@localhost:~# uname -a
Linux localhost 3.8.0 #1 SMP Wed Feb 20 14:31:07 CET 2013 aarch64 aarch64 aarch64 GNU/Linux

You need to have patience as Upstart needs to run lot of stuff before it gives login prompt.

Still lot of work required as there are many patches to packaging waiting for being merged but I think that it is a big day for Debian and all distributions derived from it.

There are many users of so-called Chrubuntu which have Ubuntu 12.04 running on their Samsung ARM Chromebooks. And I do not support them with any updates so they wonder how to upgrade to 13.04 release. So I decided to spend some time and help with it.

For this I installed Chrubuntu 12.04 on SD card (not on internal as I have own installation of Ubuntu there) and I will go though upgrade to 13.04 and document all steps here.

First thing: if your Chrubuntu installation fails on fetching 4.7MB of “ubuntu-1204-binak.bz2” file then you probably started script with “sh” instead of “bash”. Abort process and run it with “bash” — it really needs it.

But ok, you got your Chromebook booted to Ubuntu desktop (running Unity 2D). Remember: your password is “user”. Open terminal (Ctrl+LAlt+t), get root and edit APT sources so they will point to “raring” instead of “precise”. Now refresh APT data and run distro upgrade (I used “apt-get dist-upgrade“).

There may be some issues during upgrade. I had to run “apt-get -f install” and it removed some packages including “unity” and “ubuntu-desktop”. To get them back I needed “apt-get install ubuntu-desktop gnome-control-center nautilus nautilus-share nautilus-sendto eog unity libgnome-desktop-3.4 gnome-settings-daemon” command.

Next step is adding ARM Chromebook hackers PPA: “sudo add-apt-repository ppa:chromebook-arm/ppa” and again updating APT cache.

Now it is time to install Ubuntu kernel and tools: “apt-get install cgpt vboot-kernel-utils linux-image-chromebook“. During installation you will get “Warning: root device does not exist” message during creation of initrd image. Just ignore that and then remove “flash-kernel” package.

Time to sign kernel. Create file with kernel command line. I suggest “console=tty1 printk.time=1 quiet nosplash rootwait root=/dev/mmcblk1p7 rw rootfstype=ext4″ but you can adapt it as you want. Sign kernel: “vbutil_kernel --pack /tmp/kernel-to-boot-ubuntu --keyblock /usr/share/vboot/devkeys/kernel.keyblock --version 1 --signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk --config CMDLINE_FILE --vmlinuz /boot/vmlinuz-3.4.0-5-chromebook --arch arm“. And do not forget to write it to SD: “dd if=/tmp/kernel-to-boot-ubuntu of=/dev/mmcblk1p6 bs=4M“.

Time to reboot to 13.04. Less kernel messages on console then before but blue screen instead of Unity desktop ;( Good that “Ctrl-LAlt-1” switches us to text console.

Login as “user” (password is “user” as I mentioned earlier), gain root and install “chromium-mali-opengles” package. Now “restart lightdm” and check how X11 looks this time. Still blue? Switch back to text console then.

Now it is time to enable “universe” part of repository (I though that it is enabled by default). Edit “/etc/apt/sources.list” file and uncomment proper lines. Now we can install “armsoc” X11 display driver. Here you can curse at me — package in repository lacks Exynos5 part of xorg.conf ;(

But this does not change situation — still no Unity. At this moment I can recommend XFCE instead. Install “xubuntu-desktop” (181MB of disk space needed).

Ok, time to switch default session to Xubuntu one. Edit “/etc/lightdm/lightdm.conf” and set “user-session” to “xubuntu”. Save and “restart lightdm“. Now you should land in XFCE session.

Are icons broken? If yes then you probably need to complete distribution upgrade. I had 725 packages to process… Once it done — restart X11 session.

So now I have working XFCE desktop with latest kernel. OpenGLES is not working but I have to check why.

Was it hard?

UPDATE: fixed OpenGL ES package name and improved formating so -- were preserved. UPDATE 2: fixed PPA name and partition number.

Today I work from Berlin (visiting Daniel Holbach) and took only Chromebook with me to check how bad/good it works as laptop replacement for me.

First issues appeared during first minutes. It was keyboard. Or rather keys which are missing there. XFCE terminal (my main tool) switches between tabs with Ctrl-PgUp/PgDn but I lack those keys. Good that I can edit GTK shortcuts. But remove of them is possible only with Delete key. And guess what — Chromebook lacks it as well ;D So I used some crazy Emacs like shortcuts (Ctrl-LAlt-Shift-something).

Good thing is support for 5GHz WiFi. I have to consider such change at home and provide not only 2.4GHz but also 5GHz network (I have around twenty 802.11g ones at home).

Terrible issue is power plug detection. I took Chromebook from backpack, booted it and got “97% charged, AC connected” message during work on battery. It is serious problem as no one likes to have random shutdowns just because battery went flat.

So there are few things to do:

• better keymap
• fixed power state detection

And then I can go to Hong Kong (for Linaro Connect Asia) with Chromebook only.

Installing recent Ubuntu on Samsung ARM Chromebook is not rocket science. All you need is following steps.

So which steps there are? Note that I will describe only installation on SD card and assume some level of knowledge from reader — that’s why there are steps where exact commands are not given as you can use different tools.

1. Partition SD card with GPT. First partition needs type “7f00” (ChromiumOS kernel) and 4MB is enough. Second is “8300” type and should be enough to fit rootfs (or bigger).
2. Create ext4 filesystem on second partition.
3. Create rootfs — debootstrap, multistrap etc. You can do it directly to SD card partition to save copying later. You can also fetch any existing one.
4. Chroot into rootfs (you can do it from terminal under Chrome OS).
5. Add “Samsung Chromebook (ARM) support packages” PPA into APT sources.
6. Install “cgpt”, “vboot-utils”, “linux-chromebook”, “xserver-xorg-video-armsoc” packages.
7. Create file with kernel command line. I suggest “console=tty1 printk.time=1 quiet nosplash rootwait root=/dev/mmcblk1p2 rw rootfstype=ext4” but you can adapt it as you want.
8. Sign kernel: “vbutil_kernel —pack /tmp/kernel-to-boot-ubuntu —keyblock /usr/share/vboot/devkeys/kernel.keyblock —version 1 —signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk —config CMDLINE_FILE —vmlinuz /boot/vmlinuz-3.4.0-5-chromebook —arch arm”
9. Write kernel to SD: “dd if=/tmp/kernel-to-boot-ubuntu of=/dev/mmcblk1p1 bs=4M”.
10. Mark kernel as good: “cgpt add -S 1 -T 5 -P 12 -i 1 /dev/mmcblk1”
11. Copy WiFi firmware from Chrome OS — it is /lib/firmware/mrvl/sd8797_uapsta.bin file.
12. Last chance to burn your speakers cause Ubuntu will not give that functionality…
13. Reboot.
14. Press Ctrl-U at that scary white screen.
15. Enjoy your Ubuntu system.
16. You may also add symlink for Samsung media framework: “cd /lib/firmware/;ln -sf s5p-mfc/s5p-mfc-v6.fw mfc_fw.bin”. But so far nothing uses it.

Note that you may have different results due to other rootfs used. I ran “debootstrap” and then chrooted, installed “xubuntu-desktop” and lot of other packages I use for development.

Recently I got more and more questions how to upgrade from Chrubuntu to Ubuntu 13.04 to get my updates. So I think that it is a time for me to check how to do it.

I will book some time during weekend for playing with Chrubuntu installation on SD card and upgrading it to latest and greatest packages. Will post how it went and which bugs I got during process and how to fix/workaround them.

As usual I will not cover sound cause I do not have speakers in Chromebook.

Nine years ago I bought Sharp Zaurus SL-5500 as my first Linux PDA. And due to this I am where I am.

I could say that it started two years earlier when I saw PalmOS devices at local geek meetings. But it took me over year before Palm m105… Then was Sony Clie SJ30 — gorgeous device. High resolution, memory card, 16bit colour. Too bad that applications did not make use of it.

So I went for Linux. There were two options: Zaurus or iPaq. Went for former one as it had keyboard. It was good choice.

Quickly started development of packages and joined OpenEmbedded team. Then became one of OpenZaurus developers. After year or something took over release maintenance and released few last versions. 3.5.4(.1) were the best tested releases of OZ ever — I had over hundred testers for each RC image and they provided installation reports, bug reports and fixes. And it had unified installer for whole range of devices (took me several months to get it polished and few guys added own tweaks). When Ångström distribution started I was the one who officially ended OpenZaurus development.

And all that was in free time. But in mean time I created my consulting company. CELF was my first customer ;)

One nice evening I got question on irc and due to that I left dark side of IT and went from PHP programming to embedded Linux full-time. OpenedHand had interesting projects and clients with many devices. Imagine operating system + kernel + Python + GStreamer in 16 megabytes of flash… And I managed to get it done. While working for them I used proper developer boards (not only customer devices) and there were funny moments…

When we worked with ST Microelectronics on NDK-15 (later replaced by NHK-15 from ST Ericsson) I had to merge two kernel trees from two separate teams. Took me 2 days of mangling 20-30MB diffs but got it done. There are people at ST-E which reminded me this during one of Linaro Connects ;D

Also on GUADEC 2007 when we presented new interface for Openmoko phones NDK-15 had to wait for me as no one at stand was able to get it running (U-Boot config needed changes).

But then Intel acquired OpenedHand… The craziest trip of my life was return from London to my parents place. For three months I even had @linux.intel.com email but never used it due to problems with Intel corporate network and Linux (do not ask).

Next was Bug Labs and their BUG device. I cleaned their Poky trees, migrated to latest version and later to use OpenEmbedded directly. Less challenges but I also had few other customers at that time to keep me busy. Some of them were OH customers before and went to me for help.

Time passed, 2010 came. One day Canonical made another attempt to seduce me and this time I decided that it looks like good opportunity so I accepted. Sent BUG 2.0 prototype back to NYC and few weeks later I made crazy train trip to small nowhere near Brussels to meet my new coworkers from NewCore. 1-2 weeks later we got our current name: Linaro.

Total change… From embedded devices to ‘Yes, it is ARM. So what?’ kind as we support(ed) devices powerful enough to run normal desktop software. Many changes for me — from OpenEmbedded where you can (cross) build everything in few hours to Ubuntu packaging where sending package for inclusion into archive meant few hours of buildd queue and then few of build. But I learnt a lot here and met another set of hackers including grey beards ones ;)

And all that because I bought Sharp Zaurus SL-5500 nine years ago…

Few days ago was my wife’s birthday. As a gift I gave her new laptop — Acer Aspire One 722. With last released version of Ubuntu on it (with XFCE desktop).

As I got device two weeks earlier I had some time to play with it and do setup. Installed full XFCE desktop (xubuntu-desktop), LibreOffice, XBMC with set of plugins for Polish VOD services, VLC etc. No games as requested. Firefox + Thunderbird as default browser and MUA.

And then there was a day. I gave Ania laptop box with some Belgium chocolates inside (instead of computer) and when we stopped laughing I gave her new notebook in useful case. After coffee I started to migrate her configuration from Dell D400 she used before (with Microsoft Windows XP). Firefox, Thunderbird, OpenOffice and then documents etc. Easy stuff.

Configuration phase was funny — I connected our printer/scanner and before I found where to add printer I got notification “EPSON Stylus DX4000 printer configured”. OK, so maybe scanner needs configuration… Nope — Simple Scan just started scanning instead of complaining (which it did when I bought it few years ago).

Connected netbook to TV and Meta-p gave me choice which display I want to run on (my 42” Panasonic does not like 1366x768 so cloning does not work).

There are few things which I still have to find out:

1. How to remove “something has crashed” notifications. My wife will rather not report bugs directly.
2. How to make audio switching automatically to HDMI when on cable insertion.
3. How to make internal microphone working.

But other than those I did not have problems. And it is a strange feeling when you take new device, boot Linux on it and it just works.