Jump to content

OSX 10.7, 10.8 and 10.9 on the Dell XPS 1340 laptop

* * * * * 3 votes

  • Please log in to reply
293 replies to this topic

#241
wormx

wormx

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts
Ah, so it turns out I am no longer getting the header read size 200/Incorrect image signature errors/warnings. However, the computer is still unresponsive after going to "sleep." The fan is still spinning, and the power light is still on solid, but the caps lock key doesn't change. Any other ideas on where I should look?
Thanks again!

#242
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

Any other ideas on where I should look?
Thanks again!

So you could either figure out how your setup now differs from what is recommended in post #1, or just start troubleshooting which driver might be failing to suspend correctly. Most likely it's the display driver or usb failing to suspend correctly. If you don't want to figure out what's different in your setup vs the recommendations, I'd start by temporarily taking out the nvidia drivers and not using usb, and see how that changes things.

#243
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male
Anyone with a 9400m 1340 upgrade from 10.8.2 to 10.8.3 successfully?
I finally had a chance to try it, and I cannot get the system to come up multi-user. Without intervention, the system console shows everything starting, gets to the point where the graphics driver is starting, and the screen goes to black and the system locks up (no ping response). Same thing if I boot with safe mode.

I can remove some of the nvidia graphics drivers and get the system to lock up right before the screen goes black instead, or I can get the system to panic with IOPPlatformPluginLegacy in the traceback if I remove all the nvidia graphics drivers.

#244
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,944 posts
  • Gender:Male
I don't know if it's related, but i had 10.8.3 (now i'm on 10.8.4) installed in my ION system (The Asus netbook of my sig). Since i think ION and 9400m are basically the same silicon, i don't get why the XPS would have graphics issues with the updates.

All the best!

#245
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

I don't know if it's related, but i had 10.8.3 (now i'm on 10.8.4) installed in my ION system (The Asus netbook of my sig). Since i think ION and 9400m are basically the same silicon, i don't get why the XPS would have graphics issues with the updates.

All the best!

Google shows a bunch of users (even genuine mac users) having trouble with their nvidia graphics going from 10.8.2->10.8.3, but I don't see much in common. You're probably using slightly different injection strings than me; and maybe the cuda drivers are now somehow required to keep the nvidia driver working on these old systems?

#246
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,944 posts
  • Gender:Male
I don't think ION/9400m has any CUDA cores, so CUDA drivers should neither work nor make a difference. I do inject it via DSDT - yet i need GraphicsEnabler=Yes anyway: without both GE=Y and the DSDT, the system won't start.

You can try to examine the DSDTs available on the 1201n topic to find if any suits your hardware: good luck!

All the best!

#247
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

I don't think ION/9400m has any CUDA cores, so CUDA drivers should neither work nor make a difference. I do inject it via DSDT - yet i need GraphicsEnabler=Yes anyway: without both GE=Y and the DSDT, the system won't start.

You can try to examine the DSDTs available on the 1201n topic to find if any suits your hardware: good luck!

All the best!

Cuda drivers install on the 9400m and nvidia's web page show the 9400m as a supported platform.
Some users have claimed installing the cuda drivers to be a necessary step to get working video, but I've never experienced it.
I just tried the 10.8.3 upgrade again and cuda made no difference for my 10.8.3 failure case.

I don't need help on what the injection strings are, I've been supporting 9400m&9500m users here for years with regards to that. Just wondering if anyone knew what changed with 10.8.3 that would cause this failure.

#248
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,944 posts
  • Gender:Male

I don't need help on what the injection strings are, I've been supporting 9400m&9500m users here for years with regards to that. Just wondering if anyone knew what changed with 10.8.3 that would cause this failure.


Sorry, bbc9, but how could i know? To me, you were just someone asking help, and i tried my best. :D But i just realized you're the one that wrote the HDA script, so obviously any DSDT injection would be a piece of cake for you. My bad. (OFF: by the way, do you know directions for an AppleHDA patching guide from where i can learn to patch it manually, completely from scratch, for my VT 1705, since it's not supported by any current patch?)

And you are right about CUDA and the 9400m, despite the nVidia site stating 16 "stream cores" (not CUDA cores) for the 9400m: just downloaded the latest CUDA drivers, which i found were missing in my system, and CUDA-Z now displays the CUDA cores correctly (picture below). But then again, i've been running OSX on my 1201n all the way from 10.7.0 to 10.8.4 beta without a single graphics issue, so the issue must lie somewhere else. I'd say, risking to be a little futile, to test the injections of the 1201n topic.

All the best!

Attached File  Screen Shot 2013-04-30 at 5.02.53 PM.png   90.83KB   6 downloads

#249
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

I can remove some of the nvidia graphics drivers and get the system to lock up right before the screen goes black instead, or I can get the system to panic with IOPPlatformPluginLegacy in the traceback if I remove all the nvidia graphics drivers.

So this panic message was the clue. Prior to 10.8.3, I could boot with nv_disable=1 and that would disable the nvidia graphics and the system would come up with vga graphics. With 10.8.3, I'd get the panic with IOPPlatformPluginLegacy and ACPI_SMC_PlatformPlugin in the traceback.

So, I moved ACPI_SMC_PlatformPlugin out of /S/L/E and viola no more panic, and also I can boot with the 10.8.3 nvidia drivers. No more hang.

#250
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

Sorry, bbc9, but how could i know? To me, you were just someone asking help, and i tried my best. :D But i just realized you're the one that wrote the HDA script, so obviously any DSDT injection would be a piece of cake for you. My bad. (OFF: by the way, do you know directions for an AppleHDA patching guide from where i can learn to patch it manually, completely from scratch, for my VT 1705, since it's not supported by any current patch?)

No worries. The HDA script was somewhat simple actually compared to some of the other reverse engineering I've had to do (like ATI graphics, intel hd graphics, nvidia HDMI audio, etc.).
In any case, AppleHDA worked for the VT2021 I tried, so I suspect VT1705 would work too. The projectosx thread I referenced in my applehda thread, http://www.projectos...owtopic=465��is the most complete/current instructions I know of. There are other older somewhat obsolete pieces such as the pincap under linux thread: http://www.insanelym...ded&pid=1055645
These days you may be able to crib your pin configuration from voodoohda instead of using linux.

#251
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

So, I moved ACPI_SMC_PlatformPlugin out of /S/L/E and viola no more panic, and also I can boot with the 10.8.3 nvidia drivers. No more hang.

Digging further, it was 9400m_gstate_inject that was triggering the problems. Looks like mapping this system's AGPM g-state to control-id 16 no longer works. Everything is fine without 9400m_gstate_inject (and I no longer need to break ACPI_SMC_PlatformPlugin).

#252
cmputr

cmputr

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
  • Gender:Male
Hi, first would like to thank bcc9 for this great guide and all your hard work. I followed the guide "exactly" for my Mountain Lion install but no matter what I do I'm getting this [ PCI Configuration Begin ] hang when using DSDT.aml (I CAN boot without it) I also don't have this PCI hang on 10.6.3. I CAN'T use the dsdt-check.pl because when I run it I only get "Address space not recognized. Please post the output from showbootermemorymap" so I tried both DSDT.aml / DSDT-alt.aml to no avail. I have also tried metamorphoise's metamorphoiseDSDT.zip .. I have been trying to get past this for more then a WEEK :wallbash: So if someone can help me out it would be greatly appreciated. I'll be waiting for someones response. THANKS

Edit: I've tried npci=0x2000

Attached Files

  • Attached File  log.zip   3MB   1 downloads


#253
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male
My dsdt-check.pl and showbootermemorymap were designed to troubleshoot the ACPI memory space issues that some users started seeing as of osx 10.7. The script doesn't work with older OSX (10.6), but that should be OK - it's meant to be run on the version of osx that you're trying to work with not an old release.

If that doesn't describe your issue, then you'd do well to post the showbootmermemorymap output as the script asked you to.

Now, normally I update post #1 to include the latest&greatest fixes, but the DSDT changes I made to support current OSX for users with discrete GPUs (9500m/g210m) continues to lack proper feedback. I cannot clean things up without some complete feedback. For reference, the two candidate fixes are:

v4: http://www.insanelym...-9#entry1861302
v5: http://www.insanelym...10#entry1861410

If someone would benchmark which of these two actually lowers the power consumption for discrete GPU users (with kill-a-watt or some time-based measurements as asked for), then I'd know what to do next to clean things up.

If v4 really improves power consumption as much as v5 then v4 is probably the best fix, else some more refinement could be tried on v5 to fix its system_profiler side-effect.

Lacking feedback, post #1 remains busted and you need to use my v4 or v5 fix referenced above else discrete-gpu users see the system hanging during boot after "PCI Configuration Begin" is displayed.

PS: This same lack of feedback issue has been going on for a long time now:
http://www.insanelym...10#entry1861540

http://www.insanelym...11#entry1872146

if nobody is going to follow up with responses and instead just disappear once they've taken enough information to get their system working, then I propose this thread gets closed.

#254
cmputr

cmputr

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
  • Gender:Male

My dsdt-check.pl and showbootermemorymap were designed to troubleshoot the ACPI memory space issues that some users started seeing as of osx 10.7. The script doesn't work with older OSX (10.6), but that should be OK - it's meant to be run on the version of osx that you're trying to work with not an old release.

I'm running the script from 10.8

 

If that doesn't describe your issue, then you'd do well to post the showbootmermemorymap output as the script asked you to.
 

$ sudo ./showbootermemorymap 
Type       Physical Start   Number of Pages
available  0000000000000000 000000000000009d
reserved   000000000009dc00 0000000000000002
reserved   00000000000d2000 0000000000000002
reserved   00000000000e4000 000000000000001c
available  0000000000100000 000000000006fdc0
ACPI_recl  000000006fec0000 000000000000000f
ACPI_NVS   000000006fecf000 0000000000000016
reserved   000000006fee5000 000000000000001b
reserved   000000006ff00000 0000000000010000
reserved   000000007ff00000 0000000000000100
reserved   00000000e0000000 0000000000010000
reserved   00000000fec00000 0000000000000010
reserved   00000000fee00000 0000000000000001
reserved   00000000fff80000 0000000000000080

For reference, the two candidate fixes are:

v4: http://www.insanelym...-9#entry1861302
v5: http://www.insanelym...10#entry1861410
 

Still the same [ PCI Configuration begin ] hang   :(

 

Stupid Question: Could it be because I have only one 2gb stick of ram? The second stick gave out. ( also changed wireless card )

 

If someone would benchmark which of these two actually lowers the power consumption for discrete GPU users (with kill-a-watt or some time-based measurements as asked for), then I'd know what to do next to clean things up.

I would have no problem doing this for you but DSDT's still Hanging the system  

 

 

if nobody is going to follow up with responses and instead just disappear once they've taken enough information to get their system working, then I propose this thread gets closed.

Please dont close the thread i'll give you as much feedback as I possibly can.

 

I am hoping you can help me get this working. Any more suggestions will be appreciated.



#255
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

Still the same [ PCI Configuration begin ] hang   :(
 
Stupid Question: Could it be because I have only one 2gb stick of ram? The second stick gave out. ( also changed wireless card )

Ok, now we're getting somewhere. So your system does infact have a different memory region layout than everyone else, so you need a different DSDT with addresses that match yours.
Yes, it's expected that you are still hanging with the custom dsdts since they aren't matching your layout.
And yes, I'd assume your layout is different because you're running with 1/2 the normal memory.
Here's 2 DSDTs that match your layout, otherwise identical to the v4 and v5 candidates posted above.

I'd be very interested to know whether v4&v5 have the same power draw or whether v5 is better or what.

Attached Files



#256
cmputr

cmputr

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
  • Gender:Male

Good news, I think we are making progress. 

 

Both DSDT's from alt2-dsdt.zip got me past [ PCI Configuration Begin ] but graphics are still at 1024 x 768. (9400M G + G210M)

 

EDIT: no battery status. LID close detection works but when I open the laptop I see a black screen and I lose mouse function.



#257
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

Good news, I think we are making progress. 
 
Both DSDT's from alt2-dsdt.zip got me past [ PCI Configuration Begin ] but graphics are still at 1024 x 768. (9400M G + G210M)

With the dsdt, your graphics strings should be getting injected into your ioregistry automatically. Check and or post your ioregistry to verify. GraphicsEnabler should no longer be used as it erroneously adds injection strings to both graphics pci IDs intead of just the 9400m part. Newer nvidia drivers only work with the injection strings on the 9400m part.

#258
cmputr

cmputr

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
  • Gender:Male

With the dsdt, your graphics strings should be getting injected into your ioregistry automatically. Check and or post your ioregistry to verify. GraphicsEnabler should no longer be used as it erroneously adds injection strings to both graphics pci IDs intead of just the 9400m part. Newer nvidia drivers only work with the injection strings on the 9400m part.

 

not using GraphicsEnabler.

would you mind pointing me in the right direction to find the string in ioregistry? thanks

 

Edit: Very sorry, I'm new to hackintosh. I'm a long time Windows user. Anyway, Im looking in ioregistry and I see ..

IGPU@0

model   data  <"NVidia Geforce 9400M G">

 

I also just looked in About This Mac>Graphics/Displays and it says: "There was an error while gathering this information."

Attached Files



#259
bcc9

bcc9

    InsanelyMac Legend

  • Coders
  • 1,278 posts
  • Gender:Male

not using GraphicsEnabler.
would you mind pointing me in the right direction to find the string in ioregistry? thanks
 
Edit: Very sorry, I'm new to hackintosh. I'm a long time Windows user. Anyway, Im looking in ioregistry and I see ..
IGPU@0
model   data  <"NVidia Geforce 9400M G">
 
I also just looked in About This Mac>Graphics/Displays and it says: "There was an error while gathering this information."

Failing to get working battery status or native resolution (which in turn is due to failure to get the nvidia accelerated framebuffer kext to run) are symptoms of a misconfig. I think if you'll look back at previous posts in this thread you'll see this is almost always the case. The exception is when a new release comes out and something breaks. You should look back to see if the previous solutions apply to you.

Usually people say they are following post #1 but they are instead just cherry picking what parts of post #1 they think are important, and they wind up with a misconfig. The easiest way to get a misconfig is to use tonymac's installers which will configure a bunch of things without your knowledge.

If your ioregistry output really shows "NVidia Geforce 9400M G" (sic) not
"NVidia GeForce 9400M G" then you installed something else such as an old nvidia kext injector that is messing things up. Some of the older injectors mis-capitalized GeForce (compared to a genuine mac). Not that the capitalization matters to the driver, but it's a telltale sign.

If you don't know what to look for, posting all of the ioreg -lw0 output is the usual starting point.

For your particular case, you want the IGPU@0 sub-tree to be populated with the expected nvidia injection strings, ie all of those found in my dsdt edit especially NVCAP, and you want the XVR0 subtree to have no nvidia injection strings attached.
Additionally you want to see that both of these subtrees are flagged as matched&active, and that the nvidia driver added the other usual strings such as NVDA,gart-width.

As for the system_profiler output, I did just tell you that v5 of my dsdt breaks this as a side effect. This probably can be fixed, but I don't even know whether the v5 changes are necessary vs v4. I do not have a 1340 with discrete graphics so again I've been waiting for feedback before doing anything.

#260
cmputr

cmputr

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
  • Gender:Male

bcc9 your alt2-dsdt.zip files worked. Everything is working now.  :thumbsup_anim:

 

I'm not exactly sure where I went wrong but after reading your post I went back and looked over everything in ioreg. Everything you said that should be in there was in there. So I decided to just start from scratch.

 

So I redid my usb installer and reinstalled everything over again. After following your guide the second time and using the DSDT-alt2 everything is working. 

 

If your ioregistry output really shows "NVidia Geforce 9400M G" (sic) not
"NVidia GeForce 9400M G" then you installed something else such as an old nvidia kext injector that is messing things up. Some of the older injectors mis-capitalized GeForce (compared to a genuine mac). Not that the capitalization matters to the driver, but it's a telltale sign.

 

Sorry, "NVidia Geforce 9400M G" was a typo on my part. It does infact say "NVidia GeForce 9400M G"

 

If someone would benchmark which of these two actually lowers the power consumption for discrete GPU users (with kill-a-watt or some time-based measurements as asked for), then I'd know what to do next to clean things up.

 

Here you go. Hope this is what you need.  :)

 

DSDTv4 ( Laptop sitting with screen on - not running anything )
START: 3:45pm @100% battery
STOP: 5:30pm @7% battery
Total :: 105 mins.
 
DSDTv5 ( Laptop sitting with screen on - not running anything )
START: 7:53pm @100% battery
STOP: 10:06pm @7% battery
Total :: 133 mins.
 
I know you've done tutorials for OS X on this laptop for a while now ( Without you we wouldn't be running this great OS on our laptops ) so I hope you don't mind me asking but will you be doing a tutorial on OS X Mavericks? If not then that's cool :)  I just thought I'd ask.
 
Thank You for this tutorial and for helping me out!  :D






2 user(s) are reading this topic

1 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