From: Alex Fansky <garen@tut.by>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trouble with X.org and ati opensource drivers
Date: Sun, 4 Mar 2007 00:10:55 +0200 [thread overview]
Message-ID: <200703040011.13077.garen@tut.by> (raw)
In-Reply-To: <45E9C018.1080101@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2438 bytes --]
В сообщении от Saturday 03 March 2007 20:36:08 b.n. написал(а):
> I have almost your hardware configuration (ati radeon9200se, amd duron
> 1800), however I'm running stable (xorg 7.1, kde 3.5.5), and I have no
> problems whatsoever (I'm even smoothly running aiglx+Beryl).
>
> Have you checked the xorg logs/the system messages for strange things?
> Did the problem occur when you switched to xorg 7.2? X use flags?
>
> Do you have composite enabled but no aiglx/compiz/beryl? I remember
> similar behaviour when I tried to use composite before the aiglx days.
>
> Is direct rendering working?
>
> Eventually use pastebin to post your xorg.conf, so that we can have a look.
>
> m.
Well, I used aiglx+Beryl and everything worked fine on xorg 7.2. But after
kernel upgrade I got this problem(I didn't forget to reemerge x11-drm).
Yes, direct rendering is working. Composite and aiglx are enabled too, I tried
to disable them, but it gave no result. I even tried to disable direct
rendering(dri,drm,glx modules in xorg.conf) but also without result.
Here is my xorg.conf and Xorg.0.log
http://pastebin.com/892943
lsmod output:
diablo diablo # lsmod
Module Size Used by
iptable_filter 3456 0
ip_tables 13668 1 iptable_filter
x_tables 13188 1 ip_tables
snd_pcm_oss 41632 0
snd_mixer_oss 16128 2 snd_pcm_oss
snd_seq_oss 32128 0
snd_seq_midi_event 7424 1 snd_seq_oss
snd_seq 50896 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 7564 2 snd_seq_oss,snd_seq
radeon 116512 2
drm 74136 3 radeon
fuse 40340 0
snd_intel8x0 30108 1
snd_ac97_codec 96160 1 snd_intel8x0
snd_ac97_bus 3072 1 snd_ac97_codec
snd_pcm 72196 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 20228 2 snd_seq,snd_pcm
snd 46692 9
snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 7392 2 snd
snd_page_alloc 8968 2 snd_intel8x0,snd_pcm
radeonfb 106560 0
fb_ddc 3200 1 radeonfb
nvidia_agp 7708 1
agpgart 27852 2 drm,nvidia_agp
Thank you for your help.
--
wbr Alex 'V' Fansky
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-03 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 9:15 [gentoo-user] Trouble with X.org and ati opensource drivers Alex Fansky
2007-03-03 18:36 ` b.n.
2007-03-03 22:10 ` Alex Fansky [this message]
2007-03-03 23:54 ` b.n.
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=200703040011.13077.garen@tut.by \
--to=garen@tut.by \
--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