Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

arsradu
arsradu
Posted
Posted

 


The reboot problem could also be due to some compatibility problem between the Clover launch daemon (/Library/LaunchDaemons/com.projectosx.clover.daemon.plist) &/or the shutdown script (private/etc/rc.boot.d/rc.shutdown.d/80.save_nvram_plist.local) and Yosemite DP2.  I'm not so sure it is DSDT related because

 

1. You didn't have the problem before you installed the RC scripts (and Clover launch daemon)

2. You can shutdown properly using the terminal command

sudo shutdown -h now

as opposed to shutting down from the Apple menu which might allow the Clover launch daemon to do something on your system that Yosemite DP2 doesn't like.

=================================================================================================================================

 

Hey man

Thank you so much for the detailed explanation. I haven't got the time to try everything. But since I was planning on doing that anyway, I did one thing though. I installed Mavericks (10.9.4), with Clover, in UEFI mode. And the results are pretty interesting.
Check this out:
1. I'm pretty sure Clover just updated a few stuff when installing it for Mavericks HDD partition. And I'm pretty sure that, since there is only one EFI partition/disk, all I would have ever needed to do, since I already have it installed for Yosemite (in EFI), is to add FakeSMC.kext (and,eventually, NullCPUPowerManagement.kext) into the 10.9 folder of Clover. Since everything else is pretty much the same. Not sure how important that EFI-Backups folder that was added upon Clover installation in my Mavericks partition, really is. Anther proof to this is that, when I opened up the EFI partition to add FakeSMC.kext into Clover's /kexts folder, the 10.10 folder, from my Yosemite installation, was already present. And as you already know, Clover 2721 doesn't add that folder automatically. But anyway, I installed it the old fashion way, using the Clover installer. Of course I selected exactly the same things I did for Yosemite. And I shut down my system.
Guess what? It went into complete shutdown, just as it should -> the reboot problem on Yosemite is not caused by the RC scripts.
2. You'll like this one. :) With no nvram.plist on my Mavericks' root location, I was able to login to iMessage with no issues. This is crazy! :)) So the hook wasn't necessary after all? Or is it not necessary in Mavericks? Just for Yosemite DP2? By the way, under the same circumstances (no nvram.plist), when I boot up from HDD, the Mavericks partition is remembered, as it should.

After all this, I'm kinda scared to remove the nvram.plist file from Yosemite and see what happens. I'll make a backup of it anyway, but even so, I'm not so sure I want to do this if it's not really necessary. What do you think about these results and about moving nvram.plist from Yosemite? The .plist files are configuration files, right? So the nvram.plist is a configuration file for nvram. But, after everything I wrote above, do you still think it's necessary? I'm looking forward to your opinion on this.

One last thing (related to Clover, but not related to my reboot problem): Mavericks or Yosemite, I don't have a boot logo. On Mavericks, I also don't have the loading animation, the spinning wheel (if that's what should be displayed for this case). It's just a black screen all the way to the login screen, which, the first time I booted Mavericks, was kinda scary, cause I thought I did something wrong (or forgot to do something) and it will never boot up. But it did. Just...with no boot screen.

Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted

@arsradu,

 

@pokenguyen's logout hook is only necessary in Yosemite DP2 - Clover's default launch daemon & shutdown script to save NVRAM are working well in other OSX versions.  Your findings suggest a problem caused by bugs in Yosemite DP2 and its interaction with your system.

 

Are you sure that there is no nvram.plist file on your Mavericks volume, only on Yosemite?  If so, I guess it is using the nvram.plist on the Yosemite partition and that file is getting updated (check its time stamp).  Personally, I would not delete it because I know what a headache it can be to get iMessages working again when it goes awry :).

 

The EFI-backups folder on the targetted partition is normal and done for safety's sake (I would leave it alone but it is not strictly necessary).  When you install Clover "for UEFI booting only", the EFI folder in the ESP is updated and a backup copy is placed in a EFI-Backups folder on the targetted partition.  The steps you took to place FakeSMC.kext + other necessary kexts in the EFI/EFI/Clover/Kexts/10.9 are correct (another way is to put FakeSMC in the "Other" folder and delete 10.6-10.10 folders ---> this injects the same kexts for all OSX versions).

 

The boot logo is a strange thing and I don't think it is fully understood why it shows on some systems and not others.  On both of my legacy systems (desktop GA-P55aUD3 with Radeon 5770, Laptop Dell XPSm1530 nVidia 8600GT), the Apple logo appears on a white screen with loader going all the way to completion.

 

Anyway good luck with your experiments but make sure to make full time-machine backups etc :).

 

PS NullCPUPowerManagement is not necessary with a properly patched DSDT and I would recommend getting rid of it since it prevents proper power management and sleep.

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

@arsradu,

 

@pokenguyen's logout hook is only necessary in Yosemite DP2 - Clover's default launch daemon & shutdown script to save NVRAM are working well in other OSX versions.  Your findings suggest a problem caused by bugs in Yosemite DP2 and its interaction with your system.

 

Are you sure that there is no nvram.plist file on your Mavericks volume, only on Yosemite?  If so, I guess it is using the nvram.plist on the Yosemite partition and that file is getting updated (check its time stamp).  Personally, I would not delete it because I know what a headache it can be to get iMessages working again when it goes awry :).

 

The EFI-backups folder on the targetted partition is normal and done for safety's sake (I would leave it alone but it is not strictly necessary).  When you install Clover "for UEFI booting only", the EFI folder in the ESP is updated and a backup copy is placed in a EFI-Backups folder on the targetted partition.  The steps you took to place FakeSMC.kext + other necessary kexts in the EFI/EFI/Clover/Kexts/10.9 are correct (another way is to put FakeSMC in the "Other" folder and delete 10.6-10.10 folders ---> this injects the same kexts for all OSX versions).

 

The boot logo is a strange thing and I don't think it is fully understood why it shows on some systems and not others.  On both of my legacy systems (desktop GA-P55aUD3 with Radeon 5770, Laptop Dell XPSm1530 nVidia 8600GT), the Apple logo appears on a white screen with loader going all the way to completion.

 

Anyway good luck with your experiments but make sure to make full time-machine backups etc :).

 

PS NullCPUPowerManagement is not necessary with a properly patched DSDT and I would recommend getting rid of it since it prevents proper power management and sleep.

Ok, I won't delete it.

 

Yes, I'm pretty sure there is no nvram.plist on Mavericks. I can't take a screenshot right now since I'm not at home anymore, but I could try and get one tonight, when I get back home. Can it use the nvram.plist when I'm not booted into that partition? That's interesting.

Ok, I'll remove the NullCPUPowerManagement kext. I tried to boot without it before and nothing bad happened. So I guess, at least for me, it would be safe to remove. So thank you very much for that info.

About the Others folder in Clover...I didn't know that! That's pretty cool, especially for multi-booting. I actually only need FakeSMC in order to boot. Nothing else. Which is nice. :)

 

About the logos....man, I wish I could bring more light into this... I'm here if anyone needs anything. But I'm not sure where to start debugging this issue. So not sure what kind of info would be necessary for anyone to fix this.

Link to comment
Share on other sites
xhala_debru
xhala_debru
Posted
Posted

 

It is readable enough.

See

1:860  0:000    found entry 2. 'Boot Mac OS X from Mavericks_250_Sata', Volume 'Mavericks_250_Sata'
1:860  0:000  Boot redirected to Entry 2. 'Boot Mac OS X from Mavericks_250_Sata'

Is it that you want?

 

In this place

		<key>DefaultVolume</key>
		<string>HD(1,GPT,A8E466E1-9563-30A0-988E-3357B8353895,0x800,0xFF000)</string>

must be NAME, for example


		<key>DefaultVolume</key>
		<string>Mavericks_250_Sata</string>

Hi,

 

Actually, it's Mavericks_SSD I'd like Clover to boot on.

And I had already tried  that with no luck

        <key>DefaultVolume</key>

        <string>Mavericks_SSD</string>

 

Mavericks_250_Sata being the drive Clover always wants to boot to no matter what when reading nvram (<key>IgnoreNVRAMBoot</key> set to false)

 

Strange thing is that when I print the nvram of my system (nvram -p), the variables of the system do point  (Clover.MountEFI and efi-boot-device) towards Mavericks_SSD

 

Thank you anyway, with the option <key>IgnoreNVRAMBoot</key>

<true/> in config.plist, I'm able to boot on it
 
System seems stable, I've been able to update all my Apps, so far so good  :)
Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

Would it be possible to add the functionality of AHCIPortInjector to Clover at some point? I use it on my X79 to inject device names for the three different sata controllers (which show up as "unknown ahci controller" otherwise).

 

One less kext is always good and Clover already does quite a bit of injection already.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Second level devices can't be injected at boot time because system Bus drivers (USB, SATA) will created new device description forgetting the description written by a bootloader.

A kext is only solution.

Link to comment
Share on other sites
scott_donald
scott_donald
Posted
Posted

where is the language stored in clover config etc??? copied Fabio's config for my board and it has made my default language Italian....

 

changed the language in Settings a while back but just redid a new test drive and problem still there... 

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

where is the language stored in clover config etc??? copied Fabio's config for my board and it has made my default language Italian....

 

changed the language in Settings a while back but just redid a new test drive and problem still there...

Did you try opening up config.plist (in EFI/EFI/CLOVER/config.plist) with TextEdit (default text editor) and setting the language to en, as such?

 

<key>Language</key> 
<string>en:0</string>
  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Try not to edit with text editor to avoid errors but with plist editor(google).

For changing from "it" (probably) to "en:0", I guess he can use any text editor, since it's just a word. I actually never had any issues with the default TextEdit. I mean, it's not like Notepad in Windows, which sucks for anything else other then writing hate mail to Microsoft. But I'll try that plist editor that you mentioned. Thank you. :)
Link to comment
Share on other sites
scott_donald
scott_donald
Posted
Posted

Did you try opening up config.plist (in EFI/EFI/CLOVER/config.plist) with TextEdit (default text editor) and setting the language to en, as such?

 

<key>Language</key> 
<string>en:0</string>

 

doh... i was being dumb just noticed that!!!

 

Try not to edit with text editor to avoid errors but with plist editor(google).

 

thanks... use a plist editor... 

Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

My resolution is fine once I boot to desktop but the resolution is wrong at the boot prompt.  I am using bootcamp theme is there a way to increase the resolution maybe with nvram setting?  Not sure if this parameter can be written to nvram?

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

My resolution is fine once I boot to desktop but the resolution is wrong at the boot prompt.  I am using bootcamp theme is there a way to increase the resolution maybe with nvram setting?  Not sure if this parameter can be written to nvram?

	<key>GUI</key>
	<dict>
		<key>ScreenResolution</key>
		<string>1440x900</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>CustomEDID</key>
		<data>AP///////wAyDADfAAAAAAASAQOAIRV4CunVmVlTjigmUFQAAAABAQEBAQEBAQEBAQEBAQEB3iGgcFCEHzAgIFYAS88QAAAY3iGgcFCEHzAgIFYAS88QAAAAAAAA/gBXNjU3RwAxNTRXUDEKAAAA/gAjMz1IZYSq/wIBCiAgAJo=</data>
		<key>InjectEDID</key>
		<true/>
		<key>PatchVBios</key>
		<true/>
	</dict>
Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted 
	<key>GUI</key>
	<dict>
		<key>ScreenResolution</key>
		<string>1440x900</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>CustomEDID</key>
		<data>AP///////wAyDADfAAAAAAASAQOAIRV4CunVmVlTjigmUFQAAAABAQEBAQEBAQEBAQEBAQEB3iGgcFCEHzAgIFYAS88QAAAY3iGgcFCEHzAgIFYAS88QAAAAAAAA/gBXNjU3RwAxNTRXUDEKAAAA/gAjMz1IZYSq/wIBCiAgAJo=</data>
		<key>InjectEDID</key>
		<true/>
		<key>PatchVBios</key>
		<true/>
	</dict>

 

 

Thanks for helping.  Would the CustomEDID change if I wanted a higher resolution, 1920x1080?

 

For some odd reason it lowered the resolution even more and the text and bootcamp prompt is now even larger.

 

 

Edited:

 

I see that it can't set the 1920x1080 because log says its not found?  I see its setting it to 800x600.

0:348  0:001  Loading FSInject-64.efi
0:349  0:000  Loading OsxAptioFixDrv-64.efi
0:350  0:001  Loading OsxFatBinaryDrv-64.efi
0:351  0:000  Video bios patch requested or CustomEDID - forcing video reconnect
0:351  0:000  2 drivers needs connecting ...
0:351  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
0:351  0:000  Video driver loaded: disconnect Success
0:415  0:063  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:415  0:000  VideoBiosPatchNativeFromEdid:
0:415  0:000   Bios: nVidia, nv_data_table_offset: 0x2B5, nv_data_table: 0xC02B7, std_vesa: 0xC4465, nv_mode_table: 0xC446A, mode_table_size: 0x10
0:415  0:000   VideoBiosPatchInit(LegacyRegion = Success) = Success
0:415  0:000   VideoBiosUnlock:  unlocked
0:417  0:002   Patching: BT_NVDA
0:417  0:000   Parse Edid: descriptor block 0 is timing descriptor (h_active: 1440, v_active: 900, h_sync_offset: 32, h_sync_width: 32, h_blanking: 112, v_blanking: 31, pixel_clock: 8670, v_sync_offset: 5, v_sync_width: 6)
0:418  0:000   patch 0: patched 1 time(s)
0:418  0:000   patch 1: patched 1 time(s)
0:419  0:000   patch 2: patched 1 time(s)
0:420  0:000   patch 3: patched 1 time(s)
0:420  0:000   VideoBiosLock: Success
1:261  0:841  LoadDrivers() end
1:261  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
1:266  0:005  SetScreenResolution: 1920x1080 - not found!
1:266  0:000  Console modes reported: 4, available modes:
1:266  0:000    Mode 1: 80x25
1:266  0:000    Mode 3: 100x31 (current mode)
1:266  0:000    Mode 4: 128x40
1:266  0:000  SetScreenResolution: 800x600 - already set
1:266  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,54ED2158-BDF8-4FF2-BC80-5056F922678E,0x28,0x64000)
1:266  0:000  new SelfHandle=5975B118
1:266  0:000  CPU Vendor = 756E6547 Model=306C3
1:266  0:000  The CPU supported turbo
1:266  0:000  BrandString = Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
1:266  0:000  MSR 0xE2 before patch 1E000405
1:266  0:000  MSR 0xE4              00021814
1:266  0:000  MSR 0xCE              00080838_F3011800
1:266  0:000  non-usable FLEX_RATIO = 50000
1:266  0:000  corrected FLEX_RATIO = 40000
1:266  0:000  MSR 0x1B0             00000000
1:266  0:000  FSBFrequency=100MHz
1:266  0:000  Corrected FSBFrequency=100MHz
1:266  0:000  Vendor/Model/Stepping: 0x756E6547/0x3C/0x3
1:266  0:000  Family/ExtFamily: 0x6/0x0
1:266  0:000  MaxDiv/MinDiv: 24.0/8
1:266  0:000  Turbo: 32/32/33/34
1:266  0:000  Features: 0xBFEBFBFF
1:266  0:000  Threads: 8
1:266  0:000  Cores: 4
1:266  0:000  FSB: 100 MHz
1:266  0:000  CPU: 2400 MHz
1:266  0:000  TSC: 2400 MHz
1:266  0:000  PIS: 400 MHz

Edited Again:

 

This is the log before I do the edits as you had.  It cannot find 1920x1024 and sets the resolution higher in this instance.

0:408  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:586  0:177  LoadDrivers() end
0:586  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
0:592  0:006  SetScreenResolution: 1920x1080 - not found!
0:592  0:000  SetMaxResolution: found best mode 1: 1024x768Video mode change to mode #1: Success
0:748  0:155   - set
0:748  0:000  Console modes reported: 4, available modes:
0:748  0:000    Mode 1: 80x25
0:748  0:000    Mode 3: 100x31 (current mode)
0:748  0:000    Mode 4: 128x40
0:748  0:000  SetScreenResolution: 1024x768 - already set
0:748  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,54ED2158-BDF8-4FF2-BC80-5056F922678E,0x28,0x64000)
0:748  0:000  new SelfHandle=5975B118
0:748  0:000  CPU Vendor = 756E6547 Model=306C3
0:748  0:000  The CPU supported turbo
0:748  0:000  BrandString = Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
0:748  0:000  MSR 0xE2 before patch 1E000405
0:748  0:000  MSR 0xE4              00021814
0:748  0:000  MSR 0xCE              00080838_F3011800
0:748  0:000  non-usable FLEX_RATIO = 50000
0:748  0:000  corrected FLEX_RATIO = 40000
0:748  0:000  MSR 0x1B0             00000000
0:748  0:000  FSBFrequency=100MHz
0:748  0:000  Corrected FSBFrequency=100MHz
Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

You need to use CsmVideoDxe-64.efi driver in order for a non UEFI video card to function correctly, otherwise you only receive a few basic modes that must be supported in UEFI firmware such as 800x600 and 1024x768. You also need an EDID that correctly identifies the mode you want to set. The one that slice posted was for 1440x900 as it shows in your log. There are many tools that you can use to generate an EDID, then either convert it to base64 with <data> tag or hex with <string> tag.

 

 

That did it.  Just adding that driver gave me back the 1920x1024 resolution in console/boot menu.  I am already injecting in DSDT nvcap etc not sure why I don't need EDID injection?

0:699  0:205    0 640x480 attr=3BF - ok, 640x480, working, highest, pref=0
0:701  0:001    1 800x600 attr=3BF - ok, 800x600, working, highest, pref=1
0:703  0:001    2 1024x768 attr=3BF - ok, 1024x768, working, highest, pref=2
0:705  0:001    3 1280x1024 attr=3BF - ok
0:715  0:010    4 1920x1080 attr=3BF - ok
0:717  0:001    5 1280x800 attr=3BF - ok
0:717  0:000  CsmVideo: New mode: 2 1024x768 - set
0:881  0:163   - SetMode pref 2 (2) = Success
0:881  0:000  CsmVideoCheckForVbe - Success
0:881  0:000  CsmVideoDriverBindingStart end Success
0:881  0:000  CsmVideo: New mode: 1 800x600 - blocking that switch
0:881  0:000  CsmVideo: New mode: 0 640x480 - blocking that switch
1:050  0:168  LoadDrivers() end
1:050  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
1:056  0:005  SetScreenResolution: 1920x1080 - setting Mode 4
1:056  0:000  CsmVideo: New mode: 4 1920x1080 - set
1:364  0:308  Video mode change to mode #4: Success
1:364  0:000  Console modes reported: 4, available modes:
1:364  0:000    Mode 1: 80x25
1:364  0:000    Mode 3: 100x31 (current mode)
1:364  0:000    Mode 4: 128x40
1:364  0:000  SetScreenResolution: 1920x1080 - already set
1:364  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,54ED2158-BDF8-4FF2-BC80-5056F922678E,0x28,0x64000)

Edited again:

 

Does this basically mean my GTX 770m is not a UEFI card?  Any way to truly tell?

 

 

 

Edited again:

 

Now nothing makes sense.  I have another laptop exactly same model this one has Clover 2747 the logs above are from Clover 2750.  On this laptop I do not have the CSMVideoDXe64 installed.

0:328  0:026  Found theme __MACOSX - no theme.plist
0:329  0:000  Found theme MaverickLogin_4_3
0:331  0:002  Found theme MaverickLogin_16_9
0:341  0:009  Found theme Shield
0:410  0:068  Loading early settings
0:410  0:000  timeout set to 4
0:410  0:000  Default theme: bootcamp
0:410  0:000  Hiding entries with string \EFI\BOOT\BOOTX64.EFI
0:410  0:000  Hiding entries with string Windows
0:410  0:000  LoadDrivers() start
0:429  0:019  Loading HFSPlus.efi
0:440  0:011   - driver needs connecting
0:440  0:000  Loading OsxAptioFixDrv-64.efi
0:448  0:008  Loading EmuVariableUefi-64.efi
0:463  0:014  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
0:464  0:001  Loading FSInject-64.efi
0:479  0:014  1 drivers needs connecting ...
0:479  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:479  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:672  0:193  LoadDrivers() end
0:672  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent = Success, done
0:678  0:005  SetScreenResolution: 1920x1080 - already set
0:678  0:000  Console modes reported: 4, available modes:
0:678  0:000    Mode 1: 80x25
0:678  0:000    Mode 2: 80x50
0:678  0:000    Mode 3: 100x31
0:678  0:000    Mode 4: 128x40 (current mode)
0:678  0:000  SetScreenResolution: 1920x1080 - already set
0:678  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,60377C13-636F-41D7-948F-18F0C7709F2D,0x28,0x64000)
0:678  0:000  new SelfHandle=59466418
0:678  0:000  CPU Vendor = 756E6547 Model=306C3
0:678  0:000  The CPU supported turbo
0:678  0:000  BrandString = Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
0:678  0:000  MSR 0xE2 before patch 1E000405
Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

Do they have the same firmware versions? It appears that they are either not truly identical, which is entirely possible even when they are the same model, or you need to upgrade the firmware on one of them.

 

 

Both have the same windows driver/firmware.   I did not realize that the one that needs the CSMVideoDXE driver is the one on OSX 10.9.4 and the other that does not need it is on 10.9.3.  So that must be why.  Both on Clover 2751 now.

 

Thanks

Link to comment
Share on other sites
simconti
simconti
Posted
Posted
post-702252-0-80012500-1403470611_thumb.png
post-702252-0-59581100-1403470663_thumb.png

Hi, a help from you, you who are more experienced.

I have the problem for artifacts with Intel HD3000 integrated in my laptop... the problem occurs with both the Mavericks and Yosemite.

 

I have selected various combinations - EDID and configuration in the Clover.

I have not solved the problem.

 

Thanks to all for your help

Hi all,

obody has a solution, i'm sorry do not use Clover.....  :(

 

the problem is intermittent.

Link to comment
Share on other sites
Liliniser
Liliniser
Posted
Posted

Hi, a help from you, you who are more experienced.

I have the problem for artifacts with Intel HD3000 integrated in my laptop... the problem occurs with both the Mavericks and Yosemite.

 

I have selected various combinations - EDID and configuration in the Clover.

I have not solved the problem.

 

Thanks to all for your help

 

 

I used to have the same HD3000 artifact problem and I solved it by adding 'slide=0' into the Boot arguments. 

 

Not sure but why don't you give it a try.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

I used to have the same HD3000 artifact problem and I solved it by adding 'slide=0' into the Boot arguments. 

 

Not sure but why don't you give it a try.

I confirm, this is the trick.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...