User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Commented Config.txt

Wed Jun 27, 2012 8:31 pm

Hi everyone,

As looking through the eLinux wiki for the details of how to set options in 'config.txt' is not always convenient, I've put together a commented version of the file that should allow easy option editing.

The details have been transcribed from the current wiki entry, so big thanks to all who put together that information.

Before we start, a few disclaimers:
- There is no guarantee the wiki details I copied were correct
- There is no guarantee I have transcribed all details perfectly
- Description of overclocking and voltage settings are included, if you use these it is at your own risk

http://pastebin.com/HN9kMC8C

Everyone is free to use, edit and distribute this file however they want.

User avatar
Salamander
Posts: 49
Joined: Fri Mar 30, 2012 1:41 pm

Re: Commented Config.txt

Thu Jun 28, 2012 10:42 am

Great job!! Big thanks. Will be very useful (once I get my Pi, of course ;) )

RomeoPapacy
Posts: 2
Joined: Sat Jun 30, 2012 5:39 pm

Re: Commented Config.txt

Sun Jul 01, 2012 6:55 am

Thanks for the file. It's a massive help!

I think you may have an error on line 261 though. You have listed framebuffer_height under the description for framebuffer_depth. Hope this is of use.

Much thanks,

RomeoPapacy

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Tue Jul 03, 2012 9:15 am

Thanks for spotting that error RomeoPapacy, that one would be attributed to disclamer no.2 (errors I introduced :oops:).

Here is an updated copy of the config.txt:
http://pastebin.com/qEyu5dcR

User avatar
Mortimer
Posts: 801
Joined: Sun Jun 10, 2012 3:57 pm

Re: Commented Config.txt

Tue Jul 03, 2012 9:50 am

Very useful.

HDMI_Force_Hotplug is in there twice though. Lines 52 and 182.

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Tue Jul 03, 2012 10:05 am

Thanks Mortimer,

This one was due to repeated info on the wiki entry, here is another updated version...
http://pastebin.com/UDgz1RMm

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Tue Jul 03, 2012 11:58 pm

New version :
http://pastebin.com/0WL8Qaue

I've added the hdmi_ignore_edid option and a version tag to the top of the file.

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Thu Jul 19, 2012 11:26 am

Updated to revision 5:
http://pastebin.com/YHXjZJ71

- addition of sdtv_disable_colourburst
- update High Definition Video Settings header with information upon obtaining supported modes
- addition of hdmi_force_edid_audio
- addition of hdmi_ignore_cec
- update description of hdmi_force_hotplug
- addition of hdmi_ignore_hotplug
- update description of hdmi_group
- addition of ramfsaddr
- addition of initramfs
- update Overclocking Settings header with information on clock relationships
- update description of core_freq
- minor formatting changes to various sections

User avatar
piglet
Posts: 763
Joined: Sat Aug 27, 2011 1:16 pm

Re: Commented Config.txt

Thu Jul 19, 2012 11:30 am

Shouldn't this all be merged with the current content of the wiki? http://elinux.org/RPi_config.txt is there a reason not to edit it there?

User avatar
Mortimer
Posts: 801
Joined: Sun Jun 10, 2012 3:57 pm

Re: Commented Config.txt

Thu Jul 19, 2012 11:34 am

Thanks for the updates Evilbadger.

I put a copy of the commented file onto a new card with Raspbian last night, and I noticed one thing. I don't know if I am find the wrong link to use, but I couldn't work out which url to use in a WGET command to download the file directly to the /boot folder on the RPi.

I tried WGET using "http://pastebin.com/0WL8Qaue", and of course just got a whole bunch of HTML. So what url should I use with WGET?

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Thu Jul 19, 2012 11:39 am

The information is all taken from the wiki, the only difference is the formatting.

It's not always possible or convenient to have access to the wiki, so having the information contained within the config.txt as comments allows editing without having to guess/remember a lot of settings.



I've used pastebin as it was the most convenient option at the time I started creating the file. I'll transfer all the information to Git some time tonight, which should allow easier access via Wget.

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Thu Jul 19, 2012 11:41 am

The current pastebin raw file should be accessible from http://pastebin.com/raw.php?i=YHXjZJ71

That should allow grabbing with Wget.

User avatar
Mortimer
Posts: 801
Joined: Sun Jun 10, 2012 3:57 pm

Re: Commented Config.txt

Thu Jul 19, 2012 12:02 pm

OK I'll try that later. Thanks.

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 9471
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: Commented Config.txt

Thu Jul 19, 2012 12:07 pm

perhaps someone can comment on the meaning of "reduced blanking", I'm guessing that almost nobody understands what it does, I certainly do not.

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Thu Jul 19, 2012 12:21 pm

A quick search threw up this topic: http://arstechnica.com/civis/viewtopic.php?f=6&t=164574
The blanking is in the DVI signal, which has gaps between each scanline and each frame, just like an analog signal, during which it sends nothing but null bytes. 1920x1200 is pushing the limits of single-link DVI's bandwidth using normal (CRT-style) blanking, but if you use shorter blanking periods, there's less data to send, so you can use a lower data rate.
A more in-depth description can be found on here: http://www.playtool.com/pages/dvicompat/dvi.html

User avatar
Mortimer
Posts: 801
Joined: Sun Jun 10, 2012 3:57 pm

Re: Commented Config.txt

Thu Jul 19, 2012 12:27 pm

A CRT screen requires blanking time to allow time for the scanning beam to move from one side of the screen to the other to start drawing the next line, and to go from bottom to top to start the next screen, plus overscan and black borders. All this time when the beam is not drawing anything on the screen is "blanking time". An LCD monitor using DVI-D doesn't need blanking time, but it is included in the pixel stream anyway. This time can be reduced, which in turn means that for a given resolution at a particular frequency, the pixel clock frequency can be reduced. This reduces the power requirement on the sending end, in this case the RPi which could be useful, reduces error rates, and will likely increase the length of cable possible between the computer and the monitor.

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Thu Jul 19, 2012 8:27 pm

I've transferred the config.txt over to GitHub and recreated some of the history.
From now on you can find the latest version here:
https://github.com/Evilpaul/RPi-config

Wget users can grab the raw file from here (specify the option --no-check-certificate):
https://github.com/Evilpaul/RPi-config/ ... config.txt

User avatar
Mortimer
Posts: 801
Joined: Sun Jun 10, 2012 3:57 pm

Re: Commented Config.txt

Thu Jul 19, 2012 8:43 pm

Good news! And Thanks!

Patschi
Posts: 44
Joined: Thu Jun 07, 2012 1:04 am
Location: Austria
Contact: ICQ Website

Re: Commented Config.txt

Thu Jul 19, 2012 9:06 pm

Wow! Thank you very much! :)
My german homepage: http://pkern.at (Ofcourse Raspberry Pi articles too :D)

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 9471
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: Commented Config.txt

Thu Jul 19, 2012 11:48 pm

Mortimer wrote:A CRT screen requires blanking time to allow time for the scanning beam to move from one side of the screen to the other to start drawing the next line, and to go from bottom to top to start the next screen, plus overscan and black borders. All this time when the beam is not drawing anything on the screen is "blanking time". An LCD monitor using DVI-D doesn't need blanking time, but it is included in the pixel stream anyway. This time can be reduced, which in turn means that for a given resolution at a particular frequency, the pixel clock frequency can be reduced. This reduces the power requirement on the sending end, in this case the RPi which could be useful, reduces error rates, and will likely increase the length of cable possible between the computer and the monitor.
Ah, thanks, I knew about traditional blanking time in composite video systems (and VGA), didn't know that it was also used in HDMI, and therefore could be reduced.
I think the long blanking will only be needed for simple LVDS to shift-registers to D/A encoding "converter boxes" where the video signal is indeed turned back into a "legacy" analog signal.

I hope this tidbit of information will be included into the config.txt framework.

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Sat Jul 21, 2012 8:04 pm

New version available here:
https://github.com/Evilpaul/RPi-config


- add description of reduced blanking to hdmi_mode
- addition of avoid_safe_mode
- bump revision number


Raw file can be accessed here:
https://raw.github.com/Evilpaul/RPi-con ... config.txt

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 9471
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: Commented Config.txt

Sat Jul 21, 2012 8:42 pm

Just a stupid question, but am I correct in assuming that due to commenting out everything in this config.txt it in essence does the same as an empty config.txt file?

Do we have to remove the # before any entry to activate it?

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Sat Jul 21, 2012 8:49 pm

Correct, the raw file is essentially a just a commented file that would perform no actions.

True comments (e.g. section headers, descriptions) are preceded by double hashes '##', where as the actual option is preceded by a single hash '#'.
It is up to the user to edit the file to uncomment the options they wish to use and to edit the option value to match their desired configuration.

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 9471
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: Commented Config.txt

Sat Jul 21, 2012 8:51 pm

ah, just what I thought, but maybe not everybody will get this, so perhaps you should put it in the header of the file.

User avatar
Evilbadger
Posts: 29
Joined: Mon Jun 25, 2012 7:12 am
Location: No longer Coventry

Re: Commented Config.txt

Sat Jul 21, 2012 8:59 pm

I can see how those unfamiliar with configuration files may be at a loss when trying to edit the file. I'll knock up some basic instruction text to go at the top of the file.

Return to “Beginners”

Who is online

Users browsing this forum: KyluAce and 58 guests