Jump to content

Need help fixing intel hd 3000 graphics on high sierra


Alan Sojan
 Share

19 posts in this topic

Recommended Posts

Hi, does anyone know how to fix the Intel hd 3000 graphics on High Sierra?

I have tried with whatever green and lilu kext but it won't work..

 

 

Specifications:

Toshiba Satellite R850-13k 

Intel HD 3000 

Intel Core i3-2310m 

 

16587798124134948367692240662976.jpg

Edited by Alan Sojan
Link to comment
Share on other sites

11 hours ago, Hervé said:

@ricoc90 All incorrect in usage, value and syntax... See the WEG user manual.

 

No need to set InjectIntel to true, it's been deprecated for years. Whatevergreen (PlugIn of Lilu kext) takes care of it.

 

All you need to obtain graphics acceleration for HD3000 is:

1) inject the following property against iGPU @2, i.e. device location/address PciRoot(0x0)/Pci(0x2,0x0) (though this is considered/stated optional if you use the correct MBP8,x SMBIOS):

AAPL,snb-platform-id        00000100        DATA      // for layout id 0x00010000

2) use MacBookPro8,1 SMBIOS

 

ID: SNB0 0x10000, STOLEN: 0 bytes, FBMEM: 0 bytes, VRAM: 0 bytes, Flags: 0x00000000
TOTAL STOLEN: 0 bytes, TOTAL CURSOR: 1 MB, MAX STOLEN: 0 bytes, MAX OVERALL: 1 MB (1064960 bytes)
Camellia: CamelliaUnsupported (255), Freq: 1808 Hz, FreqMax: 1808 Hz
Mobile: 1, PipeCount: 2, PortCount: 4, FBMemoryCount: 0
[5] busId: 0x03, pipe: 0, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS
[2] busId: 0x05, pipe: 0, type: 0x00000400, flags: 0x00000007 - ConnectorDP
[3] busId: 0x04, pipe: 0, type: 0x00000400, flags: 0x00000009 - ConnectorDP
[4] busId: 0x06, pipe: 0, type: 0x00000400, flags: 0x00000009 - ConnectorDP
05030000 02000000 30000000
02050000 00040000 07000000
03040000 00040000 09000000
04060000 00040000 09000000

image.jpeg

 

 

OS X/macOS allocates HD3000 VRAM according to the amount of RAM present in the laptop. In your case, with 8GB of RAM, VRAM will be set to 512MB.

Please note that, on Hackintosh platforms, HD3000 is a little buggy with all OS X/macOS versions past Yosemite 10.10. Over time, you won't avoid horizontal lines across your screen + random pixelisation. No fix whatsoever, you'll have to live with these defects that a reboot solves (temporarily of course).

 

What's your screen resolution by the way? 1366x768?

Hi, sorry I'm very new to this and I don't know how I should inject the PciRoot. Could you help me?

The screen resolution is  1366x768

16588303962005619075400599555974.jpg

Link to comment
Share on other sites

5 minutes ago, Hervé said:

Your Google drive is locked and not public/opened to everyone...

 

Your property injection against PciRoot(0x0)/Pci(0x2,0x0) looks fine though I invite you to remove the device_type and model properties the are not required.

The other thing you must remove is the line in the Add Properties section above:

IntelGFX      AAPL,snb-platform-id        10000300        DATA

Then make sure you use MacBookPro8,1 SMBIOS.

 

What version of Clover are you using?

Hi, I will reupload it on Google drive and give you permissions. Now I am using Macbook Pro 8,1 SMBIOS. The clover version I am using is version 2.4k rev 4630.

16588342796645152770142273914525.jpg

Link to comment
Share on other sites

1 hour ago, Hervé said:

Ok, got it.

 

The EFI Folder you posted on your Google drive does not reflect what you post as picture attachments. You probably have a duff or corrupt config or a version of CC that's not compatible with your Clover version r4630. The EFI you posted does not even contain the CPU Power Management SSDT which is required for Sandy Bridge and Ivy Bridge platforms or a PNLF SSDT. I've got a funny feeling you're not actually working on the Clover setup in your EFI partition but somewhere else!

 

Here's what I suggest you do:

  1. keep a backup of your existing Clover setup.
  2. update Clover to, say, r5133. Clover_r5133.pkg.zip
  3. using Clover Configurator app, mount the EFI partition of the disk on which you installed Catalina
  4. in the EFI/CLOVER folder, replace your config file + kexts & ACPI folders with those included in this zipped archive: Toshiba_archive.zip

I trust the installation you made was a full vanilla, not a distro.

 

I started afresh to make a clean Clover setup:

Patched ACPI tables:

  • added i3-2310M specific CPU power management SSDT table; this in order to gain full and proper CPU speedstep
  • added PNLF SSDT table; this in order to gain screen brightness on HD3000 graphics

Kexts:

  • Refreshed Lilu + AppleALC & Whatevergreen kexts to latest version (or thereabout)
  • Removed NullCPUPowerManagement kext; you want CPU power management for obvious reasons

Config:

  • ACPI section: complete review done, removing all those unnecessary options you had selected and adding what is usually required on this type of Sandy Bridge laptop
  • Devices section: injected the appropriate device property for HD3000 iGPU; you'll have to inject the rest afterwards (eg: audio, SD card reader, wireless, LAN, etc.) as required
  • Kernel & Kext Patches: adjusted the settings as required for a Sandy Bridge laptop (Apple RTC + AICPUPM patches enabled)
  • SMBIOS: picked MacBookPro8,1 and renewed all serial numbers
  • Rt Variables: renewed ROM + MLB values (needed for iMessages and other apps) and set BooterConfig (0x28) + CsrActiveConfig (0xFEF) to disable SIP
  • System Parameters: generated a new Custom UUID and enabled Inject Kexts parameter

 

Hopefully, you should have a bootable Catalina build with full graphics acceleration on this laptop.

Should I try and reinstall High Sierra?

Link to comment
Share on other sites

Guest ricoc90

"Hi, yes this is vanilla not using any distros"
"OP had deleted all the AMD/Intel/nVidia graphics kexts from /S/L/E in the belief that Lilu and Whatevergreen would perform some kind of magic"


Hmm.
I know a certain distro that advises their users to delete these kexts if their graphics aren't working. So i'll just leave a message here for anyone that comes across this post via searching: Don't.

Link to comment
Share on other sites

  • 1 year later...
2 hours ago, Евгений Евтушенко said:

There is no option to turn it off in the BIOS

For now use -wegnoegpu bootarg with WhateverGreen.kext

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...