Update not working just blank screen after reboot.

g12345567

Running Batocera v33 Standard Desktop/Laptop (64 Bits) from the internal HDD on a laptop and was working fine. Decided to do an online update from within Batocera to new v34.

Update downloaded and installed but got stuck on “remounting the boot partition in rewritable mode” waited about half an hour then decided to reboot. Problem is that Batocera v34 will not boot. Just gives a blank screen and won’t display anything.

Any ideas on what I need to do to get Batocera v34 working again? Don’t feel like having to reinstall along with all the roms.

Laptop uses the Graphics adapter: Intel Graphics Media Accelerator (GMA) HD and standard attached 16:9, 1366 × 768 LCD. Though I’ve always update this way and never encountered this problem until the latest update to v34.

Atari

Warnings are present here: https://wiki.batocera.org/install_batocera#install_batocera_from_batocera Please do not ignore them.

Anyway, let’s assume you absolutely must use the internal storage to not get caught up on that.

You can copy your data from the userdata partition onto something such as a spare USB, and then try reflashing Batocera. In the case that you have no other operating system to do this from, you can temporarily flash Batocera onto a USB and then use its file manager to copy the data from your old installation’s userdata partition onto the USB.

g12345567

Atari looks like I fixed the problem. I’m using the internal HDD (500gb) as it offers plenty of storage for ROMs and boots faster. Laptop for some reason has trouble booting Batocera from USB (blank screen) but works perfectly when installed and run from the internal HDD.

Not sure what happened to cause the upgrade from v33 to v34 to not not mount and hence cause blank screen when booting. I suspect a diplay bug that was also reported and fixed in other builds such as Recalbox.

As I went ahead, downloaded the latest develeopement build “batocera-x86_64-35-20220620.img”. Deleted all the existing partitions on the HDD and installed that to the internal hdd. rebooted and it worked fine.. I suspect whatever display bug was introduced in the official v34 build has been fixed in later releases.