After the Circus

Random Sample
Bridge Reflections

contact me
jean at geemoo dot ca

Apr 22, 2011
So, I've finished one of my recent projects, and by finish, I really mean have a working prototype and shows most of the functionality works. Really, since this project was meant to be a stepping stone to a multitude of other projects, it's never really going to be "finished".

So far, I've published all the hardware info that you need to build the board.. I have a working proof of concept software load for the MCU which I'm going to upload soon, so stay tuned for another post in the near future.

You can checkout the board though, at
Mar 10, 2011
So.. it looks like work is sending me to the IPv6 Summit. Since we're a company that makes hardware network devices, I'm pretty excited, as this is a topic we really need to be looking into. Stay tuned, more details to come.
Mar 6, 2011
If you ever get annoyed by searching for something on debian from your vimperator command line, and get annoyed at it using the debian package search engine, you can thank jcn for mentioning this tip to me. Inside vimperator, you can type :dialog search<stab><enter> and it will open up a dialog box with the search of search engines and keywords installed so that you can remove or change the ones that bother you.

I don't know how to open this dialog within firefox normally (ie: without the vimperator plugin).. I don't see any menu item for it anywhere. So, if you know, feel free to send me a message and I can update that here.
Nov 14, 2010
I've recently started to encrypt my backup drives, so I had to learn how to do this instead of just letting debian's init scripts to take care of it for me. Turns out it's quite easy. In my case, I was encrypting /dev/sdd1 and named my partition "backup". Substitute those values for whatever device and name you use.

# cryptsetup luksFormat /dev/sdd1
# cryptsetup luksOpen /dev/sdd1 backup
# mkfs -t xfs /dev/mapper/backup 
# mount /dev/mapper/backup /mnt/backup

That's it, when you're done with the device, umount the /dev/mapper/backup device, and then do a cryptsetup luksClose backup.
Oct 19, 2010
I just went through the process of getting my older nvidia card working on debian, and decyphering the exact list of steps was a bit irritating, so I'm recording it here for everyone (including myself) to enjoy later on. I'm writing this down after completing the process (and I'm certainly not going to start over again), so this is from memory, and hopefully I'm getting all the steps in the right order.

  1. First off, you need to install the linux headers (and possibly the linux source) for your kernel. I did these steps out of order, so I can't say if the linux source tree is really required. Things started working for me once I installed the headers, so those are certainly required. apt-get install linux-headers-$(uname -r).

  2. Next up, idenfity what card you have, and what nvidia-glx package supports it. Run lspci and it will show you a list of hardware installed.. my card is shown below.
    01:00.0 VGA compatible controller: nVidia Corporation NV37GL [Quadro PCI-E Series] (rev a2)
    Take the card type, (in my case NV37GL) and do a google search for NV37GL glx debian. This will produce a list of debian packages, and hopefully you'll see a results that looks like Debian -- Details of package nvidia-glx-legacy-173xx in sid. The version doesn't matter, we're just looking for the name here. Apt-get can handle the details. (there should be a way to get this info from apt-cache, but it's not producing results for me. Feel free to send comments on how to make this work.)

  3. Run apt-get install nvidia-glx-legacy-173xx (or whatever package google found for you.) This will install the module you need and whatever dependencies it requires. If you have the require kernel source installed, you should see a message about it building for your currently installed kernel. If you see a message that looks like Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed., it couldn't find your source tree and you need to try step 1 again.

  4. Once you're done that, get into console mode by doing init 1 or /etc/init.d/slim stop (substitute slim for gdm, kdm, xdm, whatever), and then go over to /etc/X11 and run X -configure to generate a new X configuration. Move the file over to /etc/X11/xorg.conf and then edit the file. Find the line that says Driver "nv" and change it to say Driver "nvidia".

  5. Save, exit, restart X. Once started, you should be able to open a terminal, run glxinfo and get results saying that glx is working.

  6. Celebrate! yay!

If you find any errors, or better ways to do that, please send me and email and I'll update appropriately. Good luck!