Random mumblings of ARM developer
Today I looked for some tools for Microsoft Windows platform. Got some results marked as freeware so I looked deeply at them (why to pay if can get tool for free). And what did I saw? Definition of ‘freeware’ has been changed during last years… Now it means:
Freeware: software which you can try for free but any usage need you to register and pay $$$.
For me it is just ‘demo’, ‘trial’ version but not freeware.
Some time ago my home machine started to be very unstable. I was getting random rootfs corruptions ('awk: file not found' on start for example), sometimes reboot during work…
I treid to test all components:
backblocks test on /dev/hda1 — passedmemtest tests to get info how memory behave — passedcpuburn tests gave 63.5°C on CPU — passedcpuburn memory tests — FAILEDAfter switching memory sticks in slots all memory tests were passed again. But system still kept failing ;(
I’m lost of ideas how to fix it and more and more think about upgrading it to amd64 platform.
Today I again had to work on getting customer server working for website which we did at work. Since my last visit machine was replaced from crappy Celeron 333MHz with 128M ram and 2G SCSI harddrive — all under 5 years old Red Hat with 2.4.2 kernel — to dual p3/700 with 1G ram and much larger harddrive. It also got updated distribution but something a bit newer — Aurox 10.1 with 2.6.9 kernel.
Remote logged as root looks weird.. all shells with # — but if admin is lazy or do not know how to create user accounts…
The worst thing was that I had to be an admin there to get all LAMP components working in required versions. Now machine is building newer PHP from source because finding something on Aurox website is like looking into /dev/null ;( No informations for older releases, no public bugtracker, two misc forums (newer one treat my Firefox as WAP browser) — nightmare…
But it is nice to find that RPM based distros got some tools to fetch packages from network other then wget ;)
Train tickets bought. I will arrive in Berlin at 13:05 in Thursday 2006-10-05 and will leave on 12:40 on Sunday.
I plan to look around (never was in Berlin before), then meet Holger and then OEDEM evening meeting…
UPDATE: Some people asked me what is OEDEM. Let quote Michael ‘Mickeyl’ Lauer post:
OEDEM’06 (Open Embedded Developers European Meeting) in Berlin — it’s the first (of hopefully an annual series) conference about the BitBake Task Executor and the OpenEmbedded MetaData Repository, both in combination enabling to build Embedded Linux Distributions from scratch.
I will host two sessions there:
More information about OEDEM.
Yesterday I signed papers to extend my current mobile contract and bought Sony Ericsson k750i phone to replace my 4-years old Nokia 6310i.
Phone is nice and packed of features:
I’m in process of moving all data from my old phone to new one — tried OpenSync today and with help of pmarat from #opensync I got Kitchensync working and transferred my KDE addressbook into phone. Later I will work on sending datas from 6310i -> home computer -> k750i, then will have to work on synchronizing 6210 with something as I have to move whole content of 6210 to 6310i (with syncing with Thunderbird in between).
And now I know that Bluetooth is nice technology — few clicks in Konqueror and I have access to all files inside of phone.
I started own business. Main area will be OpenEmbedded consulting as I’m one of core developers of this buildsystem.
Things which I want to cover are:
Those kinds of things are nothing new to me — I maintain own branch used to build OpenZaurus, added few hundreds of packages (and changed countless of them).
Currently I prefer remote work due to fact that I still have full time job. Payments can be solved in two ways:
I can provide invoice.
In his recent posts Pavel Machek wrote about OpenZaurus status on collie and how he hacked provided image to get it working better. After reading them I decided to write something about it instead of just adding comment on his LinuxJournal entries.
There is no need to mount JFFS2 images as all images in OpenZaurus are also provided as tarballs. So user can unpack tarball, edit it content and then use mkfs.jffs2 to create image for flashing (this tool is part of mtd-tools package in many Linux distributions).
Avoid removing /usr/lib/ipkg/ directory — this is needed to be able to install any extra stuff into image. If you need free space then rather use ipkg list_installed and remove not needed stuff with ipkg remove -recursive UnNeededStuff1 UnNeededStuff2 to free space. There are many things in default rootfs which user can remove if does not need them:
Touchscreen configuration is provided for 2.4 and 2.6 kernel version — proper one is selected in /etc/profiles.d/tslib.sh script which is run by any graphic environment on machine.
For those who wonder who is Pavel Machek: he is a guy who work on getting 2.6 kernel working on collie (outside of OpenEmbedded/OpenZaurus kernel hackers team).
Today I released third testing version of OpenZaurus 3.5.4.2 version. It support only two models:
I decided to do not ship collie (SL-5000/5500) images as they need some work (for example they lack udev) and as usual there is a problem to get OPIE/GPE images fit in this small rootfs space.
The most important changes in this release:
I want to mention our kernel hackers: Richard Purdie and Liam Girdwood for sound fix, Mike Arthur for touchscreen fix. Without their work this release would not happen.