Everything says "edit config.txt" but nowhere does it say where this file exists on the system. Nowhere. I mean I went to like 10 web pages and they all say "edit config.txt" and you know what? When I log in via SSH there is no config.txt. Where is it?

Where is config.txt
- jglazer63
- Thread is Unresolved
-
-
Everything says "edit config.txt" but nowhere does it say where this file exists on the system. Nowhere. I mean I went to like 10 web pages and they all say "edit config.txt" and you know what? When I log in via SSH there is no config.txt. Where is it?Are you using a pi? It wil be /flash/config.txt
By default /flash is mounted read-only so you need to:
before you can edit it.
-
Thanks for explaining this. I got it
-
-
I actually saw that page but it didn't describe things well enough. I believe you should explain (as popcornmix does) that the file "resides in /flash but is read-only" and then proceed with directions on how to mount it r/w, edit it, then remount as read only.
If you use "The config.txt file is located in /flash" somewhere in the wiki, then people will find the page when they look for "location of config.txt file" or something along those line.
Just an idea
thanks for the hard work!!
-
I actually saw that page but it didn't describe things well enough.What? The first paragraph gives you a step by step explanation on how to edit the config.txt, and this isn't well enough for you?
-
Some people want the 'why' as well as the 'how'.
-
Except he specified he wanted specific instructions on 'how', which is already there. Unless the wiki was edited after this post, I can't see how it could be any better.
-
If you can't figure out that remounting flash as read/write and running "nano /flash/config.txt"
means you're dealing with a file in flash then the second option - take it out and stick it in a pc to edit - is still there. The page is fine. -
I actually saw that page but it didn't describe things well enough. I believe you should explain (as popcornmix does) that the file "resides in /flash but is read-only" and then proceed with directions on how to mount it r/w, edit it, then remount as read only.If you use "The config.txt file is located in /flash" somewhere in the wiki, then people will find the page when they look for "location of config.txt file" or something along those line.
Just an idea
thanks for the hard work!!
Well....we have a main wiki page: LibreELEC
At this page, you will see a "RaspberryPi Section" which links to: Raspberry Pi - LibreELEC
At this section, there is table of content on the top right where "config.txt" is mentioned....
So, tbh, I don't know how much clearer it could be
Quote
I believe you should explain (as popcornmix does) that the file "resides in /flash but is read-onlyFrom our wiki for the "why":
Quote
As LibreELEC is generally a read-only system and you don't have write permissions to the system partition, you need to get those permissions firstand then:
Quote
Now you have to change the permissions again:So I guess it's explained very well
. If one has something to improve, feel free
[hr]
Last change for the wiki at 22.6.2016 by me ;): Revision history of "Config.txt" - LibreELEC -
When I (frequently) type "libreelec config" into GoOgle this link pops up first Config.txt - LibreELEC, I do that evertime I need to adjust something.
-
I have installed LibreElec in Pine64 RockPro64 board.
The wiki ( Raspberry Pi Config.txt [LibreELEC.wiki] ) is clear but in /flash I can't find config.txt:
CodeI have read the title
and I think layout for Raspberry differs from RockPro board.
I'm missing something?
I'd like to solve this problem but I can't figure out where those options are stored for Rockchip.
Thank you,
Riccardo
-
have installed LibreElec in Pine64 RockPro64 board.
The wiki ( Raspberry Pi Config.txt [LibreELEC.wiki] ) is clear but in /flash I can't find config.txt:
the config.txt is just for the RPi, nothing else supports it
-
/flash/extlinux/extlinux.conf is not an equivalent to config.txt (RPi config commands won't work) but if you follow the instructions for Intel GPUs here Custom EDID [LibreELEC.wiki] the same process for forcing a specific edid.bin file (so the kernel drm framework always thinks an HDMI device is connected and powered) should work - Allwinner boards are also using the same kernel drm framework.
-
I'll try!
Thank you,
Riccardo
ps. the problem is solved: I got a kernel panic, but on Hdmi!