Hardware
My current hardware setup seems to work okay with the Raspberry Pi.
- Raspberry Pi model B
- Pretty Adafruit Pi Box (Enclosure)
- Belkin Gold Portable Audio Player-to-Stereo Cable (2xRCA male to 3.5 mm male)
- Belkin USB 2.0 Micro B Cable
- Sitecom USB 2.0 hub 4-port with power adaptor and weird USB port on top (ART. CODE CN-050 v1 002)
- SanDisk Ultra SDHC Card 32 Gb class 10
- Perimac USB 2 to Fast Ethernet Adapter
- RCA cable (male to male) (I had one lying around)
Software
- mpd - Music Player Daemon (plays audio files in "/var/lib/mpd/music")
- deluged - Deluge BitTorrent Client [2]
- deluge-console - Deluge BitTorrent Client console
- xbmc - X Box Media Center
- Java JDK 8 - for the arm hf
Reasons
- wanted to have internet 'always on' without a lot of power/computers involved
- wanted to be in control of the software
- wanted to download stuff easily
- wanted to be able to send my solar panels input to the internet during daylight hours
- wanted to play music on my (very old) stereo
- wanted to do stuff with our old TV
- wanted new toys to play with
Trying Wheezy Raspbian
I've downloaded Wheezy Raspbian, nowadays with Hard Float, and put it on a 32 GB SD Card.
dd bs=4M if=2013-07-26-wheezy-raspbian.img of=/dev/sdb
Downloaded 2013-05-29-wheezy-armel.zip first, which is the Software Floating Point image. XBMC is compiled for the Hardware Floating Point image. So, it won't work. Originally, I had envisioned playing with Java, and Java SDK was not available for Hardware Floating Point at the time. This has now been remedied, luckily. So no reason not to use Hardware Floating Point.[5][6]
Installing XBMC
Now, I've already tried RaspBMC, and I didn't like the fact that my default linux network scripts were replaced by XBMC scripts. Especially, as I had a non-standard setup (two ethernet ports).
So I installed XBMC on a standard Wheezy Raspbian. [4]
My TV is Black & White?
My TV provided a black and white screen. Now, given I'm European, I assumed the TV to use PAL (Phase Alternating Line, 'Picture Always Lousy') and not the (American?) NTSC (National Television System Committee, 'Never The Same Colour'). NTSC is probably the default.
Added sdtv_mode=2 to /boot/config.txt (0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL.)[1]
Attaching a second Ethernet by means of USB
I'm wanting to use the thing (amongst other things) as my little firewall.
My second ethernet is detected. Yay! My /etc/network/interfaces file looks like:
auto lo eth0 eth1
iface lo inet loopback
iface eth1 inet dhcp
iface eth0 inet static
address 10.0.0.11
netmask 255.255.255.0
#allow-hotplug wlan0
#iface wlan0 inet manual
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp
iface lo inet loopback
iface eth1 inet dhcp
iface eth0 inet static
address 10.0.0.11
netmask 255.255.255.0
#allow-hotplug wlan0
#iface wlan0 inet manual
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp
I have my little firewall script in "/etc/network/if-up.d/" so it runs upon boot, after network setup. But I usually forget to turn on "net.ipv4.ip_forward" in /etc/sysctl.conf.
Root access
Root access to Raspbmc is disabled, and you should use 'sudo'. But you can turn it on. http://www.raspbmc.com/wiki/user/root-access/.
I was never a "sudo" guy, but I'm getting used to it.
Expanding the root partition by hand
My Second SD card provided the following problems, after indicating that the Raspberry Pi should expand the SD Card partition and reboot. As the other SD card I have did not have this problem, I surmise that the SD card is a bit dodgy. This is the message I saw (a lot) on the screen upon boot:
end_request: I/O error, dev mmcblk0, sector 137029
mmcblk0: error -110 transferring data, sector 137030, nr 185, cmd response 0x900, card statux 0xb00
So, I attempted to expand my SD Card partition on my labtop. That fixed the problem (for now).[7]mmcblk0: error -110 transferring data, sector 137030, nr 185, cmd response 0x900, card statux 0xb00
References
- [1] RPiconfig
- http://elinux.org/RPi_config.txt
- [2] How to Turn a Raspberry Pi into an Always-On BitTorrent Box
- http://www.howtogeek.com/142044/how-to-turn-a-raspberry-pi-into-an-always-on-bittorrent-box/
- [3] RaspbianXBMC
- http://www.raspbian.org/RaspbianXBMC
- [4] Michael Gorven's XBMC packages for the Raspberry Pi
- http://michael.gorven.za.net/raspberrypi/xbmc
- [5] JavaFX on Raspberry Pi in 3 Easy Steps
- http://javafx.steveonjava.com/javafx-on-raspberry-pi-3-easy-steps/
- [6] OpenJDK version for the Raspberry Pi
- https://wiki.openjdk.java.net/display/OpenJFX/OpenJFX+on+the+Raspberry+Pi
- [7] RPi Resize Flash Partitions
- http://elinux.org/RPi_Resize_Flash_Partitions
- Official Raspberry Pi Website
- http://www.raspberrypi.org/
You do know that the whole Raspberry is built on a single USB bus right? So your Ethernet is actually limited to the shared bandwidth of the USB.
ReplyDeleteAnd the 480Mbit/sec USB 2.0 standard doesn't seem to bad. But beware, the Raspberry has had plenty of instability reports when running on full speed/full bandwidth. And depending on your PV Converter, it may require you to set the speed to USB 1.0. If that is the case (like in the case of my Pi/PV) there isn't a lot of "other" stuff it can do.
RPi as media box; USB 2.0 is fine for applications like streaming music and uploading your PVoutput stats, several folks have found the Raspberry to be a little limited in power and bandwidth to do proper streaming video or media-box applications (XBMC with additional apps runs, but is like Vista on a Pentium1). With video, even if you buy an mpeg license so it has hw-accelerated decoding, the system-on-a-chip is underpowered as an HTPC. Sadly. Because the Pi is a lovely little box.