DrMucki
-
Posts
36 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by DrMucki
-
-
Danke. Habe mir jetzt ein automatisches Backup Tool installiert (appdata Backup, das macht auch das Flash Drive mit)
-
Hab den Stick, da er ja anscheinend nicht ansprechbar war, rausgezogen. Am Mac war er lesbar. Also schnell nen Backup gemacht, wieder in den Server, reboot… und siehe da alles geht wieder….
warum , keine Ahnung. Ich mach jetzt erstmal Backup
danke
-
Hallo,
ich habe gerade gemerkt, dass ich ein Problem mit meinem Flash Drive habe.
Grosses Ausrufezeichen mit dem Hinweis. Flash device error.
auf Main: REGISTRATION
Unraid OS Flash device errorunter Apps komm ich gar nicht mehr.
ein Backup scheint nicht zu funktionieren, aber er zeigt mir das Flash Drive noch an.
der Server läuft noch, Reboot traue ich nicht…. Flash backup klappt nicht.. Zugriff nur von iPad aus möglich, vom Mac aus bekomme ich immer einen http 500 error..
Hat jemand einen Tipp, wie ich das wieder hinbekomme?
Ich habe nochmal die Diagnose files hinzugefügt.
wäre super wenn einer einen Tipp hat.
vielen lieben Dank schon mal
-
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
-
1 hour ago, CodingMicrobe said:
@DrMucki also why use Splashtop? Can you try just plugging in an HDMI/VGA/DP cable directly to your motherboard to see if you get output from iGPU Windows VM - without Splashtop at all? That can help narrow down if the issue is with Splashtop & AMD iGPUs, or with the passthrough itself.
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
-
1 hour ago, CodingMicrobe said:
So it sounds like you got it working, but it was very very poor performance, with poor resolution and lag on keyboard/mouse inputs?
What specific motherboard & BIOS version do you have? I can extract the VBIOS from that version of the BIOS for you. Maybe there is a newer version.
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 CETI 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...
-
9 hours ago, CodingMicrobe said:
Have you checked this post out? That message (type 127) seems to be an AMD thing when the GPU can't reset properly: https://forums.unraid.net/topic/76510-execution-error-internal-error-unknown-pci-header-type-127/
EDIT: it may be possible to extract iGPU VBIOS with UEFITool, but I believe this is Windows-only (unsure, just found this online), see https://github.com/LongSoft/UEFITool/issues/26
EDIT2: I think I got the Renoir APU VBIOS, I will PM you and if it works, I'll make it public.
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. -
7 hours ago, steve1977 said:
I am facing the same issue. Everything used to work well. Then switched back to VNC and I am getting the error above. And after switching back to GPU-passthrough, it no longer works. Used the script a few times both with and without GPU. But no luck!
Any ideas?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
-
25 minutes ago, ghost82 said:
mmm..ok thanks for the logs..
First: can you check if the R7 370 is uefi compatible?
In other words, if you force the bios to boot in uefi mode instead of legacy bios does the R7 works?
If your R7 supports uefi mode, then make sure to boot unraid in uefi mode (go into your unraid settings to allow uefi boot).
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...
-
16 hours ago, ghost82 said:
Opencore is compiled into 2 versions: debug and release.
Macinabox includes the release version.
Debug version should be used when issues appear, because by changing the key "Target" to 83 in the config.plist, you will be able to log to a file all of the things the bootloader is doing, saved in the root of the efi partition.
The release version is able to log too, but with less information saved.
I don't know which release version macinabox includes, maybe 0.6.4: if you go to github.com/acidanthera/opencorepkg and you click on "releases" on the right of the page, you can download the precompiled "debug" version and replace the files in the efi, then changing Target to 83 will let you save to a log file.
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
-
29 minutes ago, ghost82 said:
If it didn't work I would not have too much hope..I'm afraid but I'm out of ideas
If 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..
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
-
2 hours ago, ghost82 said:
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---
-
1 hour ago, ghost82 said:
It should only apply to vnc display.
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...
-
1 hour ago, ghost82 said:
no problem take your time and check carefully the code: please note that I edited the code of DeviceProperty because of an error, so refresh the page and check.
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
-
1
-
-
1 hour ago, ghost82 said:
Otherwise try to inject spoofed device-id property with config.plist only, without ssdt.
You could add the following snippet of code in the DeviceProperties-->Add in the config.plist:
<dict> <key>PciRoot(0x1)/Pci(0x1,0x4)/Pci(0x0,0x0)</key> <dict> <key>device-id</key> <data>10680000</data> </dict> </dict>
So that it becomes:
<key>DeviceProperties</key> <dict> <key>Add</key> <dict> <key>PciRoot(0x1)/Pci(0x1F,0x0)</key> <dict> <key>compatible</key> <string>pci8086,2916</string> <key>device-id</key> <data>FikA</data> <key>name</key> <string>pci8086,2916</string> </dict> <key>PciRoot(0x1)/Pci(0x1,0x4)/Pci(0x0,0x0)</key> <dict> <key>device-id</key> <data>10680000</data> </dict> </dict>
Here comes another problem...as you can see I wrote the gpu address as PciRoot(0x1)/Pci(0x1,0x4)/Pci(0x0,0x0)
but this is MY gpu address, because I found it in ioreg with the gpu attached...But how can you know your gpu address if the gpu is not attached?
By guessing?
All we know is that the gpu will be under a bridge in qemu: the PciRoot(0x1) is OK, what may change is the second address Pci(0x1,0x4): this corresponds to pci-bridge@1,4
I would try in order:
Pci(0x1,0x4)
Pci(0x1,0x1)
Pci(0x1,0x2)
Pci(0x1,0x3)
Pci(0x1,0x5)
Not sure about the lat path Pci(0x0,0x0) if it can change or not...probably not..
Sorry, I know there are a lot of variables to test...
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?
Flash device error:
in Deutsch
Posted
Super Tipp. Vielen Dank