Plum blossoms, the false hope of life
Rain, the reflection of infinite sadness
The sky, the unique embodiment of loneliness
A dog in the shadows, the instrument of Death.

People’s curiosity has no limits, particularly when it comes to Wesnoth add-ons.

In order to reproduce a bug, I had uploaded and removed a test add-on from the add-on servers for 1.8 and trunk several times, yet it seems I forgot to remove it the last time. This hasn’t stopped people from downloading it out of morbid curiosity, although nobody has dared to ask me about it on IRC or the forums. Certainly not news to me, since this is exactly what happened with it the last time prior to its removal.

As of this writing, the 1.8 version has had 949 downloads, as it can be seen in the screenshot above. You’d think an add-on with a description of “FOO” and a misspelled title would not attract anyone to try it, but this principle doesn’t work in practice. Had the add-on contained code to break all other add-ons, people would still not get the idea, I guess. Then again, I’m talking about users who often mistakenly download the source code tarballs and then ask how to install Wesnoth on Windows or Mac OS X.

This is what I get for forgetting to remove this kind of stuff. Thanks Gambit for pointing it out to me this night.

After some hesitation, I have deployed Prosilver Special Edition on the Wesnoth.org forums, with multiple changes meant to make it more similar to mainline Prosilver in terms of layout. Wesnoth’s custom Prosilver changes have also been applied on our copy of Prosilver SE.

In fact, Prosilver SE as used in Wesnoth.org depends completely on the main Prosilver template rather than its own partial template set, and it also replaces the default Prosilver theme/stylesheets and imagesets, since otherwise very few people would choose to use it. Besides, OAB.

Of course, further changes are not unlikely to occur, depending both on the users’ feedback and my own testing experiences.

Not very long ago I mentioned that Frogatto’s iris transition effect didn’t work with the ATI R600 KMS drivers, and I assumed that this was caused by some lacking in the Mesa code. I even filed a bug report to its developers about it.

I was wrong. As MostAwesomeDude explained to me on IRC, and later posted in the bug tracker:

In UMS mode, r600c provides 8 bits of stencil on all configs, but in KMS mode, the normal wider variety of configs are available. The app used to have a call to SDL_GL_SetAttribute(SDL_GL_STENCIL_SIZE, 1), but it was commented out for some reason. Uncommenting that line caused a stencilled config to be properly selected.

The moral: Always check your GL configs.

Effectively, we discovered that restoring that line would solve the issue. It was apparently commented out by Dave at some point by accident. This won’t matter for long anyway, since Frogatto is already using a different mechanism to render the transitions on SVN trunk, solving the missing effect on who knows how many PC configurations. The iPhone port also lacked these transitions because of a platform limitation, so maybe the new technique will solve that minor shortcoming as well.

So now I’m basically just waiting for a new official release of the Tux-On-Ice patch for Linux 2.6.35 before switching to a complete KMS-based configuration. Until that happens, I’ll continue using 2.6.34.4 in UMS mode.

Again, thanks to MostAwesomeDude for the help with finding the cause of the bug!

Most people who frequented phpBB 2 forums have met the Subsilver theme at some point. Wesnoth’s community is not the exception, and the phpBB 3 switch completed by cycholka/Mist in March 2008 during the third-to-last host migration involved switching everyone to Subsilver2, which is the last incarnation of the good old Subsilver. Most of us Wesnoth forumers have become accustomed to the cleanness, quirks and old-school feel of Subsilver2.

However, that will eventually change.

Maintaining patches for mods affecting the forum user and moderator front-ends involves editing three template sets, which are Prosilver (phpBB 3’s new built-in and default style), Subsilver2 and AcidTech, which is Subsilver2-based with some essential layout differences. There are even some mods that don’t provide MODX instructions for Subsilver2, since it’s not essential for approval in the official modifications database to include support for this style that’s most likely going to be dropped in future phpBB release series.

If you take a look at my Projects section you’ll also notice that I’ve needed to write a couple of Subsilver2 hacks in the past to add minor functionality that’s present in the official phpBB 3 “Olympus” forum theme by default. There’s a third custom change in my tree, corresponding to the Quick Reply editor toggle button.

Finally, now that I have a 2 TiB external hard disk drive, I can start making regular, complete backups of my dear laptop. With rsnapshot fully setup after experimenting for a while using Bluecore’s own internal hard disk as target, a full copy of all major filesystems, and a partial copy of my /home — filtering useless crap for now, to avoid including caches and such — as of this writing the system is being backed up. Considering that it resides within a 250 GiB hard disk, of which 28 GiB are allocated for the preinstalled copy of Windows Vista, this couldn’t have been a better investment.

The next logical step is backing up Greycore and Blackcore’s hard disk contents, in particular the latter since its hard disk is already dying, and many blocks near the end of the drive are unusable.

After finishing Bluecore’s backup, I intend to send it to technical support if possible, to solve the issues with the noisy fan, partially stuck touchpad buttons, excess of dirt and lint inside the case and beneath the keyboard, loose screen panel articulation, … so yeah. And I also need a new, better battery (although the current one got better!). I’d probably consider just replacing the whole damn thing, if it weren’t that I already feel comfortable using it, and that we recently invested money on a laptop for my father — which happens to be completely useless, but whatever.

Besides, I didn’t buy an extra 2 GiB RAM module to throw it away with the laptop.

(Granted, I could just use Bluecore as a backup laptop by itself, but really, it’s hard to get rid of it since I’ve had better experiences with it than Greycore, despite all the problems derived from using AMD/ATI hardware.)

I’m also considering relocating and resizing partitions since my current configuration isn’t really optimal anymore, now that I have an use for those 250 GiB.

Not very long ago, I had a rather frightening experience that made me reconsider my testing practices of the increasingly popular Kernel Modesetting (KMS) support for various ATI Radeon chipsets on Linux. While I couldn’t determine exactly what happened back then, I’ve now got another similar story of KMS-related bugs that can cause permanent damage to your hardware.

My Wesnoth-UMC-Dev collaborator and personal friend of mine, Espreon, owns a Dell Inspiron e1705 laptop which ships with an ATI Mobility Radeon x1400 graphics controller. This is in contrast to my HP Pavilion dv5-1132la notebook (bluecore) which has an ATI Radeon HD 3200 (RS780-based) controller.

Espreon’s laptop is now damaged and unusable after some minor testing of KMS + Gallium3D drivers. The screen simply doesn’t work anymore.

I feel the need to carefully and meticulously analyze our stories since the KMS-enabled Radeon drivers are slowly becoming a standard amongst X.org-based Unix distributions including Debian GNU/Linux — Squeeze (6.0) is going to ship with a configuration apt for running on Radeon controllers in KMS operation without any user intervention. This is not to be unexpected since the KMS stack is clearly superior in terms of security and stability to the Xfree86/X.org based device drivers since it doesn’t require such things like making the X server’s executable setuid root, and allowing direct access to the host’s memory, video BIOS, etc. from a userland application.

But, is it really worth the risk? Is KMS really well-tested and safe enough to feature in stable mainline Linux kernels and in major general-purpose system distributions such as Debian? Let’s take a look at our personal experiences with the new graphics subsystem and drivers which are due to become mainstream around the end of this year.

I have just rebooted from a 2.6.35 kernel to 2.6.34.2 in order to have the ability to hibernate bluecore with Tux-on-Ice again. However, the laptop acted up after the warm reboot as a consequence of running Linux in KMS operation mode, apparently. The greatest sign of doom: the Giant Blinking Cursor of Doom.

It’s normal for these HP laptops to display the text-mode blinking cursor for a bit after the BIOS splash screen, right before transferring execution to the first available boot medium. The cursor’s size is similar to Linux’s or MS-DOS under a default configuration with any generic VGA-compatible video adapter. In this transition state, the bold-white cursor blinks a few times at the top-left corner of the empty black screen, before changing its color to the normal text terminal white when GNU GRUB takes over.

However, whenever the AMD ATI Catalyst drivers lock up the laptop and I perform a warm reboot using one of the Magic SysRq sequences, the laptop doesn’t get past the system initialization code and after the BIOS splash screen disappears, instead of the usual bright blinking cursor, an abnormally large and wide white blinking cursor appears as the computer gets stuck forever.

I had not seen this occur after running with the open-source KMS drivers before, but I guess it might indicate I own a faulty GPU or motherboard.

EDIT: now I have pictures — taken with my three years old cell phone — showing the GBCoD and the normal blinking cursor:

Today, while having breakfast at a subway station before going to university, I stumbled upon a weird case of the laptop’s battery going crazy again.

As you know, Bluecore’s battery basically dropped dead after an unfortunate accident with charging cycles, but now the outlook has slightly improved after its capacity increased as a consequence of booting the laptop on battery power this morning.

$ acpitool -B
  Battery #1     : present
    Remaining capacity : 1504 mAh, 66.20%
    Design capacity    : 9000 mAh
    Last full capacity : 2272 mAh, 25.24% of design capacity
    Capacity loss      : 74.76%
    Present rate       : unknown
    Charging state     : charging
    Battery type       : rechargeable 
    Model number       : 25 mAh
    Serial number      : Primary

(The last two information fields and the design capacity are bogus as usual.)

The BIOS didn’t warn me about charge capacity this time either, nor after plugging the AC adapter in at the university’s central library, so there’s something clearly odd about this. I didn’t wait for the battery to discharge at the subway and left it at 66% before proceeding to charge it again now, so let’s see how this goes in the future. I might be able to squeeze some life out of this deteriorated power source before sending off Bluecore for maintenance and repair.

Often on IRC I refer to my computers by their unique hostnames, which I also use to differentiate their Linux kernel configuration sets, optimized for every individual machine.

Many get confused with this because the names aren’t very descriptive of these machines, so here’s some technical background and history for every one of my technological pets.

It seems that one of the big guys of the Internet can’t keep the spambots at bay.

Espreon and I have been receiving this kind of garbage in our Gmail inboxes for quite a while already. They aren’t classified as spam for obvious reasons, but they are really annoying nonetheless. How come a company with that much money doesn’t set-up some kind of smart protection for their service forms? I’ve never seen this kind of crap from Google, and I hope to never do. This people, is why I use Google.

(Notably, I’ve received 4 of these so far, one every month until now.)

The Linux kernel 2.6.35 was released today, and I compiled and installed it before all the download links appeared on kernel.org’s front-page thanks to Akregator.

There hasn’t been an official release of Tux-On-Ice for this kernel version yet, but I still went and booted 2.6.35 with Radeon KMS support enabled by default. I should say that I don’t notice any performance improvements since the last time I tried this thing, and in particular, stencil buffers seem to be still unsupported by my Mesa/kernel drivers combination, which makes Frogatto fall back to using fading for level transitions, as opposed to the cool iris effect used otherwise.

(I might even bug the Mesa developers about the stencil buffer thing if I like KMS enough now...)

Nonetheless, the VSync support in the Radeon KMS driver, just like in 2.6.34, is much better than the crap AMD ATI's proprietary suite has to offer. Watching videos in VLC with no tearing at all is just wonderful.

It’s one of those moments where I can’t decide whether I want features, or quality. Right now KMS appears to offer more quality than UMSm if only because it has VSync at all, but as far as I can see, the UMS driver is more mature in terms of OpenGL features. Granted, I may give the AMD ATI Catalyst 10.7 drivers a try later now that the SuperTuxKart issue I mentioned before appears to be fixed according to their changelogs.

EDIT: only a few hours after, I decided to file a bug report for Mesa, now #29350. Let’s hope for the best!