-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cat: rom: Input/output error #3
Comments
I am having the same problem FYI. |
I had also received the cat: rom: Input/output error when dumping my RX550 vbios. I had to actually start a Windows VM that had the RX550 already passed through to it (no vbios specified). I then shut down that VM and ran the script. Which worked. I had found the following in my syslog when the vbios dump script was run and failed.
Searching for that brought me to https://www.redhat.com/archives/vfio-users/2019-March/msg00004.html His experience was exactly the same as mine. |
I also am having the same problem. I tried what @0v3rcome mentioned (started a vm with GPU passed through, no Vbios, stopped it), and still see the same error unfortunately. |
Adding this to the syslinux config (this can be easily accomplished through the Unraid UI), rebooting, then running the script worked for me:
You'll want to remove that and reboot once again after you've successfully dumped your vbios. Thanks @0v3rcome for the link to that thread. |
I have the same error: On 6.10.0rc2 w/ nvidia 2080 super founders
I tried binding the card to vfio, appending the It always ends up with the same |
I was running into this error a lot, I followed all of the suggestions and no dice. What actually worked for me was trying one of the vbios from the techpowerup db, editing the hex file. Trying it out. That didn't work but when I shut down the VM and tried again, I got a 76kb vbios which worked - sorta. It at least allowed me to get into Windows but after doing all of the driver installs for the graphics card, I shut down the VM and ran the script again after going into System Information and binding the graphics card. (MAKE SURE THE VM ISN'T SET TO AUTOSTART), reboot after binding and presto, worked fine and got my 980 vbios. |
I am having the same issue with this device: Alder Lake-N [UHD Graphics] ❯ echo 1 > /sys/bus/pci/devices/0000:00:02.0/enable
echo: write error: device or resource busy Or: ❯ cat /sys/bus/pci/devices/0000:00:02.0/rom
cat: '/sys/bus/pci/devices/0000:00:02.0/rom': Input/output error |
@bolzerrr I too got the same error but what I did is followed spaceinvaders tutorial to get the vbios without dumping |
I found that having device bound to any driver actually hinders the VBIOS dumping, |
@0xE1 Thanks! I'll try it out later. |
I'm also having this issue. Using an AMD RX560, so I don't believe the youtube tutorial linked a few messages ago will work for me (as it's for Nvidia GPUs). I've already tried each of the potential workarounds mentioned in this thread but have had no results. |
I followed your tutorial, and got the "cat: rom: Input/output error" error. Installed the "VFIO-PCI Config" plugin, marked both nvidia devices, saved config, rebooted and still get this error..
Edit: I should mention that once I saw output on the screen connected to the card, it said something about not finding a file or something.
Edit2: I increased the sleep time in "startstopvm()" and could see the error messages:
The text was updated successfully, but these errors were encountered: