Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Sep 2015 01:35:08 +0200
From:      Polytropon <freebsd@edvax.de>
To:        doug@safeport.com
Cc:        Warren Block <wblock@wonkity.com>, freebsd-questions@freebsd.org
Subject:   Re: generating xorg.conf does not work
Message-ID:  <20150901013508.39c7f458.freebsd@edvax.de>
In-Reply-To: <alpine.BSF.2.00.1508311807570.72286@bucksport.safeport.com>
References:  <alpine.BSF.2.00.1508280029090.72286@bucksport.safeport.com> <55E0A5E5.1040803@gmx.de> <alpine.BSF.2.00.1508281432180.72286@bucksport.safeport.com> <alpine.BSF.2.20.1508281631580.74312@wonkity.com> <alpine.BSF.2.00.1508311807570.72286@bucksport.safeport.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Aug 2015 18:24:46 -0400 (EDT), doug@safeport.com wrote:
> On Fri, 28 Aug 2015, Warren Block wrote:
> 
> > On Fri, 28 Aug 2015, doug@safeport.com wrote:
> >> 
> >> Maybe I should have taken the questions one at a time. My highest priority 
> >> question is that the handbook is in error on how to generate xorg.conf.
> >> startx is just not correct.
> >
> > I don't understand what you are saying there.
> 
> This part got cut from my first post. The handbook says:
> 
>      To generate the configuration file and start the X system, issue
>      this command:
> 
>      % startx
> 
> This is clearly wrong.

In some way, yes. X will generate configuration data dynamically
(auto-detect), but will not write an xorg.conf file to be used
later on. "X -configure" will do that.



> 5.4 also says autoconfiguration is the preferred method. 

Works for most things.



> I found a post to forums.freebsd.org on 8/4/15 from wblock@ saying: 
> "Auto-generating xorg.conf is not recommended any more."

Only for the few things where auto-detection magic does not work,
or where you intendedly want to "hard wire" things and summarize
X settings in a central location. To do this, the auto-generated
file is a good starting point, but in many cases, can be stripped
off of many lines.



> > Otherwise, try this for xorg.conf.  Do not add this to an existing file, this 
> > is the *entire* file:
> >
> > Section "Device"
> > 	Identifier  "Card0"
> > 	Driver      "radeon"
> > EndSection
> 
> I assume I can then also add the font commands as needed.

Yes. It should work the same for keyboard language definitions.



> I could find no 
> documentation in the FreeBSD wiki or on Xorg that indicated X would just piece 
> all this together. I assume this would now go in /usr/local/etc/X11.

That's a valid location, but X will also use /etc/X11/xorg.conf
(even with partial content) if it is present. In fact, there are
other locations; you can find them in "man 5 xorg.conf".


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150901013508.39c7f458.freebsd>