AMD Catalyst 8.7 Linux Driver Released

[Vighy]

Hi,

again a release without support for the HD3870X2

Since I need the card for blender and ogre works, I wouldn't need the second core to be active. So it would be enough if the driver could make use of the first core. Since the HD3870 with just one core does run with the driver, that shouldn't be that big problem or am I wrong with that?

I can use radeonhd as the only alternative at the moment. But that one does support only the very basic 2D functions in 1.2.1 (anyways good work!).

I have to say, that this is my first ATI card for years. Most important reason for buying no NVidia again is, that ATI started to support OSS and relasing card specs.

So if somebody knows a workaround to get fglrx up and running with one core I would be very glad!

Greets,

Nightwulf

Guys, you were told that HD3870X2 would have not been supported under linux...

I know it was not clear to everybody.... but Bridgman already said it was supposed to work just under winblows.

[Almindor]

They finally fixed Savage 2 shaders, but they broke ETQW (crashes now) which sucks big time.

otherwise it seems to be working ok so far for me, no big difference in performance.

[NIghtwulf]

Hi,

Guys, you were told that HD3870X2 would have not been supported under linux...

I know it was not clear to everybody.... but Bridgman already said it was supposed to work just under winblows.

who told that? I'm new here and the Releas Notes in the official drivers say *currently* not supported. ATI did never tell their customers on any official channel, that the X2 cards will be only supported in Windows.

So that's no excuse nor do I believe they don't want to support it at all.

Nightwulf

[grantek]

Hi All,

This is my first post, so I just have to get this out of the way: THANK YOU AMD - my system is broken and doesn't play games, but I really appreciate the effort being put into Linux support, and my new system is all-AMD because of that fact.

Having said that, I need some help. I just bought a new AMD 9750 system with a HD4850, and I'm mainly trying to get ET:QW and Wine/Cedega going. I get a segfault on ET:QW, I haven't tested Wine on 8.7 (I was having unrelated problems while using 8.6, but I was also getting corruption). Reading the thread for the 8.6 driver, it seems like an mtrr issue.

Full system is:
AMD Phenom 9750
Gigabyte GA-MA790X-DS4
Gigabyte 512MB Radeon HD4850
1x 2GB Kingston 800MHz RAM module
Ubuntu 8.04 x86_64,running either -rt or -generic kernel (the X driver is currently compiled for -rt)

lspci -v is:

00:00.0 Host bridge: ATI Technologies Inc RD780 Northbridge only dual slot PCI-e_GFX and HT1 K8 part
	Subsystem: ATI Technologies Inc RD780 Northbridge only dual slot PCI-e_GFX and HT1 K8 part
	Flags: bus master, 66MHz, medium devsel, latency 32
	Memory at <ignored> (64-bit, non-prefetchable)
	Capabilities: [c4] HyperTransport: Slave or Primary Interface
	Capabilities: [40] HyperTransport: Retry Mode
	Capabilities: [54] HyperTransport: UnitID Clumping
	Capabilities: [9c] HyperTransport: #1a

00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx0 port A) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: fdf00000-fdffffff
	Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot-) IRQ 0
	Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
	Capabilities: [b0] Subsystem: ATI Technologies Inc Unknown device 5958
	Capabilities: [b8] HyperTransport: MSI Mapping

00:0a.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port F) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: fde00000-fdefffff
	Prefetchable memory behind bridge: 00000000fdd00000-00000000fddfffff
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot-) IRQ 0
	Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
	Capabilities: [b0] Subsystem: ATI Technologies Inc Unknown device 5958
	Capabilities: [b8] HyperTransport: MSI Mapping

00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
	Subsystem: Giga-byte Technology Unknown device b005
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 22
	I/O ports at ff00 [size=8]
	I/O ports at fe00 [size=4]
	I/O ports at fd00 [size=8]
	I/O ports at fc00 [size=4]
	I/O ports at fb00 [size=16]
	Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [60] Power Management version 2

<USB controllers snipped because the post was too long>

00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
	Subsystem: Giga-byte Technology Unknown device 4385
	Flags: 66MHz, medium devsel
	I/O ports at 0b00 [size=16]
	Capabilities: [b0] HyperTransport: MSI Mapping

00:14.1 IDE interface: ATI Technologies Inc SB600 IDE (prog-if 8a [Master SecP PriP])
	Subsystem: Giga-byte Technology Unknown device 5002
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
	I/O ports at 01f0 [size=8]
	I/O ports at 03f4 [size=1]
	I/O ports at 0170 [size=8]
	I/O ports at 0374 [size=1]
	I/O ports at f900 [size=16]

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
	Subsystem: Giga-byte Technology Unknown device a002
	Flags: bus master, slow devsel, latency 32, IRQ 16
	Memory at fe024000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2

00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
	Subsystem: Giga-byte Technology Unknown device 5001
	Flags: bus master, 66MHz, medium devsel, latency 0

00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01 [Subtractive decode])
	Flags: bus master, VGA palette snoop, 66MHz, medium devsel, latency 64
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=64
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: fdc00000-fdcfffff
	Prefetchable memory behind bridge: fdb00000-fdbfffff

00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration
	Flags: fast devsel
	Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map
	Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller
	Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control
	Flags: fast devsel
	Capabilities: [f0] #0f [0010]

00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control
	Flags: fast devsel

01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 9442 (prog-if 00 [VGA controller])
	Subsystem: ATI Technologies Inc Unknown device 0502
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Memory at fdfe0000 (64-bit, non-prefetchable) [size=64K]
	I/O ports at de00 [size=256]
	[virtual] Expansion ROM at fdf00000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Legacy Endpoint IRQ 0
	Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

01:00.1 Audio device: ATI Technologies Inc Unknown device aa30
	Subsystem: ATI Technologies Inc Unknown device aa30
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Memory at fdffc000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Legacy Endpoint IRQ 0
	Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
	Subsystem: Giga-byte Technology Unknown device e000
	Flags: bus master, fast devsel, latency 0, IRQ 509
	I/O ports at ee00 [size=256]
	Memory at fdeff000 (64-bit, non-prefetchable) [size=4K]
	[virtual] Expansion ROM at fdd00000 [disabled] [size=128K]
	Capabilities: [40] Power Management version 2
	Capabilities: [48] Vital Product Data
	Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+
	Capabilities: [60] Express Endpoint IRQ 0
	Capabilities: [84] Vendor Specific Information

03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology Unknown device 1000
	Flags: bus master, medium devsel, latency 32, IRQ 22
	Memory at fdcff000 (32-bit, non-prefetchable) [size=2K]
	Memory at fdcf8000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [44] Power Management version 2

/proc/mtrr is:

reg00: base=0x00000000 (   0MB), size=15730688MB: write-back, count=1
reg01: base=0x7ff00000 (2047MB), size=15728641MB: uncachable, count=1

If I try to disable reg00 with the system booted, or in the startup before X, the system crashes. If I add a new line at base 0x00000000 with a 2GB size, the count goes up and the size reported in /proc/mtrr doesn't change (removing it works, and just decrements the count). As far as I'm aware, I should be removing reg01 and adding an uncachable block where the 4850's memory is, but I don't know where that is. I saw some references to 0xD0000000, but the only reference to that in lspci is a range of 0xD0000000-0xDFFFFFFF, which is 256MB.

I also have no clue why my /proc/mtrr ranges are so huge by default. If anything, it looks like it should work because all but 1MB of the system memory is write-back, and from there on (where the graphics RAM would be) it's uncachable. I don't know what happens when there's an overlap in the memory ranges.

Any ideas?

[Vighy]

Hi,



who told that? I'm new here and the Releas Notes in the official drivers say *currently* not supported. ATI did never tell their customers on any official channel, that the X2 cards will be only supported in Windows.

So that's no excuse nor do I believe they don't want to support it at all.

Nightwulf

Bridgman said it here: http://www.phoronix.com/forums/showp...22&postcount=8

I'm sorry.

[pchristy]

There is no direct 2.6.26 support, but you find the patch here:

http://phorogit.com/index.php?p=fglr...da869c529cafe4

Hi, I'm new to this forum and fairly desperate for a fix! I'm running Slamd-64 (64-bit port of Slackware) on kernel 2.6.26. None of the ATI drivers will compile with this kernel, and I can't wait a month for the next release!

I normally install from the xxx.run file that I download from the ATI website. However, I can't figure out how to apply this patch to the "run" file. I suspect the file has to be unpacked, patched and then re-packed, but how?

An idiots guide would be appreciated!

--
Pete

[gsmd]

ok, on gigabyte's 780 mobo i don't get the black screen anymore, the system jest hangs! quit outsourcing to india, seriously!

[bridgman]

Those are *really* wierd looking mtrrs... don't know if they're the problem though. Can you pastebin a copy of your xorg log somewhere so we can see if the driver is complaining about anything ?

[mega_mike]

bleh

My Ubuntu 8.04 system in a Dell Inspiron 6400 with an ATI Mobility x1400 still has the same issue I have had since the initial catalyst driver release. When the hell is ATI going to address stability in their driver damnit!

Performance seems to be slightly better but my system still grinds to a halt after roughly 6 hours of usage (compiz enabled). I can't restart the X server at that point without it hard locking my machine (the only way to reboot is to issue direct kernel commands alt+prntscn+s then al+printscn+b).

[grantek]

Those are *really* wierd looking mtrrs... don't know if they're the problem though. Can you pastebin a copy of your xorg log somewhere so we can see if the driver is complaining about anything ?

pastebin.com/me640986 - dmesg
pastebin.com/m57b42621 - Xorg.0.log
pastebin.com/m56e4491c - xorg.conf - pretty standard I think

I'm mildly worried about the memory ranges in dmesg, if the card wants a single block from 0xd0000000-0xefffffff and dmesg shows 0xe0000000-0xefffffff is unavailable, it could be artificially limiting me to 256MB.