Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

benww
benww
Posted
Posted

Do you think it should be else?

Sorry for not providing enough information here. (The link I provided has more information.)

 

The CPU (L3426) should be able to turbo boost to 3.2GHz (1 core), 3.06GHz (2 cores) and 2.13GHz (3 or 4 cores) according to this. And it can turbo boost correctly on Windows 10.

 

With ssdt generated by clover, it can only turbo boost to 2.13GHz. And I tried ssdtPRGen.sh, which can't turboboost at all.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Sorry for not providing enough information here. (The link I provided has more information.)

 

The CPU (L3426) should be able to turbo boost to 3.2GHz (1 core), 3.06GHz (2 cores) and 2.13GHz (3 or 4 cores) according to this. And it can turbo boost correctly on Windows 10.

 

With ssdt generated by clover, it can only turbo boost to 2.13GHz. And I tried ssdtPRGen.sh, which can't turboboost at all.

Yes, if using 4 cores, as OSX did, boost only to 2.13 as you have.

Link to comment
Share on other sites
benww
benww
Posted
Posted

Yes, if using 4 cores, as OSX did, boost only to 2.13 as you have.

You mean OSX won't turn off some cores if only one or two cores are heavily loaded, which turboboost was supposed to do?

 

But I found an example of an iMac which can turboboost up to 3.3GHz with only 1 core activated. See here (the specs of that iMac) and here (the specs of the CPU that iMac uses).

Link to comment
Share on other sites
Dr. Hurt
Dr. Hurt
Posted
Posted

Why does clover take longer than usual to scan loaders on NTFS and MSR partition?

 

1:762  0:000  Scanning loaders...

1:762  0:000   0: 'Whole Disc Boot' no file system

1:762  0:000   1: '' no file system

1:762  0:000   2: 'EFI'

1:807  0:044      AddLoaderEntry for Volume Name=EFI

1:830  0:023   3: 'Macintosh HD'

1:860  0:029      AddLoaderEntry for Volume Name=Macintosh HD

1:903  0:042      Check if volume Is Hibernated:

1:903  0:000      Check sleep image 'by signature':

1:975  0:071      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success

1:975  0:000      using default sleep image name = \private\var\vm\sleepimage

2:012  0:037      Reading first 512 bytes of sleepimage ...

2:028  0:015   OurBlockIoRead: Lba=1464080, Offset=28C810000 (BlockSize=512)

2:028  0:000   sig lion: 7A7A7A7A

2:028  0:000   sig snow: 0

2:028  0:000   no valid sleep image offset was found

2:028  0:000      Reading completed -> Success

2:028  0:000       sleepimage offset could not be acquired

2:028  0:000       hibernated: no - sign

2:041  0:012   4: 'Recovery HD'

2:055  0:013      AddLoaderEntry for Volume Name=Recovery HD

2:071  0:016   5: 'Data 1'

2:949  0:878   6: 'Legacy HD5' no file system

2:949  0:000   7: 'Data 2'

3:984  1:034   8: 'Legacy HD7' no file system

 

 

I know this seems like a silly question but it used to be faster.

Link to comment
Share on other sites
Zenith432
Zenith432
Posted
Posted

It is actually the scan of

5: Data 1

7: Data 2

that is taking a long time.  There is a recognizable filesystem on those partitions, and it's looking for at least 31 boot loaders (by superficial count) - if they exist.  (They do not).

So the question is...

What filesystem is on those partitions?

Which filesystem driver do you use for them?

 

BTW, it says partition 2 on this disk is "EFI", so why do you think it's MBR?  Looks like GPT.

 

Why does clover take longer than usual to scan loaders on NTFS and MSR partition?

 

 

I know this seems like a silly question but it used to be faster.

Link to comment
Share on other sites
Dr. Hurt
Dr. Hurt
Posted
Posted

It is actually the scan of

5: Data 1

7: Data 2

that is taking a long time.  There is a recognizable filesystem on those partitions, and it's looking for at least 31 boot loaders (by superficial count) - if they exist.  (They do not).

So the question is...

What filesystem is on those partitions?

Which filesystem driver do you use for them?

 

BTW, it says partition 2 on this disk is "EFI", so why do you think it's MBR?  Looks like GPT.

 

I said MSR (Microsoft Reserved Partition) not MBR.

 

Those 2 partitions are exfat. (Data 1 and Data 2)

The were created recently to replace 2 NTFS. So I guess the slow down happened after that. 

 

The only efi drivers I have are fsinject and hfsplus.

  • Like 1
Link to comment
Share on other sites
Zenith432
Zenith432
Posted
Posted

These are times I get...

 

Grub Exfat

SATA disk (MBR) 1:074

USB disk (MBR) 1:417

 

Grub NTFS

SATA disk (MBR)

0:961

0:943

0:944

SATA disk (GPT)

0:944

0:944

 

EDK2 Fat Driver

SATA disk (GPT) 0:926

USB disk (MBR) 0:926

 

VBox HFS

SATA disk (GPT)

0:926

1:118 on system partition

USB disk (MBR)

1:100 on system partition

 

So none is especially snappy.

 

Grub EXFAT is bundled into boot[367].  You can disable by

./ebuild.sh -D NO_GRUB_DRIVERS

 

 

I said MSR (Microsoft Reserved Partition) not MBR.

 

Those 2 partitions are exfat. (Data 1 and Data 2)

The were created recently to replace 2 NTFS. So I guess the slow down happened after that. 

 

The only efi drivers I have are fsinject and hfsplus.

  • Like 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

You mean OSX won't turn off some cores if only one or two cores are heavily loaded, which turboboost was supposed to do?

 

But I found an example of an iMac which can turboboost up to 3.3GHz with only 1 core activated. See here (the specs of that iMac) and here (the specs of the CPU that iMac uses).

It is just specifications, not a real life.

At boot time CPU works with one core but when mach_kernel started it switched on other cores by some set of LAPIC commands. 

I don't think these commands used somewhere else performing CPU PM. So I think OSX always works with 4 cores except initially started as cpus=1.

  • Like 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Is there a possibility for packing theme files into archives like tar or dmg or iso, and having Clover read them from packed instead of having them on filesystem as individual files?

Clover has a procedure LzmaUefiDecompress()  that can be used for this purpose.

  • Like 1
Link to comment
Share on other sites
giacomoleopardo
giacomoleopardo
Posted
Posted (edited)

Hi Slice.
I hope this wouldn't sound silly to you, but I have a doubt.
I've noticed that even if I delete completely the contents of EFI partition (where clover is installed), rebuilding the cache, rebooting from USB, the moment I install clover in the empty EFI partition, the installer recognize the old clover options. That means that somewhere clover has data that I didn't delete before. Is that right?

Edited by Micky1979
"Clover v2 Instruction" is not meant to be a discussion Topic, posts and answers moved here
Link to comment
Share on other sites
Ciro82
Ciro82
Posted
Posted (edited)

Hi Slice.

I hope this wouldn't sound silly to you, but I have a doubt.

I've noticed that even if I delete completely the contents of EFI partition (where clover is installed), rebuilding the cache, rebooting from USB, the moment I install clover in the empty EFI partition, the installer recognize the old clover options. That means that somewhere clover has data that I didn't delete before. Is that right?

 

Clover makes an EFI backup on your OS X main partition... 

Take a look, you will see the folder.

Edited by Micky1979
"Clover v2 Instruction" is not meant to be a discussion Topic, posts and answers moved here
Link to comment
Share on other sites
giacomoleopardo
giacomoleopardo
Posted
Posted (edited)

Clover makes an EFI backup on your OS X main partition... 

Take a look, you will see the folder.

Thanks for your reply, Ciro. As a matter of fact I deleted everything in EFI partition and the EFI-Backups folder in my main Volume. Then rebuilt permission, cache, cleared nvram etc... with

sudo nvram -c
sudo touch /System/Library/Extensions/
sudo touch /Library/Extensions
sudo chown -R root:wheel /System/Library/Extensions/
sudo chmod -R 755 /System/Library/Extensions/
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches
sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

then rebooted from USB pen drive and still, when I tried to install Clover on main partition, it gives me my previous options like this

post-799111-0-07477200-1464081497_thumb.png

(while on a new installation, same situation, booted from usb to get to the desktop, the install options are defaulted like this)

post-799111-0-50653600-1464081552_thumb.png

which leads me to think that somewhere else some clover stuff still remains.

Edited by Micky1979
"Clover v2 Instruction" is not meant to be a discussion Topic, posts and answers moved here
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)

Thanks for your reply, Ciro. As a matter of fact I deleted everything in EFI partition and the EFI-Backups folder in my main Volume. Then rebuilt permission, cache, cleared nvram etc... with

sudo nvram -c
sudo touch /System/Library/Extensions/
sudo touch /Library/Extensions
sudo chown -R root:wheel /System/Library/Extensions/
sudo chmod -R 755 /System/Library/Extensions/
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches
sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

then rebooted from USB pen drive and still, when I tried to install Clover on main partition, it gives me my previous options like this

attachicon.gif

(while on a new installation, same situation, booted from usb to get to the desktop, the install options are defaulted like this)

attachicon.gif

which leads me to think that somewhere else some clover stuff still remains.

Library/Preferances / com.projectosx.clover.installer.plist

:)

137.png

Edited by Micky1979
"Clover v2 Instruction" is not meant to be a discussion Topic, posts and answers moved here
Link to comment
Share on other sites
Mirone
Mirone
Posted
Posted

Sorry guys, not currently interested to redistribute that theme, besides i have no rights to do that, maybe someone... someday :wink_anim:

 

I agree with you so I create
one or two themes this weekend. :D
  • Like 2
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...