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

Here we go

Second mic removed

HDAIDT.kext.zip

Thanks, I like that one better - copied to post #1. I do still get a bunch of audio assertion messages but only in 64 bit mode and those errors showed up before as well. Haven't figured them out...

 

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

Just be sure you've moved on from dsmos to fakesmc, and be sure to upgrade your hdaidt to the current version for working audio. Then, upgrade away.

I'm not aware of any downside.

If you don't have time to deal with any potential problems you shouldn't upgrade anything however.

Link to comment
Share on other sites

Hi, first time poster but long time lurker. Thanks bcc9 for all his hard work. I need some friendly advice.

 

I have a triple booting SXPS1340 (Win7, Snow, Ubuntu 9.10). First I used unallocated space to install Win7 so that I would get an EFI partition. Then I installed Snow with Chameleon and the "Extra Folder" in the HFS+ partition. I tried in the EFI partition but that seemed to screw up everything. I then used a Win7 install DVD to switch the active partitions and do a recovery to fix the Win7 booting in the NTFS partition. Now, the EFI partition is still all screwed up. Anyway, I installed Ubuntu with Grub2 at the Ext4 partition. With the HFS+ partition being set to active, I have Chameleon controlling the booting and everything runs fine.

 

Except I am still curious about my EFI partition. It still has remnants of the old Win7 boot files in there. Do I delete those, try installing Chameleon there with the Extra Folder and set it as the active partition? Any tips or hints on what that I should look out for when doing this? I really don't want to mess up my system. Thanks.

 

EDIT: Should the EFI partition be reformatted and turned into FAT32?

Link to comment
Share on other sites

I don't see a real reason at this point to use an EFI partition instead of /Extra under OSX unless you're doing something special like sharing the EFI partition across multiple OSX installs.

If you installed windows with an EFI partition, then you can't get rid of it unless you move your BCD store to a different partition such as the old traditional window's C: You can do that with bcdedit but it's not user friendly.

 

Your EFI partition is probably only 100MB or so so it's probably not worth doing anything with.

 

None of this has anything to do with the 1340 in particular so if you want to follow up please start a new multiboot thread and just point me to it...

Link to comment
Share on other sites

I have been reading the post for the 1340 audio kext and battery icon display and have been following to the T. I used the Psystar EFI boot loader to install Snow Leopard. With the help of Bcc9's help was able to get bluetooth and trackpad. I noticed that most of the threads point to placing kexts in the /Extra/Extension's folder which I don't have. Does this prohibit me from getting audio working along with the battery icon. I need help!

Link to comment
Share on other sites

fakesmc.kext updated! V2.5 reporting CPU temps. Works fine! Proceed without caution lol

Nice, it works with the istat monitoring apps like istat nano. Those are reporting temps between 3 degrees C lower and up to 10% lower than voodoomonitor. I'm guessing voodoomonitor is wrong here.

 

Update: Turns out fakesmc is reporting the wrong temps here...

I looked it up and tjmax should be 105 for these 45nm processors not 100. tjmax = tcc = junction temperature.

Too bad fakesmc doesn't have a table for the various intel processors... In the mean time just replace the 100 with 105 in fakesmc's plist.

Link to comment
Share on other sites

One thing I've noticed recently is the constant ACPI read (the flashing light every two seconds post-sleep) has stopped occurring in the move to FakeSMC 2.5, 10.6.2 and using the vanilla powermanagement.

 

Is anyone else finding this as well?

 

I've been getting fairly good response from setting the 1340 as a MacBook5,1 in the smbios ... at least I believe that throttling is working as it should.

 

Throttling down is definitely working ... but I wonder about throttling up when doing intensive things like compressing video or rendering graphics ... more investigation is needed here.

 

What smbios settings have other people found been working for them on throttling?

 

Also, has anyone noticed some bugs with their broadcom wireless driver post-10.6.2 update? I'm on the dell 1510 ... and its become a lot buggier after update, especially coming back from sleep and acquiring an IP address.

Link to comment
Share on other sites

HI everyone,

 

I have a Dell XPS M1530 with the following characteristics :

 

BIOS A12

Core2Duo T8300 2.4 GHz

3 GB DDR2

GForce 8600MGT (1680x1050)

120 GB SSD OCZ Vertex (great ssd disk)

Marvell Yukon 88E8040 + Wifi Intel 4965AGN

Double boot : snow leopard 10.6.2 and windows 7

 

- Chameleon boot loader

- /Extra/com.apple.Boot.plist :

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs\

/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>arch=i386</string>

<key>Rescan</key>

<string>Yes</string>

<key>Graphics Mode</key>

<string>1680x1050x32</string>

<key>Timeout</key>

<string>0</string>

<key>SMBIOSdefaults</key>

<string>No</string>

<key>DSDT</key>

<string>rd(0,0)/Extra/DSDT.aml</string>

</dict>

</plist>

 

Kexts :

drwxr-xr-x@ 3 root wheel 102 21 oct 21:19 AppleACPIPS2Nub.kext

drwxr-xr-x@ 3 root wheel 102 21 oct 21:19 ApplePS2Controller.kext

drwxr-xr-x@ 3 root wheel 102 21 oct 21:19 IOATAFamily.kext

drwxr-xr-x@ 3 root wheel 102 28 jui 05:37 OpenHaltRestart.kext

drwxr-xr-x@ 3 root wheel 102 10 nov 04:23 VoodooBattery.kext

drwxr-xr-x@ 3 root wheel 102 20 nov 19:02 VoodooHDA.kext

drwxr-xr-x@ 3 root wheel 102 21 oct 21:19 VoodooTSCSync.kext

drwxr-xr-x@ 3 root wheel 102 21 oct 21:19 fakesmc.kext

 

 

Does someone know where I could find a DSDT for my computer ?

Actually I already use one but it doesn't have all is necessary for the sound for instance.

If you need I already have dumped acpi tables.

 

For now halt/reset doesn't work and no sound.

I made what is suggested on this thread but still doesn't work so I suppose the last thing to have a look is the dsdt.

Link to comment
Share on other sites

Does anyone have experience with the new nvidia chip that dell is putting into the 1340, the 210m chip? I currently have two identical XPS 1340 laptops since Dell shipped me the wrong part in the first one. The only difference between the two is that the new one has the expansion hybrid SLI card that they identify has a 210m with 512 MB of discrete memory. I've noticed all the problems with the 9500 card that people mention so I'm wondering if this is another problem on that line.

 

My laptop with the vanilla 9400m works pretty well using note#1 and all the additions. I am currently using it to post. However the other laptop will get a panic that will halt right after it fails, using NVKush I see a weird error about it not being able to find the name, something like Can I Has Model? Also, there is a timeout warning from the ACPI AppleIntelPower whatever manager. I was able to install SL without a problem but I can't boot the initial time into the OS.

 

Is there anyway that I can customize the necessary files on my machine to only load the 9400m and not attempt to load the 210m?

Link to comment
Share on other sites

One thing I've noticed recently is the constant ACPI read (the flashing light every two seconds post-sleep) has stopped occurring in the move to FakeSMC 2.5, 10.6.2 and using the vanilla powermanagement.

 

Is anyone else finding this as well?

I hadn't noticed that before but yes it looks like that problem is gone. I checked back to 10.6.1 and the original fakesmc and it was still gone so I'm not sure what change took care of this. Would like to know (so that we can be sure it stays fixed).

 

Firewire after suspend/resume is still a problem however.

I've been getting fairly good response from setting the 1340 as a MacBook5,1 in the smbios ... at least I believe that throttling is working as it should.
Have you found any reason to change it vs my recommendation in post #1? Dynamic CPU frequency works with the default smbios.plist I have in post #1.

 

Throttling down is definitely working ... but I wonder about throttling up when doing intensive things like compressing video or rendering graphics ... more investigation is needed here.
As mentioned before, you can verify frequency adjustments with voodoomonitor.

 

Does someone know where I could find a DSDT for my computer ?
Probably in one of the numerous 1530 threads. Us 1340 users certainly wouldn't have the dsdt for it. That system isn't even an nvidia chipset.
Link to comment
Share on other sites

Hi,

 

After removing the older SnowOSX Universal installation I tried the boot132 method after obtaining a retail Leopard disk but I keep getting this error when booting from boot 132

 

cdboot: BIOS disk read error at sector : 00000023

 

Help?

Link to comment
Share on other sites

Have you found any reason to change it vs my recommendation in post #1? Dynamic CPU frequency works with the default smbios.plist I have in post #1.

 

Yes, I was experiencing problems. CPU was throttling down around 6x with voltage reporting an even lower pstate using voodoomonitor. But the CPU wouldn't step up when needed.

 

With the original smbios you list in post #1, a particular video file takes around 30mins to compress. With the smbios altered to SMproductname MacBook 5,1 the same video file takes only 9 minutes.

 

Interestingly, voodoomonitor seems to measure the voltage for my CPU going to much lower p-states than 6x (the voltage at system idle normally sits at 1.116v) but voodoomonitor doesn't report any multiplier lower than 6x.

 

EDIT: voltage at system idle normally sits at 1.068v ----- lower even than any of the pstates shown in voodoomonitor (the lowest pstate shown in voodoomonitor is 798mHz, x 3.0, 1.116v, 0x861A, 0x7)

Link to comment
Share on other sites

Yes, I was experiencing problems. CPU was throttling down around 6x with voltage reporting an even lower pstate using voodoomonitor. But the CPU wouldn't step up when needed.
Well I have no such problem with my default smbios.plist; cpu freq. steps up & down with only appleintelcpupowermanagement being used.

You would see the behavior you describe if you install voodoopstate but don't also run pstatechanger.

 

With the original smbios you list in post #1, a particular video file takes around 30mins to compress. With the smbios altered to SMproductname MacBook 5,1 the same video file takes only 9 minutes.

When I was debugging this, I tested and found that measured cpu performance follows the multiplier as reported by voodoomonitor. Ie the reported frequency is what the cpu is actually running at. (Unlike the # reported by cpu-x which doesn't track the multiplier correctly unless you happen to be using voodoopower).

Interestingly, voodoomonitor seems to measure the voltage for my CPU going to much lower p-states than 6x (the voltage at system idle normally sits at 1.116v) but voodoomonitor doesn't report any multiplier lower than 6x.
In voodoomonitor's p-states tab you're seeing p-states below 6x being listed; those are the potential super-lfm pstates. It's actually wrong to list the multipler as being less than 6x, in super-lfm mode the frequency is still 6x but that's another story, and I've yet to ever see super-lfm working on my laptop.

 

That p-state table is just statically computed by voodoomonitor based upon cpu reported max/min values and don't reflect measured states. The calculated vids are also wrong (see my version of pstate changer if you want better values). Oh and the voltages are wrong too as voodoomonitor cribbed the wrong equation from voodoopower.

 

So in summary you shouldn't take voodoomonitor's voltages seriously, in fact you should probably ignore the p-states tab. The status tab is handy to see the current multiplier. That's the main purpose for which I was recommending it.

 

I successfully have installed SL on a friend's XPS 1340 fine but for some reason the touchpad/trackpad doesn't work at all. VoodooPS2/ACPIPNub2 are also installed correctly because the keyboard is working fine. Is there something I'm missing?
I've seen that once or twice, it seems like the kext cache can be mis-built in some circumstances. Rebuilding it clears things up.
Link to comment
Share on other sites

I've seen that once or twice, it seems like the kext cache can be mis-built in some circumstances. Rebuilding it clears things up.

 

Hm it's really weird right now. I ran the kextcache commands thru terminal and it just says that (kexts i moved to S/L/E/) are not authentic, therefore omitting from mkext.

Link to comment
Share on other sites

D:..bastards!! Though I know we live in differnt countries, mine was of the first lots too, well at least the first lots here! =P...meh..sorry about that...I always though you had a 8600.

 

Anyway, just for you all know, I just recieved my Magic Mouse, it works great with our internal bluetooth, though no wake from sleep with mouse. (Option is grayed in system preferences menu).

 

=)!

Link to comment
Share on other sites

I'm having a small problem, My audio doesn't work anymore. Every time i boot it says sound assertion 0 failed in source cache. What can i do to make my audio work again?

 

Edit: Nevermind, i got it to work, but i had to plug in my earphones and boot up my laptop for it to work.

Link to comment
Share on other sites

I'm still trying to get the SD card reader figured out. As far as I can get (if one can consider this success) is using the new VoodooSDHC.kext where as soon as I insert a SD card, the system instantly freezes requiring a hard reboot.

 

Has anyone been getting any success with this?

 

kale

Link to comment
Share on other sites

 Share

×
×
  • Create New...