<?xml version="1.0"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>
	<channel>
		<title>Geemoo dot ca</title>
		<link>http://geemoo.ca</link>
		<description>Content from geemoo.ca specific to "linux".  To view all content from geemoo.ca, check out http://geemoo.ca/rss</description>
		<language>en</language>
		<pubDate>Fri, 18 May 2012 08:37:37 -0400</pubDate>
		<lastBuildDate>Fri, 18 May 2012 08:37:37 -0400</lastBuildDate>

	<item>
		<title>New Udev, Old Xilinx</title>
		<link>http://geemoo.ca/blog/265/new-udev-old-xilinx</link>
		<content:encoded><![CDATA[I updated my system lately and rebooted to find that the udev rules I was using to make my jtag programmer work, no longer worked.  I had been getting messages about the rules being old and being deprecated soon for some time now, but it seemed that "Real Soon Now" had suddenly became "Now". <br />
<br />
The new rules look like this:<br />
<div class=code>
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0007", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0009", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000d", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000f", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0013", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0015", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0008", MODE="666"
</div>
]]></content:encoded>
		<pubDate>Thu, 19 Apr 2012 09:41:12 -0400</pubDate>
		<guid>http://geemoo.ca/blog/265/new-udev-old-xilinx</guid>
	</item>

	<item>
		<title>IPv6 Summit</title>
		<link>http://geemoo.ca/blog/261/ipv-summit</link>
		<content:encoded><![CDATA[So.. it looks like <a href="http://thinkrf.com">work</a> is sending me to the <a href="http://ipv6summit.ca/">IPv6 Summit</a>.  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.
]]></content:encoded>
		<pubDate>Thu, 10 Mar 2011 13:06:30 -0500</pubDate>
		<guid>http://geemoo.ca/blog/261/ipv-summit</guid>
	</item>

	<item>
		<title>Getting rid of default search keywords</title>
		<link>http://geemoo.ca/blog/260/getting-rid-of-default-search-keywords</link>
		<content:encoded><![CDATA[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 <a href="http://that.guy.with.no.web.page">jcn</a> for mentioning this tip to me.  Inside vimperator, you can type <span class="code">:dialog search&lt;stab&gt;&lt;enter&gt;</span> 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. <br />
<br />
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.

]]></content:encoded>
		<pubDate>Sun, 06 Mar 2011 10:53:23 -0500</pubDate>
		<guid>http://geemoo.ca/blog/260/getting-rid-of-default-search-keywords</guid>
	</item>

	<item>
		<title>Encrypting Partitions on Linux</title>
		<link>http://geemoo.ca/blog/259/encrypting-partitions-on-linux</link>
		<content:encoded><![CDATA[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.<br />
<br />
<pre>
# cryptsetup luksFormat /dev/sdd1
# cryptsetup luksOpen /dev/sdd1 backup
# mkfs -t xfs /dev/mapper/backup 
# mount /dev/mapper/backup /mnt/backup
</pre>
<br />
That's it, when you're done with the device, umount the /dev/mapper/backup device, and then do a <span class=code>cryptsetup luksClose backup</span>.
]]></content:encoded>
		<pubDate>Sun, 14 Nov 2010 11:14:13 -0500</pubDate>
		<guid>http://geemoo.ca/blog/259/encrypting-partitions-on-linux</guid>
	</item>

	<item>
		<title>Nvidia + GLX for a Quadro Card on Debian</title>
		<link>http://geemoo.ca/blog/258/nvidia--glx-for-a-quadro-card-on-debian</link>
		<content:encoded><![CDATA[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.<br />
<br />
<ol>
<li>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.  <span class=code>apt-get install linux-headers-$(uname -r)</span>.<br /><br /></li>

<li>Next up, idenfity what card you have, and what nvidia-glx package supports it.  Run <span class=code>lspci</span> and it will show you a list of hardware installed.. my card is shown below. <div class=code>01:00.0 VGA compatible controller: nVidia Corporation NV37GL [Quadro PCI-E Series] (rev a2)</div> Take the card type, (in my case NV37GL) and do a google search for <span class=code>NV37GL glx debian</span>.  This will produce a list of debian packages, and hopefully you'll see a results that looks like <span class=code>Debian -- Details of package nvidia-glx-legacy-173xx in sid</span>. 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.)<br /><br /></li>

<li>Run <span class=code>apt-get install nvidia-glx-legacy-173xx</span> (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 <span class=code>Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed.</span>, it couldn't find your source tree and you need to try step 1 again.<br /><br /></li>

<li>Once you're done that, get into console mode by doing <span class=code>init 1</span> or <span class=code>/etc/init.d/slim stop</span> (substitute slim for gdm, kdm, xdm, whatever), and then go over to <span class=code>/etc/X11</span> and run <span class=code>X -configure</span> 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 <span class=code>Driver "nv"</span> and change it to say <span class=code>Driver "nvidia"</span>. <br /><br /></li>

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

<li>Celebrate! yay!</li>

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


]]></content:encoded>
		<pubDate>Tue, 19 Oct 2010 10:52:46 -0400</pubDate>
		<guid>http://geemoo.ca/blog/258/nvidia--glx-for-a-quadro-card-on-debian</guid>
	</item>

	<item>
		<title>CPU Speed Status Bar Monitor for wmii</title>
		<link>http://geemoo.ca/blog/257/cpu-speed-status-bar-monitor-for-wmii</link>
		<content:encoded><![CDATA[So, I recently bought a new computer, and this one is a dual core and supports all kinds of dynamic speed adjusting goodness, which apparently my last CPU did not.  While this is all great, there is a bit of a downside.<br />
<br />
Down in the status bar of the window manager I use (wmiirc-lua), there is a little box indicating the current scaled CPU speed that each core is running at.  As a result of the new dynamicness, the contents of that box are changing all the time.  I was going to remove it entirely, but instead decided to write a graphical version of the same.  The result of this effort is a wmii plugin called <a href="http://github.com/geemoo/wmii-lua/blob/cpugraph/src/plugins/cpugraph.lua">CPU Graph</a>.  Upon configuring wmii to load this, it'll create a 10 character scrolling ASCII bar indicating the current CPU speed. <br />
<br />
I've got it up at <a href="http://github.com/geemoo/wmii-lua/">github</a> for the moment, until <a href="http://github.com/bartman">bartman</a> gets a chance to merge it into the tree.<br />
<br />
Download. Install.  Enjoy the ASCII goodness.
]]></content:encoded>
		<pubDate>Sun, 14 Mar 2010 19:02:53 -0400</pubDate>
		<guid>http://geemoo.ca/blog/257/cpu-speed-status-bar-monitor-for-wmii</guid>
	</item>

	<item>
		<title>Turning off Magnetic Net Mode in gschem</title>
		<link>http://geemoo.ca/blog/256/turning-off-magnetic-net-mode-in-gschem</link>
		<content:encoded><![CDATA[I searched for this options for 15 minutes, so I'm posting this here so I don't
have to again.<br />
<br />
If you're like me and find the magnetic nets always connect to the wrong stuff,
you can turn them off!  You can do so by adding <span
class="code">(magnetic-net-mode "disabled")</span> to your <span
class="code">~/.gschemrc</span> or to a <span class="code">gafrc</span> in your
project directory.
]]></content:encoded>
		<pubDate>Wed, 10 Mar 2010 11:07:40 -0500</pubDate>
		<guid>http://geemoo.ca/blog/256/turning-off-magnetic-net-mode-in-gschem</guid>
	</item>

	<item>
		<title>Reinstalling GRUB on an Ubuntu install</title>
		<link>http://geemoo.ca/blog/255/reinstalling-grub-on-an-ubuntu-install</link>
		<content:encoded><![CDATA[So, I recently  had to fix an ubuntu install after Windows had been reinstalled onto the drive.. end result: of course Windows tromped over the MBR and wiped out grub, making the computer automatically boot into windows.  The fix is to get booted into Ubuntu and reinstall grub.  If you're a debian user, the best way I found to do this is:<br />
<ol>
<li>Download the Ubuntu liveCD for whatever version of ubuntu you are trying to fix.  Don't forget to download the 64bit version if you're trying to fix a 64bit install of Ubuntu.

<li>Do a google search for the usb-creator package for a not quite cutting edge version of ubuntu.  While it would be awesome if this package were in debian, I'm sure the demand for it is pretty low, since it seems to be an Ubuntu creation.  I am running Debian Squeeze/testing, and had good results using the usb-creator from Jaunty, which can be found <a href="http://packages.ubuntu.com/jaunty/usb-creator">here</a>.  (It'd be nice if you could just dd the iso to the usb drive and have it work, but alas I tried that, and it does not boot.)

<li>Download and install usb-creator via dpkg -i

<li>Insert a USB disk that you don't mind getting wiped, run usb-creator, select your liveCD iso file and usb disk, click format, and then Create disk.

<li>Wait forever.

<li>Pop the USB stick into the busted machine, and boot from the usb drive into the first menu with the install options.

<li>Move the cursor over the first option for "Try Ubuntu Live CD without changes" and press &lt;TAB&gt; to edit the menu command.  Replace the boot=whatever parameter with root=/dev/sdXY, where sdXY is whatever partition your Ubuntu install is on.

<li>Press &lt;ENTER&gt; and boot up into your Ubuntu install.

<li>Open up a terminal, run <span class=code>sudo bash</span> to get to a root shell.

<li>Run <span class=code>update-grub</span> to update your grub configuration file.

<li>Run <span class=code>grub-install /dev/sdX</span>, where sdx is whatever drive you boot off.. probably sda. (NOT sda1)

</ul>
<br />
<br />
Once that finishes successfully, you should be able to reboot the machine and grub will start up, allowing you to select what install you which to use.  There might be an easier way to do this, but since I'm not a regular Ubuntu user, this is what I found through web searchs and trial and error.  If someone has an easier way, please do fire me an email and I'll update this post.



]]></content:encoded>
		<pubDate>Fri, 05 Feb 2010 15:30:54 -0500</pubDate>
		<guid>http://geemoo.ca/blog/255/reinstalling-grub-on-an-ubuntu-install</guid>
	</item>

	<item>
		<title>Google Calculator for Bender</title>
		<link>http://geemoo.ca/blog/253/google-calculator-for-bender</link>
		<content:encoded><![CDATA[I used to have a <a href="http://supybot.com/">Supybot</a>, but I eventually got rid of it because I didn't want to have to use python to make it do things. <br />
<br />
I instead got myself a bender bot (a BasicBot::Pluggable perl bot) from <a href="http://www.dmo.ca/">dave0</a>.   I wanted a calculator for it, so I whipped up <a href="/files/GoogleCalc.pm">GoogleCalc</a>.  GoogleCalc uses the power of google's calculator and will respond to calc commands in channel.  It's awesome, only because google calculator is awesome.<br />
<br />
Note: There is an existing Google Calculator BasicBot module, but it seemed much more complicated than I needed and didn't come with examples or docs as to how to install it in a bender bot.  It's entirely possible it's not supposed to be installed into a bender bot.  This way seemed much easier.<br />
<br />
Grab <a href="/files/GoogleCalc.pm">GoogleCalc.pm</a> and copy it into your modules directory, and edit your yml config file to load it on startup.  Talk to it via the calc command.<br />
<div class=code>
15:10:02 [ ManOnIRC] MagicBot: calc 1 + 2<br />
15:10:03 [ MagicBot] ManOnIRC: 1 + 2 = 3<br />
15:10:15 [ ManOnIRC] Thanks MagicBot! You rock!<br />
</div>



]]></content:encoded>
		<pubDate>Sat, 29 Aug 2009 15:01:47 -0400</pubDate>
		<guid>http://geemoo.ca/blog/253/google-calculator-for-bender</guid>
	</item>

	<item>
		<title>CW sample file generator</title>
		<link>http://geemoo.ca/blog/251/cw-sample-file-generator</link>
		<content:encoded><![CDATA[I've been thinking about learning morse code (AKA CW) for a while, and after last weekend, I've finally convinced myself that I want to do it.  So, my first step was to write myself a little script to generate CW practice files that I can listen to on the bus rides to work.  Running the script will generate a text file, and an mp3 file.  The general idea is that you load up mp3 file onto your ipod, decode the message on paper (or in your head, if you're that good), and then compare it against the text version to see how many mistakes you made.<br />
<br />
The script uses an assortment of tools, all of which were fairly easy to acquire.  The list comprises the following: QSO, sox, lame, cwpcm and ofcourse bash.  You can get the list of tools by doing a <span class=code>apt-get install morse lame sox</span>.  cwpcm you have to compile from source, I'm afraid.  You can grab it at <a href="http://cwtext.sourceforge.net/">http://cwtext.sourceforge.net/</a>.<br />
<br />
Once you've got all that, run it at your command line, with the number of samples you wish to generate.  If you're going to make a large number, I recommend going for coffee.  The mp3 conversion step is time consuming. At the top of the script, there are two variables you can play with.. the characters per minute, and the words per minute, which affect the speed that the morse is played at.<br />
<br />
<pre>
# ./gencw.sh 50
cw-4WPM-8CPM-0001....
cw-4WPM-8CPM-0002....
cw-4WPM-8CPM-0003....
&lt;and so on&gt;
</pre>
<br />
You can download the script at <a href="http://geemoo.ca/files/gencw.sh">http://geemoo.ca/files/gencw.sh</a>. 

]]></content:encoded>
		<pubDate>Tue, 23 Jun 2009 23:15:53 -0400</pubDate>
		<guid>http://geemoo.ca/blog/251/cw-sample-file-generator</guid>
	</item>

	</channel>
</rss>

