Hello,
I have recently bought a computer and have installed OpenSuSE 11.1 (64-bit version). I have an ATI Radeon HD4670 graphics card and a 30 inch Dell 3007WFP-HC (2560x1600 @ 60 Hz) monitor. I tried installing the “radeonhd” driver without any success. Is anybody aware of any incompatibilities for these two components?
As a side note: I was able to install the “flgrx” driver. However, the 2D performance of this driver is just not acceptable. I have tried everything I can think of to accelerate the 2D graphics but nothing seemed to work.
Thanks in advance,
You could try taking a look at the compiz-fusion site:
Setup an ATI card with the new FGLRX drivers for Compiz-Fusion - Compiz Community Forums
User djdoo has spent the past year cataloging the options for ATI cards. It’s for fglrx and compiz, not really what you are asking, but he presents a good discussion nonetheless.
HTH
Thanks for the link. I re-installed the fglrx driver and tried the recommended changes in xorg.conf but nothing seems to help. With the new drivers (fglrx) I am getting the following error message
[fglrx:firegl_addmap] ERROR mtrr allocation failed (-22)
Today, I realized that typing
cat /proc/mtrr
will return
reg00: base=0x00000000 ( 0MB), size=8192MB: write-back, count=1
reg01: base=0x200000000 (8192MB), size=4096MB: write-back, count=1
reg02: base=0x300000000 (12288MB), size=1024MB: write-back, count=1
reg03: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1
reg04: base=0xbf800000 (3064MB), size= 8MB: uncachable, count=1
which makes me believe that there is a problem with mtrr. I have 12Gb of system memory and an ATI HD4670 512 Mb. card. Does anyone know how the MTTR problem can be fixed?
Thanks,
Hmmm, something does not seem right.
try (as root)
lsmod | grep -i fgl
Verify that the fglrx module is loaded.
try
grep -i aiglx /var/log/Xorg.0.log
Verify that the 64 bit fglrx_dri.so object is OK
Other thoughts:
dmesg | grep -i memory
Is all your RAM being recognized by your motherboard?
Does Xorg.0.log show your monitor’s EDID info read in OK?
Did you softlink your 32bit fglrx_dri.so file with your 64bit lib location?
Finally, FYI, I had poor luck with Catalyst 9.2, but 9.1 was great in my AMD64 box with 4Gb RAM.
HTH
Thanks for the reply. Here is what I get
lsmod | grep -i fglrx
fglrx 2339304 30
and
grep -i aiglx /var/log/Xorg.0.log
(**) Option "AIGLX" "on"
(==) AIGLX disabled
(WW) fglrx: Force AIGLX enabled
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
(II) AIGLX: Loaded and initialized /usr/lib64/dri/fglrx_dri.so
So I guess fglrx_dri.so is OK. The motherboard recognizes all available memory. The thing is in the BIOS there are no options I can play with (Dell Studio XPS 435MT). In addition, I did softlink the 32-bit fglrx_dri.so, without which I would keep getting a black screen. Any additional thoughts are greatly appreciated. Especially, it would be great if you have any idea on how to manually change MTTR settings for 12 Gb. system memory and 512 Mb. Graphics Card memory.
Thanks!!!
Funny, I first mistyped it as mttr, just like you. Wondered why I was getting downtime statistics from google…
You have a lot of RAM. Maybe it’s a bad chip, a voltage drop issue, a timing problem. Dunno. Unplug 8Gigs of RAM, see if it works then?
You could burn a Puppy linux CDROM and run off of that, see if the hardware checks out all right. Or, in Opensuse, log in using fvwm or icewm instead of KDE.
Seems like things are oh-so-close to working. Gotta isolate the factors. But the video driver itself seems OK now.
I forgot to add:
ATI adds a little script to collect system status, at
/usr/sbin/atigetsysteminfo.sh
Nothing you couldn’t do yourself; just a convenience.
HTH
Thanks for the replies…
I think I will switch to Kubuntu instead. I have downloaded the LiveCD and it seems to work fine. The 2D graphics performance is waaay better compared to OpenSuSE. The funny thing is it also uses the fglrx driver.
Thanks!