Forcefully-remove-bootfb Alternatives

forcefully-remove-bootfb reviews and mentions

• VM works on 5.17.5-200.fc35 but not 5.17.5-200.fc36
  1 project | /r/VFIO | 10 May 2022

  Nice find, https://github.com/furkanmustafa/forcefully-remove-bootfb fixed it for me.

• Dealing with VFIO-related issues on Fedora 36 (beta)
  1 project | /r/VFIO | 5 May 2022
• Single GPU Passthrough: EFI-Framebuffer "No such device"
  1 project | /r/VFIO | 27 Aug 2021

  If you are bound to the simplefb, you might still run into the same issue due to BOOTFB occupying the same memory space as your GPU. You can see if this is the case by doing cat /proc/iomem and looking for the pcie address of your GPU. I personally reverted to an older kernel and bypassed this because I was having other issues at the time, but if my guess is correct, you should be able to forcefully unmap BOOTFB with this repo

• 6600XT passthrough
  2 projects | /r/VFIO | 12 Aug 2021

  My next step was to try a later kernel that supports my card so I could replicate the environment (at least somewhat) I had with my 580. Unfortunately, with the edge kernel from alpine I get the (paraphrased) error Failed to mmap 0000:0b:00.0. Performance may be slow. I found that alpine's edge kernel version uses simplefb instead of efifb. I did the following on the above bind script: sed 's/efi-framebuffer/simple-framebuffer/g' -i bind_devices.sh to no avail. The gpu was clearly unbound from the framebuffer with this modification, but BOOTFB (AFAICT, the simple-framebuffer) was still in the same address range as my GPU in /proc/iomem, which of course means the 'Failed to mmap' error remained. I found a repository that forcefully unmaps BOOTFB's address range and ran that script (after compiling the kernel module of course) after unbinding the simple framebuffer with still no luck. After work, the plan is to

• A note from our sponsor - SaaSHub
  www.saashub.com | 10 May 2024

  SaaSHub helps you find the best software and product alternatives Learn more →