Jump to content

Anachronaut

Members
  • Content count

    40
  • Joined

  • Last visited

About Anachronaut

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    Minnesota, USA

Recent Profile Visitors

2,032 profile views
  1. Well now, Security Update 2016-002 broke my NVIDIA web drivers again, this time version 346.03.15f03 in El Capitan 10.11.6 build 15G1108. I tried using the NVIDIA Webdriver Updater App, but it did not successfully solve the problem. I think I used the app correctly, as I checked the modify after installation thing. Perhaps I put the wrong number in it – I could not find good documentation on this. The app just stopped responding, displaying a spinning beach ball. Although the driver was installed, it would not activate after the restart due to a wrong build error. Onto solution 2 until NVIDIA comes out with a new version for this build: I just manually edited the info.plist in the NVDAStartupWeb.kext to look for the new build, then installed the kext using my favorite kext installer program. This got it to mostly work, it is now showing Apple driver as selected at startup, but is in fact using the NVIDIA driver. Hopefully NVIDIA will issue an update in the next few days for this.
  2. I am considering building a very low budget system for testing purposes. The tests will be on different hardware, OS's, utilities, etc., so the processor will not be taxed at all. About the most difficult thing the processor will need to do well in this build is to post and respond to forum topics. Is it possible to use the integrated HD 530 graphics on the Skylake Pentium G4500? If so, then the information is difficult for me to find and/or interpret. This chip has been used in a successful build by Frank Nitty: http://www.insanelymac.com/forum/topic/311747-guide-how-to-install-el-capitan-on-asus-z170m-plus-with-clover-using-pentium-g4500/ But Frank Nitty "cheated" on this one using a great NVIDIA graphics card instead of the integrated graphics. Also, he used Clover FakeCPUID for an Ivy Bridge CPU, which may not work if I want to use the HD 530. The Clover Wiki ( https://clover-wiki.zetam.org/Configuration/KernelAndKextPatches#kernelandkextpatches_fakecpuid) lists codes for other FakeCPUID's, but there are currently none for a Skylake chip. From my limited understanding, using a FakeCPUID of a Skylake chip with HD 530 graphics would seem to give the best chance for success. Also, El Capitan 10.11.4 and later have native support for HD 530. Pike R Alpha related in his blog that this may be possible: https://pikeralpha.wordpress.com/2016/03/25/os-x-10-11-4-build-15e65-and-skylake-graphics-support/ Unfortunately, he discusses things that are quite outside of my knowledge base so it is difficult for me to interpret what he is saying or how to proceed. Any help or suggestions would be appreciated. An example build would be even better if one already exists as I have not been able to find one.
  3. My new Skylake build is mostly working. When I choose shutdown from my OS X 10.11.6 installation, everything goes well and the computer shuts off; no drives, fans, or lights appear to be active. However, if I press any key on the keyboard, or remove or attach any USB device, the computer will boot from the BIOS as if I pressed the power button. I have disabled "Power on by Keyboard" and "Power on by Mouse" in the BIOS (version F4 – the latest for this board) so this is confusing. Also, when I used Clonezilla to backup my hard disk, the computer shuts down properly from the Linux OS that it uses and required the power button to boot. I am running the latest version of Clover for my boot loader. I would like to fix this if possible, as the computer will boot at the slightest movement, touch to keyboard, etc. the way it is now.
  4. Absolutely, it should work perfectly if the clone was successful.
  5. Refresh your screen and read additional info— I updated/edited the post.
  6. Not a problem if the new drive is as large (same sector count) or larger than the drive you currently have. The model only matters for sizing, and restoring from the backup. For the initial clone, you can use any drive that is the same size or larger. It is even possible that two drives from different "manufacturers" have the same sector count because they contain the same chips internally. In that case, a clone would work in both directions. You could try buying the updated model of the drive you currently have. It may still have the same sector count as companies tend to stay the same on these things with SSD's.
  7. That is why with my new Hackintosh I just bought two identical drives right from the start. If you have extra money lying around (???!!), you could buy two new SSD's, clone to the new drive, swap it into your current computer in place of the other SSD, and then use the second one you bought for a backup. Note that if the new drive has a larger capacity than the old drive, you may want to resize the main partition after you make the clone, otherwise you will be limited to using only as much space as the smaller original drive.
  8. That is correct. Not just the same size SSD, but the same make and model — the actual sector count needs to be identical to clone easily in both directions.. This is important, as Clonezilla (with basic use) cannot clone from a larger disk to a smaller disk, even if the data on it would fit. If sectors are blocked due to damage, it may not work correctly when trying to restore. That being said, I have not had a problem restoring from my SSD clone, probably because with over-provisioning there are always the correct number of sectors unless the SSD is way overused.. It is possible to do a correct clone from a larger disk to a smaller disk by resizing the main partition and then cloning each partition separately, including the EFI partition. This is a bit sketchy and may not always work but I have done it successfully on occasion. I really like the simplicity of Clonezilla and continue to use it. Oops, one more note to add. When I first used this with SSD's it was easy to identify the internal drive to be cloned because it was an M.2 drive and it said that right on the screen. With my newest Hackintosh, I am using 2 identical SATA SSD's, one internal and one external. It does not say "internal" or "external" in Clonezilla, all you get is sda, sdb, sdc, etc. So what I did to make absolutely sure was to start Clonezilla with only the internal drive and copied down the serial number. Then I restarted Clonezilla (easy to do from the given options onscreen), and I could easily identify the internal and external drives by their serial numbers.
  9. Confirmed WebDriver 346.03.15b01 is working on my system after security update 2016-001 for 10.11.6 broke my NVIDIA web driver. For anyone who doesn't know, there is a download link for the installer for this on the first post in this thread. I have temporarily disabled the automatic update feature of my NVIDIA updater control panel until a new version of the web driver is available for this build.
  10. This behavior is apparently due to a bug in the bios, as it reportedly also affects Linux machines. The Windows drive contains its own boot loader on the boot partition of the drive from the install of Windows. This is probably why it still adds entries after reconnecting the drives. From my understanding, the solution is to remove the boot loader from the Windows drive, and just let Clover handle everything. I have no idea how to do this and still keep the Windows drive bootable. If you try something like this and are successful, please post your method so others can benefit. Apparently, you need to have only one installed boot loader (Clover) for all of your operating system drives.
  11. Could this be a problem with the install? 1024x1280 is the resolution that my system defaults to when the Nvidia Web Driver is not installed or is not up to date for the current OS version.
  12. I don't know much about using this with a non uefi motherboard. It is likely that this method will not work without a uefi bios. I would try reflashing the bios and see if that does the trick. Make sure to make note of any particular bios settings before the reflash.
  13. Anachronaut

    El Capitan - Problems with sleep

    Well, that didn't last long. Sleep is now back to not working, with the same symptoms as before. Console messages again show the problem (shortened to remove many duplicates of "Attempt to set push wake topics without dark wake enabled"): 11/4/15 11:26:41.519 AM apsd[76]: Attempt to set push wake topics without dark wake enabled: () 11/4/15 11:26:41.785 AM apsd[76]: Peer [pid=422] requested push wake but lacks APSPushWakeEntitlement I really think this has something to do with the way dark wake is used and/or provisioned in the software. Also, as stated in other threads on this forum, I think the implementation of USB and putting USB items to rest during sleep is part of the problem.
  14. Anachronaut

    El Capitan - Problems with sleep

    Question: "sleep is working" means what? How many days without reset? Sleep is working means that I can leave the computer and it goes into lower power mode – no fans, hard drives, screen display, and the "sleep" light on my case blinks. This always has worked this way, the change is that now it properly wakes up after sleep. Previously, the screen would stay black except for the mouse pointer which would not move after sleep (sometimes just after longer sleep periods, recently after any sleep). To get it out of the "black screen" state required a hard reset. I no longer get Console messages like "Attempt to set push wake topics without dark wake enabled," so something is definitely different. I had previously set Darkwake=8 in my Clover config.plist, but it did not make any difference after having tried no darkwake flag, darkwake=0 and darkwake=1. In fact, before changing to iMac 14,2, it seemed that the darkwake boot flag was not accepted by the system at all. After the change it does seem to be working properly with the previously set darkwake=8. I don't plan to mess with it at the moment unless something changes. Here is what the terminal says: anachronauts-iMac:~ anachronautscomputer$ sysctl -a | grep -iE "dark|wake" kern.waketime: { sec = 1446477693, usec = 502 } Mon Nov 2 09:21:33 2015 kern.wakereason: XHC kern.hibernatewakenotification: 0 kern.bootargs: dart=0 darkwake=8 nvda_drv=1 net.link.generic.system.rxpoll_wakeups_lowat: 10 net.link.generic.system.rxpoll_wakeups_hiwat: 100 debug.darkwake: 8 anachronauts-iMac:~ anachronautscomputer$ I just changed to iMac 14,2 yesterday after finally getting my digital audio outputs to work (steep learning curve, but I managed to figure it out with Toleda's help). Honestly, from past experience, this state will work forever, for as many days as I keep the computer on. The challenge seems to be after system or program updates and/or multiple restarts. Also, I want to make sure that my DVR program records properly after a period of sleep, and that I can wake it up when needed to watch the program. Previously, the DVR program would record properly, but I would not be able to wake the computer without a hard reset. If I wanted a complete recording and happened to get back in the middle of it, I would have to wait until the recording was finished before I reset the computer to watch it. (Normally I would just restart the computer and then restart the recording, missing a few minutes of the program which was no big deal.)
  15. Anachronaut

    El Capitan - Problems with sleep

    Changed to SMBIOS 14,2 and now sleep is working [for now only? I will continue to monitor]. Also, my system starts up much better and more consistently since the change. AppleIntelCPUPowerManagement.kext is not loading, but apparently this is not a problem (see Xnu CPU Power Management | Pike's Universum link below). AppleSMBusController.kext is loading, but AppleLPC.kext is not loading. Both of these are supposed to be necessary, so I may need an SSDT to get AppleLPC.kext to load and run properly. Xnu CPU Power Management is active, as shown by the terminal: Anachronauts-iMac:~ anachronautscomputer$ sysctl machdep.xcpm.mode machdep.xcpm.mode: 1 Really, I don't know why sleep is working well now and was not before the change. It is true that the iMac 14,2 hardware specs are much closer to mine, so maybe something changed that I am unaware of (perhaps this Xnu CPU Power Management stuff, I didn't check before). Also, Pike R. Alpha seems to be a great source of knowledge, but he has not posted about power management in a while. For now if sleep continues to work, I may just put this issue to rest (bad joke intended) for while until more definitive El Capitan power management posts appear, as it is an active area of current research in the Hackintosh community. Reference Link (Please note that this is OLD, most of the information is written about Mavericks. While useful for some background, I think I may wait until more is available about El Capitan power management): Xnu CPU Power Management | Pike's Universum This may also be of some use, but I don't have the time for it right now: http://www.insanelymac.com/forum/topic/304369-how-to-check-your-states-–-using-aicpminfo-msrdumper-or-appleintelinfo/ For what it's worth, this problem may not be limited to hacks – see this discussion: https://discussions.apple.com/thread/6610693?start=75&tstart=0
×