ATI card and compositing support?

deesto · 03-03-2010, 08:01 AM

Quote:

Originally Posted by adamk75

Odd... So the screen goes black, but the machine is still responsive?

Yep; I'm logged into it now.

Quote:

Could you grab the /var/log/Xorg.0.log file and pastebin it?

Sure:
http://deesto.pastebin.com/GiZWqQRk
No errors that I can see; the only warnings are:

Code:

(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
...
(WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area 536854528 (size: 16384) extends beyond available framebuffer size 268435456

Quote:

Have you checked to see if there are any updates to the radeon driver in F12? Or perhaps even tried a newer version from rawhide?

There doesn't seem to be anything newer in the repos, and I have a feeling the radeon driver is already somewhat experimental, as it includes 'git' in its version:
#yum list installed *radeon*

Code:

radeontool.x86_64                            1.5-6.fc12                                @rawhide
xorg-x11-drv-radeonhd.x86_64                 1.3.0-4.2.20091204git.fc12                @updates

adamk75 · 03-03-2010, 08:18 AM

You're currently using the 'radeonhd' driver, not the 'radeon' driver. While radeonhd should, theoretically, work, it doesn't see as much development or testing as the radeon driver. If you didn't have an xorg.conf file in your home directory specifying radeonhd, Xorg should, in fact, default to the radeon driver.

Adam

deesto · 03-03-2010, 08:24 AM

Quote:

Originally Posted by adamk75

You're currently using the 'radeonhd' driver, not the 'radeon' driver. While radeonhd should, theoretically, work, it doesn't see as much development or testing as the radeon driver.

Unfortunately, that's because there is no non-hd driver available, according to yum: 'yum list *radeon*' returns the same two packages as 'yum installed *radeon*'. Maybe I'm missing an additional repo?

Quote:

If you didn't have an xorg.conf file in your home directory specifying radeonhd, Xorg should, in fact, default to the radeon driver.

I get the same results if I delete xorg.conf and reboot, which is in fact what I've just done, same exact results.

adamk75 · 03-03-2010, 08:27 AM

Does /usr/lib64/xorg/modules/drivers/radeon_drv.so exist? It should, because that's the default driver F12 uses for all radeon GPUs. I don't know what that's packaged as, but it should definitely exist. Try specifying the radeon driver and then pastebin the log file if it doesn't work.

deesto · 03-03-2010, 08:39 AM

adamk75: yes; both radeon_drv.so and radeonhd_drv.so are there. 'sudo X -configure' gave me a fairly sizable conf file to work with, and it did include a "radeonhd" driver entry. I changed this to "radeon" and rebooted, and I can't tell why, but the Xorg logs still show the "radeonhd" module being loaded in addition to "radeon", same results.

adamk75 · 03-03-2010, 08:41 AM

Really, please pastebin the log file :-)

Adam

deesto · 03-03-2010, 08:45 AM

Quote:

Originally Posted by adamk75

Really, please pastebin the log file :-)

This is another attempt, even after uninstalling the radeonhd driver via yum ... go figure!
http://deesto.pastebin.com/QZgExVyU

adamk75 · 03-03-2010, 08:49 AM

Well the radeonhd driver is clearly still on your filesystem. If you actually removed it via yum, then there is something wrong with your fedora installation, which you need to resolve before trying to get compositing working. Unfortunately, I really don't have any idea what 'something' is at the moment.

Adam

deesto · 03-03-2010, 09:06 AM

The 'hd' driver was eventually removed after a few restarts. It's definitely gone now and no reference to it in the conf.

Now Xorg isn't looking for that, but still not working:
http://deesto.pastebin.com/tKazhr60

Now some new errors there: including some looking for a module called 'fgl.renamed.libglx'. Oddly enough, 'FGL.renamed.libglx.so' does exist in modules/extensions; why the 'FGL' is lower-case in the log, I'm not sure, especially, since it's referenced as 'FGL' in xorg.conf.

adamk75 · 03-03-2010, 09:15 AM

That's still the old Xorg log file. Also, if you have fgl* files on your system, you apparently still have the remnants of the fglrx driver installed all your system.

deesto · 03-03-2010, 09:31 AM

Sorry ... please refresh the page; I edited my post with the right log file (I think; too much pastebin going on here): http://deesto.pastebin.com/tKazhr60

adamk75 · 03-03-2010, 09:35 AM

OK, we're getting closer, but clearly there is still something not quite working here... First, Xorg is using /root/xorg.conf.new. Did you tell it to do that?

Second:

Code:

(II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="FireGL - ATI Technologies Inc."

You still have the FireGL drivers installed, at least partially. They need to be *completely* removed in order for Xorg to work with the open source drivers.

Adam

deesto · 03-03-2010, 09:45 AM

Thanks ... let me clear up a few things:
- the fglrx stuff was left behind by the proprietary driver. I did a re-install and un-install to clean up the cruft, which seemed to work.
- that xorg.conf.new was the default name for the file generated by 'X -configure'. I have rebooted and rerun this using the usual file name.
- after all that, still the same %$#^& result: http://deesto.pastebin.com/NS33bWrg

adamk75 · 03-03-2010, 09:51 AM

Code:

(II) RADEON(0): Output DVI-0 connected
(II) RADEON(0): Output DIN disconnected
(II) RADEON(0): Output DVI-1 connected
(II) RADEON(0): Using spanning desktop for initial modes
(II) RADEON(0): Output DVI-0 using initial mode 1680x1050 +0+0
(II) RADEON(0): Output DVI-1 using initial mode 1680x1050 +1680+0

The odd thing is that the driver clearly sees both monitors connected to DVI ports.

Wait... Are you actually running 'startx' or just 'Xorg' (or 'X')?

Adam

deesto · 03-03-2010, 10:05 AM

Quote:

Originally Posted by adamk75

Wait... Are you actually running 'startx' or just 'Xorg' (or 'X')

I wasn't manually running anything ... just booting into init 5, and then when it hung, I was running 'X' in a separate TTY to test. If I run 'startx' from there, I do get a graphic environment, but barely: just a bare desktop, no menu, no launchers. The only thing new I see in the Xorg log after doing 'startx' is '(II) AIGLX: Suspending AIGLX clients for VT switch".