Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About TheBloke

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
  • Location
    Brighton, UK

Recent Profile Visitors

264 profile views
  1. Clover General discussion

    Having the ability to block specific kexts in config.plist means I can save configuration files with certain sets of multiple config for testing which includes whether kexts are loaded or not: configA = setting1 + setting2 + kextA loaded; configB = setting1 + setting2 + kextA not loaded; configC = setting3 + kextA loaded; configD = setting3 + kextA not loaded. etc. Then each test can be run just by putting the next config in, and any past test can be repeated just by copying a single file that is already prepared. The configs can be named exactly for everything that is tested, so when I copy "config.setting2.setting3.kextA-notloaded.plist" I know everything it does - there is not required a separate external step (modifying kexts/Other, or interrupting boot to disable the kext) required to make this test correct. I know the manual methods to do this, that's what I have been doing recently - eg scripting the copying of kexts in and out of kexts/Other along with copying a specific config.plist (or an alternative - make multiple USB sticks with varying kext/Other folders.) I just feel that it would be a little cleaner and more manageable to be able to control everything from config.plist. Obviously you do not agree and I do not want to argue with you. Certainly it is not hugely important. But I know that if it existed I would definitely make use of such a feature next time I needed to debug my system with/without kexts.
  2. Clover General discussion

    1. I wanted variable kext loading for the same machine, not two different machines. 2. I wanted to disable loading of specific kexts, but not all. Disabling all kext loading will not help, in fact it would stop me booting at all. I won't open a ticket but I believe the feature request is valid - in the case of WEG it is possible to disable it via a boot flag, but this does not help in the case of other Kexts. For example, yesterday I wanted to test loading with and without FakeSMC_GPUSensors. As there is no way to do this via different config files, I must either delete this kext from EFI/CLOVER/Kexts/Other, or else continually interrupt boot to choose Block Kexts. It would definitely be useful to have this in a config.plis variable.
  3. Clover General discussion

    Oh yeah! Of course, that would work fine for WEG. Thanks, I forgot about that. I still think it would be helpful if Clover had this option in config.plist for other kexts - but yeah, no need for WEG Which is the only kext I need to do it for at the moment anyway.
  4. Oh, and more importantly the UI seems more responsive again. It seemed slower and jerkier when I went from 10.13.3 to 10.13.4 B5, but now on B6 I think (hope) it's back to normal AMD levels.
  5. Clover General discussion

    Yeah it seems not. I will raise it as a feature request on the tracker. Thanks.
  6. Clover General discussion

    Ahh yes that's the name - thanks. But do you know if there is a config.plist name for "Block injected kexts" ? So that kexts can be disabled permanently in a config file? I think maybe this Block option is only available from Boot menu, and can't be configured in config.plist? At least I can't find any name for this option in the Wiki or via Google.
  7. Clover General discussion

    Is there any way to get Clover to block loading of a Kext in EFI/CLOVER/kexts/Other? For example if I want to make two config files, one that loads WhateverGreen and one that does not. I have read through the Wiki and can't find such an option. But when I go to Options in the boot GUI, there is an option with a name that seems to suggest it might do this. I know Clover can't stop loading of kexts on the OS drive, but presumably it could theoretically prevent them loading from EFI/CLOVER/kexts? If it can't do this now, this would be a nice feature to add I think. Thanks.
  8. Beta 6 installed here on X58 legacy without issues. Noticed a couple of minor things: My Philips 4K TV is now correctly detected as 4K, and not 8K (I wish!) I'm not sure if the mis-detection at 8K started in 10.13.3 or 10.13.4, but it was definitely mis-detected in 10.13.4 Beta 5 and is working fine now. (It didn't really affect much anyway, as it still defaulted to 4K resolution in Scaled mode.) I can get working HDMI/DP audio on my Radeon 7970 / R9 280X if I boot with WhateverGreen installed. Without it I have no HDMI, same as 10.13.3 - tested both with and without Clover's InjectATI Unfortunately booting with WEG has a ~75% chance of not reaching the login screen - it hangs after the end of the Apple logo progress bar. This problem started in 10.13.4; WEG worked fine in 10.13.3 So given I don't really need HDMI Audio anyway, I am not using WEG at the moment.
  9. Excellent! Looking forward to seeing what it brings (or breaks )
  10. restore deleted files APFS

    Sorry to hear that. Stupid question: are you certain the Desktop content was deleted? Did you do it yourself (selected it all and hit delete), or did you just find it gone? I am just wondering if there's any chance it got moved somewhere instead of deleted. If you can't be 100% certain it was definitely deleted, you could try searching the drive for a known filename. Eg in Terminal: find /Volumes/drivename/Users/YourName -iname "*filename*" - replacing 'filename' with some part of a filename you know is missing. Probably no good, but worth a try unless you actually saw the data being deleted. If not, maybe the fact that recovery tools can't find any of the files, and show you files that shouldn't be deleted, indicates some problem/corruption with the APFS filesystem, which in turn caused data loss Final thought: have you tested to see if you can roll the drive back to an earlier APFS snapshot? This guide shows you how - it uses Time Machine from the Recovery partition. You don't have to have used Time Machine in order to do this - macOS will automatically create APFS snapshots in certain situations. See step 3 of the following guide: https://www.lifewire.com/roll-back-apfs-snapshots-4154969
  11. Clover General discussion

    Yeah I reported it to mackie and it's fully working now.
  12. [HOW TO] Modification of AMD FB + Clover injection

    I'm still struggling to find a way to get my 6-connector Asus Matrix 7970 (Ghz Edition / R9 280X) working from boot. I'm now on 10.13.4 beta, and that changed three things for me: doubled my OpenCL and Metal benchmark scores, enabled me to wake from sleep without WEG, and also initially gave me OOB working HDMI/DP Audio (later stopped working, I think maybe only worked in Beta 3 and stopped in Beta 5.) I still have to sleep&wake after every boot in order to get a picture from all GPU ports. From boot I have signal on all monitors, but a picture on only two. After sleep/wake I get picture on all. I'm starting to think that patching might not be possible for me, based on what @Vlada. said here: I can get this situation only with RadeonFramebuffer. If I choose any FB from AMD7000, the best I can get is four monitors with signal, and the other one or two no-signal. I cannot improve that with any patches I've tried, which matches what VladA said about needing to find the right FB. Is there any way to patch RadeonFramebuffer? Because with that one I do get a signal on all monitors - tested with all six ports. I've tested all the 6-connector 7000 FBs available - IkuraS, Junsai, KaniS, MaguroS, OPM, Ramen and Tako. The latter three don't reach Login. The others - IkuraS, Junsai, KaniS and MaguroS - give me 4 connectors with signal, the others no-signal. I've set Clover's VideoPorts to 6, and I see 6 ports in IORegExplorer, but I can never get signal on more than four. (If I don't set VideoPorts, I only see 5 connectors in IOReg - this might be because Clover defaults to 5 ports if VideoPorts isn't set.) So based on what VladA said, it seems I'm stuck - there's no patchable FB which gives me a signal on all ports, only RadeonFramebuffer does that, but as it's not part of AMD7000Controller I can't patch it? I've tested with and without WEG and with and without RadeonDeInit. DeInit doesn't seem to change anything. WEG renames the GPU to GFX0 in IoReg but doesn't change anything else in 10.13.4. InjectATI also doesn't seem to do anything other than enabling use of other FBs, which isn't helping me. Booting with InjectATI=Yes + FBName=Radeon seems identical to InjectATI=No. I still haven't tried an SSDT, because I'm no longer sure if that's even a solution to this problem - I re-read Mieze's thread and she says specifically her SSDT patches are only for fixing wake-up issues, not a replacement for FB patching. I did have wakeup issues in 10.13.3 which I fixed with WEG, but in 10.13.4 they seem to be gone. I have read of a couple of people talking about SSDTs for connector patching as well, but I think not conclusively. Unless I've missed something there - quite possible! If anyone has any further ideas, I'd be very grateful. Worst case I can just live with the situation I have now, because it's not so terrible having to sleep&wake each boot. But it bothers me I can't get everything working 100% PS. One final piece of info - if I boot with an extra NVidia GPU installed and primary in BIOS, all my AMD ports get signal and picture from boot. I think this is known and expected, but adding it just in case it's useful info. I can't use an extra GPU normally as I'm short on PCIe slots.)
  13. restore deleted files APFS

    This software says it restores deleted files on APFS: https://iboysoft.com/mac-data-recovery/apfs-data-recovery.html In order to maximise the chance of getting data back, you need to stop using that drive immediately. Every time disk writes happen, they could be overwriting your deleted data, making it impossible to restore. Ideally you would install the above data recovery software to a different bootable macOS HDD/SSD and then mount the disk with lost data as a secondary before trying to restore it. If that's not possible, at least minimise disk writes before you install and use the recovery software.
  14. Clover General discussion

    I read a few (old) posts indicating that this might be necessary on X58 motherboards. I know AppleTyMCEDriver is related to ECC memory. The MacPro 5.1 system used X58 with ECC RAM, and I've read discussion of needing to patch AppleTyMCEDriver if you don't use ECC RAM (as I don't). I've also read discussions of -nehalem_error_disable being needed sometimes, to prevent certain errors. I can't remember which ones now, but maybe again related to ECC. I don't think you need the flag. I added it because I was getting strange crashes and errors post-boot, so I was looking for anything that might be wrong. I've since resolved my errors/crashes (a bad DIMM), so it wasn't anything to do with adding that flag that fixed it. So as far as I can tell, adding -nehalem_error_disable has made zero difference to my system (positive or negative). In fact I am not even using the flag any more - I removed it a week or so ago when I was adding another flag, and nothing is different that I can see. Maybe whatever problem the flag solved is no longer an issue in High Sierra. Or maybe it's something that Clover now fixes automatically. Or maybe it was never needed at all and was just misinformation. I wouldn't bother about it at all, unless you have errors related to ECC, which I doubt you do. HWMonitor, as bundled with RehabMan's version of kozlek's FakeSMC. EDIT: Another way to see them is iStat Menus (although the info is slightly odd, in that the listed frequencies don't match the listed multipliers on a core-by-core basis, and, at least for me, one of the cores is called 'Core 18'. But the listed multipliers do generally match what HWMonitor is showing):
  15. One final update: After removing the 980Ti I did a brief test using my NVidia 760 instead, so that I could test with the Native drivers. Everything was functionally identical to Test 3 and Test 4 above - ie it works both with NV and AMD as first GPU, but it's not possible to use both GPUs for extra connections as any monitor connected to the NV causes an instant WindowsServer crash. There was also a seeming performance issue when the AMD was first GPU: it took an age to reach the login screen, and the UI seemed particularly slow once I did login. This problem did not repeat when NV was first GPU. I did not test it for more than one reboot so cannot say if it's a permanent problem. In any case this shouldn't be a problem, both because one could simply use NVidiaWeb drivers instead, and because it's unlikely someone will be keeping an idle secondary GPU that can use Native drivers, as it'd have to be pretty old and thus not really worth keeping for Windows. Also, a correction regarding HDMI/DP Audio: I've just booted with only my AMD and I still don't have working HDMI/DP audio. I definitely had it working when I first upgraded to the 10.13.4 beta, so I'm not sure what's changed, but it's seemingly not related to the addition of an NV GPU.