Category Archives: computers

Getting Licq to build with pbuilder

I wanted to test that I had specified the correct Build-Depends in my Debian package of Licq 1.5.0-rc2. It seemed like the simplest way to do this was to create a personal builder installation and build the package in that chroot.

So I did:

Building should then be as simple as executing:

Or it should have been that simple. Unfortunately the build failed with:

After some googling and testing; the fix was to add two random devices to the chroot:

(The change of permission for /dev/null was needed to avoid getting errors later in the build process.)

Git is not always better than subversion

Yesterday I wished I had used svn instead of git as VCS for Licq’s debian package, when I accidentally deleted my local git clone with lots of commits that I hadn’t pushed…

Luckily I had all the changes in a different format so I didn’t have to redo all the work, but I had to spend time trying to commit the changes in a somewhat logical way.

debian/licq.git mirror on Gitorious

To get better speed and a backup I’ve set up a mirror of debian/licq.git on Gitorious.org.

I don’t really know the best way to do this, but I did it by adding the following line to hooks/post-update:

This way the mirror will always be updated when I push to the “real” repository.

Get it by running

or clone it on Gitorious and send me merge requests :)

/me is the new Debian maintainer for Licq

Update 2010-10-30: Changed the initial setup to use gbp-clone.

I’m now officially the maintainer of Licq’s Debian packages. Since I’m not a real Debian maintainer, I’m very grateful to Joel Rosdahl who is my sponsor.

Version 1.3.8-1 is coming to a mirror near you as I write this.

The package source is kept in my git repository. To build the package from the git repository, install git-buildpackage and pristine-tar then follow the instructions below.

Initial setup:

To build the latest version:

To build a specific version:

The final packages will be available in ../build-area.

Later on when you wish to update:

The next version will have qt4-gui.

Wake on LAN with Debian

To enable Wake on LAN on a Asus P5E-V motherboard under Debian you can do the following. Since I have a Asus motherboard, that’s the only one I’ve tested, but except from the BIOS (which may differ a bit), the instructions should be the same for all motherboards/NIC that supports Wake on LAN.

In the BIOS, enable “Power on by PCIE device”.

In Linux, first install ethtool and then check that Wake on LAN is supported by running the following command:

The output should contain a ‘g’ to indicate that the device can be woken by sending it a “magic packet”.

Enable Wake-on by running:

Since this command must be run on every boot, add it to /etc/rc.local.

As the last step we must make sure that halt doesn’t disable the network device. This is done by adding this line to /etc/default/halt:

We also need the MAC address to send the magic packet to.

Then shutdown the computer. On an other computer, install e.g. wakeonlan and run:

The computer should now start.

Wii and Netgear WNR834B

I recently had a lot of problems connecting my Nintendo Wii wireless to my girlfriend’s Netgear router (WNR834B). The router was configured to use WPA-PSK [TKIP] + WPA2-PSK [AES] with a fairly long pass phrase (ASCII characters). It worked very well with my iBook (Mac OS X) and worked most of the time with my girlfriend’s laptop (Windows Vista). But it seemed like Windows used the WPA variant instead of WPA2. It just didn’t connect when forcing it to use WPA2. And the Wii would only connect if we turned encryption off. Not acceptable!

We tried many things to get the Wii to connect, without any success. In a last attempt we tried changing the pass phrase to a 64 characters long hexadecimal pass phrase. That did the trick. Both the Wii and both laptops now connect without any problem. So if you are having problems connecting your Wii to the wireless network, try changing the pass phrase to consist of hexadecimal characters (0-9, A-F) only. For WPA/WPA2 it must be exactly 64 characters long.