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 jttraverse

  • Rank
    InsanelyMac Protégé
  1. I cannot remove a boot arg from one drive!?

    Thanks for the idea...in this case though I'm not using UEFI, just legacy bios. Whatever was happening was some how attached to the drive, and would cause that arg to be included no matter what I booted from (USB, etc.) I'd never seen anything like it. I ended up just formatting the drive and after that the arg was gone, so I reinstalled El Cap and finally have everything working.
  2. I have a weird thing happening this evening...somehow one drive seems to have a boot argument (nvda_drv=1) stuck in when it boots, but I can't find anywhere it's been enabled. It just started this evening, I hadn't been using nvda_drv=1 at all before this. But I thought I'd install the latest Nvidia drivers to see if they'd work, so after installing them I checked that flag in Clover Configurator. That's the first and only time it was ever enabled. Unfortunately, the system would die and reboot, so I removed that argument in Clover Configurator. But, when I boot into the Clover menu, nvda_drv=1 is still there! Fine, I removed it from the line in the Clover menu and made sure it wasn't selected anywhere else in the Clover options. But when I hit 'return' and get back to the Clover boot screen---it's back in the args line!! I went so far as to unplug this drive so I only booted from the USB stick, and the Clover boot menu in the USB stick is clean--no nvda args, etc. But if I boot from this one HDD, which has Clover loaded in EFI, then I have the above problem. I even deleted the EFI data and reinstalled Clover completely...and it still comes back! With the USB and HDD connected in the pc, if I boot to the USB that should be clean (as checked above) the nvda_drv=1 argument persists. It's as if it's somehow attached to the HDD now, and no matter what I boot with, nvda_drv=1 sticks into every boot option, so I can't avoid it. The only way to get past it is to also add nv_disable=1...so I get to the HDD OS. But that leaves just plane jane low-res graphics, not full screen, etc. Somehow that argument is definitely sticking into the boot args--but where is it coming from and how can I get rid of it? (I reset CMOS and it's still there...so unless it's burned into the BIOS for this one particular drive...I'm stumped.) Thanks..
  3. Thanks to both of you for the support. Here's my experience with updating, and I can say that short of one frustrating scare, things seem to be working fine again. I did backup my 10.8.3 version first, so I did have a disk image to fall back on in the event things didn't go well. For a while I thought I might have restore it, but maybe my experience can help someone else to be patient. I ran the update with no obvious problems, until I rebooted. Suddenly the USB keyboard and mouse were not functional anymore. They were apparently 'alive' because the lights were on and I could tap the 'Caps Lock' key and the keyboard would respond. But the mouse would not move, and I couldn't click or type anything. Stuck dead, and for a while after rebooting, the little spinning wheel was frozen too. Oh boy... I did boot to my USB drive and ran through a file system check and resetting permissions, since I saw online that someone suggested that for such problems. But nothing. I then tried copying over some of the kexts from my USB boot drive (IOUSBFamily.kext, IOUSBMassStorage.kext, FAKESMC, etc.) on the chance something was overwritten or changed. But it did look like the update had not removed or overwritten any of the previously installed ones, and at that point it still didn't work after rebooting. But while I was again on my laptop looking for clues to what might be the problem, I'd left my Hackintosh machine sitting for a while on the stuck screen--and suddenly it moved! For some reason, it seemed to have been caught in the the dreaded "10-15 minutes of nothing" delay I'd read about once or twice, after which everything started to work again. Whew, as fast as I could I ran through mul**beast again and simply reapplied some of the things I guessed might be good to reapply, and after rebooting it came back to life right away, with no apparently mouse/keyboard delay this time. (I can't honestly say that rerunning mul**beast again did anything, it was probably just superstitious thinking or hoping that while the keyboard and mouse were working I may as well run it and pray it might reset something.) Anyway, I really have no idea what caused the long delay before the USB mouse and keyboard suddenly came back to life, but it sure had me sweatin..and a headache now :/ But I'm relieved that the update does seem to be booting and running nicely now. Thanks to all, JTT
  4. @#%...you're right that it was a year ago, not weeks ago...my bad. Still, I'm really glad it did work for you and hope it makes life better a little
  5. I've just installed my first OS X on Intel, going with ML 10.8.3 from a .dmg, and everything is working fine. So, I now see there's an update to 10.8.4 and I'm wondering if anyone has any suggestions or experience with updates to a hackintosh installation...mainly whether it's safe to do them, or not. The only major changes I had to do to my installation was a Voodoo kext to get sound working, and exchanging a JMicron kext to get access to my IDE drive(s). But, do those things typically get replaced or overwritten when updating, and do updates more often than not whack some vital aspects of a Hackintosh installation on Intel? Help me Obi-wan-kenobi...I'm a noob at this, JTT
  6. RESOLVED! You are THE KING, sir! I'm on a MIS X58 Platinum mobo with JMicron (JMB363) controllers for the IDE port. Following through on your information, I tracked down the post below and downloaded and installed the kext (removed the existing JMicronATA.kext): http://www.osx86.net/view/942-jmicron36xata.kext.zip.html HUZZAH for Molvania! Works fine now, so thank you for the quick and helpful response. -JTT
  7. I've recently installed ML 10.8.3 on a machine that I dual-boot with Windows 8. As far as I can tell, everything seems to run perfectly well. The problem is, I have a second internal hard drive installed that is seen when I boot into Windows 8, but is not seen when I boot into OS X. If I boot into OS X, I can see the Windows 8 partition (on the same SATA drive), and I can work with the shared folders on that partition...but OS X does not see the 40gb drive. My primary drive is a SATA 500gb, the second drive is an older 40gb IDE drive, empty and formatted NTFS. The second drive does work; I originally installed Windows on it and then wiped it to use as a backup drive. It is recognized in the Bios and, in fact, it does show up onscreen when I boot up with a *beast USB flash drive installer. But when I get to the Disk Utility, it only shows the SATA drive, my DVD drive, and the USB drive--there's no sign of the 40gb drive. I did verify that my USB boot drive does have IOATAFamily.kext v.2.5.1 on it, so I don't think that's the problem. Also, when I boot directly from the SATA drive and reach the Chameleon bootloader screen, that also shows all three partitions--Mac OSX, Windows 8, and the 40gb Samsung. (Fwiw, I eventually set the Chameleon boot.plist to hide 40gb second drive so I didn't have to see it on the Chameleon screen, but it still works under Win 8 and so I doubt hiding it in Chameleon has anything to do with OS X not seeing it.) So, effectively, when I'm in any version of OS X, whether on the USB boot drive or the internat SATA installation, and I check Disk Utility or System Info--there's no sign that it even sees the 40gb drive is in my system. Anyone have an idea of why the OS X installation is not seeing my second internal drive? I'd sure appreciate any help or solutions. -JTT
  8. I got audio to finally work last night (3:30am..ug) after days of trying, so I'm hoping I can pass on something that might be useful as way of saying thanks to everyone who contributed to my own successes with OS X 10.8.3. This was my first Mac installation on an Intel PC, and I watched a lot of YouTube videos to get up to speed...so thanks also to YouTube et al. The only boot arg I actually needed after starting the install from a flash drive was-- PCIRootUID=0 -- the Mult**east utility was helpful with post-installation things, and after getting ML installed it was basically a nicely running Mac (barring the odd USB mouse/keyboard problem that was resolved--see my other post). (Apologies to InsanelyMac, as a newbie I'd started with the Uni***east setup processes. I wasted a lot of time before realizing they don't tell you they've crippled the new version to only work with an .app file downloaded from the Apple store. So, to all, check Youtube for a video with a link to an older non-crippled version and how to make an install USB drive from your .dmg. But there are other utilities that likely accomplish the same thing.) My system: MSI X58 Platinum mobo EVGA GeForce GTX 260 graphics card Onboard Realtek ACL888 chipset. However, I could not get sound to work with any of the widely discussed AppleHDA or AppleHDA1 kexts I found, or any other workarounds. My 'Sound' showed no input or output devices at all, until I came across the new VoodooHDA pkg at the link below: http://www.osx86.net..._installer.html The version 2.8.2 zip, uploaded within the last couple of weeks, did the trick, and the instructions are very clear. Once installed, it removes (backs up) any AppleHDA.kexts, and you now have a VoodooHDA 'prefpane' under System Preferences to make adjustments. Check the Mac 'Sound' controls, and hopefully you now have an Input/Output device showing. If so, you may be good to go (if not, hopefully something will get you there.) One thing to be aware if you don't have sound straight away. Per the instructions, definitely check Input Gain in the VoodooHDA prefpane. It defaults far to the left, but the Gain likely needs to be pushed far to the right to get any volume (obviously check your normal system volume too.) NOTE: If you still don't have sound, the instructions say you might need to enter a couple of lines in the info.plist file that is used by VoodooHDA.kext. This requires the 'Device ID', which isn't easy to find from what I could tell. I had to use Windows to find it, but in my system the Realtek ACL888 shows to be VEN=10EC DEV=0888 making the DeviceID in this example: 0x088810EC. SIDE NOTE: It's not complicated to edit the file, but the latest OS X version (Mountain Lion) apparently locks these important files and the usual TextEdit utility permissions no longer let you edit and save them directly. There are ways around it using Terminal, but that's tricky for some folks. If needed, try the free 'TextWrangler' editing program. I tried it and it's very nice, and if you do need to edit a 'locked' file it will ask you to give a 'root' administrator account when the time comes (use your own account and passwd, etc...presuming you have admin privileges.) Hope this helps you get audio working if you have a system like mine, or one that uses similar hardware. -JTT
  9. RESOLVED!: I'm following-up to my own earlier post to say that this is resolved to my own satisfaction...but I'm not sure I can explain it. After far too many hours fruitlessly looking for an answer, I got aggravated and, in a moment of frustration (or clarity), turned the computer around and yanked out the USB chords for the mouse and keyboard and plugged them into the front USB connectors on my PC, and 'lo and behold....they WORKED! I couldn't believe it, so I plugged them back into the top USB ports on the back of my machine (the ones directly beneath the PS2 ports), which is where they typically would be and is where they'd been working fine throughout the installation setup, and they were dead again. Finally, I unplugged them from those top two non-working USB ports and plugged them into the next two ports down, the ones directly under the original ones--and the keyboard and mouse both work again! I have no idea why the mouse and keyboard worked perfectly in the top two USB ports during the installation process all the way up to when I used Mult*be*st to get things to boot from the hard drive, only to stop working afterward. But after that first reboot from the hard drive, the keyboard and mouse will not work in the back top two USB ports. Very weird.. I've rebooted several times now with the keyboard and mouse plugged into the 2nd set of ports, and it's working without a hitch. So, fwiw to anyone who has this problem, do try some of your other USB ports as a test. Fortunately my board has several extra ports, and that saved me a lot more headaches. Now, if anyone has gotten their audio working on an MSI X58 Platinum motherboard, or knows how to do it, I could use any tips. Thanks, JTT
  10. A few others have apparently had this 'mouse/keyboard stop working' problem but I've not found any definitive answer or way to resolve it, so I'd appreciate any help or ideas. I can also understand now (to my chagrin) that InsanelyMac doesn't support that other T**yM*cx86 site. Unfortunately I did use a couple of their utilities..maybe that's the problem..but if anyone can follow my outline here and help with the overall problem, I humbly appreciate it. I used the UniBe*** boot-drive utility to install Mountain Lion 10.8.3 (on an MSI X58 Platinum with GeForce GTX 260, i7)...needed only PCIRootUID=0...and after that everything seemed to go more or less perfectly. After installation and it reboots the first time, with the USB boot drive still inserted I can boot into OS X and continue. It looks great and, as far as I can tell, at this point my mouse and keyboard and network all are working...only audio is not. I fired up MultiB**** (latest version) and, because I have no DSDT, checked the EasyB*** option and then selected the Realtek '888' audio drivers, which I have, the network driver, and a couple of other things, such as SATA trim, but nothing I didn't know and didn't think was needed. (Note: I've installed and reinstalled it all a couple of times, and tried it with the USB 3.0 option checked, and without it, but that made no difference with this problem.) After MultiB**** is done and I reboot (removing the USB boot drive this time)..it boots from the hard drive installation and goes all the way in--but the mouse and keyboard are dead. I cannot get them to come around at all. I've searched for a day or two on this, tried the boot arg 'USBBusFix=Yes" at boot up, but that didn't help. I've even gone into terminal and tried deleting/replacing IOUSBFamily.kext and IOUSBMassStorage.kext, but still nothing. My guess is that the first time around it's using the USB legacy drivers from the USB drive installer, and so the mouse/keyboard work all the way thru. But after I run Multib***, when it boots from whatever changes that applied to the hard drive installation, something in that kills the USB options and the mouse/keyboard die right at that moment. I can watch the lights on the keyboard start 'on'..and then after a few minutes...'off'. So I'm pretty sure it's something that's missing in the hard drive final setup files...I think..and I have to think it's possible to go in and add or remove whatever kext or plist is causing the problem, if I can do it in 'Terminal'. I'd love some help to get this fixed...and I'd really like to know exactly why it happens, for future reference. Thanks, JTT
  11. Inspiron 1501 success?

    My first post since rethinking trying to install OSx86, so I'd like to ask if anyone has had a successful installation on an Inspiron 1501? I've tried it a couple of times and never made it all the way thru... Recently downloaded Leo4All v.2 and iATKOS S3 v.2 to see what would happen. Originally it would only go to the grey 'apple' screen then die, and now I get stuck at the 'waiting for root device' error no matter what flags I try at boot time. Ah well... So, I'm up for recommendations. If someone has been able to get a version to install and work very well, I'd like to try it...hopefully get the latest/best version that will run on this old Dell model. I have a fairly vanilla Inspiron 1501: AMD 64 Athlon X2 ATI Radeon Xpress series display Hard drive: HDC WD1600BEKT-66GF3TA ATA Thanks, JTT