<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Jonas Genannt - kernel</title>
    <link>http://blog.brachium-system.net/</link>
    <description>Weblog of an System Engineer</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.2 - http://www.s9y.org/</generator>
    
    <image>
        <url>http://blog.brachium-system.net/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Jonas Genannt - kernel - Weblog of an System Engineer</title>
        <link>http://blog.brachium-system.net/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>git - revision control systen</title>
    <link>http://blog.brachium-system.net/archives/32-git-revision-control-systen.html</link>
            <category>kernel</category>
            <category>useful stuff</category>
    
    <comments>http://blog.brachium-system.net/archives/32-git-revision-control-systen.html#comments</comments>
    <wfw:comment>http://blog.brachium-system.net/wfwcomment.php?cid=32</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.brachium-system.net/rss.php?version=2.0&amp;type=comments&amp;cid=32</wfw:commentRss>
    

    <author>nospam@example.com (Jonas Genannt)</author>
    <content:encoded>
    Git the (new) revision control systen used by the &lt;a href=&quot;http://kernel.org&quot;&gt;Linux kernel&lt;/a&gt; is very nice, if you know how to use it. &lt;img src=&quot;http://blog.brachium-system.net/templates/default/img/emoticons/wink.png&quot; alt=&quot;;-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;&lt;br /&gt;
&lt;br /&gt;
Here are some hints for you/me:&lt;br /&gt;
&lt;br /&gt;
Downloads the git archive to your local directory &lt;i&gt;linux-2.6.16.x&lt;/i&gt;:&lt;br /&gt;
&lt;b&gt;git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git linux-2.6.16.x&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Updates your git archive with the servers archive:&lt;br /&gt;
&lt;b&gt;git pull git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Lists the available Tags in the Branch:&lt;br /&gt;
&lt;b&gt;ls -la .git/refs/tags/&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Creates an diff between to Tags:&lt;br /&gt;
&lt;b&gt;git diff v2.6.16.24..v2.6.16.25&lt;/b&gt; 
    </content:encoded>

    <pubDate>Fri, 11 Aug 2006 19:05:36 +0200</pubDate>
    <guid isPermaLink="false">http://blog.brachium-system.net/archives/32-guid.html</guid>
    
</item>
<item>
    <title>Devolo dLAN linux driver</title>
    <link>http://blog.brachium-system.net/archives/31-Devolo-dLAN-linux-driver.html</link>
            <category>debian</category>
            <category>kernel</category>
            <category>network</category>
            <category>usb</category>
    
    <comments>http://blog.brachium-system.net/archives/31-Devolo-dLAN-linux-driver.html#comments</comments>
    <wfw:comment>http://blog.brachium-system.net/wfwcomment.php?cid=31</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.brachium-system.net/rss.php?version=2.0&amp;type=comments&amp;cid=31</wfw:commentRss>
    

    <author>nospam@example.com (Jonas Genannt)</author>
    <content:encoded>
    Devolo dLAN USB drivers for the devolo network over power module.&lt;br /&gt;
&lt;br /&gt;
If you try to compile the version 2.0 on an higher kernel than 2.6.13 you get the following error:&lt;blockquote&gt;&lt;br /&gt;
make[2]: Entering directory `/usr/src/linux-2.6.16.18&#039;&lt;br /&gt;
  CC [M]  /home/jonas/dLAN-linux-package-2.0/driver/devolo_usb.o&lt;br /&gt;
  /home/jonas/dLAN-linux-package-2.0/driver/devolo_usb.c: In function `devolo_tx_timeout&#039;:&lt;br /&gt;
  /home/jonas/dLAN-linux-package-2.0/driver/devolo_usb.c:205: error: `URB_ASYNC_UNLINK&#039; undeclared (first use in this function)&lt;br /&gt;
  /home/jonas/dLAN-linux-package-2.0/driver/devolo_usb.c:205: error: (Each undeclared identifier is reported only once&lt;br /&gt;
  /home/jonas/dLAN-linux-package-2.0/driver/devolo_usb.c:205: error: for each function it appears in.)&lt;br /&gt;
  make[3]:  [/home/jonas/dLAN-linux-package-2.0/driver/devolo_usb.o] Error 1&lt;br /&gt;
  make[2]:  [module /home/jonas/dLAN-linux-package-2.0/driver] Error 2&lt;br /&gt;
&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
The &lt;b&gt;URB_ASYNC_UNLINK&lt;/b&gt; symbol is removed from the kernel. &lt;blockquote&gt;&lt;br /&gt;
This afternoon Alan Stern submitted a patch to remove the URB_ASYNC_UNLINK&lt;br /&gt;
flag from the Linux kernel.  Mr. Stern explained, &quot;This flag is a relic&lt;br /&gt;
from an earlier, less-well-designed system.  For over a year it hasn&#039;t&lt;br /&gt;
been used for anything other than printing warning messages.&quot;&lt;/blockquote&gt;&lt;br /&gt;
For the complete text &lt;a href=&quot;http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg37114.html&quot;&gt;klick here&lt;/a&gt;!&lt;br /&gt;
&lt;br /&gt;
So remove the lines 204 till 208 in the file &lt;i&gt;driver/devolo_usb.c&lt;/i&gt;. &lt;br /&gt;
&lt;br /&gt;
Restart the make, and the driver will now compile fine and work. &lt;img src=&quot;http://blog.brachium-system.net/templates/default/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Wed, 02 Aug 2006 23:13:52 +0200</pubDate>
    <guid isPermaLink="false">http://blog.brachium-system.net/archives/31-guid.html</guid>
    
</item>
<item>
    <title>Why you should read the kernel changelog</title>
    <link>http://blog.brachium-system.net/archives/18-Why-you-should-read-the-kernel-changelog.html</link>
            <category>debian</category>
            <category>kernel</category>
            <category>weird</category>
            <category>work</category>
    
    <comments>http://blog.brachium-system.net/archives/18-Why-you-should-read-the-kernel-changelog.html#comments</comments>
    <wfw:comment>http://blog.brachium-system.net/wfwcomment.php?cid=18</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.brachium-system.net/rss.php?version=2.0&amp;type=comments&amp;cid=18</wfw:commentRss>
    

    <author>nospam@example.com (Jonas Genannt)</author>
    <content:encoded>
    Why you should read the kernel changelog? - You have to read it, when you use an 2.6.16 vanilla kernel on a native sarge.&lt;br /&gt;
&lt;br /&gt;
When you don&#039;t have any problems with LVM (lvm2) and the kernel.&lt;br /&gt;
&lt;br /&gt;
In the Kernel ChangeLog there are nice informations like this:&lt;blockquote&gt;If you&#039;re using lvm2, for this patch to work correctly you should update to lvm2 version 2.02.01 or later and device-mapper version 1.02.02 or later.&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
If I had read this, I would have had no problems with LVM and kernel 2.6.16!&lt;br /&gt;
&lt;br /&gt;
Note for me: Fly over kernel changelog for every new kernel! 
    </content:encoded>

    <pubDate>Fri, 19 May 2006 02:01:42 +0200</pubDate>
    <guid isPermaLink="false">http://blog.brachium-system.net/archives/18-guid.html</guid>
    
</item>
<item>
    <title>mii-tool and 1Gbit/s links</title>
    <link>http://blog.brachium-system.net/archives/15-mii-tool-and-1Gbits-links.html</link>
            <category>kernel</category>
            <category>network</category>
            <category>weird</category>
    
    <comments>http://blog.brachium-system.net/archives/15-mii-tool-and-1Gbits-links.html#comments</comments>
    <wfw:comment>http://blog.brachium-system.net/wfwcomment.php?cid=15</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.brachium-system.net/rss.php?version=2.0&amp;type=comments&amp;cid=15</wfw:commentRss>
    

    <author>nospam@example.com (Jonas Genannt)</author>
    <content:encoded>
    Note to myself: mii-tool can&#039;t operate with 1Gbit/s and more.&lt;br /&gt;
&lt;br /&gt;
Use &lt;a href=&quot;http://packages.debian.org/ethtool&quot; &gt;ethtool&lt;/a&gt;, provides more informtion and has no 100Mbit/s limit.&lt;br /&gt;
&lt;br /&gt;
It&#039;s in Debian, so &lt;i&gt;apt-get install ethtool&lt;/i&gt; 
    </content:encoded>

    <pubDate>Thu, 20 Apr 2006 02:34:43 +0200</pubDate>
    <guid isPermaLink="false">http://blog.brachium-system.net/archives/15-guid.html</guid>
    
</item>
<item>
    <title>Xen included to the kernel soon?</title>
    <link>http://blog.brachium-system.net/archives/14-Xen-included-to-the-kernel-soon.html</link>
            <category>kernel</category>
            <category>xen</category>
    
    <comments>http://blog.brachium-system.net/archives/14-Xen-included-to-the-kernel-soon.html#comments</comments>
    <wfw:comment>http://blog.brachium-system.net/wfwcomment.php?cid=14</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.brachium-system.net/rss.php?version=2.0&amp;type=comments&amp;cid=14</wfw:commentRss>
    

    <author>nospam@example.com (Jonas Genannt)</author>
    <content:encoded>
    Today I have read on &lt;a href=&quot;http://www.heise.de/newsticker/meldung/72015&quot; &gt;Heise.de&lt;/a&gt; that Xen is one step closer to go into the linux kernel.&lt;br /&gt;
&lt;br /&gt;
I hope this would be soon, because I am a big fan of Xen. 
    </content:encoded>

    <pubDate>Fri, 14 Apr 2006 19:32:21 +0200</pubDate>
    <guid isPermaLink="false">http://blog.brachium-system.net/archives/14-guid.html</guid>
    
</item>
<item>
    <title>Atheros WLan Device</title>
    <link>http://blog.brachium-system.net/archives/10-Atheros-WLan-Device.html</link>
            <category>debian</category>
            <category>kernel</category>
            <category>wlan</category>
    
    <comments>http://blog.brachium-system.net/archives/10-Atheros-WLan-Device.html#comments</comments>
    <wfw:comment>http://blog.brachium-system.net/wfwcomment.php?cid=10</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.brachium-system.net/rss.php?version=2.0&amp;type=comments&amp;cid=10</wfw:commentRss>
    

    <author>nospam@example.com (Jonas Genannt)</author>
    <content:encoded>
    Atheros W-Lan Chipsets are really cool. Easy installation...&lt;br /&gt;
&lt;br /&gt;
I have bought an Dlink DWL-G520 (WITHOUT the PLUS (+)), get the source from the subversion and compiled it on my sarge system.&lt;br /&gt;
&lt;br /&gt;
After an &lt;blockquote&gt;modprobe wlan_scan_sta &lt;/blockquote&gt;&lt;br /&gt;
and &lt;blockquote&gt;modprobe ath_pci &lt;/blockquote&gt; the Atheros card should be ready.&lt;br /&gt;
&lt;br /&gt;
An &lt;blockquote&gt;ifconfig ath0 up&lt;/blockquote&gt; and &lt;blockquote&gt;iwlist  ath0 scanning&lt;/blockquote&gt; I found my WLan.&lt;br /&gt;
&lt;br /&gt;
So nice work from the Atheros developers. &lt;img src=&quot;http://blog.brachium-system.net/templates/default/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;&lt;br /&gt;
&lt;br /&gt;
BTW: The Card have a good sending and receiveing rate! 
    </content:encoded>

    <pubDate>Mon, 13 Mar 2006 22:10:08 +0100</pubDate>
    <guid isPermaLink="false">http://blog.brachium-system.net/archives/10-guid.html</guid>
    
</item>
<item>
    <title>boot kernel over network with initrd ramdisk</title>
    <link>http://blog.brachium-system.net/archives/7-boot-kernel-over-network-with-initrd-ramdisk.html</link>
            <category>bootloader</category>
            <category>kernel</category>
            <category>work</category>
    
    <comments>http://blog.brachium-system.net/archives/7-boot-kernel-over-network-with-initrd-ramdisk.html#comments</comments>
    <wfw:comment>http://blog.brachium-system.net/wfwcomment.php?cid=7</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.brachium-system.net/rss.php?version=2.0&amp;type=comments&amp;cid=7</wfw:commentRss>
    

    <author>nospam@example.com (Jonas Genannt)</author>
    <content:encoded>
    if you want to boot kernel and initrd over the network, please recompile the kernel and change the&lt;br /&gt;
&lt;blockquote&gt;CONFIG_BLK_DEV_RAM_SIZE=&lt;/blockquote&gt;&lt;br /&gt;
to your new size of the initrd.&lt;br /&gt;
&lt;br /&gt;
Per default it is 4MB that is not very much, if you use initrd for / 
    </content:encoded>

    <pubDate>Tue, 14 Feb 2006 20:54:12 +0100</pubDate>
    <guid isPermaLink="false">http://blog.brachium-system.net/archives/7-guid.html</guid>
    
</item>

</channel>
</rss>