Jump to content

72 posts in this topic

Recommended Posts

EDIT:

Have you installed the aDummyHDA.kext properly (you should take it from post 19)? You must use something like KextWizard

 Nope, I'll try it today!

 

 

I warn you that in these days I have some exams at the university so it'll take some time for me to patch them. Maybe a couple of days.

 

I wish you good luck, man! Get not "Excellent" but "Amazing" marks!)))) If it needs you can tell your professors that micsha called you worldwide man!

Share this post


Link to post
Share on other sites
Advertisement

So, yeah, I've installed aDummyHDA.kext through the Kext Utility, but there's no affect - it's color is grey and that's is all.

 

My Origin folder (after F4) in attach.

 

Don't understand about EDID - now monitor works perfectly, my resolution is 1366x768.

 

 

origin.zip

Share this post


Link to post
Share on other sites

Only to be sure....you didn't touch the original AppleHDA.kext, did you?

I mean, after installing El Capitan you didn't try to install the AppleHDA maybe? Because it would be wrong.

If you touched the AppleHDA it won't work because you need the original AppleHDA.kext... So if you "overwrote" or modified in any way the original AppleHDA you must restore the original.

If you did the backup of it you can reinstall it always with KextWizard, otherwise if you don't have the backup of the original you have to reinstall the whole OSX system...

 

So basically you have:

Original AppleHDA+aDummyHDA.kext+Config.plist injection

 

 

Can you upload the config.plist version that you are using please? So that I'll check if the injection is correct...

Maybe also the dsdt.aml in efi\clover\acpi\patched that you are using. You can compress them in a zip.

 

 

If this won't work you can try "returning" to the patched AppleHDA method...

Share this post


Link to post
Share on other sites

No, it is ok if you don't have any AppleHDA.kext in Clover's USB flash drive. The AppleHDA.kext is installed in the system directly by OS X. I was only saying that if you, by any chance, modified it, you must restore the original version, because you need the original AppleHDA to make aDummyHDA work. I don't know, maybe you tried for instance to install a different "AppleHDA" maybe from post 1 or 34 or other, than it is normal that it is not working because you modified the system's AppleHDA.

So I'll assume that you didn't touch the AppleHDA and you didn't overwrite it, otherwise this will be useless...

 

Try this config.plist instead of yours, as it was before it was wrong because it hadn't the audio layout injection.

 

 

Besides...after the installation of aDummyHDA.kext, did you repaired disk permissions and kext caches in KextWizard as shown in the picture below?

 

 

 

PS: be aware that you are using Anerik's memory settings for 14 GB of RAM with 1333Mhz frequency with "Trust" mode enabled too....if you should have any memory error it could be one of the causes unless your machine is exactly like his...

 

 

PPS: Moreover I don't understand which dsdt you are using......Mine or Anerik's? You were using Anerik's config.plist so I guess you are using also his DSDT, isn't it? If you post it we can be sure about this too...Post the EFI\CLOVER\ACPI\"patched" folder in a zip, it contains both dsdt and ssdt.

Which processor (CPU) do you have? I7-2630QM or I7-2670QM? I guess the 2670QM is it right?

correctedConfig.plist.zip

post-1537929-0-93725800-1455225498_thumb.png

Share this post


Link to post
Share on other sites

Hi!

 

Oops, nope - I have Intel i3-2350M 2300Mg (Mac shows CPU right way), RAM is about two cards for 4Gbs (don't know, how MacOS counts RAM size - free or all) and HDD 500Gb.

 

I used anerik's files for ACPI, kexts and config.plist.

 

There's my EFI folder - https://www.dropbox.com/s/rleo2lsom22035i/EFI.zip?dl=0 .

 

P.S.: I will reinstall Mac after getting your files - it's not so long but for sure that it will be reliable to work with mac))

 

P.P.S.: Man, if it is not so hard, could you send me articles or other texts, which helped you to manipulate with DSDT, config,plist and so on? In PM).
Just because I want to know how to do it - and if I will need it in the future, I'll do it by myself. It's the lucky time, that I met you here - without you it I'm not sure that I installed MacOS))).

And I think, it's the best time to read and ask you why things have to be the way they are)).

Share this post


Link to post
Share on other sites

Unfortunately today I don't have much time (exams...), meanwhile try replacing your config.plist and dsdt with the ones attached.

According to me, if you have original untouched AppleHDA, if you have installed the aDummyHDA that you have among the kexts in Clover with Kext Wizard, if you repaired the disk permissions and rebuilt kext caches with Kext Wizard as shown in the post above, with this files you should have working audio.

 

So...

1) Install aDummyHDA in your system with kext wizard as shown in the picture below (Click "browse", select the aDummyHDA in your EFI\CLOVER\Kext\Other and Click "Install")

2) In Kext Wizard repair disk permissions and kext caches as shown in the picture in the post above.

3) Delete the aDummyHDA.kext from EFI\CLOVER\Kext\Other (save its somewhere else if you want, but remove from the Clover usb)

4) Replace your config.plist in EFI\Clover with the one attached in this post

5) Replace your dsdt.aml in EFI\CLOVER\ACPI\patched with the one attached in this post.

6) Reboot

 

According to me you should at least see the volume icon as "black" working icon. If it is the case we are "near" the solution...

 

As soon as I have some time I will send you the guide I followed, but trust me, in this case even though the files maybe are not perfect you should have audio working. According to me you should work to have also the audio working now, when you have it you can really patch your files and reinstall the system clean, but right now the not perfect ACPI files won't make the difference in the audio (except for the injection of audio layout but I fixed it....). The wrong CPU and RAM won't break audio, even because however are have the same "series" (Sandy Bridge) of processor, so it is not as bad as it seems, because probably the power management is almost the same, in fact they are however working....

 

 

If the audio doesn't work again after the process above with the files I attached I'll have two other things to try.... 

Can you tell which version of El Capitan you are using? 10.11.3? 10.11.2? Because I can send you the original AppleHDA for them if you maybe have modified it....

 

As soon as I have time I look for the guide I followed and pm it to you!

New config.plist.zip

DSDT.zip

post-1537929-0-63606700-1455268309_thumb.png

Share this post


Link to post
Share on other sites

jackal992, one more question:

If I reinstall MacOS by using Clover flash drive with changed to yours config.plist and DSDT - will it be OK?

Share this post


Link to post
Share on other sites

Unfortunately I don't know.

According to me you should have working audio also if you don't reinstall the system. When you understand which is the file that does the trick of enabling the audio of course you can "clean" everything by reinstalling OSX.

After the last update to 10.11.3 I had some difficulties in enabling the audio too...

Share this post


Link to post
Share on other sites

Yeah, it could be used for installation! Sometimes it's reboot itself (maybe error or smth else - I don't know) on loading, but then works without any problems). I tried to install MAcOS 2-3 times - finished successfully! Good job!

 

Your second config (post#57) better than first (post #55)  - VGA much better, in #55 I felt frequecy of monitor light, second is quite smooth, but quality of picture a lil' bit worse than in Windows. Small photos like a lil' bit smashed. But ok, it's not the main point - we can return later.

 

Thanks for fixing size of RAM!

 

About sound - nope, it's grey. 
I also tried VooDooHDA - OMG))). I get sound but Voodoo has linked imput from mic and output - and my ears were bleedin')). Unfortunatelly, I didn't found how can I switch off mic sound.

 

P.S.: I'll try one more way just to check, have I missed smth.

Share this post


Link to post
Share on other sites

I've reinstalled using files from post #57 - successfully complete!).

 

But even after guide from post #57 - sound icon is grey.

Share this post


Link to post
Share on other sites

Ok, even though it seems a bit strange to me that nothing works, we can try one last thing, i.e. revert to the "original" audio patching, that is directly patch the AppleHDA without using the aDummyHDA.

 

I have patched the AppleHDA as if you were using El Capitan 10.11.3...is this correct? Are you using 10.11.3?

 

I prepared 4 versions of the files that must work together as a "pack".

 

Before doing so you must remove the aDummyHDA both from Clover usb (delete from EFI\CLOVER\Kext\Others the aDummyHDA if you still have it) and from the system. To remove from the system you have to browse to "system/library/extensions" (you can go in Finder->Go->Go to Folder or Alt+Shift+G and type "system/library/extensions") and delete the "aDummyHDA".

 

Once you do this you try "pack 1" here attached:

-install AppleHDA with Kext Wizard (this time when you install enable the option "Backup kexts that will be replaced"

-In Kext Wizard repair disk permissions and rebuilt kext caches as usual

-try using the pack 1 dsdt and config.plist in your Clover usb (the dsdt in ....ACPI\patched) and reboot

 

If this doesn't work try pack 2:

-try using the pack 2 dsdt and config.plist in your Clover usb (the dsdt in ....ACPI\patched) and reboot

 

If this doesn't work try pack 3:

-try using the pack 3 dsdt and config.plist in your Clover usb (the dsdt in ....ACPI\patched) and reboot

 
If this doesn't work try pack 4:
-Install HDAenabler3.kext with KextWizard as usual
-In Kext Wizard repair disk permissions and rebuilt kext caches as usual

-try using the pack 4 dsdt and config.plist in your Clover usb (the dsdt in ....ACPI\patched) and reboot

 
To be very fair with you after this tests I don't have any other idea, if it still doesn't work you can try ask Anerik for his help, even though I managed to make his aDummyHDA work with my machine that is different, so it's strange that for you it doesn't work..

pack1.zip

pack2.zip

pack3.zip

pack4.zip

Share this post


Link to post
Share on other sites

jackal992, first pack was the right one!!! Sound and mic work perfectly!!

 

Thank you!))

 

So, my final EFI partition here: https://www.dropbox.com/s/6n1cqi33u4mz1iq/EFI_2.zip?dl=0(use it with jackal992's  AppleHDA from pack #1 in previous post!)


The only question I left is to install bootloader on hdd - just to free my usb flash))). But I think I will find a way!

 

P.S.: If you have twitter - you can write it in PM, I'll make public appreciation)))

Share this post


Link to post
Share on other sites

Wow glad to hear that!

 

For the installation on HDD I don't really know because as I explained to you I made a small partition in fat32 on my hdd where I copied my Clover USB files and I boot from that partition always from the EFI shell, so manually. I chose this way so that Windows boot loader remains the main one and I don't risk breaking it.

 

If you want to install it so that it starts when you boot the machine I think you have to install some scripts, I read in a guide by RehabMan:

-Installing to the HDD/SSD after installation is very similar to installing to the USB.

-You change the destination of Clover's installation to your target disk

Notes on HDD install:

- you might want "EmuVariableUefi-64.efi", but it would depend on whether native NVRAM works for you

- select "Install RC scripts on target volume" and/or "Install all RC scripts on all other boot volumes"

- selecting "Install Clover Preference Pane" is optional

- there are also some "Optional RC Scripts" you might want to read about

 

but again I didn't do that so I don't know...of course after the installation of Clover you copy in the "new" Clover's EFI folder the kexts, the acpi patched files and config.plist that work for you.

Share this post


Link to post
Share on other sites

I chose this way so that Windows boot loader remains the main one and I don't risk breaking it.

 

 

Yeah, I know it))). I broke two Windows bootloader (the second I repaired, but that's enough) - I don't want to play with it too)))).

 

I gonna go your way!

Share this post


Link to post
Share on other sites

Hi, jackal992!

I have two questions (maybe you can help):

1) Strange issue, but not all FNbuttons works)). Is it normal?

I can switch off screen, but can not change brightness or bump up or down volume.

2) About sound). When I close my notebook, MacOS works, but sound disappear - and only rebooting can return it. Do you have so?

 

Thanks in advance!

1) I have all the FN keys working. I used the attached kext: "AsusNBFnKeys". You can try to install it with KextWizard and repair permissions and caches as usual.

(Assuming that your brightness works properly, you can try that by going in SystemPreferences\Display and move the slider)

 

2) I don't have the problem of sound not working after sleep, but you can try to solve it with CodecCommander. Unfortunately I cannot help you with this, I didn't do it!

However here are some useful links:

Guide: https://bitbucket.org/RehabMan/os-x-eapd-codec-commander/overview

Download: https://bitbucket.org/RehabMan/os-x-eapd-codec-commander/downloads

 

There should already be a profile for the ALC269. You can try that...

 

AsusNBFnKeys.kext.zip

Share this post


Link to post
Share on other sites

USB3 works now, seemed to be a reboot issue. Ethernet is working fine as well, thanks a lot! :) Is there any way to turn off Bluetooth (my button is greyed out)?

 

interesting..

i just noticed my bluetooth button is also grayed out.

has any one found a way to correct this ?

..

i notice that on my EFI\CLOVER\OEM\N53SV\KEXT\OTHER\

I have BTFirmwareUploader

am wondering if thats the Bluetooth kext that the machine is using and causing my bluetooth issue.

 

if i remove the kext or replace it,

do i have to use disktools to fix permissions (or another tool) on the EFI partition, or can i just remove it and reboot ?

 

thanks

Share this post


Link to post
Share on other sites

interesting..

i just noticed my bluetooth button is also grayed out.

has any one found a way to correct this ?

..

i notice that on my EFI\CLOVER\OEM\N53SV\KEXT\OTHER\

I have BTFirmwareUploader

am wondering if thats the Bluetooth kext that the machine is using and causing my bluetooth issue.

 

if i remove the kext or replace it,

do i have to use disktools to fix permissions (or another tool) on the EFI partition, or can i just remove it and reboot ?

 

thanks

 

I use the attached kext to make bluetooth work and my icon is not gray but black. I don't have the "BTFirmwareUploader".

If you install/uninstall kexts from s/l/e I think it won't hurt if you rebuild disk permissions and kext caches, on the contrary many time is needed...

IOath3kfrmwr.kext.zip

Share this post


Link to post
Share on other sites

hello jackal! Thanks for your precious help!

i tried to install everything from scratch from one of the latest versions of el capitan, and it doesn't work anymore.

May you please provide both your config.plist configuration for (latest) el capitan and files provided in the EFI folder?

Thanks!!!

mal

 

EDIT : fighting with clover it seems to work again but it's very unstable, compared to chameleon and old good osx versions...

 

PS: Is there anyone that is using clover and snow leopard ?  may you please send me some directions to have snow leopard working with clover? Thanks a lot!! i know it's a bit off topic ... sorry for that

Share this post


Link to post
Share on other sites

Hi, i am new to this forum! 

I own a great old N53S and i would like to know if there is any way to install latest Sierra or latest ElCapitan on this great notebook!

Thank you.

EDIT: Any update for n53sm? Sierra? High Sierra? it is a great laptop! thanks!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By zebity
      Hi Hypervisors,
       
      I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.
       
      After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
      https://www.kraxel.org/blog/2017/09/running-macos-as-guest-in-kvm/
      https://github.com/kholia/OSX-KVM
      https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2
      https://clover-wiki.zetam.org/Home
       
      I have now managed to get OVMF/Clover boot and install of MacOS Sierra.
       
      I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.
       
      So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager
       
      As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of: 
      GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)
       
      This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).
       
      Using bare minimal Clover config.plist:
       
       
      And following Clover UEFI drivers:
       
      I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
      The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.
       
      Here is my virtlib.xml dump for the virtual machine:
       

      Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.
       
      Thank you.
       
      Regards,
       
      Zebity
       
    • By frankiee
      Hi there, time for my first guide after asking so many things
       
      Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.
       
      So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.
       
      DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.
       
      Prerequisites:
      Working clover installation Clover Configurator or some app to edit the config.plist  
      1) Memtest
       
      This is how to install the UEFI version of Memtest with Clover:
      Download memtest, I used this link: Image for creating boot-able USB Drive Open the archive by double clicking on it. Mount the file memtest86-usb.img within by double clicking again. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version. Now, mount your EFI partition, using Clover configurator. Create a folder named MemTest86 in the EFI folder on your main drive. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder. That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.
       
      Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:
       

       
      Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.
       
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <true/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MemTest86</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string>\EFI\CLOVER\themes\Icons\os_mint.png</string> <key>Path</key> <string>\EFI\MemTest86\BOOTX64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:
       

       
      And this is how it looks like:
       

       

       
      PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29
       
       
      2) gdisk
       
      Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.
       
      Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.
       
      This is how to do it (even easier):
      Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download Mount your EFI partition Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi" Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:  
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <false/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>GDisk</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string></string> <key>Path</key> <string>\EFI\gdisk-efi\gdisk_x64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> When everything went OK you should see this after selecting the respective entry in Clover:
       

       
       
      3) RU
       
      I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.
       
      Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
      Download here: http://ruexe.blogspot.de/ The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist Here are some screens:
       

       

       

       
       
      So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!
       
      Anybody who knows, maybe post it here?
    • By TimNeumann
      MB: Asus X99 A-II
      RAM: G.Skill Ripjaws V F4-3200C16D-32GVK (3200MHz, 4x 16GB DIMMs, so Total 64GB) in quad-channel configuration.
      CPU: i7 6800k @4.0Ghz
      GPUs: GTX 1080 Ti and GTX 1060 3GB
      (each one a monitor, because I can't get DVI to run parallel with DP on the 1080Ti, and my second monitor only has DVI/VGA)
      OS: High Sierra 10.13.2 (17C88) / Clover revision: 4392
       
      Hello everybody,
      I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).  
      As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
      So I also suspect that my RAM is not compatible.
      But if that were the case, how could it sometimes work completely error-free?
       
      During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
      I am appreciative for any help!
       
      Here is an excerpt from a faulty test.
      It is noticeable that it is always the same address during the test, but a different one after each test.
      Memtest version 4.22 (64-bit) Copyright (C) 2004 Charles Cazabon Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port) Licensed under the GNU General Public License version 2 only Mac OS X 10.13.2 (17C88) running in multiuser mode Memory Page Size: 4096 System has 12 Intel core(s) with SSE Requested memory: 57232MB (60012990464 bytes) Available memory: 57232MB (60012990464 bytes) Allocated memory: 57232MB (60012990464 bytes) at local address 0x00000001033e1000 Attempting memory lock... locked successfully Partitioning memory into 2 comparison buffers... Buffer A: 28616MB (30006495232 bytes) starts at local address 0x00000001033e1000 Buffer B: 28616MB (30006495232 bytes) starts at local address 0x00000007ffc4d800 Running 1 test sequence... (CTRL-C to quit) Test sequence 1 of 1: Running tests on full 57232MB region... Stuck Address : ok Linear PRN : testing 7 of 16 FAILURE! Data mismatch at local address 0x0000000e88133d30 Expected Data: 0xc4c340079ac9a645, Actual Data: 0xc4c3400788468846 Running comparison tests using 28616MB buffers... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : testing 80 of 256 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x4f4f4f4f4f4f4f4f, BUFB Data: 0x4f4f4f4f88468846 Checkerboard : testing 3 of 64 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x5555555555555555, BUFB Data: 0x5555555588468846 Bit Spread : testing 1 of 128 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000088468846 Bit Flip : testing 74 of 512 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000088468846 Walking Ones : testing 40 of 128 Clover Files attached
      config.plist
      drivers64UEFI.zip
      kexts.zip
      ACPI.zip
    • By BurpSuite
      screenshot:
       

       
      description:
      github: https://github.com/burpsuite/clover_theme
×