From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: x11-base/xorg-server-1.5.3-r5 with x11-drivers/ati-drivers-8.552-r2 -- file conflict
Date: Sat, 23 May 2009 20:49:15 -0400 [thread overview]
Message-ID: <20090523204915.71d5425e@osage.osagesoftware.com> (raw)
In-Reply-To: <gv9stt$58u$1@ger.gmane.org>
On Sun, 24 May 2009 01:22:06 +0300
Nikos Chantziaras wrote:
...[snip]...
> > ### Begin xorg.conf ###
> >
> > Section "ServerFlags"
> > Option "AllowEmptyInput" "false"
> > EndSection
> >
> > Section "Files"
> > FontPath "/usr/share/fonts/util"
> > FontPath "/usr/share/fonts/encodings"
> > FontPath "/usr/share/fonts/misc"
> > FontPath "/usr/share/fonts/corefonts"
> > FontPath "/usr/local/share/fonts"
> > FontPath "/usr/share/fonts/default"
> > FontPath "/usr/share/fonts/Type1"
> > FontPath "/usr/share/fonts/100dpi"
> > FontPath "/usr/share/fonts/75dpi"
> > EndSection
> >
> > ### End xorg.conf ###
>
> This xorg.conf won't load ati-drivers at all. If it works, it is
> probably running with another driver (radeon or vesa perhaps). You
> need to run "aticonfig --initial" as root first.
Really? My understanding had been that xorg-server-1.5.3 uses evdev and
runs happily without an xorg.conf file. Without an xorg.conf I had
keyboard and font problems -- cured by the above configuration.
As an experiment, I ran the suggested command ( "aticonfig
--initial" ). This added a lot to xorg.con and I then restarted X.
My screen resolution dropped from 1280x1024 to 640x480 and the screen
looked awful.
I've returned to the short config shown above.
To be honest, I don't know which display driver is in use and don't
much care since the display is working fine AFAICT.
David
next prev parent reply other threads:[~2009-05-24 0:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 0:46 [gentoo-user] x11-base/xorg-server-1.5.3-r5 with x11-drivers/ati-drivers-8.552-r2 -- file conflict Kevin O'Gorman
2009-05-22 1:06 ` Volker Armin Hemmann
2009-05-22 1:17 ` Alex Schuster
2009-05-22 1:34 ` Volker Armin Hemmann
2009-05-22 3:20 ` Kevin O'Gorman
2009-05-22 3:35 ` Kevin O'Gorman
2009-05-22 9:40 ` Alex Schuster
2009-05-22 13:35 ` Kevin O'Gorman
2009-05-23 21:57 ` Kevin O'Gorman
2009-05-23 22:12 ` David Relson
2009-05-23 22:22 ` [gentoo-user] " Nikos Chantziaras
2009-05-23 22:23 ` Mark Knecht
2009-05-23 23:35 ` Kevin O'Gorman
2009-05-23 23:39 ` Nikos Chantziaras
2009-05-24 4:27 ` William Kenworthy
2009-05-24 5:17 ` Kevin O'Gorman
2009-05-24 5:30 ` Nikos Chantziaras
2009-05-24 15:38 ` Kevin O'Gorman
2009-05-24 15:45 ` David Relson
2009-05-25 4:59 ` Nikos Chantziaras
2009-05-25 5:07 ` Nikos Chantziaras
2009-05-25 6:36 ` Adam Carter
2009-05-25 18:27 ` Kevin O'Gorman
2009-05-25 19:18 ` Nikos Chantziaras
2009-05-26 0:42 ` Kevin O'Gorman
2009-05-26 2:00 ` Adam Carter
2009-05-26 3:35 ` Kevin O'Gorman
2009-05-26 4:02 ` Adam Carter
2009-05-27 4:03 ` Kevin O'Gorman
2009-05-28 4:42 ` Kevin O'Gorman
2009-05-28 5:07 ` Adam Carter
2009-05-28 5:26 ` Adam Carter
2009-05-29 13:24 ` Kevin O'Gorman
2009-05-26 9:50 ` Nikos Chantziaras
2009-05-27 3:56 ` Kevin O'Gorman
2009-05-25 21:23 ` Mick
2009-05-26 0:29 ` Kevin O'Gorman
2009-05-24 0:49 ` David Relson [this message]
2009-05-24 0:56 ` Nikos Chantziaras
2009-05-24 1:00 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090523204915.71d5425e@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox