Jump to content
Tredvesone

Is my XFX Radeon HD 6870 2GB GDDR5 framebuffer ok?

2 posts in this topic

Recommended Posts

Hi.

 

I just installed a XFX Radeon HD 6870 2GB GDDR5 ("Dual Fan -DD" edition), but I'm worried my Duckweed framebuffer is not ok. Could someone verify or is everything ok?

I can play chess and DVD player.

 

Cinebench score is only 36.10. That is too low... what to do?

 

OS X Lion 10.7.2

 

Chameleon version:

Chimera 1.7

 

org.chameleon.Boot.plist:

<key>GraphicsEnabler</key>

<string>Yes</string>

 

<key>AtiConfig</key>

<string>Duckweed</string>

 

ioreg | grep ATY

+-o ATY,Duckweed@0 <class AtiFbStub, id 0x100000336, registered, matched, active, busy 0 (697 ms), retain 7>

+-o ATY,Duckweed@1 <class AtiFbStub, id 0x100000337, registered, matched, active, busy 0 (7 ms), retain 7>

+-o ATY,Duckweed@2 <class AtiFbStub, id 0x100000338, registered, matched, active, busy 0 (8 ms), retain 7>

+-o ATY,Duckweed@3 <class AtiFbStub, id 0x100000339, registered, matched, active, busy 0 (6 ms), retain 7>

 

bdmesg

Using PCI-Root-UID value: 1

Framebuffer @0xE0000000 MMIO @0xFBAC0000 I/O Port @0x0000BE00 ROM Addr @0x00000000

ATI card POSTed, reading VBIOS from legacy space

(AtiConfig) Framebuffer set to: Duckweed

Nr of ports set to framebuffer's default: 4

ATI Barts AMD Radeon HD 6870 Series 2048MB (Duckweed) [1002:6738] (subsys [1682:310a]):: PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)

 

I noticed that my 1682:310a is a different from others xfx cards. Probably the 2GB?

 

Btw: The fan is working all the time, not a full speed, but not like it does in bios/boot area. Then its pretty darn silent. In Linux Mint as well. When OS X Lion login screen appears the fan kicks in again, if you catch my drift. So there is a problem in OS X and fan control.

 

Thank you in advance :)

Share this post


Link to post
Share on other sites
Advertisement

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      As I see many novices in the forum ask "How to make my Radeon working? I have bad resolution, no QE/CI...." and so on. They come to the section and have no find an answer here because all Radeons are different and they don't know where else they read about this.
      I want to explain all steps needed for launching the Radeon family of videocards.
       
      Bootloader.
      I will speak about Clover because I maintain this bootloader to know recent hardware and modern OSX. Not sure if you will have the same result with other bootloaders. I am carefully checking the injecting of ATI card and correcting it times to times. I am also accessible for bug reports.
       
      OSX version.
      Older card require older system, newer cards require new system.
      ATIRadeon9000 is possible to launch under Tiger.
      ATIRadeonMobilityX1400 requires 10.5-10.6. See RadeonHD topic.
      As I see RadeonHD3xxx was successful only in 10.5
      For new AMDRadeonHD7xxx there must be 10.8.3+ system.
       
      DeviceID.
      This must be the first question before asking about the card.
      You may know the device-id from Windows->DeviceManger->VideoCard.properties->compatibleIDs
      You may boot into system in safe mode (key -x) and see system profiler
       
      And you may boot into Clover GUI, press F2 and get preboot.log. Find here something like
      2:709 0:000 PCI (00|01:00.00) : 1002 6758 class=030000 2:709 0:000 Found Radeon model=AMD Radeon HD 6670 Series It means my DeviceID=6758 (these are hex numbers)
      Then you must check that Apple's drivers support your DeviceID. If not then add it!
      For example HD7850 has DeviceID=6819. If we look into ATI7000Controller (AMD7000... in new systems) we find 6818 here but no 6819!
       
       
      I show you how to do this with terminal commands. Launch /Application/Utilities/Terminal.app. Type in opened window:
       
      cp /System/Library/Extensions/ATI7000Controller.kext/Contents/Info.plist ~/Desktop So you get a copy of the Info.plist on Desktop. Edit it with TextEdit. Change 68181002 -> 68191002.
      Don't edit this file directly in the system folder! 
      Then copy back by terminal. Don't use finder to copy kexts! They will have wrong permissions in this case.
      sudo cp ~/Desktop/Info.plist /System/Library/Extensions/ATI7000Controller.kext/Contents/ sudo rm -r -v /System/Library/Caches/com.apple.kext.caches/* Second command make sure next reboot the kext will use your edited info.plist.
      The same operation you must do with a kext AMDRadeonAccelerator or ATIRadeonX2000 or other one. Check all candidates if they contain such list of possible IDs and choose closest to you.
       
      FakeID
      Since Clover revision 1971+ you may just inject new DeviceID into DSDT instead of correcting kexts. See instruction here.
       
      GraphicsEnabler or Injector
      OSX needs to know some properties (Model name, Family, etc...) that must be somehow injected at boot time. Yes, also real Macs got DeviceProperties string from firmware.
      Alternatives:
      1. Set InjectATI=Yes in Clover (same as GE=y in Chameleon).
      2. Use custom string made with gfxutil. For whom who knows.
      3. Write _DSM into DSDT. You should know what to write.
      4. Use some kext like ATY_init.kext or Natit.kext. If you are sure that the kext is for your card namely.
      I want to say that all this methods make the same thing. Differencies in their tuning.
      The Clover do this automatically for most known cards at this moment.
       
      Connectors.
      As you may see to start HD5000-7000 some strange names used: Pithecia, Orangutan, Elodea... What are they?
      They are configs for framebuffer. Predefined configs how connectors are solded for cards used in real Macs. Strange but these configs rear coincide with PC card. Usually gurus make advice "choose a framebuffer that most appropriate for your card". The chances 1:10. In most cases you may find a FB name that gives you main monitor working. Or nothing at all.
      Great respect to bcc9 who gives us a method to correct one of config to be exactly for you. See here.
      My retelling for Clover is here
      Success example in the thread in posts 44-52
       
      Radeon Mobility
      I tested Clover's methods with two users having Mobility Radeon HD5470 and HD5650M. We found that full memory and QE/CI will be achieved if we set in Clover's config
      LoadVBios=Yes
      even thou no file with bios is provided. This is the key to make Radeon Mobility working!
      Other problem is bad gradients or artifacts. For this case Clover accept the key
      InjectEDID=Yes
      and sometimes you also need to inject CustomEDID.
      See Clover instructions for details.
       
      And my results.
      Gigabyte Radeon HD6670
      <key>Graphics</key> <dict> <key>GraphicsInjector</key> <true/> <key>InjectEDID</key> <true/> <key>FBName</key> <string>Ipomoea</string> <key>LoadVBios</key> <false/> <key>VideoPorts</key> <integer>3</integer> <key>PatchVBios</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>6000</string> <key>ATIConnectorsData</key> <string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string> <key>ATIConnectorsPatch</key> <string>040000000403000000010000100001061000000010000000000100000000000100080000040200000001000012040403</string> VTX Radeon HD5570
      <key>Graphics</key> <dict> <key>PatchVBios</key> <false/> <key>FBName</key> <string>Baboon</string> <key>VideoPorts</key> <string>3</string> <key>GraphicsInjector</key> <string>Yes</string> <key>LoadVBios</key> <string>No</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>5000</string> <key>ATIConnectorsData</key> <string>040000001400000000010000010201030008000000020000007100002205020110000000100000000001000000100002</string> <key>AppleRTC</key> <true/> <key>ATIConnectorsPatch</key> <string>040000001400000000010000010001040008000000020000007100002200020510000000100000000001000000000002</string> <key>AsusAICPUPM</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Name</key> <string>AppleAHCIPort</string> <key>Find</key> <data>RXh0ZXJuYWw=</data> <key>Replace</key> <data>SW50ZXJuYWw=</data> </dict> </array> </dict> See PatchVBios=No
      for this card "yes" leads to black screen. Use with precautions.
       
      A sample for Radeon R7 240
       
      UPDATE for ElCapitan.
      It seems has more problems. My HD6670 is not working in ElCapitan OOB unlike Mavericks.
      I had to set FakeID=0x67401002 as correspond to real iMac12,2 and set this model in SMBIOS section.
      It related to GraphicsPM or GraphicsControl.
      Look these kexts to decide what you can do for your configuration.
       
      HighSierra requires change these kexts by version from Sierra 10.12.6
      for Radeon HD6xxx
      AMDRadeonX3000.kext AMDRadeonX3000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .  for Radeon HD7xxx and up AMDRadeonX4000.kext AMDRadeonX4000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .    Black screen after wake problem resolved by follow method radeon_bios_decode.0.2.zip
      ati-personality.pl.0.15.zip
      ati-personality.pl.0.15a.zip
    • By DerNuntius
      Hi,
       
      Finally I finished the installation of 10.14.6 on my Dell E5440. Everything works just fine, but HDMI will not work. Every time I plug it in, it causes a grey screen on my laptop monitor. Also on boot up. I attached my EFI Folder, maybe someone can help me. I searched a bit and read something about Azul Framebuffer Kext.
       
      Thank you for helping.
      Greedings,
      Hugo
       
       
      CLOVER.zip
    • By IDON-NO
      Hello everyone 
      I decided to open this thread for Intel HD Graphics 530 SKYLAKE 
      This GPU seems to be problematic with Hackintosh , specially if you intended to use it with 4K monitor or Multi-Monitor .
      Simply after you followed all the right instructions to patch framebuffer using Lilu.kext and WEG as described here in @headkaze 
       
      "Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default) " 
       
      Simply after Apple logo boot go to black screen 
      I can't use platform-id : 0x19120000 as suggested is a default 
      I am sure Bios settings is correct , Clover is correct , Kexts , ...etc 
      But end always with Black screen 
      I've seen a lot of people have the same issue when googling it , but no solutions at all 
      I want to know what is the reason that cause the black screen ?!! 
      Is 0x19120000 not default ?
      @vit9696 WEG issue ?
      Something else? @PMheart @vandroiy2012 
       
      FYI : using  Displayport 1.2 , using HDMI = Black screen 
       
      Only solution is using Platform-ID : 0x193b0005 
      Now you can boot normally but Monitor in this case seen as TV NTSC 
      Is 0x193b0005 is the default Platform ID ?  
      Can someone help us please ?
      Thanks
       
       
       
    • By nysander
      Hello Guys,
       
      I am looking for tips on how can I patch my FrameBuffer to be able to use mobile ig-platform-id for HD 4600 Intel Graphics. ATM the only way to have recognized full resolution and memory (1,5GB) is to use 0x0d220008 desktop Haswell profile.
       
      Problem is that on this profile backlight patches do not work. I get blank screen during boot instead of apple logo.
       
      As RehabMan suggested in my debug topic, this is possible because of the fact that my laptop uses eDP to connect LCD, and that eDP is not fully supported. But as far as I've found T440 laptop's LCD is also connected via eDP and they work with backlight. 
       
      How can I debug / patch such situation? 
       
      I am new to hackintosh knowledge but want to make my laptop work so any suggestions and help is much appreciated. 
×