After lots of reading and frustration. First of all, make sure the normal user has read and write acces to the USB drive. The correct 'non-root' fix for having write acces to the USB drive is:
Step 1: Stop transmission daemon
sudo service transmission-daemon stop
Step 2: Add pi to debian-transmission group
sudo usermod -a -G debian-transmission pi
something like this might help:
$ ssh email@example.com.XXX 'echo raspberry | sudo shutdown -r now'
this command connects to your raspberry using SSH and issues the reboot command, make sure you replace 192.168.1.XXX with the real address and pi/raspberry with your real login/password.
As @lenik's answer says, your TV needs to support CEC. I installed a compiled version of libcec which included the command line utility cec-client from SourceForge using the following commands:
wget http://sourceforge.net/projects/selfprogramming/files/libCEC.deb/libcec_2.1.0-1_armhf.deb/download -O libcec_2.1.0-1_armhf.deb
sudo dpkg -i libcec_2.1.0-...
I use OpenELEC, and it is working very fine as a media center. Therefore it doesn't allow you to use it as a "normal" Linux. It doesn't have a window manager; only XBMC is started on boot.
It also allows you to use it through SSH, but it doesn't have apt-get.
For normal users I would say they are somehow similar, and the differences are not that huge. However, for advance users they are different. OpenELEC has a huge disadvantage for people who like to further customize their Pi since the system come as a read-only image, e.g. you cannot disable or enable services and you cannot even change the root password ...
You could use qemu (http://wiki.qemu.org/Main_Page) to emulate a Raspberry Pi on your computer, and feed your SD card as the boot device in the command line options of qemu.
QEMU can be used on Windows/Linux/Mac.
More resources about this :
http://www.smallbulb.net/2012/225-emulating-raspberry-pi (Windows again)
Your original config was ok, except for the comma's in your first line.
So use auto lo eth0 wlan0 instead...
auto lo wlan0
iface lo inet loopback
iface wlan0 inet manual
iface default inet static
you need a TV set that supports CEC (Consumer Electronics Control) protocol over HDMI. it might be a good idea to consult your TV manual or company web site to find details regarding your particular case, also quick search for "TV_model + CEC" might give you a few pointers.
basically, if your TV set is made just a few years ago, there's a good chance you ...
None of the answers here worked for me, so I am writing a new one referencing https://pimylifeup.com/raspberry-pi-torrentbox/ which worked great for me and allowed me to run transmission as pi user to access my USB drive. This is not directly answering the OP but this question is very popular (first Google result) for this sort of problem so I put it here.
In addition to @Krzystof 's excellent answer, I would quote what I read in this post:
Include the hdmi_ignore_cec_init=1 switch in /boot/config.txt.
Then in Settings>System>Input devices>Peripherals>CEC turn off the option: "Make XBMC the active source at start".
The iptables "rules" commands in secure-rmc are very simplistic:
logger -t iptables "Configuring ip tables for interface $IFACE"
if [ "$IFACE" != "lo" ]; then
iptables -A INPUT -s $NETMASK -i $IFACE -j ACCEPT
iptables -A INPUT -i $IFACE -j DROP
(get_subnet is a function that extracts the subnet of interface $...
This sounds very much like some of your AVI files have video encoded with MPEG-2 or VC1 (or possibly some other unsupported codec) and you don't have the MPEG-2 or VC1 codec installed (only h.264/MPEG-4 content can be played by default). I had exactly the same issue when I first installed RaspBMC and tried to play DVD content (it plays like an audio file, in ...
With Raspbmc, exit XBMC from the shutdown menu (choose exit, not shutdown). At the blue screen press Esc and you will be greeted with a login prompt. The default username is "pi", the default password is "raspberry". I believe you can also press Esc during boot to access the console. Alternatively you could log in via SSH.
This will not work on OpenELEC.
You could try this. It is best used on the Raspberry Pi 2, because this is pure software rendered and will use a lot of CPU. You need to have Chromium installed.
tar -xzf PepperFlash-126.96.36.199-armv7h.tar.gz
chmod +x *
sudo cp * /usr/lib/chromium/plugins
sudo nano /etc/...
should do the trick of cleaning your current setup, or you may use the particular chain name you don't like:
iptables -F INPUT
I'd recommend to add these commands at the top of your script issuing iptables commands, so every time you start from a known situation.
Also, could you please elaborate more about what is your goal? the ...
Research. Research. Research.
After extensively researching this on the web. Trying out many solutions. Here's the one that worked for me.
1. Install lxde-core
sudo apt-get install lxde-core xserver-xorg xinit
2. Fix the Putty X11 proxy: wrong authorization protocol
Refer my own answer here on superuser
Since a lot of packages needed to be ...
There is an undocumented option in /boot/config.txt that might help you:
Tried and tested under Raspbian "Jessie" (not Raspbmc). The display goes to sleep after about 10 minutes of inactivity. Source: https://github.com/raspberrypi/linux/issues/487
[Note that the Pi itself cannot sleep like grown-up PC-s do.]
Edit: Turns out that this ...
I solved with Apt-Pinning.
In that way you can choose to use jessie's repository to obtain an update (!not the latest!) version of transmission, actually is 2.82-1.1.
Here how you can do it:
sudo apt-cache show transmission-daemon | grep Version
Will show you only one version (the wheezy's version), right?
Add jessie repository to /etc/apt/sources.list:
TLDR: Use this line:
tcpflags = syn
instead of this :
tcpflags = syn,ack
I found it useful when debugging to run the knockd daemon in interactive mode:
sudo service knockd stop
sudo knockd -D -v
This way the daemon runs in the foreground and prints its configuration and then real-time status messages.
I then tried ...
You could make something like a TV remote with an IR LED. There is a tutorial on Adafruit on what you would like to do. Here is another blog post about the same subject.
Note: You will have to use the GPIO pins. I'm not sure if you were looking for a solution that used them or not.
After installing the cec-client per the above answer by HeatfanJohn, I am successfully able to power on/off my Vizio E390i-A1 LED HDTV. I wrote a script for the community:
Create new file via:
mkdir /opt/scripts; vi /opt/scripts/turntv.sh
paste in the following:
#Written by CaptainRewind for the RaspberryPi community
#Modify as needed
The H.264 license is included. If you stick to H.264, you don't need an extra license.
DVD playback is problematic, because you can buy the MPEG2 license, but it's not currently possible to buy a license for the DTS audio.
You may be able to decode DTS audio satisfactorily in software on an overclocked RPi. For example an H.264 with 1536kb/s DTS audio I ...
Wireless is very generalised and mis understood.
You need to examine your Wireless configurations before you can try and adjust speed.
Many new routers come pre configured to run in mixed mode, using both the g and n standards. This is great if you want all your devices to work together but it becomes a real problem when you start to transfer large ...
Figured it out when I opened it up in a tmux window because it was getting annoying to keep killing the terminal tabs; just do a ctrl+D and that will dump you back in the shell:
sqlite> select * from files where strFilename like %Recreation%';
Suppose your drive drains power from USB port, like most of 2"5: it does not work as PI does not give enough current on those ports. It the drive has its own power supply (most of 3"5), it should work fine.
Another option is to get a self-powered USB hub.
Disconnecting the Raspberry Pi will most likely solve the problem. Just remember that disconnecting Rpi straight from the power source will not cause physical nor driver damage to the SD Card. If you do reconnect and you find that the Raspberry Pi does not boot up or acts funny, reformat the SD card & reburn the OS (Noobs Image) back onto the Sd card.