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

[ice-t]

Thanks for the update. Using MBR makes the whole process a lot easier I gues. I am going the format my whole drive to install a dual boot windows 7 and Snow. What is the best approach and order to do this? What partitions do you suggest?

[bcc9]

Thanks for the update. Using MBR makes the whole process a lot easier I gues. I am going the format my whole drive to install a dual boot windows 7 and Snow. What is the best approach and order to do this? What partitions do you suggest?

If you're going to wipe your whole disk and only install those two OSes then you could just go with a guid partition table, and that'd be easier in that you don't have to change OSInstall in your snow leopard distribution.

 

Generally speaking I'd say install windows first then OSX, as windows will otherwise clobber the MBR with the windows bootloader. If you're installing over the original dell distro, I'd recommend getting rid of the old windows vista recovery partition now that vista is obsolete.

I'd probably let windows make its EFI partition, then there'd be one partition each for the OSes and I'd make at least 1 more to share across OSes (and make that one NTFS).

 

There are entire separate threads in this forum on multibooting...

[ice-t]

Thanks for the feedback again. Does the the swapping method work with this cdboot disk? If I load the iso everything goed well. But when I swap the disk and press F5 i get a number of "HFS signature not found" errors and a "can't find mach_kernel" error.

[bcc9]

Thanks for the feedback again. Does the the swapping method work with this cdboot disk?

Yes, as reported a few posts back (posts #245,#246)

[itwong]

First of all, thanks for a great tutorial for us xps 1340 owners. I've managed to get snow leopard installed. But I do have one problem which is the memory information is not displayed under about this mac and system profiler. For your reference, I've attached two screenshots of my setup.

 

I've updated to Chameleon RC3 + pcefi 10.5. I also put the SMbios.plist posted by bcc9 in /Extra except I take out the SMproductName entry in the file. Now my rig is recognized as MacBookPro4,1. But the memory information can't be displayed. Any suggestion or solution will be greatly appreciated.

[etiger13]

First of all, thanks for a great tutorial for us xps 1340 owners. I've managed to get snow leopard installed. But I do have one problem which is the memory information is not displayed under about this mac and system profiler. For your reference, I've attached two screenshots of my setup.

 

I've updated to Chameleon RC3 + pcefi 10.5. I also put the SMbios.plist posted by bcc9 in /Extra except I take out the SMproductName entry in the file. Now my rig is recognized as MacBookPro4,1. But the memory information can't be displayed. Any suggestion or solution will be greatly appreciated.

 

Why did you take out the smproductname?

[Gambit642]

I've made a driver to automatically turn on HCI mode for dell bluetooth devices. This can be used instead of hid2hci. I think it's a better solution, as detailed over here:

http://www.insanelymac.com/forum/index.php...t&p=1239975

 

Hey, some of us are still having trouble, can you please provide a PPF-O-Matic patch file for the Vanilla SL image which contains your changes? That should be small enough to upload, and would make it a snap to "fix" the SL image for our 1340's which will will work with your 1340 123-boot image mod.

[bcc9]

Hey, some of us are still having trouble, can you please provide a PPF-O-Matic patch file for the Vanilla SL image which contains your changes? That should be small enough to upload, and would make it a snap to "fix" the SL image for our 1340's which will will work with your 1340 123-boot image mod.

Lord no. ppf-o-matic is a warez patcher that would make the changes dependent upon exactly 1 version of 10.6, whereas my instructions are generic. If I make a patch for a 10.6 iso it would not work for a 10.6 .dmg for example. As a further example, you'd have yet a different version if you uncompressed the .dmg to patch for MBR installation. Then there would be like 25 versions of the PPF by now as the best known practices change over time. Too much work for me.

Besides, I don't know what problem you're having so I can't being to make a patch for it, and I don't have a one size fits all solution.

 

First of all, thanks for a great tutorial for us xps 1340 owners. I've managed to get snow leopard installed. But I do have one problem which is the memory information is not displayed under about this mac and system profiler. For your reference, I've attached two screenshots of my setup.

Works for me. Are you sure your smbios.plist is being parsed? If your filesystem is case sensitive then smbios.plist is as well, yet you typed the filename in mixed case.

[itwong]

Works for me. Are you sure your smbios.plist is being parsed? If your filesystem is case sensitive then smbios.plist is as well, yet you typed the filename in mixed case.

 

My system is not case sensitive. It's HFS+ (Journal). What do you mean by smbios.plist being parsed? I tried your original smbios.plist but still no memory information. I placed smbios.plist in /Extra/smbios.plist. Is that the correct place? What kexts do you have in your /Extra folder? I used the com.apple.Boot.plist you posted. Is there specific syntax requirement for smbios.plist to work? Anything in com.apple.Boot.plist? Thanks for your help :-)

Please be more specific about the Upper/Lower casing and the place to put the smbios.plist.

[bcc9]

What do you mean by smbios.plist being parsed?

Parsed: read and understood by the computer software. From your description it seems likely that your smbios.plist is not being parsed. You could troubleshoot this by making sure that you can successfully change other smbios.plist attributes such as the product name.

[itwong]

Parsed: read and understood by the computer software. From your description it seems likely that your smbios.plist is not being parsed. You could troubleshoot this by making sure that you can successfully change other smbios.plist attributes such as the product name.

 

The smbios.plist is parsed correctly. Whatever changes I've made to smbios.plist are reflected in the system profiler. For your reference, I made the following changes to your original smbios.plist. SMProductname -> HP HDX16T

SMmemtype-> 19, SMmemspeed->800. However, the changes are only effective in about this mac screen. When I click more info button to get to system Profiler, the memory information are not available under the memory section. It says " There was an error while gathering this information"

[bcc9]

I've written an installer for my patch-acpi script. This should eliminate any further confusion about how to install the ACPI patch (such as failure to run as root, etc). See AppleACPIPlatform.1340.pkg in post #1.

[etiger13]

I could really use some help on the non-working components! Such as:

• For 9500m, maybe someone could figure out how to get SLI video working. The OSX drivers may not be able to handle SLI at all but it's not clear whether or not that's really true.
  
• For audio, it'd be great if someone could figure out the fix to the pathmap/pinconfig to allow the analog&digital mics to fully work.
  
• Something seems wrong with the IOAHCISerialATAPI driver. Upon wakeup from suspend the disk activity light flashes every 2 seconds or so apparently with the driver trying to stat the dvd-rom drive. Putting a disk in the drive fixes this.
  
• The firewire controller loses its GUID upon wakeup from suspend, logging "FireWire GUID 0000000000000000 is invalid!" over&over to /var/log/kernel.log after wakeup. The workaround in 10.5.x of unloading/reloading the AppleFWOHCI.kext to fix this no longer works as that kext can't be unloaded.

I'd love to help. How do I do any of that?

[bcc9]

I'd love to help. How do I do any of that?

Search around and see if others have made any progress on these issues for other systems, debug the dsdt and test candidate changes, disassemble and read the driver code to figure out the conditions that are leading it/them astray. These are some of the techniques I've used with success for other issues on this laptop but no results to show for it on those 4 items.

 

I thought you were busy on a newbie guide.

 

SMmemtype-> 19, SMmemspeed->800. However, the changes are only effective in about this mac screen. When I click more info button to get to system Profiler, the memory information are not available under the memory section. It says " There was an error while gathering this information"

Why didn't you mention these things up front? Those changes are not right for this laptop. But, yes it looks like something changed regarding the detail info. The memory details get reported for me in 10.5.7 but do not as of 10.5.8. I'm not sure what changed. Cosmetic though, isn't it?

[wargle]

Has anyone tried to update to 10.6.1? Was it successful?

[econsult]

I am very new to OSX... having trouble with installing the kexts. After running the kexts update commands I receive this output. Any help would be greatly appreciated!!!!

 

-Cheers

 

"

AppleACPIPS2Nub.kext is not authentic; omitting from mkext.

Natit.kext is not authentic; omitting from mkext.

VoodooBattery.kext is not authentic; omitting from mkext.

VoodooPS2Controller.kext is not authentic; omitting from mkext.

VoodooPS2Keyboard.kext is not authentic; omitting from mkext.

VoodooPS2Mouse.kext is not authentic; omitting from mkext.

VoodooPS2Trackpad.kext is not authentic; omitting from mkext.

No kexts found for architecture i386; skipping architecture.

AppleACPIPS2Nub.kext is not authentic; omitting from mkext.

VoodooPS2Controller.kext is not authentic; omitting from mkext.

VoodooPS2Keyboard.kext is not authentic; omitting from mkext.

VoodooPS2Mouse.kext is not authentic; omitting from mkext.

VoodooPS2Trackpad.kext is not authentic; omitting from mkext.

No kexts found for architecture x86_64; skipping architecture.

No mkext archives created.

[itwong]

Why didn't you mention these things up front? Those changes are not right for this laptop. But, yes it looks like something changed regarding the detail info. The memory details get reported for me in 10.5.7 but do not as of 10.5.8. I'm not sure what changed. Cosmetic though, isn't it?

 

I've got it fixed following the guide Here

All I did is modified the sample smbios.plist and added the memory serial and now it shows up in the system profiler.

Thanks for all your help, bcc9 :-) Now all I need is 64bit voodoopower.kext ;-)

 

I am very new to OSX... having trouble with installing the kexts. After running the kexts update commands I receive this output. Any help would be greatly appreciated!!!!

 

-Cheers

 

"

AppleACPIPS2Nub.kext is not authentic; omitting from mkext.

Natit.kext is not authentic; omitting from mkext.

VoodooBattery.kext is not authentic; omitting from mkext.

VoodooPS2Controller.kext is not authentic; omitting from mkext.

VoodooPS2Keyboard.kext is not authentic; omitting from mkext.

VoodooPS2Mouse.kext is not authentic; omitting from mkext.

VoodooPS2Trackpad.kext is not authentic; omitting from mkext.

No kexts found for architecture i386; skipping architecture.

AppleACPIPS2Nub.kext is not authentic; omitting from mkext.

VoodooPS2Controller.kext is not authentic; omitting from mkext.

VoodooPS2Keyboard.kext is not authentic; omitting from mkext.

VoodooPS2Mouse.kext is not authentic; omitting from mkext.

VoodooPS2Trackpad.kext is not authentic; omitting from mkext.

No kexts found for architecture x86_64; skipping architecture.

No mkext archives created.

 

For newbies, I recommended the permission repair script posted here

 

fire up terminal and do the following commands:

sudo -s

./pfix

I assume you put the script in / root directory. If not, please edit your path accordingly.

[econsult]

I've got it fixed following the guide Here

All I did is modified the sample smbios.plist and added the memory serial and now it shows up in the system profiler.

Thanks for all your help, bcc9 :-) Now all I need is 64bit voodoopower.kext ;-)

 

 

 

For newbies, I recommended the permission repair script posted here

 

fire up terminal and do the following commands:

 

I assume you put the script in / root directory. If not, please edit your path accordingly.

 

That worked!!!!! Thanks!!!!!!!!!!

[wargle]

I just wanted to also ask whether the graphics drivers are fully supported cause games like Knights of the old republic have a lot of options which are grayed out because of unsupported hardware.

[Boombeng]

Thx Bcc9, your legacyHDA works on dell studio 1535 too

 

cheers

[twuble]

Hey there, well I decided to upgrade to 10.6 After sorting out my USB key install, and then following the great instructions from bcc9 for a clean install I got the Mac all up and running great.. well almost..

 

The small thing I haven't got going yet is the VoodooBattery icon. From my memory the icon doesnt actually show until you unplug the power, but i've done that and waited a while and still nothing displays.

 

I ran the actual pkg file that bcc9 created for the ACPI bug/fix, and then ran the kexts for VoodooPower and VoodooBattery. Both have gone into the System/Library/Extensions folder (I'm just using Kexthelper for the kext installs, but I read there was a problem if one of these kexts wasnt in the S/L/E directory)

 

Has anyone gotten the VoodooBattery to work fine? Is there some step or configuration that I'm missing? Has anyone got it working with the ACPI package file?

 

Oh and when I bootup in verbose it looks like the ACPI is all loading ok, I see a few messages regarding it and they look good. But apart from the boot messages I'm not sure where else to check, though the package did say it installed fine.

 

Thanks.

[bcc9]

Now all I need is 64bit voodoopower.kext ;-)

I think I'm repeating myself, but I haven't seen progress on voodoopower since before the 10.6 release, and it has been surpassed by voodoopstate (at least for now). Voodoopstate adds 64 bit support and an application with which you can control the various p-states directly.

 

I've just applied my super-LFM p-state patch to voodoopstate and have updated post #1 to replace voodoopower with voodoopstate. An additional catch is that you need a separate kext to manage halt/restart support, such as OpenHaltRestart. I've put that in post #1 as well.

[itwong]

I think I'm repeating myself, but I haven't seen progress on voodoopower since before the 10.6 release, and it has been surpassed by voodoopstate (at least for now). Voodoopstate adds 64 bit support and an application with which you can control the various p-states directly.

 

I've just applied my super-LFM p-state patch to voodoopstate and have updated post #1 to replace voodoopower with voodoopstate. An additional catch is that you need a separate kext to manage halt/restart support, such as OpenHaltRestart. I've put that in post #1 as well.

 

Thanks for the super+LFM p-state patch, so with voodoopstate.kext, do we still need the stock AppleIntelCPUPowerManagement.kext besides the OpenHaltRestart.kext?

 

In addition, I've noticed the system time in Snow leopard is a few hours off from the one in my windows 7. I believe it has something to do with AppleRTC.kext and it can be fixed by DSDT.aml. Is it just me having this issue? It's quite annoying that time does not syncronize on all OS. The only temporary fix I could think of is to set the timezone to some european country and this will offset the difference in Windows 7. Does your DSDT.aml include a fix for the cmos reset problem? Please point me in the right direction. Thank you for your reply :-)

[bcc9]

Thanks for the super+LFM p-state patch, so with voodoopstate.kext, do we still need the stock AppleIntelCPUPowerManagement.kext besides the OpenHaltRestart.kext?

Yes, as far as I know. Theoretically AppleIntelCPUPowerManagement would pick up the p-states and do everything without an extra "voodoo" kext, but for some reason it's not.

In addition, I've noticed the system time in Snow leopard is a few hours off from the one in my windows 7. I believe it has something to do with AppleRTC.kext and it can be fixed by DSDT.aml. Is it just me having this issue? It's quite annoying that time does not syncronize on all OS. The only temporary fix I could think of is to set the timezone to some european country and this will offset the difference in Windows 7.

Yes, I haven't seen a real fix for the UTC vs local time problem.

Does your DSDT.aml include a fix for the cmos reset problem?

This system does not have that problem - the IO segment length for the RTC is already set at 2 in the stock dsdt.

Thx Bcc9, your legacyHDA works on dell studio 1535 too

Great, I didn't know. Seems like there should be a sticky advocating genuine HDA support. I think a lot of folks are still needlessly banging their heads against voodoohda which typically has distortion problems.

 

Let me know if you guys figure out gain control for the mics.

 

Has anyone gotten the VoodooBattery to work fine? Is there some step or configuration that I'm missing? Has anyone got it working with the ACPI package file?

Per post #1, you should have the modified dsdt loaded&working as well. You didn't mention that so I suspect that's your problem. I have also posted troubleshooting info for this a while back.

[wargle]

I just wanted to also ask whether the graphics drivers are fully supported cause games like Knights of the old republic have a lot of options which are grayed out because of unsupported hardware.

 

The same options on windows are not grayed out. Can some one please answer me?