Clover General discussion

[Slice]

Thanks, Slice!

 

Well, the resolution is specified in the config.plist. And it's also present in the log, as you can see below.

 

 

 

Preboot.log attached, as well, in case you want to check out other things.

Looks good

2:392  0:003  SetScreenResolution: 1440x900 - setting Mode 3

2:617  0:224  Video mode change to mode #3: Success

2:617  0:000  Console modes reported: 4, available modes:

2:617  0:000    Mode 1: 80x25 (current mode)

2:617  0:000    Mode 3: 100x31

2:617  0:000    Mode 4: 128x30

 

If you still have an issue use CsmVideoDxe.efi. It is not loaded now.

 

 

Use fdisk I got this

Jianwei:~ jianweiliu$ sudo fdisk /dev/disk0

Password:

Disk: /dev/disk0 geometry: 15566/255/63 [250069680 sectors]

Signature: 0xAA55

         Starting       Ending

 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

------------------------------------------------------------------------

 1: EE 1023 254  63 - 1023 254  63 [         1 -  250069679]

 2: 00    0   0   0 -    0   0   0 [         0 -          0] unused      

 3: 00    0   0   0 -    0   0   0 [         0 -          0] unused      

 4: 00    0   0   0 -    0   0   0 [         0 -          0] unused 

There is no Active partition

Jianwei:~ jianweiliu$ diskutil list 

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *128.0 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS Mavericks               64.0 GB    disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:         Microsoft Reserved                         134.2 MB   disk0s4

   5:       Microsoft Basic Data                         62.6 GB    disk0s5

/dev/disk1

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *31.6 GB    disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                  Apple_HFS Install OS X Mavericks  31.3 GB    disk1s2

/dev/disk2

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk2

   1:                        EFI EFI                     209.7 MB   disk2s1

   2:                  Apple_HFS HDD                     999.9 GB   disk2s2

It's impossible to have GPT without EFI and ESP in most computer,how could you say I couldn't have ESP?And how could you say boot0ss scan hfs+ when boot0ss boot ESP on my computer.How could you say I have ESP and don't have ESP when I use boot0af and boot0ss?Boot sector doesn't affect ESP exist.

 

This is OK. You have GPT drives with real ESP and have to use boot0af. It will be good as I do the same on my computers.

Your question is just language barrier.

[magnifico]

preboot.log will be enough

 

./bdmesg >boot.log

bdmesg.zip

This is amazing   

[arsradu]

Looks good

2:392  0:003  SetScreenResolution: 1440x900 - setting Mode 3

2:617  0:224  Video mode change to mode #3: Success

2:617  0:000  Console modes reported: 4, available modes:

2:617  0:000    Mode 1: 80x25 (current mode)

2:617  0:000    Mode 3: 100x31

2:617  0:000    Mode 4: 128x30

 

If you still have an issue use CsmVideoDxe.efi. It is not loaded now.

You are correct. It's not loaded now because I removed it. As I said above, with our without it, the issue is still there.

 

I can reinstall that driver and come back with an updated preboot/boot log (cause now I know how to make one ) which will probably show CsmVideoDxe.efi as being loaded.  But I'm not sure that will make any difference to the actual problem. I don't know. If you think it's worth it, I'll do it.

 

Slice, is this supposed to happen? I took a fresh new boot.log now and this is what I found.

 

 

boot.log.zip

[liujianwei]

Looks good

2:392  0:003  SetScreenResolution: 1440x900 - setting Mode 3

2:617  0:224  Video mode change to mode #3: Success

2:617  0:000  Console modes reported: 4, available modes:

2:617  0:000    Mode 1: 80x25 (current mode)

2:617  0:000    Mode 3: 100x31

2:617  0:000    Mode 4: 128x30

 

If you still have an issue use CsmVideoDxe.efi. It is not loaded now.

This is OK. You have GPT drives with real ESP and have to use boot0af. It will be good as I do the same on my computers.

Your question is just language barrier.

No,it's OK to use boot0af on my SSD because SSD boot0af load ApplePCIIDE.kext,but it's not OK to use boot0af on my USB Flash Drive because USB boot0af doesn't load ApplePCIIDE.kext,but fakesmc.kext load whatever I do.That's my question.Why this happen?

[Slice]

You are correct. It's not loaded now because I removed it. As I said above, with our without it, the issue is still there.

 

I can reinstall that driver and come back with an updated preboot/boot log (cause now I know how to make one ) which will probably show CsmVideoDxe.efi as being loaded.  But I'm not sure that will make any difference to the actual problem. I don't know. If you think it's worth it, I'll do it.

 

Slice, is this supposed to happen? I took a fresh new boot.log now and this is what I found.

Screen Shot 2015-09-17 at 9.11.29 PM.png

This is very rare incompatibility of your nVidia and CsmVideoDxe

0:637  0:000  CsmVideoDriverBindingStart
0:637  0:000  Enable the device status=Unsupported
0:637  0:000  attributes Restored
0:637  0:000  CsmVideoDriverBindingStart end Unsupported

May be you have to update VBios?

Or live as is. I don't know how to resolve the issue.

 

 

No,it's OK to use boot0af on my SSD because SSD boot0af load ApplePCIIDE.kext,but it's not OK to use boot0af on my USB Flash Drive because USB boot0af doesn't load ApplePCIIDE.kext,but fakesmc.kext load whatever I do.That's my question.Why this happen?

 

Language barrier.

 "SSD boot0af load ApplePCIIDE.kext" - I don't understand what it means.

[liujianwei]

This is very rare incompatibility of your nVidia and CsmVideoDxe

0:637  0:000  CsmVideoDriverBindingStart
0:637  0:000  Enable the device status=Unsupported
0:637  0:000  attributes Restored
0:637  0:000  CsmVideoDriverBindingStart end Unsupported

May be you have to update VBios?

Or live as is. I don't know how to resolve the issue.

 

 

 

Language barrier.

 "SSD boot0af load ApplePCIIDE.kext" - I don't understand what it means.

Clover doesn't have CSM,which means doesn't have fully MBR support.You wanna deny yourself?

[43n79w]

Test this version

OsxAptioFixDrv-64.efi.zip

 

debugging the problem is almost impossible.

You may include this file and got a log. May be this log tell us what is happen

DumpUefiCalls.efi.zip

 

So I just wanted to follow-up. Sorry for the delay. I had slide=0 as a boot argument for my Yosemite installation. This is what was throwing off my installation. Once I removed it, I was able to use OsxAptioFix2Drv-64.efi.

[artur_pt]

hello Slice

 

i see in source big changes in config.plist for clover ..

 

custom entries works good without that changes i use mavs , yose and el capo in same hd , with diff patches for the OS .. without any problem .. is not easy to recent users config clover .. is become worst .. 

 

is only what i'm thinking

 

thanks

[Slice]

Clover doesn't have CSM,which means doesn't have fully MBR support.You wanna deny yourself?

A little quiz for you. Answer, please!

1. What is CSM?

a) Module is BIOS, Module in hardware, c) Module is Clover, d) Module in OSX

2. What is boot0af?

a) A content of MBR sector 0, A file in Clover partition, c) A kext, d) An application for OSX

3. What is legacy?

a) Allowed by law, Allowed by hardware, c) Obsolete technology still using for backward compatibility

4. BIOS has legacy boot:

a) true, false, c) depends on CSM on/off

5. Clover can be load by BIOS legacy boot

a) true, b)false, c) nonsense

6. BIOS can be load by Clover legacy boot

a) true, false, c) nonsense

hello Slice

 

i see in source big changes in config.plist for clover ..

 

custom entries works good without that changes i use mavs , yose and el capo in same hd , with diff patches for the OS .. without any problem .. is not easy to recent users config clover .. is become worst .. 

 

is only what i'm thinking

 

thanks

Hello artur-pt,

Recent users should not use such complex abilities.

They have to set in config.plist "Timeout" and "DefaultVolume".

May be own SN in SMBIOS section and own UUID in SystemParameters. 

Other values for first boot should be default/absent.

[liujianwei]

A little quiz for you. Answer, please!

1. What is CSM?

a) Module is BIOS, Module in hardware, c) Module is Clover, d) Module in OSX

2. What is boot0af?

a) A content of MBR sector 0, A file in Clover partition, c) A kext, d) An application for OSX

3. What is legacy?

a) Allowed by law, Allowed by hardware, c) Obsolete technology still using for backward compatibility

4. BIOS has legacy boot:

a) true, false, c) depends on CSM on/off

5. Clover can be load by BIOS legacy boot

a) true, b)false, c) nonsense

6. BIOS can be load by Clover legacy boot

a) true, false, c) nonsense

C

A

C

A

C

A

The question is for semite.I'm not semite.

[mnfesq]

Thanks Slice for your answer to my last question.  I have a new one for anyone who knows the answer.  I have an entry in my Clover GUI that I want to remove.  It's for an installer that is resident on the partition that has my operating system.  If I add the GUID for it in config.plist, my main operating system no longer shows up.  Here's the code from the boot log that references the unwanted boot entry:

3:456  0:000   found entry 0. 'Boot Mac OS X from SSD-OSX', Volume 'SSD-OSX', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,3401B71B-B927-4F4C-A34B-D6D4D3266997,0x64028,0x190D7B78)\System\Library\CoreServices\boot.efi'

I don't want to tamper with my nvram.plist or the boot.efi file in Core Services without some guidance.  Any help removing the "Boot Mac OS X from SSD-OSX" from my Clover GUI would be appreciated.

[Slice]

C

A

C

A

C

A

The question is for semite.I'm not semite.

No.

1.-A

4.-C

5.-A

6.-C

Thanks Slice for your answer to my last question.  I have a new one for anyone who knows the answer.  I have an entry in my Clover GUI that I want to remove.  It's for an installer that is resident on the partition that has my operating system.  If I add the GUID for it in config.plist, my main operating system no longer shows up.  Here's the code from the boot log that references the unwanted boot entry:

3:456  0:000   found entry 0. 'Boot Mac OS X from SSD-OSX', Volume 'SSD-OSX', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,3401B71B-B927-4F4C-A34B-D6D4D3266997,0x64028,0x190D7B78)\System\Library\CoreServices\boot.efi'

I don't want to tamper with my nvram.plist or the boot.efi file in Core Services without some guidance.  Any help removing the "Boot Mac OS X from SSD-OSX" from my Clover GUI would be appreciated.

Hide

SSD-OSX

Edited September 18, 2015 by Slice
correct 4 answer

[arsradu]

This is very rare incompatibility of your nVidia and CsmVideoDxe

0:637  0:000  CsmVideoDriverBindingStart
0:637  0:000  Enable the device status=Unsupported
0:637  0:000  attributes Restored
0:637  0:000  CsmVideoDriverBindingStart end Unsupported

May be you have to update VBios?

Or live as is. I don't know how to resolve the issue.

 

Yesterday I had to (re)install Windows 10 (which I hate, by the way) on my PC in order to check the VBIOS version and maybe flash a newer one, if available.

 

Not sure there is anything newer than that (although that version seems to be from 2012)...

I've seen something on MSi forums here.

And that is the exact model of my card, and that is the exact same VBIOS that guy is having (80.07.35.00.04). But I don't understand: is there such a thing as an "UEFI Bios for the video card?". Is this what I should be looking for? And is that one (the one posted as reply) newer than the one I have? And what the hell is UEFI GOP BIOS? What is GOP in this circumstance? Go Pro? )

 

Anyway, I was thinking...could it really be because of incompatibility with CsmVideoDxe driver, when I have the exact same problem with or without it, once I select Patch VBios?

 

I can also take your advice and leave it as it is, if this proves itself to be harder than it looks to fix, but when I get a higher res monitor, wouldn't this issue persist, making graphics even less appealing, considering the card will be the same one, the CsmVideoDxe driver will be the same one and the patch for Vbios will be the same one?

[Mirone]

GOP = Graphics Output Protocol

https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface

[Riley Freeman]

A UEFI GOP video bios is used in conjunction with disabling CSM in the bios. For this you need a UEFI OS and a board that has the option to disable CSM (not all UEFI boards can, like my Z68). With a UEFI GOP bios on your card and CSM disabled you can have a faster boot as the legact BIOS method of initialising hardware is disabled.

 

From the graphics point of view the main advantage is you will get native resolution boot for Windows and OS X without needing an edited CsmVideo module or the CsmVideoDxe Clover driver. However if you have any third-party pci(e) cards that need to be initialised during boot (like SATA) they also need to have UEFI support or they will be ignored.

 

If your card doesn't have an official UEFI GOP bios it's possible to create one with Andy's tool here. I've used it successfully on a Geforce 210 and a HD5450.

[arsradu]

A UEFI GOP video bios is used in conjunction with disabling CSM in the bios. For this you need a UEFI OS and a board that has the option to disable CSM (not all UEFI boards can, like my Z68). With a UEFI GOP bios on your card and CSM disabled you can have a faster boot as the legact BIOS method of initialising hardware is disabled.

 

From the graphics point of view the main advantage is you will get native resolution boot for Windows and OS X without needing an edited CsmVideo module or the CsmVideoDxe Clover driver. However if you have any third-party pci(e) cards that need to be initialised during boot (like SATA) they also need to have UEFI support or they will be ignored.

 

If your card doesn't have an official UEFI GOP bios it's possible to create one with Andy's tool here. I've used it successfully on a Geforce 210 and a HD5450.

Thank you very much for the explanation!

 

As you can see in my previous post, I actually did find a UEFI GOP BIOS, on the official MSi forums. So I guess I don't need to create one on my own.

 

Now, what you're saying is that, with this GOP Bios, I eliminate the need for a CsmVideo driver. Which is cool and all. But I'm not sure my issue is CsmVideoDxe related in the first place... Since, with or without that, the issue persists.

 

Also, I'm not sure I have the option to disable CSM in UEFI, on my motherboard. Never really dug deep enough for that.

 

What if CSM is not disabled in UEFI (let's say the motherboard doesn't have such an option)? Will flashing a GOP Bios cause any issues? Or is it just a matter of not really enjoying the full potential of having such a Bios on my video card?

 

One thing I didn't understand in your post:

 

However if you have any third-party pci(e) cards that need to be initialised during boot (like SATA) they also need to have UEFI support or they will be ignored.

 

What do you mean by that? Isn't SATA separated from PCI? I can't really see the relation between these two. I've only got my video card on PCI, but my HDDs are connected via SATA (as usual, I guess)... ) So, I'm not sure I got this part. Can you please, give me an example of such a case?

[joe75]

GOP is only for pure UEFI initiation because a "bios" driver can only be started in CSM. Without a GOP driver UEFI will automatically switch to and load CSM.

 

Speed of loading is not really a factor. The main purpose is for full graphics support in the "boot" environment and has no affect after an OS has started 

[arsradu]

GOP is only for pure UEFI initiation because a "bios" driver can only be started in CSM. Without a GOP driver UEFI will automatically switch to and load CSM.

 

Speed of loading is not really a factor. The main purpose is for full graphics support in the "boot" environment and has no affect after an OS has started 

Thanks, Joe. So I can pretty much go ahead and flash that. I need to see how can I make a backup of my current VBios before attempting that. Seems pretty risky to me. I flashed my motherboard BIOS twice so far. But never attempted such a thing on my video card. I suppose it's not that much different.

 

Anyway, do you foresee any issues if I'm attempting to run Windows, on a NON-GPT HDD (my old HDD), while having a GOP BIOS on my video card? Will that still work? I don't really want to move all my data from that HDD, to another HDD, then format it for GPT, then reinstall all my stuff and move the data back. So, any idea if I can still flash that BIOS and have no issues running Windows on my other HDD? I'm not really using Windows (unless there are no Mac alternatives) but still, when I need to switch to Windows, I would like to be able to do that.

[joe75]

It will be fine. Use a windows flashing tool and there should be no problems. An app like GPU-Z can dump the current bios for back up.

 

There is no problem with your drives. Something like Riley mentions is if you had an add-on card or controller that only has a bios driver separate from the boards firmware drivers.

[Riley Freeman]

A GOP vbios is usually like a dual-bios. It is UEFI and legacy in one. So when you disable CSM the UEFI part kicks in. With CSM enabled it will default back to the legacy bios. There should be no risk in trying it.

 

On my Z68 there's no option to disable CSM. There is an option to prefer UEFI over Legacy and when I tried this the board hung at post. So it's worth checking for any CSM options in the motherboard BIOS.

 

For my Z68 I use an alternative CsmVideo UEFI module that gives me full resolution boot without needing CsmVideoDxe. There are a few of these. Gigabyte has one as does the QUO bios. I can't remember which one I'm using now. it might even be a newer Asus one.

[arsradu]

A GOP vbios is usually like a dual-bios. It is UEFI and legacy in one. So when you disable CSM the UEFI part kicks in. With CSM enabled it will default back to the legacy bios. There should be no risk in trying it.

 

On my Z68 there's no option to disable CSM. There is an option to prefer UEFI over Legacy and when I tried this the board hung at post. So it's worth checking for any CSM options in the motherboard BIOS.

 

For my Z68 I use an alternative CsmVideo UEFI module that gives me full resolution boot without needing CsmVideoDxe. There are a few of these. Gigabyte has one as does the QUO bios. I can't remember which one I'm using now. it might even be a newer Asus one.

Thanks a lot, Joe and Riley. You guys are awesome.

 

Wait, so Gigabyte has a CsmVideo module? Can I use that with Clover? And if so, where do I get it from? I don't remember seeing something like that on Gigabyte's website. Is this an official thing? Or is it a mod made by someone who really knows what he's doing? )

 

I will try to flash that BIOS I mentioned above tonight, and let you know the result.

 

You know what's funny? I do have full resolution boot without CsmVideoDxe and without patching VBios. But, unfortunately, if I disable the VBios patch in Clover, my second-stage boot logo is gone. And if I enable it, the (second-stage) logo is back, but the resolution goes to neverland.

[joe75]

A GOP vbios is usually like a dual-bios. It is UEFI and legacy in one. So when you disable CSM the UEFI part kicks in. With CSM enabled it will default back to the legacy bios.

 

Exactly. GOP is not a separate driver. GOP is a code of instructions that starts the graphics drivers in the UEFI environment.

[arsradu]

Exactly. GOP is not a separate driver. GOP is a code of instructions that starts the graphics drivers in the UEFI environment.

I just got smarter.

Thanks, Joe.

[Riley Freeman]

You know what's funny? I do have full resolution boot without CsmVideoDxe and without patching VBios. But, unfortunately, if I disable the VBios patch in Clover, my second-stage boot logo is gone. And if I enable it, the (second-stage) logo is back, but the resolution goes to neverland.

 

If you have full resolution boot then you probably have the CsmVideo module I'm talking about. I haven't had much success with second-stage boot logos on my Z68 here but I haven't tried patching the VBios.

 

I've attached the three CsmVideo modules I have. Maybe one of them will work with the vbios patch. You need to replace the existing module in your BIOS with MMTool or UefiTool and reflash it.

CsmVideo.zip

[arsradu]

If you have full resolution boot then you probably have the CsmVideo module I'm talking about. I haven't had much success with second-stage boot logos on my Z68 here but I haven't tried patching the VBios.

 

I've attached the three CsmVideo modules I have. Maybe one of them will work with the vbios patch. You need to replace the existing module in your BIOS with MMTool or UefiTool and reflash it.

Yeah, Inject EDID (built-in feature in Clover) and Patch VBios did the trick for me. But...adding the VBios patch made the resolution scale down unfortunately.

 

There is no flashing tool for Macs, right? Also, can I go back to my original CsmVideo in case things go south really fast? Can I back up the current one before flashing the one from you? FFS (the files). LOL