Jump to content

vtd[0] fault after 10.8.2 - google hasn't heard of it, any help?


  • Please log in to reply
34 replies to this topic

#21
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,277 posts
  • Gender:Male

To set that i was right at this point:

Who cares? I thought this thread was about the hackintosh issue. Waste of time to bump the thread with no news on that.

#22
tepaks

tepaks

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts
  • Gender:Male
  • Interests:Sinclair ZX Spectrum 48 +
    x86/x64 PC
    x86/x64 iHack

Who cares? I thought this thread was about the hackintosh issue. Waste of time to bump the thread with no news on that.


I care, reading this thread wasn't waste of time and it helped me solve KP after 10.8.2 combo on my new iHack.

TNX all who joined and contributed they knowledge to this discussion.
If I was only lucky enough to bump to this thread sooner, instead of spending so manny hours goggling for the right solution.

#23
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,277 posts
  • Gender:Male

I care, reading this thread wasn't waste of time and it helped me solve KP after 10.8.2 combo on my new iHack.

TNX all who joined and contributed they knowledge to this discussion.
If I was only lucky enough to bump to this thread sooner, instead of spending so manny hours goggling for the right solution.

I was being harsh, but the point was a post that is labeled "fix" but isn't applicable to hackintosh; and required followup questions to even understand the point, did little more than add confusion. I certainly felt like it wasted my time which is why I got frustrated.

But yes, I agree the workarounds I provide in this thread are quite useful and this information should probably be stickied (perhaps rewritten as a solution instead of an investigation).

Anyways, back on topic... I don't think disabling vt-d in bios is a good workaround as then you can't run a virtual machine (fails for me with virtualbox). Has anyone tested virtual machine guests under osx with the dart=0 solution or dropdmar solutions? I would think they'd work with the former but not the later.

#24
Frank Nitty

Frank Nitty

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 127 posts
  • Gender:Male
  • Location:Rock Town
  • Interests:iHustle
Finally, I think I have found what I have been looking for to solve the problem I've been having which was preventing my GTX680 from working in Lion (10.7.4)... I will try this out when I get home. To follow the papertrail detailing what troubleshooting have already performed visit here.

#25
tepaks

tepaks

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts
  • Gender:Male
  • Interests:Sinclair ZX Spectrum 48 +
    x86/x64 PC
    x86/x64 iHack

Anyways, back on topic... I don't think disabling vt-d in bios is a good workaround as then you can't run a virtual machine (fails for me with virtualbox). Has anyone tested virtual machine guests under osx with the dart=0 solution or dropdmar solutions? I would think they'd work with the former but not the later.


Disabling vt-d in bios didn't work on my iHack. Only after adding dart=0 I was able to boot in to 10.8.3. just to find out that it rendered VMWare Fusion useless.


So for those who want to use virtual machines this isn't a good fix but to all others it may be a good temporary solution instead of rolling back AppleACPIPlatform.kext to 10.8.1



#26
Frank Nitty

Frank Nitty

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 127 posts
  • Gender:Male
  • Location:Rock Town
  • Interests:iHustle
First I've already attempted to change VT-d into VT-x in the BIOS but the only problem is that that is not an option in my BIOS.

Every solution above was no dice for me. I tried using the following bootflags in my Boot.plist:
<key>DropDMAR</key>
<string>Yes</string>

then I used:

<key>Kernel Flags</key>
<string>-v dart=0</string>

and then I used a previous version of AppleAPCIPlatform from Lion which didnt change anything. I thought my issue may have been somewhat related to the members who were receiving the vtd[0] fault error.

The error I receive happens to be:
/drv/ Hyploctls.c:779 loctl VT-d status:0
Has anybody got a fix to this? Thanks

#27
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,277 posts
  • Gender:Male

Disabling vt-d in bios didn't work on my iHack. Only after adding dart=0 I was able to boot in to 10.8.3. just to find out that it rendered VMWare Fusion useless.

So for those who want to use virtual machines this isn't a good fix but to all others it may be a good temporary solution instead of rolling back AppleACPIPlatform.kext to 10.8.1

I just tested VirtualBox, and it is working fine on my hackintosh that was booted with dart=0. I believe this is because virtualbox isn't trying to do pci hardware virtualization (vt-d) on osx hosts. When using a linux host on a system that can disable vt-d, virtualbox fails to start if I have vt-d disabled in bios, and works otherwise. Virtualbox supports vt-d for linux hosts.

So I disagree, and further I wouldn't recommend rolling back a kext as a medium term solution; I'd recommend going with virtualbox instead or using a patch like dukzry's on the 10.8.3 code so that you're running the right version of the kext.

#28
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,277 posts
  • Gender:Male

The error I receive happens to be:

/drv/ Hyploctls.c:779 loctl VT-d status:0
Has anybody got a fix to this? Thanks

From your blurry screenshot, it looks like your error is about HypIoctls.c not Hyploctls.c (would explain why you're having trouble searching on it).
I don't believe that error comes from any of the stock osx drivers, looks like you're getting it from parallels.
Seems like a bunch of non hackintosh parallels users have the same error. Perhaps you need to update to a newer version of parallels?

#29
Frank Nitty

Frank Nitty

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 127 posts
  • Gender:Male
  • Location:Rock Town
  • Interests:iHustle

From your blurry screenshot, it looks like your error is about HypIoctls.c not Hyploctls.c (would explain why you're having trouble searching on it).
I don't believe that error comes from any of the stock osx drivers, looks like you're getting it from parallels.
Seems like a bunch of non hackintosh parallels users have the same error. Perhaps you need to update to a newer version of parallels?


But I'm using Parallels Desktop 7.0.15098. Now I know it's not that old, is it?

#30
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,277 posts
  • Gender:Male

But I'm using Parallels Desktop 7.0.15098. Now I know it's not that old, is it?

11 months. Mountain lion support wasn't official until version 15104 according to the release notes.
You could start troubleshooting by moving your parallels kexts out of /S/L/E and see if your hang still occurs.

#31
Frank Nitty

Frank Nitty

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 127 posts
  • Gender:Male
  • Location:Rock Town
  • Interests:iHustle

11 months. Mountain lion support wasn't official until version 15104 according to the release notes.
You could start troubleshooting by moving your parallels kexts out of /S/L/E and see if your hang still occurs.

I see what you're saying but only my problem is relating to Lion, 10.7.4

#32
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,277 posts
  • Gender:Male

I see what you're saying but only my problem is relating to Lion, 10.7.4

Pretty off topic then as this thread is about 10.8.2+ vt-d changes.
I'd still recommend troubleshooting as above.

#33
Frank Nitty

Frank Nitty

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 127 posts
  • Gender:Male
  • Location:Rock Town
  • Interests:iHustle

Pretty off topic then as this thread is about 10.8.2+ vt-d changes.
I'd still recommend troubleshooting as above.


Yeah, true, I figured that much but I have had no luck finding a solution. What I was initially trying to accomplish at first before that error happened was use my GTX 680 on my Lion partition and there are no official drivers available for Lion that have been able to work to my benefit. I was suggested to try out these drivers here and its been an off and on troubleshooting cycle from there.

Here is my original thread where I addressed this issue: here

#34
Frank Nitty

Frank Nitty

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 127 posts
  • Gender:Male
  • Location:Rock Town
  • Interests:iHustle
I just figured out that the problem has nothing to do with Virtualization at all hence the above error:
/drv/ Hyploctls.c:779 loctl VT-d status:0
I removed the NVIDIA drivers from the MacBookProMid2012SoftwareUpd1.0 pkg that I linked above and reinstalled the default 10.7.4 NVIDIA drivers (and repaired permissions). I was able to successfully access my Lion partition and uninstall Parallels. Restarted the system and accessed the Lion drive again. I reinstalled the NVIDIA drivers from the MacBookProMid2012SoftwareUpd1.0 pkg and repaired permissions. When I restarted the system and I am now stuck on:
macx_swapon SUCCESS
So I guess I'm making some progress...

#35
blackosx

blackosx

    InsanelyMacaholic

  • Coders
  • 3,054 posts
  • Gender:Male
  • Location:UK

one can simply configure the kernel boot argument: dart=0 to avoid the DMAR processing.
...
...
Perhaps it'll catch on like my npci=0x2000 workaround did :)

Thanks again for finding and posting solutions/workarounds bcc9.
I know it was eight months ago you posted it, but it finally caught on here.!
Regards





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy