The ISO image of Raspberry Pi Desktop is available here.

I did create an VM, as illustrated here, with:

• 4GB Memory
• 32GB Hard Disk(SCSI)
• USB 3 .1
• And everything else “by default”
  • 1 processor
  • NAT Network Adapter
  • …

I did:

• a “Graphical Install” of the Raspberry Pi Desktop
• enable SSH
• keep the password “raspberry” for the user pi (with auto-login enabled)
• configure the keyboard for me (Belgian – Azerty)
• configure to location as Brussels/Belgium
• install the VMWare-Tools (screen resolution maximized automatically)
• Create an icon “Desktop Update” to update the packages via: sudo apt-get update && sudo apt-get upgrade -y

And here attached in the resulting VM (a 4.5GB zip file). Download it, unzip and double click the file “Raspberry Pi 4.vmx” to open the VM into your VMWare Workstation.

Et voilà.

Install an OS on your RPI 4

1. Download the “Raspberry Pi Imager” here.
2. Download next the “Raspberry Pi OS (32-bit) with desktop” here (the 64-bit is still only in beta. See here). Unzip the file.
   • This is the smallest image (no extra softwares) with a Desktop (mandatory to display the Plex Media Player GUI)
3. Install and Run the “Raspberry Pi Imager” to setup the “Raspberry Pi OS” on a micro-SD card.

• • Click on “Choose OS”

• • Select “Use Custom”

• • Pick the .img file “YYYY-MM-DD-raspios-buster-armhf.img” unzipped from the “Raspberry Pi OS (32-bit) with desktop” image.
  • Next Click “Choose SD” and “Write”.
  • Once the operation completed, install the micro-SD in your RPI 4 and turn it on. The Raspberry Pi Desktop will appear after some automatic reboots. Follow the setup of the Welcome screen. Steps are:
    • Setup the Country (use Page up and Page down in the Country Combo to scroll faster)
    • Change the Password of the user ‘pi’. ATTENTION: the keyboard layout is most probably not the right one. Untick the “Hide characters” option to check what you type!
    • Set Up Screen
    • Select Wireless Network (You can skip this step if the RPI is connected via ethernet). Again, untick the “Hide characters” option to check what you type!
    • Update Software
    • Click “Restart” on the last step “Setup Complete”

Configure your OS

Open a “Terminal” :

First, type this command in the Terminal to check your IP address:

ifconfig

Type next this command to configure the os:

sudo raspi-config

Among other:

• Configure your keyboard if required via “4 Localisation Options” > “change keyboard layout”
  • If your keyboard is not in the list, use the Generic 100x-Key PC corresponding to your layout. Look the picture of this wiki page for more details.
  • You can possibly also find more info about your keyboard here.
• Enable SSH via “5 Interfacing Options” > “P2 SSH”
• Give at least 512MB or more to your GPU via “7 Advanced Options” > “Memory Split” (I did set 512. Using 1024 result in a black screen after reboot)
• I gave the whole micro-SD card storage for the OS via “7 Advanced Options” > A1 Expand File System”
• I set the audio output on the HDMI port via “7 Advanced Options” > A4 Audio”
• NB.: I don’t use the 4Kp60 HDMI, but it can be configured via “7 Advanced Options” > AA Pi 4 Video Output”
• Finally, reboot to be sure that it still work.
  • If you have an issue, wait for 3 minutes and proceed with the next step here under.

You can now open a SSH console from your PC (E.g: using PuTTY) to connect on the IP address found previously and login with the user ‘pi’ and the password you introduced during the installation.

You will possibly get a PuTTY Security Alert because of the ssh key fingerprint… Accept if you are sure that you are connecting safely to your RPI.

If it seems that your RPI didn’t reboot properly and you are not able to connect using SSH after a moment, they you probably have to redo to whole setup from scratch and try other configuration options within raspi-config

If it seems that your RPI didn’t reboot properly and you are able to connect via SSH, redo the configuration with the command sudo raspi-config (try to reset the “Memory Split” to 64 if you did change it).

If you want to be sure that your OS is up-to-date, with the very latest fixes, type the following commands:

sudo apt-get update

sudo apt-get full-upgrade

And finally disable the screen sleep with the command

sudo sed -i 's/#xserver-command=X.*/xserver-command=X -s 0 dpms/g' /etc/lightdm/lightdm.conf

Build PMP for your RPI 4

Use now the SSH console (to be able to copy/paste from here) to execute this:

sudo apt-get install -y autoconf automake libtool libharfbuzz-dev libfreetype6-dev libfontconfig1-dev libx11-dev libxrandr-dev libvdpau-dev libva-dev mesa-common-dev libegl1-mesa-dev yasm libasound2-dev libpulse-dev libuchardet-dev zlib1g-dev libfribidi-dev git libgnutls28-dev libgl1-mesa-dev libsdl2-dev cmake python3 python python-minimal git mpv libmpv-dev

Then these 3 commands:

wget https://github.com/koendv/qt5-opengl-raspberrypi/releases/download/v5.12.5-1/qt5-opengl-dev_5.12.5_armhf.deb 
sudo apt-get install -y ./qt5-opengl-dev_5.12.5_armhf.deb
rm qt5-opengl-dev_5.12.5_armhf.deb

And finally these:

mkdir ~/pmp
cd ~/pmp
git clone git://github.com/plexinc/plex-media-player
cd plex-media-player/
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Debug -DQTROOT=/usr/lib/qt5.12/ -DCMAKE_INSTALL_PREFIX=/usr/local/ ..
make -j4
sudo make install

Now, PMP can be run. Go back to the Raspberry Pi Desktop, and type this command in a Terminal:

plexmediaplayer --fullscreen --tv &

In my case, the option ‘tv’ is not convenient (I can’t see enough on the screen)…

You will have to Sign In via the link page of Plex.tv and next configure Plex Media Player.

Configure PMP to launch at boot

Back into you SSH Console, on your PC, create a new user ‘plex’ with a password:

sudo adduser plex
sudo adduser --disabled-password plex
sudo passwd -d plex

Login as ‘plex’ in your RPI desktop to run once PMP via a Terminal (Without this step, it will not be displayed full screen after an autologin):

plexmediaplayer --fullscreen --tv &

Configure the user ‘plex’ to autologin with a desktop session named ‘plex’:

sudo sed -i 's/#*user-session=.*/user-session=plex/g' /etc/lightdm/lightdm.conf
sudo sed -i 's/#*autologin-user=.*/autologin-user=plex/g' /etc/lightdm/lightdm.conf
sudo sed -i 's/#*autologin-user-timeout=.*/autologin-user-timeout=delay/g' /etc/lightdm/lightdm.conf

Create the ‘plex’ desktop:

sudo nano /usr/share/xsessions/plex.desktop

and paste into it:

[Desktop Entry]Name=Plex
Comment=Plex Media Player
Exec=/usr/local/bin/plexmediaplayer
Icon=
Type=Application

And now reboot ! (It can take 3 long minutes !!):

sudo reboot

If there is a configuration issue with the desktop, edit the config via a SSH console and restart lightDM (the Desktop Manager):

sudo service lightdm restart

Tips: I had no issue with getting Plex Media Player in fullscreen but here are notes in case I would have to resize it:

sudo apt-get install -y xdotool
export DISPLAY=':0.0'
xdotool search --onlyvisible --maxdepth 1 ""
xdotool windowmove {window_id} {posx} {posy} windowsize {window_num} {sizex} {sizey}

This is based on a post of Stueh on Plex forum (see here)

If you did configure Plex Media Player on a PC Screen and move next on TV Screen, it will most probably not fit that screen et the resolution will possibly not be correct. In that case, here is how I proceed:

• Log on your RPI using any SSH console on your mobile or Tablet (I presume that your PC is not next to your TV). I am using “RaspController” on Android
• Edit the desktop to force an error. Hence, you will fallback on the default Desktop. Type in you SSL console : sudo nano /usr/shared/xsession/plex.desktop
  • Ex.: modify this line to define an invalid path: Exec=xxx/usr/local/bin/plexmediaplayer
• Now, restart LightDM
  • Either type this in your SSH console: sudo service lightdm restart
  • Or CTRL-ALT-Backspace on the keyboard of your RPI.
• You will get an error message because ‘xxx/usr/local/bin/plexmediaplayer’ does not exist and next get a prompt to login.
• Login as ‘pi’ 
• Now, open the Start menu > Preferences > Raspberry Pi Configuration > Display (or Interfaces). If you don’t see the ‘Start menu’ because it is out of the screen, press the ‘Windows’ key on your Keyboard.

• Next, change the resolution to fit the limitation of your TV:
  • 480p = DVD, old TV 720 x 480 pixels, format 16/9.
  • 720p = HD Ready, 1280 x 720 pixels, format 16/9.
  • 1080p = Full HD, 1920 x 1080 pixels, format 16/9.
  • 2160p, UHDTV1, 3840 x 2160 pixels, format 16/9 (a.ka. UHD-4K or 4K).
  • 4320p, UHDTV2, 7680 x 4320 pixels, format 16/9 (a.k.a UHD-8K or 8K).
• Then, open Plex Media Player (Start Menu > …) and configure it in TV mode. If it does not fit the TV Screen, reduce the resolution.
• Finally, log off (or restrat lightDM with CTRL-ALT-BACKSPACE) and login as ‘plex’ to also run Plex Media Player and be sure it’s also well configured.
• Ho, yes, sure: edit again the plex.desktop to remove the xxx in the path of the EXEC setting and reboot.

Voilà

I had no issue when playing a movie with my PC or with my ChromeCast, both of them being however connected on the same home cinema amplifier (a Yamaha HTR-4067) as the Raspberry PI 2 and, from there, on the projector (a Benq W1070+) via a long HDMI cable.

The problem became especially unsupportable with 3D movies as not only the signal was lost, but also the projector was coming back in 2D mode. So, I had to set it back in 3D when the signal was recovered.

It was sometimes mentioned on various blogs or forums that the problem could have been with the HDMI cable, with the power supply of the Raspberry Pi 2, with the HDMI port of the amplifier, … But I found the true solution here: boost the HDMI signal in the config file of the Raspberry Pi 2.

While already being in the config file to solve the problem, I took the opportunity to also overclock a bit the Raspberry as documented here. And finally, as I noticed that there was no specific memory size set for the GPU on my Raspberry, which has 1Gb Ram, if fixed that too. It seems to me that the config file used by RasPlex is not fully optimized for the Raspberry Pi 2.

To edit the “config.txt” file, I simply put the SD card of the Raspberry Pi 2 into my Windows PC and opened that file with Notepad++ (it’s located on the root of the card). I ended with a config file like this one (changes are in bold):

My Home Theater System includes:

• A amplifier Yamaha HTR-4067
• Speakers Eltax Monitor 91 HC  with
  • two floor-standing speakers Eltax Monitor IX
  • two speakers Eltax Monitor I
  • one speaker Eltax Monitor Center
• A subwoofer Yamaha NS-SW200
• A projector BenQ W1070+
• A Raspberry Pi 2 with RasPlex

NB.:

• The Raspberry is connected on the “HDMI 1 (BD/DVD)” input.
• I had to change the HDMI cable to use one certified “High Speed with Ethernet”.
• I had to turn on first the Amplifier, next the projector, and finally the Raspberry.

When starting, Rasplex  :

1. Detects the “Pulse-Eight CEC adapter”
2. Updates the CEC adapter configuration
3. And finally displays a message: “connected: TV-HTR-4067”

Within Plex:

• I went to “> Preferences > Change Preferences for System”
• I selected “Input Devices” and then “Peripherals”
• There, Plex displays info about the “CEC adapter”. I did click on “Ok” to enter the settings of that adapter. There, I have the following settings:
  • Enabled is ticked
  • Make XBMC the active source when stating is not ticked
  • “Device to power on…” is none
  • “Device to pwoer off…” is none
  • “Send inactive source…” is ticked
  • “Put device in standby…” is not ticked
  • “When the TV is switched off” is “Ignore”
  • “Put device in standby” is not ticked
  • “Use the TV’s language setting” is not ticked
  • “Pause playback” is ticked
  • “Physical address (overrules HDMI port)” is 0
  • “Com port” is –

Notice: when the amplifier is switched off (standby), the video is still forwarded to the projector, as well as the sound. But what’s great is that the remote control still works too via CEC !!!

I have a Raspberry Pi model b with 512 Mb Ram.

1. In order to find the reason of the problem, I have activated the logging on XBMC: In  Settings -> System -> Debugging, toggle the Enable debug logging setting.
2. I have opened a Smart Playlist and started a movie. I only got the sound but no video.
3. I have looked into the log file, whose path depend on the distribution:
   • OpenELEC: /storage/.xbmc/temp/xbmc.log
   • Raspbmc: /home/pi/.xbmc/temp/xbmc.log
   • XBian: /home/xbian/.xbmc/temp/xbmc.log
4. In that log I found this:

The problem was “Insufficient Resources”. Googling on that I found a simple solution: add more ram for the GPU.

1. Open a telnet session to the Raspberry Pi and log (user: pi, password raspberry on RaspBMC)
2. Edit the config.txt file which is located in /boot.
3. Set gpu_mem_512=256 (instead of the current value 128)
4. Restart the Rasberry Pi using the command: sudo reboot

If editing the config.txt file using “telnet” is not easy, possibly “ftp” the Raspberry to “get” the file, edit this one on Windows and “put” it back.

Regarding the codec problem that can occur, it’s usually for mpeg2 video as one has to purchase the mpeg2 license and configured the raspberry pi. See this blog for details.

About logging: http://wiki.xbmc.org/index.php?title=Log_file/Easy

About Raspberry pi : http://wiki.xbmc.org/?title=Raspberry_Pi/FAQ

256MB version

For older RaspberryPi, with 256 MB of RAM, 4 splits are available:

• 240/16 – The most RAM size ARM can get (240MB) with mimial GPU memory. It’s the best for general computing when you don’t need 3D graphics or hardware video acceleration. It has enough memory to handle 1920x1200x16bpp framebuffer resolution. While 32bpp is also working, it’s not recommended since it leaves very small amount of free memory for GPU.
• 224/32 – This one is deprecated in favor of 240/16 split. It has 3D and hardware video decoding build in but since there is not enough memory to actually use it, there’s little point in using it. Unless you have some problems with 240/16 split or want to use 32bpp framebuffer at highest resolution. It is possible it will be deleted in the future.
• 192/64 – You need at least 64MB of GPU split to use hardware video acceleration or 3D graphics. It may not be enough GPU memory for hardware accelerated video playback at highest resolution or if you need a lot of GPU memory for things like textures.
• 128/128 – The most RAM GPU can get. Use it when you need a lot of memory for 3D graphic card and hardware accelerated video playback in high resolution. This split is needed for RaspBMC to work properly or to play fullHD video content with omxplayer without problems.

512MB version

New versions of RaspberryPi has 512 MB of RAM. You have 4 additional splits designed for this version:

• 496/16 and 448/64 – like 240/16 and 192/64 split for 256MB respectively but with 256MB more RAM available for ARM. Since GPU has only 16 MB/64MB or RAM, all the limitations from240/16/192/64 still apply.
• 384/128 – Similar to 128/128 split for 256MB – you should get all the graphic chip features but with reasonable amount of ARM memory. This will probably be the most universal split right now.
• 256/256 – Some bonus graphic card memory if you really need it, like for big textures and similar things. While 256MB of ARM memory is bigger than you could possibly have in older RaspberryPis, I don’t think this one will be used on many occasions.

Mine is in a black case bought from RS components. I also bought there a power supply and a HDMI cable. The big advantage of using a Raspberry pi is that

• It has a very low power consumption (about 1-2 watts at idle)
• It is really small 85.60mm x 53.98mm x 17mm (invisible behind the TV)
• It has a HDMI with Audio with CEC support (you can pilot XBMC on the Raspberry Pi with the TV remote control)
• It comes with codec license for MPEG4 & H.264 (hardware accelerated)
• Licenses can also be bought here to play back MPEG2 or VC1.
• The Model B comes with 512MB Ram (Only 256 on the Model A)
• It boots a Linux from a SD card (= silent) in about 50 seconds (depending on the distribution). There are 3 distributions of Linux with XBMC targeting the Raspberry Pi (see the wiki here). Some Install Guides:
  • Raspbmc (The one I am using)
  • OpenElec
  • XBian
  • Look at this comparison (and read also its previous version)
• A 2GB SD is enough, but I use a 16GB class 6, the only SD I had
• There are 2 USB slots that I use for a keyboard and a mouse. That can be expanded with a USB hub (There is only one USB port on the Model A). A USB HDD can be plugged to add extra storage if required.
• There is a 10/100Gbs Ethernet Port (No Ethernet port on the Model A) with supports of various power management wakeup features, including Magic Packet, Wake-on LAN (WOL) and Link Status Change. UNFORTUNATELY, albeit Pi’s Lan chipset does support WOL, the Pi’s lack of power management (ACPI) means it doesn’t support this Lan chipset features
• It does not need a fan cooler (= silent)
• The Model B uses a standard power supply capable of supplying 5V 700ma (the Model A requires 5V 300ma)
• The GPU is capable of 1Gpixel/s
• It can be easily overclocked (and overvolted to increase stability) up to 1000MHz (without making the warranty void !). By default the Raspberry Pi runs as 700Mhz and is overclocked at 800Mhz by RaspBmc…
• Overall real world performance is something like a 300MHz Pentium 2 with great graphic performances.

site: http://www.raspberrypi.org (Look at the quick-start-guide and the FAQ)

RaspBmc: http://www.raspbmc.com (Look at the FAQ)

XBMC for Raspberry: http://wiki.xbmc.org/index.php?title=Raspberry_Pi/FAQ

buy: http://raspberrypi.rsdelivers.com/default.aspx?cl=1