Jump to content

Lord Kamina

Lord Kamina

Member Since 04 Jun 2012
Offline Last Active Jan 03 2018 02:51 AM

#2560616 i7-8700 weird beachballs

Posted by Lord Kamina on 03 January 2018 - 02:54 AM

u dont need compile it, is a oem table, if u don't drop it, is load all time check what tables load with PatchmaticPatchmatic extract.zip put in /usr/bin and run .command Even if it's an OEM table, if it is badly written, it will result in an ACPI error when it's loaded. What I did is drop the original and load a corrected version. Anyway, your clover folder didn't really fix this issue. I managed to fix it in the end by applying a mixture of fixes. I used your DSDT (but not your config.plist, although I did take some of your changes like SmartUPS and a couple other things), I kept my darkwake=10 and also added the fixes discussed here: https://pikeralpha.w...g-sleep-issues/ One thing I hadn't understood before is that deep sleep that doesn't wake with keyboard is actually intended behavior.

#2340627 A _different_ web drivers black screen on boot issue?

Posted by Lord Kamina on 28 December 2016 - 03:48 PM

Hey everyone... I'm finishing up on a new build (due to my old motherboard dying on me) I've got an i7-3770, Asrock Z77 OC Formula and a GTX980. I can't boot with the 980. It was working just fine with the old motherboard (an MSI p67a). Now, if I use nv_disable, it boots ok (without acceleration obviously) and if i use NvidiaWeb, I get a black screen (with no errors, and there is actually a signal being sent to the display;  it's just blank), and the machine doesn't finish booting up (I know because I can't VNC into it). All this is to say that no, it is NOT the AGDP issue. I'm using iMac13,2 SMBIOS. Today this happened and I left it like that a while to see if it ever finished up booting (seeing as I'd read about people experiencing long boot-times on a black screen) but after a while I had to turn it off because, I {censored} you not, there was smoke and the smell of burnt plastic. I have no idea _what_ burnt, the only symptom I've seen so far is the BIOS...

#2230534 ReadSMC for EFI, a tool to enter read SMC keys from EFI shell on real Macs

Posted by Lord Kamina on 05 April 2016 - 04:40 PM

Yeah, that's exactly the page I had found. However, I was comparing the binary they used (the original) and the one included in the MBP updates and they're completely different. So... I cannot really recommend you use it because I'm not sure it can handle your SMC. On the other hand... if you want to try it, it's probably the only alternative you've got left. (i.e. flashing your smc with that version of smcflasher)

#2230265 ReadSMC for EFI, a tool to enter read SMC keys from EFI shell on real Macs

Posted by Lord Kamina on 04 April 2016 - 06:22 PM

Try reinstalling yosemite or el Capitan and if you're lucky perhaps the correct SMC will be re-flashed.Either that, or try running the smc update package from inside OSX, not using rEFIt.

#2230185 ReadSMC for EFI, a tool to enter read SMC keys from EFI shell on real Macs

Posted by Lord Kamina on 04 April 2016 - 12:57 PM

You really shouldn't have messed with something you didn't understand. You need to open the mac, disconnect the battery and magsafe, hold power button pressed for 30 seconds or so, and with it still pressed connect the magsafe, let go of power and press it again once. The computer should boot but without sensors and fans at full speed.

#2230076 ReadSMC for EFI, a tool to enter read SMC keys from EFI shell on real Macs

Posted by Lord Kamina on 03 April 2016 - 10:25 PM

Congratulations. You bricked your mac, for no reason at all. The kernel_task error was in no way related to the SMC version, and that site is not really entirely reliable because there are some versions that are not shown on it. Not to mention, most osx updates come with bundled efi/smc upgrades that are applied automatically or not according to need. You forced install of an incorrect SMC, because your EFI version was newer than what the site said. The only possible solution I can think of other than replacing the chip is to perhaps reinstall el capitan or Yosemite on SMC Bypass mode.

#2180614 [GUIDE] USB Fix El Capitan 10.11

Posted by Lord Kamina on 22 October 2015 - 12:38 AM

Not really making progress here... D: Here's my current IOReg, I've tried injecting my properties and stuff everywhere I can think of but still no dice. The hardware is definitely being detected, as you will see in the IOReg. It just won't actually _mount_ the partitions because it's reading at speeds probably below even USB1.1.   Attached Files  Anasas.ioreg.zip 1.08MB 3 downloads

#2114129 Help tracing AppleHDA assertions?

Posted by Lord Kamina on 23 February 2015 - 12:23 AM

I've been trying to produce a working AppleHDA for my new board (an MSI P67a-GD55) and so far have been met mostly with failure. What I'm doing is trying to create a custom layout (and pathmap etc etc) from scratch and am using DigitalDJ's method to patch the layout hard-coded size in the Binary (https://digitaldj.ne...ayout-applehda/)  So far, it would appear my layout is being indeed read but I have no sound devices and I'm being plastered with assertions. Using IDA Pro I began trying to trace them as explained on that post... and have basically hit a wall with that. I'm really getting A LOT of assertions but the first two are always 22-02-15 14:42:42,000 kernel[0]: Sound assertion in AppleHDAPath at line 1350 22-02-15 14:42:42,000 kernel[0]: Sound assertion in AppleHDAEngine at line 515 Something tells me I should try to correct them from the top-down as most likely one failure would lead to another. Upon tracing those, I've gotten to the point where...

#1869527 GUIDE: HDMI Audio with unsupported on-board audio: VoodooHDA and AppleHDA at...

Posted by Lord Kamina on 28 November 2012 - 10:39 AM

It was fun working on this project. -Beta Blood, sweat and tears! Definitely wouldn't have gotten it working without your blog and commenting here and there.

#1869322 GUIDE: HDMI Audio with unsupported on-board audio: VoodooHDA and AppleHDA at...

Posted by Lord Kamina on 27 November 2012 - 04:38 PM

DISCLAIMER:I have made this guide for people using ATI/AMD GPUs because that is what I have, because as-far-as-I-know AMD uses only one audio codec and because it's what I've tried and know, works. Still, the principle should be just as valid for NVIDIA or even Intel HD cards. My Build:Motherboard: Asus P5G41T-M LX PLUSCPU: Intel E7400, overclocked @ 3.37GHzMemory: 4GB Ram DDR3 1333Ethernet: Realtek RTL8169Audio Codec: ALC887-VDGraphics: XFX Radeon HD 5570 1GB DDR3OS: Mountain Lion 10.8.2I bought this Asus board a couple months ago and mostly it works very well. Now, when I bought it I looked at the audio codec but I didn't search for actual user experiences getting it to work (my mistake) and to my surprise, upon getting home I quickly realized that AppleHDA and my board just weren't the best of buddies. Flash-forward a couple of weeks and I'm resigned to using VoodooHDA. Now, VoodooHDA doesn't make friends with my HDMI audio so I have to choose between Ap...

#1858671 64bit Lion kexts don't work on ML

Posted by Lord Kamina on 06 October 2012 - 02:38 PM

I think your problem might be in generating the kernel cache (if you do use one), sometimes you need to specify you only want 64bit versions of the kexts in there.
© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy