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
Next revisionBoth sides next revision
upgrade_manually [2020/10/31 14:22] – [Error messages when upgrading] joinskiupgrade_manually [2021/09/10 07:35] – spelling and grammar, rewrite of workaround instructions atari
Line 1: Line 1:
-~~NOTOC~~ +====== Manual upgrades/downgrades ======
-===== Manual upgrades/downgrades ===== +
-Upgrades/Downgrades can be done manually : +
-  * in case you want to reinstall a previous version +
-  * in case the upgrades are broken +
-  * in case you want to upgrade to a custom version+
  
-To upgrade/downgrade manually : +This is for if you: 
-  - download the file boot.tar.xz of the version you want. The official ones are available here : http://batocera.org/upgrades +  * can'upgrade/downgrade from stable to beta or vice versa using **MAIN MENU** > **UPDATES & DOWNLOADS** > **UPDATE TYPE** > "Stable" or "Beta" and updating, 
-  ''.tar.xz'' file is an archive formatlike a ''.zip''. Just unzip this file onto your SD card/USB key to replace existing files.+  want to downgrade to an older revision, 
 +  * want to install custom version of Batocera,
  
-Or, starting with batocera.linux 5.23+To upgrade/downgrade manually
-  - [[access_the_batocera_via_ssh|from SSH]], adapt the url to the right architecture and run : ''batocera-upgrade https://batocera.org/upgrades/x86_64/stable/last'' (this example is for PC x86_64, please adapt the URL to the right architecture)+  - Download the ''boot.tar.xz'' file of the version you want. The official ones are available at http://batocera.org/upgrades (for older versions use https://mirrors.o2switch.fr/batocera/, navigate to your architecture and go to /stable/last/archives/). 
 +  - Unzip the ''.tar.xz'' file (it's just like a ''.zip'', you can use 7-zip on Windows) onto your SD card/USB key's [[edit_boot_partition|boot partition]] (This partition is readable on Windows regardless of the filesystem you have chosen for the SHARE. You may have to assign a drive letter under Windows Disk Management to see it in the file explorerto replace existing files.
  
-For batocera.linux 5.7 to 5.22: +Alternatively (from Batocera 5.**23** onwards) you can do this [[access_the_batocera_via_ssh|from SSH]]. Get the URL to the right architecture's ''last'' folder and run: ''%%batocera-upgrade [URL]%%''For example, if you were on the x86_64 platform: ''%%batocera-upgrade https://batocera.org/upgrades/x86_64/stable/last%%''. You should then see output similar to this:
-  - [[access_the_batocera_via_ssh|from SSH]]the command line would be: ''/recalbox/scripts/recalbox-upgrade.sh https://batocera.org/upgrades/x86_64/stable/last'' (for PC x86_64, please adapt to the right architecture)+
  
-These commands upgrade -- or potentially downgrade -- the Batocera systemUpgrading or downgrading //doesn't remove// any of your user data (ROMs, metadata...)Like never, ever.+<code> 
 +Starting the upgrade... 
 +url: https://updates.batocera.org/x86_64/stable/last/boot.tar.xz 
 +need to download 1876mb 
 +m/upgrade/boot.tar.xz     0%[                              ]   9.55M  1.82MB/   eta 19m 42s 
 +</code>
  
-==== Error messages when upgrading ====+For Batocera 5.**7** to 5.**22**, the command would be: ''%%/recalbox/scripts/recalbox-upgrade.sh https://batocera.org/upgrades/x86_64/stable/last%%'' (for PC x86_64, please adapt to the right architecture)
  
-If you get an error message telling you that you don'have enough space on your Batocera system partition when you upgradethere might be several explanations+These commands download the compressed upgrade (or potentially downgrade) file and expands it to overwrite the Batocera system. Upgrading or downgrading like this //doesn'remove// any of your user data (ROMs, saves, metadata...). Like neverever.
  
-One of them is that you have [[splash_boot|stored several splash boot video files]] on the ''/boot'' partition. Remove them, and try to upgrade again. +===== Error messages when upgrading =====
  
-The other explanation: Your first installation was an older version, where the boot-partition was smaller (in newer versions of batocera the space had to be rised because of more features). +If you get an error message telling you that you don't have enough space on your Batocera system partition while attempting to upgrade, there might be several reasons: 
-In this case, you could either delete the "batocera"-file (it is just called batocera, without a file-extension, is about 1gb big and is located in the boot folder of the first/boot partition). +  - Your drive is less than 8GB totalBatocera can //run// on these drives but you will be missing out on using the built-in updater. 
-After thatextract the boot.tar.xz file onto that drive and if successfull, rename the file "batocera-update" located in the boot folder to just "batocera")+  - The [[splash_boot|splash video file(s)]] (which are copied to the ''/boot'' partition) are/is taking up too much spaceRemove them/itreboot and try to upgrade again
-But be awarethat you would have to do this manual workaround (update-procedureevery time, you want to update to a new version.+  - Your first installation was an older version of Batocerawhere the ''/boot'' partition was initially assigned less space (compared to installations of newer Batocera versions).
  
-So it may be betterto backup all the files from your share-partition (romssaves, bios, etc.) and start a fresh new install, by flashing the .img.gz file with for example balenaEtcher onto the drive, where you want to have batocera installed, then boot from it and copy back all romssaves etc. to the share-partition of this new installation of batocera+To work around thisyou can any one of the following: 
-==== The batocera.linux usb key ==== +  * Insert your drive into another computer, back up the contents of the FAT32 boot partition of the drive (Windows should only be able to see this partition and nothing else by default)delete the ''/boot/batocera'' file (it is just called ''batocera'' without a file-extension and is about 2 GB large (smaller in older versions)) and extract the ''boot.tar.xz'' file to the root of that partition. Rename the freshly extracted ''/boot/batocera'' file to ''batocera-update'', then boot Batocera. Be aware that by doing this you would have to do this manual workaround every time. 
-{{system:usbkey.png?700|}}+  * Boot into Batocera, [[:access_the_batocera_via_ssh|SSH]] in or use the file manager's xterm and run ''mount -o remount,rw /boot''Backup your ''/boot/boot/batocera'' file to another device (''cp /boot/boot/batocera /userdata/system/batocera-backup'', or you can exit the xterm with Alt+F4 and then use the file manager to copy the file to your ''/userdata/system'' folder). Then run the following command to delete the ''batocera'' file and immediately upgrade:<code>rm /boot/boot/batocera && batocera-upgrade</code>You should get an output that looks like this:<code>Starting the upgrade... 
 +url: https://updates.batocera.org/x86_64/beta/last/boot.tar.xz 
 +need to download 1876mb 
 +m/upgrade/boot.tar.xz     0%[                              ]   9.55M  1.82MB/   eta 19m 42s</code>Be aware that by doing this you would have to do this manual workaround every time. 
 +  * Flash a spare USB/portable hard-drive with a new copy of Batocera and boot into that, copy all your ''/userdata'' (everything in Share) from your old Batocera drive to your spare USB/portable hard-drive and then reflash the old Batocera drive with a new version of Batocera (or just continue to use your spare USB/portable hard-drive). 
 +  * Backup your ''/userdata'' to another device (you may lose file attributes by doing this, causing problems with WINE/Cemu) and reflash Batocera. 
 + 
 +===== The Batocera USB key ===== 
 + 
 +{{system:usbkey.png?700|An illustration showing how the batocera system is laid out on a USB stick: the BATOCERA partition first, containing all the programs, and then the SHARE, containing all the userdata}}
  • upgrade_manually.txt
  • Last modified: 4 months ago
  • by maximumentropy