Hervé

Here are BIOS settings that are known to work on Vostro 200 under Snow Leopard, Lion, Mountain Lion, Mavericks, Yosemite, El Capitan, Sierra, High Sierra, Mojave and Catalina. The settings below apply to modded/unlocked BIOS 1.0.16 (use modified BIOS #2 available here in post #6) with which they were tested and verified: Advanced BIOS Features: . CPU Feature: . Limit CPUID Value = disabled . C1E Function = enabled . Execute Disable Bit = Enabled . Virtual. Technology = Enabled or Disabled (required to run virtual machines) . Core Multi-Processing = enabled . Quick Power On Self Test = enabled . Boot Up Numlock Status = on . Typematic Rate Setting = disabled . APIC mode = enabled . MPS Version Control = 1.4 . HDD SMART capability = enabled . Module Bay Device = Enabled . Report no FDD for Win95 = No . Delay for HDD = 3 . Full Screen Logo = disabled (or enabled) Boot Device Configuration: -> Choose according to desired setup Advanced Chipset Features: . Init Display First = PCIEx (on-boad GMA 3100 is unsupported by OS X so use a supported PCIEx card) . System BIOS Cacheable = enabled Integrated Peripherals: . USB Controller: . USB Controller = enabled . USB Operation Mode = high speed . Onboard FDC Controller = disabled (enable if you have a Floppy drive) . Onboard Audio Controller = enabled . Onboard LAN Controller = enabled . Onboard LAN Boot ROM = disabled . SATA Mode = AHCI Power Management Setup: . ACPI Function = enabled . ACPI Suspend Type = S3 (STR) . Power Management = user define . Video Off Method = DPMS . Video Off In Suspend = yes . Suspend Type = stop grant . Suspend Mode = disabled . HDD Power Down = disabled . Soft-Off by PWR-BTTN = instant-off . HPET Support = enabled . HPET Mode = 64-bit mode . Remote Wake Up = Off . Auto Power On = disabled . Power On By Mouse = Mouse Click (or Mouse Move) . Power On By Keyboard = Any KEY . AC Recovery = Off Pnp/PCI Configurations: . Reset Configuration Data = enabled . Resources Controlled by = Auto (ESCD) . PCI/VGA Palette Snoop = disabled . INT Pin 1 Assignment = auto ... ... . INT Pin 8 Assignment = auto . Maximum Payload Size = 128 Frequency/Voltage Control: . Auto Detect PCI Clk = enabled . CPU/PCI Spread Spectrum = +/- 0.9% . PCIE/SATA SCC = enabled . CPU Clock = 366 (or whatever value, parameter is ineffective) The settings below apply to standard BIOS 1.0.16 with which they were tested and verified in older OS X versions: Advanced BIOS Features: . CPU Feature: . Limit CPUID Value = disabled . Execute Disable Bit = Enabled . Virtual. Technology = Enabled or Disabled (required to run virtual machines) . Core Multi-Processing = enabled . Boot Up Numlock Status = on Boot Device Configuration: -> Choose according to desired setup Advanced Chipset Features: . Init Display First = PCIEx (on-boad GMA 3100 is unsupported by OS X so use a supported PCIex card) Integrated Peripherals: . USB Controller: . USB Controller = enabled . USB Operation Mode = high speed . Onboard FDC Controller = disabled (enable if you have a Floppy drive) . Onboard Audio Controller = enabled . Onboard LAN Controller = enabled . Onboard LAN Boot ROM = disabled . SATA Mode = RAID (no AHCI option in Std BIOS, only IDE or RAID) Power Management Setup: . ACPI Suspend Type = S3 (STR) . Remote Wake Up = Off . Auto Power On = disabled . AC Recovery = Off

There's a new FileNVRam version which could remove the issues previously experienced. By all means, do contribute to the community by testing it and giving feedback. That's how it works...

Ok, done more tests and updated the procedure in the guide. Latest Chameleon (r2170 and beyond) appears to support the ATI X1300 card with patched kexts, so the Azimutz's branch boot file + ATI module are no longer necessary. Somehow, it simplifies the installation a bit. PS: noticed that using the DVI port is much better than using the VGA one. For instance, screen sleep&wake works on DVI port, not on VGA.

I've reproduced the problem. Basically the move to EDP 5.0 does affect this particular installation, so we need to look into it. Meantime, I'll upload the necessary files and put out a quick guide in the research thread.

No.

I'll have to go and install Lion on that D620 GMA of mine. Maybe tonight... Meantime, can you say which Chameleon version you're using? If above 2170, try and rolling back and use this one: boot_r2170.zip

Yes, QE/CI for the ATI X1300 under Lion (or lack of it) remains work in progress; sorry I've just not spent much time on this recently. Still on my 'ToDo' list... Regarding the graphics issue you're experiencing with SL, there's a good chance it is due to the default boot setup arrangements. Basically, ATI X1300 is supported at Chameleon level if you use Azimutz's branch boot file + ATI module and it does not look like they're included in the bootpack. As such, there may be a problem with the graphics kexts present in the bootpack, especially the enabler. Without the Azimutz's Cham files (i.e. without low-level legacy ATI support), you will indeed need to boot with option "GraphicsEnabler=No". I can suggest 2 things: 1) take out the EVOenabler kext from the USB installer /E/E folder or your SL partition /E/E folder and re-run myFix (full) on it 2) use the Generic Extra on your myHack installer, it'll still allow to boot and install SL on the system with basic graphics support. You can subsequently tune and finalise through EDP. I'll try and do a brand new SL installation on a spare HDD later on... Thanks for your feedback, it'll help adjust whatever may be necessary.

Yep, the D620 nVidia does not like Cham r2181, stick to r2170 as advised by Bronxteck. D820 nVidia might suffer same issue. My own D620 nVidia would KP with EFINVRam error messages when I tried boot file r2181 a couple of days ago. Everything was back to normal after rolling back to r2170. No such problem with the GMA version though (on SL 10.6.8)...

I'd try and change the kext setup and choose your own settings as opposed to default ones: VoodooPS2 controller Patched AppleHDA for STAC9200 audio Voodoo Battery Emulated SpeedStep TSCsync NullCPUPwrMgmt ACPIFix (Coolbook fix) GMA950 fix I did a new System Build using the above on my D620 GMA950 running SL10.6.8 earlier tonight and that worked Ok. I had previously used the default settings and experienced KP/BSOD, presumably due to VoodooHDA audio kext. Try the above and let us know.

Yes, all those kexts with version #1111 are myHack enabled (typically, all those in /E/E) and supersede OS X original kexts. That's how kexts can be added to /E/E only, leaving Apple's original files untouched.

There are threads in this E6xxx section reporting success with L and/or ML on the E6420 with HD3000. Have a browse through...

Try to boot with option 'GraphicsEnabler=No', then maybe look in the System log.

Hi, what are the specs of your model, especially graphics? Which OS are you trying to install? I can only recommend to retry with a myHack installer so that we can take it from there.

No, I used it on both my D620 GMA (SL) + D620 nVidia (Lion) and I have edge scrolling.

EDP 5.0 worked perfectly 2days ago when I updated my D620 and did a system rebuild from EDPWeb. I guess you might have had a problem during update. Try and download a fresh copy and do a (full) re-installation. Then use /Extra/edpweb.command to redo your system build.

The manual module deletion fixed it then.

Without knowing the wireless card model, it's going to be difficult to answer...

Run /Extra/EDPWeb.command https://osxlatitude.com/index.php?/topic/2107-the-future-is-here-edp5/

pci=off ? That's a new one to me... What does that do?

You have the NVRam module + Cham boot file mismatch issue... Either remove FileNVRAM.dylib from /Extra/modules or replace/update your Chameleon boot file at HDD root by version 2170 or above. Best would be to redo a system build through EDPWeb. PS: don't use Chameleon boot file rev2181 on a D620, it will cause the system to KP...

Which card? On wake, does the wifi icon in the Finder bar stay empty (=deactivated), light gray (meaning non-connected) or does it go to black (meaning connected)? If light gray, it simply has not hooked back to your network. You say "previously I'm sure it did it straight"... What did you change or recently do then?

Just no onions in the oven tray.

Your BIOS is fine (latest version is A18, but that just brings signed firmware support). Which wireless card do you have? Does wireless not come back at all on wake, even after a minute or so?

Mmm, I just quickly checked the specifications as provided on Dell's web site and I see 2 systems with non-trivial differences. For instance: - GM45 chipset on one vs. PM45 on the other (I admit the diffs will be minor between the 2) - NVidia graphics only on one vs. Intel GMA X4500 only on the other To me, that sufficient to say the DSDT table of one model is not suitable to the other.

Well, DSDT is a BIOS table, so it's kind of specific to a model or a family of models. I could be wrong of course, but maybe the DSDT of a Latitude E64xx does not suit a Precision M44xx, unless they really share the same characteristics (chipset, controllers, graphics, screen, etc.). You could try without the DSDT (boot with option DSDT=No) or extract your own one.