Jump to content

Clover problems report & features request


ErmaC
953 posts in this topic

Recommended Posts

8 hours ago, Sherlocks said:

 

your log with *efi is good. i want to know com.apple.driver.AirPort.Atheros40 (WiFi 5Ghz).

i first see Atheros40 5ghz. is it actually working?

 

 

@SavageAUS @Pavo @Badruzeus

this is last test file. i cleaned up source. please test as final before commit.

test6.zip

This works, no more freeze, just a auto reboot after clearing nvram. Well done

  • Like 1
Link to comment
Share on other sites

9 hours ago, Sherlocks said:

 

your log with *efi is good. i want to know com.apple.driver.AirPort.Atheros40 (WiFi 5Ghz).

i first see Atheros40 5ghz. is it actually working?

 

 

@SavageAUS @Pavo @Badruzeus

this is last test file. i cleaned up source. please test as final before commit.

test6.zip

Test6 working fine here.

  • Like 1
Link to comment
Share on other sites

[mention=112217]Slice[/mention]

i propose kbd-lang option in GUI part in config.plist.

now we use only kbd lang from emuvariable.efi.

if we use aptiomemoryfix.efi or osxaptiov3, not add kbd lang in nvram. therefore if user use other lang, user always see only english in recovery and installer until select lang or etc. and after update macos(when updating installing popup lang always english), we can see mixed lang on restart popup.

like emulvariables efi, can we choice option with native nvram in GUI in config?

 

process(if native NVRAM)

set "ko" language in GUI in config

if language is true, then

check kbd option.

if its true, add kbd in nvram.

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

 

 

 

  • Thanks 1
Link to comment
Share on other sites

11 hours ago, Sherlocks said:

[mention=112217]Slice[/mention]

i propose kbd-lang option in GUI part in config.plist.

now we use only kbd lang from emuvariable.efi.

if we use aptiomemoryfix.efi or osxaptiov3, not add kbd lang in nvram. therefore if user use other lang, user always see only english in recovery and installer until select lang or etc. and after update macos(when updating installing popup lang always english), we can see mixed lang on restart popup.

like emulvariables efi, can we choice option with native nvram in GUI in config?

 

process(if native NVRAM)

set "ko" language in GUI in config

if language is true, then

check kbd option.

if its true, add kbd in nvram.

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

 

 

 

Yes, you may do this.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

For UEFI we just need to use one Aptio driver, right.. Is it possible disabling multi selections for these?

I mean.. if I checked "Aptio1", then "Aptio2" will be auto-unchecked or vice versa. Thanks.

r4720.png

Link to comment
Share on other sites

10 hours ago, JorgeMax said:
The bug continues here. Today I updated the beta that came out today
Even set to "br: 0" which should be "Brazilian" for Brazilian Portuguese, I have still mixed the English language
 
2007374870_CapturadeTela2018-10-23s19_30_38.png.645c3e21b8ca811552236ca9d0739725.png478198811_CapturadeTela2018-10-23s19_33_17.thumb.png.ad7f282a4213f66bab7b8a2c85cdc7b3.png1500863573_CapturadeTela2018-10-23s19_34_24.png.e9d300e45a28deb196044aaa7e84e658.png
 
Clover v4719

tell me exactly your process. what is your update?
until you update macOS, you have to already taken a key. also show me nvram -p result.

나의 LG-F800S 의 Tapatalk에서 보냄

 

after got off my work, i tested latest beta. there is no problem.

1054212495_2018-10-246_25_11.png.9f1f196ff215a5eb23c838955cffa209.png

 

first, until update macOS, you have to set KbdPreLang option. and set your language again(initialized/one time, no need next time) in Language & Location on macOS setting.

then if release next beta update or official update, you will get only your language like me.

 


 

Edited by Sherlocks
Link to comment
Share on other sites

First I cleaned NVRAM, I downloaded the Clover 4719 revision, with "UninstallPKG" I deleted all Clover tracks (I always do this when I update it), add the "KbdPreLang" key and set it to "yes", set the " br: 0 "that proves that this key is the PTBR language, also has the" pt: 0 ", which may be the language of Portugal
Then I formatted the EFI partition in FAT32, I installed Clover always in UEFI mode, I use the driver "OsxAptioFixDrv-64.efi".
And then I rebooted the pc, soon after I had to search for new updates (since I saw that the new beta came out)
Dropped and asked to restart, but I saw that the pop-up windows showed in "English"
Completed the update and was merged between the two languages

But this your process of setting the language again before the update I did not do

Terminal Saved Output

 

Link to comment
Share on other sites

First I cleaned NVRAM, I downloaded the Clover 4719 revision, with "UninstallPKG" I deleted all Clover tracks (I always do this when I update it), add the "KbdPreLang" key and set it to "yes", set the " br: 0 "that proves that this key is the PTBR language, also has the" pt: 0 ", which may be the language of Portugal

Then I formatted the EFI partition in FAT32, I installed Clover always in UEFI mode, I use the driver "OsxAptioFixDrv-64.efi".

And then I rebooted the pc, soon after I had to search for new updates (since I saw that the new beta came out)

Dropped and asked to restart, but I saw that the pop-up windows showed in "English"

Completed the update and was merged between the two languages

But this your process of setting the language again before the update I did not do

Terminal Saved Output

 

osxaptiofix v1 can' t write NVRAM on your system. you have to use osxaptiofix1 with emulvariableuefi efi or only aptiomemoryfixup or osxaptiofix v3.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

Link to comment
Share on other sites

15 minutes ago, Sherlocks said:

osxaptiofix v1 can' t write NVRAM on your system. you have to use osxaptiofix1 with emulvariableuefi efi or only aptiomemoryfixup or osxaptiofix v3.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

 

I understand. I had already tested with "aptiomemoryfixup", with that I had problems with the clover, running the shell.efi, my keyboard when pressing certain keys, appeared several question marks
With the "emulvariableuefi" I had problems with login in the messages and facetime, I had to remove the same, since I saw that my nvram is native and I did not need it anymore
Since "osxaptiofix v3" I have never tested with it

Link to comment
Share on other sites

9 hours ago, Badruzeus said:

For UEFI we just need to use one Aptio driver, right.. Is it possible disabling multi selections for these?

I mean.. if I checked "Aptio1", then "Aptio2" will be auto-unchecked or vice versa. Thanks.

r4720.png

No matter and the comment is wrong. These drivers can be installed all togather. Clover will load only driver with highest priority

AptioMemoryFix

OsxAptioFix3Drv

OsxAptioFix2Drv

OsxAptioFix1Drv

OsxLowMemFix

They never interfere.

  • Thanks 2
Link to comment
Share on other sites

@Slice

i propose how about change intelmaxvalue from decimal to hex?

- Sandy Bridge/Ivy Bridge: 0x0710(1808)
- Haswell/Broadwell: 0x056C(1388)/0x07A1(1953)/0x0AD9(2777)/0x1499(5273)
- Skylake/KabyLake: 0x056C(1388)
- Coffee Lake: 0xFFFF(65535)

 

now, in GUI, intelmaxvalue has limit decimal 4 digits. coffelake intelmaxvalue is 65535(5 digits). Would not it be better to have a more familiar hexadecimal number? in config too.

thanks in advance

 

Edited by Sherlocks
Link to comment
Share on other sites

1 hour ago, Sherlocks said:

@Slice

i propose how about change intelmaxvalue from decimal to hex?

- Sandy Bridge/Ivy Bridge: 0x0710(1808)
- Haswell/Broadwell: 0x056C(1388)/0x07A1(1953)/0x0AD9(2777)/0x1499(5273)
- Skylake/KabyLake: 0x056C(1388)
- Coffee Lake: 0xFFFF(65535)

 

now, in GUI, intelmaxvalue has limit decimal 4 digits. coffelake intelmaxvalue is 65535(5 digits). Would not it be better to have a more familiar hexadecimal number? in config too.

thanks in advance

 

The procedure GetPropertyInteger already is able to parse Decimal as well as Hex values so you can write hex values in config.

For GUI yes, it should be rewritten.

Link to comment
Share on other sites

1 hour ago, Slice said:

The procedure GetPropertyInteger already is able to parse Decimal as well as Hex values so you can write hex values in config.

For GUI yes, it should be rewritten.

 

right. i tested each cases. thanks. what is left bugs? EDID case that i mentioned before?

 

anyone who test fresh install of old macOS(Sierra, High Sierra) on r4721?

apple start that mojave use efi version. so, i want to know whether this rule affect old macos. i don't have a time. if you can, just install or not(firmeware error message when installing)

 

sorry for my bad english

Edited by Sherlocks
Link to comment
Share on other sites

9 minutes ago, Sherlocks said:

 

right. i tested each cases. thanks. what is left bugs? EDID case that i mentioned before?

 

anyone who test fresh install of old macOS(Sierra, High Sierra) on r4721?

apple start that mojave use efi version. so, i want to know whether this rule affect old macos. i don't have a time. if you can, just install or not(firmeware error message when installing)

 

sorry for my bad english

Sorry, what bug you related?

Link to comment
Share on other sites

4 minutes ago, Slice said:

Sorry, what bug you related?

 

i don't have a bug for my configuration. I've got all the clover bugs I know.

just mentioned this case before. if need, i will debug

 

Edited by Sherlocks
Link to comment
Share on other sites

3 hours ago, Sherlocks said:

 

i don't have a bug for my configuration. I've got all the clover bugs I know.

just mentioned this case before. if need, i will debug

 

It is already fixed.

  • Like 1
Link to comment
Share on other sites

Hi, I have a problem to boot into the clover GUI being installed as only content on a CF card. 

 

My motherboard is not nvme m.2 ready. So I have installed my 960 evo via a PCI adapter. My bios is not ready as well, it does not know anything about my new m.2 disk.

Up to now I have a standard HD installed as well. There Clover is configured, nvme driver included and so I can boot my new m.2 disk.

Now I want to get rid of the old HD. So I have installed a cf-card attached via a cf2sata adapter. I copied the clover configuration to the cf card. Made it bootable and - nope!

 

My bios recognised the cf card as boot device. I select it from the list but I get only a grey boot manager gui (no clover gui!) after restarting the computer (no idea where exactly it comes from).

 

Just to be sure, can it be that if only clover is installed on a disk it will not boot the clover gui?

 

(Just of verification - I have tried a linux live cd image - this boots fine being installed on my CF card)

 

Any hints or howtos I can follow - I have tried a lot of them up to now...

Link to comment
Share on other sites

Having weird problem

Nvram -p

fmm-computer-name MyiMac
security-mode none
specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%04%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00 %19%16%1d%00%00%00%00/D%0aA%e1%bd%c8I%b1%a8%1b%e3%d8a%037%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBw%e1%b5%0dRAKF%a0cWO%0e%aa%a8y%7f%ff%04%00
platform-uuid %eb%b8%ca%ab]%25Y%c6%9fFs%11%dc%b9%9a%db
EFILoginHiDPI %00%00%00%00
LocationServicesEnabled %01
csr-active-config g%00%00%00
flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00

No boot-args, where have they gone?

Have this as my boot-args in Clover

radpg=15 -lilubetaall

This is with/without EmuVariable and NO nvram.plist

 

Edited by STLVNUB
Link to comment
Share on other sites

Having weird problem
Nvram -p
fmm-computer-name MyiMacsecurity-mode nonespecialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%04%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00 %19%16%1d%00%00%00%00/D%0aA%e1%bd%c8I%b1%a8%1b%e3%d8a%037%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBw%e1%b5%0dRAKF%a0cWO%0e%aa%a8y%7f%ff%04%00platform-uuid %eb%b8%ca%ab]%25Y%c6%9fFs%11%dc%b9%9a%dbEFILoginHiDPI %00%00%00%00LocationServicesEnabled %01csr-active-config g%00%00%00flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00

No boot-args, where have they gone?
Have this as my boot-args in Clover
radpg=15 -lilubetaall
This is with/without EmuVariable
 

it's normal.

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites

I too dont have the boot-args, but nvram works :D

One thing though...

My 300 series board wont load my nvram values if i boot with verbose, or even if i press the spacebar to change something. nvram only works if i just let it boot.

 

Edited by ellaosx
Link to comment
Share on other sites

Hi, it's an amazing project and thank you all for contributions. I have a problem that if I use TgtBridge to point to a device not in _SB root tree(for example, _SB.PCI0.HPET) and rename a method, all my OEM SSDTs' methods will be also renamed.

 

To be more specific, I want to rename HPET._STA to XSTA and set TgtBridge to HPET. However, apart from HPET._STA, all _STA methods in OEM SSDTs are renamed to XSTA. Here's my trouble shooting and related codes in config.plist

	                <dict>
	                    <key>Comment</key>
	                    <string>change HPET._STA to XSTA</string>
	                    <key>Find</key>
	                    <data>X1NUQQ==</data>
	                    <key>Replace</key>
	                    <data>WFNUQQ==</data>
	                    <key>TgtBridge</key>
	                    <data>SFBFVA==</data>
	                </dict>

Trouble Shooting.zip

Edited by zhengshiqi
Link to comment
Share on other sites

×
×
  • Create New...