Small Perturbation

Arch Linux recently produced a list of packages that cannot be built from source because of broken URLs. I had received messages like this before, and usually they simply indicate that the website for a package has changed. This happened a lot, for example, in 2016 when Google Code was shut down and replaced with a raw archive of project snapshots. So I expected that I would only have to do a little bit of searching when the notification came for GNU Talkfilters.

Instead, I could not find any up-to-date sites hosting the source. Every post about it still pointed to the old site with links that lead to 404 errors. It started to look like talkfilters had disappeared from the web. This is unacceptable for any free software project, especially one that ostensibly bears the "GNU" distinction. Because I had compiled the program on my own machine years ago, I was lucky enough to still have a copy of the source lying around. I promptly uploaded it to this very site and updated the Arch package accordingly. As a result, the crisis has been averted and free software users with nothing better to do are still free to apply chat filtering rules like this:

$ echo "Welcome friends, to a new home for GNU talkfilters!" | pirate
Welcome crew, t' a new home fer GNU talkfilters! Shiver me timbers!

Gaze upon my newest creation. This setup is probably the first of its kind. The black clock showing 2:17 is a digital alarm clock. It sits on top of a clear box holding a circuit board that I made. The white clock showing the wrong time is an analog alarm clock. I can confidently say that when the digital clock reaches the alarm setpoint, the mechanical bells on top of the analog clock will ring.

Even though I study theoretical physics I am very happy to be in the same department as people who are well versed in machining, robotics and other useful endeavours. There is something very satisfying about sitting down to make a device that serves a particular purpose and seeing it through to the end.

I use a very old laptop which only has USB 1.1 ports built into the motherboard. In order to use cameras, external drives and printers, I have always put a PCMCIA expansion card in my computer that provides two USB 2.0 ports. The PCMCIA bus is based on PCI, so it supports transfer speeds of 1Gbps... more than enough for the 480Mbps of the USB 2.0 standard.

On this card, the black hump with the USB ports sticks out of the laptop. This is the card that I used to use but it just broke. After years of using it, I noticed that it failed to detect my printer one day. It still detected my thumb drive but mounting it caused it to unmount 5 seconds later. It has a Firewire port as well and I've only had to use this once for a Mini-DV camera. I'm not sure if this part is broken. But anyway, I just got a neat replacement for it.

Since 2004, I've owned a ThinkPad A22m - a laptop that came out in 2001. Much to the dismay of certain friends, I still feel no need to purchase a newer computer. I've often said that this old hardware can do everything I need while still letting me run modern software. However, it now seems like I will have to take some responsibility for the code if I want that to still be true in the future.

Specifically, I am talking about open source ATI drivers on GNU / Linux. The four main video card lines released by ATI (now owned by AMD) have been Wonder, Mach, Rage and Radeon. I don't think Wonder cards have any features that would warrant the development of a dedicated driver but Linux drivers for the other three have been written.

The Radeon driver is actively maintained by software engineers at AMD and some people who work for other software companies. The other two? Not so much. The Rage 128 driver was especially in need of a major update recently. And since my computer has a Rage Mobility graphics card, I felt motivated to start working on the code even though I had never hacked such a low-level piece of software before. Since the effort has largely succeeded, I would like to share my experiences with editing an open source video driver. The learning curve was quite steep and when I first started reading documentation, it seemed like it was written for a different audience. This post is going to be an unadultered attempt to get a completely new reader to catch on to what I did. I'm sure I will later find out that many things written in this post are technically incorrect, but I will not edit them. I want the only knowledge communicated in this piece to be the knowledge that one might reasonably be expected to have after jumping into driver development for the first time.

The only mobile phone that I have ever owned is the Samsung SPH-N270. In 2003, when The Matrix Reloaded came out, 2500 of these phones were made and sold for $500 each to promote the movie. Mine is number 551. They were by no means the most feature-rich phones of their day but they may have been the coolest. Few phones are able to divide a community in this way. Everyone who knows about the N270 either thinks it is the ugliest phone ever or the sexiest phone ever. My opinion is obviously the latter. The only carrier participating in the promotion was the American network Sprint PCS. Figuring out how to use the phone in Canada was a minor hurdle to overcome, but that is nothing compared to the hoops I had to go through to get this phone fixed. The phone is now 8 years old which is probably twice the average lifespan of a cell phone. The only forum posts about the phone that I have seen recently say something like "I used to use my Samsung N270 but now either the phone or the battery is broken." This happened to me but to make a long story short I found a company that is willing and able to do internal repairs on this phone and other phones from that era. That company is CellFix and they did an amazing job. While I was stuck with a broken cell phone, I briefly considered doing what normal people do and purchasing something more modern (like an Android phone). But now that it is clear that my matrix phone is still usable, I will proudly recount my experiences with this phone and mention some tips to anyone who has one or wants one. It's not like I will stop using it any time soon!