From: Johannes Skov Frandsen <joe@omesc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems starting X
Date: Wed, 09 May 2007 11:22:39 +0200 [thread overview]
Message-ID: <464192DF.8070601@omesc.com> (raw)
In-Reply-To: <2fcf3fa50705081203u34aa21cx2fdfd0fd3e81acb@mail.gmail.com>
Francisco Rivas wrote:
> Excuse me please, only few things..
> On 5/8/07, Francisco Rivas <taken2k4@gmail.com> wrote:
>>
>> Hi, a few months ago I had the same problem [too], then :
>>
>> emerge xf86-input-mouse
>> xf86-video-fbdev
>> xf86-video-vga [1]
>> xf86-video-vesa [1]
>> xf86-input-keyboard
>>
>> Note: [1] Only if you want, because when you install the ati driver you
>> don't need neather of them.
>>
>> By other side and very important (my recomendation), download ati
>> 8.36driver and install it, reconfigure your
>> xorg.conf doing this
>> aticonfig --initial. It's a good idea you do a backup of your xorg.conf.
>
>
> and after aticonfig --initial, and items before do startx.. and
> $ glxinfo | grep direct [if you have a 3d accel the system response]
>
> direct rendering: Yes
> Or
>
> $glxgears :D
>
> Please excuses for my english and regards :D
>
Hi Francisco
I tried:
emerge -va emerge -av ati-drivers
but got this error:
!!! ERROR: x11-drivers/ati-drivers-8.32.5 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 4097: Called src_compile
ati-drivers-8.32.5.ebuild, line 157: Called linux-mod_src_compile
linux-mod.eclass, line 516: Called die
!!! Unable to make GCC_VER_MAJ=4 KVER=2.6.20-gentoo-r7
KDIR=/usr/src/linux kmod_build.
!!! If you need support, post the topmost build error, and the call
stack if relevant.
!!! A complete build log is located at
'/var/tmp/portage/x11-drivers/ati-drivers-8.32.5/temp/build.log'.
Any hint on what could be the problem?
Johannes Skov Frandsen
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-09 9:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 22:47 [gentoo-user] cdrtools incomplete? Kevin O'Gorman
2007-05-07 1:07 ` Philip Webb
2007-05-07 1:18 ` Kevin O'Gorman
2007-05-07 5:02 ` Leonhard Gruener
2007-05-07 5:59 ` Dirk Heinrichs
2007-05-08 13:41 ` [gentoo-user] " Alexander Skwar
2007-05-08 18:42 ` [gentoo-user] Problems starting X Johannes Skov Frandsen
2007-05-08 18:59 ` Francisco Rivas
2007-05-08 19:03 ` Francisco Rivas
2007-05-09 9:22 ` Johannes Skov Frandsen [this message]
2007-05-09 12:41 ` Francisco Rivas
2007-05-10 8:45 ` Johannes Skov Frandsen
2007-05-10 11:07 ` Aleksandar L. Dimitrov
2007-05-10 10:24 ` Johannes Skov Frandsen
2007-05-10 10:45 ` Aleksandar L. Dimitrov
2007-05-10 13:35 ` Francisco Rivas
2007-05-11 21:24 ` Johannes Skov Frandsen
2007-05-11 22:42 ` JD
2007-05-12 5:41 ` Francisco Rivas
2007-05-12 12:31 ` Johannes Skov Frandsen
2007-05-12 15:34 ` Francisco Rivas
2007-05-12 19:25 ` Aleksandar L. Dimitrov
2007-05-15 16:18 ` Johannes Skov Frandsen
2007-05-15 18:18 ` Francisco Rivas
2007-05-15 19:54 ` Dan Farrell
2007-05-12 15:56 ` Guillermo A. Amaral
2007-05-10 13:44 ` young sun
2007-05-08 21:22 ` Dale
[not found] ` <46411BE5.90009@paradise.net.nz>
2007-05-09 4:14 ` Dmitry
2007-05-09 0:04 ` [gentoo-user] Re: cdrtools incomplete? Boyd Stephen Smith Jr.
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=464192DF.8070601@omesc.com \
--to=joe@omesc.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