Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by densen

  1. I seem to be having a problem with my speedstep. It works perfectly on initial boot up, Coolbook shows it running at 800mhz, it steps up and down as it should, depending on the load.


    However, if I put the laptop to sleep and wake it up, it gets stuck at 1200mhz and does not step up or down. This makes it hotter than it needs to be. I have tried using a number of DSDT files with my own ACPI dumps and other people's (with my CPU), tried with undervolted config and it didn't fix the problem.


    Does anyone else have this problem? How can I keep native speedstep working after I wake from sleep? Is there something I'm missing or I need to fix? Any help would be greatly appreciated.


    I'm using M1330 with nVidia GPU and T9300 CPU. Current DSDT attached.



  2. C-states however stopped working after Apple added a check on the LPC device hardware in Leopard, so I guess I need to find out how to fix that, however nor does it work with mbp5,1.


    If you could fix C-States that would be sooooooooooo good.


    My M1330 has a T9300 and even with native speedstep it gets very hot after 10-15 minutes of use. The fans go crazy after a while and I am 100% sure native speedstep is working.


    People who have gotten C-States to work have seen significant drops in CPU temps. This would hopefully increase battery life to a more normal level too.


    I have spent hours trying to learn about C-States and fix them, but it's just too hard for me at this point. If anyone could help tackle this problem I'd be so happy. I know you have the skill Superhai :)

  3. Hi Densen,


    Were you able to correct the C-state error with your patched DSDT?


    ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized


    Are you using AppleIntelCpu... kext?


    Thanks in advance.





    At the moment, I still have the C-State error. I have copied the C-State info to the DSDT but maybe there's something I'm missing? If anyone knows how to tweak it to remove the C-State error that would be great.


    Yes I'm using native AppleIntelCPUPM, no disabler. It does work, I'm guessing the SpeedStep is working fine although I haven't benchmarked it yet. The native kext does load and run fine though. Any ideas about the C-State error?

  4. Would you please upload your DSDT? I have the exact same processor and it would really help me out. Thanks.


    Yes, no problem. I will attach it to this post. I am also using the nvidia 8400m gs and there is injection data in the DSDT for that too, so make sure you have the same card if you're going to use the DSDT for your system.


    If anyone else is looking for the specific info inside the DSDT, all of the CPU SSDT information for the T9300 is right at the end of the DSDT.


  5. OK, GOt it installed and everything, but the wireless isnt working.... any suggestions or drivers or anything? Thanks


    Which wireless card are you using? Is it the intel b/g/n card that came with the laptop? If so, there are no working drivers for this card. What you can do is buy another dell 15XX (can't remember exact models) card that uses a broadcom chipset. These are natively detected as airport cards. You can easily just swap out your intel card for one of these dells, they are usually pretty cheap off ebay.

  6. Yes you are right Superhai, we are probably better using a separate driver (Voodoo) for audio rather than replacing a vanilla kext which apple can update. There is still a long way to go with VoodooHDA.


    Some users can get audio working through DSDT (but not most people). Do you think there is a chance we can configure audio through DSDT on m1330 or is this impossible?


    Also, shutdown/restart problem is closely related to nvidia drivers. Now that chameleon takes care of the graphics injection, the only other option is specifying graphics vbios rom. Would this have any influence on shutdown/restart behaviour? Or is it related to DSDT? Or other vanilla graphics kexts? I know it is difficult to tell, there are many hackintosh PCs that have no problem with shutdown/restart, it would be great if we could get some clues on fixing it for the m1330.



    If anyone is having trouble with graphics/audio/sleep/clamshell in snow leopard, I can write a more detailed tutorial.

  7. The first skeleton for my new post here


    Dell XPS M1330 for Snow thread


    Looks great so far Superhai! One thing I noticed, you mention that either ApplePS2Controller or VoodooPS2Controller can be used, I think you should make it clear that if you use VoodooPS2Controller with ACPIPS2Nub you will get a KP. Hopefully that will save some headaches ;)


    I am wondering, Superhai: Why do you include OpenHaltRestart in your boot disc if it doesn't do anything? (as far as I can tell).



    I can confirm that I now have native sleep/clamshell working by injecting my CPU (T9300) SSDT tables into my DSDT. These were extracted using acpidump in linux.


    Also, I was wrong about auto-switching on VoodooHDA, it does work but only with the left-most port (while output is set to speaker) rather than the middle port. Also, digital HDMI sound output does not work. The most annoying thing about using VoodooHDA is that it has to be unloaded/reloaded every time after waking from sleep, otherwise you get distorted buzzing sound.


    I have a codec dump for the STAC 9228 but Taruga's AppleHDA patcher isn't compatible with SL.


    Now only shutdown/restart not working as usual.

  8. How did you get sound working? Would you mind posting a few more details for noobs like me?


    VoodooHDA.kext is all you need to get sound working. Once you have it in your kext folder (which ever method you use), it will make new devices show up in the audio output. Hold down "option" (or windows key) and click the volume control in the menu bar, then select speaker or audio jack. If it doesn't show up, go to system preferences > audio > output, then select the speakers/jack as the output device, increase the volume, you should have sound. If no devices show up, VoodooHDA isn't loading, or you're not using the same audio device as I am.



    If I did this, could I still dual boot Windows?


    I did this and still dual boot. If windows is already installed on another partition and you're using MBR style partition on your drive, you will need to search google on how to modify the SL install DVD to install to MBR. Then once you configure chameleon, which will overwrite the bootloader and prevent you from booting to windows, you can either configure chameleon to boot windows, or use the windows DVD to put the windows bootloader back, then use easyBCD to add mac to the windows bootloader.


    Make sure you have your partitions setup correctly before installing SL. If you're planning on using a MacLoader style retail install, you'll need an extra (small) partition for that on top of the Mac/Windows ones.

  9. Thanks for all the help getting Snow Leopard on the m1330 so far. Big thanks to Superhai as usual for the head start :D


    So far I have the following working in Snow Leopard:

    - Retail Vanilla 10.6.1

    - Sound (partial with VoodooHDA, manual output selection required, not as good as old AppleHDA)

    - Graphics QE/CI (8400M GS 128mb)

    - 2 Finger scroll (VoodooPS2Controller + prefpane)

    - Wifi (from dell wifi card, not intel)


    Still not working:

    - Sleep

    - Shutdown/restart

    - Good battery life (I didn't even have this on Leopard)

    - Perfect sound (I miss the auto-switching from AppleHDA)


    For those who want a quick rundown of how I got to this stage...

    - Started with Superhai's latest boot CD iso (v0.2)

    - Modified the retail Snow Leopard install DVD to install to MBR (so I can dual boot Win 7)

    - Upgraded Leopard to Snow Leopard with help from Superhai's boot CD

    - Booted into 10.6.0 with boot CD and re-installed MacLoader to EFI partition (more details here)

    - Updated MacLoader partition to latest version with latest chameleon

    - Removed ApplePS2Controller.kext and AppleACPIPS2Nub.kext, replaced these with VoodooPS2Controller.kext

    - 2-Finger scroll works now

    - Updated to 10.6.1 through software update

    - Removed NVResolver.kext and added the following to my chameleon boot.plist


    - Rebooted and this enabled graphics, no injector or EFI string required (they should not be used), chameleon does all the work of detecting the nvidia card


    I also noticed that with this method, the graphics performs well right after boot up, unlike previously when the screen needed to turn off and back on for the graphics performance to improve.


    Also note that Superhai's boot CD includes the VoodooHDA.kext that will give you sound. Remember to enable it in system preferences by selecting speakers as output (if you forget to do this, you might not get sound).


    So that's all, everything is working really well now, Snow Leopard is nice and fast. We just need to find a way to make sleep work. Maybe shutdown/restart will never work on m1330 but it would be nice to investigate even more.


    Superhai: Good idea about a new thread. This one is getting very long, now that Snow Leopard is out we can start again. I think the m1330 is very close to being a perfect mac, just a few things left to fix.


    I hope this helps everyone, if there are any questions about this i'll try to answer them.

  10. You choose whatever suits you and works for you. There is a problem using the value SMBIOS provides instead of the calculated fsb passed to kernel, your clock will not count correctly. And alot depends on correct timings in OS X. OSX doesn not poll for correct timings, but just go on and on with the timing calculated at startup. One place its easy to see is that your clock will not be correct after a while (you might not experience this if your clock updates from internet).

    I am using your latest SMBIOSResolver with 10.5.4 and have found that my clock is slightly slow.


    My temporary solution is to use modbin's kernel (the clock runs fine with this kernel and the 64_bit boot flag) but I'd rather use vanilla if possible. Do you think I could tweak the SMBIOSResolver plist to fix this clock problem when im using the vanilla kernel? Im using M1330 with penryn 2.6ghz. How would I go about adding in the correct FSB info?