• Content Count

  • Joined

  • Last visited

Everything posted by bjornatic

  1. Sadly it makes no (visible) change for me. I added the line in the "Samba extra configuration" field, but the copy of a large file from an Unraid share still hangs at 134.2Mo and after a while error -8084. (Big Sur 11.1 (20C69))
  2. I use the Nvmefix kext but no other (regarding Nvme). The controller used for the 980 Pro is new (and called Elpis) and i just assumed that i have to wait for a driver / kext update. I was not able to find any one else having this problem with this specific drive.
  3. Is there really an advantage to choose the "right" model ? (beside having one that is not too old for BigSur)
  4. I can report the same problem. More in detail : Unraid 6.9.0-beta35 VM pc-q35-5.1 BigSur 11.1 / OpenCore 0.6.4 e1000-82545em Copying a 9Gb file from my MacBook Pro (Catalina) connected over wifi works fine (at least the few times I tested) . Copying the same file from the same Macbook connect over ethernet 1Gb/s leads to a halt after exactly 134,2Mo and then error -8084 Copying file directly from Unraid shares leads to kernel panic. The difference on copying over wifi or ethernet would be the speed (and even more copying from unraid shar
  5. Is anyone besides me experiencing troubles with network file transfert (from the Unraid file server to the VM) ? I'm using e1000-82545em as the script dictates, but on large file transfert I get a Kernel panic and it reboots... Using Vmxnet3 is ok for file transfert, but I'm having other troubles with it (like losing the network conenction). I have a Catalina (Clover) VM running with the same hardware and no problems with it.
  6. GNIIiiiiiiiiiiiiiii !! This is me trying to push up this topic. ^^
  7. Have a look here : Or just buy a Nvidia GT 710 ! (I have one and it works great with no tweaks in BigSur.
  8. Hello ! I'll try to keep it short : Fresh BigSur install (with Macinabox) on a 256Gb Samsung 980 PRO with the controller passed through. The drive is on now on a PCIe Gen 4 socket but it may important to note that it was (my mistake) on a GEN3 socket during the install. So before I moved it to the right socket, "System Report" reported : Link width : 4x / Link Speed 8GT/s (so GEN 3). Now, it's on the right socket, the lspci command gives : LnkSta: Speed 16GT/s (ok), Width x4 (ok) BUT, and this is the problem I can't find a solu
  9. You can take a look here : If I read correctly, the 1050ti is unsupported (as is my 1070...). But the trusty GT 710 is without a tweak ! (and it's a cheap card...)
  10. I'm here for some help again... I passed through my Nvme and I finally put it on the right soket (the one wich support GEN 4 over chipset). The command : lspci -vvvn -s 04:00.0 | grep LnkSta results in : LnkSta: Speed 16GT/s (ok), Width x4 (ok) But, in System Report, I get a blank for the "link speed" information. After the install of BigSur, as my drive was on the first socket (GEN 3), "link speed" was 8GT/s (as it should have been). Now how do I get my drive at 16GT/s under Big Sur ?
  11. I did not add NullEthernet.kext and ssdt-rmne.aml. I just added a line in DevicePropreties (in config.plist using OpenCore Configurator) as I just learned here. The method explained here aslo helped. It's doing the same thing, differently ^^
  12. Sooo... I might be of some help, for a change. I had the problem with login to my Apple ID and had various error messages like "could not communicate withe server" or "this computer already registered to many ID's" (or something like that. I did two things : 1 - I fixed the En0 following this guide. The problem was thas I had a network adapater as En0 but it was not marked as built-in. 2 - I notice that even if I filled out the "PlatformInfo" tab in the OpenCore Configurator as shown in the video (with mac model, serial number etc...) when I click
  13. About this "could not communicate with server" error that I also have, I do not know if it is related but Hackintool reports "Standard PC (Q35 + ICH9, 2009)" as Model indentifier instead of the MacPro6,1 I defined in the config.plist...
  14. Thank you for you answer but it seem over my capacities ☺️. I managed to find the path (PciRoot(0x1)/Pci(0x2,0x3)/Pci(0x0,0x0)). I added the device to "DeviceProperties" but I did not find out how to set the "built-in" property to true... (and I searched). But, I does not seem that having the nvme recognize as external drive will impact performance, right ? So I might just leave it like that.
  15. Hello ! And sorry if I post (again) my question in the wrong topic... Using the new Macinabos (with opencore), I managed to install Big Sur on my Nvme drive that has its controller passed through. So I have no <disk> in my template and everything seems to be working fine. But, the drive is recognize as an external drive is MacOs... I do not know if it is a problem or not, but my OCD would like it to be recognize as an internal drive. Is there a trick ?
  16. Great news ! I'm trying to install BigSur and passed through an Nvme controller directly. In the installation process, the drive is present but as an external drive... And I can't install BigSur on it. Is there a trick that I'm missing or is it more complicated (and I should only pass through the drive itself) ?
  17. Thank you for the quick answer ! I looked at Q17, and picked : And now it's working again ! Thank's !
  18. Sooo... I've been trying to figure this out on my own since two days but as I'm just failing at that, I'm asking for your help. Until last week, the docker was running without problem using Mullvad VPN. I think that the only thing that I changed on my system was to update the docker. My problem is that I can't access the GUI (connexion failed) because the app does not completely sarts... It gets into a loop : 2020-09-28 10:50:20,362 DEBG 'start-script' stdout output: [info] Starting OpenVPN (non daemonised)... 2020-09-28 10:50:20,401 DEBG 'start-script' stdout outp
  19. Well, I'm resigned to try CCC, but could someone help me with the procedure... ? From where do I work ? From inside the VM ? I do not believe that you can clone (virtual) drives working on the vdisks ?
  20. I find it hard to believe that there is no (command line) solution... The partition setup is the default setup from a "Macinabox" install. Is there something wrong to begin with ? If there is no other solution I will have to try CCC but what if I want to expand the drive again in the next years ? :-/
  21. Hello, So I succesfully installed Catalina with @SpaceInvaderOne Macinabox docker. Everything is now working (iMessage etc..) so I'm very cautious with what I'm doing. I started with a 60G vdisk and now I would like to expand the APFS partition. I managed to expand the vdisk to 120G but I coudl not expand the APFS Volume. sudo diskutil apfs resizeContainer disk3 0 Error: -69519: The target disk is too small for this operation, or a gap is required in your partition map which is missing or too small, which is often caused by an attempt to grow a partition beyond the
  22. Hi ! I installed 6.9 beta 1 and since then my NerdPack Plugin is endlessly trying to "retrieving plugin information ...". I tried to uninstall/install but it did not change anything. So : 1 - its normal as I'm on a 6.9 "beta", i just have to wait patiently for an update 2 - I did something wrong somewhere and I need to search how to properly remove and install the plugin again