<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Linux on cat /dev/snapshot</title><link>https://rumpf.eu/michael/tags/linux/</link><description>Recent content in Linux on cat /dev/snapshot</description><generator>Hugo -- 0.154.5</generator><language>en</language><lastBuildDate>Sat, 30 Jun 2012 12:26:00 +0200</lastBuildDate><atom:link href="https://rumpf.eu/michael/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Raspberry Pi</title><link>https://rumpf.eu/michael/posts/2012-06-30-raspberry-pi/</link><pubDate>Sat, 30 Jun 2012 12:26:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2012-06-30-raspberry-pi/</guid><description>&lt;p&gt;My Raspberry Pi finally arrived after 4 months:&lt;/p&gt;
&lt;p&gt;&lt;img loading="lazy" src="http://lh4.ggpht.com/-d4He0twcz6g/T-7UaBINYfI/AAAAAAAAJTQ/2exhKrF50Ck/1341051972105.png"&gt;&lt;/p&gt;
&lt;p&gt;The stable Debian distribution &amp;ldquo;Squeeze&amp;rdquo; does not contain support for all of the Raspberry Pi
features. That means there is no way around the the latest Debian &amp;ldquo;Wheezy&amp;rdquo; image: 
&lt;a href="http://www.raspberrypi.org/archives/1435"&gt;http://www.raspberrypi.org/archives/1435&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;But even with the latest image version there is still some configuration effort left&amp;hellip;&lt;/p&gt;
&lt;h2 id="wlan-stick"&gt;WLAN Stick&lt;/h2&gt;
&lt;p&gt;For network connectivity I have chosen the Conrad WLAN Stick N150 Nano, which is based on the following chipset: USB: 0BDA:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter.&lt;br&gt;
Unfortunately this chipset has some issues with the current drivers from both Debian Linux images as discussed in the forum thread &lt;a href="http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&amp;amp;t=6256&amp;amp;sid=85adf66d944a48285a706d8cb6884190&amp;amp;start=350"&gt;Automatic setup for RTL8188CUS based wifi adapters&lt;/a&gt;. By executing the script install-rtl8188cus-latest.sh from the forum thread, the adapter started working immediately after the script was finished.&lt;br&gt;
The general WLAN configuration is described in detail in the Debian Wiki: &lt;a href="http://wiki.debian.org/WiFi/HowToUse#Command_Line"&gt;http://wiki.debian.org/WiFi/HowToUse#Command_Line&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Wake On LAN</title><link>https://rumpf.eu/michael/posts/2012-03-03-wake-on-lan/</link><pubDate>Sat, 03 Mar 2012 22:50:00 +0100</pubDate><guid>https://rumpf.eu/michael/posts/2012-03-03-wake-on-lan/</guid><description>&lt;p&gt;Under Ubuntu I chose the following way to activate wake on LAN on the eth0 device:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;# Install ethtool
sudo apt-get install ethtool
# Create init script to set the wol bit on the device
sudo vi /etc/init.d/wakeonlan
#!/bin/sh
ethtool -s eth0 wol g
exit
# Make the script executable
sudo chmod a+x /etc/init.d/wakeonlan
# Create the init links
sudo update-rc.d wakeonlan defaults
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Under Debian the following approach has been chosen:&lt;/p&gt;</description></item><item><title>Building a TP-Link TL-WR1043ND OpenWRT 10.03 image</title><link>https://rumpf.eu/michael/posts/2011-07-31-building-tp-link-tl-wr1043nd-openwrt/</link><pubDate>Sun, 31 Jul 2011 23:48:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2011-07-31-building-tp-link-tl-wr1043nd-openwrt/</guid><description>&lt;p&gt;This article gives a step-by-step description on how to get the
&lt;a href="http://www.jcoderz.org/m3dditiez/wiki/m3ddity-player"&gt;m3ddity-player&lt;/a&gt; working on the
TP-Link TL-WR1043ND device, using the stable version of OpenWRT 10.03 (backfire).&lt;/p&gt;
&lt;p&gt;First you need to checkout the OpenWRT 10.03 (backfire) branch:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;svn co svn://svn.openwrt.org/openwrt/branches/backfire
cd backfire
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Then the feed for the &lt;a href="http://www.jcoderz.org/m3dditiez/wiki/m3ddity-player"&gt;m3ddity-player&lt;/a&gt; must be added:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;cp feeds.conf.default feeds.conf
echo &amp;#34;src-svn jcoderz http://www.jcoderz.org/svn/m3dditiez/branches/openwrt-10.3/packages&amp;#34; &amp;gt;&amp;gt; feeds.conf
./scripts/feeds update ./scripts/feeds install -a
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Now run menuconfig and select the necessary modules:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;make menuconfig
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The following list shows only menuconfig entries where settings have been changed. Settings not shown here are left untouched.&lt;/p&gt;</description></item><item><title>Music player fully integrated into the OpenWRT build process</title><link>https://rumpf.eu/michael/posts/2011-07-25-music-player-fully-integrated-into/</link><pubDate>Mon, 25 Jul 2011 00:44:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2011-07-25-music-player-fully-integrated-into/</guid><description>&lt;p&gt;The &lt;a href="http://www.jcoderz.org/m3dditiez/wiki/m3ddity-player"&gt;m3ddity-player&lt;/a&gt; and the GUPnP libraries,
on which the player depends upon, can now easily be build for OpenWRT, just follow the steps below:&lt;/p&gt;
&lt;p&gt;1. Checkout the trunk version of OpenWRT&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;svn co svn://svn.openwrt.org/openwrt/trunk
cd trunk
&lt;/code&gt;&lt;/pre&gt;&lt;ol start="2"&gt;
&lt;li&gt;Add the &lt;a href="http://www.jcoderz.org/m3dditiez/"&gt;jCoderZ&lt;/a&gt; package repository to the list of feeds &lt;/li&gt;
&lt;/ol&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;cp feeds.conf.default feeds.conf
echo &amp;#34;src-svn jcoderz &amp;#34; \ 
     &amp;#34;http://www.jcoderz.org/svn/m3dditiez/trunk/&amp;#34; \ 
&amp;#34;openwrt/packages&amp;#34; &amp;gt;&amp;gt; feeds.conf
./scripts/feeds update 
./scripts/feeds install -a
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;3. Run menuconfig and select the packages as described
&lt;a href="http://dev-snapshot.blogspot.com/2011/07/building-openwrt-image-optimized-for.html"&gt;here&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Building an OpenWRT image optimized for MP3 audio playback</title><link>https://rumpf.eu/michael/posts/2011-07-13-building-openwrt-image-optimized-for/</link><pubDate>Wed, 13 Jul 2011 20:36:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2011-07-13-building-openwrt-image-optimized-for/</guid><description>&lt;p&gt;For the audio-renderer, see revious posts, I decided to switch to the trunk version of OpenWRT.&lt;br&gt;
I experienced some issues with the USB audio hardware and the trunk version should prove that there
are no issues with the USB audio drivers which are already fixed.&lt;br&gt;
The following configuration is for the bleeding-edge version, some module names have changed so it
cannot be applied to the Kamikaze (10.3) version without modification (e.g. block-mount contains the
overlay functionality and kmod-fs-ext4 has support for all ext file-system versions).&lt;br&gt;
&lt;strong&gt;NOTE: This configuration has stripped all modules which are not necessary for USB audio and Wireless LAN.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Low-budget WiFi Music Player</title><link>https://rumpf.eu/michael/posts/2011-06-12-low-budget-wifi-music-player/</link><pubDate>Sun, 12 Jun 2011 13:17:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2011-06-12-low-budget-wifi-music-player/</guid><description>&lt;p&gt;After searching the net for quite a while I could not find a pure wireless music player for small money. In case
you want to equip multiple rooms in your house with a music player it will cost you a lot of money. All products
on the market come with a lot of features, of which most are not necessary. The following links show interesting
hacks on how to build your own WiFi music player based on OpenWRT:&lt;/p&gt;</description></item><item><title>GUPNP: Failed to get SCPD: Cannot resolve hostname ((null))</title><link>https://rumpf.eu/michael/posts/2011-06-05-gupnp-failed-to-get-scpd-cannot-resolve_05/</link><pubDate>Sun, 05 Jun 2011 18:23:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2011-06-05-gupnp-failed-to-get-scpd-cannot-resolve_05/</guid><description>&lt;p&gt;The following message occurs when the &lt;code&gt;&amp;lt;urlbase&amp;gt;&amp;lt;/urlbase&amp;gt;&lt;/code&gt; tag of the root device description is empty when trying to autoconnect actions:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;** (process:25888): WARNING **: Failed to get SCPD: Cannot resolve hostname ((null))
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Changing it to &lt;strong&gt;http://localhost&lt;/strong&gt; fixes the issue.&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;&amp;lt;?xml version=&amp;#34;1.0&amp;#34;?&amp;gt;
&amp;lt;root xmlns=&amp;#34;urn:schemas-upnp-org:device-1-0&amp;#34;&amp;gt;
  &amp;lt;specVersion&amp;gt;
    &amp;lt;major&amp;gt;1&amp;lt;/major&amp;gt;
    &amp;lt;minor&amp;gt;0&amp;lt;/minor&amp;gt;
  &amp;lt;/specVersion&amp;gt;
&amp;lt;URLBase&amp;gt;http://localhost&amp;lt;/URLBase&amp;gt;
  &amp;lt;device&amp;gt;
    &amp;lt;!-- ... --&amp;gt;
  &amp;lt;/device&amp;gt;
&amp;lt;/root&amp;gt;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The message is a bit misleading. I was first trying to find an issue with my DNS configuration.&lt;/p&gt;</description></item><item><title>Compiling GUPnP on Ubuntu 11.04</title><link>https://rumpf.eu/michael/posts/2011-06-03-compiling-gupnp-on-ubuntu-1104/</link><pubDate>Fri, 03 Jun 2011 15:55:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2011-06-03-compiling-gupnp-on-ubuntu-1104/</guid><description>&lt;p&gt;Because the &lt;a href="http://gupnp.org/"&gt;GUPnP&lt;/a&gt; stack is lacking some documentation I describe my experiences with getting it complied under Ubuntu 11.04. &lt;br&gt;
The commands will setup an environment that does not interfere with the Ubuntu provided packages, which are older than the ones compiled here. The library files will be installed under the location:
~/workspaces/openwrt/upnp&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Download:&lt;/strong&gt;&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;mkdir -p ~/workspaces/openwrt/upnp
cd ~/workspaces/openwrt/upnp
wget -O - http://gupnp.org/sites/all/files/sources/gupnp-igd-0.1.11.tar.gz | tar xvfz -
wget -O - http://gupnp.org/sites/all/files/sources/gupnp-0.16.1.tar.gz | tar xvfz -
wget -O - http://gupnp.org/sites/all/files/sources/gupnp-igd-0.1.10.tar.gz | tar xvfz -
wget -O - http://gupnp.org/sites/all/files/sources/gupnp-tools-0.8.3.tar.gz | tar xvfz -
wget -O - http://gupnp.org/sites/all/files/sources/gupnp-dlna-0.6.1.tar.gz | tar xvfz -
wget -O - http://gupnp.org/sites/all/files/sources/gupnp-av-0.8.0.tar.gz | tar xvfz -
wget -O - http://gupnp.org/sites/all/files/sources/gssdp-0.10.0.tar.gz | tar xvfz -
wget -O - http://gupnp.org/sites/all/files/sources/gupnp-vala-0.8.0.tar.gz | tar xvfz -
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;strong&gt;Prerequisites:&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>VirtualBox 4.0.2 on Ubuntu 11.04</title><link>https://rumpf.eu/michael/posts/2011-05-29-virtualbox-402-on-ubuntu-1104/</link><pubDate>Sun, 29 May 2011 13:55:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2011-05-29-virtualbox-402-on-ubuntu-1104/</guid><description>&lt;p&gt;After an update to Ubuntu 11.04 VirtualBox was not running anymore. Startup fails with a hint that the kernel modules exited in error and that I should use DKMS to reconfigure the kernel module.&lt;/p&gt;
&lt;p&gt;Running the vboxdrv setup command also led to an error:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;$ sudo /etc/init.d/vboxdrv setup
[sudo] password for desktop: 
 * Stopping VirtualBox kernel modules                                  *  done.
 * Uninstalling old VirtualBox DKMS kernel modules                     *  done.
 * Trying to register the VirtualBox kernel modules using DKMS                  
Error! Bad return status for module build on kernel: 2.6.38-8-generic (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/vboxhost/4.0.2/build/ for more information.
 * Failed, trying without DKMS
 * Recompiling VirtualBox kernel modules                                        
 * Look at /var/log/vbox-install.log to find out what went wrong
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The log file indicates that a header file was missing:&lt;/p&gt;</description></item><item><title>New version of smpppd-web</title><link>https://rumpf.eu/michael/posts/2006-01-12-new-version-of-smpppd-web/</link><pubDate>Thu, 12 Jan 2006 05:46:00 +0100</pubDate><guid>https://rumpf.eu/michael/posts/2006-01-12-new-version-of-smpppd-web/</guid><description>&lt;p&gt;The original versions of &lt;a href="http://www.suse.de/~cwh/"&gt;smppd-web&lt;/a&gt; by Christopher Hofmann neither support adding and removing links on the fly nor do they support dial-on-demand ISDN interfaces. That is the reason why I extended the original codebase by these features.&lt;br&gt;
Further more the users for which I developed the software are german speaking only so that gettext support was also an important feature. Initially I added  support for german and english languages.&lt;/p&gt;
&lt;p&gt;As I&amp;rsquo;m not a SuSE user in general, the new version probably does not follow the SuSE directory guidelines and it does not come packaged as a RPM. Therefore it would be great if someone with SuSE RPM packaging know-how would create a successor RPM package out of Christopher&amp;rsquo;s original version. Or even better Christopher packages a new version for &lt;a href="http://old-en.opensuse.org/User:Cwh"&gt;OpenSuSE&lt;/a&gt; ;)&lt;/p&gt;</description></item><item><title>Creating an ISDN Gateway with SuSE 9.3</title><link>https://rumpf.eu/michael/posts/2005-10-19-creating-isdn-gateway-with-suse-93/</link><pubDate>Wed, 19 Oct 2005 07:31:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2005-10-19-creating-isdn-gateway-with-suse-93/</guid><description>&lt;p&gt;In Germany flatrates are available for DSL only, so people, living in areas where DSL is not available, have to pay expensive time based fees for slowly connecting to the Internet. The problem is that M$ Windows and many of the installed tools are known for initiating internet connections although the user did not ask them to do so. Therefore it is crucial to reliably disconnect the ISDN line so that those unwanted connection attempts will not succeed. ISDN routers, which might be of help here, are hard to find nowadays and do not offer the comfort as new DSL routers do.&lt;/p&gt;</description></item><item><title>Linux support for TFA Klima-Logger</title><link>https://rumpf.eu/michael/posts/2005-07-02-linux-support-for-tfa-klima-logger/</link><pubDate>Sat, 02 Jul 2005 00:23:00 +0200</pubDate><guid>https://rumpf.eu/michael/posts/2005-07-02-linux-support-for-tfa-klima-logger/</guid><description>&lt;p&gt;&lt;strong&gt;Update 2012-03-01:&lt;/strong&gt;&lt;br&gt;
I just ordered 2 outdoor sensors and the plan is to connect the &lt;a href="http://www.tfa-dostmann.de/Bedienungsanleitungen/30.3015_e.pdf"&gt;Klima-Logger&lt;/a&gt; to a &lt;a href="http://www.raspberrypi.org/"&gt;Raspberry Pi&lt;/a&gt; Board to make the data available via browser on my home network. Here are some resources I found&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://oss.inqnet.at/trac/klimalogger/"&gt;https://oss.inqnet.at/trac/klimalogger/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://members.home.nl/xbasic/01c2249c770e62101/index.html"&gt;http://members.home.nl/xbasic/01c2249c770e62101/index.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.atmel.com/dyn/resources/prod_documents/doc0670.pdf"&gt;http://www.atmel.com/dyn/resources/prod_documents/doc0670.pdf&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.wetterstationsforum.de/phpBB/viewtopic.php?t=7605&amp;amp;postdays=0&amp;amp;postorder=asc&amp;amp;start=0&amp;amp;sid=472299c23b04447cc15aa92492c4a76f"&gt;http://www.wetterstationsforum.de/phpBB/viewtopic.php?t=7605&amp;amp;postdays=0&amp;amp;postorder=asc&amp;amp;start=0&amp;amp;sid=472299c23b04447cc15aa92492c4a76f&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://web.student.tuwien.ac.at/~e9725348/Projects/klimalogger/"&gt;http://web.student.tuwien.ac.at/~e9725348/Projects/klimalogger/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Outdated:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I recently bought a hygrometer from &lt;a href="http://www.tfa-dostmann.de/TFA2003_englisch/"&gt;TFA-Dostmann&lt;/a&gt;, called &lt;a href="http://www.tfa-dostmann.de/Bedienungsanleitungen/30.3015_e.pdf"&gt;Klima-Logger&lt;/a&gt;. It is the cheapest thermometer and hygrometer with PC connectivity I could find on the market. Unfortunately only a Windows software is provided to get the recorded values for temperature and humidity. I thought a Linux driver would be cool and started searching for resources on the net.  Usually the Linux community is very fast in supporting new gadgets of any kind, but  nothing could be found.&lt;/p&gt;</description></item></channel></rss>