Jump to content

metaphysician

Members
  • Content Count

    37
  • Joined

  • Last visited

About metaphysician

  • Rank
    InsanelyMac Protégé
  1. okay, I managed to solve the problem, which seems to be with the installer USB I created. I downloaded and used the Olarilla image (thanks Mald0n!!), and everything worked perfectly pretty much from that point on. I have USB, Sleep, and the basic GPU detected. sorry about my panic earlier! a few questions though: 1. having a weird issue where I get the EFI partition for the boot drive showing up and then sometime after booting (maybe and hour or two?) it unexpectedly dismounts that partition as well as another mounted drive. the rest of the drives are untouched. it shouldn't be normally showing the EFI partition I would think. have you heard of this? 2. the system shows I have a 650Ti card but the menu bar isn't transparent, and the System Profiler does not show the 'QE' designation that I remember. I upgraded from Yosemite and it seems like Quartz Extreme is being replaced by Metal. So should the menu bar normally be transparent if the card is fully recognized? 3. i have software on other drives that needs to run under Yosemite, but I'm not sure what needs to be done to the kexts or the Clover boot configuration to do this. i seem to remember that you could have different folders for different OS versions to load specific kexts. i know there is a strong tendency to always go for the latest and greatest, but what forum area should I post on to be able to switch between 10.13 and 10.10? 4. any easy way to get ALC1220 audio drivers to work? the system doesn't show anything. would prefer without DSDT if possible, but happy to use it if I need to.
  2. okay i really need help here. i went to using the Tony Mac uni, which did actually create an EFI partition ( The Create Install Media app did not do this task). but i am unable to boot from either partition. the only task that i did differently had to do with the High Sierra installer. it came as a 19MB download so i found out a way to get the installer to download the rest of the files. they downloaded into a folder i can't remember the name directly onto the HD. but i took all of those files in that folder (including InstallESDDmg.pkg) and copied them to the Contents>SharedSupport directory under the app (i had to create the SharedSupport directory). i'm not 100% sure if the naming is correct - i followed the conventions of the Sierra installer i had which is a full installer. i checked the permissions and they were set the same as the other folders. i really don't think this should be an issue - unless maybe the naming convention or placement or filepath changed for High Sierra compared to Sierra. as it is, right now i am booting UEFI, and the USB stick has two partitions. selecting either partition fails. if i pick the UEFI partition it will hang, but if i select the other one it will fail and go into BIOS again. at this point i'm not even getting to the Boot Maintenence Manager window. i just get nothing. there must be something i'm not doing correctly. any assistance appreciated! especially from anyone with Gigabyte z370 boards. it just can't be this difficult to just get into Clover. i was using Clover r4813 BTW but the installer i just configured has a different Clover version i'd bet.
  3. i'm not using Legacy Boot. BIOS is configured for UEFI booting. but no matter what i do it goes to the same window - it looks like it's called the Boot Maintenence Manager. i'm reading that it might be because i have no USB2 ports. i hope that's not the issue. i have enabled Legacy support on the USB configuration. Update - okay it seems Boot Maintenence Manager is expressly for Legacy booting devices. if i turn off Legacy support on USB then my USB stick is not recognized by the system. i know my USB stick is most likely a USB 2 device. however i think the more serious issue is that it sees no boot device in the list for Boot Manager or Device Manager. so something is really strange. i've tried in UEFI booting mode as well as Legacy - no difference. i still see no choices to boot from.
  4. hi Mald0n and everybody it's been several years and i'm finally back at the hackintosh thing. i followed the instructions pretty closely and downloaded what i thought i needed. motherboard is a Gigabyte Z370 XP SLI, running BIOS F11. i'm currently unable to boot from the USB stick with Clover on it. i get 'boot6' and then it goes to the gray screen with the blue and black DOS-like lettering. if i go into the Boot Manager everything is empty. same with the Device Manager. i cannot seem to add boot options in the Boot Maintenance Manager either. as far as the tasks i used Create Installer Media to make the USB disk with High Sierra on it , for Clover i installed the one you linked to on the stick and replaced the folder with the one you linked from Olarilla. not sure what else i can do at this point - i am dead in the water right now. any help appreciated!
  5. @cyberdevs - OK will download Clover Configurator and try these. just to bring you up to date, the Sierra install on the HD has no EFI folder. the EFI folder exists on the older bootloader USB stick and is version 3556, which means i don't have a dedicated folder for 10.12 available since it hadn't been released yet. so i did install the AppleALC.kext and Lilu.kext in S/L/E and i haven't done anything else yet. ideally i would like to update Clover on this USB stick, but i don't want to lose my current settings. do you know the best way to proceed here? in the meantime, though, i will download Clover Configurator and try your fixes for USB and audio. i'll keep you informed as to progress. thanks very much again!
  6. Update - i switched to a different rear USB port which helped me to run the initial Sierra installer. interestingly when i rebooted back into Yosemite i saw the install hadn't completed yet (the disk has a folder called macOS Install Data so it needs to finish obviously) also the USB port that worked while installing Sierra was dead when i was in Yosemite. switching the cable back to the original port (i think it's a USB 2.0 port not a 3.0 port) worked fine. will keep updating the post as i progress. Update 2 - Okay install went surprisingly smooth! here's what works: boots fine with either Clover bootloader Ethernet GPU with Metal support - full transparency Firewire 2 USB 3.0 ports (Intel based) Audio (via Firewire interface) Here's what's not working All USB 2.0 ports (which should be Intel) 2 USB 3.1 Ports (which are ASRock and can't be used at all) Onboard audio (uses an ALC889 i believe) Sleep/PM (i usually give up on this) The most important of these to get working is USB 2.0. i'm not concerned about the rest, though if onboard audio was possible it would be useful to have. i did play around a bit on the BIOS to see if changing settings would work by disabling legacy USB 3.0, but at that point the USB stick with the bootloader failed to be recognized. so nothing is changed on my USB BIOS settings at the moment. i am attaching an image for clarification. i am imagining that if the port is blue it's a USB 3 port, otherwise its USB 2.
  7. Okay updated the signature. just to be clear, i'll paste it here OS:Yosemite 10.10.5 (want to upgrade to Sierra) MOBO:ASUS P8Z77-V Le Plus CPU:Intel Core i5 3750K GPU:NVIDIA GTX 650 Ti >>Secondly tell if you are using Legacy BIOS or UEFI? almost certain i'm using UEFI. >>About the USB ports you need to know that ASMedia on old mainboards is not supported by macOS and you need to use the Intel ports which are supported by macOS and >>you can use USB port limit patch to increase the number of the USB ports or you can create the Custom SSDT for your intel ports. right i read that. it seems it's possible to use a different controller for the port. i'm not using a lot of USB devices (a hub and one separate drive), so maybe i can just switch existing hardware to an Intel supported USB 3.0 port. >>You can either use a patched DSDT for your mainboard or you can use Clover's patches to fix certain problems with your mainboard. whatever works is fine. would prefer a patch to start with but if DSDT gets better results i'll use that. >>For creating the the USB installer the best course of action is to use the createinstallmedia method and once the USB disk is created just install clover and then add the >>necessary kext files with the working config.plist i did create the installer stick with Ares and then i added the latest Clover with Zeus. it looks like the kexts did not go into the CLOVER folder. i can add them there. i also did not change the default config.plist that was generated by the Clover installer. >>Send me your EFI folder and I will take a look at it. i will send you two EFI folders. one of them is from the new version of Clover i just installed on the stick,which is not bootloading (boot 0 error), the other is the bootloader from the working Yosemite drive. someone helped me with the EFI folder on that one after i had a lot of Firewire instability issues (external card but had good vanilla support generally). I have looked carefully at the Yosemite EFI folder and i can't find find a DSDT or SSDT file, just three kexts in the 10.10 folder, so i'm not sure what that person did to fix my Firewire issues. here are the links: First the EFI from the Sierra installer USB i created with createmedia: https://www.dropbox.com/s/w148hbsdj82gh2a/EFI-Sierra.zip?dl=0 next the working EFI from my Yosemite based bootloader: https://www.dropbox.com/s/4s7v9t8bzg5lcl3/EFI-Yosemite.zip?dl=0 question for you: it looks like i could use the Clover bootloader for multiple drives with different OSes, so i am wondering how easy it is to update the older Clover on the working bootloader? the Yosemite bootloader is actually on a separate USB stick. i had intended on copying it to the HD but never did it. anyway, help appreciated - thanks! not trying to confuse you too much. just trying to be thorough. i also realize that just because the current bootloader works on Yosemite that's no guarantee it will work on Sierra without any modification.
  8. hey @cyberdevs, i'm needing some assistance, on a sort of similar motherboard - ASUS p8Z77-V Le Plus, with a GTX650 Ti, upgrading to Sierra 10.12.6 from Yosemite 10.10.5. i'm somewhat experienced in hackintosh, built two already, updating my 2nd. i had a lot of exchanges with Carbo167(Marco) previously and he was very helpful but i think he doesn't have his old motherboard (same as mine). anyway i used Pandora to create a USB stick of the installer and installed latest Clover with FakeSMC, and NullCPUPowermanagement, and left everything else alone. i wasn't able to bootload the installer stick (boot 0 error) but i was able to use my other bootloader on a different drive (older Clover version) to load the OS on the stick. i'm not too concerned about all this as long as i can get the stick to load. my first issue though was that i had no USB on restart, so i can't even start the install process. i could use Pandora to install the Maverics USB rollback on the stick, but not sure if there's a better option. i see stuff about SSDT and using InjectAll and also saw other posts about just editing the SSDT directly with pjalm's USB edits via MacIASL. my plan is to install everything on a drive that has Mountain Lion on it, and i'll remove all the OS folders so it's a clean install, but i'd rather not have to reformat the drive if possible. i will keep my Yosemite drive as is until i'm confident the other drive is stable. any assistance appreciated! i'm using latest Clover EFI version so any useful EFI options for USB drivers would be useful. thanks!
  9. metaphysician

    Pandora's Box III

    hey Micky and everybody, just used the Pandora's Box almost latest version. used createinstall to make bootable disk for Sierra 10.12.6, couldn't boot with it - got boot0 errors. i was able to use an earlier Clover bootloader i had installed on a small USB flash drive, so that's not a big problem, and it appears the installer boots up fine, except that i have no USB ports, or at least no rear ports. so i'm wondering if i need to install a USB rollback, perhaps? Specs are ASUS P8Z77-V-LE Plus /3750K i5, and pretty sure i'm booting with UEFI. i'm mainly interested in the lack of USB at the moment since i do need that to run the installer. any help appreciated!
  10. hi there folks! i'm having a bit of an issue getting Clover to recognize the F4 key at boot time to generate the ACPI information needed. here's the deal - i'm currently booting from a pendrive and i do NOT have Clover actually installed on any of my main drives. i was definitely planning on it, however. Clover solved a huge amount of issues that were not working with my Chameleon/Enoch bootloader, but because this is my production machine, i really needed to make sure i wasn't going to ruin things with Clover installed directly. i had already cloned my original drive for extra safety. so with a working bootloader pendrive i was then able to update the clone to Yosemite 10.10.5 using this method. so far so good! i can now boot any of my drives on my system but i have two issues that seem to be present on the Yosemite drive: 1. No USB 3.0 support 2. Can't shutdown or restart easily so i need to find out the hardware situation on the computer, and thus i need to generate the ACPI tables at boot time. i have tried using F4 but i'm not sure how long to hold the key or whether this works. i believe my bootloader USB disk does NOT have an EFI partition on it, which means it is HFS+, and i think that means the ACPI can't be written? but the main OS drive i am booting with the bootloader does have an EFI partition with firmware.scap file. can you add a EFI partition on the bootloader drive after the fact? or would i have to redo the bootloader drive? any assistance appreciated! Hardware: Mobo: ASUS P8Z77-LE Plus with modded BIOS 0606 (avoids NullCPUPowerManager.kext) CPU - Core i5 3750K GPU - PNY branded Nvidia 650Ti 1GB OS - 10.10.5
  11. metaphysician

    Pandora's Box III

    okay, an update on the situation - i decided to try using Clover, and i found a way to do it without having to install the bootloader to an existing drive and overwriting my Chameleon/Enoch bootloader. i can see why Clover is popular. i was not only able to easily boot my old drives that were using Chameleon, i was finally able to run the Pandora Installer for Yosemite as well! so i have now successfully installed it and am now working in Yosemite with basically no major issues, using a small pendrive to load Clover and then booting the disk after that. i have onboard sound, network, and video card all recognized. have not tested USB 3.0 yet but i will. technically the drive is clone of my previous drive so all the extra kexts i needed were already in the folder. i've only had to update the Firewire audio driver for my interface. the only issue i have at the moment is that i cannot shut down or restart. i know there are a number of fixes to this symptom out there so i'll need to research that. i also need to get you the ACPI information by pressing F4 at boot time. at the moment, i'm really exhausted, so i will get you the information when i get some sleep. in the meantime, the hardware specs are: Mobo:ASUS P8Z77-V-LE Plus - BIOS version 0606 modded (means i do not need NullCPUPowerManager.kext). CPU - Intel Core i5 3750K RAM - Kingston Hyper X - 16GB (2 X8GB) Video Card - Nvidia GTX 650Ti 1GB from PNY OS Yosemite 10.10.5 Extra Firewire 400 card as it is, i am currently not using a DSDT in the Clover bootloader pendrive, but it still does exist in my Extra folder on the other drives. i don't know whether Clover takes those folders into account when booting or not. it doesn't really matter - just curious. once i test USB 3.0 and fix the shutdown/restart glitch i will install Clover to the new main drive and i will be done. i thank you immensely for the help, and sorry if i'm making your life difficult with all the changes. at any rate i think Pandora's Box is a great tool and does quite a lot very efficiently, and i appreciate all the work that went into making a pretty smooth user experience! best, scott
  12. metaphysician

    Pandora's Box III

    hey Micky, i am still having issues with trying to get my pendrive to boot properly. here's what has been done so far: i DL new fresh Yosemite installer and made new pendrive from it using Restore method and added FakeSMC.kext i decided to install the Enoch bootloader on the drive. i did not pick any options just the basic install. then i copied my DSDT.aml and boot.plist file from my other drive. on first boot it boots successfully to the installer, but i have no USB response at all. if i change the USB drivers afterwards by rollback through Zeus (Zeus only has ML and SL rollback, but i also tried Maverick's version by hand), the result will be that the computer will not boot and gets stuck at 'Attempting to loading drivers'. it behaves the same even if i put the original drivers back. i tried to use either Zeus or Kext Wizard so that it would repair permissions and rebuild cache, but the result is always the same. the only way to get it to reboot fully after changing the USB drivers in any way is to erase the pendrive and start over from scratch. after this it will boot one time reliably but the USB issue remains. i don't know why i can only get it to boot just once. if i mess with the kexts at all post booting, some setting gets changed and then i can't boot it anymore. very unreliable. also i think i discovered a bug. when attempting to use the ML USB rollback in Zeus no kexts were actually copied to the volume under S/L/E, although the Yosemite versions of the kexts were deleted. this definitely created issues when booting. will keep working on this of course, but if there's any way to reset the booting i would definitely like to know. EDIT tried again, this time with adding the USB 3.0 generic driver plus the bootloader. no luck - same issues in booting. it seems that it only works generically out of the box with the latest USB kexts. very frustrating. some day i hope to live in a world where a hackintosh install isn't a 3 day plus nightmare, but so far i've never had that luxury, and we're already at day two.
  13. metaphysician

    Pandora's Box OS X installer

    it may indeed be incredible, but i'm definitely not the only user who has encountered that identifying number. i found at least two other errors with that number installing Yosemite. it's possible that the vanilla installer i have was a late golden master before the actual release came out. that or the Inmac team put an old kernel in their version. you are absolutely right though - i do see the results of searches are mainly about Snow Leopard. i also just checked my kernel version on ML and it's 2050, not 1502. so i think this disk image is definitely suspect. anyway, so far i've only followed Carbo's method in his guide on this site and downloaded Pandora's Box. i haven't tried a bunch of different approaches at this point. i've downloaded a legit Yosemite installer, so i will try the restore method to re-create the pendrive in Pandora/Hermes, and see what happens. grazie mille for your feedback. very helpful! best, scott
  14. metaphysician

    Pandora's Box OS X installer

    actually - this is extremely helpful, Micky! i got the kernel from Carbo's post over here, because i do not run Pacifist. perhaps i should... do you perhaps have a link to a newer kernel from Yosemite? i did use the 'createinstallmedia' option using my Macbook which has 10.10 installed, but the odd thing is that on the current Hackintosh's bootloader (Enoch 2822), it did not find the kernel when i booted from the pendrive. Carbo's post suggested that it might not under Chameleon and to manually place the kernel instead, so i did this using his files. i have now just downloaded Pacifist and followed his instructions exactly. the kernel i extracted appears to be exactly the same - modification date is is 19th of Sep, 2014. that can't be Snow Leopard. i did remember something on this particular machine... when i was first installing the Mountain Lion OS a few years back, i chose to downgrade the BIOS for the motherboard to eliminate the need for NullCPUPowermanagement.kext. i don't know if that could possibly be the issue, but to me it does not appear to be caused by an old kernel as far as i can tell. i can replace the one i have but it's totally identical as far as i can see. here's a post from a Reddit user that has the exact same error. his turned out to be Ethernet card related:h/comments/3elcdm/kernal_panic_unable_to_find_driver/ i don't really believe the NIC is the issue here, but what can be done to narrow down the problem? his post said something about having an option to Fix LAN on ACPI and to install other NIC drivers under MltBst(the tool that should not be named ).
  15. metaphysician

    Pandora's Box OS X installer

    hey Micky - currently having a difficult time on Pandora's Box. i think i created the installation USB pendrive correctly, though in creating the pendrive, i chose not to install a bootloader, but instead use the Chameleon/Enoch bootloader i already had on another drive. i definitely did install FakeSMC.kext. i also had to copy the Kernels folder from Carbo's excellent Guide to Installing Yosemite 10.10 because it could not find the kernel. once i did that i was able to start the booting process. however i immediately ran into issues. there were several messages relating to kext loading ("name" not a kext, Kernel-__SYMTAB not a kext. and DriversPackage-d32000 not a kext). there was also a kernel panic as follows: \"ACPI\".n"@/SourceCache/xnu/xnu-1504.15.2/iokit/Kernel /IOPlatformExpert.cpp:1590" acpi=off does not work, DropSSDT=Yes does not work. i have done it with and without DSDT and chameleon boot.plist in the Extras folder. no difference. Enoch version on the main SSD drive is 2822 i think. i will keep working on this, but do you have any further suggestions? thanks! EDIT: just as a background i am on 10.8.5. i made the pendrive on my laptop which has 10.10 installed. on the main SSD drive/bootloader i use Enoch/Chameleon with a DSDT that Carbo provided as he has the same mobo as me (Asus P8Z77-LE Plus). i also added NullCPUPowerManagement.kext and the ACPIPlatform.kext rollback to the Extra folder. no difference. maybe it makes no difference because i'm putting it in the Extra folder and because there's no local bootloader it doesn't work? i just thought it would use the bootloader's settings on the main drive but then look at local paths to load DSDT and kexts. but so far it seems like like it's ignoring everything i do and having the same kernel panic every time. Carbo's guide says to install the bootloader on the pendrive but i did try this manually before i tried using Pandora's Box and it did not seem to work out. also there does not appear to be a System/Library/Extensions folder. i have a kextcache i think, so maybe that's what Pandora is using when booting? anyway, i'm definitely stuck at the moment. any help appreciated! best, scott
×