Jump to content

Dell XPS 1340 under OSX 10.6, including boot-132 install cd


bcc9
 Share

1,149 posts in this topic

Recommended Posts

The Extra zip of etiger13 is it functionally... I have added the new HDAIDT and repacked the zip...

 

For all newbie:

 

1. Install Snow Leopard with boot-123 of bcc9

2. Install Chameleon 2.0RC3 or newer

3. Copy the Extra folder (in the attachment) in the root of your disk

4. Execute the Kext Utility (in the attachment)

5. Reboot!

 

Now it is all functionally!

Extra.zip

Kext_Utility.zip

Link to comment
Share on other sites

The Extra zip of etiger13 is it functionally... I have added the new HDAIDT and repacked the zip...

 

For all newbie:

 

1. Install Snow Leopard with boot-123 of bcc9

2. Install Chameleon 2.0RC3 or newer

3. Copy the Extra folder (in the attachment) in the root of your disk

4. Execute the Kext Utility (in the attachment)

5. Reboot!

 

Now it is all functionally!

Guys, could you please start a newbie thread to discuss&support repack efforts.

Also any re-pack should give proper credit to the authors. And I don't know if you care, but kexts such as fakesmc require copying of the license info as well. Same with my current dellbluetoothhci. Speaking of which dellbluetoothhci needs to go to /S/L/E, otherwise you can't start it using the hotkey. Yet it looks like this repack installs my bluetooth driver into /E/E instead. If you use the current version of dellbluetoothhci with the package, the install directory is defaulted properly.

 

With some of the issues fixed, it looks like the repack would be quite handy for newbies.

Link to comment
Share on other sites

The first time my lid closes the computer goes to sleep, the second time it doesn't. Also, after sleeping once it won't shutdown properly.

 

I'm using pstate.kext and openhaltrestart. Is this a common problem ... or should I toggle with some things?

I don't have such problems. Recommend you narrow things down by trying apple->sleep instead of relying upon lid status.

 

As for voodoopstate, I've done a bit more intel speedstep testing and it seems to me that neither voodoopstate nor voodoopower is necessary on this machine. Stepping is taking place with the default appleintelcpupowermanagement. I thought it was not because cpu-x was not reporting a change but this seems to just be a limitation with cpu-x.

Link to comment
Share on other sites

Has anyone with Atheros wifi updated to 10.6.2 ? Are there any issues ? the netkas website mentioned that some extra kext is needed to load the new driver properly.
Yes, it works fine out of the box in 64 bit mode now as of 10.6.2, just like it did in 32 bit mode since 10.6. netkas's info is wrong for this system, no device id tweaking is required.
Link to comment
Share on other sites

As for voodoopstate, I've done a bit more intel speedstep testing and it seems to me that neither voodoopstate nor voodoopower is necessary on this machine. Stepping is taking place with the default appleintelcpupowermanagement. I thought it was not because cpu-x was not reporting a change but this seems to just be a limitation with cpu-x.

 

The problem only started happening with pstate, so if I can get rid of that one, perfect!

 

Great!! Did you need to tweak your SMBIOS.plist to particular values for the stock appleintelcpupowermanagement to kick in? How can you tell that stepping is taking place if you're not using cpu-x, what tool are you using?

Link to comment
Share on other sites

The problem only started happening with pstate, so if I can get rid of that one, perfect!
I don't have the problem you describe with pstate running. I still suspect you'll need to do some troubleshooting
Great!! Did you need to tweak your SMBIOS.plist to particular values for the stock appleintelcpupowermanagement to kick in?
No, I just used the smbios.plist as in post #1. Actually I've added SMmemmanufacter (sic) and SMmempart to fix memory detail reporting, similar to itwong's change. Will update post #1 in a sec.
How can you tell that stepping is taking place if you're not using cpu-x, what tool are you using?
I used voodoomonitor. It reports some buggy info as well so I'm not clear if it's using optimal voltages like what I wrote for voodoopstate, but measured CPU performance and temps suggest that stepping is happening at least as often as voodoomonitor shows it happening.
Link to comment
Share on other sites

I am confused a bit...I am wondering if I should install the voodooPstate.kext ? I dont have it installed now (using 10.6.1) and the GenericCPUpmcontrol app shows that throttling is working..so what should I do ?

You probably shouldn't install voodoopstate. I'll take it out of the recommended list in post #1.

The situation is confusing because I'm not aware of any supported apps correctly reporting the vid/fid/voltage. All of them seem to misreport or malfunction in one way or another. I think I now understand what each one is doing wrong however. Wouldn't be hard to fix if current source was published...

 

I assume your CPU temps corroborate that throttling is taking place as expected.

Link to comment
Share on other sites

You probably shouldn't install voodoopstate. I'll take it out of the recommended list in post #1.

The situation is confusing because I'm not aware of any supported apps correctly reporting the vid/fid/voltage. All of them seem to misreport or malfunction in one way or another. I think I now understand what each one is doing wrong however. Wouldn't be hard to fix if current source was published...

 

I assume your CPU temps corroborate that throttling is taking place as expected.

 

Yes bcc9 , the temperatures in OS X and linux are pretty much the same so I guess that throttling is working fine. Btw, what app do you recommend for checking the temperatures? I am using GenericCPUpmControl.app for now . .

Link to comment
Share on other sites

Yes bcc9 , the temperatures in OS X and linux are pretty much the same so I guess that throttling is working fine. Btw, what app do you recommend for checking the temperatures? I am using GenericCPUpmControl.app for now . .
I don't know what's best; I'm currently using voodoomonitor which shows the temps&cpu frequencies correctly, but calculates the voltages incorrectly. There should be a simple applet that would just show you temps.
Link to comment
Share on other sites

I updated to 10.6.2 and mostly its fine, but now when I use the GenericCPUPMControl.app , it says the kernel extension is offline. What could be the reason for this!?
From the code, that means you have neither GenericCPUPowerManagement nor VoodooPower kexts running. I think superhai deprecated GenericCPUPM* a while back so you just move on.
Link to comment
Share on other sites

Oh yes!

I checked the logs and the voodoopower.kext was not loading in 64 bit mode. I was trying out the 64 bit mode just to for fun.. I will revert back to 32 bit mode for regular use.

As I mentioned a few posts back, I don't think you need to run voodoopower or voodoopstate on this laptop; you get cpu throttling with appleintelcpupowermanagement.

Link to comment
Share on other sites

Bcc9, here is a version of your legacy kext with second jack working (auto switch with Speakers) as Line Out, nodes for Ext Mic are also added (so device is present in Audio pref pane) but it doesn't work...

Still no volume controle for Int Mic

That's great that you fixed the line out to mute the speakers. But your changes also leave me with two devices shown as "internal microphone" which I think is pretty confusing, and since the 2nd one doesn't work, not a good idea to add it. Also I get a bunch of new assertions:

	 Sound assertion "0 == fMikeyDriver" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDADriver.cpp" at line 1250 goto handler
 Sound assertion "result" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAWidget.cpp" at line 3527 goto Exit
 Sound assertion "0 != widget->setConnectionSelectNodeID ( fSelectionsForEachWidget[inputWidgetIndex] )" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAPath.cpp" at line 656 goto Exit
 Sound assertion "0 != readVolumeSettingFromCache ( pathSet, hdaSpatialChannnelID, &cachedVolumeMuteSetting )" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAEngine.cpp" at line 2308 goto Exit
 Sound assertion "0 != createVolumeControlForActivePathSet ( hdaSpatialChannnelID, direction )" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAEngine.cpp" at line 2478 goto Exit
 Sound assertion "0 != createVolumeAndMuteControlsForActivePathSet ( kPathDirectionInput )" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAEngine.cpp" at line 11258 goto Exit

Maybe you can make a new version with just the speaker mute change?

 

When I was looking at the codecgraph for this codec it doesn't look like both mic's paths can be configured at the same time. I noticed that the linux code has "quirks" with verbs to change the nodes around, I think in order to address this. (Or maybe the quirks are for no good reason, it's hard to tell with no explanations). I tried a bit but did not figure out a working equivalent with applehda.

Link to comment
Share on other sites

Maybe you can make a new version with just the speaker mute change?

When I was looking at the codecgraph for this codec it doesn't look like both mic's paths can be configured at the same time. I noticed that the linux code has "quirks" with verbs to change the nodes around, I think in order to address this. (Or maybe the quirks are for no good reason, it's hard to tell with no explanations). I tried a bit but did not figure out a working equivalent with applehda.

No problem, I'll do a new version without the second mic this evening. I didn't figure out how to use both jack outputs in the same time because as they both mute internal speakers, they also mute themselves each other.

About the "quirks" in linux codec, I agree with you, configuration of input nodes connections is very strange.

Link to comment
Share on other sites

No problem, I'll do a new version without the second mic this evening. I didn't figure out how to use both jack outputs in the same time because as they both mute internal speakers, they also mute themselves each other.
Oh, didn't realize. That's bad too. No point in having 2 jacks if only 1 works at a time. Under windows I've used both jacks at the same time - handy for sharing a movie on a plane (though it'd be even better if one could control the volume per jack).

 

Why the battery's autonomy under snow leopard is about 2 hours and under windows 7 is 4 hours?
Last time I watched a dvd under windows 7, the battery went from 100% to 5% in under 2 hours. That's with the screen dimmed, radios turned off.

So if you just have a 6 cell battery, I'd say the time windows 7 is claiming is just wishful thinking.

Link to comment
Share on other sites

Hi guys long time no speak, could anyone just guide me through the update to 10.6.2, what should i have ready or any important steps to follow. I cant afford to play around as usual given am on my mid-terms at uni and if my XPS goes nuts ill castrate myself!

 

By the way is there any downside to updating to 10.6.2 ??????

 

Thanks and i will really value your support

 

All the best

Link to comment
Share on other sites

 Share

×
×
  • Create New...