Jump to content

Dmos

Members
  • Content Count

    99
  • Joined

  • Last visited


Reputation Activity

  1. Haha
    Dmos got a reaction from Allan in OSx86.net is Down   
    Osx86.net online now! iPB is killing forums like madman
  2. Haha
    Dmos got a reaction from Allan in OSx86.net is Down   
    Osx86.net online now! iPB is killing forums like madman
  3. Haha
    Dmos got a reaction from Allan in OSx86.net is Down   
    Osx86.net online now! iPB is killing forums like madman
  4. Haha
    Dmos got a reaction from Allan in OSx86.net is Down   
    Osx86.net online now! iPB is killing forums like madman
  5. Haha
    Dmos got a reaction from Allan in OSx86.net is Down   
    Osx86.net online now! iPB is killing forums like madman
  6. Like
    Dmos reacted to fantomas1 in OSx86.net is Down   
    I think I already saw a such message before (server issue, forum update) and the forum has always been back. And I'm sure it will be the case again.  ;)
  7. Like
    Dmos got a reaction from Allan in A "macOS" reference discovered in 10.11.4   
    So apple going .. back to the past
  8. Like
    Dmos got a reaction from Allan in A "macOS" reference discovered in 10.11.4   
    So apple going .. back to the past
  9. Like
    Dmos got a reaction from Allan in A "macOS" reference discovered in 10.11.4   
    So apple going .. back to the past
  10. Like
    Dmos got a reaction from Allan in A "macOS" reference discovered in 10.11.4   
    So apple going .. back to the past
  11. Like
    Dmos got a reaction from MaLd0n in Where's MaLd0n?   
    Welcome back "Mald0n - The Mackintosh  Legend"
     looking forward to some new DSDT fixes FTW!! 
  12. Like
    Dmos got a reaction from MaLd0n in Where's MaLd0n?   
    Welcome back "Mald0n - The Mackintosh  Legend"
     looking forward to some new DSDT fixes FTW!! 
  13. Like
    Dmos got a reaction from Extravaganso in building DSDT for MSI Z170A Gaming M3   
    I'm not an expert on DSDT but in your first dsdt i see only 2 errors about Arg0..3 
    Are u using ACPI 4.0 ?
  14. Like
    Dmos got a reaction from fantomas1 in NVIDIA Web Driver Updater   
    Nice and handy 
  15. Like
    Dmos got a reaction from fantomas1 in NVIDIA Web Driver Updater   
    Nice and handy 
  16. Like
    Dmos reacted to Slice in Clover Change Explanations   
    Rev 3250
     
    New runtime variables needed for El Capitan and Yosemite.
    <key>RtVariables</key> <dict> <key>CsrActiveConfig</key> <string>0x67</string> <key>BooterConfig</key> <string>0x28</string> </dict> Bit definitions are follow
    For CsrActiveConfig
    /* Rootless configuration flags */ #define CSR_ALLOW_UNTRUSTED_KEXTS (1 << 0) #define CSR_ALLOW_UNRESTRICTED_FS (1 << 1) #define CSR_ALLOW_TASK_FOR_PID (1 << 2) #define CSR_ALLOW_KERNEL_DEBUGGER (1 << 3) #define CSR_ALLOW_APPLE_INTERNAL (1 << 4) #define CSR_ALLOW_DESTRUCTIVE_DTRACE (1 << 5) /* name deprecated */ #define CSR_ALLOW_UNRESTRICTED_DTRACE (1 << 5) #define CSR_ALLOW_UNRESTRICTED_NVRAM (1 << 6) #define CSR_VALID_FLAGS (CSR_ALLOW_UNTRUSTED_KEXTS | \ CSR_ALLOW_UNRESTRICTED_FS | \ CSR_ALLOW_TASK_FOR_PID | \ CSR_ALLOW_KERNEL_DEBUGGER | \ CSR_ALLOW_APPLE_INTERNAL | \ CSR_ALLOW_UNRESTRICTED_DTRACE | \ CSR_ALLOW_UNRESTRICTED_NVRAM) For example bit 0 (value 0x01) allows to use unsigned kexts from /Library/Extensions folder.
     
    For BooterConfig there are flags
    /* Bitfields for boot_args->flags */ #define kBootArgsFlagRebootOnPanic (1 << 0) #define kBootArgsFlagHiDPI (1 << 1) #define kBootArgsFlagBlack (1 << 2) #define kBootArgsFlagCSRActiveConfig (1 << 3) #define kBootArgsFlagCSRPendingConfig (1 << 4) #define kBootArgsFlagCSRBoot (1 << 5) #define kBootArgsFlagBlackBg (1 << 6) #define kBootArgsFlagLoginUI (1 << 7) This flags is analyzed by boot.efi not by kernel and present in boot_args that read by kernel.
    Yosemite kernel has follow usage of this flag
    int csr_get_active_config(csr_config_t *config) { boot_args *args = (boot_args *)PE_state.bootArgs; if (args->flags & kBootArgsFlagCSRActiveConfig) { *config = args->csrActiveConfig & CSR_VALID_FLAGS; } else { /* XXX: change to 0 when <rdar://problem/16239698> is in the build */ *config = CSR_ALLOW_APPLE_INTERNAL; } return 0; } Setting the bit 0x20 is equivalent to kernel flag "rootless=0" (Yosemite kernel)
    void csr_init(void) { boot_args *args = (boot_args *)PE_state.bootArgs; if (args->flags & kBootArgsFlagCSRBoot) { /* special booter; allow everything */ csr_allow_all = 1; } int rootless_boot_arg; if (PE_parse_boot_argn("rootless", &rootless_boot_arg, sizeof(rootless_boot_arg))) { /* XXX: set csr_allow_all to boot arg value for now * (to be removed by <rdar://problem/16239861>) */ csr_allow_all = !rootless_boot_arg; /* if rootless=1, do not allow everything when CSR_ALLOW_APPLE_INTERNAL is set */ csr_allow_internal &= !rootless_boot_arg; } } There is still the question what is changed in El Capitan as we have no the sources.
  17. Like
    Dmos reacted to fantomas1 in NVIDIA Web Driver Updater [UPDATE: 07/18/2016]   
    NVIDIA Web Driver Updater
    © InsanelyMac
    application for downloading Retail & Beta!!! Nvidia Web Driver versions

    Enjoy!
    With special thanks to: Micky1979
    Please, download the app from our "Download Section"
    See more captures:
     
  18. Like
    Dmos got a reaction from fantomas1 in Mafia II: Director's Cut   
    hmm ....looks like i need to download this game  again
  19. Like
    Dmos got a reaction from marcnw in PC wont boot Niresh-Maverick after successful partition   
    Very long explanation and its good for fix issues. First of all you have and amd system,so lot depends on amd kernel and some of GPU bugs comes of kernels.
    You need to use right kernel that works on your system.
     
    2nd your installation method is kinda tricky. find out what kernel ur using
    for nvidia driver try this...
    http://www.hackintoshosx.com/topic/22774-nvidia-graphics-web-drivers-installation-guide/?p=119821
  20. Like
    Dmos got a reaction from fantomas1 in Apple release final version of OS X 10.10.5   
    .S/N hacked     . Is this real S/N ? 
  21. Like
    Dmos got a reaction from fantomas1 in Apple release final version of OS X 10.10.5   
    .S/N hacked     . Is this real S/N ? 
  22. Like
    Dmos got a reaction from fantomas1 in Mafia II: Director's Cut   
    Man mafia II     'why u want to play games with them' ,Do not play with fire
     
    Nice game though, i never played in osx.
  23. Like
    Dmos reacted to Download-Fritz in Clover General discussion   
    Haha, chill, it's all good. I just didn't see the direct purpose of this PoC to be honest.
    That kext signature is only checked when creating the cache and not from cache itself has been known since it was introduced in OS X Yosemite. You could boot with kext-dev-mode, create the cache with unsigned kexts and reboot without the flag fine. And in my opinion, the PoC is pretty much the same except for the fact that the file path is changed. No offense meant to anyone though, just my direct thoughts. Correct me all day if you want, but I ask you to do it in a proper way instead of accusing me of assuming things I did not, e.g. that the idea is not good which I said in no direct way.
     
    I will play around with stuff and see if I'm capable of writing up some code to append kexts to the prelinkedkernel in-memory, though don't count on me. Beside being a little busy with other stuff, I'm also mostly unexperienced.
     
    EDIT: I saw Mr. Alpha edited his blog post saying the information was pretty unknown and saying it after he published his post is unfair. If it was known, it would have been implemented in Chameleon or Clover, right? Well... I always wondered, what business do the boot solutions have setting or managing Apple NVRAM variables? They are supposed to deliver features that the user didn't have before, though editing NVRAM is not one of them in my opinion. If the user wants kext-dev-mode enabled, the user can set it (either via hardware NVRAM, FileNVRAM, EmuVariableDrv or whatever). If he doesn't want it, he can just not set it. I always hated it when the boot solution thought it knew better than me and didn't let me manage the setup the way I wanted it (though recently I'm quite happy )
    Anyways, I didn't use Mavericks in ages and Yosemite not since El Capitan was out. I can't proof it, but I have no reason to lie. That piece of knowledge is not rocket science but an experiment of boredom maybe lasting 5 minutes. I saw quite a few users in chat saying they did it that way and being so happy they didn't need to use the flag after.
  24. Like
    Dmos reacted to Allan in How to enable iMessage   
    Precautions for sharing MLB/ROM after Apple's introduction of system-id blocking
     
    Recommendations
    Consider generating unique MLB/ROM (with correct pattern/format) for your hacks and registering them by calling Apple Support Cloning a Mac's MLB/ROM for your hack should only be done if you own the Mac whose MLB/ROM you are intending to use. Ideally, take MLB/ROM from an older Mac that has been “retired” from service If you want to continue with cloned values on your hack, its prudent to take extra precautions to protect the "donor" Mac IDs from blacklisting caused by mismatches on your hack Never share MLB/ROM values publicly Try not to have more than one machine connected to the internet and logged into iMessage/FT at the same time (using the same MLB/ROM). If you want to connect both hack and Mac to the internet at the same time, make sure to logout of iMessage/FT on one of them. To prevent Apple flagging ID mismatches, make the cloned system match the original Mac more closely - at a minimum, MLB/ROM & system-id. Procedure
    1. Run imessage_debug V2 on the real Mac to obtain system-id, MLB, ROM etc
    2. Logout of iMessage & iCloud on hack
    3. Disconnect from internet
    4. Edit config.plist on hack so at a minimum you have matching the real Mac
         * MLB in RtVariables/config.plist
         * ROM in RtVariables/config.plist
         * CustomUUID in System Parameters/config.plist = System-ID of Mac, set inject system-id to true.
         * If cautious, change board-id and system serial in SMBIOS/config.plist to real Mac's value also
    Note: changing ProductName/Mac Model to a different SMBIOS (eg to the same as the original Mac) may affect power management/sleep and other functions on the hack.
     
    5. Run imessage_debug V2 on the hack to confirm new values
    6. Reconnect internet
    7. Login to iMessage and iCloud on hack

    Finally, if your Mac's MLB/ROM is blacklisted, there is no need to panic if you are its rightful owner. Contact Apple Support - that is what they are there for   .
  25. Like
    Dmos reacted to fantomas1 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    hi
     
    ok guys,
     
    you can use this thread to link / talk about of the futur Nvidia Web Driver updates for Yosemite
     
     
    10.10.5
     
    Nvidia Web Driver - 346.02.03f14 --> build 14F2511 (thanks to core2quad)  New!
     
    Nvidia Web Driver - 346.02.03f13 --> build 14F2411 (see this post)
     
    Nvidia Web Driver - 346.02.03f12 --> build 14F2315 (see this post)
     
    Nvidia Web Driver - 346.02.03f11 --> build 14F2109 (see this post)
     
    Nvidia Web Driver - 346.02.03f10 --> build 14F2009 (see this post) 
     
    Nvidia Web Driver - 346.02.03f09 --> build 14F1912 (thanks to BreBo)
     
    Nvidia Web Driver - 346.02.03f08 --> build 14F1909 (thanks to WeBeRiO) 
     
    Nvidia Web Driver - 346.02.03f07 --> build 14F1808 (thanks to WeBeRiO)  
     
    Nvidia Web Driver - 346.02.03f06 --> build 14F1713 (thanks to Riley Freeman)
     
    Nvidia Web Driver - 346.02.03f05 --> build 14F1605 (thanks to WeBeRiO)  
     
    Nvidia Web Driver - 346.02.03f04 --> build 14F1509 (thanks to marcozardi)
     
    Nvidia Web Driver - 346.02.03f03 --> for build 14F1505 (thanks to slim.jim) 
     
    Nvidia Web Driver - 346.02.03f02 --> 10.10.5 (build 14F1021) second public release (thanks to Riley Freeman) 
     
    Nvidia Web Driver - 346.02.03f01 --> 10.10.5 (build 14F27) first public release (see here)
     
    Nvidia Web Driver - 346.02.03b01 --> 10.10.5 first beta release (thanks to MTWomg)  
     

     
    10.10.4
     
    Nvidia Web Driver - 346.02.02f03 --> 10.10.4 third public release (thanks to Vampirexx)  
     
    Nvidia Web Driver - 346.02.02f02 --> 10.10.4 second public release (thanks to Vampirexx)  
     
    Nvidia Web Driver - 346.01.03f01  --> 10.10.4 first public release (thanks to Vampirexx)  
     
    Nvidia Web Driver - 346.01.03b01 --> 10.10.4 build 14E26a (thanks to netkas and MTWomg)  
     

     
    10.10.3
     
    Nvidia Web Driver - 346.01.02f04 --> 10.10.3 fourth public release (thanks to SummerRain) 
     
    Nvidia Web Driver - 346.01.02f03 --> 10.10.3 third public relase (thanks to marcozardi) 
     
    Nvidia Web Driver - 346.01.02f02 --> 10.10.3 second public release (thanks to lukazm) 
     
    Nvidia Web Driver - 346.01.02f01 --> 10.10.3 first public release (thanks to lukazm) 
     
    Nvidia Web Driver - 346.01.02b01 --> 10.10.3 build 14D130a (thanks to horizoli) 
     
    Nvidia Web Driver - 343.02.03b04 --> 10.10.3 build 14D105g (thanks to zhuangzi23) 
     

     
    10.10.2
     
    Nvidia Web Driver - 346.01.01f01 --> 10.10.2 fifth public release (thanks to duggum)
     
    Nvidia Web Driver - 343.02.02f04 --> 10.10.2 (build 14C1514) fourth public release (thanks to Vampirexx) 
     
    Nvidia Web Driver - 343.02.02f03 --> 10.10.2 (build 14C1510) third public release (thanks to lukazm)
     
    Nvidia Web Driver - 343.02.02f02 --> 10.10.2 second public release (thanks to Mela quadrata)
     
    Nvidia Web Driver - 343.02.02f01 --> 10.10.2 build 14C109 (thanks to archfan)
     
    Nvidia Web Driver -343.02.02b04  --> 10.10.2 build 14C94b (thanks to ddani)
     
    Nvidia Web Driver - 343.01.03b01 --> 10.10.2 build 14C68k (thanks to netkas)
     

     
    10.10.1
     
    Nvidia Web Driver - 343.02.01f01 --> 10.10.1 third public release (thanks to rednous)
     
    Nvidia Web Driver - 343.01.02f03 --> 10.10.1 second public release (thanks to jamilitia)
     
    Nvidia Web Driver - 343.01.02f01 --> 10.10.1 public release (thanks to luele)
     
    Nvidia Web Driver - 343.01.02b02 --> 10.10.1 build 14B23 (thanks to Rominator) --> works fine with the public release (build 14B25)
     
    Nvidia Web Driver - 343.01.02b01 --> 10.10.1 build 14B17 (thanks to cmf)
     

     
    10.10.0
     
    Nvidia Web Driver - 343.01.01f03
     
    Nvidia Web Driver - 343.01.01f02 (with OpenCL fix?) --> (thanks to Joao Paulo Mello)
     
    Nvidia Web Driver - 343.01.01f01 (maxwell support) --> 10.10.0 (14A389)      (thanks to Moviemakergr)
     

     
    GM & PB
     
    Nvidia Web Driver - 343.01.01b04 --> GM Candidate 3.0 (14A388a) 
     
    Nvidia Web Driver - 343.01.01b03 --> Public Beta 5 (14A386b)
     
    Nvidia Web Driver - 343.01.01b02 --> GM Candidate 2.0 (14A386a)
     
     
     
    Credits go to Rominator & Netkas 
×