Leaderboard
Popular Content
Showing content with the highest reputation on 04/24/2018 in all areas
-
Boot option name retrieval 1) Locate the booter image as explained blow. 2) Locate ".contentDetails" in the parent folder 2.1) if unsuccessful, locate ".disk_label.contentDetails" in the parent folder 2.2) if unsuccessful, retrieve the volume's name HFS Boot 1) Retrieve blessed file via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L41 1.1) if unsuccessful, retrieve blessed folder via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L45, append "\\boot.efi". NOTE: This is broken in the latest binary I checked. 1.2) if unsuccessful, use the following hard-coded paths: "\System\Library\CoreServices\boot.efi", "\EFI\APPLE\{ARCH}\BOOT.EFI", <StandardEfiPath>, "\\boot.efi" in this order 2) FV2 Recovery does not follow the usual practice because it is not shown by BootPicker anyway. Determine it via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L49, verify it does not match 1). APFS Boot 1) Determine the APFS Volume Info (and hencefor detect whether it is APFS in the first place) via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L54 1.1) Determine the APFS Container Info via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L36 1.2) Verify the Volume Role via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L51 1.3) Retrieve blessed file analoguous to HFS 1). NOTE: This step and 1.3.1) are broken in the binary I checked, hencefor it does not happen, but is probably supposed to. 1.3.1) if unsuccessful, retrieve blessed folder and append the booter name the same way as in HFS 1.2) 1.4) (if unsuccessful,) locate all Volumes that are part of the same container, check whether the current Preboot partition has folders named by the just located Volumes' GUIDs and append the hard-coded paths from HFS 1.2) if existant 2) Recovery detection works the same way as 1.4), just for a Recovery instead of a Preboot volume3 points
-
2 points
-
If you use arbitrary inject, you do not need the ssdt, so try in the meantime. Later I update everyone for use this method and load the correct ssdt1 point
-
I expected it to not work, especially after so many attempts at different methods. This one sounded the least likely to work, and as soon as I booted, my Apollo turned on its HOST light and it's been working since! I added my clover arbitrary device as 32:00.00 (my BR1A) and that's it. I only pulled the cable from the Mobo but not the card... not sure if that matters.1 point
-
Holy s********!!! The cable pulling, simplified SSDT + clover injection has worked for me on my Asus Prime Deluxe with Asus TBEX3 as described by @lelet. Unreal! Thank you so much. Are there further steps we need to take to get things fully functional? I have no other USB C needs as of yet but am curious.1 point
-
Hi @fabiosun Could you please have a look at my attached files. Now booting without the TSCAdjustReset.kext . Sleep/wake and everything is working perfect without that kext so I can run my rig without it but I'm to much "noob" to understand if this is the best way for my CPU performance. Is there a way to check this? Then I would like to ask you another thing about my MSR 0xE2 register. According to KGP's site the output from voltageshift should be something similar with: RDMSR e2 returns value 0x7e000003 but when I run this test the output is: RDMSR e2 returns value 0x402? on the other hand my bootlog and AppleIntelInfo.kext output is showing quite clear that the bios is unlocked: MSR 0xE2 before patch 00000402 MSR 0xCE 00070A2C_F3811900 MSR 0x1B0 00000000 Everything shows that my MSR 0xE2 register is unlocked but still need FakeCpuid or/alt. an old XCPM bootstrap patch together with xcpm_program_msrs (c) Pike R. Alpha for booting. I can't understand that i9-7980xe processor with the same signature 0x50654 can boot perfect without this kernel patch and without FakeCpuid when at least on the paper a more native processor like the Xeon W fail. Is there anybody else out there how could help to solve this problem. I'm just a super noob trying to put this rig together and the only skill I have is my insistence and that is not enough for this project. With TSC kext.rtf without TSC kext.rtf1 point
-
SSDT will do the things needed, to make DSDT, it require you to properly Disassemble your ACPI files, patch them for OS X then compile your DSDT, it may take some time! EFI\CLOVER\ACPI\patched\here1 point
-
1 point
-
Sure thing. I'll do me best but no promises I guess you the file you attached is corrupted.1 point
-
1 point
-
i'll check it, back to home in a few hours what boot problem u have?1 point
-
The picture tells _DSM already exists. The cure is common DSDT->Binary patches-> find _DSM replace ZDSM.1 point
-
Hi Mieze, just a short feedback! It works with full speed now, I've updated my OMV 2.x to the most recent 3.x version (Openmediavault) - and I think I messed up my SMB settings on the old version in the past due to my fixing in 2016 with the old hackintosh mac pro 5.1 on Asus P6TSE. Now with 110MB/s nice and clean, thanks for your help! I love this community!1 point
-
Here you go https://www.sendspace.com/file/b5iijx It's a shame the forum only allows 10MB.1 point
-
SUCCESS!!! Finally all my THUNDERBOLT devices are hotpluggable!! The solution is unbelievable, seems to work on all chipsets without using SSDT, and shifts the focus on the cause of all problems Thunderbolt: the cable THB_C!! Already in my previous post I noticed strange behavior by inserting the _DSM method in DSB2: PCIHotplugcapable Zero. Since then I've been trying to figure out how the XHC controller affected the Thunderbolt hotplug, until Crismac2013 suggested I disconnect the THB_C cable from the motherboard. Once disconnected, it was enough to add as an arbitrary inject my first Thunderbolt address (PXSX): <dict> <key>Comment</key> <string>PCI THUNDERBOLT 15d3 first entry</string> <key>CustomProperties</key> <array> <dict> <key>Disabled</key> <false/> <key>Key</key> <string>PCI-Thunderbolt</string> <key>Value</key> <integer>1</integer> </dict> <dict> <key>Disabled</key> <false/> <key>Key</key> <string>IOName</string> <key>Value</key> <string>pci-bridge</string> </dict> </array> <key>PciAddr</key> <string>01:00.00</string> </dict> and it works!! Now I have also added my last SSDT to get PCI information on System info. Probably with my last SSDT the arbitrary inject are not needed, as PCI-Thunderbolt One is already inserted as a _DSM method in UPSB. I suspect, however, that in this way the USB-C functionality will be lost, you should do a test! In any case this is a huge step forward and makes it obvious that we need to work on XHCs controller to solve the problems with the hotplug with THB_C cable connected.1 point
-
Normal, rotational hard drives doesn't have attributes for life... (not even all ssds have it).1 point
-
So, i am thinking about pubblishing the stable release of tinu 2.0, just with a few minor chenges from the last pre-release, and to focus my work on the next one, i have just chenged a couple of UI things for the stable release and add a warning message if you try to use a time machine disk as a target drive to create the macOS install media, for the release that will come after the stable 2.0 release (and maybe also after a bug fix release for the 2.0 if needed) i am trying to use the system apis to manage the tasks which needs special priviladges to be executed, instead of the "sudo" based system which i am using now, this will make the application more secure and reliable, and also you will have to do the authentication only one time, when creating an install media, and using this system maybe i can also pubblish the application on the app store (obviusly just a limited version for mac users, but a version with all the features unlocked will be always available outside the app store and will have all the hackintosh-friendly features as well). But to do that i need to re-write a large amount of code into the app, because all the tasks which needs special permitions needs to be re-implemented differently, so that's why i do not want to use this in the 2.0 release, so because i am going to finish with tinu 2.0 tell me every complain or problem you are having with the latest pre-release or the latest release of tinu, so i can work on that before releaseing the stable 2.0 version1 point
-
Unfortunately it still doesn't sleep. Monitor does but not computer1 point
-
I tired the new DSDT and 11 & 13 in clover configurator and still no audio. Testing sleep now.1 point
-
DSDT.aml.zip check if audio work ur codec work with 11 or 13 only1 point
-
ADI 1984A High Definition Audio Codec on my Dell 780. OK I will put back old lan kext1 point
-
the command return? log show --style syslog | fgrep "Wake reason" what audio codec? back old intel Lan kext1 point
-
run app again, send me new files RunMe.app.zip1 point
-
Thanks for the Clover Maldon. Sleep still not working... display goes to sleep but computer doesn't go to sleep... power button is solid and the fans are still on.1 point
-
Hi Maldon, great guide! I got my old Dell 780 (LGA775) running High Sierra 10.13.4 nicely, thank you! I have no audio and I see where you mention "Device HDEF + AppleALC + Lilu". I have AppleALC + Lilu in my KEXT folder but not sure what "Device HDEF" is. Also when it goes to sleep it takes like 2 minutes to wake. I have a Q9400 quad core + Nvidia Quadro FX580 but don't have a DSDT for it. Can you help me with a DSDT? Here are my RunMe Results https://drive.google.com/file/d/1Duv3XYyW4UhziDVVWdquwxYcGQ-D5tvm/view?usp=sharing SPECS: Dell 780 MT, Q9400 2.66GHz Core2Quad Core, Nvidia Quadro FX5801 point
-
Can you share the Clover folder that lets you boot? I will edit it to includes Allan changes1 point
-
1 point
-
Hello Mald0n: Nice to meet you, I have created a post about my problem on High Sierra before and I was redirected to this guide by Allan. As mentioned in the post, I was not able to get pass the login screen at initial boot and the system could not shutdown occasionally. However I solve the high temperature problem when I replace the clover folder you provide on first post, currently the cpu temperature is around 5x-6x'c after 10 mins up time. Attached is the clover folder, ioreg as well as the send me app, thanks for your help! p.s. I notice that your clover boot efi is a old traditional grey apple boot logo, Is there a version of modern dark and white logo one that I could replace with? Thank you! https://www.insanelymac.com/forum/topic/333867-cant-get-pass-2nd-stage-boot-logo-on-initial-boot-and-high-temperature/ My system:Gigabyte GA-X48-DQ6Core 2 Extreme QX9650 C04 x Kingston DDR2 800ghz RamGalaxy GTX460 1GB120GB SSD Leven JS500120C, high Sierra installed250GB seagate ST3250310AS250GB WDC WD2500JS-08NCB1 File: https://drive.google.com/file/d/1_k3_jxvzGaLfDzin0zSAUT5ml16Hq15c/view?usp=sharing1 point
-
1 point
-
@MaLd0n looks like USBInjectAll has official 300 series support now. https://bitbucket.org/RehabMan/os-x-usb-inject-all/commits/all Can I drop XHCI-200-series-injector.kext and replace it with the updated XHCI-300-series-injector.kext or should I leave XHCI-200-series-injector.kext alongside the updated XHCI-300-series-injector.kext?1 point
-
Hi @vector sigma, See a solution to print CPU model and signature as Hex numbers statusString += String(format: "\tModel: 0x%X\n", System.sysctlbynameInt("machdep.cpu.model")) statusString += "\tExt Model: \(System.sysctlbynameInt("machdep.cpu.extmodel"))\n" statusString += "\tExt Family: \(System.sysctlbynameInt("machdep.cpu.extfamily"))\n" statusString += "\tStepping: \(System.sysctlbynameInt("machdep.cpu.stepping"))\n" statusString += String(format: "\tSignature: 0x%X\n", System.sysctlbynameInt("machdep.cpu.signature"))1 point
-
I'm sorry but I've not been able to control it... -.-1 point
-
Check this one: hwmonitor2.zip, there is much more information about the CPU MACHINE STATUS: CPU: Name: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Vendor: GenuineIntel Physical cores: 2 Logical cores: 4 Family: 6 Model: 58 Ext Model: 3 Ext Family: 0 Stepping: 9 Signature: 198313 Brand: 0 Features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC POPCNT AES PCID XSAVE OSXSAVE TSCTMR AVX1.0 RDRAND F16C Ext Features: SYSCALL XD EM64T LAHF RDTSCP TSCI Microcode version: 31 Thermal sensors: 1 Thermal invariant APIC timer: 1 System: 1% User: 3% Idle: 95% Nice: 0% MEMORY: Physical size: 8.0GB Free: 48MB Wired: 1.99GB Active: 2.39GB Inactive: 2.36GB Compressed: 1.22GB SYSTEM: Model: MacBookPro10,1 Sys name: Darwin Node name: FrancescoRs-MBP.station Release: 17.6.0 Version: Darwin Kernel Version 17.6.0: Fri Apr 13 19:57:44 PDT 2018; root:xnu-4570.60.17.0.1~3/RELEASE_X86_64 Machine: x86_64 Uptime: 2d 8h 40m 15s Processes: 350 Threads: 1264 Load Average: [1.74, 1.49, 1.44] Mach Factor: [2.8799999999999999, 2.4100000000000001, 2.2010000000000001] POWER: CPU Speed limit: 100.0% CPUs available: 8 Scheduler limit: 100.0% Thermal level: Not Published BATTERY: AC Powered: false Charged: false Charging: false Charge: 37.0% Capacity: 3248 mAh Max capacity: 8719 mAh Design capacity: 8719 mAh Cycles: 487 Max cycles: 1000 Temperature: 22.0°C Time remaining: 1:561 point
-
1 point
-
I got same trouble. In my case I solved that by putting kexts in clover kexts/Other directory. Fred1 point
-
Updated BIOS Image with APFS.EFI from 10.13.4 embedded (not required to install 10.13.4 but just to keep things tidy) Note: I haven't tested the ROM image (I just replaced the APFS module in a working and tested image) because I am on pager duty atm and need a working computer just in case ... 10.13.4 QUO ROM Image1 point
-
I don't get why people keep using those insanely long Defaults.plist file on a QUO board All you need is (adjust for Serial Number and Graphics Card) <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Version</key> <string>1.0.1</string> <key>Date</key> <integer>0</integer> <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key> <dict> <key>BiosDate</key> <string>02/03/2018</string> <key>BiosVersion</key> <string>IM131.88Z.0114.B00.1802030048</string> <key>FirmwareFeatures</key> <integer>0xE00DE137</integer> <key>FirmwareFeaturesMask</key> <integer>0xFF1FFF3F</integer> <key>ProductId</key> <string>Mac-FC02E91DDD3FA6A4</string> <key>ProductFamily</key> <string>iMac</string> <key>ProductName</key> <string>iMac13,2</string> <key>SystemSerial</key> <string>INSERT SERIAL NUMBER</string> <key>BaseBoardSerial</key> <string>INSERT SERIAL NUMBER + 5 DIGITS</string> </dict> <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-v nvda_drv=1</string> <key>csr-active-config</key> <integer>103</integer> </dict> <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key> <dict> <key>DisableNvidiaInjection</key> <true/> <key>BootEntryTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label $platform.$major.$minor</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label $platform.$major.$minor</string> </dict> </dict> </plist> You had disabled it ... <key>DisableVoodooHda</key> <true/>1 point
-
iMac 13,2 Defaults.plist with working FirmwareFeatures & FirmwareFeaturesMask, just change SMBios values with yours Defaults.plist1 point
-
yes because R9 270X use AMDPitcairnGraphicsAccelerator <key>IOProviderClass</key> <string>AMDPitcairnGraphicsAccelerator</string> and the one for Rx560 use the AMDBaffinGraphicsAccelerator <key>IOProviderClass</key> <string>AMDRadeonX4000_AMDBaffinGraphicsAccelerator</string> you just need to change the IOProviderClass to inject it correctly its not depend on the Framebuffer that you use but on the Accelerator1 point
-
When load Clover . Select HDD or Partition where you installed OSX. Press space. Select Boot macOS with injected kexts1 point
-
Thanks for the link dude! I want to be able to use the pre-installed wifi card. If I am unable to use that... I will continue to use Windows 8 as it is probably gonna end up dominated OS X once again. It is kinda hard taking a UX31A apart it is much easier with a UX32DVA1 point
-
did sourceforge wipe out clover repository? https://sourceforge.net/p/cloverefiboot/code/ it shows No (more) commits0 points