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 bisk

  • Rank
    InsanelyMac Protégé
  1. Dell Keyboard hotkeys remapping

    Aloha guys, Hey, I have been working diligently trying to recreate your success here but am not so lucky I have a Dell Latitude E6540 which generates the exact same scan codes and ACPI calls as the OP's E6230. I have applied the PS2K patch in Method _Q66(), tried it with both IOWMIFamily.kext loaded and not loaded and no matter what ... Plus, I have tried 4 different ALPS versions of the VoodooPSController.kext Fn+<up arrow> and Fn+<down arrow> are simply ignored. I can only affect video brightness with Fn+F3 and Fn+F15(Insert). Running Sierra 10.12.6. I must be missing something very basic. This shouldn't be that hard, should it ?
  2. Alright, I did reinstall Clover with the customization options above but no difference. My problem does not involve finding the hard drive or getting this system to begin a boot cycle. My problem is that this system will create a prelinkedkernel that will NOT boot. I have 3 versions of the prelinkedkernel: #1 is 14MB and boots perfectly fine every time. It was created manually with "kextcache -i /" in single user mode. #2 is 19MB and KPs at the graphics kext loading stage. It was created manually with "kextcache -i /" after a successful boot into full graphics mode with preklinkedkernel #1. #3 is 24MB and KPs at the graphics kext loading stage. It was created automatically by the system when it decided that the prelinkedkernel needed to be rebuilt after a successful boot into full graphics mode with preklinkedkernel #1. They are too large to attach. WTH ? Really at a loss here. Has anyone ever experienced a problem like this ?
  3. Originally extracted from my own BIOS using F4 in Clover. Its an awesome build, just so confused. It runs El Capitan perfectly w/o the prelinkedkernel corruption thing.
  4. OK, I added the -no_compat_check and, sure enough, I am able to boot with stock Sierra /S/L/CS/PlatformSupport.plist and /S/L/E/NVDAStartup.kext. However, this system will still rebuild a prelinkedkernel that crashes upon reboot and right at the same place, immediately after: "IOGraphics flags 0x43". Here is the before and after prelinkedkernel. The smaller one is the original actually built on another system with the boot drive externally mounted. The second, larger one is what this system rebuilt while running with this boot drive. -rw-r--r-- 1 wheel 14750827 Jan 30 10:20 prelinkedkernel -rw-r--r-- 1 wheel 24052658 Jan 30 10:20 prelinkedkernel Strange how the timestamp did not change, huh ? I must stress that everything works on this system. Sleep, SpeedStep, Firewire, all USB ports, full graphics acceleration, native audio output, you name it. This is a Gigabyte P43T-ES3G mainboard. I believe that I have done all of the necessary DSDT mods but I am sure that there is always room for improvement. I also don't think that I really need very many of the usual Clover mods either but I will happily attach the results of your RunMe.app for inspection. I have never experienced a problem anything like this and I am not all that new to this scene. This is, in fact, my 122nd Hackintosh dating back to the Leopard days Thanks in advance ! Send me haxmax122.zip IORegistry.zip
  5. Thanks for the super quick response, wow ! If by "InjectNVidia", u mean config.plist->Graphics->Inject->NVidia=Yes. I'm already doing that. I use MacPro3,1 instaed of iMac10,1 because MacPro3,1 opens up more USB ports. This way, I don't need to muck around with USBInjectAll.kext. Does -no_compat_check flag eliminate need to modify PlatformSupport.plist ? Does it also fix the Sierra NVDAStartup.kext problem with older NVidia cards and Sierra ? I'll give -no_compat_check a shot tomorrow and report back as instructed. Mahalo !!!
  6. Aloha ! I am having the craziest problem which had been driving me nuts for over a week. Maybe a guru out there can shed some light on this one. OK, to explain ... I have installed Sierra 10.12.6 on an unsupported desktop system. Specifically, this is a series 4 (LGA775) motherboard with a Q9505 Core 2 Quad processor. This is not a new procedure to me as I have done several of these. Since it's defined as a MacPro3,1, /S/L/CS/PlatformSupport.plist was modified to allow booting and /S/L/E/NVDAStartup.kext was rolled back to the El Capitan version to allow use of an older (NVidia 9800GT) video card. At first, the system would boot and run just fine but soon afterwards, it would crash during boot up right after: "IOGraphics flags 0x43". This was not the typical KP within NVDAStartup.kext as there was no stack trace showing that the system was within this or any other kext during the panic. Instead, all that I got was a generic CPU fault showing no call stack at all. Suspecting the ElCap NVDAStartup, I replace the Sierra version and installed a Sierra-supported video card (GTS450) but was greeted with the exact same KP ! I managed to get this system to boot again by booting single user and rebuilding the kext cache manually. I went back to the ElCap version of NVDAStartup.kext and put back the 9800GT video card. Again the system booted and ran fine but the next time that I restarted the system, the same KP at boot time. Again, I booted standalone, manually rebuilt kext caches and again a perfect boot and run session. Suspecting something was going awry with the kextcache, I started keeping an eye on the prelinked kernel. When running in graphics mode, I decided to run: "kextcache -u /" and the OS did NOT rebuild anything so, at first, I was confused. But about 30 minutes later, I decided to check the prelinked kernel again and sure enough, it had gotten rebuilt automatically some time later. Tried rebooting, and got the KP. Booted standalone, manually rebuilt the prelinked kernel, rebooted up fine and then watched my perfectly good prelinked kernel be replaced automatically with a "poison" one some time later again ! From further testing I discovered that: If I rebuild the prelinked kernel by any method manually either by mounting this boot drive on another Mac or on the trouble system in standalone mode, this system will boot and run fine from the resulting prelinked kernel. However, if on this system in graphics mode, I either force a rebuild of the prelinked kernel manually or allow the system to rebuild it automatically, which it always eventually will, the resulting prelinked kernel will always cause a KP late in the boot cycle right in the graphics driver load phase. I should also mention that the "poison" prelinked kernels are always substantially larger than the good ones. Anyway, this is a system possessed and dead set on committing suicide over and over ! I have rebuilt the boot drive from scratch twice with the same result so please don't suggest that I do that one. I don't use any installation methods that "customize" kexts or any other aspects of the startup volume. I always begin with a completely vanilla startup volume and then make all of my customizations manually from there so I know exactly what I've got. Has anybody out there ever had this kind of demon and if so, how did you exorcise it ? I have attached a view of both an unsuccessful and a successful boot. Thanks in advance !
  7. As far as DSDT mods go, there is no universal fix. Its a custom modification, albeit, a simple one. U just look for the function in your DSDT with the conditional statement comparing to "Windows 2001", "Windows 2006", "Windows 2009", etc. and just simplify it to set the values for one of those choices. If u haven't messed around with DSDTs before just let clover do it for u. Check out the clover wiki and you'll find it. Good luck !
  8. Check your HPET device in DSDT. Probably, you need 4 IRQs instead of just 2. That's what did it for me. I had started out with a DSDT from jaymack initially but needed to make quite a few adjustments to it in order to get everything working properly for my Z400. You can have a pretty good idea if your firewire is OK by looking at the Firewire line item of your System Profile. If there is a red message there, it's no bueno. I make practically no mods through the clover config. I focus on the DSDT. I plan to publish my config files when I get a chance if anyone is interested. I am only running 10.11.6, however. Also, I never run installations. I simply "clone and go" making necessary EFI and SLE customizations along the way.
  9. Hey, turns out that I solved this one myself ! All I needed to do was to add a DSDT mod such that a "Windows 2001" style _INI() executes. Now this HackPro wakes from sleep properly AND no more intermittent black screens following the clover boot menu at startup. All is good So for all of you experiencing the reboot on wake thing, be sure to consider doing the "Windows Init" DSDT mod. Bye for now ...
  10. Aloha, I have an old series 4 board running 10.11.6. All is great except audio and a reboot on wake problem. It turns out that the ALC889A audio on my board exhibits a ghost/phantom codec which renders native AppleHDA mods ineffective so I simply use VoodooHDA and all is well on that front. However the reboot on wake problem persists ! This system sleeps with NO blinking power button light as if it is off. When I click the mouse or tap the K/B, it reboots instantly upon wake with NO desktop screen. This HackPro used to do a CMOS reset as well despite the DSDT RTC fix but that was remedied by installing a patched AppleRTC kext. Never used to need to do BOTH ! This is a Gigabyte GA-EG45M-UD2H motherboard with Core 2 Quad Q6600 overclocked from 2.4GHz to 3.0GHz. The BIOS is upgraded to the final F4 version and I am booting clover v2.3k r3998 defined as a MacPro3,1. I know that these Gigabyte boards always had reboot on wake tendencies but there was a DSDT fix that declared 2 new vars: SLPE and AG3E which were then used in the _PTS() and _WAK() fuctions to fix the problem. Unfortunately, what worked for SnowLeo/Lion/MountainLion does not seem to work for El Capitan Everything else works fine including SpeedStep but seemingly with only 2 speeds, 2GHz and 3Ghz. But my temps are super cool in the upper 30's-lower 40's C, never even reaching 45C. I'm hoping that there is a DSDT guru out there who can help me with this reboot on wake issue. Here is my hibernate settings info ... pmset -g Active Profiles: AC Power -1* Currently in use: hibernatemode 0 womp 1 networkoversleep 0 sleep 60 (sleep prevented by softwareupdate_notify_agent) Sleep On Power Button 1 ttyskeepawake 1 hibernatefile /var/vm/sleepimage autorestart 0 disksleep 10 displaysleep 20 Another strange behavior is that right after the clover boot menu, sometimes I get a blank display and system freeze instead of the verbose log screen. It may take 2 or 3 reboots until I finally get the line of: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ and the system log ... What causes this ? What exactly happens in between the clover boot menu and the screen dump ? Any help to point me in the right direction will be greatly appreciated. I enclose my DSDT, config.plist and ioreg. Thanks in advance ! HelpFiles.zip
  11. Problems with firewire in HP Z400

    Unless you have the HP Z400, my DSDT is of no use to you. Looks to me like you are running a couple of Gigabyte boards, a series 4 w/Core2Duo and 1st Gen i7. I also have a series 4 Gigabyte board running 10.11.6. I have a reboot on wake problem with this one. Mine is a G45 chipset while yours seems to be a P35. Did you ever experience reboots when waking from sleep ?
  12. Moved to Power Management Forum ... sorry.
  13. Problems with firewire in HP Z400

    Aloha GuitarFa12, Are you still trying to solve this. I believe that your FW problems are created by the HPET device. I have your exact configuration and my Z400 works perfectly under 10.11.6. Lmk if u still need help and I'll happily send u my DSDT and clover config. That should do the trick for u later ...
  14. First thing ... Be sure that your disk controller is set to AHCI or ACHI/RAID in the BIOS setup, not IDE.