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
This essentially boils down to getting Netflix on Linux; which (except for Android) is intentionally not supported and difficult. I haven't seen any solution yet (for any Linux, RPi aside) that didn't involve serious and unstable hacks or some type of Windows emulation/re-implementation (which is not going to be a viable option with the ARM/x86 architecture ...
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.
I run the RPi as my media station with Xbmc (now named Kodi) on Arch Linux. I have an external 1TB HDD (with external power supply) attached which holds my movie/series collection.
Xbmc has Library features for Movies, Pictures, Series and Music with extended functionality (order by year, actor, whatever).
But, before creating a library in Xbmc, ...
Ugg. I wasn't able to solve my own problem the other day, but when I typed out the question, then I got inspired to search the interwebs in a different way that yielded a solution. My issue was that iptables is configured to block traffic that isn't on my subnet. You can test that this is the issue by running this command on your raspbmc:
sudo iptables --...
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-...
If you want use your RPi as NAS you should read this:
If you want use your RPi as Media Center you should read this:
You can do all this in one system.
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.
Please note that Plex no longer supports a Netflix channel (thus the following only has historical interest).
You could also use the Plex Media Server (PMS) - unlike PlayOn, it's free. As far as I know, the server needs to be able to play Netflix though. I use Windows 7 as the Plex Media Server. I don't know if using the Netflix-on-Ubuntu workaround ...
Due to people exposing SSH without changing the default password, I added some basic rules that restrict network access to LAN only. In a couple of days there'll be an option to disable these from Raspbmc's XBMC settings plugin, but for now, you can see this thread for advice
You can try adding hdmi_ignore_cec_init=1 config option to your /boot/config.txt. It should, in theory, disable sending initial active source message by RaspberryPi which is probably responsible for changing input source to HDMI in your case.
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/...
I believe your problem is your USB stick is formatted as NFTS or FAT, filesystems that do not support the per-user/group permissions. The solution is to reformat as ext4. If you do that, you will also have much less lag if you are using your Pi as a media center. The drivers for the Pi are much faster when you use ext4.
Right at the top of the raspmc homepage it says:
The firewall that we added in the release can now be enabled and
disabled via Raspbmc Settings.
They claim elsewhere the firewall is iptables and the system is debian based, so if you can't find Settings or it doesn't work, look thru the list returned by service --status-all for "iptables". If it's ...
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 ...