Jump to content

Gorelander

Members
  • Content count

    38
  • Joined

  • Last visited

About Gorelander

  • Rank
    InsanelyMac Protégé
  1. Thanks for your reply. I am using clover, and not hot-plugging TB3. As many have said you need to have it plugged in before you boot which I have tried, and I have also booted into Windows first to wake it up then boot into MacOS. I haven't tried plugging in at the clover screen yet - will try next chance I get. I have a feeling that I'm missing some sort of TB3 kext. Does anyone know what I should have for kexts to enable TB3?
  2. Has anyone tried thunderbolt with this build? I've been using a WD15 dock fine via the USBC port although the WD15 is USB. I'm on OSX 12.6.4. Today I tried a couple thunderbolt audio interfaces (Focusrite Clarett, Universal Audio Apollo - both TB1 I believe) and they can't be seen by MacOS (either by the installed driver, or system info). Of course, booting into Windows everything works fine. The evidence leads me to believe that there's a kext I need, or something I need to patch in order to enable TB over MacOS.
  3. Hey guys, If anyone is looking for a docking solution, I bought the Dell WD15 and it works well with MacOS 12.6. Single cable charging and data is a dream come true. MacOS sees all the devices on the dock (including audio) and everything works. The only issue is with the ethernet port. For some reason MacOS will only grab a self-assigned IP although the device shows up fine. I'm going to try to delete all the network plists and see if it comes alive. It's not a big deal if I can't get it to work as the wifi works fine. I also bought the Dell U3415 monitor which includes KVM switching. The WD15 outputs HDMI and USB to the monitor and is met with similar ports from my gaming PC (which is also a hackintosh). With the KVM switching you can have a single keyboard, mouse and other USB peripherals (I have an audio interface) shared between both computers and switch back and forth via the monitor. It also supports different types of picture in picture and you can view the output of both computers at the same time.
  4. I think this topic is for the SD cards so you'll have to "get in line".
  5. Ok thanks for trying. Even if it can get to the point where you can just shut down to eject (but be able to read cards) would be a step in the right direction.
  6. What if you powered up the machine with a card in it? If that worked it would be a start, and would provide some usefulness IMO.
  7. Looking for a better touchpad driver I came across this cypress one: https://github.com/ulysse31/voodoops2controllercypress It looks interesting as there is a Preferences Pane component for configuration. Has anyone tried it for the 9560? I did try to install it and remove any conflicting kexts but it causes crashes on boot for me. It would be nice to find a smoother scrolling touchpad, or one that does pinch-to-zoom.
  8. Thanks for you reply. Do you think patching it would correct the issue described? Thanks for the tip RM, I patched in Clover Configurator, removed NvidiaGraphicsFixup.kext, and now both the brightness control and HDMI out works.
  9. Updating the nvidiagraphicsfixup.kext causes MacOS screen brightness controls to become non-existent. The keyboard shortcuts stopped working, and there is no slider in display preferences. So I rolled back to the original nvidiagraphicsfixup.kext included in this guide which fixes the display brightness controls, but again, the HDMI out port stopped functioning. This implies that the nvidiagraphicsfixup.kext included in this guide doesn't work with the HDMI port, but I recall testing it beforehand. Can someone test their HDMI out and see if it works with the kext included in this guide? If this kext is working for everyone else, I can only guess that my lilu update to get the DW1560 working has somehow broken the functionality of nvidiagraphicsfixup.kext causing the HDMI port to stop working. Any insight to which version of this kext I should be using would be greatly appreciated. .
  10. FYI, unsigned kext messages are normal. It's a hackintosh it's going to have non-official kexts loading.
  11. I updated from 12.4 to 12.6 and thought everything was working well until I tried my HDMI again and it stopped working. Sigh. Researched on another thread that nvidiagraphicsfixup.kext was responsible for HDMI out and that it might also be lilu dependent. Updated to latest version of nvidiagraphicsfixup.kext and it's working again. Happy day!
  12. Hey guys, is anyone else experiencing intermittent crashes on boot after the clover boot screen? It doesn't happen very often, but upon booting the laptop, it gets to the clover login screen, then spits out a ton of text and reboots itself. The next boot is always fine. I remember reading someone else with the same problem, but heck if I can find where I read it. It reboots itself so quickly that I don't have time to read what it's complaining about. I haven't been able to determine any pattern which causes it either. Would the preboot.log offer any info on this crash?
  13. This afternoon I booted up my Mac and noticed weird graphic artifacts plus my wifi and audio stopped working. Thinking MacOS updated on it's own, I reinstalled as Jonny4911 described: Lilu.kext, AppleALC.kext, and CoreDisplayFixup.kext. After updating caches everything was fine again. However surprisingly, when I checked the App store program, it didn't list any completed MacOS updates so I'm not sure what happened. I think I figured it out. I had re-enabled SIP which I'm assuming stops the loading of unsigned kexts (the kexts for the audio, videodisplayfix, and wifi). This time around I changed the CSR-active-config to partially enabled (0x3). Please let me know if this doesn't make sense.
  14. That worked KNNSpeed, thanks for all your efforts. Thanks also to Blazinsmokey who helped me discover I was missing BcrmFirmwareRepo.Kext. From my experience, in order to get the DW1560 to work requires the following kexts: FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, BrcmPatchRAM2.kext, and BrcmFirmwareRepo.kext. However, lilu.kext (version 1.1.4) included in this guide was too old to work with BrcmFirmwareRepo.kext. Updating lilu.kext (to version 1.2.0) breaks the audio (included in this guide) and requires AppleALC.kext to be updated from 1.1.2 to 1.2.2. Throwing these kexts in S/L/E and rebuilding caches in terminal will show if there are any dependency issues: sudo kextcache -i / I just thought I would document this in case anyone else was having issues.
  15. It seems that throwing the new Lilu.kext enabled AirportBrcmFixup.kext but broke AppleALC.kext (and the audio). For interest's sake I installed the AppleALC.kext and Verbstub.kext into SLE with the lilu.kext and this is what it said: AppleALC.kext - no compatible dependency found for as.vit9696.Lilu So the lilu.kext that enables the wifi, won't work with the audio. Strange.
×