Clover General discussion

[Slice]

1 hour ago, kushwavez said:

In my case I need this kext for my notebook 1's Intel 100 series internal HDD, SSD. If I don't use this system doesn't recognise my drives and stall with AppleAHCIPort (or smth like that). Before Catalina it was SATA-100-series-unsupported.kext. it's simply injecting some pciids into AppleAHCI I think

100 series? As mine?

[Slice]

3 hours ago, Matgen84 said:

@Slice Remember that with latest commit, I also can't boot BS Preboot.

I can -vv-

Take this Clover 

CLOVERX64.efi.zip

[Matgen84]

21 minutes ago, Slice said:

I can -vv-

Take this Clover 

CLOVERX64.efi.zip

@Slice I can too.

Do you think, it's a bad compilation or a bad installation with previous one (same commit) ! Please, your opinion: theoretically with my Z390, it should be native? what is the best way to see "Intel 11 series SATA" instead of generic SATA. 

[iCanaro]

6 minutes ago, Matgen84 said:

theoretically with my Z390, it should be native? what is the best way to see "Intel 11 series SATA" instead of generic SATA. 

 

Z390 is "native" a bit shaky... gigabyte then... brrrrrrr I have the thrills  
I assume a good AHCI injector is enough

[iCanaro]

PS: i checked on big sur

 

[Matgen84]

16 minutes ago, iCanaro said:

PS: i checked on big sur

 

 

@iCanaro Thanks for your verification. I try this injector with my Aorus Master. But I'm a little be surprise to not found my 'pci8086,a352' for Z390. So the injector don't work for my mobo.

 

[Slice]

57 minutes ago, Matgen84 said:

@Slice I can too.

Do you think, it's a bad compilation or a bad installation with previous one (same commit) ! Please, your opinion: theoretically with my Z390, it should be native? what is the best way to see "Intel 11 series SATA" instead of generic SATA. 

I think a bad compilation. You probably didn't update linked OpenCore.

Why Generic AHCi is wrong? It works.

Under BigSur I see Generic AHCI

 

While my controller is known for BigSur AHCI kext

[iCanaro]

1 hour ago, Matgen84 said:

 

@iCanaro Thanks for your verification. I try this injector with my Aorus Master. But I'm a little be surprise to not found my 'pci8086,a352' for Z390. So the injector don't work for my mobo.

 

 

OK I added your IDs to the injector, if you tell me I'd be grateful archivio.zip

[Matgen84]

8 minutes ago, Slice said:

I think a bad compilation. You probably didn't update linked OpenCore.

Why Generic AHCi is wrong? It works.

Under BigSur I see Generic AHCI

@Slice I think so, it's a bad compilation despite I'm using Buildme script. Today or tomorrow, I will make a clean git clone to be safe.

My Z390 SATA is pci8086,a352: Intel 11 Series instead of generic, with kext injector or ssdt, is cosmetic of course. 

[Slice]

8 minutes ago, Matgen84 said:

@Slice I think so, it's a bad compilation despite I'm using Buildme script. Today or tomorrow, I will make a clean git clone to be safe.

My Z390 SATA is pci8086,a352: Intel 11 Series instead of generic, with kext injector or ssdt, is cosmetic of course. 

Yes, a352 is also known for the bigsur kext.

[Matgen84]

7 minutes ago, Slice said:

Yes, a352 is also known for the bigsur kext.

Big Sur know it but don't display 11 Series.

 

 

17 minutes ago, iCanaro said:

 

OK I added your IDs to the injector, if you tell me I'd be grateful archivio.zip

The new one display correctly the Intel chipset for my Z390.

 

[Slice]

As well for my 10 series chipset. But I am sure it is cosmetic. The same kext works the same manner. It is AboutMac.app shows wrong.

Vendor name = Generic

why?

 

[kushwavez]

@Slice Mine is 8086,a103. If I don't use CtlnaAHCIPort.kext the device is not recognisable and the system cannot boot. So what do you suggest instead of that kext?

[Matgen84]

9 minutes ago, Slice said:

As well for my 10 series chipset. But I am sure it is cosmetic. The same kext works the same manner. It is AboutMac.app shows wrong.

Vendor name = Generic

 

why?

 

 

I'm agree with you. It is just cosmetic. Thanks for your explanations 

It's a little bit strange : why vendor name is generic !

[Slice]

30 minutes ago, kushwavez said:

@Slice Mine is 8086,a103. If I don't use CtlnaAHCIPort.kext the device is not recognisable and the system cannot boot. So what do you suggest instead of that kext?

FakeID = 0xA1028086

or Properties

PciRoot(0x0)/Pci(0x17,0x0)

device-id  = <02 a1 00 00>

 

But I really don't understand why I have vendor=Generic. It seems Apple's AHCI controller has some mark it is Apple. And the kext CtlnaAHCIPort  ignores this mark.

[kushwavez]

Unfortunately FakeID doesn't work. "Waiting on boot-uuid-media" then after a while "Still waiting for root device"

 

EDIT:

1 hour ago, iCanaro said:

 

OK I added your IDs to the injector, if you tell me I'd be grateful archivio.zip

Unfortunately same with yours, even though I see my dev-id in the Info.plist.

 

Well, I'm good with CtlnaAHCIPort, but yes just a FakeID or smth like that would be nice option, less kexts are always better.  

 

 

Edited November 29, 2020 by kushwavez

[Alpha22]

for series 9, I use this kext no problem

 

 

 

[Matgen84]

17 minutes ago, kushwavez said:

Unfortunately FakeID doesn't work. "Waiting on boot-uuid-media" then after a while "Still waiting for root device"

 

EDIT:

Unfortunately same with yours, even though I see my dev-id in the Info.plist.

 

 

Well, I'm good with CtlnaAHCIPort, but yes just a FakeID or smth like that would be nice option, less kexts are always better.  

 

 

 

Do you try Item 3 instead of Item 0 for @iCanaro Kexts/Info.plist 

Edited November 29, 2020 by Matgen84

[kushwavez]

I'm pretty sure that the order doesn't matter, but sure I can try.

EDIT: yes, doesn't matter. Not working unfortunately.

Edited November 29, 2020 by kushwavez

[Jief_Machak]

Hi everyone.

I'd like help to identify a potential Clover bug.

If you have a bootable OC configuration (no need that everything is configured, just bootable), check that you can boot with quirks DevirtualiseMmio enabled, and nothing in MmioWhitelist. It's supposed to be ok from IvyBridge.

Then check the same quirks in Clover config.plist. For me, when this is enabled in Clover, there is a very early crash. And you ?

 

[kushwavez]

@Jief_Machak 

Notebook 1:

Clover v5127: DevirtualiseMmio enabled : halting at "HID: Legacy Shim 2" (very early, as you mentioned)

2020-11-29_20-14-32_CLOVERX64.efi.log

-> Disabling DevirtualiseMmio: booting OK

 

OpenCore 0.6.3: DevirtualiseMmio enabled: halting at exactly the same spot "HID: Legacy Shim 2"

opencore-2020-11-29-201458.txt

-> Disabling DevirtualiseMmio: booting OK

Edited November 29, 2020 by kushwavez

[Jief_Machak]

In your case, it seems to do the same. So that's ok. In my case, it doesn't...

Because Clover now use OC "kernel engine", a quirk is supposed to act the same.

Anyone else can test ?

@kushwavez : thanks for the test.

[PG7]

26 minutes ago, Jief_Machak said:

Hi everyone.

I'd like help to identify a potential Clover bug.

If you have a bootable OC configuration (no need that everything is configured, just bootable), check that you can boot with quirks DevirtualiseMmio enabled, and nothing in MmioWhitelist. It's supposed to be ok from IvyBridge.

Then check the same quirks in Clover config.plist. For me, when this is enabled in Clover, there is a very early crash. And you ?

 

I'm here with Ivybridge and I have both bootloaders ready.I'm here with Ivybridge and I have both bootloaders ready.

[PG7]

39 minutes ago, Jief_Machak said:

Hi everyone.

I'd like help to identify a potential Clover bug.

If you have a bootable OC configuration (no need that everything is configured, just bootable), check that you can boot with quirks DevirtualiseMmio enabled, and nothing in MmioWhitelist. It's supposed to be ok from IvyBridge.

Then check the same quirks in Clover config.plist. For me, when this is enabled in Clover, there is a very early crash. And you ?

 

 

 

Dell Latitude E6330
Ivybridge Intel i7-3520M
intel HD4000

tested here with OpenCore 0.6.3 and DevirtualiseMmio active = Crach

Clover r5127 with DevirtualiseMmio active = Crash

 

[iCanaro]

46 minutes ago, Jief_Machak said:

Then check the same quirks in Clover config.plist. For me, when this is enabled in Clover, there is a very early crash. And you ?

 

however, when you have Devirtualisemmio skills then depending on the platform, it is necessary to see if with all the MMIO active you work so the hack. On AMD platform it is better that you get them all and then add them in the list and check if 1 or more give problems. On AMD X570 (in mine I have 13 MMIO voices) and TRX40, this is very important.

For example, on my X570 if I have DevirtualiseMmio, then the hack no longer shuts down unless you turn off the power outlet 

 

PS: then another important thing, the MMIO voices could also change from one version of the BIOS to another, I always take my X570 example, at first I had 4 MMIO voices, then with new BIOS 13 and now that I have already flashed BIOS for ZEN3 I did not verify.... how many do I have? more, less, the same?

Edited November 29, 2020 by iCanaro