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

[bcc9]

works smoothly updating from 10.6.1 to 10.6.4. install myHack installer 1.1 to upgrade bootloader and run comboupdate 10.6.4. use pfix to repair permission. use bcc9's acpi patcher to fix acpi detection issue and use 10.6.3 AppleHDA patch to patch the stock AppleHDA to work with bcc9's HDAidt v4. Everything now works like it should. Thank you for everyone contributing in this thread

When 10.6.4 came out, I updated AppleHDA for that version:

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

I just put the link into post #1 as well.

[olegpronin]

Hello

 

mac os x 10.6.4, dell 1340.

 

I'm using deep sleep all the time, works great exept one thing: each time when I did deep sleep and power on the laptop, I see that CMOS was bad and receive reset of bios settings.

 

How can it be fixed?

 

So, if you turn off the Power Adapter before press "Sleep" button in the menu, your laptop will NOT have bad cmos checksum.

 

I believe something wrong in Device (ADP0) {} in DSDT?

 

May somebody check it? bcc9, please try to check this..

 

For activating deep sleep (little longer going to sleep but no battery power is going out while laptop sleeps) you can use it:

$ sudo pmset -a hibernatemode 1

 

Thanks for any replies

[bcc9]

I'm using deep sleep all the time, works great exept one thing: each time when I did deep sleep and power on the laptop, I see that CMOS was bad and receive reset of bios settings.

 

How can it be fixed?

 

So, if you turn off the Power Adapter before press "Sleep" button in the menu, your laptop will NOT have bad cmos checksum.

 

I believe something wrong in Device (ADP0) {} in DSDT?

 

May somebody check it? bcc9, please try to check this..

 

For activating deep sleep (little longer going to sleep but no battery power is going out while laptop sleeps) you can use it:

$ sudo pmset -a hibernatemode 1

 

Thanks for any replies

My system with chameleon RC4 doesn't hibernate properly ever. I assume you're only able to get hibernation partially working by using one of the chameleon forks, such as aserebln's? I wonder if he's planning on integrating his changes back to the project, he doesn't seem to be actively working on it.

[olegpronin]

My system with chameleon RC4 doesn't hibernate properly ever. I assume you're only able to get hibernation partially working by using one of the chameleon forks, such as aserebln's? I wonder if he's planning on integrating his changes back to the project, he doesn't seem to be actively working on it.

 

I'm using acere_LDR 1.9.

 

Hibernation works perfect exept small problem with CMOS resetting if adapter was powered when you started hibernation..

[bcc9]

I'm using acere_LDR 1.9.

 

Hibernation works perfect exept small problem with CMOS resetting if adapter was powered when you started hibernation..

Where is acere_LDR 1.9, and why are you using that? I'd suspect a problem with that bootloader first.

[olegpronin]

Where is acere_LDR 1.9, and why are you using that? I'd suspect a problem with that bootloader first.

 

I Installed original Chameleon RC4 so same thing

[bcc9]

I Installed original Chameleon RC4 so same thing

With chameleon rc4, my system hangs trying to wake up from hibernation. Unless I boot with Wake=no.

 

Still don't know what you mean by "acere_LDR 1.9" and why you're using it.

[mikeraffone]

With chameleon rc4, my system hangs trying to wake up from hibernation. Unless I boot with Wake=no.

 

Still don't know what you mean by "acere_LDR 1.9" and why you're using it.

 

I assume he means aserebln 1.9 - see here:

http://wiki.github.com/aserebln/Chameleon/

[bcc9]

I assume he means aserebln 1.9 - see here:

http://wiki.github.com/aserebln/Chameleon/

Actually he probably meant aserebln booter 1.1.9, but if he now claims chameleon rc4 behaves the same way then I am lost as to what he's doing and so I can't begin to help.

[olegpronin]

With chameleon rc4, my system hangs trying to wake up from hibernation. Unless I boot with Wake=no.

 

Still don't know what you mean by "acere_LDR 1.9" and why you're using it.

 

acere loader 1.9 I mean. Based on Chameleon rc4.

 

I don't use Wake=no in my settings.

[bcc9]

acere loader 1.9 I mean. Based on Chameleon rc4.

I don't know where/what that is. I'm not going to ask again. (It is customary to provide the necessary/relevant details when asking for help).

I can't reproduce the behavior you describe.

[PacketCollision]

When booting my 1340 (which is using Ubuntu 10.04's default installed GRUB2 as the bootloader) after shutting down OSX 10.6.4, I am experiencing the CMOS reset too. I haven't tried shutting down/booting without the power adapter yet, but I'd be happy to help with a fix if bcc9 or anyone can point me in the right direction. I'm currently on BIOS A11.

 

BTW, GRUB2 otherwise works perfectly, and handles /Extra/Extensions and DSDT with no configuration. I simply installed OSX and Ubuntu, and both showed up in the grub menu working correctly out-of-the-box.

[bcc9]

So it seems those who are having problems with CMOS reset errors are all using boot loaders other than what I recommended in post #1.

A further step would be to compare the boot loader code to see what is being done different by chameleon vs these other boot loaders.

[PacketCollision]

So it seems those who are having problems with CMOS reset errors are all using boot loaders other than what I recommended in post #1.

A further step would be to compare the boot loader code to see what is being done different by chameleon vs these other boot loaders.

As a first step, would installing Chameleon to a USB key and booting that, to see if the problem goes away be useful? I'm reluctant to switch to it as my primary bootloader if I can get grub working, because I've found it to be finicky in the past, especially when it comes to coaxing windows to boot under BIOS and a GPT disk, but I'll do it (or chainload chameleon from grub) if that will fix the problem.

 

I only have a little experience with programming bootloaders (I've done some work on SYSLINUX), but if we can confirm that the problem is in the difference between chameleon and grub, I'll see what I can do to rectify it.

[bcc9]

As a first step, would installing Chameleon to a USB key and booting that, to see if the problem goes away be useful? I'm reluctant to switch to it as my primary bootloader if I can get grub working, because I've found it to be finicky in the past, especially when it comes to coaxing windows to boot under BIOS and a GPT disk, but I'll do it (or chainload chameleon from grub) if that will fix the problem.

 

I only have a little experience with programming bootloaders (I've done some work on SYSLINUX), but if we can confirm that the problem is in the difference between chameleon and grub, I'll see what I can do to rectify it.

Yes, testing against chameleon would be useful as it's not clear that anybody has confirmed whether using something other than chameleon is enough to cause CMOS errors.

Assuming you followed post #1 to install OSX, you could just use the bootcd to run chameleon.

 

Also I haven't had trouble using GPT disks with chameleon, except on a system whose bios was too old to properly support gpt.

[olegpronin]

Then you can proceed to install the rest of my changes to get platform specific components working fully. For the case where you don't have a fancy multi-boot setup to worry about, probably the easiest bootloader setup is to use the chameleon installer, the newest seems to be named: Chameleon-2.0-r431.pkg.zip

I tried to install chameleon r431, and what's then?

 

Same thing, CMOS error after hibernation.

 

//edit

bcc9, did you install chameleon to EFI partition or to main system partition?

I'm using chameleon on efi.

[bcc9]

I tried to install chameleon r431, and what's then?

 

Same thing, CMOS error after hibernation.

Again, I don't see that behavior.

But also, I'm using chameleon rc4, as recommended in post #1.

bcc9, did you install chameleon to EFI partition or to main system partition?

Neither.

I use grub, and chainload into chameleon on the osx partition.

I don't use an EFI partition on my 1340's internal disk.

 

 

So now I just tried grub2, where instead of my usual

grub->chameleon->osx (grub chainloading chameleon booting osx)

I did

grub->grub2->osx (grub chainloading grub2 booting osx)

 

Same result as before.

No CMOS error

Upon resume from suspend, the disk access happens where RAM is loaded from the sleepimage, then the system hangs.

I have to reboot thru chameleon with Wake=no to recover.

 

So now I'm wondering if your CMOS errors are due to something else, such as a mismatch between your DSDT version and your bios version.

[olegpronin]

So now I'm wondering if your CMOS errors are due to something else, such as a mismatch between your DSDT version and your bios version.

 

A14 bios + A14 dsdt.

 

May be system doesn't like that I use EFI partition.

[twuble]

Hmm, I seem to be a bit stuck with my 10.6.4 upgrade i've just done and am looking for suggestions.

 

I was previously on 10.6.2 from bcc9's original post on page 1 and it worked all fine. Decided to do the upgrade, so I installed 10.6.4, then ran the ACPI v1.2 pkg, and then went to fix the AppleHDA problem. To do that from what I could make out I went to S/L/E/AppleHDA.kext and went show contents. I then drilled in further and went to Contents/MacOS, under here I replaced the AppleHDA file I had downloaded from bcc9's 10.6.4 post with the one that was there.

 

That didn't make the sound work though. I even did the touch and repair of the extensions folder (using osx86tools), still didn't work, in fact it seemed to make things worse when i did the repair option and then rebooted.

 

I ended up getting a KP with AppleHDA at one so went back to the original 10.6.2 kext and installed that again, though obviously that doesn't seemed to have fixed the problem as I'm now getting this "21/07/2010 15:27:38 kernel Not loading kext com.apple.driver.AppleHDAController - not found and kextd not available in early boot.

 

Any suggestions? Have I not done the AppleHDA replacement correctly?

[bcc9]

Same result as before.

No CMOS error

Upon resume from suspend, the disk access happens where RAM is loaded from the sleepimage, then the system hangs.

I have to reboot thru chameleon with Wake=no to recover.

I went on to test with 3 different disk drives attached to my laptop, and 2 out of 3 would not resume from hibernate (requiring Wake=no to recover). With one of the disks, I could hibernate and resume just fine, still no CMOS errors.

 

I think in my failure cases, the system is not selecting the correct partition to load /private/var/vm/sleepimage. My disk that resumes with chameleon rc4 is unique in that the boot loader partition is the same as the partition being booted.

 

I went on to test with the newer AnVAL4 chameleon rc5 build: http://www.insanelymac.com/forum/index.php?showtopic=216726

and just by replacing /boot with the newer version, I can resume from hibernate just fine even when the boot loader and boot target partitions differ.

 

 

 

[unrelated, regarding AppleHDA (any way I can prevent the system from merging separate unrelated posts into single messages??)]:

Any suggestions? Have I not done the AppleHDA replacement correctly?

Apparently you haven't. I would recommend putting back the vanilla 10.6.4 AppleHDA, verifying that the system boots cleanly, and then re-apply my applehda patch for 10.6.4. To apply the patch in an idiot proof manner, copy applehda from the system directory to somewhere else, such as your desktop. Apply the patch to the copy, then use a kext helper program such as kext helper to install.

[twuble]

Apparently you haven't. I would recommend putting back the vanilla 10.6.4 AppleHDA, verifying that the system boots cleanly, and then re-apply my applehda patch for 10.6.4. To apply the patch in an idiot proof manner, copy applehda from the system directory to somewhere else, such as your desktop. Apply the patch to the copy, then use a kext helper program such as kext helper to install.

 

Excellent! Thanks for that. It seemed to take a couple of goes, but went back to the Apple vanilla 10.6.4 AppleHDA. The system still gave lots of HDA errors when I booted up with that, but then when I applied your fix (and the idiot proof way made a lot more sense!) i had sound working again! Cheers!

[hxh103]

Hi all, I've had to reinstall my OSX. I'm using the bootcd to install as last time, but it keeps giving me a "Still Waiting for root device" after it goes through all the error and starts loading up the kext. What does this mean? My HD is set to ACHI

[bcc9]

Hi all, I've had to reinstall my OSX. I'm using the bootcd to install as last time, but it keeps giving me a "Still Waiting for root device" after it goes through all the error and starts loading up the kext. What does this mean? My HD is set to ACHI

Root device not mounting during OSX boot suggests that the necessary disk controller driver didn't load. That in turn suggests that you used an incomplete OSX repack instead of a genuine 10.6/10.6.3 OSX distribution to boot off of as recommended in post #1.

[olegpronin]

bcc9, I think you still didn't understand me. I have NO problems with hibernation. I just have CMOS error all time when I turn on laptop after hibernation.

[bcc9]

bcc9, I think you still didn't understand me. I have NO problems with hibernation. I just have CMOS error all time when I turn on laptop after hibernation.

I understand you. I think you don't understand me. I have NO problems with CMOS errors. I've found that whether or not hibernation has problems depends upon boot partition layout and boot loader version. The latest chameleon rc5 build as referenced in my prior post works fine for me.