Jump to content

peanutman314

Members
  • Content Count

    9
  • Joined

  • Last visited

About peanutman314

  • Rank
    InsanelyMac Protégé
  1. Thank you very much for the help! I would like to learn to do this myself. May I ask what you changed?
  2. In attachment you will find the DSDT. The slot I would like to disable is _SB.PCI0.RP09 (or _SB.PCI0.RP09.PXSX ?). I have no idea if I'm looking for a DSDT or SSDT patch. I found references to _SB.PCI0.RP09 in the DSDT and in SSDT files 1, 5, 6 and 8. In IOReg it looks like this. Any help would be greatly appreciated. dsdt.zip
  3. That's not a bad idea, I will try this. Thank you for the suggestion. However, I'm not sure if this will fix the problem. It's not very clear if accessing the disk causes problems, or if simply having the disk in your motherboard is the issue. I'm just basing myself on the many many reports coming from other users and people only mention "incompatible firmware" as a reason.
  4. As you might know the Samsung 970 EVO Plus variant causes major issues on hackintosh installs. I want to keep it plugged into my motherboard for use in Windows. However, if it's plugged in, macOS is going to try to index this disk eventually and it will crash macOS even though it's not the main install disk. Because I don't need this disk under macOS I thought it would be a good solution to somehow disable/hide the unsupported disk for macOS. I looked into doing this via Clover but couldn't find anything useful. I'm hoping I can disable the slot via a DSDT patch. I only want to disable one specific M.2 slot, the others should remain functional (I have another working M.2 disk). So disabling the driver is not an option.I have very little experience with DSDTs and I have no idea how to do this. I recently created a USB injection patch using RehabMan's excellent guide, so I have some experience with the process, but no idea how to formulate the DSDT patch. I have a Gigabyte Aurus Pro z390 motherboard. Below is a screenshot of IORegistryExplorer showing the other working drive (not the one I want to disable, that one is not plugged in yet). I would be very grateful if anyone can point me in the right direction. If anyone knowns of a non-DSDT solution to disable a specific slot (but not all slots) then that's also fine of course. Thank you for your time
  5. Thank you very much for this guide. Without knowing about your guide I bought the same motherboard and similar other hardware. I was expecting to have to do a few days of trial and error. Instead I found this awesome guide where most of the research has already been done. I love how your guide is so detailed and that you bundled up the necessary files for us. Thanks, very much appreciated!
  6. peanutman314

    [HOW TO] Modification of AMD FB + Clover injection

    Thanks for the tutorial! I always wanted to know how you made your driver packs. I'm happy I can do it myself now if needed. However, I have an Asus 270 (non-X) and have some questions about some things that were not entirely clear from your guide: - I understand the device id for the 270X is already in AMD7000Controller but the one for the 270 is not. I guess I can add it manually, but I was wondering if there was an update-proof way? What if I use clover's fakeid feature to set it to the 270X id (the hardware is very similar, no?). Will this work or will things go wrong. - Do I still need to enable the "Inject ATI" feature in Clover? What does it do anyway... - Do I still need something like ATYinjector.kext from your original pack? What was its purpose, is it the same as the Clover Inject ATI? I always assumed if your id was in the kext the driver would be loaded and if the framebuffer is correct it would work. But apparently you needed this for the 270X so I'm curious what it does. I was hoping you could help me figure out these details so I can get my 270 working with your method. Thanks again!
  7. Thanks for this! I have an Nvidia 210 which worked fine with an EFI string in 10.8 but stopped working decently in 10.9 (choppy animations, non-transparent menubar, ...). The command above fixed it for me.
  8. peanutman314

    Mountain Lion + 8800 GT (black screen)

    I have the same problem. Dual 8800GT 512mb, worked fine up to Lion with EFI strings or GraphicsEnabler. One of my monitors should be in portrait mode. Most of the time all 4 monitors work in ML, if they are in landscape mode, but as soon as I change the vertical one into "90° rotation" it goes black, but with the mouse visible like you described. Also, sometimes at random he makes one screen black at boot (rarely), but for some weird reason it is not always the same one that goes black. I tried replacing the drivers with the NV* kexts from my last 10.7 install, but that only resulted in a KP. Please let me know if you find a fix.
  9. peanutman314

    dual nvidia videocard PCI/PCI-E

    So, because I can't post in the nVidia subforum because I'm new, I'll give it a shot here. It would be nice if a mod could move it there though, because it's a very specific problem. There are many posts around for dual videocards, but none seem to handle 2 videocards in different slot types (one pci-e, one regular pci). I've happily been using my hackintosh with a GA-EP45UD3LR, and an EVGA 8800 GT 512mb using Kakewalk. This machine has been working great across multiple OS updates. My 8800GT worked out of the box with Chameleon graphics enabler, so I never really had to mess around with videocards. Now, I would like to go from dual screens to 4 screens. My motherboard does not have a second PCI-E slot. I do however have an 8400 GS (256mb) via regular PCI. I tried a lot of stuff to make it work, but I'm all out of ideas. I would be forever grateful if someone could point me in the right direction. This is some stuff I have tried: - the 8400GS in the PCI slot, with no other cards installed, works out of the box in OSX - When both cards are inserted , everything works as expected in WINDOWS7 out of the box (4 monitors, hardware accelerated) - When both cards are inserted in OSX with default BIOS setting I got a black screen after the gray loading screen. This was resolved by setting the default graphics slot to PEG (the pci-e slot) in the BIOS. OSX now boots fine, but only the monitors on the 8800 work. System Profiler detects the 8400 but shows 2 empty "Display Connector" places. - When disabling the Chameleon graphics enabler, and using NVEnabler.kext with an EFI string, I am able to inject card info (Profiler shows injected strings and such). This is the string I'm using (afterwards encrypted to hex of course): http://pastebin.com/zjCf18Ne The 8800 works fine, the monitors on the 8400 don't. The 8400 is still detected in Profiler, but shows 0MB VRAM even though I specified 256mb in the string. The device paths were gathered with gfxutil. It also thinks the 8400 is connected via PCI-E instead of PCI. Is there anyone that can help me with this? For instance, I'm not sure if the EFI string is 100% correct. Like what is the connector-type value for, and what are the possible values? same for display-connect-flags and device-type. Could this be a way to specify PCI/PCI-E ? The fact that it works great in Windows, that that both cards propably use the same driver, and that the 8400 works fine by itself makes me believe that it's possible. Please advise. I might consider a reward for someone that can walk me through this. Reinout
×