-
Notifications
You must be signed in to change notification settings - Fork 42
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
FBV not compatible with some framebuffer drivers on 6.1.13+ kernels #30
Comments
Here is a kernel commit which breaks fbv: "Takashi Iwai [email protected] Reverting it makes the fbv working with latest kernels and all drivers. After reading this thread: I dont think upstream is going to revert this commit as it fixes some other issues (kernel oops in certain situation). Fim/fbi works OK so it should be possible. Thanks |
Interesting. I'm also curious about this. Also heard about some "kernel changes". Always get worried when I hear this. Although I'm not apparently experiencing any problem myself, with kernel 6.2.1. I'm using fbv to both browse pictures and set a background image to my fbterm terminal. I'm keeping an eye on this issue to see what is really happening, and leave my feedback. Maybe useful for others. I'm a heavy user of the terminal and the framebuffer. I dont boot a desktop. I dont even boot X11. Fbv and other framebuffer programs have been serving me very well to watch movies and see pictures. I'm on Archlinux, uname -a
pacman -Qi fbv
I use fbv to set a background image with fbterm wallpaper_fbterm.sh
Links: https://wiki.archlinux.org/title/Fbterm |
As stated previously only some drivers are affected. Real hardware may work OK, I guess their drivers (i915, radeon, etc) do not use the code from:
Thanks |
For everyone who searches for working solution on newest kernels I found a way to draw in framebuffer directly.
|
Hi Team,
As title says - I'm not able to use fbv on latest kernels with certain drivers.
Seems that kernel 6.1.13 (or maybe 6.2.0 and patches were backported to 6.1.x LTS kernel?) introduced changes the the framebuffer code which broke fbv:
https://lkml.org/lkml/2023/2/20/511
According to my tests some drivers work:
uvesafb
efifb
and some do not:
vboxvideo (VirtualBox)
vmwgfx (VMware)
hyperv-fb (Hyper-V gen1)
hyperv-drm (Hyper-V gen2)
I have tested it using Ubuntu-22.10 and 6.1.13 kernel from ppa mainline.
On non-working platforms, sometimes I can get the picture displayed if i send the image to /dev/fb0 using fbv and then manually "refresh" the console using e.g dmesg command (image displays then on the right side of the screen).
Other framebuffer viewers like fim, fbi are not affected (but i prefer fbv due to its simplicity).
Any chance to get it fixed?
Thank you.
The text was updated successfully, but these errors were encountered: