Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/02/2019 in all areas

  1. Well then there’s probably something else in there that’s broken. Since no one could give me a straight answer, i had to try and figure it out on my own. It works now and that’s what matters. I’ll take a look when i get home to see what else could be causing this. So far, as i said, the sample config is your best friend.
    2 points
  2. I am looking original’s Mac Pro 7.1 ACPI folder. Hack more
    2 points
  3. 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
    1 point
  4. I'm not near my pc right now. But open up your config and check out your ACPI -> Block section. It shouldn't be empty. You can take some inspiration from the sample config inside the Docs folder.
    1 point
  5. Sorry for some stupid opinion: what version of Opencore do you use? In the actual sample.plist, you will find these keys bellow for Kext and Patch <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string></string>
    1 point
  6. github is the official site for Clover download now.
    1 point
  7. Looks like you changed the size window which truncated a part of the french text @ system read/write -> read only If you wish to keep that new size format, that same text can be expressed by a shorter one. Ex below. I made the change in the fr.strings attached. Your call. fr.strings
    1 point
  8. @SavageAUS, this looks like a typo in kext injection. E.g. missing executable file or something like that.
    1 point
  9. Why did you laugh for??? You are asking for help, i need to make sure first,, I must avoid duplicate resource with same Node Id. I don't know you if you're smart or not. Before made resource i need to check your IOREG Output first. But if you know how to make resource by yourself, then make it. Good luck
    1 point
  10. Clover.app v1.11 Beta available at first post: - Retro compatibility since OS X Mavericks (10.9). - Search update ability of Clover.app. - Auto mount of the selected ESP. - ESP umounting after Clover installation. - French translation by Ellibz. - Some other corrections and improvements. The code has been heavily modified to run in older OSes but I've tested the app in Mavericks, Yosemite, El Capitan, Sierra, Mojave and Catalina. Missing High Sierra. I did not expect my code behave differently in any supported OSes, but the difference can reside in the Cocoa.framework shipped with them. You know starting from 10.10 Apple introduced vibrancy and Dark mode, and for my experience I know that the relative classes (NSColor, NSAppearance and NSVisualEffectView) had bugs and behave differently like having black background with black text, i.e. totally unreadable. In mentioned OSes I fixed all of these bugs and only 10.13 remain to be tested. As soon someone will report me that the interface is good (dark and light) in High Sierra too, Clover.app will be released as "stable" and no longer in Beta stage. Anyway, just to ensure no regressions or new bugs are introduced (and not visible by me), tests and reports are welcome! Note: in 10.10 and 10.9 the installer looks very different just because the original one I wrote for 10.11+ can't work with all the functionalities in Yosemite and Mavericks.
    1 point
  11. This utility is wrong Clover is 5099 now, not 5096. FakeSMC 1800 is obsolete as well other kexts on your screen.
    1 point
  12. I updated AnVMSR so it would work on Catalina. - It can read and write MSR register. - It can read and write the TSC. - It can read and write the PMC. Enjoy EDIT: Little code fix. I tested the module, it works... AnVMSR.zip
    1 point
  13. • go to Start Menu, launch cmd as Administrator • Paste the following command: Reg add HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation /v RealTimeIsUniversal /t REG_QWORD /d 1
    1 point
  14. Ok, just checked out the source... I'll build and test that tool too
    1 point
  15. lspci? It included into DarwinDumper, see inside. Andy, See to compare msr_tools
    1 point
  16. Haven't tested yet, but thanks anyway. Is there some software to read and interpret values of common PCI registers, such as LPC (D31:F0) or ME interface? Will be very useful too.
    1 point
  17. This tool is made by me for reading and writing to CPU MSR registers. It works in kernel mode by a driver which is linked to the tool in user land with a user client. Source is included WARNING: Don't randomly read or write to MSR registers... If you read or write invalid MSR registers, or invalid data written, your system will crash... Usage: anvmsr read E2 = read MSR register E2 and show value. anvmsr write E2 0BAD = write 0BAD to MSR register E2 Enjoy... AnVMSR-1.0.zip A version for BigSur see here
    1 point
  18. Anyone? Sent from my iPhone using Tapatalk
    0 points
  19. Update: I tried renaming UAR1 in DSDT, but that didn't work. I also tried creating a small SSDT to disable the device, and that didn't work either ....
    0 points
×
×
  • Create New...