Clover General discussion

Micky1979 · November 3, 2016

:hysterical: , sorry, damaged volumes cannot be mounted..

I've just made this test script (attached) to simulate how Clover mounts the ESPs by selecting a volume, like one do when run the installer.

(the script only work inside its folder that contains partutil + the clover's MountESP script modded to show some info)

MountESP.zip

pkdesign · November 3, 2016

@ pkdesign

If PatchVBios isn´t working automaticly you can have a look on your vbios, find the correct entry and patch it on the fly via the key PatchVBiosBytes.

I believe i have edited my VBIOS corrected and added 1920x1080. I used this method: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/

I found two entries that had 1280x1024 and edited both to be 1920x1080. (see attached VBIOS) I then placed that file in /EFI/CLOVER/ROM/10DE_1380.rom

1) I then entered a Screen Resolution of 1920x1080 in GUI of Clover.

2) Inject Custom EDID

3) Load VBios

4) Patch VBios

I also tried booting without Patch Vbios.

Unless I've done something wrong, I still do not have full resolution at Clover boot.

prebootlog.txt

10DE_1380.rom.zip

arsradu · November 3, 2016

, sorry, damaged volumes cannot be mounted..

I've just made this test script (attached) to simulate how Clover mounts the ESPs by selecting a volume, like one do when run the installer

Micky, damaged volumes cannot be mounted. True, but then how does 3882 get installed? This is what I don't understand.

Micky1979 · November 3, 2016

Micky, damaged volumes cannot be mounted. True, but then how does 3882 get installed? This is what I don't understand.

Where? on the damaged Volume? ... I don't think so!

arsradu · November 3, 2016

Where? on the damaged Volume? ... I don't think so!

Hmm... Apparently 3882 doesn't even try to mount EFI. It installed on the root of the system directory. That's why it also didn't show any errors.

3882 log attached.

How did the EFI partition get damaged? Could it be because of the encryption? I can't think of anything else that could damage it.

Clover_Install_Log.txt

Fljagd · November 3, 2016

, sorry, damaged volumes cannot be mounted..

I've just made this test script (attached) to simulate how Clover mounts the ESPs by selecting a volume, like one do when run the installer.

(the script only work inside its folder that contains partutil + the clover's MountESP script modded to show some info)

strange

if I mount EFI before

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/El Capitan

2) /Volumes/Stockage 4) /Volumes/Time Machine

#? 1

realDisk =

UUID =

DiskDevice = disk0

disk0 is already mounted on /Volumes/EFI

disk0 is now succesfully mounted on /Volumes/EFI

If EFI isn't mount

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/El Capitan

2) /Volumes/Stockage 4) /Volumes/Time Machine

#? 1

realDisk =

UUID =

DiskDevice = disk0

fstype of disk0s1 is msdos

mkdir: /Volumes/ESP: Permission denied

mount: realpath /Volumes/ESP: No such file or directory

ERROR: can't mount ESP partition (disk0s1) !

Check that the partition is well formated in HFS or Fat32.

To format as HFS use command like:

sudo newfs_hfs -v EFI /dev/rdisk0s1

For format as Fat32 use command like:

sudo newfs_msdos -v EFI -F 32 /dev/rdisk0s1

Micky1979 · November 3, 2016

Yes sorry, use sudo to run the script..

Fljagd · November 3, 2016

Yes sorry, use sudo to run the script..

right :yes:

Last login: Thu Nov 3 22:00:24 on ttys000

Mac-Pro-de-Fljagd:~ fljagd$ sudo /Users/fljagd/Downloads/MountESP/pressMe.command

Password:

Sorry, try again.

Password:

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/El Capitan

2) /Volumes/Stockage 4) /Volumes/Time Machine

#? 1

realDisk =

UUID =

DiskDevice = disk0

fstype of disk0s1 is msdos

disk0 is now succesfully mounted on /Volumes/ESP

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/El Capitan

2) /Volumes/Stockage 4) /Volumes/Time Machine

#?

Riley Freeman · November 3, 2016

I found two entries that had 1280x1024 and edited both to be 1920x1080. (see attached VBIOS) I then placed that file in /EFI/CLOVER/ROM/10DE_1380.rom

I did this a long time back on my GT210 before I was able to just add a UEFI ROM to it. I had full (for me) 1680x1050 on boot. My memory is hazy about how I did it, but there were 4 entries that I had to change. I kept a note of the strings to replace but not the other steps as I got those from a post on projectosx. Unfortunately, that site is dead now, but the thread you linked might have most of the same info.

Here's the strings I had to replace. Maybe it'll be some help.

replace:

12 CD 9F 9F 91 A9 1A 3A 21 1F 1F 3B 44 FE C0 00 01 (1280x800)

with

12 15 D1 D1 99 E0 17 3D 1B 19 19 3E 0E 00 01 24 13 (1680x1050)

replace:

00 05 20 03 A0 31 10 23 07 (1280x800)

with

90 06 1A 04 D2 41 10 25 05 (1680x1050)

replace:

60 02 18 60 01 06 01 08 A0 00 FF FF 20 (1280x800x8)

with

68 01 18 68 01 08 01 08 48 03 FF FF 20 (1680x1050x8)

replace:

61 01 18 61 01 08 01 20 80 02 FF FF 20 (1280x800x32)

with

69 01 18 69 01 08 01 20 48 03 FF FF 20 (1680x1050x32)

Micky1979 · November 3, 2016

@asradu, you should try my script above (with sudo) and post the output after selecting a physical volume and then a logical volume..

magnifico · November 3, 2016

@ Sergey

There is something that does not convince me with clover on the Z97, I'll explain: when I turn off the PC, as soon as you turn off by itself, it does so even with El , there something that corrupts clover NVRAM? He does this only with Sierra, Yosemite while no

Let me know what can be

Carmine

Ps Where is on repo old version clover ? I don't see 36××( 3577 to 3811 mhmmm )

@ Sergey I have solved, with a bit of logic and reasoning

I'm sorry about earlier, mine was only a hypothesis ..but then thinking I solved

Forgive me , i have a red wine for you

arsradu · November 3, 2016

@asradu, you should try my script above (with sudo) and post the output after selecting a physical volume and then a logical volume..

Ok, Micky. Will try it and come back with fresh information.

wastez · November 3, 2016

I believe i have edited my VBIOS corrected and added 1920x1080. I used this method: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/

I found two entries that had 1280x1024 and edited both to be 1920x1080. (see attached VBIOS) I then placed that file in /EFI/CLOVER/ROM/10DE_1380.rom

1) I then entered a Screen Resolution of 1920x1080 in GUI of Clover.

2) Inject Custom EDID

3) Load VBios

4) Patch VBios

I also tried booting without Patch Vbios.

Unless I've done something wrong, I still do not have full resolution at Clover boot.

That is only working if you flash the vbios on the graphicscard.

But as i said clover can do that for you.

Use PatchVBiosBytes and do the same like on the Rom.

Find: The bytes from the 1280x1024

Replace: The bytes from 1920x1080

Ramalama · November 3, 2016

@Slice

Can you explain what EFILoginHiDPI is?

Thx :-)

Slice · November 4, 2016

I believe i have edited my VBIOS corrected and added 1920x1080. I used this method: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/

I found two entries that had 1280x1024 and edited both to be 1920x1080. (see attached VBIOS) I then placed that file in /EFI/CLOVER/ROM/10DE_1380.rom

1) I then entered a Screen Resolution of 1920x1080 in GUI of Clover.

2) Inject Custom EDID

3) Load VBios

4) Patch VBios

I also tried booting without Patch Vbios.

Unless I've done something wrong, I still do not have full resolution at Clover boot.

I see preboot.log

1:850  0:000  EdidOverrideFound!
1:850  0:000   found Detail Timing 2560x1440
1:914  0:064     0 640x480 attr=3BF - ok, edid+, 640x480, working, highest, pref=0
1:916  0:002     1 800x600 attr=3BF - ok, edid+, 800x600, working, highest, pref=1
1:918  0:002     2 1024x768 attr=3BF - ok, edid+, 1024x768, working, highest, pref=2
1:921  0:002     3 1280x1024 attr=3BF - ok, edid+, working, highest, pref=3
1:931  0:010  BV new mode: 3 1280x1024
2:160  0:228   SetMode pref 3 (3) = Success
2:503  0:343  === [ InitScreen ] ========================================
2:503  0:000  SetScreenResolution: 1920x1080 - not found!

The customEDID doesn't contain 1920x1080.

arimuras · November 4, 2016

With Clover r3900, Boot UEFI Mode

Previous OS Version "El Capitan 10.11.6", "Sierra 10.12"

To Hibernate mode to operate properly, run this in Terminal:

"sudo pmset -a hibernatemode 25"

It works

But "Sierra 10.12.1"

Dont wake up

It is a log of when I started to reset

-----boot.log (Only Target Partition)

3:012 0:016 - [14]: 'Sierra 10_12_1 HD'

3:051 0:039          AddLoaderEntry for Volume Name=Sierra 10_12_1 HD

3:067 0:015      Check if volume Is Hibernated:

3:067 0:000      Check sleep image 'by signature':

3:137 0:069      read prefs \Library\Preferences\com.apple.PowerManagement.plist status=Success

3:137 0:000      using default sleep image name = \private\var\vm\sleepimage

3:151 0:014      Reading first 512 bytes of sleepimage ...

3:160 0:009      OurBlockIoRead: Lba=30272720, Offset=604E4E4000 (BlockSize=512)

3:160 0:000      sig lion: 73696D65

3:160 0:000      sig snow: 0

3:160 0:000      got sleep image offset

3:160 0:000      Reading completed -> Success

3:160 0:000       sleepimage offset acquired successfully: 604E4E4000

3:160 0:000       gSleepTime: 1478121423

3:173 0:012       HFS+ volume modifyDate: 1478121422

3:173 0:000       image older then volume: -1 sec

3:173 0:000      hibernated: yes

3:173 0:000      UEFI with NVRAM: Boot0082 no

-----

What does it mean "UEFI with NVRAM: Boot0082 no" ?

With Clover r3905, Boot UEFI Mode

The test many times has attempted.

"Sierra 10.12" - terminal operation

-----

Last login: Fri Nov 4 15:55:34 on console

sierraReferenceHD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 15:55 /var/vm/sleepimage

sierraReferenceHD:~ arimuras$ pmset sleepnow

Sleeping now... ( power off, then I do power on → "hibernate wake OK")

sierraReferenceHD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 15:59 /var/vm/sleepimage

-----

File "sleepimage" is modified

"Sierra 10.12.1" - terminal operation

-----

Last login: Fri Nov 4 16:12:41 on console

sierra10-12-1HD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 16:08 /var/vm/sleepimage

sierra10-12-1HD:~ arimuras$ pmset sleepnow

Sleeping now... ( power off, then I do power on → but "hibernate not wake" then reset power on)

sierra10-12-1HD:~ arimuras$

[Restored 2016 Nov 4 16:17:39]

Last login: Fri Nov 4 16:17:18 on console

sierra10-12-1HD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 16:08 /var/vm/sleepimage

-----

File "sleepimage" is not modified

What does it mean?

arsradu · November 4, 2016

Micky, I tried your script again.

Please, see the results below.

For phisical volume

realDisk = 
UUID = 
DiskDevice = disk3
fstype of disk3s1 is msdos
disk3 is now succesfully mounted on /Volumes/ESP

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/SierraHDD 5) /Volumes/Untitled
2) /Volumes/Mail Mac 4) /Volumes/Storage 6) /Volumes/Untitled 1
#?

For logical volume

disk2 is a logical volume
realDisk = disk0s2
UUID = 95415CE1-023D-4894-89A1-FCE6BA524194
DiskDevice = disk0
fstype of disk0s1 is 

ERROR: can't mount ESP partition (disk0s1) !
Check that the partition is well formated in HFS or Fat32.

To format as HFS use command like:
sudo newfs_hfs -v EFI /dev/rdisk0s1

For format as Fat32 use command like:
sudo newfs_msdos -v EFI -F 32 /dev/rdisk0s1

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/SierraHDD 5) /Volumes/Untitled
2) /Volumes/Mail Mac 4) /Volumes/Storage 6) /Volumes/Untitled 1

Slice · November 4, 2016

@arimuras

Show reboot.log or output from bdmesg. There will be a reason why no hibernate.

arimuras · November 4, 2016

@arimuras

Show reboot.log or output from bdmesg. There will be a reason why no hibernate.

Thanks for reply!

Again,

"Sierra 10.12.1" - terminal operation

-----

Last login: Fri Nov 4 18:18:27 on ttys000

sierra10-12-1HD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 16:08 /var/vm/sleepimage

sierra10-12-1HD:~ arimuras$ pmset sleepnow

Sleeping now...

sierra10-12-1HD:~ arimuras$

[Restored 2016 Nov 4 18:23:00]

Last login: Fri Nov 4 18:22:37 on console

sierra10-12-1HD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 16:08 /var/vm/sleepimage

sierra10-12-1HD:~ arimuras$ bdmesg > output_bdmesg_Sierra_10_12_1_HD.txt

-----

attach bdmesg message (target portion "Sierra 10_12_1 HD")

output_bdmesg_Sierra_10_12_1_HD.txt.zip

Slice · November 4, 2016

Thanks for reply!

Again,

"Sierra 10.12.1" - terminal operation

-----

Last login: Fri Nov 4 18:18:27 on ttys000

sierra10-12-1HD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 16:08 /var/vm/sleepimage

sierra10-12-1HD:~ arimuras$ pmset sleepnow

Sleeping now...

sierra10-12-1HD:~ arimuras$

[Restored 2016 Nov 4 18:23:00]

Last login: Fri Nov 4 18:22:37 on console

sierra10-12-1HD:~ arimuras$ ls -lh /var/vm/sleepimage

-rw------T 1 root wheel 4.0G Nov 4 16:08 /var/vm/sleepimage

sierra10-12-1HD:~ arimuras$ bdmesg > output_bdmesg_Sierra_10_12_1_HD.txt

-----

attach bdmesg message (target portion "Sierra 10_12_1 HD")

Well, you have no hardware NVRAM (UEFI with NVRAM: Boot0082 no) so you have to use legacy hibernation mode 29.

But AFAIK it no more works in 10.12.1.

arimuras · November 4, 2016

Well, you have no hardware NVRAM (UEFI with NVRAM: Boot0082 no) so you have to use legacy hibernation mode 29.

But AFAIK it no more works in 10.12.1.

Thanks for reply!

My hardware "MSI H87-G41 PC Mate" Bios 3.9

Perhaps it is not possible to use the "Sleep" for "Unsynchronised TSC after wake/reboot after wake", it has been using the "Hibernate" until now.

However, in "Sierra 10.12.1", is a pity that "Hibernate" is also no longer available.

pkdesign · November 4, 2016

That is only working if you flash the vbios on the graphicscard.

But as i said clover can do that for you.

Use PatchVBiosBytes and do the same like on the Rom.

Find: The bytes from the 1280x1024

Replace: The bytes from 1920x1080

It was my understanding that Clover can load a VBIOS from a file located at EFI/CLOVER/ROM and that I didn’t have to actually flash the card.

Am I wrong anyone?

I will try patching with the entire string that I found and see what happens.

EDIT:

Okay, according to AnalyzeVBIOS:

Found 1. possible NVIDIA Mode at 0x4985(Decimal:18821)

Empty Table at 0x4aa5(Decimal:19109)

Empty Table at 0x4b25(Decimal:19237)

Empty Table at 0x4b65(Decimal:19301)

So I tried patching using the following:

0005FF040000FF042F059F0597060004FF030000FF0300040304290400FF302A

8007FF040000FF042F059F0597063804FF030000FF0300040304290400FF302A

This exact string is found twice so I patched both.

Still nothing.

Do I check both "Load" and "Patch" VBIOS?

I see preboot.log

1:850  0:000  EdidOverrideFound!
1:850  0:000   found Detail Timing 2560x1440
1:914  0:064     0 640x480 attr=3BF - ok, edid+, 640x480, working, highest, pref=0
1:916  0:002     1 800x600 attr=3BF - ok, edid+, 800x600, working, highest, pref=1
1:918  0:002     2 1024x768 attr=3BF - ok, edid+, 1024x768, working, highest, pref=2
1:921  0:002     3 1280x1024 attr=3BF - ok, edid+, working, highest, pref=3
1:931  0:010  BV new mode: 3 1280x1024
2:160  0:228   SetMode pref 3 (3) = Success
2:503  0:343  === [ InitScreen ] ========================================
2:503  0:000  SetScreenResolution: 1920x1080 - not found!

The customEDID doesn't contain 1920x1080.

You have mentioned this before but when I open the EDID in AW-EDID Editor the standard timings for those resolutions are there. Or am I not understanding it correctly. (see attached).

DELL.bin.zip

EDID.txt

prebootlog.rtf

Micky1979 · November 4, 2016

Micky, I tried your script again.

Please, see the results below.

For phisical volume

realDisk = 
UUID = 
DiskDevice = disk3
fstype of disk3s1 is msdos
disk3 is now succesfully mounted on /Volumes/ESP

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/SierraHDD 5) /Volumes/Untitled
2) /Volumes/Mail Mac 4) /Volumes/Storage 6) /Volumes/Untitled 1
#?

For logical volume

disk2 is a logical volume
realDisk = disk0s2
UUID = 95415CE1-023D-4894-89A1-FCE6BA524194
DiskDevice = disk0
fstype of disk0s1 is 

ERROR: can't mount ESP partition (disk0s1) !
Check that the partition is well formated in HFS or Fat32.

To format as HFS use command like:
sudo newfs_hfs -v EFI /dev/rdisk0s1

For format as Fat32 use command like:
sudo newfs_msdos -v EFI -F 32 /dev/rdisk0s1

select a volume to simulate Clover MountESP script

1) / 3) /Volumes/SierraHDD 5) /Volumes/Untitled
2) /Volumes/Mail Mac 4) /Volumes/Storage 6) /Volumes/Untitled 1

Thanks. If you look at the logical one, the partutil command also fails to find the filesystem type returning nothing:

fstype of disk0s1 is

Now or your ESP is really corrupted, or has no filesystem. To ensure that run 'diskutil info disk0s1' hoping in some sane status. Why that happens is for me unknown, but something tells me that happened during the conversion to a logical/encrypted volume (assuming this was the only time that you played with your disk..).

Rest the doubt on why Clover installer continue installing to the target volume if you have selected 'install to the ESP...'. for me should go to fail, and with more detailed infos

arsradu · November 4, 2016

Now or your ESP is really corrupted, or has no filesystem. To ensure that run 'diskutil info disk0s1' hoping in some sane status. Why that happens is for me unknown, but something tells me that happened during the conversion to a logical/encrypted volume (assuming this was the only time that you played with your disk..).

Rest the doubt on why Clover installer continue installing to the target volume if you have selected 'install to the ESP...'. for me should go to fail, and with more detailed infos

Hi Micky!

Please, see below the result for the diskutil info command:

diskutil info disk0s1
   Device Identifier:        disk0s1
   Device Node:              /dev/disk0s1
   Whole:                    No
   Part of Whole:            disk0

   Volume Name:              Not applicable (no file system)
   Mounted:                  Not applicable (no file system)
   File System:              None

   Partition Type:           EFI
   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 SATA
   SMART Status:             Verified
   Disk / Partition UUID:    146925A5-70AC-4D17-8AF0-D2D7B264BEDF

   Disk Size:                204.5 MB (204492800 Bytes) (exactly 399400 512-Byte-Units)
   Device Block Size:        512 Bytes

   Read-Only Media:          No
   Read-Only Volume:         Not applicable (no file system)

   Device Location:          Internal
   Removable Media:          Fixed

   Solid State:              Yes

And yes, 3882 is set to install to the ESP, and it goes to the system partition instead.

Micky1979 · November 4, 2016

It's strange also that your ESP is only 204,5 MB (though min size allowed is 100 MB) while usually is 209,7 MB if created in OS X .

If you have backup you can run:

sudo newfs_msdos -v EFI -F 32 /dev/rdisk0s1

and anyway what was in it is lost, I think.

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites