Jump to content

[Guide] El Capitan 10.11.X - Dell Optiplex 780 (760) 755 (790) (990)


morpheousman
 Share

1,157 posts in this topic

Recommended Posts

Well, there's nothing to understand about installing Windows in UEFI mode. It's just a choice. All you have to do is prepare the Windows Install disk as explained in the second link and use Clover to boot it on a non-UEFI Bios like the one in Optiplex 760/780/790 Series.

 

The rest of the process is identical to the one used to install Windows in a "standard" (Legacy) mode.

 

The main benefit is that Clover will boot Windows more flawlessly in UEFI mode than in Legacy mode because Clover is more a UEFI oriented bootloader than a Legacy oriented bootloader (which is what Chameleon actually is).

 

Also, keep in mind that using GPT/GUID partition scheme is more flexible and secure than using old MBR partition scheme. You'll have less risks to overwrite the boot files for instance ;).

 

Read this :D.

 

 

 

I like the tiny tiny text at the end :hysterical:

 

 

 

 

I used the Guide in the second link here.

 

I had already created a partition for Windows 10 when I did my El Capitan install a couple months ago. 

 

I made an USB installer using Rufus,  with only Windows 10 on it. Then I installed Windows 10 to the partition I had previously made for it.

 

I had a few minutes of frustration trying to get the USB installer to boot, then I realized I needed to press <6> at boot.  :hysterical:

  • Like 1
Link to comment
Share on other sites

I had a few minutes of frustration trying to get the USB installer to boot, then I realized I needed to press <6> at boot.  :hysterical:

 

:lol:

 

The same happened to me :hysterical:

 

On a side note :

 

There's a drawback I forgot to mention and I think it should be highlighted :

 

Using Clover to boot a Windows UEFI installation on a non-UEFI bios equiped PCs makes mandatory to have Clover… forever :o !

 

Without Clover, these PCs won't boot Windows AT ALL !

  • Like 1
Link to comment
Share on other sites

 

:lol:

 

The same happened to me :hysterical:

 

On a side note :

 

There's a drawback I forgot to mention and I think it should be highlighted :

 

Using Clover to boot a Windows UEFI installation on a non-UEFI bios equiped PCs makes mandatory to have Clover… forever :o !

 

Without Clover, these PCs won't boot Windows AT ALL !

 

Like forever ever? Even if you wanted to turn it back to a windows machine with new drive and Windows operating system?

Link to comment
Share on other sites

Hey, just to report, polyzargone intrigued me with this so I tried and succeeded installing Win8.1 to the same HD with OSX.

 

I had two hiccups during installation process but it all went well (and it was risky since I have many files in OSX and zero trust in new Disk Utility :D ) 

 

First thing is that you have to have MBR partitioned USB because Windows wont start installer from GUID (hung there for a day before checking format method I did on it... Idiot...).

Second, I had to use GPT fdisk to revert from hybrid MBR, because I made FAT32 partition through OSX.

 

Made installation USB just copying files from Win81.iso. Not my first (nor second) choice, but It was the only Windows I had here.

  

P.S.

Renamed both win boot files and installed Clover on USB, but I had successful boot from existing Clover on EFI (HDD) every time I tried. I too forgot to press <6>, so gave up on booting from USB. :lol:  So for post-install I had to do nothing.

  • Like 1
Link to comment
Share on other sites

 

 Using Clover to boot a Windows UEFI installation on a non-UEFI bios equiped PCs makes mandatory to have Clover… forever :o !

 

Without Clover, these PCs won't boot Windows AT ALL !

 

 

Like forever ever? Even if you wanted to turn it back to a windows machine with new drive and Windows operating system?

No, its not forever, ever :).

 

Like @polyzargone said, for best compatibility with Clover, you should install Windows in UEFI mode, even if your machine has a legacy BIOS (since Clover is able to create a UEFI booting environment like a proper UEFI BIOS).

 

However, it is possible to reverse the process without reformatting or reinstalling Windows.  Post #359 partII) describes how to convert a legacy Windows install to UEFI but the procedure can be modified to convert UEFI Windows back to legacy:

 

Procedure

 

 

1.  Convert your pure GPT disk (with protective MBR) back to hybrid MBR/GPT with GDisk or simply add a FAT partition with OSX Disk Utility.

2.  Reinstall the legacy Windows bootloader files:

  • Boot your computer with a Windows install DVD/USB and open a command prompt with <Shift> <F10>. 
  • Type the following lines into the terminal, pressing <Enter> after each line...
diskpart
list disk
select disk X (where X is the number of the hard disk with Windows installed)
list partition
select partition # (where # is the partition number where Windows is installed)
active
assign letter=W
exit
bcdboot W:\windows /s W:

3.  Reboot your computer with the Windows bootloader on your hard drive.

 

 

 

 

As an aside, it's also possible to boot Windows with its own legacy bootloader and chainload to Clover installed on the OSX partition's PBR (of the same disk) or the EFI system partition of a separate disk ---> boot OSX - see Using EasyBCD to Chainload Chameleon or Clover from the legacy Windows Bootloader.

  • Like 3
Link to comment
Share on other sites

Hey Fusion71au !

 

Nice to see you here :D.

 

Thanks for clarification about going back to Legacy Windows. I wasn't sure it was possible (and also didn't know how to do that :P).

 

OFF Topic : update to Windows 10 1511 Threshold 2 was flawlessly done on legacy Bios dualboot OSX/Win10 on the same drive. But I had to unplug OS X SSD and use Clover USB pen to complete installation on triple boot OS X + Win10/Mint with different drives.

  • Like 1
Link to comment
Share on other sites

No. Well… this is actually not required.

 

Read carefully :

 

 

The option is meant to make possible the use of Chameleon (aka the alternative Booting PBR). Not using this option won't make the disk unbootable by Clover as long as you don't forget to press <6> to load it.

 

Remember that by default, the install disk boots with the Windows UEFI boot manager (bootmgfw.efi). That's why you must press <6> key to boot Clover.

 

When you say <6> does that mean pressing the F6 Function key?

Link to comment
Share on other sites

Hello Every Optiplex 755 owners,

Yet another patched DSDT :)

I applied usual patches to the original A22 for Optiplex 755 : IRQ, HPET, SMBUS, LPC, insert HDEF, PEGP, DTGP, ...
and cut some useless devices (SPK, COMA, COMB, FDC, WMI, ...)

EHC1&2 are renamed EH01&2 for 10.11.

My first version crashed early during boot (like owbp some pages before).
I spent hours to compare and modify the generic and my patched version and succeed when I transferred "MEMP" from generic to the patched version. Who knows why ?
 

Everything is OK but unfortunately, as with generic dsdt, System Profile can't show anything about sata (an error occurred...). I tried many injections in dsdt and even old kexts from 10.8 when ICH9R was in compatibility list but no luck. :wallbash:

...No obvious advantage compared to the generic version :lol:

 

Let's be satisfied to run ElCapitan on these ancient machines

DSDT-Optiplex755-fromA22.aml.zip

Link to comment
Share on other sites

@polyzargone @morpheousman

 

I'm sorry, but I do not understand very well, last week I installed W10 and OSX at least 10 times. I have a 300GB HDD, how many partitions and in what order? Before OSX or Windows?
 
I currently have created the USB drive with Rufus with only Windows 10, in another USB drive El Capitan.
 
And now?  :wub:
Link to comment
Share on other sites

@Fabiosk

 

The dualboot stuff is clearly starting to be OFF TOPIC !

 

This has been largely discussed here and you should just follow the links & guides I posted/pointed out to install Windows beside OS X. It's really not that hard and you have everything you need to successfully do this.

 

Good readings and good luck :D !

  • Like 1
Link to comment
Share on other sites

@Fabiosk

 

The dualboot stuff is clearly starting to be OFF TOPIC !

 

This has been largely discussed here and you should just follow the links & guides I posted/pointed out to install Windows beside OS X. It's really not that hard and you have everything you need to successfully do this.

 

Good readings and good luck :D !

 

:rolleyes:

 

Darn, and I was just getting ready to ask how to triple-boot with adding Linux Ubuntu or Mint.  :(

 

:hysterical:

  • Like 1
Link to comment
Share on other sites

I followed your guide to install 10.11.1 on my Dell 780 sff (120 GB ssd, 8G ram, Asus GeForce GT 610 (1GB)), using the generic DSDT as mentioned in the guide.

Installation went well and programs like Office 2011 works like a charm. Installed all App Store updates (only iTunes and one small other one).
Alle hardware including the GT 610 is recognized.
 
The problem is Firefox and Safari crash a lot! Reloading pages because of errors, spontaneous log-offs and even whole restarts of the machine! At a point Firefox did not even start any more, strangely enough when I choose in Clover booting for "InjectNVidia = no" Firefox did start again. But the problems with the webpages are not over.
There are a lot of crash reports something to do (I think) with the graphics.
 
Does someone have any ideas how to solve this?
(I had the same issue with 10.10 and I hoped 10.11 would solve this)
Link to comment
Share on other sites

try this with DSDT and Clover Nvidia Inject = yes

Device (PEG0)

            {

                Name (_ADR, 0x00010000)
                Device (GFX0)
                {
                    Name (_ADR, Zero)
                    Name (_SUN, One)
                    Method (_DSM, 4, Serialized)
                    {
                        Store (Package (0x18)
                            {
                                "@0,compatible", 
                                Buffer (0x0B)
                                {
                                    "NVDA,NVMac"
                                }, 
                                "@0,device_type", 
                                Buffer (0x08)
                                {
                                    "display"
                                }, 
                                "@0,name", 
                                Buffer (0x0F)
                                {
                                    "NVDA,Display-A"
                                }, 
                                "@1,compatible", 
                                Buffer (0x0B)
                                {
                                    "NVDA,NVMac"
                                }, 
                                "@1,device_type", 
                                Buffer (0x08)
                                {
                                    "display"
                                }, 
                                "@1,name", 
                                Buffer (0x0F)
                                {
                                    "NVDA,Display-B"
                                }, 
                                "NVCAP", 
                                Buffer (0x18)
                                {
                                    /* 0000 */    0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00, 
                                    /* 0008 */    0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, 
                                    /* 0010 */    0x00, 0x00, 0x00, 0x00
                                }, 
                                "VRAM,totalsize", 
                                Buffer (0x04)
                                {
                                    0x00, 0x00, 0x00, 0x40
                                }, 
                                "device_type", 
                                Buffer (0x0D)
                                {
                                    "NVDA,GeForce"
                                }, 
                                "model", 
                                Buffer (0x1B)
                                {
                                    "nVidia GeForce GT 610 "
                                }, 
                                "rom-revision", 
                                Buffer (0x29)
                                {
                                    "nVidia GeForce GT 610 OpenGL Engine"
                                }, 
                                "hda-gfx", 
                                Buffer (0x0A)
                                {
                                    "onboard-1"
                                }
                            }, Local0)
                        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                        Return (Local0)
                    }
                }
            }
Link to comment
Share on other sites

 

try this with DSDT and Clover Nvidia Inject = yes

Hi Pete,

This is my first DSDT editing (I'm still a noob), so I want to ask you how to do this.

I downloaded MaciASL and opened CLOVER/ACPI/patched/DSDT.aml.

I searched but there is no 'device (PEG0)' entry in the text, can I just copy and paste your code and compile or need it to be in a specific place/position in the DSDT?

Link to comment
Share on other sites

Little error in MacPeet's DSDT :

 

In "device-type"

 

Instead of NVDA,GeForce, should be NVDA,Parent (if not, possible black screen issues) :

Device (PEG0)

            {

                Name (_ADR, 0x00010000)
                Device (GFX0)
                {
                    Name (_ADR, Zero)
                    Name (_SUN, One)
                    Method (_DSM, 4, Serialized)
                    {
                        Store (Package (0x18)
                            {
                                "@0,compatible", 
                                Buffer (0x0B)
                                {
                                    "NVDA,NVMac"
                                }, 
                                "@0,device_type", 
                                Buffer (0x08)
                                {
                                    "display"
                                }, 
                                "@0,name", 
                                Buffer (0x0F)
                                {
                                    "NVDA,Display-A"
                                }, 
                                "@1,compatible", 
                                Buffer (0x0B)
                                {
                                    "NVDA,NVMac"
                                }, 
                                "@1,device_type", 
                                Buffer (0x08)
                                {
                                    "display"
                                }, 
                                "@1,name", 
                                Buffer (0x0F)
                                {
                                    "NVDA,Display-B"
                                }, 
                                "NVCAP", 
                                Buffer (0x18)
                                {
                                    /* 0000 */    0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00, 
                                    /* 0008 */    0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, 
                                    /* 0010 */    0x00, 0x00, 0x00, 0x00
                                }, 
                                "VRAM,totalsize", 
                                Buffer (0x04)
                                {
                                    0x00, 0x00, 0x00, 0x40
                                }, 
                                "device_type", 
                                Buffer (0x0D)
                                {
                                    "NVDA,parent"
                                }, 
                                "model", 
                                Buffer (0x1B)
                                {
                                    "nVidia GeForce GT 610 "
                                }, 
                                "rom-revision", 
                                Buffer (0x29)

That said, I'm not sure it is DSDT GFX injection the problem. Looks like something else to me…

 

Try this one :

DSDT.aml_DutchAcerOne.zip

Link to comment
Share on other sites

Looks like something else to me…

 

Could it be a RAM issue? I saw at the end of a crash report (sic) that I have 3 different types of RAM.

4x 2GB, 2 are exactly the same brand and typenumber, the other two are different.

Windows had no problems with this, but maybe OSX does? It is regonized as 8GB 1333 MHz.

Link to comment
Share on other sites

Could it be a RAM issue? I saw at the end of a crash report (sic) that I have 3 different types of RAM.

4x 2GB, 2 are exactly the same brand and typenumber, the other two are different.

Windows had no problems with this, but maybe OSX does? It is regonized as 8GB 1333 MHz.

 

I don't think so. If Windows's OK, there no reason OS X isn't. Plus, you'd have different problem if is was a RAM issue.

 

What's the version of OS X ?

Link to comment
Share on other sites

The problem is perhaps on the config.plist and not in the DSDT ???

 

Could be. Or the problem is using a DSDT from 760/780 series with a 755 model. I'm not even sure there's no big differences between 760/780. AFAIK, both 5450 and Generic DSDT works fine with the 760/780 but we don't have enough reports about 755…

Link to comment
Share on other sites

 Share

×
×
  • Create New...