Hervé

Could you give us your D620 specs? You're installing SL retail 10.6.3, right?

 

You should also follow, not the above guide (which is kind of obsolete now), but that fully documented in the EDP pages: http://www.osxlatitude.com/edp/

 

It'll get you through without headaches.

Great video indeed. It's possible to do it without so much dismantling, but it does require a bit of dexterity.

 

When you change your CPU, I'd strongly recommend that you do the following:

- clean off dust of the CPU fan, it's a perfect opportunity to do it (hoover does wonder there)

- wipe any thermal paste residue off the new CPU + heatsink's bottom

- put a rice grain-equivalent of ArticSilver 5 thermal paste on the CPU and apply it evenly to the surface before putting the heatsink back into place (buy some AS5 if you don't have any paste at hand, it only costs a few bobs).

 

This will ensure best possible cooling for your CPU.

CPU change is not too difficult but it does require a bit of dismantling. Anyone with a bit of time and patience/care should be able to do it.

 

D620 will support any Intel C2D with FSB 667MHZ, the T5600 being one of them but not the best. A T7xxx is a much better choice with bigger cache and higher frequencies.

Sounds like your installation USB key is invalid: it's not booting. Re-install Chameleon on it and give it a try, or re-un myHack completely if that is what you used.

 

For SL, I was always using ModCD, not myHack, so here's an opportunity to play again! (sad...)

If I'm not mistaken, there's an Intel tool for Mac that provides the CPU model. It's not at all like a CPU-Z tool, but does the job in terms of CPU identification. Then you can consult the specific pages for the CPU model/family. Wasn't it supplied as a tool in previous releases of EDP to think of it?

Indeed, you can recover from black screen by putting the D620 to sleep (close lid or press Fn-ESC) and then wake it up.

 

The other problem with this black screen thingy is that it won't let the computer go to sleep automatically. It seems to hold that feature.

Did you try to bootload your new Lion system via your USB installation key (boot off the USB key and press [ENTER] when the Chameleon delay bar starts scrolling, then select the new Lion installation)?

 

This should let you boot your new Lion system for the very 1st time, finalise the OS settings and get you to the desktop. You can then install EDP to secure things off and be able to boot directly off the hard disk from there on.

 

It always works for me on D620 nVIDIA or D630 Intel, so I see no reason why it'd be different for a D630 nVIDIA...

Yes, the USB ports are not electrically fed when the computer goes to sleep and, consequently, cannot supply 5V to connected devices. Not really a surprise, it is an expected behaviour during an energy-saving mode after all.

 

This can be somehow/partially controlled in the BIOS. If you enable the USB wake feature, the USB ports will remain electrically fed when the computer is connected to the mains but not when operating on the battery.

I don't know (yet) what causes that black screen issue, but it's bugging me. The D620 does that in SL and in Lion, grrr.

 

I think I had seen a message from Leon that indicated a possible AppleIntegratedBuffer kext issue. To be confirmed...

 

I have found that an alternative to setting the Energy Saving parameters to off/never via the Preferences panel is to open the Chameleon Boot plist in /Extra with the wizard and set the "darkwake" parameter.

I do the kext installation (you don't choose any order there), then I do the hibernation fix and then the S/L/E fix. Obviously, I'd always do the kext installation before the fixes...

Yes, it's a known minor problem. Just disable Intel Dynamic Acceleration in the BIOS (Performance -> Dynamic Acceleration) and you'll see the expected frequencies within Mac OS.

 

See here: https://osxlatitude.com/index.php?/topic/1388-d630-intel-screen-goes-black-during-boot-to-install-snow-leopard/page__gopid__9358#entry9358

 

IDA is not a critical feature, it only allow a very brief/temporary frequency boost of 1 CPU core when the other core is idle (for e.g., on my 2.2GHz T7500, IDA would allow occasional brief boost of 1 core to 2.4GHz). Not much gain in terms of real performance to be honest.

Yes, you should be able to upgrade to 10.6.8 without hiccups but maybe your downloaded combo upgrade is corrupt. After the installation and before reboot, re-run EDP 3, re-install your kexts and myFix will automatically be run at the end. You can then reboot to 10.6.8 successfully.

 

Out of curiosity, how did you disable screen off?

I'd be interested to hear if you experience the 'black screen' issue. This is when the screen goes off before the computer goes to sleep, but when you try to reactivate it, it stays dark.

 

Found a workaround, but it seems to have other side effects...

Yes, those D4x0 models need specific BIOS settings to avoid KP at wake from sleep. It's well documented on "Tweaks" pages of this site, but basically, you need to do 2 things in the BIOS:

1) set a System password

2) set password bypass on reboot/resume

 

It's a bit annoying on initial switch on, but afterwards, no need of the password and you can put the lappy to sleep & wake without problems.

Don't worry about the error messages, they won't prevent anything from working.

 

Now, re: lack of sound, I guess you proceeded with "pre-defined values" for kexts in EDP. Run EDP again and opt for your own values this time. Choose 'VoodooHDA (more stable)' option and you should get your sound back. That's how I fixed it.

Sounds like a duff installation. How did you create myHack USB key and with which version/media of Lion?

Hi,

 

Some time ago Ptesone had mentioned:

1) the 32/64bit kernel activation commands

'sudo systemsetup -setkernelbootarchitecture i386'

versus

'sudo systemsetup -setkernelbootarchitecture x86_64'

 

2) consequential modification of the /Library/Preferences/SystemConfiguration/com.apple.Boot.plist file

'Kernel Architecture'

'i386'

versus

'Kernel Architecture'

'x86_64'

 

 

I was wondering how that interacts or interferes with the chameleon.Boot.plist 32-bit (i386) flag? I've done a few tests to check things out and obtained different results depending on the Mac OS X versions.

 

1) D630 X3100 with Lion 10.7.4 (EDP 3 v409)

System will boot fully functional, whether the Chameleon 32-bit flag is set or not ("32-bit (i386)" check box of /Extra/org.chameleon.boot.plist when opened with Chameleon wizard).

 

Interestingly enough, the /L/P/S com.apple.Boot.plist file was found containing not only the 'Kernel Architecture' field, but also a 'Kernel Flags' field (found set at "arch=i386") and a whole set of other stuff looking like the actual Chameleon settings. What I've noticed is that, whatever the Kernel Architecture value (i386 or x86_64), the system will boot fully functional when the 'Kernel Flags' field of the file is kept to "arch=i386". However, if I changed this to "arch=x86_64", the system boots with graphics defaulting to 1024x768, no iStat, no keyboard, etc.

 

2) D620 nVidia 110M with SL 10.6.8 (EDP 3 v383)

Again, the system will boot fully functional whether the Chameleon 32-bit flag is set or not.

 

I found the /L/P/S com.apple.Boot.plist file of that system with an empty "Kernel Flags" field (i.e. empty string). In that condition:

a. if Chameleon Boot plist 32bit flag is set, the system will boot fully functional whatever the value "Kernel architecture" in L/P/S com.apple.Boot.plist file

b. if Chameleon Boot plist 32bit flag is unset, the system will not complete its boot when the value "Kernel architecture" in L/P/S com.apple.Boot.plist file is set to "arch=x86_64". System only completes its boot if the flag 'arch=i386' is manually entered at bootloader initial stage, i.e. 64bit mode does not appear viable...

 

 

Conclusion:

i. it seems that the "Kernel Flags" field of the /Library/Preferences/SystemConfiguration/com.apple.Boot.plist overwrites any Chameleon 32-bit flag setting/unsetting.

 

ii. does the "Kernel Architecture" field really serve a purpose?

 

iii. is there any interop between the "Kernel Flags" and "Kernel Architecture" flags of /L/P/S boot plist?

Hi,

 

1) I've had no problem with Sleep per sé on my D620 (see specs in signature). When I run EDP (you should install the latest EDP 3 available), I do not proceed with the pre-defined values but with my own and install the NullCPUManagement + SleepEnabler + Simulated SpeedStep, followed by the hibernation fix + touch S/L/E fix.

 

After that, I can close the lid of press Fn-Esc to put the D620 to sleep and press On-Off button or open the lid to wake it. No need to configure the BIOS system password like that appeared necessary on other laptops like the D4x0 to avoid KP at wake-up.

 

The only issue that subsist and that I have not fixed yet, is the screen switch-off (I see this called the 'black screen' issue). I don't know if this is configured somewhere, but after some period of idle time, the screen will go off black and when I press a key or move the mouse, it sorts of switches back on but stays dark grey. I've tried to modify the EnergySaving settings in 'Preferences' but it made no difference. I can't see anything in the BIOs for that either.

 

The only way to get my screen back again is to put the D620 to sleep and wake it. Everything then works Ok.

 

Could you give us your exact D620 specifications, especially the graphics?

Yes, after upgrading to a subsequent release, the error did not repeat. Probably a one-off.

Well, I've had those Wireless gremlins on my D620 today at my Dad's. If I moved more than 5m away from his Wireless router to a room separated by a thick stone wall, I couldn't connect to his network at all. Sometimes, the network was not listed, sometimes it was listed but I couldn't connect.

 

When I moved within 5m of the router, I could connect. I didn't have that problem with the D630, I could always connect.

 

What difference between the two?

-> D630 has Broadcom/Dell 1390 card, reported capabilities 802.11b/g

-> D620 has Broadcom/Dell 1490 card, reported capabilities 802.11a/b/g

 

Sitting side by side at approximately 3m of the router, the Dell 1390 card reports 54Mbps, whilst the Dell 1490 reports 18Mbps.

 

Obviously the 1490, being 802.11a capable, is more sensitive to signal disturbance and performing much less than the 1390. I'll have to swap them to verify if indeed it's a card issue and eventually get rid of the 1490 for a 1390.

 

I would suggest you get real close to your Wireless router to check things out.

'appears I had no 'org.chameleon.Boot.plist', no 'smbios.plist' and no 'dsdt.aml' files under /Extra! On copying the plist files + DSDT table from the USB installation key, I'm back in business.

 

Could there be something within the latest EDP that causes this problem?

Here it is:

 

I had just installed Lion 10.7.2 successfully through the recommended method, i.e. myHack 3.1 (the latest version).

 

To avoid any confusion, please note the following:

1) after Lion 10.7.2 installation, the USB HDD was not bootable -> complained about GPT error as if Chameleon did not properly install.

2) I rebooted onto internal SATA HDD with SL and installed Chameleon on the USB HDD

3) I then rebooted onto the USB HDD and completed the Lion 1st boot settings

4) Having completed those settings, I proceeded with EDP 3.1 v366 installation (installed pre-defined values for kexts)

5) On reboot, got above KP

 

Interestingly enough, if I boot via internal SATA HDD Chameleon, I can boot Lion!

 

???

Hi guys, I see there's lots going on with EDP 3.1 updates.

 

I was starting afresh with Lion on an external disk for my D620 (C2D with nVidia 1440x900) and noticed EDP 3.1 is now up to v366. However, having installed that version on a brand new 10.7.2 installation, I get KP at restart, no matter what I try. Looks like severe regression here...

Correct!

-> http://ark.intel.com/products/27233/Intel-Core-Duo-Processor-T2300-(2M-Cache-1_66-GHz-667-MHz-FSB)

 

So you're limited to Snow Leopard with that CPU. Lion needs Core 2 Duo minimum.

Hi,

 

That part of myHack refers to what is called "Bootpack" here, i.e. drivers & technical specification files specific to the model you're installing Mac OS X onto. Clever people of OSXL have created these bootpacks by collecting all the necessary kexts and technical information for our laptops.

 

In your case, you have a D430 and you should therefore download the specific bootpack for that laptop and unarchive it somewhere. This will create a "Extra" folder that you should then point to when you opt for the "Supply my own" option if myHack. The tool then copies the bootpack kexts (i.e. drivers) to /Extra of the installation USB key being created.

 

Since myHack is a generic installation tool, not everyone has a complete set of specific kexts (i.e. drivers) at hand, therefore myHack offers a set of generic one. They may or may not work, that depends entirely of the computer.