<?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>blog.crox.net (Entries tagged as raspberry pi)</title>
    <link>https://blog.crox.net/</link>
    <description></description>
    <dc:language>en</dc:language>
    <generator>Serendipity 2.5.0 - http://www.s9y.org/</generator>
    <pubDate>Fri, 15 Aug 2025 22:48:00 GMT</pubDate>

    <image>
    <url>https://blog.crox.net/templates/2k11/img/s9y_banner_small.png</url>
    <title>RSS: blog.crox.net - </title>
    <link>https://blog.crox.net/</link>
    <width>100</width>
    <height>21</height>
</image>

<item>
    <title>Disable WiFi Power Management on Raspbian 12 (Network Manager)</title>
    <link>https://blog.crox.net/archives/129-Disable-WiFi-Power-Management-on-Raspbian-12-Network-Manager.html</link>
    
    <comments>https://blog.crox.net/archives/129-Disable-WiFi-Power-Management-on-Raspbian-12-Network-Manager.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=129</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=129</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    &lt;a href=&quot;https://blog.crox.net/archives/106-How-to-solve-Edimax-EW-7612UAn-v2-73927822-power-management-issues-on-Raspberry-Pi-Raspbian-WiFi-disconnect.html&quot; title=&quot;How to solve Edimax EW-7612UAn v2 (7392:7822) power management issues on Raspberry Pi (Raspbian WiFi disconnect)&quot;&gt;8 years later&lt;/a&gt; there are still issues on Raspberry Pi / Raspbian with WiFi power management causing disconnects and generally bad performance.&lt;br /&gt;
&lt;br /&gt;
I&#039;ve found a reliable method to disable WiFi Power Management for the on-board WiFi chip (brcmfmac) here: &lt;a href=&quot;https://gist.github.com/jcberthon/ea8cfe278998968ba7c5a95344bc8b55&quot; title=&quot;NetworkManager WiFi Power Saving&quot;&gt;NetworkManager WiFi Power Saving&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Fri, 15 Aug 2025 22:48:00 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/129-guid.html</guid>
    <category>debian</category>
<category>linux</category>
<category>raspberry pi</category>
<category>wlan</category>

</item>
<item>
    <title>How to solve Edimax EW-7612UAn v2 (7392:7822) power management issues on Raspberry Pi (Raspbian WiFi disconnect)</title>
    <link>https://blog.crox.net/archives/106-How-to-solve-Edimax-EW-7612UAn-v2-73927822-power-management-issues-on-Raspberry-Pi-Raspbian-WiFi-disconnect.html</link>
    
    <comments>https://blog.crox.net/archives/106-How-to-solve-Edimax-EW-7612UAn-v2-73927822-power-management-issues-on-Raspberry-Pi-Raspbian-WiFi-disconnect.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=106</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=106</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    &lt;ul&gt;&lt;li&gt;On Raspbian, you don&#039;t need to install the 8192cu driver manually, as it comes with the distribution&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;To avoid disconnection issues, you need however to disable power management. This needs to be done in two places. First, this is what I have in /etc/modprobe.d/8192cu.conf:&lt;pre&gt;options 8192cu rtw_power_mgnt=0 rtw_enusbss=0&lt;/pre&gt;&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;This alone did not prevent the issue. I also had to add this entry to /etc/network/interfaces:&lt;pre&gt;auto wlan0&lt;br /&gt;allow-hotplug wlan0&lt;br /&gt;iface wlan0 inet dhcp&lt;br /&gt;wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf&lt;br /&gt;&lt;b&gt;wireless-power off&lt;/b&gt;&lt;br /&gt;iface default inet dhcp&lt;/pre&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
&lt;br /&gt;
Sources: &lt;a href=&quot;https://github.com/xbianonpi/xbian/issues/217&quot;&gt;https://github.com/xbianonpi/xbian/issues/217&lt;/a&gt;, &lt;a href=&quot;https://www.kuerbis.org/2016/03/raspberry-pi-3-kurztipps-wlan-sleep-mode-verhindern/&quot;&gt;https://www.kuerbis.org/2016/03/raspberry-pi-3-kurztipps-wlan-sleep-mode-verhindern/&lt;/a&gt; 
    </content:encoded>

    <pubDate>Sun, 12 Nov 2017 19:04:00 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/106-guid.html</guid>
    <category>debian</category>
<category>linux</category>
<category>raspberry pi</category>
<category>wlan</category>

</item>
<item>
    <title>OSMC NFS mount</title>
    <link>https://blog.crox.net/archives/97-OSMC-NFS-mount.html</link>
    
    <comments>https://blog.crox.net/archives/97-OSMC-NFS-mount.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=97</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=97</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    It looks like you need some systemd &quot;magic&quot; to successfully mount an NFS share on &lt;a href=&quot;https://osmc.tv/&quot; title=&quot;OSMC&quot;&gt;OSMC&lt;/a&gt;. Adding &quot;&lt;tt&gt;x-systemd.automount,noauto&lt;/tt&gt;&quot; to the mount options in &lt;tt&gt;/etc/fstab&lt;/tt&gt; did the trick for me.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Sun, 02 Aug 2015 14:19:46 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/97-guid.html</guid>
    <category>linux</category>
<category>network</category>
<category>nfs</category>
<category>osmc</category>
<category>raspberry pi</category>
<category>systemd</category>

</item>
<item>
    <title>Enable IPv6 on OSMC (wired and wireless)</title>
    <link>https://blog.crox.net/archives/96-Enable-IPv6-on-OSMC-wired-and-wireless.html</link>
    
    <comments>https://blog.crox.net/archives/96-Enable-IPv6-on-OSMC-wired-and-wireless.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=96</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=96</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    Despite having read the opposite, it looks like IPv6 is disabled by default on the latest &lt;a href=&quot;https://osmc.tv/&quot; title=&quot;OSMC&quot;&gt;OSMC&lt;/a&gt; release (2015.06-1). I&#039;ve tried adding a sysctl.d file to set /proc/sys/net/ipv6/conf/eth0/disable_ipv6 to 0, but this did not help. It worked only when I ran the command manually. By going through numerous forum posts I eventually found out that you need to use the &lt;tt&gt;connmanctl&lt;/tt&gt; CLI tool:&lt;pre&gt;root@osmc:~# connmanctl&lt;br /&gt;connmanctl&gt; services&lt;br /&gt;*AO Wired                ethernet_b827ebaabbcc_cable&lt;br /&gt;connmanctl&gt; config ethernet_b827ebaabbcc_cable --ipv6 auto preferred&lt;br /&gt;connmanctl&gt; quit&lt;br /&gt;root@osmc:~# &lt;/pre&gt;This enables IPv6 with &lt;a href=&quot;https://en.wikipedia.org/wiki/IPv6#Stateless_address_autoconfiguration_.28SLAAC.29&quot; title=&quot;SLAAC&quot;&gt;autoconfiguration&lt;/a&gt;, turns on &lt;a href=&quot;https://en.wikipedia.org/wiki/IPv6#Privacy&quot; title=&quot;IPv6 Privacy Extensions&quot;&gt;Privacy Extensions&lt;/a&gt; and prefers these ephemeral addresses over the autoconfigured ones.&lt;br /&gt;
&lt;br /&gt;
The same command works for wireless as well, you just need to select the appropriate interface (the service name will start with &lt;tt&gt;wifi_&lt;/tt&gt;).&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;tt&gt;help&lt;/tt&gt;&quot; will display basic usage info.&lt;br /&gt;
&lt;br /&gt;
If for some reason you would like to disable IPv6, the command would be &quot;&lt;tt&gt;config ... --ipv6 off&lt;/tt&gt;&quot;.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Sat, 01 Aug 2015 22:14:00 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/96-guid.html</guid>
    <category>ipv6</category>
<category>linux</category>
<category>network</category>
<category>osmc</category>
<category>raspberry pi</category>

</item>
<item>
    <title>Using a Raspberry Pi running raspbmc to sync Fitbit One with galileo (fitbit linux sync)</title>
    <link>https://blog.crox.net/archives/85-Using-a-Raspberry-Pi-running-raspbmc-to-sync-Fitbit-One-with-galileo-fitbit-linux-sync.html</link>
    
    <comments>https://blog.crox.net/archives/85-Using-a-Raspberry-Pi-running-raspbmc-to-sync-Fitbit-One-with-galileo-fitbit-linux-sync.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=85</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=85</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    (it should work with any other Debian-based Raspberry Pi distribution and all newer Fitbit devices that use &lt;a href=&quot;https://en.wikipedia.org/wiki/Bluetooth_low_energy&quot;&gt;BLE&lt;/a&gt;)&lt;br /&gt;
&lt;pre&gt;sudo -i&lt;br /&gt;apt-get update&lt;br /&gt;apt-get install python-pip&lt;br /&gt;pip install galileo&lt;br /&gt;galileo&lt;/pre&gt;&lt;br /&gt;
You can then use cron or a simple shell script to periodically run &lt;a href=&quot;https://bitbucket.org/benallard/galileo&quot;&gt;galileo&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Sat, 05 Apr 2014 11:47:47 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/85-guid.html</guid>
    <category>ble</category>
<category>bluetooth</category>
<category>debian</category>
<category>fitbit</category>
<category>linux</category>
<category>raspberry pi</category>
<category>raspbmc</category>

</item>
<item>
    <title>raspbmc - getting rid of iptables</title>
    <link>https://blog.crox.net/archives/80-raspbmc-getting-rid-of-iptables.html</link>
    
    <comments>https://blog.crox.net/archives/80-raspbmc-getting-rid-of-iptables.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=80</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=80</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    I don&#039;t need a firewall on my Raspberry PI which runs XMBC (raspbmc distribution) - it&#039;s in a dedicated subnet behind a firewall. Furthermore, there are several reports of iptables having an impact on the performance of network playback, causing buffering issues (although I didn&#039;t do any benchmark myself).&lt;br /&gt;
&lt;br /&gt;
I modified /etc/network/if-up.d/secure-rmc by adding &quot;exit 0&quot; right at the beginning like this:&lt;pre&gt;#!/bin/bash&lt;br /&gt;&lt;br /&gt;exit 0&lt;br /&gt;&lt;br /&gt;dec_to_bin() {&lt;br /&gt;...&lt;/pre&gt;&lt;br /&gt;
And then I ran:&lt;pre&gt;apt-get remove iptables&lt;/pre&gt;&lt;br /&gt;
This was followed by a reboot.&lt;br /&gt;
&lt;br /&gt;
nb: the secure-rmc file appears to be a raspbmc addition, and it could probably just be deleted instead.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 04 Apr 2013 20:39:00 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/80-guid.html</guid>
    <category>debian</category>
<category>iptables</category>
<category>linux</category>
<category>raspberry pi</category>
<category>raspbmc</category>
<category>xbmc</category>

</item>

</channel>
</rss>
