Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

Riley Freeman
Riley Freeman
Posted
Posted

All this bios flashing/modding stuff is covered in great detail in the Ozmosis thread.

 

I always use DOS for flashing. Just feels safer that way. You can make a backup of your BIOS from there using FTK so long as there's no flash/backup protection. Make a copy of the backup and replace the CsmVideo module in it and flash. If it doesn't work out try another module or just flash the backup and you're back to where you started.

 

UefiTool is available on OS X so you don't need Windows to replace the module. There's no guarantee any of these will work with a patched VBios. I just shared them if you're feeling adventurous. BIOS flashing is always risky if you have no recovery option. I know some Gigabyte boards have a dual-bios thing in case of a bad flash.

  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

All this bios flashing/modding stuff is covered in great detail in the Ozmosis thread.

 

I always use DOS for flashing. Just feels safer that way. You can make a backup of your BIOS from there using FTK so long as there's no flash/backup protection. Make a copy of the backup and replace the CsmVideo module in it and flash. If it doesn't work out try another module or just flash the backup and you're back to where you started.

 

UefiTool is available on OS X so you don't need Windows to replace the module. There's no guarantee any of these will work with a patched VBios. I just shared them if you're feeling adventurous. BIOS flashing is always risky if you have no recovery option. I know some Gigabyte boards have a dual-bios thing in case of a bad flash.

Got it.

 

Well, mine has Dual-BIOS as well. And I did flash the BIOS a few times so far using an official tool from Gigabyte (I don't remember the name of the top of my head). And had no issues with that. Also, that tool has a backup feature, as well. So I can just back up the entire BIOS and flash it again, if anything. I just never edited one...which I think I need to do if I want it to use the custom modules you shared. So, basically, it's unpacking -> modding (replacing CsmVideo module) -> repacking -> flashing. Right? I'll check the Ozmosis thread for more info on that. Thank you! :)

Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

That's pretty much it. You might run into a problem with flashing it back using the official tool if it checks the signature of the BIOS. I think a lot of them do this nowadays. Once you modify the BIOS the signature is invalid. So it needs to be flashed by other means. This is where FTK comes in.

 

My Z68 predates all that so I have no problem flashing a modded BIOS. My X79 won't allow me to flash a modded BIOS using the built-in update tool but I can with the Asus USB Flashback feature.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

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?

My experience. Sig#1.

Motherboard Gigabyte H61M-S1 has UEFI BIOS.

Videocard Gigabyte AMD HD6670, VBios V1 had no UEFI part. But there is V12 on the Gigabyte site that can be upgraded to UEFI.

Guys from applelife,ru helped me to make a custom VBIOS as V1 legacy+V12 uefi. Yes, it is twice in size. I flashed it into card.

All works as before.

To have an advantage I have to go to BIOS and find here CSM support.

It appears only if I switch OS from Other to Windows 8 WHQL.

With WIndows 8 WHQL setting I can disable CSM support.

As well full screen logo must be disabled.

 

The difference.

Old VBIOS

I can set 1920x1080 in Clover GUI with CsmVideoDxe but with black frame around the screen.

New VBIOS + settings above.

Without CsmVideoDxe I have 1920x1080 full screen.

Now dunping ACPI tables by F4 in Clover I find one new table VFCT.aml.

It contains UEFI VBIOS part beginning at address 0x68.

  • Like 1
Link to comment
Share on other sites
Pike R. Alpha
Pike R. Alpha
Posted
Posted

Anyone here tried nvram csr-active-config=%80%00%00%00 (or that value in config.plist) because _csr_init() checks for it.

 

@slice,

 

There is a new NVRAM GUID 

// 5d62b28d-6ed2-40b4-66d3939bd76c60a5
#define APPLE_NVRAM_TRB_STAGING_COMMAND_GUID {0x5d62b28d, 0x6ed2, 0x40b4, 0x66, 0xd3, 0x93, 0x9b, 0xd7, 0x6c, 0x60, 0xa5}
extern EFI_GUID gAppleEFINVRAMTRBStagingCommandGuid
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Anyone here tried nvram csr-active-config=%80%00%00%00 (or that value in config.plist) because _csr_init() checks for it.

 

@slice,

 

There is a new NVRAM GUID

// 5d62b28d-6ed2-40b4-66d3939bd76c60a5
#define APPLE_NVRAM_TRB_STAGING_COMMAND_GUID {0x5d62b28d, 0x6ed2, 0x40b4, 0x66, 0xd3, 0x93, 0x9b, 0xd7, 0x6c, 0x60, 0xa5}
extern EFI_GUID gAppleEFINVRAMTRBStagingCommandGuid

OK, this is unknown guide for me.

But what I have to do with it?

Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted

I don't know what timespan you mean by 'new', but I stumbled upon it before, so had to be either in an early El Cap DP or in Yosemite already.

Added the Apple GUIDs I know about below... no guarantee for the names, but I tried to stick to Apple names present as symbols in binaries or make up names that sound about right. One or two names are also from the Mac OS X Internal books iirc.

#define APPLE_VENDOR_NVRAM_GUID \
  { 0x4D1EDE05, 0x38C7, 0x4A6A, { 0x9C, 0xC6, 0x4B, 0xCC, 0xA8, 0xB3, 0x8C, 0x14 } }

#define APPLE_EFI_NVRAM_GUID \
  0x7C436110, 0xAB2A, 0x4BBB

#define APPLE_EFI_NVRAM(Data41, Data42, Data43, Data44, Data45, Data46, Data47, Data48) \
  { APPLE_EFI_NVRAM_GUID, { Data41, Data42, Data43, Data44, Data45, Data46, Data47, Data48 } }

#define APPLE_BOOT_GUID \
  APPLE_EFI_NVRAM (0xA8, 0x80, 0xFE, 0x41, 0x99, 0x5C, 0x9F, 0x82)

#define APPLE_CORE_STORAGE_NVRAM_GUID \
  { 0x8D63D4FE, 0xBD3C, 0x4AAD, { 0x88, 0x1D, 0x86, 0xFD, 0x97, 0x4B, 0xC1, 0xDF } }

#define APPLE_EFI_NVRAM_TRB_STAGING_COMMAND_GUID \
  { 0x5D62B28D, 0x6ED2, 0x40B4, { 0xA5, 0x60, 0x6C, 0xD7, 0x9B, 0x93, 0xD3, 0x66 } }

#define APPLE_WIRELESS_NETWORK_NVRAM_GUID \
  { 0x36C28AB5, 0x6566, 0x4C50, { 0x9E, 0xBD, 0xCB, 0xB9, 0x20, 0xF8, 0x38, 0x43 } }

#define APPLE_EFI_APPEARANCE_NVRAM_GUID \
  { 0xFA4CE28D, 0xB62F, 0x4C99, { 0x9C, 0xC3, 0x68, 0x15, 0x68, 0x6E, 0x30, 0xF9 } }

#define APPLE_EFI_NVRAM_TRB_SECURE_VARIABLE_GUID \
  { 0xF68DA75E, 0x1B55, 0x4E70, { 0xB4, 0x1B, 0xA7, 0xB7, 0xA5, 0xB7, 0x58, 0xEA } }
Link to comment
Share on other sites
Pike R. Alpha
Pike R. Alpha
Posted
Posted

I don't know what timespan you mean by 'new', but I stumbled upon it before, so had to be either in an early El Cap DP or in Yosemite already...

Correct. And I meant new as in not already known in Clover. Perhaps this should be added to DarwinDumper, in case it wasn't done already.

 

@slice, add them to Clover, like other unknown GUIDs, and wait for someone to come up with a real answer because I have no idea what they are used for.

  • Like 1
Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

No.

1.-A

4.-C

5.-A

6.-C

Hide

SSD-OSX

 

If I hide SSD-OSX, I can't boot to my main installation of El Capitan.  When I installed El Capitan on SSD-OSX, the installer was on my desktop.  I moved the installer after I installed El Cap but the entry remains.  That's why this is a problem.  I wish it was as easy as hiding SSD-OSX.  If you have any other or more specific suggestions, I would appreciate your input.

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

To have an advantage I have to go to BIOS and find here CSM support.

It appears only if I switch OS from Other to Windows 8 WHQL.

With WIndows 8 WHQL setting I can disable CSM support.

As well full screen logo must be disabled.

This information was pure gold! Thank you so much. I would have searched a long time for that option in BIOS, and wouldn't figure out that I need to look under Windows 8 or Windows 8 WHQL to find it. Good news? It's there! And it can be disabled (I just did). :D

post-1303722-0-09690300-1442604216_thumb.jpg

  • Like 1
Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

Hello Slice,

 

can you consider to add Clover native support for nvidia's EDID injection dsdt tags, like used here:

http://www.insanelymac.com/forum/topic/218556-sony-vaio-vpcf115fm-discussion-dsdt-injection/?p=2152883

 

Or is it already supported, and if so, how can I use it?

 

It finally makes most sony vaios full gfx accelerated...

 

Its the following in the _DSM method of the NGFX device:

"AAPL00,override-no-edid", 
                                Buffer (0x80)
                                {
                                    /* 0000 */    0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 
                                    /* 0008 */    0x36, 0x7F, 0x25, 0x00, 0x00, 0x00, 0x00, 0x00, 
                                    /* 0010 */    0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, 
                                    /* 0018 */    0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, 
                                    /* 0020 */    0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, 
                                    /* 0028 */    0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 
                                    /* 0030 */    0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x40, 0x38, 
                                    /* 0038 */    0x80, 0xB4, 0x70, 0x38, 0x40, 0x40, 0x3C, 0x3C, 
                                    /* 0040 */    0x55, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, 
                                    /* 0048 */    0x40, 0x38, 0x80, 0x80, 0x71, 0x38, 0xAA, 0x40, 
                                    /* 0050 */    0x80, 0x80, 0x88, 0x00, 0x68, 0xC8, 0x10, 0x00, 
                                    /* 0058 */    0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, 
                                    /* 0060 */    0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, 
                                    /* 0068 */    0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, 
                                    /* 0070 */    0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, 
                                    /* 0078 */    0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0x1F
                                },
  • Like 1
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted

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.

 

This is due to the presence of boot.efi in the temporary installer files, left behind on your main OSX partition, when you directly run Apple's OSX Installer.app (“.IABootFiles” or it might be "OS X Install Data").

 

To fix:

 

 

1.  Enable showing of hidden files in Finder by typing the following in terminal...

defaults write com.apple.finder AppleShowAllFiles -boolean true ; killall Finder  

2.  Delete the hidden folder named “.IABootFiles” (or "OS X Install Data") in the root directory of your OSX partition...

post-846696-0-45655300-1434195154_thumb.

 

post-846696-0-66506600-1441893225_thumb.

 

3.  You can then re-hide the hidden files.  Type in terminal...

defaults write com.apple.finder AppleShowAllFiles -boolean false ; killall Finder

 

 

  • Like 2
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Ok.. So flashing VBios didn't end well. I just recovered using a flashable USB drive and the backup I made earlier. Now I think I might have broken the audio module on my moderboard. Not sure how that happened. But I have no more sound. And the speakers are fine. Anyone know how to double check this? Can it be from mb Bios? I didn't touch that.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Hi, I've just downloaded Clover r3270 from http://sourceforge.net/projects/cloverefiboot/

 

However, Avast for Mac flags the download as having 19 suspected infections of type Win32:Evo-gen[susp]

 

Can I safely ignore these warnings and put it down to false positives?

This is OpenSource software without Troyans.

This package was compiled by me usual way in OSX environment. I think OSX is still virus free.

 

Ok.. So flashing VBios didn't end well. I just recovered using a flashable USB drive and the backup I made earlier. Now I think I might have broken the audio module on my moderboard. Not sure how that happened. But I have no more sound. And the speakers are fine. Anyone know how to double check this? Can it be from mb Bios? I didn't touch that.

Sound hardware consists of two devices, PCI controller and Audio codec.

You can check if Clover sees PCI controller. See boot.log.

If yes then load VoodooHDA and get his dump. It will find Audio Codec chip.

 

Otherwise you may use DarwinDumper for full diagnostics including audio.

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Sound hardware consists of two devices, PCI controller and Audio codec.

You can check if Clover sees PCI controller. See boot.log.

If yes then load VoodooHDA and get his dump. It will find Audio Codec chip.

 

Otherwise you may use DarwinDumper for full diagnostics including audio.

I'm not sure what I'm looking for.

 

I attached the boot.log, maybe you can take a look at it, if you have time.

 

Last night I installed the Realtek audio driver for Windows. I don't have sound in there either. And, usually, when I plug one of the audio jacks, it would pop-up and show me which one I plugged in. It would recognize it. Now it didn't. Also, I only have digital audio options in there. There used to be a "Speakers" section there.

boot.log.zip

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

I'm not sure what I'm looking for.

 

I attached the boot.log, maybe you can take a look at it, if you have time.

 

Last night I installed the Realtek audio driver for Windows. I don't have sound in there either. And, usually, when I plug one of the audio jacks, it would pop-up and show me which one I plugged in. It would recognize it. Now it didn't. Also, I only have digital audio options in there. There used to be a "Speakers" section there.

If Windows says "Good bye, audio" then that is.

Clover found the PCI controller, both HDMI and HDA

72:277  0:000  HDA Controller [8086:0C0C] :: PciRoot(0x0)\Pci(0x3,0x0) => setting specified layout-id=1 (0x1)
72:277  0:000  HDA Controller [8086:8C20] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1)

Can't say more because you don't set "Detect" and using AppleHDA while VoodooHDA may gives you diagnose.

 

  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

If Windows says "Good bye, audio" then that is.

Clover found the PCI controller, both HDMI and HDA

72:277  0:000  HDA Controller [8086:0C0C] :: PciRoot(0x0)\Pci(0x3,0x0) => setting specified layout-id=1 (0x1)
72:277  0:000  HDA Controller [8086:8C20] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1)

Can't say more because you don't set "Detect" and using AppleHDA while VoodooHDA may gives you diagnose.

 

Thought you might say that... I'll order a replacement then. :( The worst thing is that I don't know why did this happen so I can avoid it in the future.

 

Anyway, if you're referring to Detect in System Parameters, you are correct. It wasn't set to Detect. But I set it now, rebooted and reattached a new boot.log. Although...I'm not hoping for much. The audio controller is probably f****d.

 

Thank you, Sergey. :)

boot.log.zip

Link to comment
Share on other sites
Faradis
Faradis
Posted
Posted

Thought you might say that... I'll order a replacement then. :( The worst thing is that I don't know why did this happen so I can avoid it in the future.

 

Anyway, if you're referring to Detect in System Parameters, you are correct. It wasn't set to Detect. But I set it now, rebooted and reattached a new boot.log. Although...I'm not hoping for much. The audio controller is probably f****d.

 

Thank you, Sergey. :)

log is still the same there is a detect command in clover device section and u need to use detect there 

 

HDA Controller [8086:0C0C] :: PciRoot(0x0)\Pci(0x3,0x0) => setting specified layout-id=1 (0x1)

HDA Controller [8086:8C20] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1) 

 

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

log is still the same there is a detect command in clover device section and u need to use detect there 

 

HDA Controller [8086:0C0C] :: PciRoot(0x0)\Pci(0x3,0x0) => setting specified layout-id=1 (0x1)

HDA Controller [8086:8C20] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1) 

 

Oh, you mean Audio detect in Devices section. Ok, I found it now.

 

New log attached.

boot.log.zip

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Oh, you mean Audio detect in Devices section. Ok, I found it now.

 

New log attached.

Yes,

6:201  0:000  HDA Controller [8086:8C20] :: PciRoot(0x0)\Pci(0x1B,0x0) => codec not detected

It doesn't mean the codec is broken because Clover tested only CAD=0.

If you can install VoodooHDA then it tested all CADs.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...