Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted

For NVIDIA cards, I'm not sure... I don't think there is any.

 

A few pages back, Slice mentioned something about a specific identifier for ATI cards. And how, based on that information, you can determine if your card has a UEFI VBIOS or not... Now, in our cases, this does not help, since we have Nvidia cards. So no, I don't know another way.

 

By the way, I've got a question for everyone here (it might be only in the final release of Clover, didn't pay attention to it before, it might be an older change that caused this), but was this always a thing for Clover to make a zip of CLOVERX64.efi inside the CLOVER folder? :))

 

Just curious. Doesn't seem to affect the functionality in anyway. And the update from 4114 to 4128 went without any issues (I'm on r4128 now). Just seemed a bit strange. And I was wondering whether or not it's intended. And if it is, what's the reason for this archive.

 

attachicon.gifScreen Shot 2017-07-28 at 5.04.21 PM.png

 

No zip file here with r4128 or lower version.

arsradu
arsradu
Posted
Posted

No zip file here with r4128 or lower version.

 

I'll check at home, as well... Maybe it's only for Skylake systems....? God knows. As I said, it doesn't affect anything. I could simply delete it and everything would be fine. But I was curious...

 

Anyway, I'll check again when I get home (with the build in my signature) and update you guys on the matter. Nothing to worry about. Just my curiosity.

 

I just tried to install it from scratch (build 4128) on an EFI partition where I didn't have it before (well, it was, but I removed it), and it still created that zip. I guess it could be for backup purposes...? But that's why I thought I would ask you guys. Maybe you know something.

Wppley2
Wppley2
Posted
Posted

I'll check at home, as well... Maybe it's only for Skylake systems....? God knows. As I said, it doesn't affect anything. I could simply delete it and everything would be fine. But I was curious...

 

Anyway, I'll check again when I get home (with the build in my signature) and update you guys on the matter. Nothing to worry about. Just my curiosity.

 

I just tried to install it from scratch (build 4128) on an EFI partition where I didn't have it before (well, it was, but I removed it), and it still created that zip. I guess it could be for backup purposes...? But that's why I thought I would ask you guys. Maybe you know something.

arsradu, thanks for response. I'm having the .zip file too.

Cyberdevs
Cyberdevs
Posted
Posted

For NVIDIA cards, I'm not sure... I don't think there is any.

 

A few pages back, Slice mentioned something about a specific identifier for ATI cards. And how, based on that information, you can determine if your card has a UEFI VBIOS or not... Now, in our cases, this does not help, since we have Nvidia cards. So no, I don't know another way.

 

By the way, I've got a question for everyone here (it might be only in the latest release of Clover, didn't pay attention to it before, it might be an older change that caused this), but was this always a thing for Clover to make a zip of CLOVERX64.efi inside the CLOVER folder? :))

 

Just curious. Doesn't seem to affect the functionality in anyway. And the update from 4114 to 4128 went without any issues (I'm on r4128 now). Just seemed a bit strange. And I was wondering whether or not it's intended. And if it is, what's the reason for this archive.

 

attachicon.gifScreen Shot 2017-07-28 at 5.04.21 PM.png

There's nothing here either. Clover r4128. I have never noticed any zip file in my clover folder.

bronxteck
bronxteck
Posted
Posted

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/?p=2470241. the zipped CLOVERx86.efi should not affect anything it was just something slice left when he compiled the clover package on source forge repo. if you compiled clover on your own it will not have it.

oSxFr33k
oSxFr33k
Posted
Posted

Thanks everybody. Unfortunately my boot is too fast on SSD hfs partition beta 4 (17A315i) clover 4128 to tell you if there are (and what kind) errors. W-Fi network starts immediately and monitor preferences appears an main bar.

 

The only way I can get a snapshot of the kernel verbose boot is to use the new camera feature rapid shot on the latest iPhones may have been able to do this in iPhone 5 not sure but should be able to do this on iPhone 6 and 7.  It can take up to 200 frames, I look through them and save the ones that pickup anything unusual. You can almost see it even it if boots fast but no way you will know what the error is unless you can catch it with a photo snapshot.

arsradu
arsradu
Posted
Posted

Looks like I've got the archived CLOVERX64.efi at home, as well. :)) Interestingly enough, not everyone does. So maybe someone knows when is that archive created. Maybe this could lead to an answer as to why it was created.


 

That is sick!

 

  • Like 3
Cyberdevs
Cyberdevs
Posted
Posted

Uhm, how cool is this: https://github.com/vit9696/WhateverGreen

 

Does that finally fix the AMD wakeup problem and maybe should be integrated into clover?

Yes it does :):yes:

@Funky frank

Take look at this

  • Like 1
artur_pt
artur_pt
Posted
Posted

For NVIDIA cards, I'm not sure... I don't think there is any.

 

A few pages back, Slice mentioned something about a specific identifier for ATI cards. And how, based on that information, you can determine if your card has a UEFI VBIOS or not... Now, in our cases, this does not help, since we have Nvidia cards. So no, I don't know another way.

 

By the way, I've got a question for everyone here (it might be only in the latest release of Clover, didn't pay attention to it before, it might be an older change that caused this), but was this always a thing for Clover to make a zip of CLOVERX64.efi inside the CLOVER folder? :))

 

Just curious. Doesn't seem to affect the functionality in anyway. And the update from 4114 to 4128 went without any issues (I'm on r4128 now). Just seemed a bit strange. And I was wondering whether or not it's intended. And if it is, what's the reason for this archive.

 

attachicon.gifScreen Shot 2017-07-28 at 5.04.21 PM.png

 

hello

 

clover 4128

 

already have the zip file in efi folder from the clover installer pkg

 

see that with pacifist

 

maybe slice create that in this src .. only the one download from source forge .. the one I compile don't have that zip file

 

good hack

  • Like 3
nmano
nmano
Posted
Posted

Can I know how to fix unknown CPU 

 

I try with clover type 2561 not work

post-413859-0-86413500-1501289151_thumb.png

post-413859-0-64231300-1501289158_thumb.png

apianti
apianti
Posted
Posted

For everyone wondering, there is no zipping of anything in the build script. What happened was that slice zipped up a clover binary in the build output folder for someone for some thing, I can't remember where/when (obviously recent) but if you look I'm sure you will find it. He then didn't remove the zip from the output of the build so when he built the next time it was still there and accidentally included in the package.

 

@xtddd,

 

nmano has a HASWELL-E so it should be cool with some minor patching. What CPU do you have? Usually the MacPro models are the worst ones to attempt use.


Thanks everybody. Unfortunately my boot is too fast on SSD hfs partition beta 4 (17A315i) clover 4128 to tell you if there are (and what kind) errors. W-Fi network starts immediately and monitor preferences appears an main bar.

 

Do these errors not appear in the Console.app system log??? Or can you not boot into system?


The only way I can get a snapshot of the kernel verbose boot is to use the new camera feature rapid shot on the latest iPhones may have been able to do this in iPhone 5 not sure but should be able to do this on iPhone 6 and 7.  It can take up to 200 frames, I look through them and save the ones that pickup anything unusual. You can almost see it even it if boots fast but no way you will know what the error is unless you can catch it with a photo snapshot.

 

Is this stuff not in the log???

  • Like 1
maxodoble
maxodoble
Posted
Posted

Clover Linux Boot: Kernel Panic

 

I can't boot my Arch Linux Installation any more with Clover, getting a kernel Panic.

 

When starting via Linux Boot Manager (systemd-boot) the system is starting up correctly.

Starting via Clover: Kernel Panic

 

Any idea why this is happening suddenly?

 

To verify, today i installed a completely new Arch Linux minimal System, and i am getting the same problem:

 

* Boot with Clover: Linux kernel Panic

* Boot with Linux Boot Manager: system boots normally up and is running.

 

Mac and Win are booting o.k with Clover.

 

Using the latest Clover Version from Sourceforge.

 

Am attaching my config.plist and the systemd-boot loader configuration

 

Please let me know, if other infos/files are needed!

 

Thanks,

 

Max

config.plist.zip

loader.zip

SavageAUS
SavageAUS
Posted
Posted

Clover Linux Boot: Kernel Panic

 

I can't boot my Arch Linux Installation any more with Clover, getting a kernel Panic.

 

When starting via Linux Boot Manager (systemd-boot) the system is starting up correctly.

Starting via Clover: Kernel Panic

 

Any idea why this is happening suddenly?

 

To verify, today i installed a completely new Arch Linux minimal System, and i am getting the same problem:

 

* Boot with Clover: Linux kernel Panic

* Boot with Linux Boot Manager: system boots normally up and is running.

 

Mac and Win are booting o.k with Clover.

 

Using the latest Clover Version from Sourceforge.

 

Am attaching my config.plist and the systemd-boot loader configuration

 

Please let me know, if other infos/files are needed!

 

Thanks,

 

Max

Installing arch linux now to test will edit with comments.

sebinouse
sebinouse
Posted
Posted

I'm not sure if this is a clover issue, but I believe it might be:

El Capitan 2017-003 Security Update for 10.11.6 has caused issues booting on one of my machines (others are starting to report this issue too). For me, I get stuck at the OsxAptioFixDrv screen (before loading OS X). For others, it restarts in an infinite loop. For me it just hangs.

 

Would this have something to do with the Clover configuration? I was on r4061 and I updated to the latest stable, still having those issues. Any help would be appreciated. Thanks.

 

I have the EXACT same behaviour.

 

I tried OsxAptioFixDrv.efi, OsxAptioFix2Drv.efi, Clover r4097 r4084 r3270.

There is already a ticket on sourceforge #381, but maybe someone here has an idea  :P

 

There seems to be a new kernel ... Is this the reason why ?

kernels.zip

Sherlocks
Sherlocks
Posted
Posted

I have the EXACT same behaviour.

 

I tried OsxAptioFixDrv.efi, OsxAptioFix2Drv.efi, Clover r4097 r4084 r3270.

There is already a ticket on sourceforge #381, but maybe someone here has an idea

 

There seems to be a new kernel ... Is this the reason why ?

I will check on my old laptop

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
SavageAUS
SavageAUS
Posted
Posted

Clover Linux Boot: Kernel Panic

 

I can't boot my Arch Linux Installation any more with Clover, getting a kernel Panic.

 

When starting via Linux Boot Manager (systemd-boot) the system is starting up correctly.

Starting via Clover: Kernel Panic

 

Any idea why this is happening suddenly?

 

To verify, today i installed a completely new Arch Linux minimal System, and i am getting the same problem:

 

* Boot with Clover: Linux kernel Panic

* Boot with Linux Boot Manager: system boots normally up and is running.

 

Mac and Win are booting o.k with Clover.

 

Using the latest Clover Version from Sourceforge.

 

Am attaching my config.plist and the systemd-boot loader configuration

 

Please let me know, if other infos/files are needed!

 

Thanks,

 

Max

Try this

<dict>
<key>AddArguments</key>
<string>root=UUID=4AF9AFB5-C9D1-4123-B3AF-4E6E36006706 rw add_efi_memmap initrd=/intel-ucode.img initrd=/initramfs-linux.img</string>
<key>Disabled</key>
<false/>
<key>FullTitle</key>
<string>Arch Linux</string>
<key>Ignore</key>
<false/>
<key>Image</key>
<string></string>
<key>Path</key>
<string>\EFI\systemd\systemd-bootx64.efi</string>
<key>Type</key>
<string>Linux</string>
<key>Volume</key>
<string>E4F6EC78-856B-4D46-AD8D-B466F5A54C8C</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
</plist>

Where 4AF9AFB5-C9D1-4123-B3AF-4E6E36006706 is, use your UUID

Where E4F6EC78-856B-4D46-AD8D-B466F5A54C8C is, use your EFI

  • Like 1
fatala
fatala
Posted
Posted

Hello. I am kindly asking for help with my Intel HD P4600 graphics card not working properly using Clover version beyond 4061. I am currently running Sierra 10.12.5 & Clover 4061 on a Lenovo TS140 / Intel C226 Chipset, CPU:Xeon E3-1225v3, Graphics: Intel HD P4600. My graphics card Intel HD P4600 has been running fine for two years with the following settings:

  1. FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext installed.
  2. Clover: Under "Devices>FakeID>IntelGFX" section, add 0x04128086.
  3. Clover: Under "Devices>Properties", "NoDefaultProperties" is selected.
  4. Clover: Under "Devices>Add Properties" section, the following is added:
    1. Devices: IntelGFX; Key: AAPL,ig-platform-id; Value: 0300220D; Value Type: DATA
  5. Clover: Under "Graphics>ig-platform-id", 0D220003 is used.
  6. Clover: Under "Graphics", "Inject Intel" is selected.

I am using a dual monitor setup (Full HD), connected to both DP ports. When I update Clover to any version beyond 4061, the IntelGFX injection stops working (the DeviceID which should be injected as 0x04128086 is not, and it is reverted back to the actual 0x041a8086). Incidentally, clover version 4064 updated Intel Injection (by Sherlock), which I am assuming might have introduced a bug. Users with the same hardware configuration as my system have experienced the same issue after upgrading to any Clover version beyond 4061. Please advise.

Sherlocks
Sherlocks
Posted
Posted

Hello. I am kindly asking for help with my Intel HD P4600 graphics card not working properly using Clover version beyond 4061. I am currently running Sierra 10.12.5 & Clover 4061 on a Lenovo TS140 / Intel C226 Chipset, CPU:Xeon E3-1225v3, Graphics: Intel HD P4600. My graphics card Intel HD P4600 has been running fine for two years with the following settings:

  • FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext installed.
  • Clover: Under "Devices>FakeID>IntelGFX" section, add 0x04128086.
  • Clover: Under "Devices>Properties", "NoDefaultProperties" is selected.
  • Clover: Under "Devices>Add Properties" section, the following is added:
    • Devices: IntelGFX; Key: AAPL,ig-platform-id; Value: 0300220D; Value Type: DATA
  • Clover: Under "Graphics>ig-platform-id", 0D220003 is used.
  • Clover: Under "Graphics", "Inject Intel" is selected.
I am using a dual monitor setup (Full HD), connected to both DP ports. When I update Clover to any version beyond 4061, the IntelGFX injection stops working (the DeviceID which should be injected as 0x04128086 is not, and it is reverted back to the actual 0x041a8086). Incidentally, clover version 4064 updated Intel Injection (by Sherlock), which I am assuming might have introduced a bug. Users with the same hardware configuration as my system have experienced the same issue after upgrading to any Clover version beyond 4061. Please advise.
please upload files each cases

Case1

Working; ioreg and clover full log

 

Case2

Not working; ioreg and clover full log

 

Not tested Some intel graphics(p4600)

But some haswell graphics(hd4400 hd4600) tested.

 

Lastet clover recorded your behavior exactly.

I can see your problem.

 

Now, no need to add platformid and fakeid on most of intel graphics. Haswell need fakepciid to fix glitches and something.

 

Code is no problem.

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
fatala
fatala
Posted
Posted

please upload files each cases

Case1

Working; ioreg and clover full log

 

Case2

Not working; ioreg and clover full log

 

Not tested Some intel graphics(p4600)

But some haswell graphics(hd4400 hd4600) tested.

 

Lastet clover recorded your behavior exactly.

I can see your problem.

 

Now, no need to add platformid and fakeid on most of intel graphics. Haswell need fakepciid to fix glitches and something.

 

Code is no problem.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Thank you for your help Sherlocks! I have attached the working case files. I will attach the non-working case files in the next post.

please upload files each cases

Case1

Working; ioreg and clover full log

 

Case2

Not working; ioreg and clover full log

 

Not tested Some intel graphics(p4600)

But some haswell graphics(hd4400 hd4600) tested.

 

Lastet clover recorded your behavior exactly.

I can see your problem.

 

Now, no need to add platformid and fakeid on most of intel graphics. Haswell need fakepciid to fix glitches and something.

 

Code is no problem.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Here are the non-working files. Thanks again!

Clover Working.zip

Clover not working.zip

  • Like 1
Sherlocks
Sherlocks
Posted
Posted

Thank you for your help Sherlocks! I have attached the working case files. I will attach the non-working case files in the next post.

Here are the non-working files. Thanks again!

 

clover full log please. you were forgot it

 

EDIT. this isn't clover bug. seems your setting is wrong.

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