From: Andrew Long <jandrewlong@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Lost ability to log in graphically
Date: Tue, 9 Feb 2010 10:27:05 -0500 [thread overview]
Message-ID: <76fa89841002090727sdc40b16pd72f2d150696e1ff@mail.gmail.com> (raw)
In-Reply-To: <20100209151759.GB835270@sgi.com>
On Tue, Feb 9, 2010 at 10:17 AM, Bob Sanders <rsanders@sgi.com> wrote:
> Jim Seymour, mused, then expounded:
>>
>> that is completely up to date package wise. The hardware does not seem to be the issue as a gentoo live dvd works perfectly. Any ideas on how I can get this working again? The only worthwhile errors I can find is in the xdm.log are below. This is with a clean xdm.log, reboot, login attempt and then killing X with ctrl_alt_bkspc.
>>
>
> Sometimes it takes just rebuilding the device drivers, which can be
> found by the gine in the xorg-server ebuild -
>
> emerge portage-utils; qlist -I -C x11-drivers/
>
> Take that output and emerge the drivers.
>
> Bob
I second this suggestion.
There was an update to xorg a few months ago that required a rebuild
of the drivers, but did not force it. What happened when I did that
upgrade was that I would get the graphical login screen, but the mouse
and keyboard did not work. Rebuilding the drivers fixed it for me.
Andrew
next prev parent reply other threads:[~2010-02-09 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 14:46 [gentoo-amd64] Lost ability to log in graphically Jim Seymour
2010-02-09 15:15 ` Mark Knecht
2010-02-09 15:17 ` Bob Sanders
2010-02-09 15:27 ` Andrew Long [this message]
2010-02-09 16:10 ` [gentoo-amd64] " Duncan
2010-02-09 16:23 ` [gentoo-amd64] " Mark Knecht
2010-02-09 22:01 ` Volker Armin Hemmann
-- strict thread matches above, loose matches on Subject: below --
2010-02-09 17:42 Jim Seymour
2010-02-09 18:26 ` Dieter Ries
2010-02-11 1:46 Jim Seymour
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=76fa89841002090727sdc40b16pd72f2d150696e1ff@mail.gmail.com \
--to=jandrewlong@gmail.com \
--cc=gentoo-amd64@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