Jump to content


  • Content Count

  • Joined

  • Last visited

About rotoyouoio

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

2,163 profile views
  1. rotoyouoio

    80 Core Hackintosh :)

    any news on what the limit is with mojave/high sierra? edit: to answer my own question - it's still 64 threads
  2. i pm'ed that guy, since I'm also russian, waiting for him to answer, how he flashed modded defaults. meanwhile, I found an s3 ssdt from an imac and with that it enters sleep with powering down all the fans, but it fails to exit sleep EVEN in windows. but my guess is that changing that setting in BIOS rather than reporting it to the system with an SSDT has more chances of being successful
  3. hello, world I have one of those chinese boards, namely 3.5B Everything is working good, here is my darwin's dump: http://rgho.st/private/87y5TQqwm/708e722405be697706d76cd077f3a2b7 but the only problem is that I cannot get my hack to even TRY to sleep, it only puts the display to sleep in Windows I can get it to hibernate and that works. sleep after messing around with the bios is acheivable, though initially it wasn't, but it has the bug of the cpu cooler not stopping in macOS i i don't even know if it can hubernate, because the thing won't try to. what are the ACPI tables missing for the system to assume the possibility of sleep?
  4. can anyone try using the 10.13.0 IOUSBHostFamily.kext in 10.3.2+? i've attached the kext from 10.3.0 gm (the only one i've had) install it using kext utility overwriting the original (make a backup if you wish) do not delete generic usb kext kind of in a rush here, about to buy an x79 mobo tomorrow, don't want to get stuck in sierra IOUSBHostFamily.kext.zip since no one reacted I'll share my findings. the VIA vl805 chipset to my surprise continues to work normally with the generic kext holy {censored}, it works without any kext whatsoever!!! the NEC has problems on 10.13.2+ with generic and if flashed to caldigit (the last being the better solution that doesn't require to stick-eject-stick and yet with a drawback of only drive type peripherals working) which is why I've attached the pre 10.13.2 usb system kext for someone to test can anyone report about asmedia?
  5. rotoyouoio

    Disk Utility v13 for macOS Sierra.zip

    this stopped working completely in 10.13.4 betas. doesn't show a single disk/partition/image. such a bummer. any ideas anyone? ah, well, paragon has a nice substitute
  6. rotoyouoio

    Clover General discussion

    i made Darwin do a dump over here http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2522249 i think everything but the screenshots are in that darwin's dump =0) please correct me if i'm wrong. the error happens instantly in memtest/rember displaying that text all the other occurences are hard to screenshot, like finder getting stuck, resolve render output getting corrupted, or prefence files getting messed up up to the point of the system becoming unbootable (the reason i started testing initially) i can only reproduce this problem by having usb drive devices attached. so i believe that yes, only usb related dumping the original acpi tables is going to take some time, i am away from the machine now. i can, however, try to get a darwin dump with the original acpi tables from a similar setup, if my Darwin's dump is of no help without the original unpatched tables. I don't use a custom, only the patches that are in the plist an i believe that clover drops most of the secondary
  7. rotoyouoio

    Clover General discussion

    umh... where did i insult any developer? i only said i was frustrated from diagnosing this. i mean i wasted a week before coming to the conclusion that it is not me being an idiot or the hardware being faulty. thus the frustration. the possibility of me being an idiot remains though. concerning dmazar. he might be a great guy, i just remember him saying that this is heavy work that he won't spend any more time when the x99 problem happened. and i've remembered this only to save someone's time pointing me at his direction. this in no way contradicts that he's a great guy and someone's good friend =0) anyway, back to the problem. screenshots of rember are in no way more informative than the text copied. i will spill my understanding of the problem, forgive me if it's too lame/nooblike/utterly silly the EFI (?) reserves and uses some physical memory addresses for hardware operation after the kernel is loaded, particularly usb storage devices (they are a certain condition for reproducing on x299 hardware), that the system considers available, hence writing to these addresses (virtual or not - no idea) is NOT successful, but the system has no idea. which means that when reading from these addresses - the system/software/memtest reads incorrect data, which can lead to practically anything. memtest is only different in the way that it knows what data must be returned after the inquiry. there. there is no way i can better describe the problem than the text above and in the previous posts. not that i expect you to diagnose this without such hardware, and i can live with legacy booting. (the only practical downside is sata hotplug not working in case of no harddrive attached to the hotplug port before boot) i am still rather grateful to be mentioned by someone like apianti and fritz (very little sarcasm here and it's in good spirit =0) this is more a cryout and a warning for future users of x299 platforms/a challenge for hackintosh (can a new term be made?) developers
  8. rotoyouoio

    Clover General discussion

    this is from memtest, it's an example of the actually occupied address during the time that darwin dump was made but the problem affects all the system
  9. rotoyouoio

    Clover General discussion

    to continue address after running darwindumper: FAILURE! Data mismatch at local address 0x0000000ecbaf5d30 Actual Data: 0x0000000e88498849 does darwindumper do the dump you requested? DarwinDumper_3.0.3_25.10_14.27.59_iMac19,1_AMI_X64_4264.RM-4339.22551(750c5fff.b2eb1d0b90)__Unknown_17B45a_user.zip
  10. rotoyouoio

    Clover General discussion

    LastBootedVolume only works with a functional nvram. you don't have any, since you require emuvariable
  11. rotoyouoio

    Clover General discussion

    will do, but the address is non constant, though it always ends in ***d30 and i maybe naming it wrong, forgive me, trying the best i can. and the error does not prevent booting. the system is operational the last phase of troubleshooting i did before confirming it with others looked like this: strip the mobo from everything, attach components one by one. attach usb3 internal cardreader, get errors. disconnect it. have a hunch the problem is more generic. boot into system. get pass the stuck address test. stop. attach a usb3 hardrive. start testing. errors. disconnect it. start testing. no errors. so the problem is rather dynamic. and completely absent during legacy boot. and i need point out once again, that it affects everything, not only the outdated memtest. will update once i dump
  12. rotoyouoio

    Clover General discussion

    i've wasted a {censored}load of of time to test EVERY component by replacing it, so please don't tell me that mine is faulty, or to try other efi modules, or to lower the bios settings or any other obvious first steps. really frustrated with this. on asus (quite possibly other vendors are affected too) x299 motherboards there is an issue of memory allocation errors with uefi boot. i can only but certainly reproduce the problem when a usb3 storage device is attached, others have reported that no matter what the usb generation is. memcheck within os is a witness of this problem, and every time the occupied address ends in ***d30 this corrupted operation affects not only memcheck, but every operation possible. a more obvious way to produce evidence for the non believers is to render an hour or two of RED camera files to a compressed codec onto an external storage device and see the result is corrupted i'm rather tired of proving that this is an actual error and not memtest being outdated. memtest is only a tool to witness this, not to test the memory this obviously does not happen with legacy boot quite possible this is a problem on other aptiov5 capsules and even more possible that future platforms will posses this problem too to my limited understanding (it might be wrong) this effect is an evolution of memory allocation problems that people encountered on x99 platforms with aptiov5 capsules and hence aptiofix related. but back in the day this occured only before kernel loading. and i've seen somewhere, that dmazar refused to revisit aptiofix stating that it's too much time to do this from scratch.
  13. https://github.com/mologie/NVWebDriverLibValFix/releases is this of any help?
  14. rotoyouoio

    New Driver for Realtek RTL8111

    Hello and thank you for your hard work. Your kext is great except this occasional KP upon going to sleep (possibly, when the network is under heavy load, but cannot be sure) here is the log: *** Panic Report *** panic(cpu 0 caller 0xffffff80003ce40a): Kernel trap at 0xffffff7f82b1347e, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff81e409c1d0, CR3: 0x00000000093aa000, CR4: 0x00000000001626e0 RAX: 0x0000000000000000, RBX: 0xffffff81a3631000, RCX: 0x00000000000001d0, RDX: 0x0000000000000100 RSP: 0xffffff91f22ebce0, RBP: 0xffffff91f22ebd70, RSI: 0xffffff8024a85c00, RDI: 0x000000000000001d R8: 0x0000000000000000, R9: 0xffffff8000a9e7c0, R10: 0x0000000000000000, R11: 0x00002ac243f6c62e R12: 0xffffff81a3631000, R13: 0xffffff81e409c000, R14: 0xffffff81a3631000, R15: 0x0000000000000000 RFL: 0x0000000000010202, RIP: 0xffffff7f82b1347e, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff81e409c1d0, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0 Backtrace (CPU 0), Frame : Return Address 0xffffff91f22eb970 : 0xffffff80002dab12 0xffffff91f22eb9f0 : 0xffffff80003ce40a 0xffffff91f22ebbd0 : 0xffffff80003ec273 0xffffff91f22ebbf0 : 0xffffff7f82b1347e 0xffffff91f22ebd70 : 0xffffff7f82b13f86 0xffffff91f22ebd90 : 0xffffff7f81844ae4 0xffffff91f22ebdc0 : 0xffffff80008b5958 0xffffff91f22ebe30 : 0xffffff7f81844b4b 0xffffff91f22ebe80 : 0xffffff7f81848d7c 0xffffff91f22ebef0 : 0xffffff8000565b8b 0xffffff91f22ebfb0 : 0xffffff80003c8e27 Kernel Extensions in backtrace: com.apple.iokit.IONetworkingFamily(3.2)[848B398F-4D96-3024-8092-6CD3534D2CCA]@0xffffff7f8183c000->0xffffff7f8186ffff com.insanelymac.RealtekRTL8111(2.2.1d4)[B320DB79-DD55-303F-8181-C1CED8269439]@0xffffff7f82ab2000->0xffffff7f82b18fff dependency: com.apple.iokit.IONetworkingFamily(3.2)[848B398F-4D96-3024-8092-6CD3534D2CCA]@0xffffff7f8183c000 dependency: com.apple.iokit.IOPCIFamily(2.9)[4FE41F9B-2849-322A-BBF8-A94816C003D6]@0xffffff7f80b7d000 BSD process name corresponding to current thread: kernel_task Boot args: nvda_drv=1 nv_spanmodepolicy=1 kext-dev-mode=1 rootless=0 slide=0 Mac OS version: 15E65 Kernel version: Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 __HIB text base: 0xffffff8000100000 System model name: iMac13,2 (Mac-FC02E91DDD3FA6A4) System uptime in nanoseconds: 47013852363025 last loaded kext at 46650209409283: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f82b2e000, size 32768) last unloaded kext at 46780152258995: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f82b2e000, size 32768) loaded kexts: com.nvidia.CUDA 1.1.0 com.nvidia.web.GeForceWeb 10.1.1 com.nvidia.web.NVDAGK100HalWeb 10.1.1 com.nvidia.web.NVDAResmanWeb 10.1.1 com.usboverdrive.driver.hid 3.2 at.obdev.nke.LittleSnitch 4362 org.hwsensors.driver.GPUSensors 1707 com.insanelymac.RealtekRTL8111 2.2.1d4 org.hwsensors.driver.LPCSensors 1707 net.osrom.kext.Disabler 1.0.1 org.voodoo.driver.VoodooHDA 2.8.8 org.hwsensors.driver.ACPISensors 1707 org.hwsensors.driver.CPUSensors 1707 org.netkas.driver.FakeSMC 1707 com.apple.filesystems.ntfs 3.13 com.apple.driver.ApplePlatformEnabler 2.6.0d0 com.apple.driver.AGPM 110.21.18 com.apple.driver.X86PlatformShim 1.0.0 com.apple.filesystems.autofs 3.0 com.apple.driver.pmtelemetry 1 com.apple.iokit.IOUserEthernet 1.0.1 com.apple.driver.AppleUpstreamUserClient 3.6.1 com.apple.driver.AppleMCCSControl 1.2.13 com.apple.iokit.IOBluetoothSerialManager 4.4.4f4 com.apple.driver.AppleOSXWatchdog 1 com.apple.Dont_Steal_Mac_OS_X 7.0.0 com.apple.driver.AppleIntelHD4000Graphics 10.1.4 com.apple.driver.AppleHV 1 com.apple.driver.AppleLPC 3.1 com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0 com.apple.driver.AppleIntelFramebufferCapri 10.1.4 com.apple.driver.AppleRAID 5.1.0 com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0 com.apple.BootCache 38 com.apple.iokit.IOAHCIBlockStorage 2.8.5 com.apple.driver.AirPort.Atheros40 700.74.5 com.apple.driver.AppleAHCIPort 3.1.8 com.apple.driver.usb.AppleUSBEHCIPCI 1.0.1 com.apple.driver.AppleRTC 2.0 com.apple.driver.AppleACPIButtons 4.0 com.apple.driver.AppleHPET 1.8 com.apple.driver.AppleSMBIOS 2.1 com.apple.driver.AppleAPIC 1.7 com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0 com.apple.nke.applicationfirewall 163 com.apple.security.quarantine 3 com.apple.security.TMSafetyNet 8 com.apple.driver.AppleIntelCPUPowerManagement 218.0.0 com.apple.kext.triggers 1.0 com.apple.driver.AppleSMBusController 1.0.14d1 com.apple.iokit.IOSMBusFamily 1.1 com.apple.iokit.IOSerialFamily 11 com.apple.iokit.IOBluetoothFamily 4.4.4f4 com.apple.iokit.IOSurface 108.2.1 com.apple.driver.CoreCaptureResponder 1 com.apple.driver.X86PlatformPlugin 1.0.0 com.apple.driver.AppleSMC 3.1.9 com.apple.driver.IOPlatformPluginFamily 6.0.0d7 com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0 com.apple.iokit.IOAcceleratorFamily2 205.3 com.apple.AppleGraphicsDeviceControl 3.12.6 com.apple.iokit.IONDRVSupport 2.4.1 com.apple.iokit.IOGraphicsFamily 2.4.1 com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.7 com.apple.iokit.IOUSBMassStorageDriver 1.0.0 com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7 com.apple.driver.AppleUSBAudio 303.3.1 com.apple.iokit.IOUSBHIDDriver 900.4.1 com.apple.driver.usb.cdc 5.0.0 com.apple.driver.usb.networking 5.0.0 com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1 com.apple.driver.usb.AppleUSBHub 1.0.1 com.apple.iokit.IO80211Family 1110.26 com.apple.iokit.IONetworkingFamily 3.2 com.apple.driver.corecapture 1.0.4 com.apple.iokit.IOUSBFamily 900.4.1 com.apple.driver.AppleEFINVRAM 2.0 com.apple.iokit.IOAudioFamily 204.3 com.apple.vecLib.kext 1.2.0 com.apple.iokit.IOAHCIFamily 2.8.1 com.apple.driver.usb.AppleUSBEHCI 1.0.1 com.apple.driver.usb.AppleUSBXHCIPCI 1.0.1 com.apple.driver.usb.AppleUSBXHCI 1.0.1 com.apple.iokit.IOUSBHostFamily 1.0.1 com.apple.driver.AppleUSBHostMergeProperties 1.0.1 com.apple.driver.AppleEFIRuntime 2.0 com.apple.iokit.IOHIDFamily 2.0.0 com.apple.security.sandbox 300.0 com.apple.kext.AppleMatch 1.0.0d1 com.apple.driver.AppleKeyStore 2 com.apple.driver.AppleMobileFileIntegrity 1.0.5 com.apple.driver.AppleCredentialManager 1.0 com.apple.driver.DiskImages 417.2 com.apple.iokit.IOStorageFamily 2.1 com.apple.iokit.IOReportFamily 31 com.apple.driver.AppleFDEKeyStore 28.30 com.apple.driver.AppleACPIPlatform 4.0 com.apple.iokit.IOPCIFamily 2.9 com.apple.iokit.IOACPIFamily 1.4 com.apple.kec.Libm 1 com.apple.kec.pthread 1 com.apple.kec.corecrypto 1.0 Model: iMac13,2, BootROM IM131.010A.B05, 4 processors, Intel Core i7, 3,5 GHz, 16 GB, SMC 2.11f14 Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In Graphics: NVIDIA GeForce GTX 760, NVIDIA GeForce GTX 760, PCIe, 2047 MB Memory Module: BANK0/DIMM1, 8 GB, DDR3, 2133 MHz, Geil, CL10-11-11D3-2133 Memory Module: BANK1/DIMM1, 8 GB, DDR3, 2133 MHz, Geil, CL10-11-11D3-2133 AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9287: Network Service: Ethernet, Ethernet, en2 Serial ATA Device: OCZ-VERTEX4, 256,06 GB Serial ATA Device: ST2000DL003-9VT166, 2 TB Serial ATA Device: ST9750420AS, 750,16 GB Serial ATA Device: ST9750420AS, 750,16 GB USB Device: USB 2.0 Bus USB Device: Hub USB Device: Mass Storage Device USB Device: USB 2.0 Bus USB Device: Hub USB Device: USB Keyboard USB Device: Composite Device USB Device: USB 3.0 Bus USB Device: Hub USB Device: Hub USB Device: Monitor Webcam USB Device: G500 Thunderbolt Bus: