Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

I have tried this HPET patch(need set FixHPET_0010 to false to affect),inject or disable inject usb,use or not use DSDT,put fakesmc.kext in 10.11 or other folder.Still Apple Usb Host Port interrupt Occurred enumeration failed retrying enumeration in 50ms,then still wait for root device.And I find if I don't format USB Flash Drive all to one partition I always get create usb installer fail.I install clover to ESP,it always install to installer Partition that include Install OS X 10.11 Developer Beta.app,is this normal?before I always see clover EFI folder in ESP

May be some BIOS settings affected.

Anyway. Did you try also Clover way - all DSDT fixes and no custom patches?

Link to comment
Share on other sites

May be some BIOS settings affected.

Anyway. Did you try also Clover way - all DSDT fixes and no custom patches?

Yes,I have tried.I also tried also DSDT patches no Clover DSDT fixes.I found some clover DSDT fixes doesn't suit well for my old P45 motherboard well which DSDT Editor with a lot of DSDT patches that suit well like FakeLPC FakeSATA Shutdown,so I disable all Clover DSDT fixes.I using untouched DSDT.aml,shutdown also doesn't work.So it's should not relate to GPU.

I have tried 10.10.3 USB installer or SSD OS,all doesn't have USB interrupt Occurred enumeration failed problem,which 10.11 DP1 always have,all using same config.plist and DSDT.aml

Link to comment
Share on other sites

 I disable all Clover DSDT fixes.I using untouched DSDT.aml,shutdown also doesn't work.

Yes, without fixes you will have problems.

Fixes are not intended to create problems.

Fixes are intended to resolve problems.

Link to comment
Share on other sites

Yes, without fixes you will have problems.

Fixes are not intended to create problems.

Fixes are intended to resolve problems.

Yes Clover has a lot of useful fixes like FakeLPC FixDarwin FixRTC,however Clover still have useless fixes for me like FixShutdown(only works for ASUS,mine is much like Gigabyte),FixSATA,FixHPET,FixUSB(for Wakeup),though I have searched forum to add alternative fixes to DSDT.aml.Sometimes I think if those Clover add those fixes should be easy for me,also help me get rid of my DSDT.

Link to comment
Share on other sites

Yes, without fixes you will have problems.

Fixes are not intended to create problems.

Fixes are intended to resolve problems.

 

Well, my own experience was different. With all the default settings I HAD problems. Very weird problems. With some modifications, too.

 

With a customized DSDT and NO clover settings I do NOT have these problems. Go figure. While I appreciate Clovers patching capabilities, not all fixes are useful, especially with the default settings.

 

Of course YMMV, but these were my personal experiences.

Link to comment
Share on other sites

 

PikerAlpha told me this:

The zone_init panic you guys are seeing is likely caused by a memory map error; check getMemoryMap() and compare its results with Clover. That should resolve this issue.

It is not Clover problem

  • Like 1
Link to comment
Share on other sites

hello clover team.

i found lapic error code change in El Capitan DB1.

so i added Lapic error fix in clover source.

65 8B 0C 25 1C 00 00 00 pattern is not near location. it's exist about 1411 offset far.

also it have code "mov     eax, cs:_master_cpu" between _panic and 65 8B 0C 25 1C 00 00 00. it's 6 hexs

so i get 1411 and _panic is 5 hexs and "master_cpu" is 6 hexs then total 11. so  1411-11.

my english is not good. if you have some sense, you will know it blow code.

 

clover team, please add code 

 

 

add,

1. el capitan 10.11 folder is not make in latest clover

2. latest clover version cant pass applecpupowermanagement.kext in snow 10.6.8.

i check AsusACPIM. but i got KP. 10.7~ 10.11 is no problem.

 

 

 

 
BOOLEAN KernelLapicPatch_64(VOID *kernelData)
{
  // Credits to donovan6000 and sherlocks for providing the lapic kernel patch source used to build this function
  
  UINT8       *bytes = (UINT8*)kernelData;
  UINT32      patchLocation=0;
  UINT32      i;
  
  DBG("Looking for Lapic panic call (64-bit) Start\n");
  
  for (i=0; i<0x1000000; i++) {   
    if (bytes[i+0] == 0x65 && bytes[i+1] == 0x8B && bytes[i+2] == 0x04 && bytes[i+3] == 0x25 &&
               bytes[i+4] == 0x3C && bytes[i+5] == 0x00 && bytes[i+6] == 0x00 && bytes[i+7] == 0x00 &&
               bytes[i+45] == 0x65 && bytes[i+46] == 0x8B && bytes[i+47] == 0x04 && bytes[i+48] == 0x25 &&
               bytes[i+49] == 0x3C && bytes[i+50] == 0x00 && bytes[i+51] == 0x00 && bytes[i+52] == 0x00) {
      patchLocation = i+40;
      DBG("Found Snow Leopard Lapic panic at 0x%08x\n", patchLocation);
      break;
    } else if (bytes[i+0]  == 0x65 && bytes[i+1]  == 0x8B && bytes[i+2]  == 0x04 && bytes[i+3]  == 0x25 &&
               bytes[i+4]  == 0x14 && bytes[i+5]  == 0x00 && bytes[i+6]  == 0x00 && bytes[i+7]  == 0x00 &&
               bytes[i+35] == 0x65 && bytes[i+36] == 0x8B && bytes[i+37] == 0x04 && bytes[i+38] == 0x25 &&
               bytes[i+39] == 0x14 && bytes[i+40] == 0x00 && bytes[i+41] == 0x00 && bytes[i+42] == 0x00) {
      patchLocation = i+30;
      DBG("Found Lion, Mountain Lion Lapic panic at 0x%08x\n", patchLocation);
      break;
    } else if (bytes[i+0] == 0x65 && bytes[i+1] == 0x8B && bytes[i+2] == 0x04 && bytes[i+3] == 0x25 &&
               bytes[i+4] == 0x1C && bytes[i+5] == 0x00 && bytes[i+6] == 0x00 && bytes[i+7] == 0x00 &&
               bytes[i+36] == 0x65 && bytes[i+37] == 0x8B && bytes[i+38] == 0x04 && bytes[i+39] == 0x25 &&
               bytes[i+40] == 0x1C && bytes[i+41] == 0x00 && bytes[i+42] == 0x00 && bytes[i+43] == 0x00) {
      patchLocation = i+31;
      DBG("Found Mavericks Lapic panic at 0x%08x\n", patchLocation);
      break;
      //rehabman: 10.10.DP1 lapic
    } else if (bytes[i+0] == 0x65 && bytes[i+1] == 0x8B && bytes[i+2] == 0x04 && bytes[i+3] == 0x25 &&
               bytes[i+4] == 0x1C && bytes[i+5] == 0x00 && bytes[i+6] == 0x00 && bytes[i+7] == 0x00 &&
               bytes[i+33] == 0x65 && bytes[i+34] == 0x8B && bytes[i+35] == 0x04 && bytes[i+36] == 0x25 &&
               bytes[i+37] == 0x1C && bytes[i+38] == 0x00 && bytes[i+39] == 0x00 && bytes[i+40] == 0x00) {
      patchLocation = i+28;
      DBG("Found Yosemite Lapic panic at 0x%08x\n", patchLocation);
      break;
      //sherlocks: 10.11.DB1
    } else if (bytes[i+0] == 0x65 && bytes[i+1] == 0x8B && bytes[i+2] == 0x0C && bytes[i+3] == 0x25 &&
               bytes[i+4] == 0x1C && bytes[i+5] == 0x00 && bytes[i+6] == 0x00 && bytes[i+7] == 0x00 &&
               bytes[i+1411] == 0x65 && bytes[i+1412] == 0x8B && bytes[i+1413] == 0x0C && bytes[i+1414] == 0x25 &&
               bytes[i+1415] == 0x1C && bytes[i+1416] == 0x00 && bytes[i+1417] == 0x00 && bytes[i+1418] == 0x00) {
      patchLocation = i+1400;
      DBG("Found El Capitan Lapic panic at 0x%08x\n", patchLocation);
      break;
    }
  }
  • Like 4
Link to comment
Share on other sites

Hi,

 

I'm having some problems with boot Yosemite. The system boots so far and then crashes. It loads FakeSMC and the Elan Touchpad kexts and sits there. When it crashes it shows a line saying "still waiting for root device' in garbled text.

 

20b4b290e3e75ef30aa444292ad3f379.jpg

 

2a96f1b1e223e1e7825d849f2bdb8e1e.jpg

 

Is there anyway to log the boot up and it can find out what it causing it to crash.

 

I am using a patched DSDT as well.

 

I hope you can help.

 

Thanks

  • Like 1
Link to comment
Share on other sites

Hi,

 

I'm having some problems with boot Yosemite. The system boots so far and then crashes. It loads FakeSMC and the Elan Touchpad kexts and sits there. When it crashes it shows a line saying "still waiting for root device' in garbled text.

 

Is there anyway to log the boot up and it can find out what it causing it to crash.

 

I am using a patched DSDT as well.

 

I hope you can help.

 

Thanks

 

Same problem with a Dell D830 Nvidia. I know it's a quite old laptop but it runs El Capitan just fine as long as I don't try to install via a USB pen. Cloning method did the trick but I can't boot any USB Install disk with or w/o DSDT, Clover's fixes nor nv_disable=1 boot flag !

 

Always hangs at still waiting for root device… :wallbash:

 

I'm clueless :(.

  • Like 1
Link to comment
Share on other sites

Would you be able to point me in the right direction to were I can get this problem fixed.

 

Thanks

I have to say that Intel HD4000 is not my field of battle.

  • Like 2
Link to comment
Share on other sites

Hey guys

 

Has anyone successfully installed (post-install) Clover on 10.11 (UEFI mode)? Cause I keep getting an error that the installation will fail cause the software (Clover) is not compatible or something like that. I can take a screenshot if you need it.

 

But since booting off an installation USB of 10.11, WITH Clover as bootloader, works without a problem (that's how I got the OS installed in the first place), I'm wondering why it doesn't work after that. Any idea? Is there a fix to that?

Link to comment
Share on other sites

Hey guys

 

Has anyone successfully installed (post-install) Clover on 10.11 (UEFI mode)? Cause I keep getting an error that the installation will fail cause the software (Clover) is not compatible or something like that. I can take a screenshot if you need it.

 

But since booting off an installation USB of 10.11, WITH Clover as bootloader, works without a problem (that's how I got the OS installed in the first place), I'm wondering why it doesn't work after that. Any idea? Is there a fix to that?

 

Hi @arsradu,

 

I assume the error message is the same as the one posted by @MNSiw ?  If so, try booting into 10.11 with the rootless=0 boot flag, then run the installer....

 

post-846696-0-73323200-1434776522_thumb.png

 

Same problem with a Dell D830 Nvidia. I know it's a quite old laptop but it runs El Capitan just fine as long as I don't try to install via a USB pen. Cloning method did the trick but I can't boot any USB Install disk with or w/o DSDT, Clover's fixes nor nv_disable=1 boot flag !

 

Always hangs at still waiting for root device… :wallbash:

 

I'm clueless :(.

 

This is a known problem with OSX 10.11 DP1, not really a Clover issue.  The developer release notes for El Capitan warns 

 

  • USB storage devices, including internal SD card readers, may become unavailable after system sleep and require either re-plug or restart to recover.
  • USB input devices may become non-functional on some Macs after several days.
  • USB 1.0, 1.1 and older 2.0 devices may not function.

For those affected by the buggy drivers (including my Dell XPS M1530 laptop), this means that instead of creating and booting off a USB installer, you need to boot to an installer partition on the hard drive (use the createinstallmedia method) or directly run the Install OS X 10.11 Developer Beta .app in the Applications folder - see post #1887.

  • Like 3
Link to comment
Share on other sites

Hi @arsradu,

 

I assume the error message is the same as the one posted by @MNSiw ?  If so, try booting into 10.11 with the rootless=0 boot flag, then run the installer....

My old friend @fusion.  :)

 

Of course that was the error I was talking about, and of course adding boot flag rootless=0 solved it.

 

post-1303722-0-22611900-1434796441_thumb.png

 

Thank you very much!

  • Like 1
Link to comment
Share on other sites

Hi @arsradu,

 

I assume the error message is the same as the one posted by @MNSiw ?  If so, try booting into 10.11 with the rootless=0 boot flag, then run the installer....

 

attachicon.gifClover r3229 on El Capitan.png

 

 

This is a known problem with OSX 10.11 DP1, not really a Clover issue.  The developer release notes for El Capitan warns 

 

  • USB storage devices, including internal SD card readers, may become unavailable after system sleep and require either re-plug or restart to recover.
  • USB input devices may become non-functional on some Macs after several days.
  • USB 1.0, 1.1 and older 2.0 devices may not function.

For those affected by the buggy drivers (including my Dell XPS M1530 laptop), this means that instead of creating and booting off a USB installer, you need to boot to an installer partition on the hard drive (use the createinstallmedia method) or directly run the Install OS X 10.11 Developer Beta .app in the Applications folder - see post #1887.

Thank you,so it's a hardware and software issue,not a firmware like DSDT issue.By the way what's old usb 2.0 devices,what's new usb 2.0 devices?If it possible I use PCI to USB card to use new USB 2.0 devices?

Link to comment
Share on other sites

For those affected by the buggy drivers (including my Dell XPS M1530 laptop), this means that instead of creating and booting off a USB installer, you need to boot to an installer partition on the hard drive (use the createinstallmedia method) or directly run the Install OS X 10.11 Developer Beta .app in the Applications folder - see post #1887.

 

Indeed. I made a clone of a fresh install from an USB disk connected to another system and that did the job. I guess I'll have to wait a fix (hopefully) with next DPs to have a functional USB stick :P.

 

Otherwise, El Capitan runs just fine :D !

 

EL_Capitan_D830.png

  • Like 2
Link to comment
Share on other sites

Thats the first time  I am Install Clover Only UEFI on my Probook 4530s

 

I Install  Clover r3237 and this is great because everything working perfect

Thanks Slice and are Team for the great Bootloader

 

sans_t11.jpg

 

Boot time 3 sec is very fast :P  :D

I am very happy of this :thumbsup_anim:

Geekbench is verry good for an i3 2350m HD 3000

 

126.png

  • Like 1
Link to comment
Share on other sites

4530s has been confirmed to work with Clover UEFI since the release of 10.9.0 2 years ago.

Hi poke  

I know that but my last attempt to make Clover UEFI Install not working = ( mystery ) 

thats why  I am alway Install chameleon  since to 2010  :)

Link to comment
Share on other sites

×
×
  • Create New...