Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

Tried also to solve the long boot time (over 75 seconds!). Now that's a huge deal breaker, since I have to restart a lot. I can live without sleep or a perfect Apple boot logo, but if I fail to shorten this boot time, I'll have to go back to Chameleon... =/

Maybe here #4

Link to comment
Share on other sites

Hi at all...

A marvell Raid set with Win8.1 is not recognized in Mav 10.9.2 but ok in GUI... (with chameleon, no problem, in system specs marvell controller has been recognized)

Usb keyboard don't work in GUI, mouse ok...

Clover ver. 2652

any ideas?

 

thx, Luca

Link to comment
Share on other sites

Hi, Slice and thx for your reply.

Problem are two: i don't have usb-keyboard function in Clover-GUI, only mouse...

and Raid set of two disks under Marvell controller are not recognized after boot with clover by Mav 10.9.2...

What i've missed? a kext? Bad configuration of Clover? I used: Clover Configurator.app.

I hope... I've written clearly, sorry for my bad english...

 

Luca..

Link to comment
Share on other sites

dmesg > log.txt on wherever you're file directory (cd changes or modifies it)

 

It gets the boot log of the boot that currently happened

 

if you are booting an installer make sure you run the command mount -uw / beforehand

Link to comment
Share on other sites

 

Custom SMBios

SMBIOS part of config.plist may be as follow

<key>SMBIOS</key>
<dict>
  <key>FirmwareFeatures</key>
  <string>0xC001F537</string>
</dict>
Moreover, this key may be absent too.

Clover automatically detect the hardware and chooses the best values for SMBIOS by internal tables. It is enough.

It is quite enough for all hardware configurations. You may apply your own settings in the case if you want to test how the OS will live with other settings or may be you want to set your unique serial number. OK, do this!

But do not strive to fill all fields of the section if you don't understand what is what!

 

How port from Chameleon Smbios.plist to Clover config.plist

 

To be filled ....

Example n.1

 

From smbios.plist (Chameleon)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>SMbiosdate</key>
    <string>08/03/10</string>
    <key>SMbiosvendor</key>
    <string>Apple Inc.</string>
    <key>SMbiosversion</key>
    <string>MP31.88Z.006C.B05.0903051113</string>
    <key>SMboardproduct</key>
    <string>Mac-F2268DC8</string>
    <key>SMfamily</key>
    <string>MacPro</string>
    <key>SMmanufacturer</key>
    <string>Apple Inc.</string>
    <key>SMproductname</key>
    <string>MacPro3,1</string>
    <key>SMserial</key>
    <string>ElEvEnChArS</string>
    <key>SMsystemversion</key>
    <string>1.3</string>
</dict>
</plist>
to confing.plist (Clover)

....
    <key>SMBIOS</key>
    <dict>
        <key>BiosVendor</key>
        <string>Apple Inc.</string>
        <key>BiosVersion</key>
        <string>MP31.88Z.006C.B05.0802291410</string>
        <key>BiosReleaseDate</key>
        <string>08/03/10</string>
        <key>Manufacturer</key>
        <string>Apple Inc.</string>
        <key>ProductName</key>
        <string>MacPro3,1</string>
        <key>Version</key>
        <string>1.3</string>
        <key>Family</key>
        <string>MacPro</string>
        <key>SerialNumber</key>
        <string>ElEvEnChArS</string>
        <key>SmUUID</key>
        <string>00000000-0000-X000-X000-XXXXXXXXXXXX</string>
        <key>BoardManufacturer</key>
        <string>Apple Inc.</string>
        <key>BoardSerialNumber</key>
        <string>C02032101R5DC771H</string>
        <key>Board-ID</key>
        <string>Mac-F42C88C8</string>
        <key>BoardVersion</key>
        <string>Proto1</string>
        <key>Mobile</key>
        <string>No</string>
        <key>LocationInChassis</key>
        <string>Part Component</string>
        <key>ChassisManufacturer</key>
        <string>Apple Inc.</string>
        <key>ChassisAssetTag</key>
        <string>P6TDeluxeV1</string>
        <key>FirmwareFeatures</key>
        <string>0xX000XXXX</string>
    </dict>
....

 

Hi Slice,

 

How to generate a string to Firmware Features for my hack?

<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>10/12/2012</string>
		<key>BiosVendor</key>
		<string>Apple Inc.</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010A.B05.1210121459</string>
		<key>Board-ID</key>
		<string>Mac-xxxxxxxxxxxx</string>
		<key>BoardManufacturer</key>
		<string>Apple Inc.</string>
		<key>BoardSerialNumber</key>
		<string>xxxxxxxxxxxx</string>
		<key>BoardType</key>
		<string>10</string>
		<key>ChassisType</key>
		<string>0x03</string>
		<key>Family</key>
		<string>iMac</string>
		<key>FirmwareFeatures</key>
		<string>0x00000000</string> ###### here ######
		<key>ProductName</key>
		<string>iMac13,2</string>
		<key>SMsystemversion</key>
		<string>1.0</string>
		<key>SerialNumber</key>
		<string>xxxxxxxxxxxx</string>
		<key>SmUUID</key>
		<string>DD34773F-xxxxxxxxxxxx</string>
		<key>Trust</key>
		<true/>
	</dict>
Link to comment
Share on other sites

Question:

 

I am using terminal to create an installer and it worked fine on my intel notebook

 

However I have an AMD Desktop and I want to replace the mach_kernel in the Install OS X Mavericks.app so I can boot the installer and then install mavericks that way on my amd desktop.

 

I tried using Pacifist and that didn't work. I couldn't replace any files in that application

 

(Again I didn't want to make a new topic because that is a waste of space)

Link to comment
Share on other sites

Question:

 

I am using terminal to create an installer and it worked fine on my intel notebook

 

However I have an AMD Desktop and I want to replace the mach_kernel in the Install OS X Mavericks.app so I can boot the installer and then install mavericks that way on my amd desktop.

 

I tried using Pacifist and that didn't work. I couldn't replace any files in that application

 

(Again I didn't want to make a new topic because that is a waste of space)

Transmac or macdrive in windows

Link to comment
Share on other sites

Hi Slice,

 

How to generate a string to Firmware Features for my hack?

<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>10/12/2012</string>
		<key>BiosVendor</key>
		<string>Apple Inc.</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010A.B05.1210121459</string>
		<key>Board-ID</key>
		<string>Mac-xxxxxxxxxxxx</string>
		<key>BoardManufacturer</key>
		<string>Apple Inc.</string>
		<key>BoardSerialNumber</key>
		<string>xxxxxxxxxxxx</string>
		<key>BoardType</key>
		<string>10</string>
		<key>ChassisType</key>
		<string>0x03</string>
		<key>Family</key>
		<string>iMac</string>
		<key>FirmwareFeatures</key>
		<string>0x00000000</string> ###### here ######
		<key>ProductName</key>
		<string>iMac13,2</string>
		<key>SMsystemversion</key>
		<string>1.0</string>
		<key>SerialNumber</key>
		<string>xxxxxxxxxxxx</string>
		<key>SmUUID</key>
		<string>DD34773F-xxxxxxxxxxxx</string>
		<key>Trust</key>
		<true/>
	</dict>
		<key>FirmwareFeatures</key>
		<string>0xC0001403</string>

PS. And I may notice wrong key in your list

		<key>SMsystemversion</key>
		<string>1.0</string>

It must be

		<key>Version</key>
		<string>1.0</string>

Link to comment
Share on other sites

I may be way behind others around here, BUT ---I have tried in every conceivable way to get Clover to work on a PC running MacOS.

 

I  am using 10.6.8 and would like to know if others are successful with 10.6.8 building a USB for Mavericks or Mountain Lion?

 

I have tried to get Clover to boot a USB to install Mavericks, but every time I do , it fails to boot into the window where you select the drive to boot up. I've tried a GUID formatted USB, a MBR formatted disk with a second partition as Fat-32 titled EFI and every conceivable combination thereof.

 

Can some one tell me PLEASE!! What works with what OS version.??

 

Thanks for any responses.

Link to comment
Share on other sites

I may be way behind others around here, BUT ---I have tried in every conceivable way to get Clover to work on a PC running MacOS.

 

I  am using 10.6.8 and would like to know if others are successful with 10.6.8 building a USB for Mavericks or Mountain Lion?

 

I have tried to get Clover to boot a USB to install Mavericks, but every time I do , it fails to boot into the window where you select the drive to boot up. I've tried a GUID formatted USB, a MBR formatted disk with a second partition as Fat-32 titled EFI and every conceivable combination thereof.

 

Can some one tell me PLEASE!! What works with what OS version.??

 

Thanks for any responses.

 

Take a look this web:

 

http://cloverboot.weebly.com/before-you-start.html

Link to comment
Share on other sites

I may be way behind others around here, BUT ---I have tried in every conceivable way to get Clover to work on a PC running MacOS.

 

I  am using 10.6.8 and would like to know if others are successful with 10.6.8 building a USB for Mavericks or Mountain Lion?

 

I have tried to get Clover to boot a USB to install Mavericks, but every time I do , it fails to boot into the window where you select the drive to boot up. I've tried a GUID formatted USB, a MBR formatted disk with a second partition as Fat-32 titled EFI and every conceivable combination thereof.

 

Can some one tell me PLEASE!! What works with what OS version.??

 

Thanks for any responses.

 

I think starting a bootloader from a USB stick is not related to OSes installed on this computer.

Yes I work with 10.6.8 and with 10.5.8 Clover booted. See no problems.

Link to comment
Share on other sites

Question: nVidia GTX 660 video card is in the boot of the bios that of clover but I do not have full screen edges blacks, desktop full resolution.

I tried to use the .rom in EFI /Clover/Rom and config.plist LoadVBios=true same problem.

Advice

 

Fabio

Link to comment
Share on other sites

 

Question: nVidia GTX 660 video card is in the boot of the bios that of clover but I do not have full screen edges blacks, desktop full resolution.
I tried to use the .rom in EFI /Clover/Rom and config.plist LoadVBios=true same problem.
Advice
 
Fabio

 

U need this

GTX 660 uefi gop

Google for it.

Link to comment
Share on other sites

I think starting a bootloader from a USB stick is not related to OSes installed on this computer.

Yes I work with 10.6.8 and with 10.5.8 Clover booted. See no problems.

Slice,

 

I sent another post to you explaining that I found the text file included in Clover/usr/local about installing clover to a USB. I need to understand how to install the fdisk440 executable included in the Local file to my Terminal commands.

 

Thanks

Link to comment
Share on other sites

Slice,

 

Thanks for that information. I got as far as building the USB to the point where it says copy the BOOT file to /Volumes/USB(Kingston) and then copy -r EFI /Volumes/(Kingston)USB. My USB is 16GB GUID formatted with Clover loaded in the msdos EFI partition and Mavericks loaded in the main EFI partition.

 

I don't understand which boot should be copied to the USB as there is a boot file in the EFI main

partition titled boot. Since Clover is loaded in the EFI partition of the USB fomatted GUID, does that copy of Boot still need to be done?

 

When I issued the sudo fdsik440 -f boot0ss -u -y /dev/rdisk1 --I got a segmentation error? Don't know what that means?

 

Thanks for helping me understand how to successfully use Clover as my bootloader.

Link to comment
Share on other sites

Slice,

 

Thanks for that information. I got as far as building the USB to the point where it says copy the BOOT file to /Volumes/USB(Kingston) and then copy -r EFI /Volumes/(Kingston)USB. My USB is 16GB GUID formatted with Clover loaded in the msdos EFI partition and Mavericks loaded in the main EFI partition.

 

I don't understand which boot should be copied to the USB as there is a boot file in the EFI main

partition titled boot. Since Clover is loaded in the EFI partition of the USB fomatted GUID, does that copy of Boot still need to be done?

 

When I issued the sudo fdsik440 -f boot0ss -u -y /dev/rdisk1 --I got a segmentation error? Don't know what that means?

 

Thanks for helping me understand how to successfully use Clover as my bootloader.

If you want legacy boot then you need a file BOOT. 

If you want UEFI boot then only EFI folder is needed.

Depends on your BIOS.

 

segmentation fault means your copy of fdisk440 is not working in your OS version. 10.6.8? It requires an fdisk440 compiled under 10.6.8.

Or use dd command instead it

Something like

dd if=/dev/disk1 count=1 bs=512 of=origMBRcp origMBR newMBRdd if=boot0ss of=newMBR bs=1 count=440 conv=notruncdd if=newMBR of=/dev/disk1 count=1 bs=512
Link to comment
Share on other sites

×
×
  • Create New...