Clover General discussion

[Maniac10]

Since Clover 3952 we can use EDK2-23447 and more? Test, please.

 

Now boot7 works again, thanks Slice.

[SavageAUS]

As this is general discussion i will ask here.

Which Linux OS's / Distro's are supported by Clover?

I have Ubuntu installed and that works just fine.

Linux Mint shows up as Ubuntu.

Antergos (Arch based installer/Distro)Does not show up in Clover menu at all.

Marjaro as above.

All installed using UEFI.

Windows 10 and macOS boot perfectly.

Thanks

[vusun123]

As this is general discussion i will ask here.

Which Linux OS's / Distro's are supported by Clover?

I have Ubuntu installed and that works just fine.

Linux Mint shows up as Ubuntu.

Antergos (Arch based installer/Distro)Does not show up in Clover menu at all.

Marjaro as above.

All installed using UEFI.

Windows 10 and macOS boot perfectly.

Thanks

Most of us doesn't use all the Linux distros available. If you want you can always make a custom entry for your Linux installation

[dgsga]

Hi

I have just moved over to an MSI R9 270X Gaming 2G ITX graphics card as got tired of waiting for Nvidia Web updates. I have got the 2 mini display ports on the card working well with a modified Futomaki frame buffer but only when booting in verbose mode. I get a black screen when booting in normal mode. I have tried all the working AMD7000Controller framebuffers and the default Radeon framebuffer with the same result. Here are the outputs of the various decoders:

ATOM BIOS Rom:
    SubsystemVendorID: 0x1462 SubsystemID: 0x303a
    IOBaseAddress: 0x0000
    Filename: TV303MH.1L0
    BIOS Bootup Message:
113-MSI TV303MH.1L0 CURACAO XT V30321S C63101 64Mx32 G5 2G

PCI ID: 1002:6810
Connector at index 0
    Type [@offset 43588]: DisplayPort (10)
    Encoder [@offset 43592]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 43698]: 0x92, OSX senseid: 0x3
Connector at index 1
    Type [@offset 43598]: DisplayPort (10)
    Encoder [@offset 43602]: INTERNAL_UNIPHY2 (0x21)
    i2cid [@offset 43725]: 0x90, OSX senseid: 0x1
Connector at index 2
    Type [@offset 43608]: HDMI-A (11)
    Encoder [@offset 43612]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 43752]: 0x94, OSX senseid: 0x5
Connector at index 3
    Type [@offset 43618]: DVI-I (2)
    Encoder [@offset 43622]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 43789]: 0x95, OSX senseid: 0x6
Connector at index 4
    Type [@offset 43628]: DVI-I (2)
    Encoder [@offset 43632]: INTERNAL_KLDSCP_DAC1 (0x15)
    i2cid [@offset 43789]: 0x95, OSX senseid: 0x6




TV303MH.1L0 :

113-MSI TV303MH.1L0 CURACAO XT V30321S C63101 64Mx32 G5 2G

Subsystem Vendor ID: 1462
Subsystem ID: 303a
Object Header Structure Size: 360
Connector Object Table Offset: 48
Router Object Table Offset: 0
Encoder Object Table Offset: fd
Display Path Table Offset: 12
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [12] which is [HDMI_TYPE_A]
    encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x21 [duallink 0x1] enc 0x3)] linkb: true
Connector Object Id [2] which is [DVI_I]
    encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false
Connector Object Id [2] which is [DVI_I]
    encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false

01 [DISPLAY_PORT]
encoder obj 0x20 transmitter 0x11 duallink 0x2 enc 0x2

Connector at index 0
    Type [@offset 43524]: DisplayPort (10)
    Encoder [@offset 43528]: INTERNAL_UNIPHY2 (0x21)
    i2cid [@offset 43616]: 0x91, OSX senseid: 0x3

CODE CONSTRUCTION 11 02 01 03

02 [DISPLAY_PORT]
encoder obj 0x21 transmitter 0x12 duallink 0x1 enc 0x4
Connector at index 1
    Type [@offset 43534]: DisplayPort (10)
    Encoder [@offset 43538]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 43643]: 0x90, OSX senseid: 0x1

CODE CONSTRUCTION 12 04 02 01

03 [HDMI_TYPE_A]
encoder obj 0x20 transmitter 0x21 duallink 0x1 enc 0x3

Connector at index 2
    Type [@offset 43544]: DisplayPort (10)
    Encoder [@offset 43548]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 43670]: 0x93, OSX senseid: 0x5

CODE CONSTRUCTION 21 03 03 05

04 [DVI_I]
encoder obj 0x1e transmitter 0x10 duallink 0x0 enc 0x0
Connector at index 3
    Type [@offset 43554]: DisplayPort (10)
    Encoder [@offset 43558]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 43697]: 0x95, OSX senseid: 0x6

CODE CONSTRUCTION 10 00 04 06


11 02 01 03
12 04 02 01
21 03 03 05
10 00 04 06


    Personality: Futomaki
ConnectorInfo count in decimal: 4
Disk offset in decimal 1765440
00 04 00 00 04 03 00 00 00 01 01 01 00 00 00 00 12 04 04 01 00 00 00 00
00 04 00 00 04 03 00 00 00 01 02 01 00 00 00 00 22 05 05 02 00 00 00 00
04 00 00 00 14 02 00 00 00 01 03 00 00 00 00 00 00 00 06 06 00 00 00 00
00 08 00 00 04 02 00 00 00 01 04 00 00 00 00 00 11 02 01 03 00 00 00 00


FIXED    Personality: Futomaki
ConnectorInfo count in decimal: 4
Disk offset in decimal 1765440
00 04 00 00 04 03 00 00 00 01 01 01 00 00 00 00 11 02 01 03 00 00 00 00
00 04 00 00 04 03 00 00 00 01 02 01 00 00 00 00 12 04 02 01 00 00 00 00
00 08 00 00 00 02 00 00 00 01 03 00 00 00 00 00 21 03 03 05 00 00 00 00
04 00 00 00 14 02 00 00 00 01 04 00 00 00 00 00 10 00 04 06 00 00 00 00

I can't fathom out why it only works in verbose mode, could it be Clover related in any way?. Any help would be much appreciated.

[Slice]

As this is general discussion i will ask here.

Which Linux OS's / Distro's are supported by Clover?

I have Ubuntu installed and that works just fine.

Linux Mint shows up as Ubuntu.

Antergos (Arch based installer/Distro)Does not show up in Clover menu at all.

Marjaro as above.

All installed using UEFI.

Windows 10 and macOS boot perfectly.

Thanks

  { L"\\EFI\\grub\\grubx64.efi", L"Grub EFI boot menu", L"grub,linux" },
  { L"\\EFI\\Gentoo\\grubx64.efi", L"Gentoo EFI boot menu", L"gentoo,linux", "Gentoo" },
  { L"\\EFI\\Gentoo\\kernelx64.efi", L"Gentoo EFI kernel", L"gentoo,linux" },
  { L"\\EFI\\RedHat\\grubx64.efi", L"RedHat EFI boot menu", L"redhat,linux", "Redhat" },
  { L"\\EFI\\ubuntu\\grubx64.efi", L"Ubuntu EFI boot menu", L"ubuntu,linux", "Ubuntu" },
  { L"\\EFI\\kubuntu\\grubx64.efi", L"kubuntu EFI boot menu", L"kubuntu,linux", "kubuntu" },
  { L"\\EFI\\LinuxMint\\grubx64.efi", L"Linux Mint EFI boot menu", L"mint,linux", "Linux Mint" },
  { L"\\EFI\\Fedora\\grubx64.efi", L"Fedora EFI boot menu", L"fedora,linux", "Fedora" },
  { L"\\EFI\\opensuse\\grubx64.efi", L"OpenSuse EFI boot menu", L"suse,linux", "openSUSE" },
  { L"\\EFI\\arch\\grubx64.efi", L"ArchLinux EFI boot menu", L"arch,linux" },
  { L"\\EFI\\arch_grub\\grubx64.efi", L"ArchLinux EFI boot menu", L"arch,linux" },

[SavageAUS]

Awesome thanks @Slice.

I like to test out linux distro's on a regular basis so ill let you know if i run into any trouble on the Clover end.

Maybe i still had EFI files left over from Ubuntu on my mint install which could be why Clover showed Mint as Ubuntu.

[joe75]

I can't fathom out why it only works in verbose mode, could it be Clover related in any way?. Any help would be much appreciated.

 

Try removing windowserver.plists and any previous display configs

[arsradu]

Guys, I've done something really stupid. 

 

I bought a Retina Macbook Pro 13 late-2013 and installed Sierra 10.12.1 onto it. No problems so far. Then I created a new partition and tried to install the Beta onto it, using a USB drive made with Clover (hackintosh style) and at first I selected OSX Base System on boot up. And it got to the installer and got an error (error 0 or something like that). And now I think I know why that happened.

 

Anyway, then I selected EFI (also from the USB drive) and it loaded up Clover. Then I selected the USB drive from the Clover UI (like I would do if I want a Hackintosh installation) and...it would just stay there with the Apple logo and no loading bar. After a while, I force shut down the computer. And tried to boot up normally. Removed the USB and everything.

 

But since then, it goes into boot loop, with no Apple logo, only the chime. It sounds the chime over and over again.

 

Please, tell me you know how to fix this. It's clearly a software issue. I'm pretty sure something got corrupted. I just don't know what and how to fix it.

 

I tried booting in Safe Mode (holding the Shift key while booting), tried booting in Recovery (holding Command + R), tried selecting a different boot drive (Option key). I don't know what else to try....

 

Sorry about the possible off-topic. I just don't know what to do. I even made a new USB installation and tried to boot from it. But..I only got the endless loop and nothing else.

[Faradis]

 

 

 

Guys, I've done something really stupid. 

 

I bought a Retina Macbook Pro 13 late-2013 and installed Sierra 10.12.1 onto it. No problems so far. Then I created a new partition and tried to install the Beta onto it, using a USB drive made with Clover (hackintosh style) and at first I selected OSX Base System on boot up. And it got to the installer and got an error (error 0 or something like that). And now I think I know why that happened.

 

Anyway, then I selected EFI (also from the USB drive) and it loaded up Clover. Then I selected the USB drive from the Clover UI (like I would do if I want a Hackintosh installation) and...it would just stay there with the Apple logo and no loading bar. After a while, I force shut down the computer. And tried to boot up normally. Removed the USB and everything.

 

But since then, it goes into boot loop, with no Apple logo, only the chime. It sounds the chime over and over again.

 

Please, tell me you know how to fix this. It's clearly a software issue. I'm pretty sure something got corrupted. I just don't know what and how to fix it.

 

I tried booting in Safe Mode (holding the Shift key while booting), tried booting in Recovery (holding Command + R), tried selecting a different boot drive (Option key). I don't know what else to try....

 

Sorry about the possible off-topic. I just don't know what to do. I even made a new USB installation and tried to boot from it. But..I only got the endless loop and nothing else.

trybooting from usb without clover only with apple installer

[arsradu]

 

 

 

 

trybooting from usb without clover only with apple installer

 

Can't select the boot drive anymore. It just sounds the chime over and over again. With no logo, no graphics on the screen.

[smolderas]

Can't select the boot drive anymore. It just sounds the chime over and over again. With no logo, no graphics on the screen.

Try reseting PRAM and then SMC. After that recovery mode should work.

 

If none of those above works, try with an USB installer (vanilla!). If that won't work either, try the apple support.

[arsradu]

Try reseting PRAM and then SMC. After that recovery mode should work.

 

If none of those above works, try with an USB installer (vanilla!). If that won't work either, try the apple support.

Tried PRAM and SMC reset. None of them worked. I mean they did work (at least I think the SMC reset worked), but didn't actually solve the issue.

 

 

I made another USB drive. Without Clover. And it boots fine from it on another Macbook Pro (using the Option key to select the boot drive). So I'm pretty sure the USB is now ok.

 

But on this Mac, it just doesn't show anything on the screen when pressing Option. It just sounds the chime, over and over again, without showing the logo.

 

The laptop is not under warranty. So..not sure what good the Apple Support would do in this case.

[TheRacerMaster]

Use createinstallmedia and reinstall. Be sure to wipe the ESP.

[smolderas]

Tried PRAM and SMC reset. None of them worked. I mean they did work (at least I think the SMC reset worked), but didn't actually solve the issue.

 

 

I made another USB drive. Without Clover. And it boots fine from it on another Macbook Pro (using the Option key to select the boot drive). So I'm pretty sure the USB is now ok.

 

But on this Mac, it just doesn't show anything on the screen when pressing Option. It just sounds the chime, over and over again, without showing the logo.

 

The laptop is not under warranty. So..not sure what good the Apple Support would do in this case.

Well, then begin using clover on it then

You said that it works.

[bronxteck]

did your clover boot stick have a apple folder? if it did it might have tried installing an smc update and if it was from another model then you might have to load the correct one into it.

 also if you can pull the drive and see if the bootloop stops then you know its just a corrupted drive.

[arsradu]

Well, then begin using clover on it then

You said that it works.

 

I can't select any boot drive anymore. It doesn't respond to Option + Power. It just keeps rebooting.

did your clover boot stick have a apple folder? if it did it might have tried installing an smc update and if it was from another model then you might have to load the correct one into it.

 also if you can pull the drive and see if the bootloop stops then you know its just a corrupted drive.

 

I don't know.... If it ads one when installing it, then it might have had one indeed. And yeah, it was surely from another model.... Stupid me. I just realized it. Of course it couldn't have worked.

 

I'm pretty sure it will stop. Just as I'm pretty sure it's just a corrupted EFI.

 

But I've got two problems here:

1. no pentalobe screwdriver.

2. even if it stops, how do I correct the mistake from outside? How can I put back the correct whatever it is, without being able to boot up the computer? It's not like I can connect it to my hackintosh and access it from outside. The connector on those SSDs is proprietary.

Use createinstallmedia and reinstall. Be sure to wipe the ESP.

 

How? I already got a USB drive and it boots fine on another MacBook Pro. So let's say the USB drive is ok now. With no Clover. But how do I wipe the ESP without being able to load the USB drive and without being able to boot into the OS?

[joevt]

2. even if it stops, how do I correct the mistake from outside? How can I put back the correct whatever it is, without being able to boot up the computer? It's not like I can connect it to my hackintosh and access it from outside. The connector on those SSDs is proprietary.

Target disk mode?

https://support.apple.com/en-ca/HT201462

 

Or maybe your EFI boot fails before it checks for that "T" keypress, like it fails for every other keypress you've tried?

[arsradu]

Target disk mode?

https://support.apple.com/en-ca/HT201462

 

Or maybe your EFI boot fails before it checks for that "T" keypress, like it fails for every other keypress you've tried?

 

Indeed it does. None of the key combinations (aside from Reset SMC, which didn't actually do anything to fix the issue) seemed to worked. Maybe PRAM reset too. i don't know, cause it didn't make a difference.

Anyway, I bought an adapter to connect the SSD directly to my hackintosh and see what's wrong with it. I suppose the EFI partition got corrupted or something. Or it just wrote some wrong values onto it. I think it's the most logical explanation. Anyway, I still need the screwdrivers (Torx T5 and Pentalobe P5) to remove the SSD from the MacBook before attempting anything with it. So maybe tomorrow I'll try to fix this.

 

If anyone got any idea how to do it without taking out the SSD, I would gladly try it. But so far this looks like the only possible solution to this issue.

[bronxteck]

maybe you can uncompress the smc from apples download page and add it to the apple folder on the efi of the thumb drive using the file paths and structures. you would have to look at an existing APPLE folder of course. or setup a hack with your machines smbios and see if osx creates it for you on the efi partition then transfer it.

[arsradu]

maybe you can uncompress the smc from apples download page and add it to the apple folder on the efi of the thumb drive using the file paths and structures. you would have to look at an existing APPLE folder of course. or setup a hack with your machines smbios and see if osx creates it for you on the efi partition then transfer it.

 

So..I got the SSD out... Connected it to my hackintosh. And the only thing I noticed different from my other macbook's EFI, is the presence of an UPDATERS folder, containing what I can only assume is what Clover tried to flash onto it.

 

 

 

Problem is that, even with no SSD installed, it still goes into the endless chime... So..I guess it's either cached somewhere. Or I don't know... But it doesn't seem to be the SSD anymore. Any ideas what else could it be?

[bronxteck]

mac-189a3d4f975d5ffc seems to be MacBook Pro 11,1 but i do not see an SMC update for it at https://support.apple.com/en-us/HT201518only an EFI Boot Rom.

maybe a methode like this one might help https://pubmem.wordpress.com/2011/04/09/flash-efi-firmware-update-manually-on-a-macbook-51/

even if you can create it on a hack and compare/ transfer it. or boot the hack with the MAC HDD using the correct smbios and trying.

[FredWst]

So..I got the SSD out... Connected it to my hackintosh. And the only thing I noticed different from my other macbook's EFI, is the presence of an UPDATERS folder, containing what I can only assume is what Clover tried to flash onto it.

 

Screen Shot 2016-12-07 at 8.08.00 PM.png Screen Shot 2016-12-07 at 8.08.08 PM.png Screen Shot 2016-12-07 at 8.08.16 PM.png

 

Problem is that, even with no SSD installed, it still goes into the endless chime... So..I guess it's either cached somewhere. Or I don't know... But it doesn't seem to be the SSD anymore. Any ideas what else could it be?

 

So..I got the SSD out... Connected it to my hackintosh. And the only thing I noticed different from my other macbook's EFI, is the presence of an UPDATERS folder, containing what I can only assume is what Clover tried to flash onto it.

 

Screen Shot 2016-12-07 at 8.08.00 PM.png Screen Shot 2016-12-07 at 8.08.08 PM.png Screen Shot 2016-12-07 at 8.08.16 PM.png

 

Problem is that, even with no SSD installed, it still goes into the endless chime... So..I guess it's either cached somewhere. Or I don't know... But it doesn't seem to be the SSD anymore. Any ideas what else could it be?

 

hi,

 

if you got this, it means that your smbios data are not up to date.

Try to use Clover last revision. and delete these files.

 

Fred

[arsradu]

 

 

hi,

 

if you got this, it means that your smbios data are not up to date.

Try to use Clover last revision. and delete these files.

 

Fred

 

I did, but not using Clover. As I said above, I bought a PCI adapter for Mac SSDs to have direct access to it. But it's not the SSD since it does this even without the SSD plugged in. It doesn't even show the boot drive picker (Option key + Power)

 

Update: fixed by replacing the EFI chipset on the motherboard. Apparently, the firmware on that chipset got corrupted due to an incomplete update (I suppose when I force shut it down, that happened). It was like a $60 repair. Could have been a lot worse. Just for everyone wondering if it can be fixed without replacing the entire board. Yeah, it can.

 

Thanks for everyone's feedback on this.

[hackintosh1984]

  Please share link for download pkg installer 3960. Very thanks.

[Fljagd]

  Please share link for download pkg installer 3960. Very thanks.

here

Clover_v2.3k_r3960.zip