66 replies to this topic

[jamesst20]

Up ?

Cant we do anything for this? Infos when it works

[q64ceo]

try always booting with -f

[jamesst20]

Did already, always boot with it

[q64ceo]

Did already, always boot with it

Try the opposite and remove it, then. Boot twice without it. That may work.

[eep357]

As I said, disable USB3 in bios. xhci. Make sure it's staying disabled, and if there's any option to have it run as USB2 instead, enable that. Your USB3 might work, but there are other devices on that bus that will not work as USB3 (like bluetooth-or mouse even tho it shows up) and the hubs can cause problems (not the kind you plug in but the one seen in system profiler). You might be able to get both working at some point with DSDT or kext edits, but for now just working USB comes first. Legacy USB option in bios relates to how it reads thumbdrives and stuff to boot from and can be left at default. Just disable the USB3 stuff.

[jamesst20]

As I said, disable USB3 in bios. xhci. Make sure it's staying disabled, and if there's any option to have it run as USB2 instead, enable that. Your USB3 might work, but there are other devices on that bus that will not work as USB3 (like bluetooth-or mouse even tho it shows up) and the hubs can cause problems (not the kind you plug in but the one seen in system profiler). You might be able to get both working at some point with DSDT or kext edits, but for now just working USB comes first. Legacy USB option in bios relates to how it reads thumbdrives and stuff to boot from and can be left at default. Just disable the USB3 stuff.

I only have xHCI, EHCI, USB Debug, USB Emulation, USB Legacy, xHCI Preboot Driver, USB Post-Control(something like it), USB Wake support, USB Powershare, options in Bios.

I don't have a 'USB 3.0' option

How would I fix that using a DSDT? How come it rarely works when xHCI is disabled?

[iFIRE]

xHCI is your 3.0

[jamesst20]

Tried already please read a bit before

Rarely works when xHCI is off, sometimes the controller is recognized as EHCI(2.0) otherwise it is not reconized at all.

[slayer2333]

I have an Asus g75vw with only USB 3.0 ports but i can either :
Get them work as USB 2.0 by enabling Legacy USB + disabling XHCI in Bios.
Get them work as USB 3.0 by enabling XHCI and disabling Legacy USB
if i enable both of them i get a freeze as soon as i plug something in, so try to play a bit with these options in your Bios.

On another side, om a bit surprised that you could get your 660m GTX to work nativelly with your system where the rest of people around need to delete the Nvidia kext to at least boot into ML. Did you change anything particular to your DSDT/NVIDIA kext/Bios options or was it working after the initial OSX install without adding anything ?
Can you Share your IOREG ?

[jamesst20]

I have an Asus g75vw with only USB 3.0 ports but i can either :
Get them work as USB 2.0 by enabling Legacy USB + disabling XHCI in Bios.
Get them work as USB 3.0 by enabling XHCI and disabling Legacy USB
if i enable both of them i get a freeze as soon as i plug something in, so try to play a bit with these options in your Bios.

On another side, om a bit surprised that you could get your 660m GTX to work nativelly with your system where the rest of people around need to delete the Nvidia kext to at least boot into ML. Did you change anything particular to your DSDT/NVIDIA kext/Bios options or was it working after the initial OSX install without adding anything ?
Can you Share your IOREG ?

Working natively and I would share my IOREG if I knew what it is

And my Legacy USB is always on wheter I enable or not xHCI and even if I disable it, it does absolutely nothing :/

[TeoTheCool]

Could you also share your iAtkos selected options please? I have tried with a G55vw which has pretty much the same specs as your M17x, but mine still gets stuck after "GK100Hal Loaded and registered"

[jamesst20]

Hmm I've only selected stuff like PS/2 drivers and the Baterry Sensor, nothing according to drivers as the sound driver doesn't works either in iATKOS, I need VoodooHDA.

[TeoTheCool]

Thanks, I've tried selecting only those and its still not working... I really can't figure out what could be so different... One last request, would you mind sharing your DSDT (patched/original)?

[jamesst20]

Thanks, I've tried selecting only those and its still not working... I really can't figure out what could be so different... One last request, would you mind sharing your DSDT (patched/original)?

Thanks, I've tried selecting only those and its still not working... I really can't figure out what could be so different... One last request, would you mind sharing your DSDT (patched/original)?

I have no DSDT

[kelobb]

Jamesst20, could you attach a "print screen" from system report (the same quality like usb etc) - sections: "graphics/monitors" and "extensions" (bit trouble - maybe 3 parts of screen, extensions has long list).
Me and Slayer2333 probably want to investigate a different alienware layout of PCI id for graphics components.
Thanks for any info.
Regards

[IDDPioneer]

Thinking, as for us our USB works and VGA no and for him its VGA works and USB no, it could be a conflict between them in PCs maybe the mac have another way to work in this question, I am just thinking loud here, I will try to mix in my USB options here in my laptop.

My Lap:
i7 - 3740QM
Geforce GT650M - 2GB
Chipset HM 76

[q64ceo]

Here is your solution for USB 2: http://www.insanelym...t/#entry1893097

I should have googled your machine before having you run in circles. I was under the impression it was a desktop, not a laptop, and that is why I didnt consider this being a possibility.

[kelobb]

Hello,
Today I went to my local Ispot store to investigate newest iMac with gtx660m
the osx 10.8.2 build is 12C3103 and the deviceid is not fd4 but fd0.
The kext of nvidia is from october 2012 (i don't remember revision now)
But on Alienware it works with fd4 so this is very strange. I wonder where is the hack...

[IDDPioneer]

Hello,
Today I went to my local Ispot store to investigate newest iMac with gtx660m
the osx 10.8.2 build is 12C3103 and the deviceid is not fd4 but fd0.
The kext of nvidia is from october 2012 (i don't remember revision now)
But on Alienware it works with fd4 so this is very strange. I wonder where is the hack...

The supposed "hack" is here :

<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
If the kexts has only these lines above, it will load ever the class matches the values in the string.

<key>IOPCIMatch</key>
<string>0x000010de&amp;0x0000ffff</string>
And here the kexts will load if the PCI device matches what is in the string: it means 0000 any value in the device field and 10de is for the vendor part of the field.


<key>IOPCIPrimaryMatch</key>
<string>0xfd110de&amp;0xffc0ffff</string>
If the IOPCIPrimaryMatch is not in the plist the kexts will load for all the devices from the vendor in the IOPCIMatch, or else if the value is there the kext will load only for 0df0 or 0df1, or whatever is in the string.

Ok kelobb ? I think your doubt is explained, and if your system freezes with NVDAResman, or the kext not load is for any other reasons than tese ones explained above.

[kelobb]

This is natural first way I tried to modify this kext - but from my tests I have Geforce GK100Hal.kext loaded (message in -v verbose output) and nothing switched my text mode to graphic mode.
Did you test this "hack" on kexts or talking about thoretical method.
What do You think?
Thanks