Jump to content
30960 posts in this topic

Recommended Posts

 

You patched VideoBios twice.

1.

1:875  0:083  VideoBiosPatchBytes(2 patches):
\
1:875  0:000   VideoBiosPatchInit(LegacyRegion = Not Found, LegacyRegion2 = Success) = Success
\
1:875  0:000   VideoBiosUnlock:  unlocked
\
1:876  0:001   patch 0: patched 2 time(s)
\
1:878  0:001   patch 1: patched 0 time(s)
\
1:878  0:000   patched 2 time(s)
\
1:878  0:000   VideoBiosLock: Success

Sorry for extra symbols. It is your rtf while I am on Mac.

 

2.

1:878  0:000   Patching: BT_NVDA
\
1:878  0:000   Parse Edid: descriptor block 0 is timing descriptor (h_active: 1920, v_active: 1080, h_sync_offset: 48, h_sync_width: 32, h_blanking: 160, v_blanking: 31, pixel_clock: 13850, v_sync_offset: 3, v_sync_width: 5)
\
1:879  0:001   patch 0: patched 1 time(s)
\
1:880  0:001   patch 1: patched 1 time(s)
\
1:881  0:001   patch 2: patched 1 time(s)
\
1:882  0:001   patch 3: patched 1 time(s)
\
1:882  0:000   VideoBiosLock: Success
\

 

I did see that and fixed it.

prebootlog4.txt

But is CSM really absent in original Apple firmware? In my opinion CSM is on (because of bootcamp compatibility).

You just need CSM if your graphicscard has no UEFI GOP vbios.

CSM is a compatibiliy Mode for older cards.

It's only pure UEFI Mode if it is disabled.

But is CSM really absent in original Apple firmware? In my opinion CSM is on (because of bootcamp compatibility).

 

Closest thing Apple ever had to CSM/bios is old boot-132 boot files. Even old Windows installs were started by an .efi file.

Mac graphics cards have traditionally had larger boot roms to accommodate a proprietary GOP type vbios.

I did see that and fixed it.

I see in the log

1:491  0:001   patch 0: patched 2 time(s)
1:491  0:000   patched 2 time(s)

There are your custom PatchVBiosBytes? Erase them!

Set PatchVBios=yes because it must be 4 times.

I see in the log

1:491  0:001   patch 0: patched 2 time(s)
1:491  0:000   patched 2 time(s)

There are your custom PatchVBiosBytes? Erase them!

Set PatchVBios=yes because it must be 4 times.

It gets patched twice because that exact string shows up twice in the VBios. I have attached the VBios for this card so you can see it for yourself. You can see it in the attached screen shot as well.

 

I have also tried editing the VBios using Hex Fiend to add those patches directly into the VBios and copying it into /EFI/CLOVER/ROM

 

The attached preboot log uses the following set-up:

1) Screen Resolution set to 1920x1080

2) Custom EDID with 1920x1080 resolution added using AWEDIDEditor

3) Inject EDID

4) Load VBios (with NO VBios ROM in folder)

5) Patch VBios

There are so many variations of this that I have tried. What would be the best possible steps? Should I use the edited VBios or just let Clover patch the original. If I do that, do I need to copy the original VBios into the ROM folder?

 

It has to be possible to have full resolution at Clover boot. This is a common card and a very popular monitor.

 

Thank you!

post-488070-0-60912100-1478710102_thumb.jpg

post-488070-0-11048700-1478710110_thumb.jpg

prebootlog5.txt

config.plist.zip

EVGA.GTX750Ti.2048.140825.rom.zip

Sleep / Wake is operating perfectly.

 

I have been using a Bluetooth dongle (I-O DATA USB-BT40LE).

When I put the power of Sony's Bluetooth headphones (SBH20), sleep machine it will be released.

Is it possible to make some kind of deal in the setting of "Clover"?

 

So ASPM isn´t working on hackintosh at all?

Even if the kernel log displays the following?

AppleLPC::notifyPlatformASPM  ASPM callback registered

May be you are happy with working ASPM.

 

 

It gets patched twice because that exact string shows up twice in the VBios. I have attached the VBios for this card so you can see it for yourself. You can see it in the attached screen shot as well.

 

I have also tried editing the VBios using Hex Fiend to add those patches directly into the VBios and copying it into /EFI/CLOVER/ROM

 

The attached preboot log uses the following set-up:

1) Screen Resolution set to 1920x1080

2) Custom EDID with 1920x1080 resolution added using AWEDIDEditor

3) Inject EDID

4) Load VBios (with NO VBios ROM in folder)

5) Patch VBios

There are so many variations of this that I have tried. What would be the best possible steps? Should I use the edited VBios or just let Clover patch the original. If I do that, do I need to copy the original VBios into the ROM folder?

 

It has to be possible to have full resolution at Clover boot. This is a common card and a very popular monitor.

 

Thank you!

 

I was asking you to not patch Vbios by yourself. Just set PatchVBios=yes and see what Clover will do.

 

 

Sorry guys for asking, but i want to know where CLOVER saves its bootlog file. Reason:

 

I use RX460 in PCIe-slot#1 and could boot into SIERRA

 

Any help is appreciated.

 

$ bdmesg >boot.log

bdmesg.zip

@Slice with Clover 3918

Wow ..

 

1:631  0:000  === [ Dump SMC keys from NVRAM ] ==========================

1:631  0:000  found AppleSMC protocol
1:649  0:017     fakesmc-key-NATi-ui16:00 00 
1:650  0:000     fakesmc-key-NATJ-ui8:00 
1:651  0:000     fakesmc-key-NTOK-ui8:01 
1:652  0:000     fakesmc-key-CLKT-ui32:00 00 DB 3F 
1:653  0:001     fakesmc-key-CLKH-{clh:00 00 70 80 00 01 19 40 
1:654  0:001     fakesmc-key-LsBA-ui8:90 
1:655  0:000     fakesmc-key-HI0N-ui8:04 
1:656  0:001     fakesmc-key-MSDW-ui8:00 
1:658  0:001     fakesmc-key-LSSS-ui16:02 00 
1:666  0:007     fakesmc-key-NATJ-ui8 :00 
1:667  0:001     fakesmc-key-NTOK-ui8 :01 
1:668  0:001     fakesmc-key-LsBA-ui8 :90 
1:670  0:001     fakesmc-key-HI0N-ui8 :04 
1:671  0:001     fakesmc-key-MSDW-ui8 :00 
1:673  0:001     fakesmc-key-#KEY-ui32:00 00 00 1E 
1:674  0:001     fakesmc-key-$Adr-ui32:00 00 03 00 
1:676  0:001     fakesmc-key-$Num-ui8 :01 
1:680  0:003     fakesmc-key-RMde-char:41 
1:683  0:002     fakesmc-key-RPlt-ch8*:6A 39 30 00 00 00 00 00 
1:685  0:002     fakesmc-key-RBr -ch8*:6A 39 30 00 00 00 00 00 
1:687  0:002     fakesmc-key-EPCI-ui32:06 F0 F0 00 
1:690  0:002     fakesmc-key-REV -ch8*:02 20 0F 00 00 18 
1:693  0:002     fakesmc-key-BEMB-flag:00 
1:695  0:002     fakesmc-key-BATP-flag:00 
1:698  0:002     fakesmc-key-BNum-ui8 :00 
1:703  0:004     fakesmc-key-MSTc-ui8 :00 
1:707  0:004     fakesmc-key-MSAc-ui16:00 00 
1:710  0:002     fakesmc-key-MSLD-ui8 :00 
1:714  0:004     fakesmc-key-MSWr-ui8 :19 
1:719  0:004     fakesmc-key-MSPS-ui16:00 03 
1:728  0:009     fakesmc-key-$Num-ui8:01 
1:732  0:003     fakesmc-key-BNum-ui8:00 
1:735  0:003     fakesmc-key-MSTc-ui8:00 
1:739  0:003     fakesmc-key-MSLD-ui8:00 
1:743  0:003     fakesmc-key-MSWr-ui8:19 
  • Like 1

Could anyone please help me to fix this:

I'm building CloverGrowerPro on El Capital, Xcode 8.1 and I got this error:

Building ... /Users/toantit/workspace/CloverGrowerPro/edk2/Clover/Protocols/HashServiceFix/HashServiceFix.inf [X64]
[CC] AppleUITheme
In file included from /Users/toantit/workspace/CloverGrowerPro/edk2/Clover/Protocols/HashServiceFix/sha1.h:4:0,
from /Users/toantit/workspace/CloverGrowerPro/edk2/Clover/Protocols/HashServiceFix/HashServiceFix.c:18:
/Users/toantit/workspace/CloverGrowerPro/toolchain/cross/lib/gcc/x86_64-clover-linux-gnu/4.9.3/include/stdint.h:9:26: fatal error: stdint.h: No such file or directory
# include_next <stdint.h>
^
compilation terminated.
make: *** [/Users/toantit/workspace/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/Clover/Protocols/HashServiceFix/HashServiceFix/OUTPUT/HashServiceFix.obj] Error 1


build.py...
: error 7000: Failed to execute command
make tbuild [/Users/toantit/workspace/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/Clover/Protocols/HashServiceFix/HashServiceFix]


build.py...
: error F002: Failed to build module
/Users/toantit/workspace/CloverGrowerPro/edk2/Clover/Protocols/HashServiceFix/HashServiceFix.inf [X64, GCC49, RELEASE]

Thanks a lot.

 

I was asking you to not patch Vbios by yourself. Just set PatchVBios=yes and see what Clover will do.

 

Okay. I've attached two preboot logs. One with only PatchVBios=yes. The second with PatchVBios=yes and Inject Custom EDID.

 

Still no full resolution.

prebootlog-PatchVBios Only.txt

prebootlog-PatchVBios-Inject EDID.txt

Sleep / Wake is operating perfectly.

 

I have been using a Bluetooth dongle (I-O DATA USB-BT40LE).

When I put the power of Sony's Bluetooth headphones (SBH20), sleep machine it will be released.

Is it possible to make some kind of deal in the setting of "Clover"?

Same as iBUFFALO's Bluetooth headphones(BSHSBE14), sleep wake.

hello
got this in system log :

AppleLPC::notifyPlatformASPM - registering with plugin with ASPM Support false

So, i tested that in ACPI section (clover 3911) :

<key>ACPI</key>
	<dict>
		<key>DisableASPM</key>
		<true/>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>Name</key>
			<string>DSDT.aml</string>
		</dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Length</key>
				<integer>2684</integer>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
		</array>
		<key>ResetAddress</key>
		<string>0x0cf9</string>
		<key>ResetValue</key>
		<string>0x0006</string>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>EnableC2</key>
			<true/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<true/>
				<key>PStates</key>
				<true/>
			</dict>
			<key>MaxMultiplier</key>
			<integer>8</integer>
			<key>MinMultiplier</key>
			<integer>6</integer>
		</dict>
	</dict> 

But i still have the ASPM warning in log.

Is there a compatibility trick with other keys used in my config ?

Is DisableASPM broken in 3911 ?

  • Like 1

@pico jeo

Better to have some keys twice than never :D

Dunno if this is good or if it's not important...

 

Maybe the logic should be changed to update changed keys not just to save them?

EDIT: just realized i have this too :(

Many of the duplicates are the same except for an extra space character between the type and the data, as in this example:

 

1:650  0:000     fakesmc-key-NATJ-ui8:00 

1:666  0:007     fakesmc-key-NATJ-ui8 :00

Is that extra space character supposed to be there?

  • Like 1

hello

got this in system log :

AppleLPC::notifyPlatformASPM - registering with plugin with ASPM Support false

So, i tested that in ACPI section (clover 3911) :

<key>ACPI</key>
	<dict>
		<key>DisableASPM</key>
		<true/>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>Name</key>
			<string>DSDT.aml</string>
		</dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Length</key>
				<integer>2684</integer>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
		</array>
		<key>ResetAddress</key>
		<string>0x0cf9</string>
		<key>ResetValue</key>
		<string>0x0006</string>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>EnableC2</key>
			<true/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<true/>
				<key>PStates</key>
				<true/>
			</dict>
			<key>MaxMultiplier</key>
			<integer>8</integer>
			<key>MinMultiplier</key>
			<integer>6</integer>
		</dict>
	</dict> 

But i still have the ASPM warning in log.

Is there a compatibility trick with other keys used in my config ?

Is DisableASPM broken in 3911 ?

Same here

Many of the duplicates are the same except for an extra space character between the type and the data, as in this example:

 

 

Is that extra space character supposed to be there?

Yes, it is a bug.

 

We should do

sudo nvram -c

and check with new Clover.

Same as iBUFFALO's Bluetooth headphones(BSHSBE14), sleep wake.

In my environment, Bluetooth is turned off, the machine was found to be not wake.

It has changed the bluetooth to sleep off, the bluetooth to wake when on, the automatic execution processing to.

Since my purpose of use does not matter in the above operation, I think let's take a look at the course for a while.

Hi everyone,

I'd like to know what's difference between config.plist -> ACPI -> EnableCx and config.plist -> CPU -> Cx ?

 

Thanks

PMheart

Same. Just different developers place them in different places. Both work same way.

×
×
  • Create New...