Jump to content

Clover General discussion


ErmaC
29,869 posts in this topic

Recommended Posts

@Slice:

 

Something is wrong with Intel graphics injection. With the Intel HD3000 on my Dell, I get a white screen after boot.

 

The only way to fix it by disabling Clover's injection and adding: "AAPL,snb-platform-id", Buffer() { 0x00, 0x00, 0x01, 0x00 } to the DSDT.

 

Am I the only one having this issue?!!

Hi Dr.Hurt,

How you able to get debug.log from Clover? Did you mount the efi partition?

Link to comment
Share on other sites

 

@Slice how if the clover was installed in efi partition? After I make efi partition readable and I can take the debug.log,

will it cause my hard disk won't bootable anymore?

Sorry for my stupidness, I just read clover wiki and I found this... :

post-1295795-0-76018200-1393930735_thumb.jpg

Link to comment
Share on other sites

@Slice:

 

Something is wrong with Intel graphics injection. With the Intel HD3000 on my Dell, I get a white screen after boot.

 

The only way to fix it by disabling Clover's injection and adding: "AAPL,snb-platform-id", Buffer() { 0x00, 0x00, 0x01, 0x00 } to the DSDT.

 

Am I the only one having this issue?!!

So many people so many opinions.

Other people reported Clover injection is fine.

I don't know as I have no such card.

Sorry for my stupidness, I just read clover wiki and I found this... :

@Slice how if the clover was installed in efi partition? After I make efi partition readable and I can take the debug.log,

will it cause my hard disk won't bootable anymore?attachicon.gifimage.jpg

Why your hard drive is not bootable anymore? Did you propose debug.log will erase the partition???

  • Like 1
Link to comment
Share on other sites

thats NOT true.. PC UEFI booting is the only thing dependent on ESP. In Macs the EFI partition is generally only used for loading firmware updates and does not contain main boot files.

Link to comment
Share on other sites

Your graphics are unsupported and will never work correctly in OS X. You must add -v to see where your boot is stopping

So far no error and succeed load to installer, when load to installer I met that problempost-1295795-0-53664600-1393938683_thumb.jpg

Here is -v picture, what can you detect?post-1295795-0-31641900-1393938877_thumb.jpg

Link to comment
Share on other sites

So many people so many opinions.

Other people reported Clover injection is fine.

I don't know as I have no such card.

 

Just have a look at an ioreg from a real Mac with an HD3000 (MacBookPro8,1 for example). It has a "AAPL,snb-platform-id" key.

 

Clover only injects an ig-platform-id which doesn't work with Sandy Bridge.

 

I don't mean to upset you, Slice. I'm just trying to contribute to your excellent Clover project with what little I could :)

 

Thanks for all your work.

  • Like 3
Link to comment
Share on other sites

Just have a look at an ioreg from a real Mac with an HD3000 (MacBookPro8,1 for example). It has a "AAPL,snb-platform-id" key.

 

Clover only injects an ig-platform-id which doesn't work with Sandy Bridge.

 

I don't mean to upset you, Slice. I'm just trying to contribute to your excellent Clover project with what little I could :)

 

Thanks for all your work.

snb-platform-id only matches certain macbook model to certain connector table. by default macbookpro8,1 is matched to snb-platform 01 (first conenctor table in the framebuffer)... no need to inject what doesn't need to be there to work.

Link to comment
Share on other sites

snb-platform-id only matches certain macbook model to certain connector table. by default macbookpro8,1 is matched to snb-platform 01 (first conenctor table in the framebuffer)... no need to inject what doesn't need to be there to work.

 

Correct me if I'm wrong, but I think that Clover currently injects an ig-platform-id for the HD3000 which is probably why I get the white screen on boot.

Link to comment
Share on other sites

I'm using Intel inject with my HD3000 (Clover rev 2638) and I don't have that property injected.

 

Hmm, interesting!!

I never actually got the system to boot with inject intel enabled so I really don't know what is being injected!!

 

If it works for you then there must be something in my particular setup. Perhaps the switchable graphics.

 

Thanks for the info :)

Link to comment
Share on other sites

If it works for you then there must be something in my particular setup. Perhaps the switchable graphics.

If SNB is loading, your white screen is caused by a connector mismatch.

In my experiments, HD3000/Intel=YES, SNB does not load (Post 4006/2816-1)

 

SNB/AAPL,snb-platform-id works differently than Capri/Azul/AAPL,ig-platform-id. AAPL,snb-platform-id does not refer directly to the framebuffer. Credit: RevoGirl

 

The suggested HD3000 framebuffer injection is:

1. Desktop (macmini5): AAPL,snb-platform-id = 0x10000300

SNB framebuffer:

0x00020300

DP, DP, HDMI

0002030000000000ffffffff

020500000004000007000000

030400000004000009000000

040600000008000006000000

000000000100000040000000

 

2. Laptop (macbookpro8), AAPL,snb-platform-id = 0x10000300

SNB framebuffer:

0x01020400

LVDS, DP, DP, DP

010204001007000010070000

050300000200000030000000

020500000004000007000000

030400000004000009000000

040600000004000009000000

  • Like 1
Link to comment
Share on other sites

People who followed my guide running Inspirons and Vostros with AMD SG use MacBooPro8,1 model identifier. IGPU by default has _DSM with OEM properties, so HD3000 injection via DSDT is not possible (and Clover won't properly drop _DSM on that device for some reason.. not going into this right now). The only way they inject HD3000 is by using Intel inject with Clover. It allows for HDMI audio to work ("onboard-1" property finally fixed after being broken for ages) as well as enables the graphics. In my experiments with HD3000 back in early 2012 I have found that I didn't even need to inject anything as long as GFX0 was renamed to IGPU (to allow for AGPM) and model was set to MBP8,1.. SNB frambuffer would load by its own then.

Link to comment
Share on other sites

I want to install Mavericks, does Fakesmc.kext has 32bit or 64bit version? If it doesn't have I think I can use backe my old fakesmc.kext

 

since OS X Lion, Mavericks is 64 bits only, so FakeSMC is 64 bits too.

Link to comment
Share on other sites

@Dr Hurt et al

re: HD 3000 snb-product-id 

 

FWIW,

 

i have 2 hacks with Intel HD 3000. 

 

1) snb-platform-id NOT set - Lenovo T420 with i5-2520M using MBP8,1 model and custom DSDT -  note: snb-platform-id does not show in ioreg -l)

2) snb-platform-id IS set     - custom-mini with i3-2125 (clover thinks it is a HD 2000 btw OSX figures it out to be 3000) but i do set property snb-platform-id to 10000300 in the custom DSDT since i use macpro3,1 model instead of typical macmini5,1 for sound reasons (power alway on). I use clover to kext patch SNBGraphics down to single HDMI buffer to eliminate artifacts. this is where the ID is handy to know which table to mod.

Link to comment
Share on other sites

I use clover to kext patch SNBGraphics down to single HDMI buffer to eliminate artifacts

 

Would you be so kind as to share that patch? I don't really use the HD3000 output but I do enable it for the graphics acceleration and now and then I've noticed some artifacts on videos.

Link to comment
Share on other sites

@maniac10 - sure.

 

caveat: I am not at home to get access to that system for a few days --  but here is what it would look like - i do something similar for my laptop. i recall i patched the 3rd table and the HDMI port was the 2nd buffer (0304 line) -- there was a bit of trial and error until i got it right! 

 

 

find

0002030000000000ffffffff020500000004000007000000030400000004000009000000040600000008000006000000000000000100000040000000

replace

0002010000000000ffffffff030400000004000009000000000000000100000040000000000000000100000040000000000000000100000040000000

 
config.plist section (sorry cut/paste lost the white space!)

 

<key>KernelAndKextPatches</key>

<dict>

<key>AppleRTC</key>

<true/>

<key>AsusAICPUPM</key>

<true/>

<key>Debug</key>

<false/>

<key>KextsToPatch</key>

<array>

<dict>

<key>Comment</key>

<string>Reduce to 1 port</string>

<key>Find</key>

<data>

AAIDAAAAAAD/////AgUAAAAEAAAHAAAAAwQAAAAEAAAJ

AAAABAYAAAAIAAAGAAAAAAAAAAEAAABAAAAA

</data>

<key>Name</key>

<string>AppleIntelSNBGraphicsFB</string>

<key>Replace</key>

<data>

AAIBAAAAAAD/////AwQAAAAEAAAJAAAAAAAAAAEAAABA

AAAAAAAAAAEAAABAAAAAAAAAAAEAAABAAAAA

</data>

</dict>

</array>

</dict>

 
partial cut/paste of script with first 3 of 8  buffers converted to hex 

 

using offset=173552

 

dd if=${dir}/AppleIntelSNBGraphicsFB of=table bs=1 skip=$offset count=480

480+0 records in

480+0 records out

480 bytes transferred in 0.001274 secs (376804 bytes/sec)

xxd -c 12 < table > hex

 

 

tluck@Toms-Mac /Extra/OSX-build/T420-pieces/SNBGraphics-vga-fix

$ cat hex

0000000: 0102 0400 1007 0000 1007 0000  ............

000000c: 0503 0000 0200 0000 3000 0000  ........0...

0000018: 0205 0000 0004 0000 0700 0000  ............

0000024: 0304 0000 0004 0000 0900 0000  ............

0000030: 0406 0000 0004 0000 0900 0000  ............

000003c: 0102 0100 1007 0000 1007 0000  ............

0000048: 0503 0000 0200 0000 3000 0000  ........0...

0000054: 0000 0000 0100 0000 4000 0000  ........@...

0000060: 0000 0000 0100 0000 4000 0000  ........@...

000006c: 0000 0000 0100 0000 4000 0000  ........@...

0000078: 0002 0300 0000 0000 ffff ffff  ............

0000084: 0205 0000 0004 0000 0700 0000  ............

0000090: 0304 0000 0004 0000 0900 0000  ............

000009c: 0406 0000 0008 0000 0600 0000  ............

00000a8: 0000 0000 0100 0000 4000 0000  ........@...

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...