From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Radeon trouble
Date: Fri, 1 Jun 2007 21:09:34 +0200 [thread overview]
Message-ID: <200706012109.34978.wonko@wonkology.org> (raw)
Hi there!
I have a new video card (and a new motherboard + CPU, but I got that to work
already), and once again I am having trouble configuring X.
It is a ATI Radeon 9250 (128 MB-AGP, 200/240 MHz). I added fglrx and radeon
to my VIDEO_CARDS in /etc/make.conf, now it is VIDEO_CARDS="fglrx radeon
nvidia nv vesa vga fbdev". X was updated with "emerge -uN xorg-x11". I
usually configure with X -configure, but here it gives me this:
weird ~ # X -configure :1
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/weird:1
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: Linux 2.6.20-gentoo-r7 i686
Current Operating System: Linux weird 2.6.20-gentoo-r7 #6 PREEMPT Fri Jun 1
05:21:29 CEST 2007 i686
Build Date: 01 June 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Fri Jun 1 20:23:38 2007
List of video drivers:
ati
atimisc
radeon
nv
nvidia
r128
fglrx
fbdev
vesa
vga
Backtrace:
0: X(xf86SigHandler+0xa9) [0x80af86f]
1: X(DoConfigure+0x199) [0x80a367b]
2: X(InitOutput+0x186) [0x80967b0]
3: X(main+0x305) [0x806e405]
4: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7d8f83c]
5: X(FontFileCompleteXLFD+0xa1) [0x806d9c1]
Fatal server error:
Caught signal 11. Server aborting
I used the :1 argument because I have X running at the moment, but I also
tried without X up, so this should not be the problem. The full log file is
available here: http://wonkology.org/~wonko/tmp/Xorg.1.log
I also tried xorgconfig, but I get this message:
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(EE) No devices detected.
Fatal server error:
no screens found
Log file: http://wonkology.org/~wonko/tmp/Xorg.2.log
xorg.conf: http://wonkology.org/~wonko/tmp/xorg.conf.xorgconfig
I got X running by keeping my last xorg.conf and exchanging "nvidia"
with "radeon". But I want 3d acceleration, and I guess I need the "fglrx"
driver instead, but with that I get this error:
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
Log file: http://wonkology.org/~wonko/tmp/Xorg.3.log
xorg.conf: http://wonkology.org/~wonko/tmp/xorg.conf.fglrx
What could I do? Via google I do not find threads about such problems.
Alex
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-06-01 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 19:09 Alex Schuster [this message]
2007-06-01 19:38 ` [gentoo-user] Radeon trouble Mick
2007-06-03 18:48 ` Dimitar Toshev
2007-06-26 0:06 ` X -configure trouble (was: Re: [gentoo-user] Radeon trouble) Alex Schuster
2007-06-26 7:10 ` [gentoo-user] Re: X -configure trouble (was: trouble) Xavier Parizet
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=200706012109.34978.wonko@wonkology.org \
--to=wonko@wonkology.org \
--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