Catalyst 8.7

[pierluc]

The Windows béta of Catalyst 8.7 is out:
http://www.fudzilla.com/index.php?option=com_content&task=view&id=8277&Itemid=34

Do you know if the Linux béta is also out?

[d2kx]

It's a leaked, early test driver for the Catalyst 8.8 driver release, so no one will recommend you downloading that driver.

But I can smell that a new official driver release is in the air... can't be far away from now ;)

[Melcar]

Leaked driver. ATI only holds closed BETA programs. Use at your own risk.

[Vighy]

It's a leaked, early test driver for the Catalyst 8.8 driver release, so no one will recommend you downloading that driver.

But I can smell that a new official driver release is in the air... can't be far away from now ;)

maybe tomorrow... or the next week... :D ain't it right? :D

[Nille]

maybe tomorrow... or the next week... :D ain't it right? :D

someone sayd tomorrow ;)

[brot]

:) new driver would be a nice thing, since it would be the first driver update while i own a amd card and i hope it will be a nice release.

And yes, i smell a new release, too

[enzobelmont]

why bother with it??

is the same shame every month... :(

[Vighy]

why bother with it??

is the same shame every month... :(

Not always, and not in any compartment. it simply depends :D :D :D

[yoshi314]

is the same shame every month...not the same. developers work hard to screw up at a different place each month :]

[Vighy]

someone sayd tomorrow ;)

Mhh it was not yesterday.... so it will be the next week :D:D:D:p

[Nille]

Mhh it was not yesterday.... so it will be the next week :D:D:D:p

No Problem the Catalyst 8.6 works fine vor me so i can wait :p

[DanL]

I tried the Catalyst 8-6 drivers with my new 3200 IPG (780G mobo) and got a white screen of death. I went back to radeonHD and at least mode-setting works if no acceleration. I'm a patient man, and will wait for the radeonHD team to bang away at the registers.

[pierluc]

with Catalyst 8.6 the performance on fgl_glxgears are very bad.

Catalyst 8.5: 300 fps
Catalyst 8.6: 75 fps

The 3D work but the performance are bad.

Last year I have read that AMD will give a Linux driver who give the same performance than the Windows driver... Is it for Jully 2008? for Jully 2030?...

[mtippett]

with Catalyst 8.6 the performance on fgl_glxgears are very bad.

Catalyst 8.5: 300 fps
Catalyst 8.6: 75 fps

The 3D work but the performance are bad.

Last year I have read that AMD will give a Linux driver who give the same performance than the Windows driver... Is it for Jully 2008? for Jully 2030?...

Numbers like that indicate that you have are running with vsync on. Go into CCCLE and look for the vsync options.

Regards,

Matthew

[Janusz11]

I’m really looking forward to this new driver release and hope its coming out soon.

So far, I have only been able to install Catalyst 8.6 on Arch Linux, but not to change the screen resolution (to 1152x864 @ 100Hz – I don’t think that’s something extraordinary!).

On Zenwalk I couldn’t install the driver at all, neither on kernel 2.5, nor 2.6. I have checked the net for the several error messages I got due my process in trying to get the drivers to work and it seems like its back to applying patches and compiling the kernel just to get a graphics card driver to work (reminds me of my time when I was still using a Radeon 9800 and why I have changed to nVidia).

In games on Windows the new HD4870 is a blast, which is why I really like to keep this card. But its frustrating to see that momentarily that’s really the only way my new rig is workable.

Since I still have a week time to return the new card I hope the driver is coming out in the next couple of days because I really want to give it another try.

[Vighy]

I’m really looking forward to this new driver release and hope its coming out soon.

So far, I have only been able to install Catalyst 8.6 on Arch Linux, but not to change the screen resolution (to 1152x864 @ 100Hz – I don’t think that’s something extraordinary!).

On Zenwalk I couldn’t install the driver at all, neither on kernel 2.5, nor 2.6. I have checked the net for the several error messages I got due my process in trying to get the drivers to work and it seems like its back to applying patches and compiling the kernel just to get a graphics card driver to work (reminds me of my time when I was still using a Radeon 9800 and why I have changed to nVidia).

In games on Windows the new HD4870 is a blast, which is why I really like to keep this card. But its frustrating to see that momentarily that’s really the only way my new rig is workable.

Since I still have a week time to return the new card I hope the driver is coming out in the next couple of days because I really want to give it another try.

Remember that they do not support their driver on those platforms.
I've got problems too: Xorg hangs when closed, but I don't complain since I'm not on a supported platform.

I will check if the problem is mine, or it's the driver, but as long as I'm not sure, I don't complain.

I know you may say that suse, or fedora suck, (I don't think it, even if I use gentoo) but they're the best way at the moment to make Catalyst work for sure and as expected.

But don't worry, on Wednesday the driver should be out.

[NeoBrain]

Last year I have read that AMD will give a Linux driver who give the same performance than the Windows driver... Is it for Jully 2008? for Jully 2030?...

Just for the record, my X1600 works just as fast on Linux as on Windows when playing Nexuiz :D
I'm sorry that there are still people who suffer these kinds of problems at every new driver release... I, for myself, are forced to stay at 8.4 for now as 8.5 & 8.6 can't do 3d on a second x server for me.

However, I REALLY hope they finally fixed their damn Wine bug!
(http://bugs.winehq.org/show_bug.cgi?id=13335)

[pierluc]

Numbers like that indicate that you have are running with vsync on. Go into CCCLE and look for the vsync options.

Regards,

Matthew

Where is this option on the Catalyst Control Panel?

[storma]

Where is this option on the Catalyst Control Panel?

3D -> More Settings -> Wait for vertical refresh.

[ivanovic]

I will check if the problem is mine, or it's the driver, but as long as I'm not sure, I don't complain.


Remove atieventsd from your list of progs and xorg will be able to normally shutdown.

[Vighy]

Remove atieventsd from your list of progs and xorg will be able to normally shutdown.

Mh ok, but what's the real function of it? ain't it there to catch acpi events like the lid closed, or the Fn+"whatever button" press to perform something to the monitor?

and what I really miss removing it? :)

thanks

[JA_SAM]

and what I really miss removing it? :)
thanks
PowerPlay i think,maybe few things also.

[Vighy]

Now Xorg crashes on the re-start.

Closing is ok, starting again results in hang :D :D funny ain't it?

[anyone]

I had the problem of X hanging when I restarted it; try to disable framebuffer. That's what fixed it for me.

[Vighy]

I had the problem of X hanging when I restarted it; try to disable framebuffer. That's what fixed it for me.

Really!?

nuooooo I will have to say goodbye to that beautiful theme! :D:D:D ok I will try that too.. :D I really want to get rid of those boring hangs!

thanks to all! :)


EDIT: Ok right, without frame buffer, it doesn't hang on X restart... only sorry for my splash screen :D :D :D

[pierluc]

3D -> More Settings -> Wait for vertical refresh.

Tanks! Now my performance are better.

[Laughing1]

The Windows béta of Catalyst 8.7 is out:
http://www.fudzilla.com/index.php?option=com_content&task=view&id=8277&Itemid=34

Do you know if the Linux béta is also out?

The Linux (or Windows) beta is private and you are required to accept a NDA. The above beta is clearly a breach of that agreement, IMHO. :eek:

[d2kx]

http://www2.ati.com/drivers/linux/ati-driver-installer-8-7-x86.x86_64.run :)

Release Notes: https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_87_linux.html

[kiwibob32]

Here I was thinking that this release would FINALLY support the version of xorg that comes with Fedora 9 and my wait would be over... Guess I have to go down the path of installing the xorg from Fedora 8 instead.

slackers...

[zappbrannigan]

What about Kernel 2.6.26?

[Heiko]

Just installed the driver on a fresh Ubuntu 8.04 with a Radeon 4870. After the installation was finished I heard the Ubuntu logoff sound, and when I logged of and did a Ctrl-Alt-Backspace I got screen corruption. But after I restarted my pc, the corruption was gone, so I guess it works. Glxgears gives me a nice 12500 fps and everything feels nice and smoothly so far.

[homerhomer]

As always theses drivers have issues (sign). I found that by using the default amdpcsdb fixed slowdown that I was having.

:Warning this will reset all your setting that you changed in ATI control center, maybe your xorg settings too.

log in as root and type

cp /etc/ati/amdpcsdb /etc/ati/amdpcsdb.old
cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb

[caleb12]

One thing is fixed and another is broke... Although, I have to say I am not completely sure this is an ATI issue.

fgl_glxgears gives me a seg fault Using GLX_SGIX_pbuffer

I've been googling a bit, but havent found anything that fixes it. Everything is fine when compiz isnt running... but seg faults with it on. flg_glxgears -fbo works, but... creates massive screen distortion even after I kill the gears - pretty much renders the desktop useless until I restart X.

Nothing unusual in the logs... and this only started occurring after the 8.7 update. ATI is such an easy scapegoat though... :)

** So, I've discovered that since compiz always runs as LIBGL_INDIRECT - that launching a terminal window using compiz's key commands will create that terminal as a child process and as such will inherit compiz's environment (along with the LIBGL_INDIRECT)... Well, fgl_glxgears will always seg fault in that environment. Running a simple xterm and running the same will work as it should **

[bridgman]

caleb12, which GPU are you using ?

[hehe2]

Well,

the 8.6 ati driver was just freezing and locking my whole computer when I was launching a 3D game.

the 8.7 is a bit better, it only crashes the Xorg server at the start of a 3D Game (using cedega) ... or (when it doesn't) just make the display look like a random colorful art picture ...

Summary :
---------

- 8.4 ATI DRIVER :

Lacks the 2.6.25 kernel support ...
Pb with 4Gb of RAM using 64Bit arch or 32bit arch with no 64Gb support enabled.

- 8.5 ATI DRIVER :

Same issues as the ones of the 8.4 driver but has 2.6.25 kernel support
Black borders at the X start and after each resolution change ==> fixed using a script got on this forum then tuned.

- 8.6 ATI DRIVER :

cedega Wow.exe -opengl ==> Computer freeze, needs a hard reboot.
wine Wow.exe -opengl ==> Computer freeze, needs a hard reboot.

- 8.7 ATI DRIVER :

cedega Wow.exe -opengl ==> X crash, need to CTRL+ALT+BACKSPACE and restart X
wine Wow.exe -opengl ==> corrupted display, unusable, need to kill the app.

In four month, I've not seen much improvement ...

At the same time, still no 3870X2 support ... how long will it take ATI to provide us with consistent and solid fully working drivers ?

Desperate ...


hehe2

[caleb12]

caleb12, which GPU are you using ?

ATI Technologies Inc M24 1P [Radeon Mobility X600]
Subsystem: Hewlett-Packard Company Device 3082

Kernel driver in use: fglrx_pci
Kernel modules: fglrx, radeonfb

[Gottxxc]

Another bullshit release...

The open source ati and radeonhd driver are much better than the crap fglrx driver.

[storma]

:s bullshit on your bullshit.

There was a time when I couldn't play savage2 because of invisible models. S2games put out a release that fixed most of it and now with 8.7, ati have fixed the few remaining graphical problems.

Yes we do have a few bugs overall but for the most part things are moving forward.

A lot of people have been complaining that the wine bug isn't fixed. Remember, we are using linux! Native apps should come first. As for games, they're a recreational pass time, they should be low on the list of priorities.

[paul]

I'm seeing some improvement too. My mobility X1400 seems a bit quicker scrolling in firefox with 8.7 versus 8.6.

But on the negative side, the latest ubuntu hardy kernel update to 2.6.24-20 seems to have broken the fix for full screen flashing in google earth and dvd's. With the older kernel 2.6.24-19 and 8.7 and compiz, there's no flashing. But with the latest kernel (-20), the flashing is back. Any ideas?

Thanks for the progress!

paul

[mile]

i will stick with radeon 6.9.0 on my mobility 1600...its much better then this crap

it is missing just powerplay implementation. It is much better to have nosier than unstable notebook

[Moronix]

So I see conflicting info, does this support kernel 2.6.26 or not?

[Kano]

Possible using a patch, but it was deleted from phorogit. My script has it included too:

http://kanotix.com/files/install-fglrx-debian.sh

Works directly with a system where dkms is preinstalled or installable. That means it works for Ubuntu and for Debian when

http://linux.dell.com/dkms/dkms_2.0.20.2-0ubuntu1_all.deb

is installed. This does _not_ fix the ABI error with Xserver 1.5.

[paul]

i will stick with radeon 6.9.0 on my mobility 1600...its much better then this

I thought 6.9.0 did not support compiz? Do you have compiz running on it?

paul

[Photodeus]

As for games, they're a recreational pass time, they should be low on the list of priorities.


Oh please. Getting a high end graphics card is because of games. I could buy something low-end if I didn't prioritize games.

[bridgman]

i will stick with radeon 6.9.0 on my mobility 1600...its much better then this

I thought 6.9.0 did not support compiz? Do you have compiz running on it?

paul

AFAIK the changes related to Compiz were all in the drm and mesa drivers not radeon, so 6.9.0 should be OK for Compiz on 5xx if you have the right bits for the rest of the driver stack. Just be aware that the latest version of Mesa (which you probably need) also needs a very recent X server so you'll probably have to update X as well.

The good news is that the combination seems to work quite nicely.

[harvy]

what about slow 2D performance? browsing in konq is very slow (refreshing).

[zappbrannigan]

I found 2 bugs on my system (Debian unstable, 32 bit, kernel 2.6.25, Radeon 3870, nearly empty xorg.conf):

If I start my kernel with vga=31b the X Server crashes with:
(EE) fglrx(0): PreInitDAL failed

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x7e) [0x80c914e]
1: [0xffffe400]
2: /usr/lib/xorg/modules/drivers//fglrx_drv.so(amdPcsFree+0x36) [0xb7942216]
3: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit+0x2af) [0xb791b90f]
4: /usr/bin/X11/X(InitOutput+0xa0f) [0x80ab33f]
5: /usr/bin/X11/X(main+0x2b1) [0x8074591]
6: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7dde455]
7: /usr/bin/X11/X(FontFileCompleteXLFD+0x21d) [0x8073a81]

Fatal server error:
Caught signal 11. Server aborting

I don't know if this happens with old drivers.


The second bug concerns suspend to disc. After the first system boot (not resuming) it's necessary to start a video. If not the system will hang on playing a video after resuming. This concerns all releases this year.

I don't know if there is a progress with my mtrr problem under 64 bit since i'm not using 64 bit anymore.

[Vighy]

I found 2 bugs on my system (Debian unstable, 32 bit, kernel 2.6.25, Radeon 3870, nearly empty xorg.conf):

If I start my kernel with vga=31b the X Server crashes with:
(EE) fglrx(0): PreInitDAL failed

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x7e) [0x80c914e]
1: [0xffffe400]
2: /usr/lib/xorg/modules/drivers//fglrx_drv.so(amdPcsFree+0x36) [0xb7942216]
3: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit+0x2af) [0xb791b90f]
4: /usr/bin/X11/X(InitOutput+0xa0f) [0x80ab33f]
5: /usr/bin/X11/X(main+0x2b1) [0x8074591]
6: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7dde455]
7: /usr/bin/X11/X(FontFileCompleteXLFD+0x21d) [0x8073a81]

Fatal server error:
Caught signal 11. Server aborting

I don't know if this happens with old drivers.


The second bug concerns suspend to disc. After the first system boot (not resuming) it's necessary to start a video. If not the system will hang on playing a video after resuming. This concerns all releases this year.

I don't know if there is a progress with my mtrr problem under 64 bit since i'm not using 64 bit anymore.

Here on M76 - Mobility Radeon HD2600:

The second happens to me too here (with all versions of fglrx with all versions of Xorg and with all versions of the kernel :D but under 64bit)

For the first I get it even without specifying anything to the kernel! (but sure with xserver-1.4.*, with xserver 1.3 not tested, and every kernel :D)
http://www.phoronix.com/forums/showthread.php?t=11570

so, what about this!?

[zappbrannigan]

For the first I get it even without specifying anything to the kernel! (but sure with xserver-1.4.*, with xserver 1.3 not tested, and every kernel :D)
http://www.phoronix.com/forums/showthread.php?t=11570

No your problem seems to be different. My XServer crashes later. :p

(II) fglrx(0): === [atiddxPreInit] === begin
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 2.0
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "DPMS" "true"
(II) fglrx(0): Loading PCS database from /etc/ati/amdpcsdb
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(**) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(--) fglrx(0): Chipset: "ATI Radeon HD 3870" (Chipset = 0x9501)
(--) fglrx(0): (PciSubVendor = 0x1002, PciSubDevice = 0x2542)
(--) fglrx(0): board vendor info: original ATI graphics adapter
(--) fglrx(0): Linear framebuffer (phys) at 0xd0000000
(--) fglrx(0): MMIO registers at 0xfe9e0000
(--) fglrx(0): I/O port at 0x0000d000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.1.0
ABI class: X.Org Video Driver, version 2.0
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 10.67
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: RV670
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.51.3
ABI class: X.Org Server Extension, version 0.3
(II) fglrx(0): Using adapter: 1:0.0.
(II) fglrx(0): [FB] Find the MC FB aperturs range(MCFBBase = 0xc0000000, MCFBSize = 0x20000000)
(--) fglrx(0): VideoRAM: 262144 kByte, Type: DDR4
(II) fglrx(0): PCIE card detected
(--) fglrx(0): Using per-process page tables (PPPT) as GART.
(II) fglrx(0): board/chipset is supported by this driver (original ATI board)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module "ddc" already built-in
(II) fglrx(0): Connected Display1: DFP on secondary TMDS [tmds2i]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: ENC Model: 1687 Serial#: 0
(II) fglrx(0): Year: 2003 Week: 30
(II) fglrx(0): EDID Version: 1.2
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 38 vert.: 30
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
(II) fglrx(0): blueX: 0.140 blueY: 0.100 whiteX: 0.313 whiteY: 0.329
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 108.0 MHz Image Size: 376 x 301 mm
(II) fglrx(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) fglrx(0): Serial No: 46716073
(II) fglrx(0): Ranges: V min: 59 V max: 61 Hz, H min: 31 H max: 64 kHz, PixClock max 110 MHz
(II) fglrx(0): Monitor name: L767
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff0015c3871600000000
(II) fglrx(0): 1e0d010280261e78eaeee5a3544c9923
(II) fglrx(0): 195054a1080081800101010101010101
(II) fglrx(0): 010101010101302a009851002a403070
(II) fglrx(0): 1300782d1100001e000000ff00343637
(II) fglrx(0): 31363037330a20202020000000fd003b
(II) fglrx(0): 3d1f400b000a202020202020000000fc
(II) fglrx(0): 004c3736370a202020202020202000f8
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(EE) fglrx(0): PreInitDAL failed


.

The second happens to me too here (with all versions of fglrx with all versions of Xorg and with all versions of the kernel but under 64bit)

I started with suspend to disc this year...

so, what about this!?
It's a bug not a feature ;)