On Monday 29 June 2009 04:17:55 pm David C. Rankin wrote:

On Monday 29 June 2009 04:13:39 pm you wrote:

...

2009/6/29 David C. Rankin :

...

Here is the zypper se output (sorted)

Try xorg-x11-server-sdk

That was it, thanks!

(smacks self -- should have caught it ;-)

Rafal, Before I royally screw up my openSuSE 11.0/fglrx install, will I have trouble with library conflicts after installing the radeonhd driver along side the fgrlx driver? I wouldn't think so. Normally, switching between radeon and fglrx is just a matter of xorg.conf and loading/unloading the drivers. Anything special about the radeonhd driver?? (Ounce of prevention -- pound of cure...) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

On Tuesday 30 June 2009 01:08:47 am you wrote:

2009/6/30 David C. Rankin :

...

Before I royally screw up my openSuSE 11.0/fglrx install, will I have trouble with library conflicts after installing the radeonhd driver along side the fgrlx driver? I wouldn't think so. Normally, switching between radeon and fglrx is just a matter of xorg.conf and loading/unloading the drivers. Anything special about the radeonhd driver??

It's the same thing for radeon and radeonhd. Unless you use 3D, easy switching between fglrx and other driver is just a matter of changing xorg.conf and rebooting (not just X restart!). Actually it's the safiest to do cold reboot with powering off machine for a moment. That's because fglrx changes some GPU's registers in it's own way and other driver may not work as expected on modified state of GPU.

Switching between radeon and radeonhd without reboot generally doesn't cause problems, but no guarantee. For best, absolutly safe testing radeon vs. radeonhd you also should reboot.

The problem will come when 3D will be available as open driver (Mesa) and you will want to use it. fglrx changes some files in system, so open driver may not be able to work on modified system.

Thanks Rafal, That's what I needed to confirm. I'll give the radeonhd driver a good run-through on openSuSE tomorrow (I guess later today) after I get back from depos in Galveston. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Matthias Hopf wrote:

On Jun 30, 09 08:08:47 +0200, Rafał Miłecki wrote:

...

2009/6/30 David C. Rankin :

...

Before I royally screw up my openSuSE 11.0/fglrx install, will I have trouble with library conflicts after installing the radeonhd driver along side the fgrlx driver? I wouldn't think so. Normally, switching between radeon and fglrx is just a matter of xorg.conf and loading/unloading the drivers. Anything special about the radeonhd driver??

Using radeonhd when the fglrx module has *ever* been loaded during boottime is unsupported, and the driver will probably fail to present a reasonable image. Unloading the module is *not* enough.

Matthias, it's not that bad :-) If you load both and you are configured to use the radeonhd driver in xorg.conf -- you get a "white" screen. However, clicking around on the white screen you can see your menu and window outlines. You can also either alt+f2 "halt" or ctrl+alt+backspace to drop to the console. It was rather interesting.

That typically means that you have to deinstall the fglrx kernel module in order to use radeon/radeonhd. Because the fglrx module might be loaded in front.

Yes, it tries to load in front. I just blacklisted it in /etc/modprobe.d/blacklist. I am still working to get the radeonhd to run on openSuSE 11.0 (I haven't had time in the past couple of days to work with it) But, sax2 does not allow me to configure it even with sax2 -r -m 0=radeonhd. sax2 fails to start the driver for configuration. I will try again later today time permitting.

3D apps use different libGL. Depending on your distribution, the libGL might be located in different locations, so the wrong one could be loaded (can be workarounded with LD_LIBRARY_PATH), or the other library is overwritten (cannot be workarounded).

BTW, this is a FAQ.

Matthias

Thanks, I'll search for the FAQ -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

On Jul 02, 09 09:08:10 -0500, David C. Rankin wrote:

Matthias Hopf wrote:

...

Using radeonhd when the fglrx module has *ever* been loaded during boottime is unsupported, and the driver will probably fail to present a reasonable image. Unloading the module is *not* enough. Matthias, it's not that bad :-) If you load both and you are configured to use

Given the issues we had this scenario is completely unsupported. You may be lucky, other users have worse experience. All in all as long as you have fglrx installed you are on your own. It *might* work, but don't expect support from SuSE when e.g. sax2 doesn't work. That said, maybe the community has some good ideas to try. Blacklisting fglrx is not enough, because there is still the different libGL, which can actually lead to the driver module not loading at all (remember? AIGLX now requires the Xserver to load libGL as well :-/ ). CU Matthias -- Matthias Hopf __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org