Jump to content
InsanelyMac Forum

qwerty12

Members
  • Content count

    49
  • Joined

  • Last visited

About qwerty12

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    UK
  1. Mavericks MBR patch

  2. VoodooPS2-10.9 Only

  3. It won't net you better detection but will allow AppleGraphicsPowerManagement.kext to load and attach itself to your HD 4000. When I originally fixed the lid sleep and Fn+F7 on my N55SL, I didn't look at ASUS' original SPIN and RPIN methods in the DSDTs for their older laptops closely enough and copied values that were correct for that series for ASUS laptops, but not the Sandy Bridge and Ivy Bridge series of ASUS' laptops. SPUN only worked if I called the original SPIN afterwards or my screen would go off if I pressed Fn+F7 but wouldn't come back on again. Just to be careful, I had RPUN call the original RPIN too. This worked fine on my laptop, a Sandy Bridge one, but obviously was not correct since I needed to call the original methods. I didn't really care, though, as it was working nevertheless and was much better than what I had been doing before: downgrading AppleACPIPlatform.kext. For the Zenbook, the same trick didn't work. After a long while, looking at the old DSDTs again, I realised my mistake and attempted to fix it; 68x tested with his Zenbook and it worked. In short: you can replace RPIN with the contents of RPUN and SPIN with the contents of SPUN if you want since the original methods aren't needed anymore - it's a remnant of my first attempt when the original methods were needed. I still kept them with the second version though because: As for myself, I don't even use the new-old RPUN and SPUN methods anymore, and keep the original RPIN and SPIN methods that came with my laptop, as Apple fixed whatever bug in AppleACPIPlatform was blocking the original RPIN and SPIN methods in Mavericks.
  4. Disable Optimus Nvidia GT640M ?

    PINI is conventionally called from _INI inside the PCI0 scope, not the PEGP Device. (PINI has been christened "PCI0/Wake INI" and you're also doing other things inside PINI that are totally unrelated to the NVIDIA card.) I don't think it makes a difference, though, but I feel it's worth mentioning. Look again carefully at your SSDT-4. _PS3() already calls _OFF to turn off the card but only if OMPR is set to 0x03. This makes the _PS3() call redundant but it's not recommended to call _OFF directly. So, make it so that calling _PS3() actually calls _OFF: Look at this post to see how to correctly set OMPR and turn off the card. Use it as a base for your PINI() method and fix your _WAK and _INI (in PCI0) accordingly. If you're dropping SSDTs, you'll have to merge the correct sections from your SSDTs into the DSDT yourself and ignore the External lines.
  5. Atheros ar5b195 but Bluetooth doesn't exist?

    Hello, Just to save you from the disappointment: I have one of these, in the form of a Dell DW1702, and to be frank here: its Bluetooth capabilities aren't really up to par. It takes a while to wake from sleep and it doesn't maintain as good a connection to my Bluetooth mouse compared to my Centrino. That said, you're not going to see anything Bluetooth related on the PCI Bus - the Atheros and the Centrino that I had both exposed their Bluetooth device over USB. Here's how mine shows up: I don't know why you're not seeing anything in Windows (my AR3011 was picked up by drivers in Windows Update on Windows 8) but in Debian and its derivatives, you need to apt-get install linux-firmware for it to show up. In OS X, you don't need to modify any Bluetooth kexts; all you need to do is install IOath3kfrmwr.kext. (That said, if it still doesn't show up after installing the firmware kext, then I have no idea. I know Bluetooth can be disabled on the card by sellotaping pins but something like that would've been noticable.) EDIT: RAS syndrome strikes again!
  6. Haswell success - GA-Z87M-D3H - GTX 670

    The first post has you copy FakeSMC but not set the permissions (EDIT: OP does repair permissions later on so that would fix this. Did you do that?), so the following might work: chown -R root:wheel /Volumes/[target volume]/System/Library/Extensions/FakeSMC.kext chmod -R 755 /Volumes/[target volume]/System/Library/Extensions/FakeSMC.kext
  7. [Help] for solving DSDT (french)

    For Asus laptops, yes because Asus are weird and name both graphic cards "GFX0" and the patch you took from the ProBook repo indiscriminately renames *all* GFX0 instances to IGPU (probably because they don't need to watch out for this sort of thing - I think every other manufacturer other than ASUS calls the NVIDIA/ATI card PEGP)
  8. Asus G75VX - Mountain Lion

    Yeah, see, if you didn't rename it then the BIOS isn't going to pick it up. Simple as that.
  9. Asus G75VX - Mountain Lion

    Did you rename the bin file you copied like both those links said (yes, my post is less concise on things - the thread is on my N55SL and when I'm putting files on the USB stick through my phone in USB host mode, I don't really have the time to figure out which filename is the correct one)? If it's found the correct file, the BIOS will restore the default failsafe settings and you will see the ASUS splash screen followed by ASUS EzFlash flashing the BIOS you put on the USB stick.
  10. [Help] for solving DSDT (french)

    You don't want to rename *every* instance of GFX0 to IGPU! Remember: The easiest way to rename the correct GFX0 to IGPU is to dump the original DSDT (in Windows, I recommend iasl -g or AIDA64; in Linux, sudo cp /sys/firmware/acpi/tables/DSDT ./DSDT.dat) and do a find and replace: PCI0.GFX0 -> PCI0.IGPU (and then rename the correct "Device (GFX0)" to "Device (IGPU") Later versions of iasl optimise (^^^PEG0.GFX0 takes up less space inside the DSDT than \_SB.PCI0.PEG0.GFX0 does) and while it's not exactly hard* to figure out what GFX0 device a certain line is referring to, it's a lot quicker to just find and replace on an unmodified DSDT, where every reference to the GFX0 device inside PCI0 will be the same. *I'm a liar: it is hard but easier when you're using MaciASL as it has a handy "path" bar on the bottom.
  11. HWSensors

    Is this under Xcode 4? Just curious. Under Xcode 5 at least, it won't build saying version.h is not to be found, but after looking, I see that Scripts/PreBuild.sh creates this file - the script should've been run by Xcode as part of the build process but does not for some reason - but it also sets the version number that is later inserted into the plists. I did this before building in XCode (svnversion always returns "Unversioned directory" for me): /usr/bin/sed -i '' 's/sc_revision=$(svnversion)/sc_revision="exported"/' Scripts/PreBuild.sh sh Scripts/PreBuild.shand I got this in the resulting Info.plist inside FakeSMC.kext: <key>CFBundleVersion</key> <string>761</string>which looks right to me since the FakeSMC.kext (installed from the official installer) inside my /S/L/E has a CFBundleVersion of 755
  12. Asus G75VX - Mountain Lion

    The procedure is explained quite well here: http://forum.notebookreview.com/asus/714764-asus-n56vz-no-logo-no-post-no-boot-no-screen-2.html#post9153960 I had to do something similar before with my N55SL when it would turn on and instantly go off when I had changed the Intel MEI firmware flashing settings in the BIOS...
  13. OS X 10.9 DP's builds

    MaciASL by SJ_UnderWater: I use RehabMan's fork because he turned off the annoying auto save. I use it with the latest iasl built from Homebrew (symlink ${HOMEBREW_PREFIX}/bin/iasl to /Applications/MaciASL.app/Contents/MacOSX/iasl5 and tell MaciASL to target ACPI 5.0), which works fine except MaciASL cannot parse the error messages from the latest version so its error message window remains blank. However, it works as expected if you use the bundled version of iasl.
×