From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Xorg segfaults, but GDM welcome screen loads
Date: Tue, 8 Feb 2011 22:02:06 +0000 [thread overview]
Message-ID: <201102082202.17675.michaelkintzios@gmail.com> (raw)
In-Reply-To: <AANLkTi=6xfnexnL32KOqVz0t6bVQ-RDHDYbu0NJsttEg@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 988 bytes --]
On Tuesday 08 February 2011 16:38:34 Grant wrote:
> >> I only mention it because in my experience I always have weird shit
> >> happening when I upgrade xorg-server over a big version number change.
> >>
> >> And rebuilding everything that underpins xorg always fixes it. Including
> >> drivers and mesa.
> >>
> >> In the old days when xorg was monolithic this never happened, as all the
> >> drivers always got rebuilt anyway. Nowadays with xorg sources being
> >> modular, we have to be a little more alert.
> >
> > ... and if you have just upgraded to xorg-server-1.9 you'll (probably)
> > need an xorg.conf file. The old .fdi files are no longer being used.
> > --
> > Regards,
> > Mick
>
> My laptop is on xorg-server-1.9.2 and it doesn't use an xorg.conf. In
> what type of situation is it needed?
When you want to configure different languages on the keyboard, synaptics,
etc, and when evdev doesn't work nicely with your set up.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-08 22:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 22:26 [gentoo-user] Xorg segfaults, but GDM welcome screen loads Grant
2011-02-04 22:38 ` Alan McKinnon
2011-02-05 0:54 ` Grant
2011-02-05 20:10 ` Alan McKinnon
2011-02-07 23:05 ` Mick
2011-02-08 16:38 ` Grant
2011-02-08 22:02 ` Mick [this message]
2011-02-05 22:15 ` [gentoo-user] " walt
2011-02-06 0:14 ` Grant
2011-02-05 11:44 ` [gentoo-user] " Florian Philipp
2011-02-05 16:57 ` Grant
2011-02-05 16:59 ` Grant
2011-02-05 17:39 ` Florian Philipp
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=201102082202.17675.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.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