Jump to content

[Discussion] - TRX40 Bare Metal - Vanilla Patches

fabiosun

By fabiosun
in General

 Share

Recommended Posts

Recommended

Posted by fabiosun,

Ok..good news playing with MMIO and with opencore 061 i have solved reboot/shutdown problem... now it is working as it must work

MMIO rules shutdown and reboot previous problems

Recommended by fabiosun

  • Like

2 reactions

Go to this post
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

@iGPU

this part : 

4. Now type: /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -v /Volumes/BigSur -r ""   (<--- again, use your disk name; the final characters are 2 double-quote marks) You'll get a response such as "Attempting tagging of snapshot on volume: /Volumes/BigSur

produces not such file directory (I have used obviously my disk name)

however, I can delete with others steps my snapshot 

and then rebooting I can also execute sudo mount -uw

But also with this, Nvidia driver is not able to write on volume because it is read only

with Catalina and previous beta I didn't have this problem


I must also admit that probably when I previously managed to install the driver, very probably I was not from a clean installation like in this case

 

Link to comment
Share on other sites
  • Moderators
iGPU Senior Member

iGPU

Posted
  • Moderators
Posted (edited)
10 hours ago, fabiosun said:

@iGPU

this part : 


4. Now type: /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -v /Volumes/BigSur -r ""   (<--- again, use your disk name; the final characters are 2 double-quote marks) You'll get a response such as "Attempting tagging of snapshot on volume: /Volumes/BigSur

produces not such file directory (I have used obviously my disk name)

however, I can delete with others steps my snapshot 

and then rebooting I can also execute sudo mount -uw

But also with this, Nvidia driver is not able to write on volume because it is read only

with Catalina and previous beta I didn't have this problem


I must also admit that probably when I previously managed to install the driver, very probably I was not from a clean installation like in this case

 

 

I ran these instructions on my clean install and had no problem removing the snapshot in Recovery. Once back in Big Sur ß7, I was then able to change files after executing the "sudo mount -uw /" command. I'm wondering if you had (have) more than one snapshot partition? Did you verify after deleting the first snapshot that none were remaining?

 

The only time I saw the an error something like "no such file or directory", when using the (/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -v /Volumes/BigSur -r "") command, was when I made a typo in the command or file name (esp if there were a space in the name), or, if there are no snapshots to tag. So if not first problem with extra snapshot, then I would guess a typo error.

 

 

EDIT:


The other thing to try is before going into Recovery, add boot-arg (it can later be removed for routine BS bootin): -no_compat_check and amfi_get_out_of_my_way=1

 

And once in Recovery, run:  nvram csr-active-config csr-active-config %7f%08%00%00

 

 

Edited by iGPU
  • Thanks 1
Link to comment
Share on other sites
fojerhar Junior Member

fojerhar

Posted
Posted

Hi

I don't know if this is the good thread to ask this, I try to make alive my Firewire card for my uad sound card . Tried many things, irq conflicts, and so on, inserted at Device properties, kext loaded, but still no success. This was a native working card in my previous builds.

Software writes Driver not installed correctly, it means that I did not allowed in in security and Privacy , but there was no option for that

Screenshot 2020-09-22 at 13.05.32.png

Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

if you try from terminal 

sudo mount -uw /

 

it works or you have a permission errors?

Firewire driver add some kext in L/E or S/L/E?

any modify o SIP should be done in recovery mode
I use E7030000 for disable and all 0 for enable (in config.plist after enabling or disabling via recovery)

maybe it could be also useful for you disabling gatekeeper

sudo spctl --master-disable

Link to comment
Share on other sites
Driftwood Senior Member

Driftwood

Posted
Posted (edited)
7 hours ago, fojerhar said:

I don't know if this is the good thread to ask this, I try to make alive my Firewire card for my uad sound card . Tried many things, irq conflicts, and so on, inserted at Device properties, kext loaded, but still no success. This was a native working card in my previous builds.

 

I dont know about the Cheetah Xpress but a lot of bridged firewire cards have been problematic in Proxmox (maybe iGPU can comment about Bare metal) but my LSI643 card (single chip NOT bridged) works great and has done for years in other builds.

 

I guess you could look at enabling SIP (csrutil Enable) when installing it, and check to see if it supports the current OSX you are using. Use Recovery Mode to properly enable SIP.

Edited by Driftwood
  • Like 1
  • +1 1
Link to comment
Share on other sites
meina222 Senior Member

meina222

Posted
Posted (edited)

That was quick (and I am not as quick as others noticed it too already 😉).

 

Tried to launch the update on bare metal - getting a popup "Full installer required". So it doesn't like something about my setup.

 

Downloading full 12.16GB now. If this KP's like beta 7, I am convinced Apple is spying on this forum 😂.

Edited by meina222
  • whahahah 3
Link to comment
Share on other sites
Ploddles Senior Member

Ploddles

Posted
Posted (edited)
6 minutes ago, meina222 said:

That was quick (and I am not as quick as others noticed it too already 😉).

 

But dare you try it yet to see if it breaks our new patches by algrey again? 🙂

 

EDIT

Just seen your update to previous post. 😞

Edited by Ploddles
  • Like 1
Link to comment
Share on other sites
  • fabiosun changed the title to [Discussion] - TRX40 Bare Metal - Vanilla Patches

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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.