-
Notifications
You must be signed in to change notification settings - Fork 474
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
batocera-settings-(get/set) fails to read and write properly to /boot/config.txt #3349
Comments
@glebm you have any idea ? |
@rtissera it's fixed - caused by some byte order in config file |
can we close the issue then ? |
IMHO fixed for B31 take a look at PR3312 |
Right, fixed by #3312 |
@rtissera
|
@crcerror can you reopen ? |
but batocera-settings is not for /boot/config.txt, it is for /boot/batocera-boot.conf and batocera.conf or i am wrong ? |
https://wiki.batocera.org/usage_of_batocera-settings#handling_in_scripts My impression was that |
@rtissera It was decided to drop batocera-settings and use the 2 binaries instead. In theory both ways should still work even though batocera-settings used advanced error return codes. If there is a fix needed then @glebm should do that. @wholee Key=value every file can be opened and used with batocera-settings-get set. You can also copy the old script back and use the CLI. I removed the script usage in wiki because it is outdated EDIT |
@wholee is describing an issue that is unrelated to this one. I've filed glebm/mini_settings#1. It's fairly low priority because it is rare that you want to edit /boot/config.txt in that manner. If you're enabling UART debugging you probably know how to use |
Ah, nevermind, the original issue was unrelated to the UTF-8 BOM markers, this should be reopened (or we could say editing /boot/config.txt is not supported yet) |
Allows `batocera-settings-set` to be used with `/boot/config.txt`. Fixes batocera-linux#3349 batocera-linux/mini_settings@32d05a4
Fixed in #3781 |
Hi, RaspberryPi 4 2GB @glebm config.txt before:
after running
( also note the updated dtoverlay under Looking at the code I can see where this behavior is coming from. And that behavior is correct because if a user has multiple same key/value pairs it needs to change them all but that does not apply to boot/config.txt |
@wholee Yeah, I guess for that use case you're better off with |
Disables file validation by default for the `batocera-settings-get` command. This allows (limited) usage with /boot/config.txt. Refs batocera-linux#3349 batocera-linux/mini_settings@b9822f8
RaspberryPi 4 2GB
Batocera v.30
batocera-settings-set:
batocera-settings-set -f /boot/config.txt dtovelay disable-bt
returns
Invalid config file: key 'initramfs boot/initrd.gz' has no value on line 69#
batocera-settings-get:
batocera-settings-get -f /boot/config.txt kernel
returns proper value:
boot/linux
batocera-settings-get -f /boot/config.txt overscan_scale
returns nothing
Basically, if the
<key><value>
is after entryinitramfs boot/initrd.gz
in/boot/config.txt
it will not be readContent of
/boot/config.txt
:The text was updated successfully, but these errors were encountered: