-
Posts
10026 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
Type ? at Chameleon boot loader and look for the appropriate command to manually set back resolution to 1280x800. Once booted, undo your Chameleon Wizard change.
-
Dell Vostro 200 - Snow Leopard/Lion/Mountain Lion/Mavericks
Hervé replied to Hervé's topic in The Archive
-
If you follow my ML guide to the letter, you can't normally go wrong. At least on the initial 64bit initial install (without graphics acceleration). This assumes your initial USB installer is correct and it seems that is not the case... May be you should start by telling us what you did, step by step, not missing anything you did in the process.
-
If you managed to boot with -f, you must now rebuild your cache. You can either use myFix (quick) for that or choose to rebuild it manually. The manual way has the advantage of showing any potential errors/conflicts that could prevent successfull cache rebuild. It's done through Terminal command sudo kextcache -system-prelinked-kernel. Search the forum for a compatible card, there's a section dedicated to it. Yes, you can do it on your own.
-
How about with -f flag?
-
You should not have any graphics issues with the pack I posted in my guide, knowing that you need to replace the SSDT file by the file that fits your own CPU. I could play clips, watch movies or streams when I tested those. I never tried any mkv files though.
- 150 replies
-
- e6420
- Dell Latitude
- (and 5 more)
-
I guess you meant DSDT. Do not confuse DSDT table extraction from BIOS with what you call "creation". Extracting a DSDT to then use the generated .aml file "as is" is basically useless. OS X / Chameleon can perfectly use the table from BIOS directly. You only use a DSDT file if you've had a need to patch the table. This is not mandatory per sé, some systems work perfectly without a patched DSDT. Furthermore, attempting to extract a DSDT when a DSDT.aml file is already used... simply regenerates that file! In other words, it's totally useless. In the case of the E6420, I believe all bootpacks already provide a patched DSDT so you should be covered from that angle. Just place your SSDT file in /Extra and make sure it's loaded. You should then see a real difference in terms of SpeedStepping using tools such as HWMonitor.
- 150 replies
-
- e6420
- Dell Latitude
- (and 5 more)
-
Something wrong with d830 HiRes(1920x1200) DSDT.aml file
Hervé replied to yuriym21's topic in The Archive
Ok, will need to look at the two tables to try and find out what's wrong in the D830 HiRes table. -
Something wrong with d830 HiRes(1920x1200) DSDT.aml file
Hervé replied to yuriym21's topic in The Archive
It may not work, but try the DSDT of the D630 X3100 HiRes. -
Boot with -f bootflag to take your hardware modifications into account. Otherwise, you retain the same boot cache.
-
Sorry, it's offline, pending EDP work completion.
-
Answer Yes to questions about kexts removal, answer No to question about MBR patch installation (i.e. do not install/apply MBR patch).
-
Configure BIOS as per recommended settings in pinned thread.
-
See previous reply. You also normally need to disable either Intel graphics or nVidia graphics as only one can run: Optimus not supported on Hackintosh. Lastly, there are lots of threads related to the E6410 nVidia on the forum, read them thoroughly. Jake pointed you to Patel's very complete guide, it should get you sorted.
-
Intel wireless cards are not supported so yours needs to be disabled or replaced. Intel wireless cards were known to interfere with OS X startup on some Latitude D series, may be yours does the same here too.
-
Something wrong with d830 HiRes(1920x1200) DSDT.aml file
Hervé replied to yuriym21's topic in The Archive
Can you please post your /Extra folder? Also, check that your BIOS is configured as per recommended settings listed in the dedicated pinned thread in this very forum section. -
Disable or remove your Intel wireless card. It will have to be replaced by a supported model.
-
Dell D830 (bios A17) Crestline Graphics installation problem (OS 10.7.2)
Hervé replied to yuriym21's topic in The Archive
Whatever the OS X version you go for, you can only run a Crestline laptop in 32bit kernel mode. There's no graphics support for the GMA X3100 graphics chip in 64bit mode. If you're running Lion 10.7.2 in 64bit default mode, that'll be the reason why you're not getting any graphics support. Make sure you use our bootpack and if EDP fails, we'll work something out to make it work. I think it's fairly safe for you to go back to ML 10.8.5 (if that's what you prefer) and we'll get those features to work. No need to downgrade BIOS, it'll not make any difference. -
Use "More Reply Options" button at bottom right corner of message box...
-
Dell Precision 670 - Paxville - BIOS A07 - GT210 black screen (ML & M)
Hervé replied to vanguart's topic in The Archive
Those apps are probably querying the CPU directly through CPUID command, in which case it'll never work on the Precision 670. Irwindale and Paxville Xeon CPUs do not have that instructions set. That does not mean SSSE3 emulation is not there though... In your case, I think you have little choice except switching to different apps or using a more modern machine with a CPU that possess the necessary full instructions set. -
That kind of reboot is usually a sign of unsupported vanilla kernel. I suspect you may not have a Core2Duo model… What does your BIOS Device Info page show?
-
Duff installer maybe. Did you check that your BIOS was configured as per recommended settings in the dedicated pinned thread of this very section? No Intel wireless that you would have kept enabled?
-
Ha! That's a good old well-known BIOS matter. Basically, it's doing the full/thorough POST checkup, not the quick one. That happens when BIOS thinks a parameter has changed. You can interrupt the checkup by pressing ESC then Enter. This thorough checkup will eventually go away after a full clean shutdown or startup. I recommend you make sure to use the patched AppleRTC kext, though it does not always prevent that long BIOS POST. My Latitude D laptops do that frequently, especially as I switch between different OS X versions.
-
Does your D430 have a Core2Duo CPU? If so, boot with flags -f -v. If not, you have a 32bit CPU and you're limited to Snow Leopard (Lion and ML need 64bit C2D CPUs minimum). You can only boot 32bit (i.e. with Chameleon option arch=i386) the MLPF installer and/or your "MLPF'ed" ML installation. Naturally, the initial vanilla ML installation is 64bit kernel mode only. As Spock would say, it's only logical...
-
Then boot with -v and check where it's holding for so long.