Jump to content
InsanelyMac Forum

P5QMac

Members
  • Content count

    29
  • Joined

  • Last visited

About P5QMac

  • Rank
    InsanelyMac Protégé
  1. OS X El Capitan Test Thread

    Tried it on my Asus ZenBook UX32VD and it works exactly like Yosemite. The only difference was the creating of the USB media where simply using the normal OS X USB creator that is built into the installer app is not enough. I needed to create the USB by mounting BaseSystem.dmg and such. There are guides out there. USB 2.0 and 3.0 works just fine with my patched DSDT (this is a 7-series Ivy). I do not use GenericUSBXHCI in any way. I just wanted to see if the new kext stuff had solved a serious graphical glitch that the UX3(1/2) seems to have where the screen glitches like crazy after boot until the screen is turned off and on again. Unfortunately it is still not fixed, and will probably never be fixed either. Seems like a nice upgrade, the multitask full-screen thing was quite nice on a laptop, but I'll erase the El Capital partition for now until it has become far more stable than what it currently is.
  2. This is sort of a known problem as far as I know, and I do know that the problem happened after 10.9. I have this problem myself on my UX32VD and I have tried everything in my power for over a year to fix it. I'd like to test out a BIOS mod where the GOP and VBIOS is upgraded to 2170 instead of 2137 that the UX32VD is equipped with in BIOS 214, however doing so is risky business. The problem is either: 1. The screen used in the ZenBooks are eDP connector displays. AppleIntelFramebufferCapri does not like eDP and has in fact no support for it. 2. The GOP/VBIOS driver is causing a ruckus. Upgrading it with a BIOS mod might get it working. 3. Apple's capri driver is s**** and in 10.9 they removed VGA compatibility. This might be the reason why it's going bananas. The current temporary solution to the problem is: 1. Sleep the display once the computer starts. BrightnessFix or Blinkscreen can do this automatically on login. You can also create a hotspot in one of the corners in the screensaver settings to sleep the screen. 2. Change the ig-platform-id to 0166000A. That will make it think the screen is a HDMI/DP connected external display which solves the issue without any need to sleep the display. It'll boot correctly every single time, but it'll make you unable to change screen brightness and the laptop lid won't sleep the computer. Sleep through the menu will also not work anymore as the display will not awaken again. So pick your solution and stick with it until a fix is found which might never happen.
  3. First off, don't use the MacPro3,1 SMBios. Use the MacBookPro10,1 one instead as the MBP10,1 has the exact same processor. You left out the screen resolution. If it is 1366x768 or higher you'll need to enable dual link (which in your chameleon config there you've disabled). If it is under 1366x768 you'll disable it. This will most likely solve your problem. If that doesn't work it's most likely the wrong ig-platform-id and you need to change it into an applicable one. 01660009 and 01660003 are normal laptop ig-platform-ids with different LVDS connectors. If that doesn't work, try every single one from 01660000 - 0166000B. Clover: http://clover-wiki.zetam.org/Configuration/Graphics#ig-platform-id Clover can also try to inject the correct platform-id by having "InjectIntel" sat as true in the config. Chameleon uses the "IntelCapriFB=X" boot argument where X is the last number in the 0166000X hex. Try IntelCapriFB=9 or IntelCapriFB=3 for example. http://www.insanelymac.com/forum/topic/288241-intel-hd4000-and-haswell-inject-aaplig-platform-id/ A few other tips: Use Clover, that's hands down the best bootloader out there and will solve a lot of problems. Generate your SSDT using ssdtPRGen or find one on the net. Once you're ready, upgrade to Yosemite and get rid of the nasty Niresh {censored} by installing OS X properly using Clover or MyHack. Distros are horrendous. If you don't have a custom DSDT yet, start learning about how to patch one if you want a properly working laptop.
  4. Most likely the ig-platform-id is wrong and you need to change it into an applicable one. I assume this is a laptop? 01660009 and 01660003 are normal laptop ig-platform-ids with different LVDS connectors. If that doesn't work, try every single one from 01660000 - 0166000B. Clover: http://clover-wiki.zetam.org/Configuration/Graphics#ig-platform-id Clover can also try to inject the correct platform-id by having "InjectIntel" sat as true in the config. Chameleon uses the "IntelCapriFB=X" boot argument where X is the last number in the 0166000X hex. Try IntelCapriFB=9 or IntelCapriFB=3 for example. http://www.insanelymac.com/forum/topic/288241-intel-hd4000-and-haswell-inject-aaplig-platform-id/ As for that other chameleon bootloader based on a beast from greek mythology, it uses a "IGPEnabler=Yes/No" argument, but is barely usable if you ask me. It also has an argument named "IGPlatformID=0166000X" that does the same as IntelCapriFB normal Chameleon has. If none of the ig-platform-id possibilities work, use Clover's EDID injection. You'll need to get the EDID from GNU/Linux or Windows in that case as OS X is not picking up the EDID correctly if that is the case. Use "ioreg -l | grep "IODisplayEDID" and compare that to whatever GNU/Linux's readEDID tool or Windows' EDID reading tools give you. If that doesn't work either and you're 100% sure it isn't the ig-platform-id or the EDID, you'll need to learn how to modify the LVDS connectors in the IntelFramebufferCapri kext. This is probably the last resort and is quite easy to do in Clover by using its KextPatching capabilities, but requires some knowledge first. Look up OSXLatitude's HD4000 VGA patching guide to learn how to modify the LVDS connector to something else.
  5. Hmm, I tried out the 2560x1400 resolution on my UX32VD and it worked fine. Dunno if it is usable though as the text gets incredibly small at that resolution. Any downsides when "overclocking" the screen like that except it using the HD4000 more? Doesn't exactly seem healthy for the screen if 1920x1080 is the recommended screen resolution, will it damage the screen in any way? Edit: Works fine in 1280x720 HiDPI too obviously, however as the name implies the resolution is scaled down to 1280x720 while being rendered at 2560x1400 since that's the GPU's maximum resolution. It probably doesn't hurt, but it looks damn ugly (at least in my experience) as the elements are so insanely huge and uncomfortable. It's also quite taxing on the Intel chip which is noticeable when scrolling or moving windows.
  6. Probably more trouble than it's worth, as far as I've heard by people running it on actual Macs it's quite rough around the corners to say the least. Plus it has a few issues with kexts, kernels and more: http://netkas.org/?p=1329 it harder to Hackintosh than before. I'd recommend coming back when the public beta arrives, at least then it'll be more stable and have more features as this DP1 release is clearly an older seed than what they showed during the keynote. Edit: Here's a guide for those who absolutely need to try it out, but I'd wait until DP3 or the public beta. http://www.skylineosx.com/yosemite-installation-guide/ It's pretty much exactly the same as before, just this time you use a new kernel flag: kext-dev-mode=1 .
  7. Yep, Clover creates a small and hidden FAT32 partition on the OS X drive named EFI which the UEFI detects as a valid boot device (where you put all the DSDT stuff inside). That's why you don't need anything else with Clover, it's "Clever" that way.
  8. The sound issue shouldn't be too hard to fix. Just find out what type of audio codec it is and go from there (the UX32VD has a ALC269 codec). Then find a pre-patched AppleHDA or preferably fix it yourself: http://forum.osxlatitude.com/index.php?/forum/76-applehda/ The Intel wireless cards will NEVER work in OS X, end of story. This is the same problem as all the UX31/UX32 versions as well. It won't work, you'll need to replace it with another half-mini PCI wireless card. I'd recommend the Azurewave AW-CE123H which has both bluetooth and wireless 802.11ac compatibility. It's the latest and the greatest within wireless tech and it works perfectly in OS X. It's a bit pricey though, so if that's a factor you might want to look at something else (if you google "half-mini PCI wireless OS X" you'll get to that other site that shall-not-be-named which has a really, really nice compilation of half-mini cards that work in OS X). As for the trackpad: forum.osxlatitude.com/index.php?/topic/1948-elan-touchpad-driver-mac-os-x/ as the UX42VS does have a Elan Touchpad. Try and see if it works. You will only be able to boot through the flash drive because the BIOS will not boot from OS X Extended drives. Since you're Russian you shouldn't have any problem finding info on Clover which is developed by Russians. Clover is the best way to go so once you get that running (it's quite tricky if you ask me) you'll be able to boot normally. Personally I use the small caching SSD as a bootloader partition for Chameleon as Clover has been nothing but trouble from day one for me, but Clover is without a doubt the best bootloader on the market, so see if you can't get that working. You might also want to check out: http://www.skylineosx.com/installation/switching-from-chameleonchimera-to-clover/ but I believe the Russian documentation and guides to installing Clover is far, FAR superior to what is in English, but don't quote me on that.
  9. I've tried a lot of different options by manually patching the capri framebuffer's connection values to make it work and it never does. I've tried different bootloaders, none which give any correct result. Overrides? Nope. IntelCapriFB? No. Injecting a different FB into the DSDT? No. Injecting the EDID into the DSDT? No. I've tried a lot of crazy things to get that screen working perfectly on boot, but I have absolutely no idea what might cause it. All I know is that it won't do it in safe mode (thus hinting at the Framebuffer), that it didn't happen before Mavericks and that turning the screen off (sleeping it) fixes it. A temporary fix I've found is to use EMlyDinEsH's "Fix Brightness" LaunchAgent so that when you log in it'll sleep the screen automatically and turn it on again. It's a horrible way to do it though and there has to be a solution somewhere. ---------- Here is the HDMI audio patched AppleIntelFramebufferCapri for 10.9.3. This is for those of us who can't get HDMI audio out for some strange reason with the stock one. Use it with Chameleon as Clover does the same thing automatically if I remember correctly. AppleIntelFramebufferCapriFixed10.9.3.zip
  10. So I thought maybe my EDID changed sometime after boot since it's the EDID is the same when the screen is scrambled and when it's normal, but that wasn't the case. So I still don't have any solution to my own problem. If anyone is interested, here's a script I made to make the system report the EDID to the system log so you can view it in the Console (the OS X app). It'll read the screen's EDID continuously every 10 seconds after boot and put it inside the system log. So after installing it you'll be able to find out when it's scrambled and when it's not, or if it changes during or after boot (most likely not). Usage: - Use the terminal to cd into the "readedid" folder you downloaded. - Write "sh install.sh" without the quotes. - Write your password to give root access. - Reboot until it's scrambled - Reboot again until it's normal and compare all the EDIDs that's located in the console (search for "IODisplayEDID") and you'll most likely see two different EDIDs getting reported. The one that isn't being reported right now while the screen is normal is probably the faulty one. Remember to uninstall it (do the first three steps as above, just with "uninstall.sh" instead) after you got all the information you need and reboot, otherwise it'll continue to report the EDID to the console every 10 seconds, even when you don't need it. You can obviously read what the source code does by opening the files inside a text editor. While my experiment didn't bear fruit for me, at least I practiced my bash scripting. Good luck everyone, hopefully someone will have use of this! readedid.zip
  11. Tried that many times before, but I'll give it another shot. The problem is that the IODisplayEDID is exactly the same both when the screen works, and when it doesn't. Was this the case for you, or did the EDID change when the screen was scrambled? Turning the screen on and off solves the problem and gives a clean normal screen, but that's not a permanent solution. The EDID is the same as both GNU/Linux and Windows reports and there's no form of scrambled screen there. The screen also get temporary burn-ins if the screen is scrambled for more than a minute. Edit: Yup, doesn't change. If anyone wants my tools to check for the EDID pickup: http://www.insanelymac.com/forum/topic/208410-fixing-scrambledstretched-or-wrong-resolution-laptop-display-problems/?p=2018547
  12. Wait, wait, wait. You managed to solve the scrambled screen on boot problem? Did it look anything similar to this? https://i.imgur.com/dwBAgw7.jpg In that case, could you give me some directions? I've been having that problem since Mavericks and it's been bugging me non-stop. I feel like I've tried everything in my power and researched it for hours and no solution.
  13. http://www.insanelymac.com/forum/topic/283038-asus-zenbook-prime-ux31a-db51-ultrabook-fixes-mods-tweaks-etc/page-34?do=findComment&comment=1957404 It's a bit old, so search the different kexts up in Google and see if there's any new ones out there. However you can use that zip for reference what you might need. I think that's the latest DSDT and SSDT for the UX31A. Instructions are all over the thread, so look around previous pages. Good luck.
  14. Yup, sleep working fine and audio works fine after sleep as well. I'm using Chameleon though, so that might be the reason, as I think 68x had problems with sleep as well according to:
  15. Apple released 10.9.2 which is a crucial update due to a dangerous security flaw. It has updates to the sound drivers and the graphics drivers. Thus the GeForce drivers will reappear and the Intel driver will be overwritten with newer ones. Plus the AppleHDA will be overwritten. I tried with HDMI audio with the stock kext and it did not work, so here's the fresh 10.9.2 AppleIntelFramebufferCapri edited for HDMI audio (UX32VD). Tested and working perfectly fine. Enjoy! AppleHDMICapri 10.9.2.zip
×