Jump to content
30960 posts in this topic

Recommended Posts

i tested snow leopard boot.

 

OsxAptioFixDrv

-snow boot no problem

-native nvram - works

 

OsxAptioFix2Drv

-lead to get memory allocation error

-native nvram - works

 

my sandy laptop show that OsxAptioFixDrv is best.

hd 3000 is no problem on hp 4230s

  • Like 2

 

hd 3000 is no problem on hp 4230s

 

No weird horizontal lines from time to time, specially in web browsers when you have many tabs and apps open? 

 

What's your SMBIOS? Can you share your config / DSDT?

 

Thanks in advance.

i tested snow leopard boot.

 

OsxAptioFixDrv

-snow boot no problem

-native nvram - works

 

OsxAptioFix2Drv

-lead to get memory allocation error

-native nvram - works

 

my sandy laptop show that OsxAptioFixDrv is best.

hd 3000 is no problem on hp 4230s

 

You must use old AptioFix or AptioFix2 pre r4369 for anything older than ML.

 

EDIT: Also just don't use AptioFix after r4369 at all. It will produce side effects.

No weird horizontal lines from time to time, specially in web browsers when you have many tabs and apps open? 

 

What's your SMBIOS? Can you share your config / DSDT?

 

Thanks in advance.

 

I will go weeks, then for days have artifacts, then fine again. Currently I can't even get my HD3000 to work right. It is not injected properly and I can't figure out why.

  • Like 1

No weird horizontal lines from time to time, specially in web browsers when you have many tabs and apps open?

 

What's your SMBIOS? Can you share your config / DSDT?

 

Thanks in advance.

UEFI, only intel inject, macbookpro8,1, slide=0

 

나의 LG-F800S 의 Tapatalk에서 보냄

You must use old AptioFix or AptioFix2 pre r4369 for anything older than ML.

 

EDIT: Also just don't use AptioFix after r4369 at all. It will produce side effects.

 

 

I will go weeks, then for days have artifacts, then fine again. Currently I can't even get my HD3000 to work right. It is not injected properly and I can't figure out why.

Thank you for advice

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1

Quick question:

 

At least in theory, would it be possible for Clover (and / or some connected UEFI drivers) to update the CPUs microcode?

 

Yeah, if you have the microcode update, I don't see why it couldn't. The operating system is able to do this, linux does, look at the proprietary drivers in use in say ubuntu.

  • Like 1

Well, I think you might guess why I am asking this. So, there are new microcode updates for many Intel CPUs fixing (at least partially, likely it is more a mitigation than a real fix) those nasty security issues. And yes, I know you can update the microcode using Linux. But AFAIK this is not persistent. When I understand this correctly, you usually need a BIOS update to make it more persistent, but I doubt there will be many esp for older boards.

 

So, what about delegating this to clover? I.e. a user would download the microcode update (for example here: https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File) and a UEFI module/driver will take care of doing the update?

 

By this way, we would have mitigation for many Hacks where it wouldn't be possible otherwise. And of course not everyone is on 10.13 ...

Well, I think you might guess why I am asking this. So, there are new microcode updates for many Intel CPUs fixing (at least partially, likely it is more a mitigation than a real fix) those nasty security issues. And yes, I know you can update the microcode using Linux. But AFAIK this is not persistent. When I understand this correctly, you usually need a BIOS update to make it more persistent, but I doubt there will be many esp for older boards.

 

So, what about delegating this to clover? I.e. a user would download the microcode update (for example here: https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File) and a UEFI module/driver will take care of doing the update?

 

By this way, we would have mitigation for many Hacks where it wouldn't be possible otherwise. And of course not everyone is on 10.13 ...

 

Yeah, it's not persistent unless it's flashed with the firmware. Only SOME CPUs can be microcode updated to MITIGATE the problem in conjunction with the actual separating of the kernel and user space so it's no longer possible to attack by side-channeling. The separating of the memory spaces is really what will protect from the vulnerability, as well as Intel saying that all accesses of this nature should have a serializing instruction to prevent speculation.

 

 ive been wondering the same thing. any chance somehere could tell us how to implement a microcode update (made for linux) with clover that would be awesome! 

 

I'm not sure it makes much sense. It alone is not going to protect from the vulnerability, because the problem is in the actual silicon of the chip, so the memory map can be side-channeled through speculation. The memory map needs to be separated from any other memory map if you want to not have this vulnerability.

 

How are you doing with the graphical glitches of the HD3000? do you have any??

 

I have 2 systems with HD 3000 and my experience is that glitches and/or gfx artifacts (random black lines/spots etc) can be caused by an improper EDID - or conversely fixed by an alternate/proper EDID. without going into detail, besides EDID there are other causes of glitches and there are plenty of other threads that discuss this topic.

I have 2 systems with HD 3000 and my experience is that glitches and/or gfx artifacts (random black lines/spots etc) can be caused by an improper EDID - or conversely fixed by an alternate/proper EDID. without going into detail, besides EDID there are other causes of glitches and there are plenty of other threads that discuss this topic.

My laptop with i5-2410M with HD3000 have glitches and have no way to freak with even with Edie injection.

 

Only way is downgrade to osx10.11.3 or early and with slide=0 can solve this problem.

 

After OSX10.11.4 the slide=0 with no use to solve the glitches on HD3000 and I tried every method such as use MacBookPro8,1 properties and inject vbios or inject edid but still have no success.

 

So I brought a new laptop...............

 

But I still want to solve this problem.

 

Rehabman said it may be related with DVMT but HD3000 how to change DVMT?

 

And VBIOS I can’t inject Intel graphics vbios through Clover.

 

Now I hope some one can work into this graphic.

 

 

HD OK

HD2000 OK

HD3000 Glitches

HD4000 OK

 

Only HD3000 have this problem and I don’t know why.

 

I have tried all my best and tried all method I can thought.

 

 

从我的 iPhone 发送,使用 Tapatalk

Both my computers #1 and #2 work fine with NVRAM with new AptioFix2.

Congratulations to whom concerned!

Hello Slice.

 

SourceForge have changed style and I suppose to upload an new high resolution icon about Clover.

 

Thanks and good evening.

 

 

从我的 iPhone 发送,使用 Tapatalk

I really have enough now of High Sierra. So much software is buggy, laggy, unstable now. nvidia graphics driver behaviour is weird. Maybe I'll try the new security patch if the recent nvidia arrives. But I think that it will be the same. So going back to a solid and stable 10.12.6 pre-spectre.

I have 2 systems with HD 3000 and my experience is that glitches and/or gfx artifacts (random black lines/spots etc) can be caused by an improper EDID - or conversely fixed by an alternate/proper EDID. without going into detail, besides EDID there are other causes of glitches and there are plenty of other threads that discuss this topic.

 

Been there, done that.

 

I extracted my EDID from linux and injected it in Clover and faked the display ID to match the Color LCD of the Macbook (610 9cf2) and love the Color profile. The default is too cool (bluish)  for my taste.

 

I still get some glitches with the EDID injection.

I'm not sure it makes much sense. It alone is not going to protect from the vulnerability, because the problem is in the actual silicon of the chip, so the memory map can be side-channeled through speculation. The memory map needs to be separated from any other memory map if you want to not have this vulnerability.

 

So you would say patching the microcode alone is useless? I was under the impression that it would be better than nothing. At least its the code that runs directly on the CPU, so it should help at least a bit. Of course since  this bug is deeply rooted in the hardware and cannot be really fixed, the only solution is to redesign the chips itself. But that could take quite some time, so ANY mitigation in the meantime would be welcome. I think I understand at least a bit how the exploit works, and I would say it is one of the worst things I ever saw.

So you would say patching the microcode alone is useless? I was under the impression that it would be better than nothing. At least its the code that runs directly on the CPU, so it should help at least a bit. Of course since  this bug is deeply rooted in the hardware and cannot be really fixed, the only solution is to redesign the chips itself. But that could take quite some time, so ANY mitigation in the meantime would be welcome. I think I understand at least a bit how the exploit works, and I would say it is one of the worst things I ever saw.

 

I would say that most likely it's just adding additional instructions to CPUs like PCIDs or something similar to make the performance hit less. The problem lies in the architecture, in the pipeline of the cpu, even the microcode has to be executed in the pipeline - everything does. The vulnerability is that the pipeline tries to make predictions based on speculation of previous instructions, it however does not verify the privilege domain and can be allowed to execute instructions from say the user domain in the kernel domain, etc. This even allows a virtual machine to attack the host machine.... Search google for "cache side-channel attack".

 

I really have enough now of High Sierra. So much software is buggy, laggy, unstable now. nvidia graphics driver behaviour is weird. Maybe I'll try the new security patch if the recent nvidia arrives. But I think that it will be the same. So going back to a solid and stable 10.12.6 pre-spectre.

 

I think it will stabilize out but truthfully why would you go back to a state that has a known vulnerability that could be exploited?

 

Usually got kernelcache erros with new aptiofix 2 using clover 4369. Had to boot twice at minimum for system to go forward.

 

Select a slide value.

Been there, done that.

 

I extracted my EDID from linux and injected it in Clover and faked the display ID to match the Color LCD of the Macbook (610 9cf2) and love the Color profile. The default is too cool (bluish)  for my taste.

 

I still get some glitches with the EDID injection.

 

i did the same thing for the color profile. different topic.  but it sounds like means you injected/used the same built-in EDID from the LCD that macOS finds. i am talking about replacing the built-in EDID with a modified EDID. can be done with DSDT and/or Clover. That is a use a EDID with different timings, blanking time, spacing etc. the standard LCD edid glitches like crazy and eventually get total gfx freeze (BRSNC in log etc). my guide for Lenovo T420 has examples. I also use EDID with just RGB mode so now I don't get acid wash color flicker on certain apps - was getting that using LCD+External. (thanks vusun).

 

High Sierra does seem more prone to HD 3000 gfx issues -  as i ran artifact free fro about 3 or 4 years on 10.10, 10.11 and 10.12 without issue. but all of sudden High Sierra has issues?! For example, I was using EDID injection on my mini-mac5 hack for years now by adding AAPL00,override-no-connect "trick" for headless boot - but had to remove that otherwise i get wicked artifacts. oh well.

  • Like 1

I would say that most likely it's just adding additional instructions to CPUs like PCIDs or something similar to make the performance hit less. The problem lies in the architecture, in the pipeline of the cpu, even the microcode has to be executed in the pipeline - everything does. The vulnerability is that the pipeline tries to make predictions based on speculation of previous instructions, it however does not verify the privilege domain and can be allowed to execute instructions from say the user domain in the kernel domain, etc. This even allows a virtual machine to attack the host machine.... Search google for "cache side-channel attack".

 

 

I think it will stabilize out but truthfully why would you go back to a state that has a known vulnerability that could be exploited?

 

 

Select a slide value.

Not working, same behaviour. Replaced osxaptiofix2drv from Clover r4334. All good!

i did the same thing for the color profile. different topic.  but it sounds like means you injected/used the same built-in EDID from the LCD that macOS finds. i am talking about replacing the built-in EDID with a modified EDID. can be done with DSDT and/or Clover. That is a use a EDID with different timings, blanking time, spacing etc. the standard LCD edid glitches like crazy and eventually get total gfx freeze (BRSNC in log etc). my guide for Lenovo T420 has examples. I also use EDID with just RGB mode so now I don't get acid wash color flicker on certain apps - was getting that using LCD+External. (thanks vusun).

 

High Sierra does seem more prone to HD 3000 gfx issues -  as i ran artifact free fro about 3 or 4 years on 10.10, 10.11 and 10.12 without issue. but all of sudden High Sierra has issues?! For example, I was using EDID injection on my mini-mac5 hack for years now by adding AAPL00,override-no-connect "trick" for headless boot - but had to remove that otherwise i get wicked artifacts. oh well.

 

Where can I learn to make those edits? I made a dump from linux of my EDID but I don't know how to patch it. I know how to inject it with clover, tho.

×
×
  • Create New...