Jump to content

jan-munich

Members
  • Content count

    50
  • Joined

  • Last visited

About jan-munich

  • Rank
    InsanelyMac Protégé
  1. Than you press F3 and have all your volumes back. Agree: easiest way seems to be just to add the following: <key>GUI</key> <dict> <key>Hide</key> <array> <string>Recovery</string> <string>Preboot</string> <string>VM</string> </array> <key>Scan</key> <true/> </dict>
  2. jan-munich

    NVMe Express digging

    Has nothing to do with you NVMe drive. please keep this post clean. To answer your question: Have a look on how to successfully patch your AppleGraphicsControl.kext dependent on your FakeSMC to make the driver properly load up.
  3. jan-munich

    NVMe Express digging

    To bad to hear. So im sticking to mainboard / bios issues. So seems that gigabyte users are the lucky ones right now.. would be good to confirm this from another user, so we could start looking even deeper into the bios differences.
  4. jan-munich

    NVMe Express digging

    Well guys from what I can tell is that many manufacturers lacking a proper bios support for NVMe. In particular UEFI boot of NMVe. What you still can do is installing clover to a sata drive for reaching clover then inject the driver and load your Nvme disk. (this was a workaround I used whilst UEFI boot wasn't working properly on my board.) But i guess the general tendency is that manufacturer focus more on their new boards therefore the lack of proper support of UEFI NVMe could take a while to be solved.. if solved at all. Well as you say.. fully recognized. my bios didnt recognize my ssd at all.. than after the first beta bios. it still didnt recognize it but gigabyte broke it totally even in the boot selection. After applying the newest beta now i still cant see my drive in bios but in the boot manger and UEFI boot process has been fixed.. My drive is definitely 100% reliable. So i guess the Z170 series are generally better supported than older chipsets.
  5. jan-munich

    NVMe Express digging

    Well, totally makes sense that in SLE it doesn't work properly. SLE loads Kernel extensions after mounting the root partition (otherwise he couldnt access the SLE folder..), if your root partition can not be found there is no way SLE drivers will be loaded. You have to use clover in 10.x folders and or Other folder. *mentioned before* My 950Pro runs flawlessly after contacting Gigabyte support for releasing an appropriate bios. From what I can tell if the driver/ssds not working properly blame your mainboard manufacturer for it.- gigabyte support was outstanding they even provided the skylake register fix with the new bios when I asked them to do so. Regards
  6. jan-munich

    NVMe Express digging

    you should see this in your debug.log / system.log or clover boot log: 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: com_MinnowStor_NVMeDisk::start 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: This driver must be licensed for commercial use. 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: This driver may not be posted, distributed, bundled, shared, or sold without the written consent of MinnowStor.com 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: This driver is free for personal, non-commercial use. 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: No guarantee of performance, suitibility, or warranty expressed or implied. Use at your own risk. 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: Copyright 2015 MinnowStor, all rights reserved. 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: devid a802144d subdev a801 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: desc SM951 512 GB SSD [m.2] 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: unable to map BAR4 resources 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: MSICAP: 86 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: DATA: 4077 14/01/16 14:34:14,000 kernel[0]: NVMeGeneric: Using INTX interrupts 14/01/16 14:34:14,000 kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP09@1D/IOPP/PXSX@0/com_MinnowStor_NVMeDisk/com_MinnowStor_NVMeDiskStorageDevice/IOBlockStorageDriver/MinnowStor Samsung SSD 950 PRO 512GB Media/IOGUIDPartitionScheme/Untitled@2 If not the driver is not loaded properly. There is no need to copy the driver to S/L/E but just in clover / kexts/others. at least for me. Make sure you have the appropriate folder structure in clover either kexts/other or 10.x folders by setting the proper OS in the clover boot menu / config. I think its the easiest way to test by creating an USB stick with the OS installer and appropriate kext files. Boot into setup see if drive is detected as a starter.
  7. jan-munich

    NVMe Express digging

    But you installed the NvmeGeneric.kext to kexts/Other on your SSD right? What if you boot the osx installer with the kext in place do you see the drive? From your screenshot I can't see the driver is loading. Have you verified there is a log output and the nvme driver gets loaded properly?
  8. jan-munich

    NVMe Express digging

    Hey Sammlersen, that clarifies it, well I also had problems with NVMe Boot which originated from my bios @ gigabyte Z170. So after a little back and forth chatting with their support they pushed 2 beta versions and the second now works fine (Fast Boot + Skylake APCI Register fix included in the bios) But well im running skylake with on-board m.2. Maybe the X99 have some more problems.. :/ To quickly state the problems I had before the bios fix: 1. No boot if I disabled other sata devices in bios. 2. Usually using my wrong boot device (sata) to boot. 3. Could randomly find my UEFI boot on NVMe (So thats why i contacted gigabyte, to tell them their UEFI boot on NVMe is corrupted..) In the meantime i came with an itermediate solution until gigabyte fixed the bios : Installing clover onto a sata boot device boot clover from there and then select my nvme device in clover.. this worked fine and 100%. Finally i got rid of this workaround as the bios provided fixed it for me. - Kudos to gigabyte support even if they told me not officially supporting hackintoshes they helped me out. (Well it was UEFI boot issue anyway..) Regards Jan
  9. jan-munich

    NVMe Express digging

    What for exactly? If you put the driver in clover not in SLE you can boot fine with NVME and everything works OOB? If the drive would not get detected in the boot process the OS would not even load to the login screen.?
  10. Hi all, since Ive been in contact with the gigabyte support for a while after complaining about bad nvme speed while booting + the missing IOACPI 24-119 Register selection flag for Skylake (if you don't want to apply Pike's Fix) They managed to put up a new Bios F4c - just before christmas what a present.. This solves actually the slow boot speeds in clover + has the wished entry for IOACPI 24-119 Register selection as needed to get rid of the "waiting for root device" issue. Hope that helps anyone else out there thinking about an mini itx build: http://www.gigabyte.com/products/product-page.aspx?pid=5529#bios Kudos to gigabyte support for their help! Regards Jan
  11. jan-munich

    NVMe Express digging

    maybe thats because of the requirements of the bundle libraries inside the driver? (not sure if thats actually a problem..) have you tried to run the cli: ./nvme-cli list to see if your device gets detected via the driver?
  12. jan-munich

    NVMe Express digging

    i think you refering to : http://www.overclock.net/t/1571271/tutorial-how-to-add-nvme-support-on-any-ami-uefi-bios-with-an-intel-chipset that just works for ami uefi which are many bios but not all of them. My bios supports nvme already, but it seems it has troubles with uefi nvme boot / also not detecting the ssd properly in bios -> but in boot selection screen. (had it running on ubuntu last week) im not sure if flashing the bios actually helps to encounter that issue? anyone tried already?
  13. jan-munich

    NVMe Express digging

    your welcome. good to know that this causes the issue. maybe you can also leave it in SLE but use the forcekextload function of clover.?
  14. jan-munich

    NVMe Express digging

    i actually had problems to get my bios/uefi to boot/recognize clover when placed on the nvme drive.. i guess thats a bios problem, so i placed clover on another drive. not optimal but good until gigabyte releases a proper update..
  15. jan-munich

    NVMe Express digging

    Hey all, quick update: Thanks again @ jimj first for your effords and following this thread from time to time. I was able to get my 950Pro to boot, I reinstalled osx and have the genericnvme.kext now in clover kext other -> but not in SLE. (maybe thats a problem for some of you?) It also shows up early in the boot process so if you can't get it booting I presume its more an mobo / bios issue. I also directly updated to 10.11.2 and everything runs fine. I also run AJA to have a better comparsion as jimj mentioned blackmagic speed test does not seem to reflect proper speeds.. So all in all running smooth right know.
×