Page Collection for ^2013-05-07

2013-05-07 Raspberry Pi WiFi

Summary: Install wicd-curses. Run it. Press the right arrow on the wireless network you want to use. Check automatically connect to this network. Switch to WPA 1/2 (Passphrase) and provide your password. Hit F10 (or Command F10 on a Mac). Hit C to connect. You’ll see messages about it generating config files (/etc/wicd/wireless-settings.conf), validating authentication and obtaining an IP address (use ifconfig to verify that you have an “inet addr”).

Ignore the rest on this page.

Reading Raspberry Pi: WLAN einrichten… I bought the Nano-WLAN-USB-Stick 150 Mbps by hama.

pi@raspberrypi ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. 
Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
pi@raspberrypi ~ $ sudo apt-get install firmware-realtek
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
firmware-realtek ist schon die neueste Version.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

Apparently I installed it already. iwlist wlan0 scan results in a lot of output. Including the network I’m looking for:

pi@raspberrypi ~ $ iwlist wlan0 scan | grep Schroeder

Set your network and password using sudo nano /etc/wpa.conf. This is what you want:

 pairwise=CCMP TKIP
 group=CCMP TKIP

Edit the list of interfaces using sudo vi /etc/network/interfaces and append the following:

auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa.conf

I was astonished to find some stuff relating to wlan0 in the file already. Anyway, I followed the instructions…

Restart and check:

pi@raspberrypi ~ $ ifconfig
eth0      Link encap:Ethernet  Hardware Adresse b8:27:eb:81:a6:af  
          inet Adresse:  Bcast:  Maske:
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:17450 (17.0 KiB)  TX bytes:14232 (13.8 KiB)

lo        Link encap:Lokale Schleife  
          inet Adresse:  Maske:
          UP LOOPBACK RUNNING  MTU:16436  Metrik:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:1104 (1.0 KiB)  TX bytes:1104 (1.0 KiB)

wlan0     Link encap:Ethernet  Hardware Adresse 80:1f:02:8f:91:26  
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

The last entry is shows that we didn’t get an IP number. Oops! It turns out that there is some other stuff in the /etc/network/interfaces file that might interfere. Commenting them out, I have:

auto lo

iface lo inet loopback
iface eth0 inet dhcp

# allow-hotplug wlan0
# iface wlan0 inet manual
# wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
# iface default inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa.conf

Still doesn’t work, however. I tried a few variants for the config files. Nothing seemed to work. This makes me so tired. I’m not sure I’m learning much. This is “fiddling with GNU/Linux” and frustrating. :(

Then I read How to install Wifi on a Raspberry Pi which tells you to install wicd-curses.

That seemed to work! Suddenly ifconfig provided me with an IP number for wlan0. I removed the ethernet cable, rebootet, and was unable to connect. Did the IP number change? Is DHCP taking too long? Why is bonjour not working? Patience! It just takes forever to boot. After a minute—long enough to write this paragraph--it suddenly worked:

alex@Pyrobombus ~$ ssh pi@raspberrypi.local
pi@raspberrypi.local's password: 
Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l


Tags: RSS

Comments on 2013-05-07 Raspberry Pi WiFi

If you start X, there is a GUI app on the desktop to set up the wifi :)

Radomir Dopieralski 2013-05-08 08:07 UTC

Hah. The problem there is how to provide keyboard, mouse and wifi all at the same time without a USB hub. I think I need a hub.

AlexSchroeder 2013-05-08 10:17 UTC

If you get a powered hub, your Pi will take power from it too!

Radomir Dopieralski 2013-05-16 18:15 UTC

Add Comment

2013-05-07 WMA to MP3

This is based on How to Convert Unprotected WMA Files Into MP3 Files. I’m leaving the instructions here for my future self. :)

for file in *.wma; do
  mplayer -vo null -vc dummy -af resample=44100 \
    -ao pcm:file="${file%%.[Ww][Mm][Aa]}.wav" "$file"
  lame --preset standard "${file%%.[Ww][Mm][Aa]}.wav" \

Use locate lame|grep 'lame$' and locate mplayer|grep 'mplayer$' to find the location of your executables. On a Mac, they’re probably not on your PATH… I installed MPlayer OSX and iTunes-LAME to get the executables. You’ll need to do something similar.

This is the result I just used for some files with upper case file extension:

for file in *.WMA; do
  "/Applications/MPlayer" \
    -vo null -vc dummy -af resample=44100 \
    -ao pcm:file="${file%%.[Ww][Mm][Aa]}.wav" "$file"
  "/Applications/" \
    --preset standard "${file%%.[Ww][Mm][Aa]}.wav" \


Add Comment

2013-05-07 iPhone Sync and Not Enough Disk Space

Once again, I’m syncing my wife’s iPhone 4S using iTunes and half way through the process it claims that it can’t do it because the computer is out of disk space. With more than 9 GB on the main hard disk and much more on the external hard disk (and a link from ~/Library/Application Support/MobilySync to the external hard disk), this is simply impossible. Strangely enough, synchronization continues anyway.

Luckily I remembered what to do: open preferences, find the backup for my wife’s device and delete it. Done. Now I can sync without any messages interrupting it. Strange.

Update: August 1, 2013. Same problem. Same solution.


Add Comment