ATI radeon Sticky (part 3)

itsr0y · Tux's lil' helper Joined: 22 Dec 2002 Posts: 81

taipan67, thanks for the reply. I tried doing the omit dga thing, as well as disabling those other modules (I have no idea what they are), but nothing changed. I noticed that when I quit X, I get the following message:

taipan67 · Posted: Fri Apr 21, 2006 9:25 pm Post subject:

itsr0y, I'm afraid i don't understand that output any better than you do, but i've got a couple of suggestions that might help you to find more clues...

Your comment about seeing the posted output when you quit X suggests that you're currently using 'startx' from a command-prompt. If that's the case, you can switch between virtual-terminals & see what the X-server was up to while it was initiating. X starts in the first available VT starting from VT7, & you can switch back & forth by holding down CTL + ALT & pressing the function-key who's number corresponds to the VT you want to switch to. So, if you boot to a command-prompt & don't change VT's in the meantime, when you 'startx' you'll be switched to VT7 & your X-windows environment. Now do 'CTL-ALT-F1' & you should see the console you started it from, with an open X-server process listed in it (no terminating comand-prompt). It's possible that you might see something culpable listed there. Doing 'CTL-ALT-F7' should then take you back to X.

Two other good places to find clues are, as the server-error snippet said, /var/log/Xorg.0.log, & also 'dmesg' - both of those are usually very long & confusing, & if you felt the need to post them here for assistance in making sense of them, you wouldn't be the first, so don't worry about offending anyone. :wink:

_________________
"Anyone who goes to see a psychiatrist should have their head examined!"

itsr0y · Tux's lil' helper Joined: 22 Dec 2002 Posts: 81

Yep, I'm using startx while I try to get this resolved---it's easier to restart X with 'startx' than gdm. As far as log messages, the Xorg.0.log doesn't seem to have anything interesting in it - no warnings or anything. dmesg gives me the following when X starts:

taipan67 · Posted: Fri Apr 21, 2006 10:30 pm Post subject:

itsr0y · Tux's lil' helper Joined: 22 Dec 2002 Posts: 81

Ah, I feel like such a fool! When I ran top, conky was taking 99.9% cpu. It must have gotten screwed up when I upgraded X and wouldn't quit when you do a normal (not -9) kill, so it stayed around across X restarts. Once I killed it, I got normal speed! Thanks for helping me problem solve!

The silver lining of this was that I learned a bit about X options and ran a few speed tests. Here are my results if they are useful to anyone:

taipan67 · Posted: Sat Apr 22, 2006 12:32 am Post subject:

drvolk · n00b Joined: 05 Jul 2003 Posts: 72

I am not sure if it is already solved in this or all the other related "ATI sticky" threats, so here maybe again the solution for "Failed to load module "glx"" Problem, which in my opinion causes also the "symbol unresolved" und "DRI not init" Errors in Xorg.conf.log:

The problem is that the library "libglx.a" is not installed under "/usr/lib/modules/extensions" but under "/usr/lib/opengl/ati/extensions".

Do:

schlumpf · n00b Joined: 29 Apr 2006 Posts: 8

Hi,
I have a 64bit-only system and for my Radeon X550 (PCIe) I use the x11-drivers/ati-drivers version 8.24.8 ebuild.
Initially I configured the "fglrx" driver in the xorg.conf, without any extra options. When I started xawtv I got just a black screen. When I switched the xawtv option "capture" from 'overlay' (default) to 'grabdisplay', I could see the tv image but it was fuzzy and flickered.

Then I used aticonfig to enable video overlay (see xorg.conf below), and restarted X and xawtv. Now I see some funny colored lines in overlay mode, and only a black screen in grabdisplay mode.

My xorg.conf looks like this:

ChaoticCoyote · n00b Joined: 13 Dec 2002 Posts: 8

I'm getting another problem. From the tail of my /ver/log/Xorg.0.log:

sjuerges · n00b Joined: 22 Dec 2005 Posts: 10

I have a weird problem here. Everything works perfect, until i logout of gnome. Then the XServer locks up, and can only be killed via ssh.
I've been googling for a hour now, and trying VARIOUS fixes, nothing works. Can anyone help ?

Regards,
Sebastian

System Data:
Asus A8N-SLI Deluxe
Powercolor x800 XL

System Setup:

sys-kernel/gentoo-sources-2.6.16-r6
x11-drivers/ati-drivers-8.24.8
x11-base/xorg-x11-7.0-r1

Xorg.cfg

supernov · Apprentice Joined: 18 Feb 2005 Posts: 164

OmG!

uname gave me the fact that I was running the previous kernel! I tried so many things to explain all the behaviour I was constantly seeing,
I'm not a noob anymore, but now I really dropped my trousers.

For some reason, in previous gentoo installations, I didn't have to
mount boot. It was probably done automatically, but with the new one I apparently changed this (which is a good thing I believe). So here I was
compiling new kernels, copying them to /boot, checking to see if they were copied, updating my linux link... and probably was doing all
that virtually!? Mounting the boot did the trick, after that my modules loaded, eth0 was working again and even the ati-drivers with
fglrx!! Incredible, weeks I spend behind the screen for this.

So, what works for me on this system is gentoo 2.6.16-r6 with ati-drivers 8.23.7, not forgetting to mount /boot when copying new kernels:

- Ati Radeon 9600
- SiS chipset controllers
- Realtek, SiS ethernet controllers

Thanks m8's!

WareKala · n00b Joined: 03 Jul 2004 Posts: 7

I have a Radeon 9100, 128mb ram, using fglrx drivers. I just seem to not be able to configure X correctly. The machine has no monitor connected, only TV, and I did get TV-out working, but it's limited to 800x600 resolution even though I know that it does 1024x768 under Windoze. I imagine it should be able to do that under Linux, too, as nVidia cards do, too. But no, what ever I try, I can't get 1024x768. Can anyone help me? Oh, and I've got another rather strange problem: when playing videos with f.ex. MPlayer using XV for display output, the picture is cropped somehow strange and stretched. Using -vo gl2 (or any other for that matter) shows the picture as it should. What's wrong? Also, the whole machine comes crashing down when X is killed, but I'm going to look into that later on, I want those first two problems solved. I hope someone here knows how to fix them.. Maybe someone could just paste a working TV-only 1024x768 configuration?

linuxn00bie255 · n00b Joined: 04 Dec 2005 Posts: 58

Hey all. I have a terribly annoying problem that occurs whenever X has to stop. For instance when I want to log out of KDE to switch users with KDM. Or if I simply startx and stop it again. My entire screen goes black. I can still move around the virtual consoles BUT I don't get to see what is going on. I tested this by typing in the commands to reboot and hoping I didn't make any typos. If I shutdown the computer from a virtual console with X running off to the side. I see this lovely error!

Erlend · Guru Joined: 26 Dec 2004 Posts: 493

Does anybody else get this problem?

Run fgl_glxgears:

DownSet · n00b Joined: 21 Jan 2006 Posts: 32 Location: Riverside, CA

Heres the error im getting

DrUberEgo · n00b Joined: 21 May 2005 Posts: 5

Yes, I know... buy an nvidia card. I hate ATI now too but I'm stuck with a Shuttle XPC box that has an Xpress 200 chipset in it and was wondering if somebody could help me get it working.

Processor: AMD Athlon FX-55.
Video (lspci): 01:05.0 VGA compatible controller: ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
ati-drivers version is at: 8.24.8
Kernel Version: 2.6.17-rc3

fglrx modules seems to load fine and pulls in agpgart as well (do I even need agpgart? My box has PCIe slot for
video)

The problem is rather severe: After running aticonfig whenever I start X the screen goes black, I lose video signal and a couple of seconds later the console comes back displaying a kernel panic. I never get any X11 or graphics at all.

Nobody else seems to be complaining about this problem, or if they did their post was so long ago that I doubt it applies to the latest ATI drivers since ATI says that the Xpress 200 is supported.

Any ideas?

Thanks.

jevge · n00b Joined: 08 Jun 2004 Posts: 17 Location: Hungary

Sorry if this was asked before, but i couldn't find anything trough search...

I managed to enable 3d on my r300, with the official ati drivers ( 8.24.8 )
(had to include intermodule support in kernel).
Everything is working, the modules are loading like they should, according to glxinfo, i have direct rendering:

CloudBolt · Posted: Fri May 12, 2006 7:51 pm Post subject: Re: eselect error

jevge · n00b Joined: 08 Jun 2004 Posts: 17 Location: Hungary

Hmm. No, the DRM isn't enabled, and i didn't emerged the ati driver, i installed the one from ati.com...
So obviously i can't remerge it

. I think that one symlink is missing, but don't know which one, and where to look...

DownSet · n00b Joined: 21 Jan 2006 Posts: 32 Location: Riverside, CA

Ok i got it down to this

Admiral_Trigger_Happy · Guru Joined: 05 Sep 2004 Posts: 337 Location: Australia

If I try to get ati-drivers 8.23.7 or 8.24.8 working on any 2.6.26+ kernel I get a hard lock whenever I start X, has anyone got any decent solutions?
I need to upgrade my kernel but I also must have acclerated opengl.
So currently I'm stuck on 2.6.14*
_________________
Admiral Trigger Happy
-------------------------------
www.kiba-dock.org

cosmicnut · Tux's lil' helper Joined: 26 Apr 2004 Posts: 94

Have you tried emerging the "ati-drivers-extra" ebuild. It seems that it links to a later version of the ATI drivers than doing the standard ati-drivers ebuild

I was having all sorts of "symbol" problems due to my kernel version, emerging the extras with the newer driver version made all my problems go away!

Erlend · Guru Joined: 26 Dec 2004 Posts: 493

Are other people getting the kernel crash when they try and logout/shutdown the computer?

I've been getting this for the last 3-4 months now (3 different driver versions) and it really annoying me. Is it "normal", is my kernel badly configured?

Thanks,

Erlend

sebgarden · Guru Joined: 21 Dec 2002 Posts: 353

I also have this problem of X crashing every time I want to restart/stop:
- if log out of gdm and try to reboot/stop the machine, the screen goes black and the box freezes
- if I am still in the gnome session and tell gnome to directly restart/stop the machine, the box freezes with the gnome background on the screen
- if I try to stop the machine pushing the on/off button on the box, I get the same freezes.

Additionaly, after a freeze and a hard reboot, firefox config get screwed and I have no bookmarks anymore if I started firefox during the last gnome session. If I started evolution during the last gnome-session and didn't shut it down completely with evolution --force-shutdown before trying to reboot/stop, then my email account setup also get screwed and I have to redo it (fortunately, my stored email are still there).

I don't know from where this problem comes but, as mentionned before, it is _really_ annoying. I think I will switch to the xorg ati drivers, if I can get them working. Why oh why is graphics configuration under linux such a hell !?!?

Seb the gardener.

Erlend · Guru Joined: 26 Dec 2004 Posts: 493

A fix for the X crash when you logout.

Recompile the kernel without vesa-tng support - use vesafb instead.

http://www.thinkwiki.org/wiki/Problems_with_fglrx#Hardlock_on_X_logout

There are more, like making the x-server restart everytime you logout, but I didn't try them.

Erlend