Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About voodoor

  • Rank
    InsanelyMac Protégé
  1. Pandora's Box (Beta 2 Testing)

    I've had my first go with Pandora 1.34 beta2. I used it to create a 'Mode 2' (not sure if that was the best option?), Pandora-style USB of Mavericks - I created it on a iATKOS S3 install. I installed to a 8GB USB pen drive and apparently all went fine but it didn't even boot as far as chameleon or whatever bootloader it uses: boot1: error Was as far as I got! Some of the Pandora install screens definitely need more or clearer explanation of the options - especially the one which asks you to pick 1 of 3 modes - 'original' (?), mode 2 that has USB3 or mode 3 that drops the gfx drivers during install, or something. Each option needs more explanation of who should use it and when / under what circumstances. Networking doesn't work on my Hack so I was unable to reference the online help whilst I was installing. I was also very unsure if to go for retail or a Pandora install. Also, it seems that when Pandora asks for the install image, it really means the InstallEMD.dmg, not the full OSX install dmg so it should really ask for InstallESD.dmg specifically.
  2. Pandora's Box (Beta 2 Testing)

    Is Pandora likely to handle installation (of 10.8.5 or 10.9) on Haswell machines like mine or not? When doing a vanilla install I had to replace mach_kernel with rehabman's patched kernel to get as far as the installer, same goes for myHack but myHack would crash after selecting the language to use. Hopefully Pandora will fare better?
  3. Thanks for the suggestions guys! I don't have the cash or the desire to buy another rig solely for OSX. In fact I only want OSX to run 1 app - REAPER - as they're dragging their feet with their Linux port and I don't much like running music production software under wine even though REAPER is officially supported running under Linux/wine. Running a native build will always have the edge. I did understand that Apple only released Mav as free upgrade so it was funny that some in the tech press hyped it as a rival to Linux all of a sudden, when really nothing had changed. I'd heard of Pandora and that now seems like my last viable option to try getting a working install before I throw in the towel and return to the 'it just works' simplicity of good ol' Linux!
  4. Hi RehabMan! I didn't think it was BT causing my boot prob seeing as I know that works already seeing as I used it during install. We can't expect you to cover everything about OSX PM in this thread so thanks for the tips! I've added the basic specs of my machine to my sig - is there anything more I should add?
  5. Hi rockinron! I'm sorry but his post upset me as it wasn't helpful at all. If people can't answer a forum posting or they think its a waste of time, they should just ignore it instead of claiming I'd not done my research when you know I've been trying very hard, doing lots of reading on the subject and I'm on topic. Maybe I would create such a tool myself if I had the knowledge to do so but when it comes to Hackintosh I openly admit I'm a noob. Thankfully, we have people like you who are willing to help us noobs and without people like you this scene would die pretty quick!
  6. Rehab: Aha! You made no mention of the need for a custom SSDT in the OP nor the need for DropSSDT=Yes , GeneratePStates=No and GenerateCStates=No. Maybe it would be worth updating the OP with this info until you get round to writing a more complete guide? The guide I followed to do a vanilla Mavericks install is: http://www.insanelymac.com/forum/topic/280756-guide-the-all-in-one-guide-to-vanilla-os-x-including-chameleon-dsdt-for-beginners-updated-for-mavericks/ This seems to be the most highly recommended guide for vanilla installs but it does not cover creating custom SSDT's so is there a guide you can recommend for doing this, preferably using Linux? If having to create and use custom SSDT's is common for vanilla installs then it should prob. be added to that guide. I have now tried all 15 IntelAzulFB settings, I've tried using DropSSDT=Yes , GeneratePStates=No and GenerateCStates=No but nothing is getting me past the BT init phase of my 10.9 install. I've also tried doing a vanilla install of 10.8.5 but it seems to have the same early reboot issue as Mavericks does without your kernel. I tried using your kernel with 10.8.5 but that only resulted in a KP. I think its safe for you to remove Bluetooth as being untested from the OP as BT works fine for me during the 10.9 install when using your kernel. My laptop is using the H87 chipset.
  7. You sound like you are against the Hackintosh installation process being made easier and that it should only be possible for those with a deep understanding of OSX's internals. That's called elitism. I've already done 100's of hours of searching, reading and experimenting on this - easily - thank you v. much! Sounds like you'd ban Chameleon Wizard, MyHack, iATKOS etc and you'd have a raging fit if anyone ever released the sort of tool I'm after! Do you like wasting your time and damaging your hardware experimenting trying to do OSX installs? I just want to install and run the OS with minimum fuss. I like OSX but I don't like Apple or their hardware, which has seen a distinct down turn in both its build quality and fixability in recent years so I have even more reason not to want to buy a real Mac. If they officially supported installing OSX on non-Apple hardware, I'd happily pay for it but Apple are a hardware company primarily so I can't see that happening. Besides, Mavericks is 'Free' according to Apple's marketing! Anyway, I have: System 76 Gazelle Pro H87 chipset i7-4700MQ Intel HD4600 8GB RAM + 250GB Samsung 840 SSD PS I've owned both an iMac and the eMac - the eMac I still have but don't use anymore. I paid in full for the iMac - never again I said. Same goes for Sony!
  8. I've spent weeks trying different combinations of boot switches, kexts, SMBioses, SSDTs etc etc trying to get Mavericks to boot on my Haswell laptop but I've pretty much given up now. I've had much more success using distros on older hardware but doing vanilla installs can be a very tedious, time-consuming and drawn out procedure thats no good for the heath of yourself or your computer so I may just leave it now and try again when iATKOS or someone creates a Mavericks-based distro. Chameleon wizard is a step in the right direction but I think its a shame its OSX only as Janek wrote it in ObjC. If he'd wrote it in Qt instead we could've run it under Linux, OSX and maybe Windows too. As we all know, Linux supports much more hardware than OSX (and Darwin) and it runs nicely off USB or optical media so I'm wondering why no-one has created a tool to remove a lot of the guesswork out of getting OSX to install and/or boot that runs under Linux? Linux has lspci, lsusb, dmesg, dmidecode, hfs+ tools and all the info under /proc and /sys etc which in most cases should be able to provide enough info about the machine to translate this info into suitable boot flags for Chameleon, Clover or whatever. So far I have tried MyHack and a vanilla install using Chameleon. I don't have access to the App store so I can't use Tony's tools and Kakewalk doesn't support 10.9 yet. I have got OSX Mav to install but all my hacking has failed to get the installed system to boot past bluetooth init so I never see the desktop. I've tried a vanilla install of 10.8.5 with Chameleon too but that didn't even get as far as the installer. What is the most foolproof way to install Mavericks on a Haswell laptop?
  9. Hi Rehab! I don't think I would've been too happy with my laptop it it had any noisy fans. Thankfully, the Gazelle Pro (w/SSD, at least) is silent. I wish it had Iris Pro and more BIOS options but apart from those minor issues/wants I'm really happy with it so far although it'd be better if I could boot OSX too, of course! From reading your latest post, I think you are suggesting an initial boot command (or obcp equivalent) something like: -f -v GraphicsEnabler=Yes InjectIntel-ig=0x0a260006 The impression I get is that I should be using GraphicsEnabler=Yes as that auto-detects most of the graphics config then I'd use EITHER an InjectIntel-ig=0x0a260006 or pass IntelAzulFB and a mode value - the IntelAzulFB modes being akin to InjectIntel-ig 'presets', so to speak? That's my guess as to whats going on here, anyway! I have checked S/L/E on my SSD and AppleIntelFramebufferAzul.kext is there alright, but OSX never gets far enough (ie to the desktop) to let my access the terminal to run bdmesg so that's no use to me, unless there is some other way to run cli apps or boot OSX to a prompt that I don't know about. -f doesn't help things. A more verbose guide would be fantastic - I can't wait for that! I wonder if I'd have more luck using the Enoch bootloader or installing 10.8.5 instead?
  10. Hi rehabman! Thanks for looking at my errors, but I don't understand how you deduced its a graphics-related issue as I don't see anything in that screenshot that looks like it relates to GFX. Of course, its just text in that image as I used -v but if I don't I use -v I at least see the Apple logo when I boot off my 10.9 HD install. I presuming it must be because my boot has stalled at the point when the gfx drivers would normally get loaded? I have so far tried booting with GraphicsEnabler=Yes combined with IntelAzulFB and values from 0-9 but none of the AzulFB values I've tried so far have made any difference whatsoever - boot still stalls at the same point. As nice as it would be to have QE and GL working, I'd be happy enough with just unaccelerated ('VESA') gfx as this seems to work fine when I boot off USB so it makes no sense that I can't even get a basic graphical display as soon as I boot off HD? Its exactly the same OS! Is there some relatively easy way to discover and replicate the settings used when booting from USB? It'd be great if you could update the first post with a few more details on how you got (fully) functional GFX (and everything else) to work, making note if you had to use any patches or boot arguments etc. I'm presuming you used your voodoops2 kext to get your keyboard working?
  11. First, I owe rehabman an apology for not following his instructions properly! For my first attempt at doing a vanilla install, I didn't use the patched AppleIntelCPUPowerManagement so that probably explains why my laptop went into a coma. Let this be a warning to any future Haswell hackintoshers! I had left my brand new and presumed dead Haswell laptop unplugged for about 24 hours earlier after I had pretty much told System76 I was going to have to return it for repair but before boxing it back up I thought I'd have one last try and was delighted to see the LEDs light up when I inserted the PSU! I tried the power button and, lucky me, its back from the dead for more Hackintosh-related antics! After having replaced the official AppleIntelCPUPowerManagement with the patched 10.8.5 one, I was able to install Mavericks without any beeeping, computer comas or even a single boot flag. Amazingly, install 'just works' now so it was an unexpected disappointment that the HD install doesn't boot - even after replacing the kernel with the same one used to install (Rehab's). I have attached a screenshot of where my the booting of my HD install stalls. It looks like the drive is being mounted read-only, which doesn't sound right, although maybe thats not the problem here? I've tried fixing the permissions and verifying the drive but its not helped. The other issue I'm having now is my laptops integrated keyboard and trackpad aren't working. Bronxteck has already given me a link to a Elan pad driver (which I've not tried yet) but I'm more concerned about the keyboard. So far I've just tried Rehab's latest VoodooPS2 kext which claims to support Mavericks (and yes, I did read his (voodooPS2) instruction this time!) but that failed to get my keyboard to work. Are there any other kexts out there that may get my AT laptop keyboard working with Mavericks? I used a bluetooth one to install with but I wouldn't want to have to use that or an external USB one all the time. Thanks! http://imgur.com/d3gkfiA
  12. Hi bronxteck! (I can't say I'm surprised you read these forums too) Hopefully there is such a procedure as I'll be without it for a few weeks (at least?) if it needs to go back to the US. I couldn't see any mobo manuals or details on their site, I don't know what sort of MB or chipset it uses and nor do I want to bust it open to find out in case I invalidate the warranty. I've just written to them now but I don't expect I'll get a reply until tomorrow as its weekend. When I get it resolved I'll update these threads. Thanks for your help!
  13. Hi rockinron_1! You're saying I wasn't installing vanilla because I used Rehabman's kernel instead of the normal one, right? From my experience at trying to install Mavericks using the stock kernel + myHack and also from what I've read elsewhere (like Rehab's thread), installing 100% vanilla isn't possible on Haswell as you don't even get as far as the installer. OSX reboots a couple of seconds after boot unless you're using Rehab's kernel. RehabMan's kernel is identical to the stock 10.9 kernel except it doesn't have the new XNU (?) PM stuff compiled in as apparently that isn't open source. You're prob right that I should play it safe and pretend I wasn't trying to install OSX, just in case they void my warranty as its too much of a blow to take the risk. As well as being the first laptop I've ever bought (my existing one was donated to me so is quite outdated and faulty) its also the most expensive thing I've ever bought, having never bought a new car or a house or anything like that. I've not checked to see if it has any warranty tags/seals that may break if I try to remove the HD to remove the OSX partition as thats what I'll have to do if I'm going to pretend I wasn't attempting a Hackintosh install.
  14. Maybe, but I tested all the hardware under Ubuntu and Debian and all seemed well. It has been running Debian all day for the last few days (as I've been off work) without a hitch but its true that I hadn't got round to doing anything to really stress the CPU before this happened. However, surely installing an OS is only taxing the installation drive a bit. It shouldn't be a big stress on a (modern) CPU and I would've expected it would survive the 20/30m required to install OSX even if PM wasn't working correctly. Maybe not!
  15. It booted alright, but it also looks like I may have just killed my brand new Gazelle Pro laptop that I got 3 days ago in the process! What's worse is I'll have to ship it back to the US from the UK and I expect they'll make me pay for at least half of the postage - hopefully not but I'd be lucky! My Gazelle Pro is very similar, hardware-wise, to the HP laptop RehabMan has. He documented how he got Mavericks installed w/ pretty much all his hardware fully working in this thread: http://www.insanelymac.com/forum/topic/293503-haswell-early-reboot-mavericks-locked-msrs-and-hp-envy-15-j063cl-i7-4700mq/ I followed the first two parts of this guide (the vanilla install guide) to the letter with the two exceptions of not including the NullCPUPM kext (as I'd read not to in Rehab's Haswell thread) and I used the kernel from the RehabMan instead of using the stock one. I used the MBP8,3 SMBios as recommended in the first post of both Rehab's guide and this guide. I was happy to see the installer get much further than myHack did in that it didn't crash after choosing the language. Install seemed to go fine until there was about 5m remaining which is when my computer started beeping. I did realise that this likely meant it was starting to overheat but I'd just spent 3 full days trying to get 10.9 to install and I was almost at the finish line so I thought I'd see if it could survive a few more minutes and it seems that was a fatal mistake as my laptop shut down with 2m left to go of the install and it will not turn back on now! I think its prob. best that I be upfront with them and tell them exactly how it died and hope that installing OSX isn't cause for voiding my 1 year warranty. I've done 1000's of OS installs (of Linux and Windows) and I've never killed a machine before. Is this something that happens frequently with Hackintoshes? As for this guide, I think it may be best to add a warning to others to INSTANTLY turn off their computer if it starts emitting a loud beep every couple of seconds during installation so no-one else ends up in my sorry state!