Announcement

Collapse
No announcement yet.

ATI Radeon HD 5850/5870 On Linux?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Otherwise seems nice, but what the heck is with the near-200W power draw for a single card? 27W idle? Damn, that's what my current card uses at max

    Comment


    • #32
      Originally posted by Joe Sixpack View Post
      It may not be popular, but I don't really care because it's the honest truth...

      Have you even read the last few phoronix.com summaries for Linux Catalyst releases? They're less about actually news and reporting, and more about negative slanting ans fanning the flames. Absolutely no mention of what's added and what's fixed - just a bunch of complaining about Xvba when truthfully most non-experts don't even know what the hell it is. No balance whatsoever.

      With the lack of journalistic integrity we've seen as of late in regards to AMD/ATI, I would suspect this would be the last website to get a tech preview. I mean seriously, in the end you'll only highlight the bad and gloss over everything that's good.
      I've been on the nvidia side for quite awhile and I have to say I kinda agree with phoronix. As a nvidia user under linux I'm used to compiz, google earth working, full screen video playback. Even on fairly old hardware mid range from a few generations ago. In fact similar even works on the rather slow intel embedded chipsets. I bought a new quad core phenom, with the radeon 3300 (785g I believe) only to find that compiz, google earth, and full screen video playback do not work well. ATI seems to be trying hard, publishing tons of docs, some support for the opensource folks. But still seems lacking with a decent driver (binary or otherwise).

      Anyone out there there with a ati 4770, how does it work with google earth (full screen), video playback (full screen) and compiz?

      Comment


      • #33
        well, patch X and see almost all problems go away...

        Comment


        • #34
          Originally posted by BillBroadley View Post
          Anyone out there there with a ati 4770, how does it work with google earth (full screen), video playback (full screen) and compiz?
          From what I hear on IRC, using bleeding edge code, the 4xxx series cards are running Compiz and playing Nexuiz just fine, so I assume Google Earth would be fine too. Don't know about video playback.

          Comment


          • #35
            Originally posted by BillBroadley View Post
            I've been on the nvidia side for quite awhile and I have to say I kinda agree with phoronix. As a nvidia user under linux I'm used to compiz, google earth working, full screen video playback. Even on fairly old hardware mid range from a few generations ago. In fact similar even works on the rather slow intel embedded chipsets. I bought a new quad core phenom, with the radeon 3300 (785g I believe) only to find that compiz, google earth, and full screen video playback do not work well. ATI seems to be trying hard, publishing tons of docs, some support for the opensource folks. But still seems lacking with a decent driver (binary or otherwise).

            Anyone out there there with a ati 4770, how does it work with google earth (full screen), video playback (full screen) and compiz?
            I understand where you are coming from. It's a slippery slope though. There's a very fine line between reporting, telling it how it is, and ranting. If you're running some personal blog then fine - rant all day and night. But if you are considered to be the authority on linux hardware, then a little neutrality is expected.

            I guess I dodged the bullet because I'm still using the old HD 3870. Compiz used to be abysmal, but it improved greatly with Catalyst 9.2 - 9.6. Catalyst 9.8 seems to have fixed whatever that was causing the random hard locks (someone else mentioned it in the forums), and I've been able to play Nexuiz since Catalyst 8.7.

            Comment


            • #36
              Originally posted by bridgman View Post
              My guess was "a couple of weeks for modesetting and a couple of months for acceleration".

              Alex is going to be out at XDC next week so I'm revising that to "a few weeks for modesetting..."

              We haven't started the work though, so these really are guesses for now.
              How much of a deviation is this generation in terms of hardware interface?

              Anything we can help with? Docs available?

              Comment


              • #37
                Originally posted by Joe Sixpack View Post
                Nice try.

                The topic was about AMD, and how they didn't provide phoronix with a sample. Not about Linux as a whole, not about phoronix as a whole. If you don't see it, no biggie - but that's an invalid comparison and a rather childish rolling of the eyes.
                Why provide a sample if there are no drivers yet? I am getting my 5850 in a couple days so I can check if the 9.10 beta drivers work, but I have my doubts. If you have read anything from the forums and reviews the drivers on windows seem a bit rough right now, so its understandable that they don't have working drivers for Linux yet. Also I am not implying that the windows driver team also works on the Linux driver, but that it might require more work than the R700 series.

                Comment


                • #38
                  if you try the ubuntu-pre-relase of the 9.10 drivers, they might work - but you also might get a 'hardware not supported' watermark in the right bottom corner

                  imho worth a try

                  Comment


                  • #39
                    Yes, I agree.

                    On my desktop 4850, I have had some noticeable improvements in performance, and bugfixes since I got it a year ago.

                    Where are the benchmarks comparing the different ATI divers on each new release?

                    I used to look at the articles, and I'd get a good idea of what the new driver bring. Now, I have to read trough a hundred pages of forum posts to get an idea.

                    Comment


                    • #40
                      Originally posted by energyman View Post
                      if you try the ubuntu-pre-relase of the 9.10 drivers, they might work - but you also might get a 'hardware not supported' watermark in the right bottom corner

                      imho worth a try
                      I'm really curious as to whether the 9.10 drivers support the 5800 series or not (I know *one* of you guys has to have bought one already, so speak up! ). I want to buy an ATi card in the coming weeks, but I don't know if I should get a 4850, a 4870, or a 5850...

                      Comment


                      • #41
                        have you read the test on anandtech? The 5850 is blazing fast. There is no reason to buy a 4870 - except the prize...

                        Comment


                        • #42
                          I'm typing this from a Debian Lenny/Sid amd64 box (AMD X4 955BE, 8GB PC2-8500, MSI K9A2 Platinum) with a brand new Radeon 5870 in it. I've got the "Unsupported hardware" banner at the bottom right, but I've not run into any problems so far. I've been running Heroes of Newerth at 1680x1050, vsync off, with 8xAA and 32xAF on at >70FPS. X-Plane runs very nicely at 1680x1050 extreme res with 4xAA and 4xAF (not nudged it any higher yet), ETQW runs very nicely with 16xAF (>60FPS constant). This is with Catalyst 9.9.
                          Last edited by GotenXiao; 10-02-2009, 07:12 PM.

                          Comment


                          • #43
                            32xAF? Since when do ATI cards perform 32x anisotropic filtering?
                            Last edited by tuxdriver; 10-02-2009, 07:14 PM.

                            Comment


                            • #44
                              Originally posted by GotenXiao View Post
                              I'm typing this from a Debian Lenny/Sid amd64 box (AMD X4 955BE, 8GB PC2-8500, MSI K9A2 Platinum) with a brand new Radeon 5870 in it. I've got the "Unsupported hardware" banner at the bottom right, but I've not run into any problems so far. I've been running Heroes of Newerth at 1680x1050, vsync off, with 8xAA and 32xAF on at >70FPS. X-Plane runs very nicely at 1680x1050 extreme res with 4xAA and 4xAF (not nudged it any higher yet), ETQW runs very nicely with 16xAF (>60FPS constant). This is with Catalyst 9.9.
                              The AIB vendor (which one BTW?) has the option of including a driver on the CD. Did you check?

                              The hardware became "supported" between the final packaging of Catalyst 9.9 and the next release. There may some bugs that you may still encounter that were resolved prior to the final release, but the 9.9 catalyst will be 95% "there". Beyond a few small corner cases, the driver should be representative of the performance of the card.

                              Regards,

                              Matthew

                              Comment


                              • #45
                                Originally posted by tuxdriver View Post
                                32xAF? Since when do ATI cards perform 32x anisotropic filtering?
                                Since the 5870, apparently

                                Originally posted by mtippett View Post
                                The AIB vendor (which one BTW?) has the option of including a driver on the CD. Did you check?

                                The hardware became "supported" between the final packaging of Catalyst 9.9 and the next release. There may some bugs that you may still encounter that were resolved prior to the final release, but the 9.9 catalyst will be 95% "there". Beyond a few small corner cases, the driver should be representative of the performance of the card.

                                Regards,

                                Matthew
                                XFX - I did check, but they've only got Windows 2k/XP and Vista/7 drivers on the CD.

                                I believe I encountered one of the bugs - this happened after I went to bed, and I've not been able to get an X server running this morning (without rebooting).

                                This is from kern.log:
                                Code:
                                Oct  3 02:45:06 nightstalker kernel: [14496.680795] [fglrx:firegl_cail_init] *ERROR* CAIL: CAIL_ASICSetup failed, error 1
                                Oct  3 02:45:06 nightstalker kernel: [14496.680799] [fglrx:hal_init_asic] *ERROR* Failed to initialize ASIC.
                                Oct  3 02:45:06 nightstalker kernel: [14496.680967] BUG: unable to handle kernel paging request at ffffc200121898f0
                                Oct  3 02:45:06 nightstalker kernel: [14496.680970] IP: [<ffffffffa04b5815>] halReadReg32+0x5/0x10 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681030] PGD 23fc6c067 PUD 23fc6d067 PMD 23cbcd067 PTE 0
                                Oct  3 02:45:06 nightstalker kernel: [14496.681033] Oops: 0000 [#1] SMP
                                Oct  3 02:45:06 nightstalker kernel: [14496.681035] last sysfs file: /sys/devices/pci0000:00/0000:00:14.4/0000:04:00.0/resource
                                Oct  3 02:45:06 nightstalker kernel: [14496.681037] CPU 3
                                Oct  3 02:45:06 nightstalker kernel: [14496.681038] Modules linked in: fuse snd_seq_dummy usb_storage udf joydev fglrx(P) binfmt_misc rfcomm l2cap bluetooth battery ppdev parport_pc lp parport cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative nf_conntrack_ipv6 ip6table_filter ip6_tables xt_tcpudp xt_state iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish des_generic cbc cryptd aes_x86_64 aes_generic xcbc rmd160 sha256_generic sha1_generic hmac crypto_null af_key nls_utf8 nls_cp437 vfat fat nls_base ext2 dm_crypt f71882fg firewire_sbp2 loop snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device usbhid snd hid i2c_piix4 wmi i2c_core processor button soundcore serio_raw psmouse pcspkr snd_page_alloc evdev ext3 jbd mbcache dm_mir
                                Oct  3 02:45:06 nightstalker kernel: or dm_region_hash dm_log dm_snapshot dm_mod ide_cd_mod cdrom ide_pci_generic sd_mod crc_t10dif atiixp ide_core ahci ata_generic libata firewire_ohci firewire_core crc_itu_t scsi_mod ohci_hcd floppy ehci_hcd r8169 mii thermal fan thermal_sys [last unloaded: fuse]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681093] Pid: 7907, comm: Xorg Tainted: P           2.6.30-1-amd64 #1 MS-7376
                                Oct  3 02:45:06 nightstalker kernel: [14496.681095] RIP: 0010:[<ffffffffa04b5815>]  [<ffffffffa04b5815>] halReadReg32+0x5/0x10 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681136] RSP: 0018:ffff8801d3575d20  EFLAGS: 00010216
                                Oct  3 02:45:06 nightstalker kernel: [14496.681137] RAX: ffffffffa0614ac0 RBX: ffff88023a4882c0 RCX: 0000000000000006
                                Oct  3 02:45:06 nightstalker kernel: [14496.681139] RDX: 00000000000098f0 RSI: 00000000000098f0 RDI: ffffc20012180000
                                Oct  3 02:45:06 nightstalker kernel: [14496.681140] RBP: ffff88021f8f8000 R08: 0000000000000000 R09: ffffffffa057d640
                                Oct  3 02:45:06 nightstalker kernel: [14496.681142] R10: 0000000000000009 R11: 000000003e920000 R12: 00000000017c9720
                                Oct  3 02:45:06 nightstalker kernel: [14496.681143] R13: ffff8801d3575dc8 R14: 00000000c0406466 R15: ffff8801fc8f33c0
                                Oct  3 02:45:06 nightstalker kernel: [14496.681145] FS:  00007fe0b8c72790(0000) GS:ffff880028082000(0000) knlGS:00000000f7df26c0
                                Oct  3 02:45:06 nightstalker kernel: [14496.681146] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
                                Oct  3 02:45:06 nightstalker kernel: [14496.681148] CR2: ffffc200121898f0 CR3: 000000020b12c000 CR4: 00000000000006e0
                                Oct  3 02:45:06 nightstalker kernel: [14496.681149] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
                                Oct  3 02:45:06 nightstalker kernel: [14496.681151] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
                                Oct  3 02:45:06 nightstalker kernel: [14496.681152] Process Xorg (pid: 7907, threadinfo ffff8801d3574000, task ffff8801dbdc8b30)
                                Oct  3 02:45:06 nightstalker kernel: [14496.681154] Stack:
                                Oct  3 02:45:06 nightstalker kernel: [14496.681155]  ffffffffa04b5f32 ffff88021f8f8000 ffffffffa04b4aaf ffff8801d3575d78
                                Oct  3 02:45:06 nightstalker kernel: [14496.681157]  ffffffffa049b9f6 ffff8801d3575de8 ffff880231f2ad58 ffff88021c174c80
                                Oct  3 02:45:06 nightstalker kernel: [14496.681159]  0000000000000001 ffff8801d3575ed8 ffffffff802939a8 ffff88021f8f8000
                                Oct  3 02:45:06 nightstalker kernel: [14496.681162] Call Trace:
                                Oct  3 02:45:06 nightstalker kernel: [14496.681164]  [<ffffffffa04b5f32>] ? __get_num_hzmem_pipes_r7xx+0x12/0x20 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681204]  [<ffffffffa04b4aaf>] ? hal_get_num_hzmem_pipes+0x1f/0x80 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681244]  [<ffffffffa049b9f6>] ? firegl_init_pcie+0xf6/0x3f0 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681282]  [<ffffffff802939a8>] ? generic_file_aio_write+0x6f/0xc4
                                Oct  3 02:45:06 nightstalker kernel: [14496.681288]  [<ffffffffa015f384>] ? ext3_file_write+0x16/0x96 [ext3]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681296]  [<ffffffffa049b900>] ? firegl_init_pcie+0x0/0x3f0 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681334]  [<ffffffffa049755a>] ? firegl_ioctl+0x1ea/0x250 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681372]  [<ffffffff802cc04b>] ? vfs_ioctl+0x56/0x6c
                                Oct  3 02:45:06 nightstalker kernel: [14496.681375]  [<ffffffff802cc48c>] ? do_vfs_ioctl+0x42b/0x464
                                Oct  3 02:45:06 nightstalker kernel: [14496.681377]  [<ffffffff802c13c5>] ? vfs_write+0xcd/0x102
                                Oct  3 02:45:06 nightstalker kernel: [14496.681380]  [<ffffffff802cc516>] ? sys_ioctl+0x51/0x70
                                Oct  3 02:45:06 nightstalker kernel: [14496.681382]  [<ffffffff8020fa42>] ? system_call_fastpath+0x16/0x1b
                                Oct  3 02:45:06 nightstalker kernel: [14496.681385] Code: 00 00 48 89 8f f8 03 00 00 48 85 c0 74 0d 48 83 f8 ff 74 07 48 89 87 f8 03 00 00 b8 01 00 00 00 c3 66 66 90 66 90 c1 e6 02 89 f2 <8b> 04 3a c3 66 66 66 90 66 66 90 c1 e6 02 89 f0 89 14 38 c3 66
                                Oct  3 02:45:06 nightstalker kernel: [14496.681402] RIP  [<ffffffffa04b5815>] halReadReg32+0x5/0x10 [fglrx]
                                Oct  3 02:45:06 nightstalker kernel: [14496.681441]  RSP <ffff8801d3575d20>
                                Oct  3 02:45:06 nightstalker kernel: [14496.681442] CR2: ffffc200121898f0
                                Oct  3 02:45:06 nightstalker kernel: [14496.681444] ---[ end trace bd5cd2ab2dcbaae5 ]---
                                Oct  3 02:45:06 nightstalker kernel: [14496.682163] [fglrx:firegl_release] *ERROR* device busy: 1 0
                                Oct  3 02:45:06 nightstalker kernel: [14496.682165] [fglrx] release failed with code -EBUSY
                                This is from Xorg.0.log (this morning after trying to restart kdm):
                                Code:
                                (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: 12.11
                                (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
                                (II) fglrx(0): VESA VBE OEM Product: CYPRESS
                                (II) fglrx(0): VESA VBE OEM Product Rev: 01.00
                                (EE) fglrx(0): CAIL: CAIL_ASICSetup failed, error 1
                                (EE) fglrx(0): GetBIOSParameter failed
                                (EE) fglrx(0): PreInitAdatper failed
                                (EE) fglrx(0): PreInit failed
                                (II) fglrx(0): === [atiddxPreInit] === end
                                (EE) fglrx(0): PPLIB: PPLIB is not initialized!.
                                (EE) fglrx(0): PPLIB: swlPPLibNotifyEventToPPLib() failed!
                                (EE) fglrx(0):        ulEventType = 0000000c, ulEventData = 00000001
                                
                                Backtrace:
                                0: /usr/bin/X(xorg_backtrace+0x26) [0x4ee256]
                                1: /usr/bin/X(xf86SigHandler+0x39) [0x4840b9]
                                2: /lib/libc.so.6 [0x7f3d824c0fc0]
                                3: /usr/lib/xorg/modules/drivers//fglrx_drv.so(swlDalHelperClose+0x87) [0x7f3d80a918a7]
                                4: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxFreeScreen+0x129) [0x7f3d80a6d589]
                                5: /usr/bin/X(xf86DeleteScreen+0x7e) [0x480e5e]
                                6: /usr/bin/X(InitOutput+0xdda) [0x46de3a]
                                7: /usr/bin/X(main+0x200) [0x4331d0]
                                8: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f3d824ada8d]
                                9: /usr/bin/X [0x432819]
                                Edit: came back up fine after a reboot. I also reset the amdpcsdb to the default file to make sure there were no lingering entries from my 3870 crossfire setup.
                                Last edited by GotenXiao; 10-03-2009, 07:17 AM.

                                Comment

                                Working...
                                X