Been a lonnnngg time since I have done anything with the site (aside from renewing the domain for another 2 years). Nearly a year since my last update in fact! 😮 I simply haven’t found the time lately with one thing or another. I have been unable to keep up with answering all the comments I receive too, simply due to the volume I get through (on here and Youtube), and I feel bad for this as I would like to help people out, that was the whole purpose of creating this site. I do however notice that most people have the same or similar issues so I figured it would be a good idea to try and address all queries by creating a FAQ page.
…..so here it is! I will add to it as I see different queries arise but for the meantime this should answer most questions. Of course there is the ‘Readme’ file that I always include with each build too so please check that out too as you may well find your answers in there.
I am also unsure how much interest there is in these type of builds any more? When I first made my own dual-boot image it was because I wanted KODI and RetroPie on 1 SD card, but I didn’t like the version of KODI that I was limited to in the ‘standard’ build (and it was buggy), so I found a way to package it together with OpenELEC instead, which at the time was a 10x improvement (for me at least), on the other KODI version. These days I don’t know if that is still the case? I personally use a dual-boot of LibreElec with RetroPie now and I’m more than happy with it, but is it better than the regular ‘KODI’ provided in RetroPie / Raspbian? I don’t know. And it is this type of question that makes me wonder; is still a need for this type of multiboot build? These builds are probably ‘frowned upon’ by the actual developers of the OS’s that I am packaging up too because they work in slightly different ways so need a slightly revised instruction set (hence this FAQ), so there is that too, but anyway – I would welcome any thoughts in the comment section below. I appreciate I probably have somewhat of a closed audience here (you wouldn’t be here if you didn’t want a multiboot OS after all!). :p
All the best, Steve
- Can I create a copy of my SD card? – Yes, and I would strongly recommend you do! I use ‘Win32 Disk Imager’ to make my backups in Windows.
- Can I resize the partitions after I have installed the image? – No, all partition sizing must be carried out prior to installing the images using the steps outlined in the ‘readme’ file. This is a feature of NOOBS which cannot be otherwise avoided.
- Can I update the OS(s) when a new version comes out? – Yes, you can update each OS in the normal manner which will be detailed on their website. You may need to use FTP / Samba / SSH, or a Linux PC if you need to transfer files to the OS. I strongly recommend creating a backup of your SD card before you attempt any such changes.
- What are the SSH / FTP login details for the OS(s)? – The login details can be found on the official website for each OS.
- I have lost the add-ons that allow me to switch partition in KODI, can I get them back? – Yes, you can find my add-ons at multibootpi.com/addons/ – add this as a source in file manager and then install as you would a normal add-on. Now you can add a shortcut onto the home screen if desired (they will be in ‘Programs’).
- I changed theme / updated in RetoPie and lost access to a partition switching script, can I get it back? – Yes, the script will still be present in /home/pi/RetroPie/roms/ in a folder with the OS name (i.e. kodi, raspbian etc.) so you can either amend the new theme to create an entry for the OS that is missing, or you can just copy the script into the ‘ports’ folder instead.
- How do I overclock the Pi using a multiboot image? – You will need to overclock each OS separately by editing the individual ‘config.txt’ file for each. If you place the SD card into a Windows PC it will only show the boot partition for NOOBS (you don’t want to edit this). The easiest way to overclock is by using SSH and then using a text editor to edit the file. For example, when you have the RetroPie partition loaded, type in
sudo nano /boot/config.txt(the boot partition is mounted to /boot/ at startup in RetroPie).
- How can I set up my Pi LCD screen to a multiboot image? – As above you will need to edit your config.txt file for each partition separately whilst in that OS (I find it easiest to use SSH). Your screen should come with instructions on what text needs to be added into the config.txt file.
- I have no sound in an OS(s), how can I fix this? – This is again something that will require tweaks within the config.txt file. For specific config.txt teaks, including sound settings, please visit https://www.raspberrypi.org/documentation/configuration/config-txt/ and check out both ‘Video’ and ‘Audio’ sections to help with sound issues.
- I want to get back to the NOOBS OS selection screen, how do I do this? – To do this you need to remove a file in the NOOBS partition that prevents a partition being booted at launch. You can do this via SSH on the Pi by typing this into the console:
#this creates a mountpoint for the noobs partition – skip this step if you already have a mountpoint you prefer to use
sudo mount /dev/mmcblk0p1 NOOBS/
sudo rm NOOBS/autoboot.txt
Now the next time you reboot you will be presented with the NOOBS OS selection screen. Please note if you are using OpenELEC or LibreELEC then you will not need to use ‘sudo’ as you are alsready logged in as root / superuser by default.
- Will you be making some new versions of multiboot images? – Yes, when I get time to do it. Very busy with work and home at the moment, so apologies for lack of updates. 🙁 I would welcome any requests for improvements however in the meantime. 🙂