Announcement

Collapse
No announcement yet.

what driver should i use for ati 3870?

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

  • muzzymurray
    replied
    Originally posted by Raven3x7 View Post
    Yep
    Yeah, its weird that some peoples work. Although I would much prefer to use RadeonHD, I think I will try with 7.12 when they are released on the 18th.

    Leave a comment:


  • Raven3x7
    replied
    Originally posted by muzzymurray View Post
    Really? With a 3870? The 7.11 drivers do not recognise my chipset.
    Code:
    (--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x9501) rev 0, Mem @ 0xe0000000/28, 0xf5000000/16, I/O @ 0xb000/8
    (II) Addressable bus resource ranges are
    Yep
    Code:
     Primary Device is: PCI 01:00:0
    (II) ATI Proprietary Linux Driver Version Identifier:8.43.2
    (II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.433                    
    (II) ATI Proprietary Linux Driver Build Date: Nov  9 2007 21:19:16
    (--) Assigning device section with no busID to primary device
    (--) Chipset Supported AMD Graphics Processor (0x9501) found
    (II) AMD Video driver is running on a device belonging to a group targeted for this release
    (II) AMD Video driver is signed
    Code:
    (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: "RV670" (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 0xfdbe0000
    (==) fglrx(0): ROM-BIOS at 0x000c0000
    So maybe it just needs the pci ids and the arch devs added them?
    On a side note, just like with my x1800xt its only seeing half the ram
    Code:
    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)

    Leave a comment:


  • Michael
    replied
    My message to the RadeonHD devs:

    Hello,

    Have you guys got your hands on the Radeon HD 3850 or 3870 parts yet?

    I added both IDs to rhd_id.c with their respective PCI IDs, but it's failing on TMDSBVoltageControl. Do you know the appropriate values to use then for the 3850 and/or 3870 inside the RV6xxTMDSBMacro array?

    Best,
    Michael

    The fglrx 7.11 isn't good with the 3850 test I did, didn't swap in the 3870 for fglrx yet.

    Leave a comment:


  • muzzymurray
    replied
    Originally posted by Raven3x7 View Post
    well 7.11 works fine for me.
    Really? With a 3870? The 7.11 drivers do not recognise my chipset.
    Code:
    (--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x9501) rev 0, Mem @ 0xe0000000/28, 0xf5000000/16, I/O @ 0xb000/8
    (II) Addressable bus resource ranges are

    Leave a comment:


  • Raven3x7
    replied
    well 7.11 works fine for me.

    Leave a comment:


  • muzzymurray
    replied
    @pccp

    I have the same card and am in the same boat at the moment. You probably made the same ill informed decision as me: "Well ATI are talking alot about opening their video cards, the new series must be supported well"

    It is a little annoying that a company that is talking about open source is releasing cards when drivers are non existent for Linux. I'd settle for being able to run my screen at its native res at the moment.

    Lets hope they get it right in the long run. I will let you know if and when I get a working proprietary or open source driver.

    Cheers

    Leave a comment:


  • Dandel
    replied
    hmm... it would be in their or somewhere in the dmesg logs, however one gets in to that.

    Leave a comment:


  • teroedni
    replied
    Yea im considering that
    But then i would need to install all over again.

    my wine version is wine-0.9.49

    But how will the xorg.0.log file help ?
    After what i known it only shows the startup and intilisation of the graphic cards. I dont think it shows any error message later on when fglrx hard locks the system:/
    Last edited by teroedni; 09 December 2007, 05:47 PM.

    Leave a comment:


  • Dandel
    replied
    I'd upgrade to ubuntu 7.10, however i was refering to the xorg.0.log or whatever the last file was... back it up before you reboot if you can... and as for wine... which version.

    Leave a comment:


  • teroedni
    replied
    1. No 22 1680x1050

    2.Linux mint old version (based on ubuntu7.04)

    3.Wow trough .wine

    4

    b: You mean the Xorg.o.log file?
    that only shows the startup, noy anything consider the crash?.

    or do you mean another log file
    This is whhat i got in my var/log folder
    teroedni@brisbane:/var/log$ dir
    acpid cups gdm syslog.0
    acpid.1.gz daemon.log installer syslog.1.gz
    acpid.2.gz daemon.log.0 kern.log syslog.2.gz
    acpid.3.gz daemon.log.1.gz kern.log.0 syslog.3.gz
    acpid.4.gz daemon.log.2.gz kern.log.1.gz syslog.4.gz
    apport.log daemon.log.3.gz kern.log.2.gz syslog.5.gz
    apport.log.1 debug kern.log.3.gz syslog.6.gz
    apport.log.2.gz debug.0 lastlog udev
    apport.log.3.gz debug.1.gz lpr.log unattended-upgrades
    apport.log.4.gz debug.2.gz mail.err user.log
    apport.log.5.gz debug.3.gz mail.info user.log.0
    apport.log.6.gz dmesg mail.log user.log.1.gz
    apport.log.7.gz dmesg.0 mail.warn user.log.2.gz
    aptitude dmesg.1.gz messages user.log.3.gz
    aptitude.1.gz dmesg.2.gz messages.0 uucp.log
    auth.log dmesg.3.gz messages.1.gz wtmp
    auth.log.0 dmesg.4.gz messages.2.gz wtmp.1
    auth.log.1.gz dpkg.log messages.3.gz wvdialconf.log
    auth.log.2.gz dpkg.log.1 news Xorg.0.log
    auth.log.3.gz dpkg.log.2.gz pycentral.log Xorg.0.log.old
    bittorrent dpkg.log.3.gz samba Xorg.1.log
    boot envy-installer.log scrollkeeper.log Xorg.1.log.old
    bootstrap.log faillog scrollkeeper.log.1
    btmp fontconfig.log scrollkeeper.log.2
    btmp.1 fsck syslog

    Leave a comment:

Working...
X