Jump to content
ErmaC

nVidia Sub-Vendor & Sub-Device Injection for Chameleon

52 posts in this topic

Recommended Posts

In the last couple of days, I was writing a Cosmetics nVidia support in Chameleon, and had a few testers, but I need to make sure it works on most supported cards.

  • What cosmetics support would be? I added the recognition of the graphics cards also based on the Sub-Vendor ID and Sub-Device ID.
  • What "COSMETICS" does this mean? It means that you... (we) can now customize the output "string" for your graphics card. Example:
    - Before1: reading just the Device Id was...
    GeForce GTX 470


    - After1: reading also the Sub-VendorId and Sub-DeviceID will be

    Zotac GTX 470


    - Before2: reading just the Device Id was...

    GeForce GTX 470


    - After2: same Device ID (as for Before1) but different Sub-VendorId & Sub-DeviceId

    Zotac GTX 470 AMP


  • What happens if the Sub-Vendor and Sub-Devices are missing in the boot loader? In this case will be assigned a standard string based only on the VendorID.

First I would like to outline a few things:

  • This isn't a HOW TO get your card working, this is a request for testing.
  • Don't ask how to install the booter, how to use or add a given booter flag or how to run an update, if you don't know how to do that yourself, then this isn't for you, yet, learn that elsewhere, and you're more than welcome here.
  • I don't take responsibility for any damage this may cause, so take your precautions before you use this.

This project will take the name of Enoch.

  • This will help you. To not confuse this with Chameleon.
  • The core sources (Booting) are the same as my ErmaC Sub-Branch(Trunk) on voodooprojects.
  • The source code will be committed/released when I have accumulated feedback and different "Subs_ID".

Requirements:

  • An NVIDIA already supported cards by Chameleon's GraphicsEnabler.

How and what to report:

  • Disable any kind of enabler,DSDT injection, injector or device-properties you're currently using.
  • Save an bdmesg dump (From terminal or from Chameleon Wizard bdmesg’s TAB).
    A report example
    GFX card model = MSi VN240GT-MD1G
    bdmesg info =
    Using PCI-Root-UID value: 0
    GeForce GT 240 1024MB NVa3 [10de:0ca3]-[1462:8041] :: PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) device number: 1
    dcb table at offset 0xad3b

  • Report any observations or comments.
  • Include a screenshot of the Graphics tab from System Profiler when reporting.

Bootloader Binaries and changelog:

  • 29th may 2012
    More Subs ID
    11th may 2012
  • More Subs ID
    9th May 2012
  • Added a lot of new SubsID
    5th May 2012
  • Added a lot of new SubsID
    4th May 2012
  • Added some new ID and correct old bad names.
     
    + Dell GeForce 8600M GT Works! Confirmed thx to DarwinX
    Using PCI-Root-UID value: 0
    Dell GeForce 8600M GT 256MB NV84 [10de:0407]-[1028:022e] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1
    dcb table at offset 0x893c

     
  • 3rd May 2012
    Added a couple of new Sub-VendorId e Sub-DeviceId with proper card name.
     
    + MSi VN240GT-MD1G Works! Confirmed thx to Fabio71
    Using PCI-Root-UID value: 0
    MSi VN240GT-MD1G 1024MB NVa3 [10de:0ca3]-[1462:8041] :: PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) device number: 1
    dcb table at offset 0xad3b


    + Asus EN8400GS Works! Confirmed thx to Fabio71

    Using PCI-Root-UID value: 0
    Asus EN8400GS 512MB NV98 [10de:06e4]-[1043:8322] :: PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) device number: 1
    dcb table at offset 0xbb70


    + [10DE:06CD]-[19DA:0010] Zotac GTX 470 Works! Confirmed
    + Zotac GTX 470 AMP Works! Confirmed thx to magnifico10

    Using PCI-Root-UID value: 0
    Zotac GTX 470 1280MB NVc0 [10de:06cd]-[19da:1153] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1
    dcb table at offset 0x4e88


    + Asus EN9600GT Magic Works! Confirmed thx to Fabio71

    Using PCI-Root-UID value: 0
    Asus EN9600GT Magic 512MB NV94 [10de:0622]-[1043:82ac] :: PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) device number: 1
    dcb table at offset 0xb93e

     

Thanks all. Fabio (.: ErmaC:.)

Share this post


Link to post
Share on other sites
Advertisement

I'll check it out. :)

 

Edit: it doesn't appear to be working for my 9600 GT...I'm using GraphicsEnabler with the (_UID) fix for the PCI0 device in DSDT. Do I need to remove the DSDT first?

 

I'll post a pic when I get a chance.

Share this post


Link to post
Share on other sites

Edit: it doesn't appear to be working for my 9600 GT...I'm using GraphicsEnabler with the (_UID) fix for the PCI0 device in DSDT. Do I need to remove the DSDT first?

How and what to report:

  • Disable any kind of enabler,DSDT injection, injector or device-properties you're currently using.

Share this post


Link to post
Share on other sites
Using PCI-Root-UID value: 0
nVidia GeForce 8600M GT 256MB NV84 [10de:0407] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)

 

post-185231-0-16489000-1336133337_thumb.png

Share this post


Link to post
Share on other sites
 Using PCI-Root-UID value: 0 nVidia GeForce 8600M GT 256MB NV84 [10de:0407] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) 

 

THX DarwinX.

But I need you install the Enoch bootloader

because I see it show only the Vendor and device ID

nVidia GeForce 8600M GT 256MB NV84 [10de:0407]-[????:????]

Also the "correct name for your GFX if it have one...

 

THX

Fabio

Share this post


Link to post
Share on other sites

THX DarwinX.

But I need you install the Enoch bootloader

because I see it show only the Vendor and device ID

nVidia GeForce 8600M GT 256MB NV84 [10de:0407]-[????:????]

Also the "correct name for your GFX if it have one...

 

THX

Fabio

 

Using PCI-Root-UID value: 0
GeForce 8600M GT 256MB NV84 [10de:0407]-[1028:022e] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1
dcb table at offset 0x893c

Share this post


Link to post
Share on other sites
Using PCI-Root-UID value: 0
GeForce 8600M GT 256MB NV84 [10de:0407]-[1028:022e] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1
dcb table at offset 0x893c

 

THX now is ok!

The name "Dell GeForce 8600M GT" should be ok?

Or "Dell GeForce Go 8600M GT"?

 

Fabio

Share this post


Link to post
Share on other sites

THX now is ok!

The name "Dell GeForce 8600M GT" should be ok?

Or "Dell GeForce Go 8600M GT"?

 

Fabio

 

Chipset model name: NVIDIA GeForce 8600M GT or Dell GeForce 8600M GT.

I believe that the nVidia has only used the "Go" in its GeForce 7 notebook series and had subsequently replaced it with the "M" starting with the GeForce 8 notebook series.

Thank You.

Share this post


Link to post
Share on other sites

Chipset model name: NVIDIA GeForce 8600M GT or Dell GeForce 8600M GT.

I believe that the nVidia has only used the "Go" in its GeForce 7 notebook series and had subsequently replaced it with the "M" starting with the GeForce 8 notebook series.

Thank You.

 

Done. (Dell GeForce 8600M GT)

 

Fabio

Share this post


Link to post
Share on other sites

Done. (Dell GeForce 8600M GT)

 

Fabio

 

Using PCI-Root-UID value: 0
Dell GeForce 8600M GT 256MB NV84 [10de:0407]-[1028:022e] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1
dcb table at offset 0x893c

 

post-185231-0-07328600-1336166200_thumb.png

 

Again, Thank You.

Share this post


Link to post
Share on other sites

the Go versions are usually shared on mobo. these are separate discrete. .. i have a similar 8600M 10de:0407 sub 1028:01f1 (inspiron 1520) but mine shows nv84 and it has no hdmi. unlike DarwinX

 

i got the id with lspci -v -n

Share this post


Link to post
Share on other sites

Hi

This is with the latest Enoch ver.1.04

 

Using PCI-Root-UID value: 0
Zotac GeForce GTX 470 AMP 1280MB NVc0 [10de:06cd]-[19da:1153] :: PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) device number: 1
dcb table at offset 0x4e88

 

hope this helps

post-460069-0-46719100-1336246184_thumb.png

Share this post


Link to post
Share on other sites

This is with the latest Enoch ver.1.04

Using PCI-Root-UID value: 0
Zotac GeForce GTX 470 AMP 1280MB NVc0 [10de:06cd]-[19da:1153] :: PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) device number: 1
dcb table at offset 0x4e88

 

Thx akhenamenra!

This confirm yours IDs are already inside the bootloader.

Fabio

Share this post


Link to post
Share on other sites

:thumbsup_anim:

Great Fabio..your package work perfect , :gathering:

You need a bdmesg ?

 

 Enoch by ErmaC (r1955) [2012-05-09 00:20:44]
cpu freq classic = 0x00000000d09e79d0
msr(385): platform_info 70012300 bla bla bla ....
Zotac GeForce GTX 470 1280MB NVc0 [10de:06cd]-[19da:1153] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1
dcb table at offset 0x4e88

 

PS: Only Generate P and C state i dont see in my bdmesg...maybe i have a bios mod ?

Share this post


Link to post
Share on other sites

not for me ... ( Zotac GeForce GT 520 )

GeForce GT 520:

Chipset Model: GeForce GT 520

Type: GPU

Bus: PCIe

Slot: Slot-1

PCIe Lane Width: x16

VRAM (Total): 1024 MB

Vendor: NVIDIA (0x10de)

Device ID: 0x1040

Revision ID: 0x00a1

ROM Revision: 75.19.1B.00.01

Displays:

Studio Display 21:

Resolution: 1600 x 1200 @ 85 Hz

Pixel Depth: 32-Bit Color (ARGB8888)

Main Display: Yes

Mirror: Off

Online: Yes

Rotation: Supported

 

GeForce GT 520:
 Name: NVDA,Display-B
 Type: Display Controll
 Driver Installed: Yes
 MSI: Yes
 Bus: PCI
 Slot: Slot-1
 Vendor ID: 0x10de
 Device ID: 0x1040
[b] Subsystem Vendor ID: 0x19da
 Subsystem ID: 0x0010[/b]
 ROM Revision: 75.19.1B.00.01
 Revision ID: 0x00a1
 Link Width: x16
 Link Speed: 2.5 GT/s

Share this post


Link to post
Share on other sites

not for me ... ( Zotac GeForce GT 520 )

GeForce GT 520:

Vendor ID: 0x10de

Device ID: 0x1040

Subsystem Vendor ID: 0x19da

Subsystem ID: 0x0010

 

I will add it in the next version thx!

 

	/*SubsID*/	{ 0x10DE1040,	0x104383A0,	"Asus GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x104383BD,	"Asus GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x104383C1,	"Asus GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x14622592,	"MSi GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x14622593,	"MSi GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x16423A98,	"Bitland GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x16423B42,	"Bitland GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x174B3214,	"PC Partner GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x196E0915,	"PNY GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x19DA0010,	"Zotac GeForce GT 520" }, // robertx
/*SubsID*/	{ 0x10DE1040,	0x19DA1215,	"Zotac GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x1ACC5213,	"Point of View GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x1ACC5214,	"Point of View GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x1ACC522C,	"Point of View GeForce GT 520" },
/*SubsID*/	{ 0x10DE1040,	0x1B0A90AA,	"Pegatron GeForce GT 520" },
/*Generic*/	{ 0x10DE1040,	NV_SUB_IDS,	"GeForce GT 520" },

Share this post


Link to post
Share on other sites

Done!

 

Fabio

...hmmm..didn't change anything...still GeForce GT 520...i'll recheck ids in windows

 

edit: here's what windows shows in device manager...(PCI\VEN_10DE&DEV_1040&SUBSYS_122219DA&REV_A1)

Share this post


Link to post
Share on other sites

...hmmm..didn't change anything...still GeForce GT 520...i'll recheck ids in windows

 

edit: here's what windows shows in device manager...(PCI\VEN_10DE&DEV_1040&SUBSYS_122219DA&REV_A1)

is more fast if you post your bdmesg log...

 

Fabio

Share this post


Link to post
Share on other sites

GeForce GT 520 1024MB NVd9 [10de:1040]-[19da:1222] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1

dcb table at offset 0x50aa

...there you are...thx

Share this post


Link to post
Share on other sites

GeForce GT 520 1024MB NVd9 [10de:1040]-[19da:1222] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1

dcb table at offset 0x50aa

...there you are...thx

 

ok now is correct...

[10de:1040]-[19da:1222]

here the boot file just replace this...

(In the next revision I will add it permanently)

 

Let me know.

 

Fabio

Share this post


Link to post
Share on other sites

ple help 8700m thanks.

Share this post


Link to post
Share on other sites

Here's mine, although it's not quite working with full res/openGL yet:

 

 

GeForce GTX 560 Ti-448 1280MB NVc8 [10de:1087]-[19da:2207] :: PciRoot(0x1)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1

dcb table at offset 0x4fa3

 

 

GeForce GTX 560 Ti-448:

 

Chipset Model: GeForce GTX 560 Ti-448

Type: GPU

Bus: PCIe

Slot: Slot-1

PCIe Lane Width: x16

VRAM (Total): 1280 MB

Vendor: NVIDIA (0x10de)

Device ID: 0x1087

Revision ID: 0x00a1

ROM Revision: 70.10.61.00.02

Displays:

Display:

Resolution: 1280 x 1024

Pixel Depth: 32-Bit Color (ARGB8888)

Main Display: Yes

Mirror: Off

Online: Yes

 

 

If anyone can tell me how I can get full resolution (1920x1080) and full openGL etc I would be very happy :). Already did Netkas' openCL hexedit patching, using graphicsenabler=yes

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs
       
      This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
       
      Cheers!
    • By Coke2g
      I've been happily using macOS Sierra 10.12.6 (16G29) successfully for more than a year (all things working), but now I replaced my old Asus GTX 750 Ti card with a new Zotac GTX 1060 6GB, and it get stuck on boot just before going to the login screen (verbose boot screen attached).
       
      I've updated Clover with all its kexts, and reinstalled the Nvidia Web Drivers (using nvidia-update script), but it's still stuck in the same part. I can only enter using nv_disable=1
       
      My current Hackintosh specs:
      Motherboard MSI H110M Gaming (MS-7994) (LGA 1151/Intel H110/DDR4/SATA 3 & USB 3.1) CPU Intel Core i5-6600 6M Skylake Quad-Core 3.3 GHz LGA 1151 65W RAM HyperX FURY 16GB (2 x 8GB) DDR4 2133 (PC4-17000) HX421C14FBK2/16 Video Zotac GTX 1060 6GB SSD Samsung SSD 850 EVO 250GB HDD Western Digital Black 1TB (32MB Cache) (WDC WD1001FALS-00J7B1)  
      I've read that maybe it can be fixed patching the DSDT, but I don't know how to do it.
       
      My RunMe.app generated zip file and verbose boot screen are attached.
       
      Any kind of help is appreciated. Thanks.
      Send me Coke-iMac.zip

    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • By al3asdfmovie
      Buongiorno a tutti,
      E la prima volta che scrivo su questo forum, spero di non sbagliare nulla!
      Scrivo qua sperando che qualcuno di voi possa darmi una grossa mano, perchè ho letto di tutto, visto qualsiasi video possibile, ma non riesco proprio ad uscirne fuori.
      Ci avevo già provato 3 anni fa, ma ero riuscito solo su un notebook Sony, sul fisso non ero riuscito a fare nulla. Dicevano che c'erano problemi con i driver della serie Skylake, così ho voluto riprovare ora a distanza di anni.
      Premetto che non sono un informatico, non ho conoscenze particolari. Sono semplicemente un ragazzo che si informa, legge tutorial ed esegue, quindi chissà che la soluzione non sia in realtà una banale sciocchezza.
       
      Dunque, il problema consiste nel fatto che, in circa 8 ore di prove, non sia ancora riuscito ad andare oltre il caricamento del logo, dopo aver selezionato la chiavetta da clover.
      Sto cercando di installare High Sierra, ho provato con una chiavetta con un programma che non ho capito bene perchè, ma non posso scriverlo qui, e una con Clover Configurator (che tra l'altro, nella schermata boot mi da un'interfaccia diversa da quella che ho visto nel tutorial, o anche solo 3 anni prima), ma il problema è sempre lo stesso: dopo circa metà caricamento, o mi esce il simbolo di divieto, o si riavvia il computer, riportandomi nel boot di clover.
      Ho provato un po' di flags, come -v, -x, -s, -f, nv_disable=1 (tra l'altro, per evitare problemi al principio, ho impostato la scheda video di intel come primaria), cpus=1, dart=0, Slide=0, insomma, qualsiasi cosa leggessi in giro che avesse portato esiti positivi, la provavo
      Ho provato su porte sub 3.0, 2.0 e le 2.0 dietro al pc.
      Penso sia irrilevante, ma nel caso, sto usando una chiavetta da 32 gb.

      Nella firma dovrebbero esserci tutte le specifiche del mio PC, non so se debba postare altro. Nel caso scusatemi, ditemi pure cosa manca che la aggiorno.
      Spero davvero che qualcuno di voi possa aiutarmi. Ho un MacBook Air (High Sierra l'ho scaricato da qui) e ho scoperto quanto sia più affidabile usare Final Cut rispetto a quel bug chiamato Premiére Pro che ho usato per anni, e vorrei poterlo usare anche sul fisso, senza dover acquistare un iMac. Ho letto in giro che con Mojave non è supportata l'accelerazione grafica, per questo vorrei installare High Sierra.

      Grazie mille a chiunque vorrà aiutarmi!
    • By MaLd0n
      Now have a Olarila app, just download app and clover folder for your Chipset! https://olarila.com/forum/viewtopic.php?f=81&amp;t=6771   Install MacOS with Olarila Image, Step by Step, Install and Post Install
       
      https://olarila.com/forum/viewtopic.php?f=50&t=8685
          First... If you need DSDT edits for SkyLake, KabyLake or CoffeeLake... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Post Ioreg, extract with Ioreg Explorer http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222606 -Run it, post files generated in your desktop http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222609  Installation   --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/   --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder  CLOVER.zip   --Install Sierra/High Sierra and boot into system!   Post Installation   --Install Clover in HDD/SSD and replace with my folder CLOVER.zip   --Reboot and activate video!   -Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/ -Nvidia WebDriver High Sierra http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/ -Cuda http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/   --DSDT My DSDT with Skylake patches DSDT.MaLd0n GA H110M-S2.zip Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -PNLF -HDMI --FakeSMC https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek --Audio https://github.com/vit9696/AppleALC --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!  
×