Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

kushwavez
kushwavez
Posted
Posted (edited)

Well I do have Realtek card readers in my notebooks with Sinetek-rtsx.kext, I need to find an SD card now to test with.

If I remember correctly I have an old SD card laying somewhere in my basement. I'll report back about this if I found one later today.

Edited by kushwavez
Allan
Allan
Posted
Posted

I've did more tests, and the problem was the old kext :wallbash:

 

I've visit the Sinetek's page and noticed that he had updated the kext 11 days ago. Now, with this new version everything works just fine :thumbsup_anim:

 

Thank you Clover team and @Sinetek!

  • Like 2
  • Haha 1
kushwavez
kushwavez
Posted
Posted (edited)

Great!

I found two SD cards (1 full-size, 1 micro-SD) so I tested too.

On Lenovo X1 Carbon 6th (USB3.0-CRW) I used Sinetek-rtsx v1.0: Working well, after sleep/wake it's ejecting, but that just for a second, doesn't really matter. Same case with v2.5.

 

On Lenovo T440 (I think it's an RTS5227 PCI-e) Sinetek-rtsx v1.0: Freeze, restart with KP (related to Sinetek-rtsx). With v2.5 It doesn't even recognise the card anymore.

Edited by kushwavez
  • Like 1
Sherlocks
Sherlocks
Posted
Posted
Great!
I found two SD cards (1 full-size, 1 micro-SD) so I tested too.
On Lenovo X1 Carbon 6th (USB3.0-CRW) I used Sinetek-rtsx v1.0: Working well, after sleep/wake it's ejecting, but that just for a second, doesn't really matter. Same case with v2.5.
 
On Lenovo T440 (I think it's an RTS5227 PCI-e) Sinetek-rtsx v1.0: Freeze, restart with KP (related to Sinetek-rtsx). With v2.5 It doesn't even recognise the card anymore.
sorry for off topic. how about x1 carbon 6th?
i'm considering new laptop for last hackintosh.
light weight, high quality display, sound, fan noise.


Sent from my SM-N960N using Tapatalk

chris1111
chris1111
Posted
Posted
14 minutes ago, Sherlocks said:

sorry for off topic. how about x1 carbon 6th?
i'm considering new laptop for last hackintosh.
light weight, high quality display, sound, fan noise.


Sent from my SM-N960N using Tapatalk
 

You are the Rich man :hysterical: :drool: Off Topic,,, Dont know about this Lapy? Sorry :angel:

jsl2000
jsl2000
Posted
Posted
11 hours ago, Slice said:

 

Hi, Slice:

After update Clover from 5116 to 512x~5131 I always got Red Screen Panic if I press "O" for Option

How can I fix it ?

My hackintosh need legacy booting from USB flash.

IMG_0033.JPG

config.plist

Sherlocks
Sherlocks
Posted
Posted
You are the Rich man :hysterical: :drool: Off Topic,,, Dont know about this Lapy? Sorry :angel:
i'm not rich man haha. recently i'm interested in this laptop when searching proper hackintosh laptop. seems this laptop almost perfect with performance and PD charge and thundervolt too. the best of all is light weight. now i'm using intel 6th LG gram model. it is very light weight. but performance is not good although i7. and HEVC is not support. therefore i decided to change laptop.

Sent from my SM-N960N using Tapatalk

  • Like 2
Slice
Slice
Posted
Posted
3 hours ago, jsl2000 said:

Hi, Slice:

After update Clover from 5116 to 512x~5131 I always got Red Screen Panic if I press "O" for Option

How can I fix it ?

My hackintosh need legacy booting from USB flash.

IMG_0033.JPG

config.plist 17.88 kB · 0 downloads

Hello!

I want to look your debug.log

Снимок экрана 2021-02-27 в 8.19.01.png

Slice
Slice
Posted
Posted
4 hours ago, jsl2000 said:

Hi, Slice:

After update Clover from 5116 to 512x~5131 I always got Red Screen Panic if I press "O" for Option

How can I fix it ?

My hackintosh need legacy booting from USB flash.

 

config.plist 17.88 kB · 0 downloads

I'll recommend you to set

RebuildAppleMemoryMap - False

SyncRuntimePermissions — False

jsl2000
jsl2000
Posted
Posted
1 hour ago, Slice said:

I'll recommend you to set

RebuildAppleMemoryMap - False

SyncRuntimePermissions — False

Thanks for your prompt reply and help.

The new config.plist and debug log are attached here:

config.plist 2021-2-27_6-46-5_CLOVERX64.EFI.log

kushwavez
kushwavez
Posted
Posted
9 hours ago, Sherlocks said:

sorry for off topic. how about x1 carbon 6th?
i'm considering new laptop for last hackintosh.
light weight, high quality display, sound, fan noise.

 

It is really good I must say, good battery time, working combo-jack without any trouble, working Thunderbolt 3 (with eGPU)

I wanted a smaller and lighter notebook, I really didn't regret it. Configuring Clover for this was also pretty easy.

 

Internal sound quality is 'meh'... It isn't really good, I use Boom 3D to tune it a little bit, but most of the time I'm on my Bluetooth speakers or on jack.

The 1080p display is really good, but I'll change to HDR WQHD screen later on, that will be awesome.

Fan noise: There are two types of fans in 6th notebooks, Nidec and Delta.

Mine has Nidec: If ramps up, there is a high pitched sound, but not so loud. It is not that great, the Delta is better in performance, but nothing significant, it is good for i5, temp is about ~80 °C when the notebook is on 100% (rendering for example)

Battery: ~8 hrs(?), I need to replace my battery because it is dying. for now I have 4 hrs of battery if browsing the web. It is also on AC most of the time if I'm working, with charging threshold set to 80%

 

It has 3 issues, you can see in my guide in the signature, but nothing critical.

 

Overall it is a really good notebook for hackintoshing, I am really surprised how easy and trouble free the setup was.

I have 8 GB RAM, unfortunately it is soldered so I can't upgrade. I'd go for the 16 GB.

There is i7 more powerful variant too, but I'm okay with the i5. 

  • Thanks 1
Slice
Slice
Posted
Posted
2 hours ago, jsl2000 said:

Thanks for your prompt reply and help.

The new config.plist and debug log are attached here:

config.plist 17.89 kB · 1 download 2021-2-27_6-46-5_CLOVERX64.EFI.log 89.97 kB · 1 download

Reduce BIOS overclock. It is too big!

jsl2000
jsl2000
Posted
Posted (edited)
56 minutes ago, Slice said:

Reduce BIOS overclock. It is too big!

Thanks again !

The same problem remained without any BIOS overclock.

Two debug logs are attached:

The first one when "O" was entered and crashed with red screen errors showing.

The second one after successful booting of Big Sur 11.3 beta.

2021-2-27_9-35-20_CLOVERX64.EFI.log 2021-2-27_9-36-14_CLOVERX64.EFI.log

Edited by jsl2000
MacKonsti
MacKonsti
Posted
Posted
21 hours ago, Allan said:

I've visit the Sinetek's page and noticed that he had updated the kext 11 days ago. Now, with this new version everything works just fine :thumbsup_anim:

 

Can you kindly share the URL please as I have not found it? GitHub has a project but it seems abandoned.... Thank you (or send me a PM to not flood this thread, better)

 

On 2/24/2021 at 11:46 PM, MacKonsti said:

Hi everyone, @Slice and @Jief_Machak thank you again for your hard work.

Is the key/function DeleteUnused of any use, these days? What is it supposed to do today? I recall that it was supposed to remove Device XYZ from DSDTs/ACPI Tables, but specific names like floppies or other generic-named devices.

Can you briefly comment on its usefulness in Clover releases from the past 1-2 years? (or even r5xxx)

 

Coming back to Clover discussion and knowledge, please can I kindly ask you @Slice on this Clover key? Does it really have a meaning? Is it trying to remove Device (XYZ) from a fixed-list of known devices for example? (that aren't Mac supported anyway) Thank you.

Slice
Slice
Posted
Posted
58 minutes ago, MacKonsti said:

 

Can you kindly share the URL please as I have not found it? GitHub has a project but it seems abandoned.... Thank you (or send me a PM to not flood this thread, better)

 

 

Coming back to Clover discussion and knowledge, please can I kindly ask you @Slice on this Clover key? Does it really have a meaning? Is it trying to remove Device (XYZ) from a fixed-list of known devices for example? (that aren't Mac supported anyway) Thank you.

This key will delete these devices 

    DsdtLen = DeleteDevice("CRT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("DVI_"_XS8, temp, DsdtLen);
    //good company
    DsdtLen = DeleteDevice("SPKR"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("FDC0"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP1"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT1"_XS8, temp, DsdtLen);

Why are you interesting?

  • Thanks 1
matxpa
matxpa
Posted
Posted
1 hour ago, MacKonsti said:

Can you kindly share the URL please as I have not found it? GitHub has a project but it seems abandoned.... Thank you (or send me a PM to not flood this thread, better)

 

 

https://github.com/cholonam/Sinetek-rtsx

  • Thanks 1
MacKonsti
MacKonsti
Posted
Posted (edited)
1 hour ago, Slice said:

This key will delete these devices 



    DsdtLen = DeleteDevice("CRT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("DVI_"_XS8, temp, DsdtLen);
    //good company
    DsdtLen = DeleteDevice("SPKR"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("FDC0"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP1"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT1"_XS8, temp, DsdtLen);

Why are you interesting?

 

Hi @Slice thank you for your valuable input on the deeper features of Clover.

As mentioned in my earlier post, I am in the process of updating the guides in my hack repo and wanted to ask you, since you have access and understanding of Clover code.

I have been using DeleteUnused for years but I had a feeling that this was no longer needed as it was most likely addressing to older PCs and their ACPI tables, with device names that no longer exist in modern PCs (last 5-6 years at least).

So thanks for confirming that DeleteUnused=TRUE key is no longer needed on my hacks!

Edited by MacKonsti
Slice
Slice
Posted
Posted
1 hour ago, MacKonsti said:

 

Hi @Slice thank you for your valuable input on the deeper features of Clover.

As mentioned in my earlier post, I am in the process of updating the guides in my hack repo and wanted to ask you, since you have access and understanding of Clover code.

I have been using DeleteUnused for years but I had a feeling that this was no longer needed as it was most likely addressing to older PCs and their ACPI tables, with device names that no longer exist in modern PCs (last 5-6 years at least).

So thanks for confirming that DeleteUnused=TRUE key is no longer needed on my hacks!

In the past, on very old PC this patch was very useful to switch from black screen to working system.

  • Thanks 1
Slice
Slice
Posted
Posted
19 hours ago, jsl2000 said:

Thanks again !

The same problem remained without any BIOS overclock.

Two debug logs are attached:

The first one when "O" was entered and crashed with red screen errors showing.

The second one after successful booting of Big Sur 11.3 beta.

2021-2-27_9-35-20_CLOVERX64.EFI.log 10.65 kB · 1 download 2021-2-27_9-36-14_CLOVERX64.EFI.log 89.97 kB · 1 download

Install OpenRuntime.efi.

 

@Jief_Machak

See. For legacy boot we lived without AptioMemoryFix and all was good.

Then we switch to OpenRuntime that does almost same functions switched on-off by Quirks.

Then we switch to Clover+OC and now legacy boot can't works without OpenRuntime. Red Screen panic. Why?

The problem seems related to ConsoleGop?

jsl2000
jsl2000
Posted
Posted (edited)
3 hours ago, Slice said:

Install OpenRuntime.efi.

 

@Jief_Machak

See. For legacy boot we lived without AptioMemoryFix and all was good.

Then we switch to OpenRuntime that does almost same functions switched on-off by Quirks.

Then we switch to Clover+OC and now legacy boot can't works without OpenRuntime. Red Screen panic. Why?

The problem seems related to ConsoleGop?

Thanks.

But install OpenRuntime.efi in EFI/CLOVER/drivers/BIOS still got the same crash if "O" was selected during booting.

I guess there's something incompatibility in BOOTX64.efi after Clover + OC integration because it occurred before in AMD CPU hackintoshs with older Clover too.

Edited by jsl2000
Slice
Slice
Posted
Posted
2 hours ago, jsl2000 said:

Thanks.

But install OpenRuntime.efi in EFI/CLOVER/drivers/BIOS still got the same crash if "O" was selected during booting.

I guess there's something incompatibility in BOOTX64.efi after Clover + OC integration because it occurred before in AMD CPU hackintoshs with older Clover too.

If there is legacy boot then BOOTX64.EFI is unused.

The chain is follow

BIOS-> MBR-> PBR-> boot (for example boot6)-> CLOVERX64.efi

because boot6 directly calls /EFI/CLOVER/CLOVERX64.EFI

 

AMD CPU is very different story.

  • Like 1
Slice
Slice
Posted
Posted

The problem is follow:

When we start legacy Clover without OpenRuntime then start system by timeout then Clover crashed.

Снимок экрана 2021-02-28 в 19.24.14.png

It happen with Clover 5129+ but not with 5128.

 

The I made git bisection. Yes. There is the result 

iMac2017:CloverBootloader sergey$ git bisect bad
16c627596faff40d2d3b91d308aeeb4e16b18575 is the first bad commit
commit 16c627596faff40d2d3b91d308aeeb4e16b18575
Author: jief666 <github.com@jfa.knudsen.ovh>
Date:   Sun Jan 31 12:50:23 2021 +0300

    Rename OSVersion to macOSVersion.
    Fixed some icons ordering in main menu.
    Fixed macOs version detection for custom entries.
    Fixed main Big Sur partition appearing in menu.
    Refactor IsValidGuidAsciiString.

:160000 160000 620e4378f9a3d0558c144936e3fc5affbf445e44 78708c2edcfb358a6577f92a6afda1f99f2f48a0 M	OpenCorePkg
:040000 040000 faff6df313e126409cd11edce0266cebd289c994 c2827fd686b8bf596529a0b55d7cde26121d5b4a M	Xcode
:040000 040000 20082b1202448709b95f0a2f0ff1372da8a22e4a 405dacb7b36f725cc2b6c6368a7125e22bb1bde9 M	rEFIt_UEFI
iMac2017:CloverBootloader sergey$

During the bisection OpenCore subproject remained unchanged while the crash inside it between messages 

7:725  0:000  OCST: Missing vault data, ignoring...
7:768  0:043  config-oc.plist isn't use at all

 

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...