Redhatter’s Web Blog

I’m in the process of installing Debian/MIPS on QEMU. Why might you ask? Well… the situation only came up just recently.

It seems there is some interest in running Gentoo on the QEMU virtual machine. The catch: QEMU emulates a MIPS Malta board with a 4Kc processor — which implements the MIPS32 ISA (a superset of MIPS2).

Until recently, this was impossible, as we did not produce stages for anything less than MIPS3 on big-endian MIPS, or MIPS4 on little-endian. MIPS32 is officially defined as the 32-bit subset of MIPS64, thus implements all the 32-bit instructions present in MIPS64, MIPS4, MIPS3 and completely implements MIPS1 and MIPS2.  It doesn’t however, implement any of the 64-bit instructions in these ISAs, which is where users come unstuck.  I produced some MIPS1 stages for little-endian MIPS, so in theory, the port is possible.

There’s also the question of performance — the guide I’m following suggests I can expect the performance of an R4400 200MHz Indy when ran on a 3GHz AMD64 host. Unfortunately for me, my host is a 1.4GHz Pentium 4. So I’m expecting things to be quite slow.

If things test okay, I might look into how one compiles a kernel for QEMU, and see if it’s worthwhile, since QEMU is much easier to get hold of then most supported MIPS platforms. It’s not known if mips-sources will be suitable, theoretically it should be, but this has never been tested. Support will be quite minimal, since most second hand SGI machines I suspect will outperform QEMU many times over. At the moment, my VM is “installing core packages” (yes, debian-installer is quite stingy on information), after which, I should be able to set up Gentoo on a second virtual HDD.

Support will likely take the form of a minimalist HDD image and kernel that can be booted on the VM.

Hi All…

Figured I better let you know what’s happening from where I’m sitting, since it’s been a while.

Mozilla Package Support on MIPS…

For the past month or so, I’ve been faced with a few problems. Firefox 2.0.0.4 has decided to not compile, despite 2.0.0.3 working fine … It would appear I need to re-jig this MIPS patch so that it works with the updated codebase. The patch I specifically refer to is the 006_mips-asm.patch file that you’ll notice included in all the patchsets distributed with Firefox and Thunderbird. Without it, Mozilla uses assembly code specially crafted for the Sony Playstation II — an incompatible machine to just about every other MIPS machine in existence.

Thunderbird has its own problems too. People may have noticed -mips KEYWORDS on the 2.0 series and my refusal to mark >1.5.0.8 stable? Seems there’s a bizzare bug that only happens to me on big-endian MIPS (mips-unknown-linux-gnu) when talking to my local IMAP server (running B-Inc IMAPd 1.2.12). On little-endian MIPS (mipsel-unknown-linux-gnu), everything works flawlessly. Indeed, I’ve been using Thunderbird 2.0 on mipsel for the past few months without issues… if mipsel was our only architecture, it’d be keyworded in a heartbeat, but it’s not. The problem manifests itself in two ways: one is the apparent non-existant mail folders, the other is hanging in an infinite loop apparently switching folders. I’ve tried strace and other tools to no avail… but my biggest problems revolve around my (big-endian) boxes being quite slow and my limited time. Needless to say… I’d appreciate others’ comments on this issue if they’ve experienced these problems with Thunderbird, or if indeed, it works on their SGI box.

Adventurous users can try it for themselves by editing the relevant ebuild directly and running ebuild foo.ebuild digest before attempting a merge.

Gnome packages…

I’ve began trying a test-compile of Gnome 2.18.0 on MIPS lately… largely to see just how much of it is actually broken. Unsurprisingly, much of it failed in N32… mono being one spectacular failure: it got stuck in an infinite loop and filled up the disk printing debugging output, which of course portage logged in the package’s build.log. My O2 is busy doing many of the package builds here, progress being quite slow. Needless to say, there’ll be updates on the situation as I get each part built. I strongly doubt this will lead to a re-keywording of Gnome on MIPS however, because frankly, it’s a pain in the arse to maintain.

Possible support for Loongson on the horizon…

This is the first time I’ve discussed this on Gentoo Planet… Others may recall seeing my Gentoo Universe post talking about my usage of a Lemote Fulong minicomputer… No official decision has been made at this time, but behind the scenes work is already underway to allow support for this architecture under the Gentoo/MIPS banner. This is the box that I’ve been doing much of my little-endian testing on, since a 660MHz Loongson 2E will outperform a 250MHz RM5231 any day. Ultimately, I’d like to see this machine become officially supported, as I suspect it’ll be machines like this that will keep the MIPS port alive. The SGI boxes currently supported will eventually fail, and as the pool of parts dries up, so will our users.

At present, these boxes can be made to run Gentoo no problem. You need a small patch for xorg-server to prevent a nasty segfault when starting X, and of course, the kernel needs some patches that are not yet in mips-sources (or upstream). Work is being done in an overlay hosted by Lemote for now, but as soon as I get the official go-ahead, I’ll start moving things into the main Gentoo tree.

glibc upgrade issues…

Some users have reported issues when upgrading to glibc-2.5, essentially the build seems to cause hard-locks on some IP28 and IP30 users (me included). Work is still ongoing to track down why this occurs — as always though, feedback would be appreciated.

Cobalt IDE-related issues…

On later mips-sources kernels, some users have reported kernels failing to detect their IDE HDDs. I haven’t been able to test since 64-bit kernels are broken (I run a 64-bit kernel on my Qube2 for N32 testing) in other Apparently the issue is related to hotplug support — yes, despite the machine having no hot-pluggable interfaces, you still need hotplug in your kernel. People may want to look into moving across to the newer VIA PATA driver too, since I suspect the upstream kernels will start moving this way anyway — the newer driver is quite stable on Cobalt. More info in this forum thread.

If I think of anything… I shall post more later.

Hi,

As promised, some stages compiled for MIPS-I have been released.  These stages should be appropriate for almost all little-endian MIPS hardware equipped with a decent amount of memory (128MB or more).  This should make things a little easier for those wishing to install Gentoo on MIPS32 hardware such as AMD Alchemy development boards.

Note, anything kernel or bootloader related, we can’t help with.  It’s assumed you know what you’re doing as far as actually preparing a bootable kernel and configuring your firmware to boot Gentoo.

Next on the list, is to look into µClibc stages for Cobalt — which will hopefully be used to produce updated netboot images for Cobalt.  So yeah, I’ve been absent for the last week or so, de-stressing and getting uni sorted out.  In short, it’s all system’s go now.

Hi All…

At the moment, stresses are running high.  Exactly why, I’m not sure, but it seems everyone is on edge.  And I don’t just mean the Gentoo Development community — I mean elsewhere too.  Everyone seems to be edgy for reasons I cannot fathom.

I’m not going to speculate about what could be causing this stress… I know in my case, the tense atmosphere has had an impact.  I’m nowhere near the point of doing anything irrational like suicide (I know this will create more problems than it will solve), but I am noticing that I’m not in my usual “stable” mental state.  I think in my case, there are a few factors in play…

• At university, I’m doing a subject entitled “Core Project Initiation”, which heavily depends on groupwork.  We have to form groups of 5 people or so, choose a project, find a project supervisor (typically other lecturers at QUT), then work towards implementing a prototype.  The first assessment item, is due this Friday, and more or less requires the group to be formed.  After having two attempts at forming a group fail, I’ve been in contact with the lecturers and am in urgent need to get into a group.  Basically, if by Wednesday, I’m not in a group — I’ll pull out of the subject, it’s just not going to be viable for me to continue.
• Last semester was rather stressful, having had two major stuffups by the university (in one case, a lost exam paper; in a second, a breech of examination procedure), and winding up failing a telecommunications subject for seemingly unknown reasons.  A total lack of feedback was a big factor — there was nothing to suggest I was offtrack, yet, I got a 2 (7-point scale) as my grade for the subject in question.
• I’m still looking around for work.  I’m quite conscious that I’m basically living out of my father’s back pocket — have been for some time now.  This has been playing on my mind a lot lately.  I know that without any work, I can forget passing my degree, I can forget moving out of home at some point.  And luxuries like attending LCA2008 are definitely out of the question.  I’ve applied to several positions over the last few months without success.
• The weather has been rather hot and humid lately, enough to shorten the fuses of most people.  Add to that the fact that Brisbane (like much of Australia) is in drought, and that the dam levels are dropping to alarmingly low levels.
• Then there’s the censorship debate that’s been raging on for the past fortnight on both gentoo-dev and gentoo-core.

Some of these problems are aggrivated by communications issues stemming from my Asperger’s Syndrome.  Stress is not something I handle well, with depression being quite common in such circumstances.  I’m in the happy position that I haven’t needed any medication to keep things under control however — I intend to keep things that way if I can.  Right now, I’ve just detected abnormalities in my behaviour, and thus know something is up.
At this point, I’m certainly not planning on resigning from Gentoo.  My builds for MIPS1 (little endian) are progressing, having just started Stage 2 this evening.  There’s no major issues to deal with at this time, and I hope to have these out soon.  I’ve also picked a fight with µClibc trying to bash out updated stages — managed to mess something up rather badly there, but I’ll hopefully get that straightened out and have some netboot images for you.

Presently, I’ve got stuff in my personal life that needs my attention first.  Thus, I’ll be “away” for the next fortnight whilst things settle down locally.  I’ll be contactable by email, and may be on IRC sporadically — but I don’t expect to be doing a hell of a lot.  I need some time to reduce some of the external pressure, get myself mentally ontrack again.  Hopefully when I return, not only will things have calmed down around here, but people within Gentoo, and perhaps others globally, might have settled down too.

In short, I’ll be around, just laying low for a while.

Hi All,

I’ve just uploaded the stage 3 tarball for Cobalt users. This build is compiled for MIPS4… hopefully in a few days ~ a week, a MIPS1 build will join it. I’d greatly appreciate it if users could test these builds out and report back any findings.

Also, in case you missed… there’s a new CoLo release. I’ve tested it both booting from disk, as well as netbooting, and so far, everything seems to work as it should… but I’d again appreciate feedback before I bump it to stable. I aim to do this very soon, as the presently stable version does not compile under gcc-4.1.

Hopefully, I should have all this on mirrors by the end of the month once testing has been completed.

Hi All…

Some of you may recall a proposed patch to block the use of proprietary kernel modules in the Linux kernel.  This seemed like a good idea, and it’s one I’d support — however, I do realise there are some shortcomings in the plan.  Looking at the thread tonight, I happened to see a post by David Schwartz which suggested a trademark that could be used by the manufacturer if decent specifications were made available.

I did some thinking about this… and the idea of a small (perhaps non-profit) organisation, could be appointed, to devise Linux-compatibility standards, which companies must meet before they can claim their device is “Linux-Friendly”.  If this organisation agreed that, indeed, the device met the specs, the manufacturer would be given a license to use an appropriate logo when advertising their device to consumers, and they’d be allowed to call their device “Linux-Friendly”.  Otherwise, they’d be told how they can rectify the situation.

I’m thinking something like a 3-level system, which indicates the level of support provided by a device for Linux: (The following is obviously a rough draft)
Bronze-Level Compatibility:

1. Complete Hardware specifications must be made available to those implementing open-source device drivers
2. Technical people responsible must be willing to answer questions relating to the implementation of such drivers
3. Drivers and utilities for the device must be released under the GNU General Public License (may be dual-licensed) and should allow a user to utilise all the device’s features.

Silver-Level Compatibility:

In addition to the requirements of Bronze level, a manufacturer must offer technical support (at minimum, by email) for users running Linux.  Such support should apply to the mainstream Linux distributions (Red Hat/Fedora/CentOS, SuSE, Debian, Gentoo, Ubuntu), but may include other distributions too.
Gold-Level Compatibility:

In addition to the requirements for Silver level, a manufacturer must be actively involved in the development of the open-source driver.  Examples would include the Intel PRO/Wireless devices, WACOM tablets, HP printers…etc — all of these companies run open-source projects that develop drivers for their products.

The above is obviously a work-in-progress, and should not be considered official.  I use the Gold/Silver/Bronze system here, because many people are familiar with how it works.  If you’re new to Linux, obviously Silver or Gold level is best, but things may JustWork with Bronze-rated hardware… if you have contact with Linux-savvy people, or are Linux-savvy yourself, then Bronze will suffice.  If you don’t see any rating at all, it’s a matter of buyer-beware.
What would the logo look like?  Well… I’ve got an idea for that too:

The penguin was hand-traced from a photograph of a King Penguin uploaded to the WikiMedia Commons.  The thought is, perhaps the blue ring there could be coloured to indicate the level of support.  I have a SVG version of that image here.  Note: I ask people, to not use this logo for commercial use until proper guidelines are worked out.
Anyways… what are people’s thoughts?  I personally think it’ll make life easier for the typical Linux user, in determining what hardware to buy.  If there’s support for the concept, then it encourages through peer pressure, companies to participate, hopefully leading to better quality drivers.

Hi All…

Well, my stagebuilds are in full swing… at this rate, I hope to have stage1 up in a day or two, and I’ll be starting on stage2, etc very soon.
New Profiles:

The structure is much the same as the 2006.1 release, just replace “2006.1″ with “2007.0″ in your profile path. Portage will tell you what to do when we officially mark the profiles deprecated.  Or, you can switch ahead of time… e.g. on Cobalt:

# rm /etc/make.profile
# ln -sv /usr/portage/profiles/default-linux/mips/2007.0/cobalt/o32 /etc/make.profile

This will set your machine up with the new profile (using LinuxThreads… see below for NPTL).

MIPS1 Stages for Cobalt:

There has been some demand for such stage files for some time now, mainly for enthusiasts that wish to run Gentoo on mipsel machines that don’t implement the full MIPS4 ISA. In this release (after I get the MIPS4 stuff pushed out safely), I’ll build MIPS1 stages for those who wish to experiment. Please Note: We can’t help you with queries involving unsupported systems. For some userland-related issues, we may be able to provide some assistance, but anything involving hardware or kernel, you’re on your own.

The MIPS1 stages are primarily being used in a few unofficial ports of Gentoo to various architectures. I won’t say much more than that, as there are some legal issues which need to be addressed first… however, it is hoped these ports can go ahead. Naturally, I’ll let you know when this happens.

Heads Up - 2007.1 release:

In 2007.1, we plan to switch over to running NPTL across all MIPS platforms. At present, I’m doing some testing on mipsel using NPTL to confirm stability. Other MIPS developers have been running NPTL on SGI boxes for some months now with great success, so the code is considered reasonably stable now, even though it’s not keyworded as such. To use NPTL, switch to the nptl/ profile for your system, unmask glibc-2.4-r4, then upgrade glibc:

e.g. on Cobalt:

# rm /etc/make.profile
# ln -sv /usr/portage/profiles/default-linux/mips/2007.0/cobalt/o32/nptl /etc/make.profile
# echo '=sys-libs/glibc-2.4-r4 ~mips' >> /etc/portage/package.keywords
# emerge -a glibc

It would be greatly appreciated, if a few brave users could give this a try, and report back their findings.

Hi All…

Well, it’s that time of the year again… the lead up to release time for 2007.0. The official snapshot date is apparently next week sometime, which means I need to produce some pre-2007.0 stages in preparation.

Recently, I started the beginnings of an n32 port to Cobalt, with these stages being available from my devspace (contact me and I’ll provide the URL). In this release, I hope to provide stage1/2 tarballs (perhaps stage3 too) compiled for MIPS1, potentially allowing all standard (note; the PS2 and PSP are not standard) LE MIPS systems to run Gentoo. Users porting Gentoo to new platforms will still be largely on their own as far as support goes… but at least they’ll have a reasonable base system to work from.

Also on my TODO list, is to update the docs. Things aren’t too shabby, however there are some bootloader-related updates, now that arcboot has been punted from the tree, and arcload 0.5 is stable. CoLo will eventually need to be updated too… I’ve held off doing this, since I use my Qube2 as a file server, and thus value its availability. Also, since my PDA has decided to go on the blink, I’ve been without a convenient VT100 terminal to plug in… thus I’ll need to build a new null-modem cable to hook my laptop up.

Hopefully by next week, I’ll have some prerelease stages for 2007.0 (32-bit only for now)… and can start building the official stages once the snapshots are released by the Release Engineering team.

Hi All…

Well, after much waiting, I managed to get KDE 3.80.2 to build and run. What can I say? Right now it’s not much to look at (low-res screenshot 800×600 100kB, full-res screenshot 2MB 2048×1576), and there are loads of sharp edges, but this is to be expected for a pre-alpha release.

My impressions:

• The new build system — This is going to take a bit of getting used to, but cmake seems to do a nice job building KDE. And there’s progress displayed as each package is built — very handy with long-haul builds.
• Build Time was significantly lower in KDE 3.80.2, compared to KDE 3.5 releases
• Some of the core apps (Konqueror, Konsole…etc) seemed to work fine, although there were some instability issues. (not suprising) Konqueror also seemed to like picking up the resources from KDE 3.5.5, leading to some oddities in the interface.
• KDE Control Centre appeared to be broken, in that it would not display applets. kcmshell worked however.
• Some of the kicker Panel applets failed to work (e.g. the clock)
• The startkde script locks up half-way (loading the Window Manager). In the screenshots above, I had to run kdesktop, kicker and kwin manually from xterm.
• There appear to be DBUS communications issues that need to be resolved.

In short though… it’s early days, but it looks like we’ll be seeing a lot of behind-the-scenes action in this release. I didn’t see anything that resembled the ideas for Plasma, but perhaps that will come later. It’ll definately be worth having another look in a few months.

Now I know a number of you have been gagging for a guide on how to install KDE 3.80.2. Here’s a very rough guide.

Part 1: KDE Dependancies

For this release, you need a number of things:

• Qt 4.2.1 with D-BUS support
• D-BUS 0.95
• cmake 2.4.3

cmake is fairly trivial, just add the appropriate line into your /etc/portage/package.keywords to allow you to install version 2.4.3 (currently unstable on x86) and run emerge cmake.

For the others… you’ll need to unmask both ebuilds in package.mask, and will need to hack the Qt ebuild to enable D-BUS support. D-BUS 0.95 is masked at the moment, pending updated mono bindings. Qt 4.2 is masked, pending D-BUS 0.95. You’ll need to uninstall earlier versions of D-BUS in order to install the new release. Be prepared, this will break HAL, avahi, and anything else you have which uses D-BUS, so prepare to have a big rebuild task ahead.

To enable support for D-BUS in the Qt ebuild you’ll need to change the following:

1. Add dbus to the IUSE variable:

   IUSE="accessibility cups dbus debug doc examples firebird gif glib jpeg mng mysql nas nis odbc opengl pch png postgres sqlite xinerama zlib ${IUSE_INPUT_DEVICES}"

2. In DEPEND, put in the D-BUS dependancy (it’ll be commented down below):

   glib? ( dev-libs/glib )        input_devices_wacom? ( x11-drivers/linuxwacom )        dbus? ( >=sys-apps/dbus-0.93 )"

3. Update the qt_use function to pass -qdbus to the configure script (it’ll be commented out). Also, comment out the line below as shown here:

   use dbus        && myconf="${myconf} -qdbus" || myconf="${myconf} -no-qdbus" #      myconf="${myconf} -no-qdbus"

Once the updates are complete, run ebuild qt-4.2.1.ebuild digest. Then, install all of the above: emerge dbus qt.

Part 2: Installing KDE by hand

As mentioned earlier, this new release uses the cmake build system, which is a bit different to get used to. Some of the docs (namely the ones for kdebase) haven’t been written yet, but in short, the procedure is as follows:

1. Unpack the source tarball (tar -xjvf /path/to/sourcepkg-3.80.2.tar.bz2) into a temporary directory.
2. Create a build directory (mkdir sourcepkg-build), then change into it.
3. Run cmake -DCMAKE_INSTALL_PREFIX=/place/where/you/want/kde/3.80.2 -DCMAKE_BUILD_TYPE=debug /path/to/sourcepkg-3.80.2
4. Run make
5. (As root) Run make install

The tricky bit, is the arguments to cmake:

• -DCMAKE_INSTALL_PREFIX= specifies the directory in which you want KDE installed. I put my installation in /usr/kde/3.80.2 so that it was placed alongside my KDE 3.5 install (but not in a place where it would get clobbered). This location is entirely up to you.
• -DCMAKE_BUILD_TYPE= specifies the level of debugging to include. Valid values are debug (normal debugging), debugfull (full debugging) and profile (full debugging with test coverage).
• The last argument, points to the directory containing the sources.

The KDE components need to be installed in the following order:

1. kdelibs
2. kdepimlibs
3. kdebase
4. other packages

Those three above mentioned packages, will get you the desktop shown in the screenshots. I have not yet installed the remaining packages, but these three will get things up and running.

I don’t recommend people mess with this release, unless they know what they are doing… As I say though, I’ll be keeping a close eye on this release, as it looks like there’s going to be lots of goodies going in behind the scenes for us KDE users come release time.

I’ve been a KDE user since installing SuSE Linux 5.3, and seeing KDE 1.0 in all its glory. I later tried Gnome 1.0/Enlightenment, when Red Hat 6.0 was released, and numerous other desktops, but I always found myself moving back to KDE. Prior to this, I had been using window managers like AfterStep, WindowMaker, FVWM and Red Hat’s FVWM95 clone, AnotherLevel.
The other day, I was looking around on the KDE news site, and noticed KDE 3.80.2 had been released for testing. This is a prerelease version of the upcomming KDE 4 desktop, intended for developers to take the desktop for a spin, port their applications to it, etc… Given my interest in the desktop, I figured I’d download a copy and take it for a spin.

The new KDE uses a different build system to previous releases. KDE 3.5 and earlier used GNU autotools, but not anymore. You’ll need cmake 2.4.3 or above to compile KDE 4. You’ll also need Qt4.2, and dbus, which means fun-and-games with masking, modifying ebuilds to disable some tests, and in general, lots of nasty hacks. Unless you know what you’re doing, I wouldn’t recommend anyone try it.

Anyway… after much fiddling, I managed to get it building. Already, I notice something new. The new build scripts actually show the build progress, as KDE builds. This is handy if you’re running on slow machines, and the first time I’ve seen such a feature in use. Here (right) is what the start of the build looks like (low resolution, full resolution).
I shall upload some pics of the desktop the moment I get kdebase installed, but so far, this is prooving very different to previous releases of KDE.