Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dual_boot_ubuntu_batocera.linux [2022/02/12 01:29] – added Ventoy ataridual_boot_ubuntu_batocera.linux [2024/09/21 20:15] (current) – [Ventoy] maximumentropy
Line 1: Line 1:
 ====== Dual boot Batocera ====== ====== Dual boot Batocera ======
  
-It is recommended to boot Batocera off of a USB drive and to use your BIOS boot selection menu to switch between Batocera and other operating systems that may already be on other drives. You can still [[:store_games_on_a_second_usb_sata_drive|use drives with other operating systems on them]] to host your userdata such as ROMs, BIOS files, saves, etc. However, some people prefer to have Batocera directly installed on the main hard drive alongside another pre-existing OS.+It is recommended to boot Batocera off of a USB/other external drive and to [[:install_batocera|use your BIOS boot selection menu]] to switch between Batocera and other operating systems that may already be on other drives. You can still [[:store_games_on_a_second_usb_sata_drive|use drives with other operating systems on them]] to host your userdata such as ROMs, BIOS files, saves, etc. This is the far simpler option to do instead of what you'll have to do if you only want to do everything from one drive. However, some people prefer to have Batocera directly installed on the main hard drive alongside another pre-existing OSes, this page is for that. 
 + 
 +<WRAP center round alert> 
 +Before attempting //any// of this, **make a backup of your data**. There is a chance that the following actions (shrinking partitions, replacing boot loaders, etc.) can render the storage devices inoperable. 
 + 
 +If this sounds too spooky to you, just [[:install_batocera|flash Batocera to a USB drive]] as is recommended and use that instead. 
 +</WRAP>
  
 Ordinarily, Batocera utilizes [[https://wiki.syslinux.org/wiki/index.php?title=The_Syslinux_Project|Syslinux]] to boot, which is configured to only boot Batocera. Thus, for most dual boot setups we will be utilizing [[https://www.gnu.org/software/grub/|GRUB]] to show a boot selection menu after BIOS has loaded instead. Ordinarily, Batocera utilizes [[https://wiki.syslinux.org/wiki/index.php?title=The_Syslinux_Project|Syslinux]] to boot, which is configured to only boot Batocera. Thus, for most dual boot setups we will be utilizing [[https://www.gnu.org/software/grub/|GRUB]] to show a boot selection menu after BIOS has loaded instead.
Line 11: Line 17:
 ===== Dual boot Batocera and Windows ===== ===== Dual boot Batocera and Windows =====
  
-You will likely have to wipe your hard drive's contents to do this, so no data can be carried over from a pre-existing Windows installation. To dual boot Windows and Batocera on the same drive:+==== Automatically ====
  
-  - Partition your intended drive to begin with a large physical NTFS partition for Windows. It is recommended to use a GPT partition table. The rest of the free space will be used for Batocera. +For those that prefer video guides (there is... no actual need to flash a spare USB drive, just download the boot.tar.xz): [[https://www.youtube.com/watch?v=VjyBKHadbgw|Pleilleur's Choice #1 Dualboot Windows 10 and Batocera]]
-  - Install Windows via your preferred method. It will re-partition the existing NTFS partition into smaller logical partitions, but should retain its total size. +
-  - In the empty space, add a new physical FAT32 partition around 8GB in size (can be larger if you want, but not smaller) labelled "BATOCERA". This will be used for Batocera's boot files. +
-  - Immediately after the BATOCERA partition, create another partition to fill up the rest of the drive. This will be used as the "internal" userdata. [[:add_games_bios#userdata_filesystem_options|Check out which filesystem to use.]] If you'd like to allow Windows to access the userdata partition, it is recommended to use exFAT or NTFS. BTRFS can also work, but requires kernel drivers for Windows to be installed to allow access to it. +
-  - Rename the folders in Windows' EFI partition from ''EFI/Boot'' to ''EFI/Boot_backup'' +
-  - Download [[https://updates.batocera.org/grub/EFI_WINDOWS.zip|this ZIP file]] and extract it. +
-  - Copy the contents of ''EFI_WINDOWS'' to Windows' EFI partition. The ''BOOT'' folder should be in the same spot as the old ''Boot'' folder was. +
-  - Boot into Batocera from a USB drive, run ''blkid /dev/sda#'' (where ''sda#'' is the Windows EFI partition) and note down the ID of the partition. +
-    * FIXME (confirmation needed) To do this on Windows itself, open an administrator command prompt and run ''diskpart'', ''list disk'', ''select disk=#'' (where # is the number of the disk with Windows EFI on it, usually 0), ''uniqueid disk'' to get your disk ID (add the hyphen in the middle). {{ :diskpart-disk-id.png?nolink |}} +
-  - Open ''ubuntu/grub.cfg'' and change ''2AD8-4A0C'' to the ID of the partition.+
  
-The final ''grub.cfg'' file should look like this: <file - grub.cfg>set default=0 +This guide is assuming Windows is being booted from an EFI partition. If it isn't, or you don't know, **proceed at your own risk**.
-set timeout=5+
  
-menuentry 'Windows 10' { +=== Preparing the drive ===
-  search --fs-uuid --no-floppy --set=root 2AD8-4A0C +
-  chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi +
-}+
  
-menuentry "batocera.linux" { +Partition the drive, having a 8 GB FAT32 partition after the Windows drive immediately followed by the "userdata" partition, which can be [[:batocera.linux_architecture#using_an_alternative_filesystem_for_userdata|any compatible filesystem]]. If preferred, it is also possible to [[:store_games_on_a_second_usb_sata_drive|have Batocera to use the Windows partition as its userdata]], however that requires manually setting it up before the rest of the installation so for first-timers this is not recommended. 
-  search --set=root --label BATOCERA + 
-  linux /boot/linux label=BATOCERA console=tty3 quiet loglevel=0 vt.global_cursor_default=0 +Extract and copy the latest [[https://mirrors.o2switch.fr/batocera/x86_64/stable/last/boot.tar.xz|Batocera ''boot.tar.xz'']] (can be extracted with 7-zip) to the root of the FAT32 partition. Its contents should look similar to the following: 
-  initrd /boot/initrd.gz+ 
 +<code> 
 +D:\ 
 +├─ boot\ 
 +├─ EFI\ 
 +├─ tools\ 
 +└─ batocera-boot.conf 
 +</code> 
 + 
 +=== Installing GRUB over Windows' boot manager === 
 + 
 +Download and install [[https://sourceforge.net/projects/grub2win/|grub2win]]. It may come up as a false positive on anti-virus software, we are going to be overiding the boot manager which could potentially prevent Windows from booting so maybe they are right in that regard. Either way, just let it through to continue. 
 +  - Extract the grub2win ZIP, and run ''setup.exe''. 
 +  - Allow grub2win to download the latest EFI package for your operating system. 
 +  - Ensure the target drive is the one the system boots into by default (usually C:\). Click **Setup**. 
 +  - Once it's done, click **Return To The Setup Menu**. 
 +  - Check "Delete setup files" if desired, and then **Close The Setup Program**. 
 +  - Grub2win will automatically scan for available operating systems. It will not find Batocera, unfortunately. Click **Manage Boot Menu** in the middle bottom of the window. 
 +  - Click **Add New Entry** near the top of the window. 
 +  - Under "Type", select **Custom code**. 
 +  - Name the "Title" as "Batocera", place it in whichever "Menu Slot" desired and reduce the "Pause Seconds" to **0**. 
 +  - Click **Edit Custom Code**. A text document will be opened with the default text editor. Paste in the following and save the file, for Batocera **v39** and higher: <code> 
 + set efibootmgr=/EFI/batocera/bootx64.efi 
 +     getpartition  file  $efibootmgr  root 
 +     if [ ! -z $reviewpause ] ; then 
 + echo GNU Grub will load the Batocera EFI Boot Manager at disk address $root 
 +         g2wsleep   
 +     fi 
 +     echo GNU Grub is now loading the Batocera EFI Boot Manager 
 +     chainloader $efibootmgr 
 +     savelast 1 'Batocera' 
 +</code>For Batocera **v38** and lower: <code> 
 + set efibootmgr=/EFI/BOOT/bootx64.efi 
 +     getpartition  file  $efibootmgr  root 
 +     if [ ! -z $reviewpause ] ; then 
 +  echo GNU Grub will load the Batocera EFI Boot Manager at disk address $root 
 +         g2wsleep   
 +     fi 
 +     echo GNU Grub is now loading the Batocera EFI Boot Manager 
 +     chainloader $efibootmgr 
 +     savelast 1 'Batocera' 
 +</code> <WRAP center round tip> 
 +Pleillear keeps an updated copy of the file at [[https://drive.google.com/file/d/1L5bf_DNFhYDFIieS8ktj41rbVfPRAD67/view|this Google Drive link]], so check that if this page hasn't been updated for a while.  Note that the file at this Google Drive link is not up to date for v39, and would need ''set efibootmgr=/EFI/BOOT/bootx64.efi'' changed to ''set efibootmgr=/EFI/batocera/bootx64.efi'' 
 +</WRAP> 
 +  - Close the text editor. 
 +  - Grub2win will then scan the code for mistakes. If all goes well, click **OK**, followed by **OK**. 
 +  - Check that the Batocera listing is correct and in the menu slot desired. Then click **Apply**. 
 +  - Set any further cosmetic settings desired. Lower the "Grub timeout" from **30** down to **10** and change the background by clicking on the preview. When done, click **OK**. 
 +  - Grub2win will then install the desired boot menu onto the drive. Green means it's good. Click **Close**. 
 +  - Reboot and pray to whatever entity that you want that it worked. 
 + 
 +===== Dual boot Batocera and MacOS or other UEFI-based x86_64 systems using rEFInd ===== 
 + 
 +<WRAP center round important> 
 +Although Windows can be hostile towards other operating systems (erasing their bootloaders on an update, clearing the master boot record without warning, etc.), Macs can be even more hostile. Keep this in mind and definitely have a secure method of restoring a backup when playing with the Mac's bootloader. 
 + 
 +For "Hackintosh" builds, this is usually safer. 
 +</WRAP> 
 + 
 +<WRAP center round important> 
 +Before installing rEFInd, be sure to read and understand the entire contents of its documentation first. Being negligent in this regard can result in an unbootable system if no flashing method is prepared earlier. To quote the author of rEFInd: "Note: I consider rEFInd to be beta-quality software! That said, rEFInd is a usable program in its current form on many systems." 
 +</WRAP> 
 + 
 +Install [[https://www.rodsbooks.com/refind/|rEFInd Boot Manager]] and check that the system is still booting. Batocera might be automatically detected (but with a generic name); if so lucky you! Otherwise, Batocera can be added manually by adding the following to the ''refind.conf'' file. 
 + 
 +<code> 
 +menuentry "Batocera" { 
 +    icon EFI/boot/icons/os_linux.png 
 +    loader /boot/linux 
 +    initrd /boot/initrd.gz 
 +    options "label=BATOCERA console=tty3 quiet loglevel=0 vt.global_cursor_default=0"
 } }
-</file>+</code>
  
 ===== Dual boot Batocera and other Linux distributions ===== ===== Dual boot Batocera and other Linux distributions =====
Line 69: Line 132:
 EOF EOF
 </file> </file>
 +  - Make it executable by running ''sudo chmod +x /etc/grub.d/50_batocera''
   - Run ''sudo update-grub''   - Run ''sudo update-grub''
   - Reboot   - Reboot
Line 80: Line 144:
 </WRAP> </WRAP>
  
-==== Linux Mint ====+==== Linux Mint/MX Linux ====
  
-For other distributions like Linux Mint 19.03, you can use the following method. +For other distributions like Linux Mint 19.03, you can use the following method. It also works for MX Linux, all mentions of Linux Mint also refer to MX Linux in this section.
  
 === Install Linux Mint === === Install Linux Mint ===
Line 94: Line 158:
   * Partition 2: type = ext4. It must be created and placed right after the ''BATOCERA'' partition.   * Partition 2: type = ext4. It must be created and placed right after the ''BATOCERA'' partition.
  
-Then download [[http://batocera.org/upgrades/x86_64/stable/last/boot.tar.xz|boot.tar.xz]] and unzip it on the ''BATOCERA'' partition.+Then download [[https://batocera.org/upgrades/x86_64/stable/last/boot.tar.xz|boot.tar.xz]] and unzip it on the ''BATOCERA'' partition. 
 + 
 +<WRAP center round tip> 
 +Since it's been set up manually, you can remove the ''autoresize'' flag from ''batocera-boot.conf''. It may interfere with booting if it's still on and there's no more space to expand to. 
 +</WRAP>
  
 === Configure the GRUB boot loader === === Configure the GRUB boot loader ===
Line 120: Line 188:
 </file> </file>
     * The file can also be automatically downloaded with the following command: <code>     * The file can also be automatically downloaded with the following command: <code>
-sudo wget https://batocera.org/upgrades/grub/15_batocera -O /etc/grub.d/15_batocera+sudo wget 'https://wiki.batocera.org/_export/code/dual_boot_ubuntu_batocera.linux?codeblock=4' -O /etc/grub.d/15_batocera
 </code> </code>
   - Then run the following commands: <code>   - Then run the following commands: <code>
Line 140: Line 208:
 Technically, this isn't really dual-booting, but booting a static image already loaded onto your drive's filesystem as its own mounted filesystem. It can ease the process of updating the image, however this is probably unnecessary as Batocera itself has [[:updates_and_downloads|its own updating tool]]. Nonetheless it could be useful for machines that otherwise don't have an internet connection and have to rely on another one to update or machines that absolutely refuse to boot via conventional manners. Technically, this isn't really dual-booting, but booting a static image already loaded onto your drive's filesystem as its own mounted filesystem. It can ease the process of updating the image, however this is probably unnecessary as Batocera itself has [[:updates_and_downloads|its own updating tool]]. Nonetheless it could be useful for machines that otherwise don't have an internet connection and have to rely on another one to update or machines that absolutely refuse to boot via conventional manners.
  
-By default, Batocera's userdata partition is only 512MB before expanding, obviously not large enough to do anything. Ventoy's boot process prevents Batocera from seeing the drive as having any available free space, so auto-expansion on the first boot never occurs. This can be solved by either //only// mounting Batocera's boot partition (thus making the next immediate partition the userdata partition, whatever that may be) or by running the following:+By default, Batocera's userdata partition is only 512MB before expanding, obviously not large enough to do anything. Ventoy uses the booted image file as a virtual hard disk, so with a factory-provided image, the userdata partition can't be auto-expanded beyond the baseline 512MB at first boot. This can be solved by either //only// mounting Batocera's boot partition (thus making the next immediate partition the userdata partition, whatever that may be) or by running the following (replace ''#'' with the number of GB you want in **total**, including the boot partition):
  
 <code> <code>
-qemu-img resize batocera.img +xG+qemu-img resize batocera.img +#G
 sudo losetup --find --show batocera.img sudo losetup --find --show batocera.img
 </code> </code>
Line 150: Line 218:
  
 {{:ventoy_mount.png|}} {{:ventoy_mount.png|}}
 +
 +If you want to keep using [[https://gparted.org/display-doc.php?name=help-manual#gparted-run-from-cmd-line|the command line for Gparted]]:
 +
 +<code>
 +gparted /dev/loop *
 +</code>
 +
 +If you prefer using a script instead of manual procedures, this will add a specified amount of space to a Batocera image file, 
 +and will expand the /userdata SHARE partition to fill the added space:
 +
 +<code bash| batocera-ventoy-resize.sh>
 +#!/bin/bash
 +# batocera-ventoy-resize.sh 20240921 n2qz/maximumentropy
 +# Expand a Batocera installation image file to make storage space
 +# available in SHARE when booting the image from Ventoy.
 +#
 +# Tested on Ubuntu 24.04.1 LTS with e2fsprogs 1.47.0. May not work on
 +# older versions of linux, as current Batocera images (v41+) use newer
 +# ext4 features not available with older ext4 utilities
 +err () {
 +    exitcode=$?
 +    echo "... Exit code $exitcode on line ${BASH_LINENO[0]} while executing command: $BASH_COMMAND"
 +    exit $exitcode
 +}
 +trap err ERR
 +growsize="$1"
 +inputimage="$2"
 +outputimage="$3"
 +if [ -z "${growsize}" -o -z "${inputimage}" -o "${inputimage}" = "${outputimage}" -o "${outputimage}" != "$(basename "${outputimage}" .gz)" ]
 +then
 +    echo "Usage: $0 growsize inputimage[.gz] [outputimage]"
 +    echo "Example: $0 32G batocera.img ventoy.img"
 +    exit 2
 +fi
 +image=$(basename "${inputimage}" .gz)
 +if [ -z "${outputimage}" ]
 +then
 +    outputimage="ventoy-${image}"
 +fi
 +if [ "${inputimage}" = "${image}" ]
 +then
 +    echo "... Copy ${inputimage} to ${outputimage}"
 +    cp "${inputimage}" "{$outputimage}"
 +else
 +    echo "... Decompress ${inputimage} to ${outputimage}"
 +    gzip -vkcd "${inputimage}" > "${outputimage}"
 +fi
 +echo "... Grow image ${outputimage}"
 +truncate -s "+${growsize}" "$outputimage"
 +echo "... Set up loopback device"
 +lodev=$(sudo losetup --find --show --partscan "${outputimage}")
 +echo "... Loopback device is: ${lodev}"
 +sharepart=2
 +sharepartdev="${lodev}p${sharepart}"
 +echo "... Adjust GPT on ${lodev}"
 +sudo sgdisk -e "${lodev}"
 +echo "... Show free space on ${sharepartdev}"
 +sudo dumpe2fs "${sharepartdev}" | grep '^Free blocks'
 +echo "... Resize SHARE partition ${sharepartdev}"
 +sudo parted -s "${lodev}" "resizepart ${sharepart} 100%"
 +echo "... Check ${sharepartdev}"
 +sudo fsck -f "${sharepartdev}"
 +echo "... Grow ${sharepartdev}"
 +sudo resize2fs "${sharepartdev}"
 +echo "... Show free space on ${sharepartdev}"
 +sudo dumpe2fs "${sharepartdev}" | grep '^Free blocks'
 +echo "... Detach loopback device ${lodev}"
 +sudo losetup -d "${lodev}"
 +echo "... Successfully completed"
 +</code>
 +
  
  • dual_boot_ubuntu_batocera.linux.1644629347.txt.gz
  • Last modified: 4 years ago
  • by atari