DrMucki

Hier sind die Einstellungen….

Hallo zusammen ich hab das gleiche Problem, komme aber nicht weiter (OS 6.10.2). Das device (eine USB HDD) wird remounted unter /mnt/disks/WD_Elements_2620 , darunter kann ich auch die Datenfreigabe durchsuchen, aber einen SMB share bekomme ich nicht hin. Es steht auch nur einmal "Mount" da und zwar bei dem Device, nicht aber bei der wohl automatisch gemounteten partition (Exfat) was mache ich falsch?

sorry for the question... but how to change the bios within Unraid for the vm... it only gives me OVMF...

Thanks a lot. I will give it a try and will post the results here. How did you manage to extract the vbios? Can you explain it to us here. A step by step how to could be useful, even for those who come will find this post here

It is a headless system... there is no Mouse/keyboard or even a monitor.... Just SSH and web....I will give it a try with the monitor within the next days.. I have to completely remove the system. which is within a server rack... but not today anymore and with this I can go the latest bios as well

Yeah that is right. i have a ASUS PRIME A520M-K. Unraid gives the following Infos: ASUSTeK COMPUTER INC. PRIME A520M-K, Version Rev X.0x American Megatrends Inc., Version 1401 BIOS dated: Fri 04 Dec 2020 12:00:00 AM CET I know that there is a newer bios but I did not install it so far

Thank you. I am just trying to get it to work with your bios... What I did so far... Set up a Win 10 VM which is working with VNC or with a AMD GPU. For the AMD GPU and the iGPU Part and their sound part are both bound to VFIO.. First tried the VNC --> Working with all resolutions tried my GPU with my extracted Vbios... working perfectly changed to AMD Renoir with your bios... first I got an error in the log file. Started it with no changes a second time... no Errors are shown.. and yeah Splashtop connects... windows login screen is coming up (ugly resolution, black and white). You can log onto it and it takes ages to show a screen. Ok its color but the resolution.... and there it comes it very very laggy on keyboard or even. mouse inputs . I was not able to interact with the machine at all.... May be you can tell me how you extracted the bios... I will give it a try on mine 4650g...

I would really appreciate your APU Vbios for the 4650.. can you post it here of send it to me via PN... on which unraid version are you? Did you get it to passthrough for windows VM or even with macinabox? how did you manage to get it? I tried to use the tool of Spaceinvader one, but that did not work...

4650g doesn’t work so far. I added a AMD GPU... but that only works in windows so far

Ok once again: here the solution: but as I told before: use the search function or click on my name, than you will see my posts...there is the solution... copied it for you here.... because me was helped as well here.. The problem is, that when you switch back from gpu to VNC add using the Macinabox helper script, the bus from the vnc is not set correctly. To fix it do the following: After switching back from Gpu to VNC and running the helper script, go to your vm setting of your vm and Open the XML view (right corner there is a switch Form view). scroll nearly to the end. You have to change the XML in this part: </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/> for me worked CHANGED to bus='0x00' slot='0x02' function='0x0' </video> but you must not run the Helper script afterwards.

I think I answered the question with the issue switching back to VNC several times here, when the display says: guest Display not initialized... the script changes the bus for the video in vnc the wrong way. You have to set it back manually in the xml after you run the script. if you want to know exactly how, please just use the search function within this forum please. I do not have it here now... Marc

The problem is, that when you switch back from gpu to VNC add using the Macinabox helper script, the bus from the vnc is not set correctly. To fix it do the following: After switching back from Gpu to VNC and running the helper script, go to your vm setting of your vm and Open the XML view (right corner there is a switch Form view). scroll nearly to the end. You have to change the XML in this part: </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/> for me worked CHANGED to bus='0x00' slot='0x02' function='0x0' </video> but you must not run the Helper script afterwards.

Hi maybe I can help you with returning to VNC.. does the VNC say that guest display is not initialized....? But I also having trouble enabling my amd gpu...

Sorry about what? I mean in the Bios of my mainboard , I did not find any option to change between UEFI and legacy there in the bios. I think it is UEFI. Unraid is defintely in UEFI mode (checked it within the syslinux config).... just checked my Windows VM with it, still works fine with passthrough. May be we can find out there anything?? I also got the radeon software installed, may be we get some needful information there?? Would a dummy HDMI Plug help here? I was just wondering, because my windows VM was not accepting resolutions higher than 1600x1200

I did not bother before about UEFI and legacy... so everything was set to UEFI when setting up. Unraid is already booting in UEFI Mode and in windows VM the GPU passthrough works. Should I switch to legacy, but how to do it........ IN the morning I had a quick look to my bios of the motherboard (ASUS) but I did not find anything to change there...

Ok, did that at installed the debug version (replaced the files mentioned here https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/debug.html and followed the instructions) finally I was able to create some log files. For comparison I created the 3 files: 1st: (VNC): I started up the VM with the standard config.plist without any changes (except the ones for the logging) 2nd(VNC with new config): I changed the config.plist while adding the part in Device Properties and booted up with this in VNC Mode 3rd (GPU with new config): I modified the VM (added GPU and vbios) run helper script and started the VM. 4th(VNC Spoofed GPU). I modified the VM Back to VNC and added the config.plist with the Spoofed GPU mal part, deleted the APCI part which was added in 2) 5th (GPU spoofed). Added the GPU with VBIOS and started again... I looked throughout them and. th 3rd and the 5th one are complaining about missing compatible GOP. Googling around with missing GOP and R7-370 didn't get me any hints opencore-2021-01-09-101113(VNC).txt opencore-2021-01-09-103445(VNC with new config).txt opencore-2021-01-09-103843(GPU with new config).txt opencore-2021-01-09-121610(VNC spoofed GPU).txt opencore-2021-01-09-124847(GPU spoofed).txt

it's ok... I wasted many hours of your time...... and mine... but if I will not work I will give it up. I am trying to get from 0x0,0x0 to 0x5, 0x5 with all combinations and than I will stop it. I always have to wait for 60 sec to get the VM a chance to come up.. with vnc I get a response after 30 sec.. What do you mean with "f you can replace opencore files with that of a debug version and obtain a full log of a gpu failure maybe we will have some for info to evaluate.." I need a little help with it.. google was not so helpful. Otherwise may be you have suggestion for a GPU for max 150 Euros, which will work out of the box 🙂 I am sorry for not being as smart as you with these things. BTW where are you from? seems to be the same time zone 🙂 as here in Germany

Thank you with this file OC shows no error (of cause :-)). I went back went the GPU and tested (0x1, 0x4) and the numbers from 0-5 at the last position.. now going on to check 0x2, 0x0... what numbers are logical to test I mean the first an the second part.... 0xa,0xb. (where a and b are ini which range) to ask mathematically---

ok. So the only way to check if the machine starts is Teamviewer coming up , right? I edited the config.plist, but I think I misunderstood you somewhere First I checked it with vnc without gpu, machine was starting but when opening with OC it complained about the config.plist when opening it "OpenCore Configurator was unable read because it isn’t in the correct format. Please fix the following code before saving: Found non-key inside <dict> at line 212" I did not manage to fix it...maybe I forgot something or added wrongly. Would you mind having a look to my edited config.plist please? Thought I had to check my config before adding the GPU... config.plist

Before i will start with it i got a further question when changing from VNC to passthrough back to VNC the following in the XML gets wrong after the script: <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/> </video> It leads "the Guest has not initialized the display yet error" changing the red part to: bus='0x00' slot='0x02" fixes the problem... when swapping to GPU XML changes like this <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disk1/isos/vbios/ATI.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> I am just wondering if this error also occurs, when changing to gpu and i cannot see it, beacuse i do not have vnc... and it stucks somewhere there..... What do you think

I tried the other aml... with no success will go on with the other method withoud SSDT... Just to get it right...... I will boot in VM, restore my old config, add the code snippet in config.plist add gpu and restart.... I think it could be a good idea to mount the disk in unraid terminal, modify the config.plist there and try it this way. So i do not have to restart the vm in vnc to do the changes there.... <key>PciRoot(0x1)/Pci(0x1,0x4)/Pci(0x0,0x0)</key> the red part is the part to change... right?

Thank you. I will give it a try.... plz stand by 🙂 this will take a while.... Doing this while in homeoffice.... but now breakfast....

I just trief I did it on the unraid server using the terminal... I just copied your aml file to the efi folder unmounted and rebooted.... Am i doing correct... I always switch back to vnc, booting back the vm, do the changes in OC, powering down Vm, edit the VM to passthrough with vbios, helper script, starting the machine... but than the only way is Teamviewer to check... and this is not coming up again so with your 1st file nu success .Where to check whether the path is correct? Can i do this within the vm ( i dont think so because im not getting i the vm with the card passing through) Meanwhile I will try the other file you provided... Thanks for your help so far....

Just started from scratch and the vm is working again. I also got it managed to mount the disk, but this ended up with a stable apple logo... so start from scratch looks only an hour ..... But I did not get it managed to get it started with the amd passing through. Here is what I did, for trying it to get to work: 1. found the Device ID from my GPU: Device: Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [6811] 2. discovered the firmware path: cat /sys/bus/pci/devices/0000:01:00.0/firmware_node/path \_SB_.PCI0.GPP0.X161 3. Edited the provided SSDT-GPU-SPOOF.dsl file a) changed the firmware path , wherefore I changed twice the "EXTERNAL" and the "Scope" changed the spoofed "device id" to 0x11 , 0x68 and renamed the model (Did I forget anything here or did I make a mistake? I provided the file at the end...) 3. Downloaded MaciASL and double clicked my .dsl file and saved it as aml file 4. opened Openconfigurator and mounted the partition and opened it. Looked for the config.plist and double clicked it to open it with OC 5. On the first page I saw several aml files, so I dragged and dropped my aml. file here and saved the config.plist, and unmounted the partition (I am not sure for this step, so I decided to do as described, may be it is wrong....) 6. Did a shutdown and started the vm again... I did not change anything in the VM , because I want to see if the VM comes up. It does and it started without any problems. Teamviewer starts up automatically and I was able to get in via TeamViewer . OK Shut Down.... 7. Edited the VM: changed graphics to AMD Radeon, added VBIOS, Saved changes, runned helper script and started the VM again. VM is starting but no possibility to get in via TeamViewer 8. changing back to VNC (after editing the known bug in the xml file..) brings back the machine... but with no amd- What am I doing wrong? Thank you for your help! SSDT-GPU-SPOOF.aml SSDT-GPU-SPOOF.dsl config.plist config.original.plist

i totally messed up my config.plist the vm is not booting anymore. I got a copy of my old config.plist, but i don't now how to mount the proper image and where it is.... I don't get into the boot menu, because i configured it in opencore to boot directly into the image.... Any help appreciated