Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update not possible - Not enough Space #92

Open
paparansen opened this issue Dec 21, 2023 · 9 comments
Open

Update not possible - Not enough Space #92

paparansen opened this issue Dec 21, 2023 · 9 comments
Assignees

Comments

@paparansen
Copy link

What happened?

Update to 1.0.2 is not possible, because there is not enough space
to copy the files from the ZIP to first Partition.
Tried with fresh & 1 time started 1.0 & 1.0.1
First Partition is 2.99GB, shouldnt this be 5.99GB ?

@acmeplus
Copy link

You have to delete the existing files before. Otherwise it does not have enough temporary space to write the new files.

@paparansen
Copy link
Author

ALL files?

@acmeplus
Copy link

Yeah, but technically you can just delete boot/batocera to free space and then copy the files over

@paparansen
Copy link
Author

thx, that worked... but now there is different & ugly boot logo ^^
also, shutdown from menu not working - it just reloads emulation station.
and no kodi :( any way to add kodi ?

@benni092
Copy link

Jeah had the same issue. I dont know what file contains the bootscreen, but just copy all other files from a previous release.

@acmeplus
Copy link

I was tired of the original logo. The logo is boot_logo.bmp.gz I believe. You can download the boot.tar.xz from v1.0.1 and copy that logo over

@paparansen
Copy link
Author

found a some other bugs/issues.
should i open 1 thread for all, or 1 thread for each ?

@acmeplus
Copy link

found a some other bugs/issues. should i open 1 thread for all, or 1 thread for each ?

Add those here first

@paparansen
Copy link
Author

paparansen commented Dec 21, 2023

-- shutdown from menu not working - it just reloads emulation station
-- volume at max after power on - previous setting not recognized i guess
-- brightness at max after power on - previous setting not recognized i guess
-- when using hotkey & vol for brightness - volume changes too
-- after slepp/wakeup - controller mapping comes up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants