From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't boot into X
Date: Thu, 17 Jun 2010 18:39:50 +0200 [thread overview]
Message-ID: <AANLkTikGaYSe_CxkYPBLDebDR5peWwCmxfw3I8CTirgz@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimwf7VOv7gX5o2EBB7FX2Zft0xaJpu_Eunb9q1D@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
The dri messages are normal for nvidia.
Run revdep-rebuild to fix the png issue.
On 17 Jun 2010 5:59 PM, "Colleen Beamer" <colleen.beamer@gmail.com> wrote:
First, I looked in the archives and didn't find anything relevant - could be
my stupidity, but I did try!
About 6 days ago, I updated my system and since then, I can't boot into X.
My nvidia driver loads okay and it looks like it is going to start X, but
then reverts to the command line. I've been sick and haven't really been
able to follow this up.
Also note that I can't provide any output because I am, obviously, not on my
computer. Details are as follows:
From my kdm log the last few lines are as follows:
(EE) Failed to load module "dri" (module does not exist, 0)
(EE) Failed to load module "dri2" (module does not exist, 0)
/usr/lib/kde4/libexec/kdm_greet: error while loading shared libraries:
libpng12.so.0: cannot open shared object file: No such file or directory
I don't have a dri USE flag in my make.conf file
The dri line in my xorg.conf file exists, but it is commented
I do not build dri into my kernel
Yesterday, I decided to try another update to see if there was an ebuild
that might have corrected whatever the problem was
On attempting to upgrade gtk+, it fails and I get told to run:
emerge --info =x11-libs/gtk+-2.18.9
When I do that, there is a USE line which includes dri and I'm not sure
where that is being pulled from unless it is global because as stated
previously, I don't have a dri USE flag in my make.conf or an active line in
my xorg.conf file.
Regarding libpng - on my first upgrade 6 days ago, I removed libpng prior to
doing the update because the updated libpng file was being blocked by the
existing one. I don't know if this makes a difference.
Any advice on how to fix this?
Regards,
Colleen
[-- Attachment #2: Type: text/html, Size: 2165 bytes --]
next prev parent reply other threads:[~2010-06-17 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 15:58 [gentoo-user] Can't boot into X Colleen Beamer
[not found] ` <AANLkTimwf7VOv7gX5o2EBB7FX2Zft0xaJpu_Eunb9q1D@mail.gmail.com>
2010-06-17 16:39 ` Alan McKinnon [this message]
2010-06-17 16:54 ` Alex Schuster
2010-06-17 19:23 ` Mick
2010-06-18 18:34 ` Colleen Beamer
2010-06-18 19:21 ` Alex Schuster
2010-06-18 22:33 ` CJoeB
2010-06-17 18:56 ` [gentoo-user] " James
2010-06-17 19:13 ` Dale
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=AANLkTikGaYSe_CxkYPBLDebDR5peWwCmxfw3I8CTirgz@mail.gmail.com \
--to=alan.mckinnon@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