Jump to content
InsanelyMac Forum

madmodmike

Members
  • Content count

    44
  • Joined

  • Last visited

About madmodmike

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    Italy
  1. madmodmike

    GeForce GTX 560Ti and Clover 2k

    Yup, I made a bootable USB thumbdrive with the 10.9.4 installation files (from the Mac App Store).
  2. madmodmike

    GeForce GTX 560Ti and Clover 2k

    Hello Evgeniy, sure, here you go: https://dl.dropboxusercontent.com/u/3367593/config.plist (just in case, add a -v in the Boot-> Arguments section, for verbose boot)
  3. madmodmike

    GeForce GTX 560Ti and Clover 2k

    Update: it finally worked, looks like it was a config.plist misconfiguration, I'm very happy right now woohoo! Thanks A LOT to apianti for his help and patience, and expecially to stehor for the fix that made all working again
  4. madmodmike

    GeForce GTX 560Ti and Clover 2k

    Hello I'm writing here because I'm extremely in trouble with those two, they apparently don't seem to like each other, and I'm pretty sure it's not an OSX related problem, but let me explain in details: Last year, I built successfully an hackintosh, ~99% vanilla, on my Asus P5Q-E with a GeForce 560Ti and Mountain Lion, I began with 10.8.0, upgraded through 10.8.4 with almost no issues at all (just had to replace every time the AppleHDA kext with the one patched by ErmaC for the ADI 2000B, and the sleep was totally unreliable, even on Windows though). The bootloader I used was Chameleon, but after a while, I decided to move over and switch to Clover, for a series of reasons (easier fixes for iMessage/Facetime, PatchVBiosBytes for native display resolution during the boot, etc). The switch wasn't totally painless, I had to rewrite the config.plist from scratch, but after a few hours, I had again my hackintosh up and running flawlessly, on Clover 2k r1745 (I do still remember the versions, because each and every time I upgraded clover, I made a tarball of the EFI folder with all the stuffs inside). Now, the problems started when I decided to upgrade Clover from r1745 to r1858. After upgrading to the new version, my GeForce refused to show anything after the boot logo, just switching the display off with no video output at all. I thought it was some kind of misconfiguration, I tried to look around for fixes with no avail, unless I switched back to Clover r1745 and it worked again. I stopped caring about my Hackintosh because after a while I got myself a brand new Macbook Pro, so It was pretty natural for me to move over to the MBP. Just a few days ago, I've got an old 775 motherboard (G31/ICH7 and an X3100 integrated GPU), I had a spare Q6600 CPU around, so I thought well, let's try to make an hackintosh again. Took a brand new USB flash drive, downloaded from my MBP the latest Mavericks .app from the store (10.9.4), made two partitions on the USB flashdrive, on the smallest one I installed the latest Clover, on the other one, the Mavericks .app (using the createinstallmedia command from the command line). Dropped the latest FakeSMC 3 (build 748) and NullCPUPowerManagement, and replaced the config.plist with a bare minimum one: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <false/> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <false/> <key>AddHDMI_8000000</key> <false/> <key>AddIMEI_80000</key> <false/> <key>AddMCHC_0008</key> <false/> <key>AddPNLF_1000000</key> <false/> <key>DeleteUnused_400000</key> <false/> <key>FIX_ACST_4000000</key> <false/> <key>FIX_ADP1_800000</key> <false/> <key>FIX_INTELGFX_100000</key> <false/> <key>FIX_RTC_20000</key> <false/> <key>FIX_S3D_2000000</key> <false/> <key>FakeLPC_0020</key> <false/> <key>FiX_TMR_40000</key> <false/> <key>FiX_WAK_200000</key> <false/> <key>FixAirport_4000</key> <false/> <key>FixDarwin_0002</key> <false/> <key>FixDisplay_0100</key> <false/> <key>FixFirewire_0800</key> <false/> <key>FixHDA_8000</key> <false/> <key>FixHPET_0010</key> <false/> <key>FixIDE_0200</key> <false/> <key>FixIPIC_0040</key> <false/> <key>FixLAN_2000</key> <false/> <key>FixRegions_10000000</key> <false/> <key>FixSATA_0400</key> <false/> <key>FixSBUS_0080</key> <false/> <key>FixShutdown_0004</key> <false/> <key>FixUSB_1000</key> <false/> <key>NewWay_80000000</key> <false/> </dict> <key>Name</key> <string>DSDT.aml</string> <key>ReuseFFFF</key> <false/> </dict> <key>HaltEnabler</key> <false/> <key>SSDT</key> <dict> <key>DropOem</key> <false/> <key>Generate</key> <dict> <key>CStates</key> <false/> <key>PStates</key> <false/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>-v dart=0</string> <key>DefaultVolume</key> <string>MacHDD</string> <key>Legacy</key> <string>PBR</string> <key>Log</key> <true/> <key>Secure</key> <false/> <key>Timeout</key> <integer>10</integer> <key>XMPDetection</key> <string>NO</string> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <string>1</string> </dict> <key>FakeID</key> <dict> <key>ATI</key> <string>0x0</string> <key>IMEI</key> <string>0x0</string> <key>IntelGFX</key> <string>0x0</string> <key>LAN</key> <string>0x0</string> <key>NVidia</key> <string>0x0</string> <key>SATA</key> <string>0x0</string> <key>WIFI</key> <string>0x0</string> <key>XHCI</key> <string>0x0</string> </dict> <key>USB</key> <dict> <key>FixOwnership</key> <false/> <key>Inject</key> <false/> </dict> <key>UseIntelHDMI</key> <false/> </dict> <key>DisableDrivers</key> <array> <string>Nothing</string> </array> <key>GUI</key> <dict> <key>Hide</key> <array> <string>Windows</string> <string>\EFI\BOOT\BOOTX64.EFI</string> </array> <key>Language</key> <string>en:0</string> <key>Mouse</key> <dict> <key>Enabled</key> <true/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Legacy</key> <string>First</string> <key>Tool</key> <true/> </dict> <key>Theme</key> <string></string> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <true/> <key>NVidia</key> <true/> </dict> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> <key>AsusAICPUPM</key> <true/> <key>KernelPm</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>External icons patch</string> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>LogEveryBoot</key> <string>10</string> <key>LogLineCount</key> <integer>3000</integer> <key>MountEFI</key> <string>Yes</string> </dict> <key>SMBIOS</key> <dict> <key>Trust</key> <false/> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Detect</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> I set the Graphics-> Inject for Intel and nVidia both on true, just to see if my old desktop would be able to boot the installer as well. Then I booted the flash drive on this "new" hardware (generic ASRock motherboard on G31, Q6600, onboard Intel X3100 GPU): success at the first try, and I got the OSX Utilities screen. Next I just thought "oh well, let's try again on my old PC". Nope. Still the same issue as the last year: the boot goes on with no issues, and then when the GUI should start, I just get a blank screen with no video out (and the monitor goes itself in standby) I tried with every bootarg I know (npci=0x2000, -v, -x, PCIRootUID=0 and =1, even though it should be =0 by default on clover). It boots without halting and then I get just the black screen with no signal, exactly like I experienced the last year after the unlucky upgrade. Now after this huge WOT, I'm here to ask you gurus: what causes this strange behaviour? Should I give up and go back to Chameleon? I'm honestly clueless.
  5. madmodmike

    [Guida] AppleHDA su Mountain e Lion

    Si, ho un MacBook Pro con 10.8.4 quindi la versone e` la medesima, appena posso faccio la prova. Grazie mille per il suggerimento
  6. madmodmike

    [Guida] AppleHDA su Mountain e Lion

    Ciao Micky, grazie per la risposta. Non uso Pandora (la pennetta di installazione l'ho realizzata manualmente partendo dal dmg di 10.8), e` possibile usare Pandora lo stesso per patchare l'AppleHDA? Dovrei avere il vanilla backuppato, nel caso non lo trovassi, se lo prendo da un Macbook Pro va bene lo stesso? Grazie mille
  7. madmodmike

    [Guida] AppleHDA su Mountain e Lion

    Riuppo perche` ho ancora qualche problemino, ho provato il kext di ErmaC (per AD2000B, preso qui) sulla mia P5Q, funziona perfettamente, ma ho un glitch con il pannello frontale con le connessioni di cuffie e microfono: nonostante tenga costantemente connesse le cuffie al pannello frontale, ogni volta che faccio partire OSX e arrivo al desktop dopo il login, alcune volte le ha rilevate automaticamente e l'audio viene correttamente veicolato (da System Properties risultano effettivamente Headphones), spesso e volentieri invece rimane su Internal Speakers, con l'uscita posteriore delle casse abilitata, e per far "vedere" le cuffie devo rimuoverle e reinserirle dal pannello anteriore. E` un problema solo mio? qualche idea sul come diagnosticarne la causa? Premetto che con i kext che usavo prima non accadeva (si tratta di questi: http://www.osx86.net/downloads.php?do=file&id=2444 , AppleHDA.kext di Lion 10.7.4, AD2000b.kext, HDAEnabler.kext e HDEFEnabler.kext), ma sinceramente preferisco di gran lunga questa nuova soluzione, dato che e` piu` pulita ed usa il kext di ML (se solo appunto riuscissi ad evitarmi l'attacca-stacca col connettore cuffie ogni volta ) Grazie mille!
  8. madmodmike

    audio assente p5q pro ML 10.8.4

    Hai installato anche il kext? (magari con kextwizard) provato anche a ricostruire la cache e fixare i permessi? Inoltre, se usi chameleon, prova a passargli esplicitamente il path del DSDT nello org.chameleon.Boot.plist con
  9. madmodmike

    audio assente p5q pro ML 10.8.4

    dai un'occhiata qui: http://www.insanelymac.com/forum/topic/161430-realtek-alc1200-ich10-working-kext-on-mountain-lion-and-snow-leopard/
  10. madmodmike

    Clover General discussion

    Ok, update: I had another USB keyboard around, but wireless with a common "dongle" for both keyboard and mouse, it's a Wireless Media Desktop 1000 (this is a Microsoft keyboard too, like the Wired DMK 3000 I'm using right now) with the Wireless Desktop Receiver 3.1, this large thing here: I plugged the USB receiver on the front USB ports (no hub, they're directly wired to the internal motherboard USB headers), rebooted, and... IT WORKS.. I left both my wired and wireless keyboard connected, here's the final status: *the wireless mouse WORKS *the wireless keyboard WORKS (both the mouse and keyboard share the same USB receiver) *the wired mouse WORKS *the wired keyboard DOESN'T WORK. So, I suppose at this point this isn't a BIOS issue, am I right? Can be something done to make my wired keyboard work on Clover GUI? btw, both wired and wireless work on BIOS too.
  11. madmodmike

    Clover General discussion

    Hello, nope, connected directly to the motherboard USB ports on the back. Also tried to cycle all the available ports, with no luck Thank you.
  12. madmodmike

    Clover General discussion

    Other than Legacy Mode, nothing I could think of. These are all the options available in my bios: Tried every combination, but got nothing, in Clover GUI only the mouse works (I installed UsbMouseDxe, no problems with the mouse so far). Yes it does, (like the screenshot, it detects "1 Keyboard, 1 Mouse", even during the POST messages).
  13. madmodmike

    Clover General discussion

    Hi Slice, thank you for you reply! I upgraded Clover to r1902, I turned on "Legacy USB" in my bios, but nothing changed, under Clover GUI, the keyboard is still not functioning I probably forgot to say, this only happens in Clover menu: under OSX, the USB keyboard is working as expected (I already have those keys set to "true" in my config.plist), but under Clover menu, my only option to interact with Clover GUI is to plug a PS/2 keyboard before booting my machine. Don't know if this might be useful, but during the Clover startup (after boot:/boot 7...), the Numlock light goes on for a while, then it turns off, and when the Clover GUI finally pop up, there's no input available from the USB keyboard.
  14. madmodmike

    Clover General discussion

    Any hint? The keyboard is driving me crazy
×