you can add your ioata kext to e/e and run a myfix from myhack after using edp if you wish. myfix will generate your kernel cache. if it does not then it might not like your ioata kext.
only issue with that is if it is named the same as the stock apple kext it will be overwritten with apple updates. then you have to remember that you replaced that kext after freaking out because wifi broke.
have you tried just shutting of the blue tooth entirely from bios? other dells have a similar install issue. you also might need an older AppleIntelCPUPowerManagement and iopcifamily kext
well i see your iopcifamily kext in e/e but where is the NVDAN50Hal located? also are you using chameleons graphics enabler option?also sometimes you have to use a PciRoot=1 flag with certain mobo's.
you can also have myhack install the bootpack by choosing the option to install extra then point it at the bootpack. and have it install to the partition you want to fix so you can get back into your drive
download the bootpack for your model to a chameleon usb stick and boot from that ..... once your back in osx install edp4 and run it for your model then you should be fine.
yeah i came across the issue before. you would have to try it before loading osx like at the chameleon prompt. hit the space bar when chameleon has the timer showing then do it. if i remember it's been a while.
have you tried swapping the cards to see if this new one works in the old machine? if it's a 1945 instead of a 1940 then yes you have to add your device id's like Herve said.
i think both models, the D630 nvidia and the M4300 share the same hardware except the graphics is NVIDIA QuadroFX 360M on the M4300.... have you ran a myfix once your in osx so it can generate a cache?
hmm this cscreen is interesting..... i wonder if it would show what resolutions the screen has in mirror mode or force set a correct resolution?
$ cscreen 1 display found Index Depth Width Height Refresh(Hz; LCD displays show 0) 1 32 2560 1440 0
$ cscreen -h Usage: cscreen [-d ] [-x ] [-y ] [-r ] [-s ] [-v] [-m] [-f] [-l] [-h] [-d ] : specifies the bit depth (bits per pixel) [-x ] : specifies the width in pixels [-y ] : specifies the height in pixels [-r ] : specifies the refresh rate in Hz [-s ] : specifies which display to use (defaults to main display) use a as the option to -s to specify the action on all displays [-v]: display valid modes (use -s to specify display or nothing for the default) [-m] : require an exact match [-f]: forces settings (ignores safety mechanisms; USE AT YOUR OWN RISK) [-l]: lists the current displays and modes [-p]: sets the requested display to be the primary display [-h]: displays the usage
i think sleepwatcher would trigger cscreen http://www.pyehouse.com/cscreen/ if i remember... the issue was that it was ppc and it would not work but it looks like they have updated it..
ok. d620 nvidia has a similar issue with display sleep. there used to be a solution that used sleepwatcher and it would trigger a script that briefly switched resolutions to turn on the display. maybe if you used something similar you can have it trigger what the hot corner does... but then again... it is only display sleep so idk how it would work out.
no i have a 620 gma.... the cure to that is adding a password in bios. the d620 has an option to also bypass the passoword on wake from sleep. so i only have to enter the password at a cold boot. sleeps and wakes fine after that.
http://www.osxlatitude.com/getting-sleep-to-work-on-your-dell/