Hi,
First time posting so...hello!
I have been using Rasplex on an RPi for a while now. On a separate SD Card I have Raspbian. What I would like to do is combine the two so I have one system running command line Raspbian and be able to load Rasplex or come Plex client/hometheather.
I guess the first thing I should ask is, is this possible?
Like Ned already told you, what you ask for is not currently possible.
There is no PHT version available for Raspbian.
If you really need to run Raspbian and a plex client from the same card, there are two ways to do it.
1: Keep using your current Raspbian and install XBMC for it.
(Not sure what versions are available for that Linux distro.)
Then install the XBMC addon PlexBMC and a Plex-aware XBMC skin,
to make it work like a real Plex client.
You can at any time exit to Linux and then restart XBMC again as you please.
And Linux can access the partitions of XBMC for custom modifications.
But the Plex client will NOT be Plex Home Theater...
2: Make BerryBoot the primary boot of your SD card.
Then install Raspbian and RasPlex as two of the alternative OS of that card.
It's possible to have dozens of OS installed, on card or external USB drive.
Just make sure you have enough space for them. (I use a small boot card, and a large USB3 drive for the OS.)
You then have to reboot in order to switch between Raspbian and RasPlex (or others).
And the two OS (or others) do not share the same data partitions (virtual).
But you can still interact with RasPlex through SSH or SMB, from other devices in LAN.
That is the method I always use to customize things (alternate skin installs etc).
NB 1: For installs with BerryBoot you do not use the normal RasPlex image file directly.
You extract the "SYSTEM" file from within that image (can also be done by flashing, then copying).
Then you rename the extracted "SYSTEM" file to whatever you please, adding a ".img" extension.
But it's wise to use something descriptive, to separate this image file from others.
eg: I've used names like "BB_rasplex-RP-0.4.1_SYSTEM.img", to ensure I recognize it in any context.
Then you can add that image to your collection of other BerryBoot compatible images.
NB 2: It's the config.txt file of BerryBoot that you need to edit in order to add your RaspberryPi CODEC licenses (if you bought any), and it is also there that you can modify video mode and overclock settings. But whatever you choose here will have to fit ALL of the OS you install under BerryBoot, as these settings will be shared for all of them. Also, BerryBoot uses its own 'memory-split' method, so may behave a little differently from a standard RasPlex setup. (Adapts dynamically to some RAM needs.)
Here is an example of a complete working "config.txt" file for BerryBoot, compatible with RasPlex (tested).
disable_overscan=1
Peter’s CODEC Licenses
decode_MPG2=0x6d19ee69
decode_WVC1=0x466e4f4d
Ronald’s CODEC Licenses
decode_MPG2=0x1d6f36db
decode_WVC1=0x487c968f
gpu_mem=128
cma_lwm=16
cma_hwm=32
cma_offline_start=16
arm_freq=950
core_freq=450
sdram_freq=450
over_voltage=4
Berryboot settings, do not change
kernel=kernel_rpi_aufs.img
initramfs berryboot.img
Note that the CODEC license codes obviously won’t work for you as-is, since they are specific to each RPi unit. But I included them here for two reasons. Partly because this is exactly the file I use, and partly because it shows a convenient way to make a config.txt file easily adapted for use with different RPi units (to switch I just comment and un-comment two lines each).
Make sure to read the BerryBoot docs fully before trying to make your own BerryBoot setup, as there are several pitfalls…
Best regards: dlanor