Jump to content

El Capitan

Members
  • Content Count

    20
  • Joined

  • Last visited

About El Capitan

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

569 profile views
  1. @linasmit No, it's a minor inconvenience to have to boot into windows first; but the method works: both for 10.13 and 10.14. @Elvis2018 I am not familiar with the HPZ210. The following instructions work for 10.14.2 ===== AMD FireGL W4100. === vi /System/Library/Extensions/AMDRadeonX4000.kext/Contents/Info.plist CAIL_DisableGfxCGPowerGating 1 ===== ===== sudo cp /System/Library/Extensions/AMD7000Controller.kext/Contents/MacOS/AMD7000Controller . hexdump -ve '1/1 "%.2X"' AMD7000Controller | \ sed "s/000400000403000000010101000000001204040100000000000400000403000000010201000000002205050200000000040000001402000000010300000000000000060600000000000800000402000000010400000000001102010300000000/000400000403000000010100000000001204040200000000000400000403000000010200000000001102050100000000000400000403000000010300000000002103010400000000000400000403000000010400000000002001020600000000/g" | \ xxd -r -p > AMD7000Controller.patched sudo cp AMD7000Controller.patched /System/Library/Extensions/AMD7000Controller.kext/Contents/MacOS/AMD7000Controller ======= rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && \ touch /System/Library/Extensions && \ kextcache -u / && \ update_dyld_shared_cache -force ====== Once you get everything working, I suppose you could just diff and patch the respective files. The W4100 has basic metal support under 10.14, and the Cinebench 3D is approximately 80% of Windows 10
  2. ESXi 6.7.0 (Build 8169922) and Unlocker 2.0.9 (on a standalone server).
  3. El Capitan

    Tracing back the AMD GPU wakeup issue to its origin

    Thank you Slice. I will examine RadeonDump; it's included in DarwinDumper. I know that this is off-topic. At the moment I am using Windows 10 as a glorified graphics microcode loader (GuC). Is there anyway to capture the microcode that is loaded by Windows for the AMD Firepro W4100; then use Clover or macOS to write the microcode to the W4100? The loading of the microcode is the key to unlocking the full 3D performance of the W4100.
  4. Use Futomaki, Dashimaki or Radeon framebuffer. PATCHED KEXTS.zip
  5. El Capitan

    Tracing back the AMD GPU wakeup issue to its origin

    @Mieze Would you please provide instructions on how to dump BARS, the GPUs control register space, and how to change them. This is my problem: https://www.insanelymac.com/forum/topic/334965-amd-firepro-w4100-high-cinebench-r15-opengl-if-first-run-under-windows/ I believe that your generic method would be helpful in resolving my problem. The intention is to compare the Gpu's registers (BARs etc) between a soft Windows reboot, and a cold High Sierra boot. Then to patch the DSDT. I've read the thread and am surprised that no one has inquired about the tools that you have used. Thank you.
  6. I have an AMD FirePro W4100 2GB fully functioning (resume from sleep, HDMI audio, all ports working) under High Sierra 10.13.6 There is only one problem: the Cinebench 3D OpenGL benchmark is only 15 frames per second (fps). If I reboot my computer into Windows 10 then run the Cinebench 3D OpenGL benchmark the result is 55 fps. Now, if I REBOOT (with out turning off the power) into High Sierra then re-run Cinebench 3D OpenGL benchmark the result is 44 fps. It is obvious that the windows 10 Cinebench 3D OpenGL benchmark is initialising the W4100. Does anyone have any ideas how to create the Windows initialising action under High Sierra? In order to get the W4100 to work under High Sierra 10.13.6, I patched the Futomaki framebuffer to be consistent with the W4100, set CAIL_DisableGfxCGPowerGating to 1 - in the respective kext, and injected a graphics ID of 0x683d1002. Edit: It is not necessary to run Cinebench 3D OpenGL benchmark under Windows 10 to initialise the W4100: just booting to Windows 10 and then re-booting to High Sierra results in a high Cinebench 3D OpenGL benchmark score. If the computer is put to sleep and then resumed the Cinebench 3D OpenGL benchmark drops back to 15 fps.
  7. It most certainly does! Made an image of my previous esxi 6.5, updated to 6.7.0 and everything works. Be careful though: read the release notes, certain CPUs have been deprecated and said CPUs will result in the purple screen of death! Sterling work dear chap! You are greatly appreciated.
  8. Thank you MacPeet! I tried the config that you suggested [Pinconfigs.kext info.plist Optiplex790/990 Version 2]: <01B71C20 01B71D40 01B71E11 01B71F90 01871C30 01871D90 01871EA1 01871F90 01971C40 01971D90 01971E81 01971F01 02171C50 02171D40 02171E21 02171F02> I am pleased to announce that everything functions correctly. Headphone switching works; rear input and output works - tested by doing a looped recording, the rear input only accepts pre-amplified sources. Front microphone input (and monitoring) works.
  9. @MacPeet Is the rear input and front (microphone) input working with (autoswitch) layoutID 16/0x10 when using Optiplex790/990? I developed the AppleALC for the Dell Precision T1600 Workstation. I'm certain that the ALC269VB High Definition Audio Driver is the same for the Precision T1600 and OptiPlex 790/990. The layoutID for Dell Precision T1600 Workstation is 11/0x0B: would you try this value on your Optiplex790/990. I've tried layoutID 15/0x0F on my Dell Precision T1600 Workstation and it functions correctly. LayoutID 16/0x10 works, but the output volume is low and the front microphone does not function. I can also confirm that the Optiplex 780 and the HD5450 functions correctly (with video acceleration) on macOS High Sierra beta 7: when video rollback is used.
  10. El Capitan

    ALC269VB Dell Precision T1600 Workstation - macOS 10.12.1

    Yes! I've incorporated support into AppleALC. Thanks for that. NullCPUPowerManagement literally means no PM! I now have a fully functioning Dell Precision T1600 E3-1270
  11. El Capitan

    AppleALC — dynamic AppleHDA patching

    Previously, I stated that the "rear input" on the back of the Dell Dimension T1600 Workstation was not working with the latest revised AppleALC. Well, this is only partially true. The input on the back of the iMac (and the T1600) is NOT for a microphone; it is only for amplified input: looping the "rear output" to the "rear input" results in a sound recording.
  12. El Capitan

    AppleALC — dynamic AppleHDA patching

    @vit9696 I've revised my AppleALC entry for "Mosser - ALC269VB Dell Precision Workstation T1600" Now all the outputs and input(s) actually work - apart from the blue/green "rear input". The front input/mic has "ambient noise reduction" and very good sound quality. The rear LINE OUT and FRONT HEADPHONE are mutually selectable. Dell Precision T1600 Workstation layout-id 11 (0x0B) Codec: Realtek ALC269VB Vendor Id: 0x10ec0269 Subsystem Id: 0x10280498 Revision Id: 0x100100 T1600.AppleALC.Params.rev1.zip
  13. El Capitan

    ALC269VB Dell Precision T1600 Workstation - macOS 10.12.1

    I used Clover legacy install. I've attached a generic copy of my Clover EFI. I've also included my work in progress of AppleALC for the RTL679 audio processor as used by the T1600: at present all the audio outputs work; but none of the inputs! {layout-id 11 (0x0B)} The DSDT is for an AMD HD6750 and the SSDT (power management) for a Xeon e3-1270/i7 2600 EFI.latest.zip
  14. I've managed to install macOS Sierra on a Dell Precision T1600 Workstation (Xeon E3-1270, AMD HD6570 graphics card). The HDMI sound works perfectly; but the onboard sound does not work. I'm a bit disappointed that the AppleHDA requests has been pinned. But I would be grateful if one of the sound experts would take a look at the attached files. The strange thing is that HDMI sound works with AppleHDA; and the onboard sound works with Voodoohda: but not concurrenly. Thank you. sound.zip
  15. The pyhon converter 2to3 highlights the change in syntax. esxi.patch.txt
×