Jump to content

Search the Community: Showing results for tags 'Framebuffer'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 10 results

  1. 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
  2. Rampage Dev

    Patched Framebuffer Repository

    about: This is a Repository for ATI and AMD patched Framebuffers. Here you will find a complete list of successfully patched framebuffers for ATI and AMD Graphics Cards. This is not a support page so do not post questions on this page. Start a new topic if you have questions. Thank you for your cooperation. Framebuffer Editing Guides: BCC9′s post that can be found here Alexander Martinez’s post that can be found here Mucha’s post that can be found here Posting Guidelines: The following are the posting guidelines for this page. Failure to follow set guidelines will mean that the patched framebuffer will not be posted on the first post. Thank you for your cooperation. Graphics Card Model: Graphics Card Manufacture Name: Graphics Card Manufacture Part Number: Fixed by: Patched Framebuffer:
  3. Hello everyone! OK I know this is a relatively ancient system, but here it is: I was having some free time in the summer and thought of giving my old Toshiba Satellite A300 (PSAGCE) a second try in installing Mac OS X El Capitan with Clover. Generally, I think that this is a good hackintosh-candidate laptop, apart from its Mobility Radeon HD 3650 GPU (DevID 0x9591). So, I tried to follow-up guides from bcc9, mucha, slice and vlada on ATI kext patching to enable the internal LVDS display and see what will happen. I started with the two scripts decoding the VGA Bios. My results were the following: Radeon_bios_decode: ATOM BIOS Rom: SubsystemVendorID: 0x1179 SubsystemID: 0xff1c IOBaseAddress: 0x5000 Filename: 28109C.bin BIOS Bootup Message: Tosh_IEC_Potomac_M86_DDR2 M86 GDDR2_16Mx16 128bit 256MB 600e/500m PCI ID: 1002:9591 Connector at index 0 Type [@offset 45056]: VGA (1) Encoder [@offset 45060]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 45146]: 0x90, OSX senseid: 0x1 Connector at index 1 Type [@offset 45066]: LVDS (7) Encoder [@offset 45070]: INTERNAL_KLDSCP_LVTMA (0x1f) i2cid [@offset 45169]: 0x14, OSX senseid: 0x5 Connector at index 2 Type [@offset 45076]: HDMI-A (11) Encoder [@offset 45080]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 45192]: 0x91, OSX senseid: 0x2 Connector at index 3 Type [@offset 45086]: 9 pin DIN (9) Encoder [@offset 45090]: INTERNAL_KLDSCP_DAC2 (0x16) Redsock_bios_decode: 28109C.bin : Tosh_IEC_Potomac_M86_DDR2 M86 GDDR2_16Mx16 128bit 256MB 600e/500m Subsystem Vendor ID: 1179 Subsystem ID: ff1c Object Header Structure Size: 266 Connector Object Table Offset: 46 Router Object Table Offset: 0 Encoder Object Table Offset: ce Display Path Table Offset: 10 Connector Object Id [5] which is [VGA] encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false Connector Object Id [14] which is [LVDS] encoder obj id [0x1f] which is [iNTERNAL_KLDSCP_LVTMA] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A] encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [15] which is [DIN] encoder obj id [0x16] which is [iNTERNAL_KLDSCP_DAC2] linkb: false As you can see, the Bios decode scripts point out this structure: CRTC1>DIG2>UNIPHY_KLDSKP_LVTMA>LVDS (SenseID 05 ???) CRTC2>DAC>DAC A>VGA (SenseID 01) CRTC2>DIG1>UNIPHY_A>HDMI (SenseID 02) CRTC2>DAC>DAC B>S-Video So, I tried to create a custom framebuffer string for each output: VGA 10000000100000000001000000100101 LVDS 02000000400000000901000010010205 HDMI 00080000000200000001000010000302 I injected the LVDS and VGA strings for AMD3800Controller.kext in Clover. This resulted in black screen in LVDS (nothing was showing up in system info as well), but the VGA was successfully detected and enabled. [FIRST WIN! ] I tested it with the single monitor setting in BIOS (in previous tests with Chameleon, the change in this setting gave me different results, I don’t know why, but they were weird - e.g. LVDS was showing up as a second VGA monitor with the same characteristics as the VGA monitor connected when both outputs were enabled in BIOS! Apparently, Clover uses only single monitor setting - even when LVDS+VGA setting is selected in BIOS, when Clover shows up, one monitor is off). What was strange, was the i2cid value of LVDS (0x14). Doing some search for it, I found a thread from 0xdeadbeef pointing that Radeon_Bios_Decode script may return wrong values about SenseID. http://www.insanelymac.com/forum/topic/255199-editing-personalities-in-older-ati-framebuffers-iago-friends/ Also, an old thread from YannickD about this laptop on Leopard suggests that this laptop has a LVDS which behaves like a DVI in a way (I didn’t actually understand that to be honest). So, I decided to do some trial and error tests on SenseID and ATY-ControlFlag values of the framebuffer (I was considering Transmitter and Encoder values as well, but on HD3000 these are hardwired, so it wouldn’t make much difference). Also tried to change some settings in Clover (Rename my GPU from OVGA to IGPU in DSDT and play with Load VBIOS and Inject EDID options in Clover). http://www.insanelymac.com/forum/topic/149872-ati-moblity-radeon-hd-3650-on-ideneb-13/ After some (not too many to be honest! ) tests (mainly brute-force attack on framebuffer values and change of options) I found out a setting which successfully worked on LVDS!!! My internal monitor is successfully detected and I can have the basic 2D functions for it (resolution & colour change)! [sECOND WIN! ] What did work was the default SenseID of the framebuffer (11 instead of 05) AND the ATY-ControlFlag for DVI (1402 instead of 4000 - others for DVI might work as well!) PLUS the options in Clover (Rename in IGPU for DSDT, Load VBIOS and Inject EDID, which are usual Clover settings for laptops). When tried both LVDS and VGA, both monitors were correctly detected and working! The only strange thing was that the GPU was detected as an ATI Radeon HD4330M instead of Mobility HD3650. Now the bad things… I can’t enable QE/CI acceleration, even though the DevID 9591 is included by default in ATIRadeonX2000.kext. Apparently, the kext is loaded, but returns zero values. This is the second computer that I cannot enable because of the damn ATIRadeonX2000.kext - YannickD says that after Snow Leopard Apple removed some detection routines with fixed values. Has anyone here found any clues about ATI Acceleration kexts and their values? I tested different controllers as well to see if I can get the acceleration. Results were the same for AMD2400Controller.kext, AMD2600Controller.kext and AMD3800Controller.kext, but on AMD4600Controller.kext the system crashed and rebooted before showing anything. Finally, I tested the HDMI string. The result was that the monitor was successfully detected and its properties were correctly showed up in Mac OS X, but the monitor was showing nothing (black screen). Since HD3650 can drive up to two different outputs, maybe a special switch must be enabled for the output, or might be a transmitter-encoder issue (don’t know - didn’t have the time to search more for it, as I was focused on the internal monitor, but it seems something minor). This was for the Video only - I have not tested the HDMI Audio To sum up The framebuffer working was: VGA (successfully detected and enabled - no QE/CI) 10000000100000000001000000100101 LVDS (successfully detected and enabled - DIFFERENT VALUES FROM SCRIPTS IN BOLD - no QE/CI) 02000000140200000901000010010211 HDMI (successfully detected but showed nothing in monitor - no QE/CI) 00080000000200000001000010000302 S-Video - not tested Load VBIOS, Inject EDID and Rename from OVGA to IGPU in DSDT were essential for the monitors to work. I tested these settings across different versions of Mac OS X as well, and got the same results. I can try them on Sierra as well, but I think results will be the same. Bottomline I think there is a need to do further search about framebuffer string values and their meaning. - IF they do not function for you DO NOT BLINDLY TRUST THEM - ESPECIALLY IF YOU GET BLACK SCREEN!!!!!!!!! Also, it would be very good if someone could tear down the acceleration kexts (especially the ATIRadeonX2000.kext) Anyone??? Please??? Thant’s all folks and sorry for my long thread!
  4. Hello all, So finally i have managed to edit my DSDT to allow the 7970M card to be enabled. I have the HDMI working 100%, this is great but as it is a laptop i would love to have to internal screen working. I have read every forum on the net on how to edit custom personalities but i just can't seem to understand it! My laptop is a Alienware M17X R4, the ports from the card are: Internal screen, HDMI, VGA, DP. My frame buffer is Buri. I understand i need to inject these ports into the frame buffer, i just don't understand how to do it. I have looked everywhere on how to do it, and i have found articles that physically show me how, i just don't get it. So any help would be awesome!! If you ned any dumps, extra info tell me and i will get back to you ASAP! Cheers! Personality: Buri ConnectorInfo count in decimal: 4 Disk offset in decimal 1489792 0000000 02 00 00 00 00 01 00 00 29 05 01 00 10 00 05 05 0000010 00 04 00 00 04 03 00 00 00 09 02 00 11 02 01 01 0000020 00 04 00 00 04 03 00 00 00 09 03 00 21 03 02 02 0000030 00 08 00 00 04 02 00 00 00 01 04 00 12 04 03 03 0000040 ATOM BIOS Rom: SubsystemVendorID: 0x1028 SubsystemID: 0x057b IOBaseAddress: 0x3000 Filename: C42904A1.118 BIOS Bootup Message: Wimbledon XT A01 MXM GDDR5 300e/150m 0.9V A1 PCI ID: 1002:6800 Connector at index 1 Type [@offset 45958]: LVDS (7) Encoder [@offset 45962]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 46111]: 0x94, OSX senseid: 0x5 Connector at index 2 Type [@offset 45968]: DisplayPort (10) Encoder [@offset 45972]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 46138]: 0x91, OSX senseid: 0x2 Connector at index 3 Type [@offset 45978]: HDMI-A (11) Encoder [@offset 45982]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 46165]: 0x90, OSX senseid: 0x1 Connector at index 4 Type [@offset 45988]: HDMI-A (11) Encoder [@offset 45992]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 46192]: 0x92, OSX senseid: 0x3 Connector at index 5 Type [@offset 45998]: VGA (1) Encoder [@offset 46002]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 46219]: 0x97, OSX senseid: 0x8
  5. TheHoffinator

    ATI HD6990 + 9800GTX Framebuffer issue

    Hey Guys, I've been building my own Hackintosh for a few times now. I keep struggling with my graphics card. I've got an ASUS Radeon HD6990. Which is pretty hard to get working under OS X Mountain Lion (10.8.4). I've already put in my old card as the primary card (along with the HD6990) which is an Nvidia 9800GTX. The 9800GTX works out of the box with full QE/CI. Now after a lot of tries i've managed to get my tripple screen setup working using the two outer screens on my 9800GTX and the middle screen on my HD6990. The problem here is that i can not get QE/CI working on my HD6990. I'm suspecting the following to be the issue: This is what i read on another forum: So i reproduced this. I added my device ID to the ATI6000Controller.kext. And then my middle screen turned on. Now i rebooted several times and I tried a lot of bootflags. I tried to use the following: "-v" --> All 3 screens work but the HD6990 has no QE/CI (the 9800GTX does have QE/CI) "-v GraphicsEnabler=No AtiConfig=Gibba" --> All black screens "-v AtiConfig=Gibba" --> Outer 2 screens work. Middle one (HD6990) stays black (but in OS X it does get detected when i look in the Monitor part of the System Configuration panel). "-v AtiConfig=Duckweed" --> Same as Gibba The GraphicsEnabler=No flag seems to be needed (as i've read in some other threads) for my HD6990 to have QE/CI, but when I use this my 9800GTX stops working (along with the HD6990). Please help me out. I'm kind of out of idea's how to get this monster fully working. Thanks in advance guys. EDIT: I'm using a P6T motherboard with an Core i7 920 CPU. I'm having 24GB of DDR3 @ 1600mhz. (Not sure if this matters)
  6. conorgill

    Radeon R9 270x Framebuffer/ID problem?

    Hi all! My first post here First of all, I want to say a warm hello & thank you to everyone on here! InsanelyMac has pulled me out of the s**t many a time before now! On the topic of this graphics card - I have followed Vlada's InsanelyMac post (Here) regarding this GPU & I haven't had much luck! Basically, I have the Sapphire Radeon R9 270x running on (Niresh) Mavericks 10.9.2 - it's displaying as 'Radeon HD 7xxx 2048 MB'.. I am getting full resolution, and I assume QE/CI is working as I can make a move in Chess. However, running a LuxMark benchmark I am getting a "clBuildProgram -11" error, and in Unigine Heaven I am barely scraping 10fps with the settings on Extreme I have tried installing Vlada's driver package and it just gives me nothing (Black screen on DVI, screen goes off completely on HDMI). I have tried the Terminal method too, still no luck. The only section I could not follow properly was the DSDT section - I couldn't find the "PEGP" device in MaciASL, my Graphics Card is on PC02 according to IORegistryExplorer. So I guess my question is, has my n00b level reached a new extreme & I'm missing something completely obvious? Or should everything be working? BTW, I have another Mac installation on my second HDD, so copying/restoring {censored}-ups is easy enough for me! Thanks in advance! Conor
  7. Putting this here for posterity in hopes it helps someone else (maybe just my future self). I just spent 2.5 days getting my previously working HD5750 up and running after a motherboard swap. At the same time, I upgraded to Sierra. Here's what I wish people had told me about patching your framebuffer in Clover: Patches only take effect with "WithKexts" in boot args. At least, that was the case for me. Patches don't get recognized if they cross line breaks (yes, even in a binary file there are line breaks). Thus, attempting to patch a multi-line framebuffer fails in a single patch. I believe this is why the official "ATIConnector" patch sometimes fails. If someone had spelled out those things for me, I would have been done in a few hours, not a few days. That said, here's my working configuration: Card details: Asus HD5750, 1GB vRAM, Mfr ID: 0x1002 (ATI), Device ID: 0x68BE Subsystem ID (useful for matching BIOS): 0x03381043 Card on TechPowerUp: https://www.techpowerup.com/vgabios/79262/asus-hd5750-1024-100331 Working Framebuffer (note the extra 2 bytes at the end of each line compared to most examples ... I believe this is a Sierra quirk): 10 00 00 00 10 00 00 00 00 01 00 00 00 00 00 00 02 12 04 03 00 00 00 00 00 08 00 00 04 02 00 00 00 71 00 00 00 00 00 00 22 05 01 01 00 00 00 00 00 04 00 00 04 06 00 00 00 71 00 00 00 00 00 00 21 03 02 02 00 00 00 00 02 00 00 00 00 01 00 00 00 71 00 00 00 00 00 00 11 02 02 04 00 00 00 00 To get it working in Clover v2.3 r3766 (Use Clover Configurator to make your life easier): Spoof Device ID as 0x100268B8 ("Fake ID" in "Devices") Check Inject ATI (in "Graphics") FB Name "Alouatta" (in "Graphics") Video Port "4" (in "Graphics") (Setting ports to 4 with the Alouatta personality will initially recognize both the HDMI and DVI outputs, but they will detect with the monitors swapped) Custom Boot Flag: "WithKexts" (in "Boot") Three separate patches in "Kernel and Kext Patches", one for each output: Name: AMD5000Controller, Find: 00040000 04060000 00710000 00000000 11020101 00000000, Replace: 00080000 04020000 00710000 00000000 22050101 00000000, Comment: HDMI Name: AMD5000Controller, Find: 00040000 04060000 00710000 00000000 22050404 00000000, Replace: 04000000 14000000 00710000 00000000 11020204 00000000, Comment: DVI Name: AMD5000Controller, Find: 02000000 00010000 19010000 00000000 12040303 00000000, Replace: 10000000 10000000 00010000 00000000 02120403 00000000, Comment: VGA (not tested) ----------------------------------------------------- Useful resources: Premade kexts for El Capitan (was working in my previous config): http://www.osx86.net/files/file/4609-hd5750-0x68be-el-capitan/ Official Clover documentation for ATIConnector patching (and the only place where WithKexts boot flag is mentioned. Doesn't mention the issue with multi-line patches: http://www.insanelymac.com/forum/topic/282787-clover-v2-instructions/?do=findComment&comment=1853099 Official Clover documentation for patching any kext (needs to mention WithKexts boot flag): http://www.insanelymac.com/forum/topic/282787-clover-v2-instructions/?do=findComment&comment=1853204 Excellent how-to guide for creating a framebuffer start to finish. Clover section doesn't mention WithKexts or multi-line issues: http://www.insanelymac.com/forum/topic/303186-how-to-modification-of-amd-fb-clover-injection/ Another good guide for framebuffer. Best technical explanation for what each section of the framebuffer means, but lack of consistent endianness gets confusing: http://www.insanelymac.com/forum/topic/273937-guide-getting-xfx-hd6850-connectors-to-work/
  8. Fellow Hackintoshers, I used to have a two monitor setup under 10.8.x / Clover which was a bit of a hassle to get to work because of the video ports not working. So I searched all over the place and where else but here on insanelymac did I find people kind enough to explain step by step how to change framebuffers manually. Back then I did like Alexander Martinez did (After following his tutorial, working on my files, I realized my card had the exact same setup, and copied it really) and it worked out quite well! Instead of choosing a framebuffer somewhere in Clover I wrote a patch into my DSDT and everything worked just fine. Now we moved on to 10.9.x and Ozmosis 'came out' (i.e. found it's way into the community). I'm glad to have moved to this bootloader, makes lots of things easier imho. But. After installing Mavericks (clean, complete Re-Install with Ozmosis) and re-editing a new DSDT with my patches, I once again had no video ports. So I edited the new AMD6000Controller's Duckweed frame buffer again, but dang...this time...it...didn't work. I did it again these days realizing that back then I used a Kext Utility not officially compatible with Mavericks, but still...nothing. When I still had no framebuffer forced with the DSDT, OSX decided to use Bulrushes for my card, which gave me wrong resolutions and mouse lags. Apparently this is a problem with 10.9 not with Ozmosis, so I'd love to see if somebody can give me some tips/hints on what to do, on what I did wrong maybe, or what I should try. To make this easier I'm gonna sum up again what I've done: (People take care: This is no solution to anything. It does not work. It's what I have done so far, to make debugging easier!) 1) Patch DSDT with the following: Device (PEGP) { Name (_ADR, 0x00010000) // _ADR: Address Method (_PRT, 0, NotSerialized) // _PRT: PCI Routing Table { If (PICM) { Return (AR02 ()) } Return (PR02 ()) } Device (GFX0) { Name (_ADR, Zero) // _ADR: Address Name (_SUN, One) // _SUN: Slot User Number Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0C) { "@0,name", Buffer (0x0D) { "ATY,Duckweed" }, "@1,name", Buffer (0x0D) { "ATY,Duckweed" }, "@2,name", Buffer (0x0D) { "ATY,Duckweed" }, "@3,name", Buffer (0x0D) { "ATY,Duckweed" }, "model", Buffer (0x13) { "AMD Radeon HD 6870" }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Device (HDAU) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } 2) Change the original framebuffer "Duckweed" in 10.9.1 AMD6000Controller from: 00 04 00 00 04 03 00 00 00 01 00 00 12 04 04 01 00 04 00 00 04 03 00 00 00 01 00 00 22 05 05 02 00 08 00 00 04 02 00 00 00 01 00 00 11 02 03 04 00 02 00 00 14 02 00 00 00 01 00 00 00 00 06 05 3) Into the adapted version fitting for my Sapphire HD6870 04 00 00 00 14 02 00 00 00 01 00 00 00 00 06 05 00 08 00 00 04 02 00 00 00 01 00 00 22 05 02 04 00 02 00 00 04 00 00 00 00 01 00 00 11 02 03 06 00 04 00 00 04 03 00 00 00 01 00 00 12 04 04 01 . Hopefully somebody has time and inner peace to help me on this. I know some of you guys are badass smart! Would really appreciate it. Thank you for reading. Kudos Marian
  9. Key Guys! I workin with my kaptop My setup OS OSX 10.9.4 VIDEO - ATI AMD HD 5870 Mobile WIFI - Dell Wirelles 1520 Half mini card Bluetooth - Dell 370 Bluetooth Enthernet - Intel® 82577LC Gigabit Network Connection Sound -IDT 92HD73C1/92HDW74C1/92HDW74C2 Workin Kext.zip VIDEO - OSX KEXT WIFI - IO80211Family.kext and toledaARPT.kext (in some website i cant remeber for give credits) Bluetooth - DellBluetoothHCI.kext(Found on web i dont remeber were) Enthernet - IntelE1000e.kext (Found in #####) Sound - VoodooHDA.kext (Found on web i dont remeber were) delete AppleHDA.kext for work. I found all kexts on web. after install mavericks. i Install cameleon i install all the kexts on /System/Library/Extensions remember to delete the AppleHDA.kext before install VoodooHDA.kext for work sound. the extra kexts i put on /Extra All the Kexts are in Kext.zip Not workin? Sound over HDMI - not tested Microphone - not workin Sound is little noise when you volume up. And...... I have some trouble with my ATI AMD HD 5870 Mobile after update to 10.9.4, i have a video problem ONLY on my laptop screen(blinkin sloid collors Grey Red Blue Green), on 10.9 i have the same problem only when i unplug the external monitor. but when i restart the both monitors work perfect. But when i update for 10.9.4 this problem back and only on the laptop screen. i tink is a framebuffer problem. i upload 2 images of the problem. i try edit the Nomascus Framebuffer to work with this setup. but not sucess, i cant understand how do this. i try put the ROM of my ATI CARD but not work. My conectors is Connector Object Id [14] which is [LVDS] encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A] encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector Object Id [5] which is [VGA] encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false Nomascus framebuffer original. 0000000 02 00 00 00 40 00 00 00 09 01 00 00 00 00 00 05 0000010 02 00 00 00 00 01 00 00 09 03 00 00 12 04 03 03 0000020 00 04 00 00 04 06 00 00 00 73 00 00 11 02 01 01 0000030 00 04 00 00 04 07 00 00 00 73 00 00 21 03 02 02 0000040 so if som guys help me with the framebuffer i appreciate! the ATI rom of my card is inside of Kext.zip
  10. I have DVI fully working, but LVDS is not recognized. I am almost positive that it is assigned to port 0, and the senseid is correct. I've tried changing the control flags, but any changes and none of the graphics work. This also happens when I change the last two entries. This is what I am currently using: 02 00 00 00 00 01 00 00 09 01 00 00 12 04 05 05 <-- LVDS, not recognized 00 04 00 00 00 02 00 00 00 01 00 00 10 00 03 03 <-- HDMI, not working, but it doesn't matter to me 04 00 00 00 14 00 00 00 00 01 00 00 11 02 01 01 <-- DVI, fully working as far as I can tell 00 04 00 00 00 01 00 00 00 01 00 00 21 03 02 02 <-- Not used/not sure what it is 00 04 00 00 00 01 00 00 00 01 00 00 22 05 04 04 <-- Not used/not sure what it is Is there anything I'm doing blatantly wrong? ATOM BIOS Rom: SubsystemVendorID: 0x1558 SubsystemID: 0x5104 IOBaseAddress: 0x0000 Filename: BR40793.004 BIOS Bootup Message: Clevo P150HM Blackcomb XT Samsung 2GB PCI ID: 1002:6720 Connector at index 0 Type [@offset 44696]: LVDS (7) Encoder [@offset 44700]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 44780]: 0x94, OSX senseid: 0x5 Connector at index 1 Type [@offset 44706]: HDMI-A (11) Encoder [@offset 44710]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 44803]: 0x92, OSX senseid: 0x3 Connector at index 2 Type [@offset 44716]: DVI-I (2) Encoder [@offset 44720]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44840]: 0x90, OSX senseid: 0x1 Connector at index 3 Type [@offset 44726]: DVI-I (2) <--- Not actually sure what this is, no other DVI port that I know of Encoder [@offset 44730]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 44840]: 0x90, OSX senseid: 0x1 IOService: (Only parts of LVDS & DVI shown) LVDS (I believe) | | | | +-o ATY,Elodea@0 <class AtiFbStub, id 0x1000002ef, registered,$ | | | | | | { | | | | | | "port-number" = 0 | | | | | | "display-type" = "NONE" | | | | | | "connector-type" = 2 | | | | | | "ATY,ActiveFlags" = 1 | | | | | | "IOFBDependentIndex" = 0 | | | | | | "IOFBDependentID" = 18446743524284400384 | | | | | | "ATY,ControlFlags" = 256 | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "device_type" = "display" | | | | | | "av-signal-type" = 0 | | | | | | "AAPL,iokit-ndrv" = <a06707817fffffff> | | | | | | "AAPL,gray-value" = <c38c6400> | | | | | | "display-connect-flags" = <00000000> | | | | | | "name" = "ATY,Elodea" | | | | | | "AAPL,boot-display" = <01000000> | | | | | | } DVI (I know) | | | | | | | | | +-o ATY,Elodea@1 <class AtiFbStub, id 0x1000002f0, registered,$ | | | | | | { | | | | | | "display-type" = "LCD" | | | | | | "connector-type" = 4 | | | | | | "ATY,ActiveFlags" = 4 | | | | | | "IOFBDependentIndex" = 1 | | | | | | "IOFBDependentID" = 18446743524284400384 | | | | | | "ATY,ControlFlags" = 20 | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "device_type" = "display" | | | | | | "av-signal-type" = 2 | | | | | | "AAPL,iokit-ndrv" = <a06707817fffffff> | | | | | | "AAPL,gray-value" = <c38c6400> | | | | | | "display-connect-flags" = <00000000> | | | | | | "name" = "ATY,Elodea" | | | | | | "port-number" = 2 | | | | | | }
×