ATI Drivers - Some questions

English Hardware
1

I have a relatively new PC, AMD 785 North Bridge device.
I have not seen specific references to this device, but have generally had luck with drivers aimed at the “AMD 7xx” family.

Under Suse 11.1, fglrx_02(from repository) and Catalyst 9.11 (from ATI) loaded and ran fine.
I also tried what I believe was Xorg radeonhd, but am now not sure if it was radeon or radeonhd.

I have updated to 11.2.
So far, I have been running the repository radeonhd driver, but cannot get suspend-to-ram to come back alive and believe it is video issue.

I set up the video using

SaX2 -r -m 0=radeonhd

at level 3 in a console, then init 5. Seems to run OK.
But why, when I execute

lsmod|grep radeon

do I see nothing? I have also looked thru the entire lsmod output, do not see anything that looks like radeon or radeonhd. I can’t say for sure that it is not the VESA driver running - any thoughts out there?

I expect that fglrx_02 and Catalyst 9.11 would load and run, but prior experience says they will not play well with S2RAM.

I went to try the Xorg radeon driver, which supposedly is still different than radeonhd, to see if it would suspend properly.
But I don’t see it in the 11.2 repository, only radeonhd - anyone know why?

2

Your correct, in that the active driver should appear in ‘lsmod’ results. Anyway, see what graphics driver is reported with one of these commands

/sbin/lspci /k

/usr/sbin/hwinfo --gfxcard

Many of the open source graphics drivers are included as part of the xorg-x11-driver-video package or similar.

3

Thanks, I do believe I was running VESA driver of some sort.

lspci -k did not list any kernel module under the video controller

And yes, the radeon driver is part of the
xorg-x11-driver-video RPM.
The radeonhd is in its own rpm,
xorg-x11-driver-video-radeonhd

I’ll investigate why radeonhd is not loading.

4

What AMD/ATI graphics chipset do you have?

5

Integrated gpu in the 785 North Bridge.
Also know as 4200 Graphics.

Looking at /var/log/Xorg.0.log, it appears that several errors (EE) were being logged with the radeonhd driver.
Switched to radeon driver, still experimenting.