Jump to content
470 posts in this topic

Recommended Posts

Would suit my build better as well

https://www.pccasegear.com/products/39992/gigabyte-radeon-rx-vega-64-8gb-game-bundle

 

Sent from my SM-G930F using Tapatalk

Yeah, but when it comes to power consumption it's a bit much. it needs at least 750W power supply and it needs two 8-pins power connector. but the memory bus it way faster than any existing GPU 2084 Bits!!!!

Link to comment
Share on other sites

Hi,

Can anyone tell me which Terminal commands to open (edit) and then close the Nvidia installer (.pkg) package?

I've had it and used it, but I've lost it...

Thanks.

Sorry I don't know the command.

Link to comment
Share on other sites

Hi,

Can anyone tell me which Terminal commands to open (edit) and then close the Nvidia installer (.pkg) package?

I've had it and used it, but I've lost it...

Thanks.

Used Flat Package Editor but its does work anymore in HS

Works in Sierra

Link to comment
Share on other sites

Guest ricoc90

Hi,

Can anyone tell me which Terminal commands to open (edit) and then close the Nvidia installer (.pkg) package?

I've had it and used it, but I've lost it...

Thanks.

pkgutil --expand

 

to repack again pkgutil --flatten

Usage: pkgutil [OPTIONS] [COMMANDS] ...

Options:
  --help                 Show this usage guide
  --verbose, -v          Show contextual information and format for easy reading
  --force, -f            Perform all operations without asking for confirmation
  --volume PATH          Perform all operations on the specified volume
  --edit-pkg PKGID       Adjust properties of package PKGID using --learn PATH
  --only-files           List only files (not directories) in --files listing
  --only-dirs            List only directories (not files) in --files listing
  --regexp               Try all PKGID arguments as regular expressions

Receipt Database Commands:
  --pkgs, --packages     List all currently installed package IDs on --volume
  --pkgs-plist           List all package IDs on --volume in plist format
  --pkgs=REGEXP          List package IDs on --volume that match REGEXP
  --groups               List all GROUPIDs on --volume
  --groups-plist         List all GROUPIDs on --volume in plist format
  --group-pkgs GROUPID   List all PKGIDs in GROUPID
  --files PKGID          List files installed by the specified package
  --lsbom PKGID          List files in the same format as 'lsbom -s'
  --pkg-groups PKGID     List all GROUPIDs that PKGID is a member of
  --export-plist PKGID   Print all info about PKGID in plist format
  --pkg-info PKGID       Show metadata about PKGID
  --pkg-info-plist PKGID Show metadata about PKGID in plist format
  --file-info PATH       Show metadata known about PATH
  --file-info-plist PATH Show metadata known about PATH in plist format
  --forget PKGID         Discard receipt data for the specified package
  --learn PATH           Update --edit-pkg PKGID with actual metadata from PATH

File Commands:
  --expand PKG DIR       Expand the flat package PKG to DIR
  --flatten DIR PKG      Flatten the files at DIR as PKG
  --bom PATH             Extract any Bom files from the pkg at PATH into /tmp
  --payload-files PATH   List the paths archived within the (m)pkg at PATH
  --check-signature PATH Validate the signature of the pkg at PATH and print certificate information
Link to comment
Share on other sites

Yeah, but when it comes to power consumption it's a bit much. it needs at least 750W power supply and it needs two 8-pins power connector. but the memory bus it way faster than any existing GPU 2084 Bits!!!!

I got a corsair rm850i so I think I'll be fine.

http://www.corsair.com/en-us/rmi-series-rm850i-850-watt-80-plus-gold-certified-fully-modular-psu.

 

Sent from my SM-G930F using Tapatalk

  • Like 1
Link to comment
Share on other sites

Guest ricoc90

@cyberdevs

sorry me for offtopic in your threads

command posted here@ricoc90 are known and discussed on nvidiaweb thread for HS

Now I miss a part so we can

1) bypass osx check and version

2) then we have to modify NvidiaStartup.kext , and now it is in L/E (so Nvidiagraphicfix updater is not working for me. At least 1.5 release)

if we can repack payload file correctly (standard zip not working well) we could modify NvidiaStartupWeb inside it and do only a step when patching Beta Osx with unsupported Nvidia driver..

 

sorry again for offtopic here!

Not quite sure what you mean.

 

I used pkgutil —expand to unpack the Nvidia webdrivers installer package

 

Editted macOS version in Distribution

 

Repacked the installer again with pkgutil —flatten

 

Installed the webdrivers

 

Editted the macos Build in nvidiastartupweb.kext’s info.plist

Link to comment
Share on other sites

@cyberdevs

sorry me for offtopic in your threads

command posted here@ricoc90 are known and discussed on nvidiaweb thread for HS

Now I miss a part so we can

1) bypass osx check and version

2) then we have to modify NvidiaStartup.kext , and now it is in L/E (so Nvidiagraphicfix updater is not working for me. At least 1.5 release)

if we can repack payload file correctly (standard zip not working well) we could modify NvidiaStartupWeb inside it and do only a step when patching Beta Osx with unsupported Nvidia driver..

 

sorry again for offtopic here! 

It's ok man, no worries, we can learn something new here :)

Link to comment
Share on other sites

Guest ricoc90

try this

after expand step

show package contents inside expanded pkg

you should see a file (payload)

 

inside this you can find all file driver installs (like NvidiaStartupWeb.kext)

I would like to modify it and repack correctly..to have a patched pkg for OSX version I need

 

I hope it is more clear now

here attachement to explain better

 

What do you want to edit in nvidiastartupweb.kext? Just the macOS buildnumber?

 

Different approach, but same result: how about editting the postinstall script by adding a cmd to edit the info.plist?

system("sudo perl -i -pe 's/orignumbnumber/patchedbuildnumber/g;' /Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist")

You could even fetch the current macOS build to make it more universal

my $osBuild = `defaults read /System/Library/CoreServices/SystemVersion.plist ProductBuildVersion`;
chomp($osBuild);
system("sudo perl -i -pe 's/orignumbnumber/$osBuild/g;' /Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist")

Well, in theory of course.

 

EDIT: Editted the commands. Above works for me from terminal. Not sure how the webdriver installer would deal with it. Will try it later

Edited by ricoc90
Link to comment
Share on other sites

Guest ricoc90

^ works for me.

 

1. unpacked the webdriver installer package: 

pkgutil --expand ~/Downloads/WebDriver-378.10.10.10.15.120.pkg temp

2. Editted Distribution:

orig: var supportedOSBuildVer = "17A405";
editted: var supportedOSBuildVer = "17B35a";

3. Editted postinstall script:

#!/usr/bin/perl
#
# postinstall perl script
#
# - set "nvda_drv" NVRAM variable to "1"
#

use strict;

# current build version

my $osBuild = `defaults read /System/Library/CoreServices/SystemVersion.plist ProductBuildVersion`;
chomp($osBuild);

# patch NVDAStartupWeb

system("perl -i -pe 's/17A405/$osBuild/g;' /Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist");

# select the web driver
my $cmd = "nvram nvda_drv=1";
system("$cmd");

# done

4. repacked the installer again:

pkgutil --flatten temp patched_webdriver.pkg

5. Run the installer succesfully:

 

post-1502423-0-60723600-1508269457_thumb.png

 

 

So, instead of patching the kexts within the Payload, you could instead just use the postinstall script to let the installer patch the kexts once the installation is done.

Edited by ricoc90
Link to comment
Share on other sites

  • 3 weeks later...

That would be great, because I don't understand most of the things going on in here.

 

I tried updating via App Store but that failed. So a nice updated guide for High Sierra would be highly appreciated.

Sure thing, I will create another guide as soon as I can. I will keep you posted.

Link to comment
Share on other sites

That would be AWESSOME :thumbsup_anim:

Can I ask you to update your signature with your hardware specs please, it would be helpful to know about your hardware it might have help to know what you are using to make the guide more universal.

Link to comment
Share on other sites

my hard drive is not listed to install macOS sierra..

 

in ussing a HDD... in using a barracuda Green

Is that the only hard disk you have or it's the one that doesn't show? Please update your signature with your hardware specs and be specific.

Link to comment
Share on other sites

Is that the only hard disk you have or it's the one that doesn't show? Please update your signature with your hardware specs and be specific.

updated. 

Im using your clover r4246 from that topic.

 

 

Yes.. im using only one hard disk + usb with macOS Sierra installer with your clover folder.

 

 

It not show to select _hard drive to install_ in macOS Sierra installer setup screen.

  • Like 1
Link to comment
Share on other sites

Ok, Thanks for the update and first of all welcome to InsanelyMac.com and my topic :)

 

I assume you read the whole guide and created the installer using the CreateInstallMedia right?

 

Is your SATA settings set to AHCI in BIOS?


Here is the Latest version of the Clover r4289.

Clover_v2.4k_r4289.pkg.zip

Link to comment
Share on other sites

i don't know if i use CreateInstallMedia, my AHCI is enabled. 

 

I will test that clover version. 

 

I can replace entire EFI folder ? 

 

 

thanks for your big help

 

I have much to learn.

No it's only the installer version. You can use it to update your existing EFI folder. or you can send me the EFI folder that you are currently using and I will take a look at it to see if anything is in order.

So guys, anyone update to 10.13.2?

after update I have sleep issue.

 

And somebody has a legacy usb kext to our motherboard and patched dsdt? with dsdt from first post a had many error during boot. 

here's my EFI folder https://1drv.ms/u/s!Amvk7o5bHjRkhZQd1Kzg6fW_xKb9kg

I decided to go DSDT free for a while and everything seemed to be working fine. Those errors won't affect your performance (unless you have noticed otherwise) you can ignore them.

I'm only using UEFI so no comment on the legacy part.

 

If you decide to ditch the DSDT you'll need the Audio patch under ACPI section "change HDAS to HDEF" and the "FixShutdown-0004" patches.

I haven't tested the 10.13.2 beta yet.

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...