I use vesa frame buffer in console. The problem looks like the first and second letter in each row are too close to each other. The second letter seems not to have the first column of pixels so it looks like it's too close to the first one. It is too narrow in some way. I know it sounds strange but that is what I see. Graphic card is ATI IGP-345. System is gentoo build a few days ago. sysfont lat2-16. When I use midnight commander the same effect occur. Machine: Sony VAIO laptop PCG-FR285M.
ps. the kernel version is 2.6.2
Does this happen right after the boot is finished (ie. BEFORE X is started)? Do you use any vesafb patches (like the refresh-rate change patch)? In which vesa modes does it happen? Could you tell us the kernel parameters you use?
Created attachment 25884 [details] this is config file for my kernel (2.6.2)
It happens just from when kernel loads frame buffer. It is permanent. I mean if i switch to X and then back to console it is still there. It is on every console. Frame buffer mode is vga=791. No patches applied by myself. Kernel emerged is 2.6.2 from gentoo servers. X looks fine. No problems there. Refresh rate is 60Hz (1024x768). Accualy when I look at it there might even be 2 columns of pixels missing in each second letter (each row). Not shure about that. If you tell me how to get a screenshot in console I'll prepare it for you :). Previously I used 2.6.1 kernel with slackware and all was fine. Now switched to gentoo and the bug is there. I tried different fonts and the result is the same. So I guess it has something to do with VESA frame buffer itself. I attached kernel configuration file. If you need any more information or testing fell free to ask me.
Ok. I did some more research. I found out that this is not right from the begining. It boots fine but when I switch to X and then back to console the bug is there and is there untill I power off the machine. Sorry, my mistake... I thought it is there just from when kernel loads vesa fb but it is not. Now it may be somehow related to Xfree??
Yep, XFree often doesn't play nice with framebuffers because usually the drivers perform no memory management whatsoever on certain reserved areas of memory. Can I suggest that you try out xfree-4.3.99.902-r2?
I've got the same problem here with vesafb on fb and nvidia on X, and it's definitely related to X. If you want to have even more fun, you can try starting X, exiting it and then starting it again ;) On my system it results with a completely garbled vesafb console. Unfortunately, there isn't much we can do about it :/ Anyway, please tell us if the new XFree version solved the problem.
Ok. I emerged xfree-4.3.99.902-r2 and it did not solve the problem. it looks exacly the same.
Ok, we just might be able to (at least partially) solve this problem in a few days, please stay tuned - more details will follow :)
Reassigning to me to make sure I don't forget about this bug ;)
Ok, it has been a lot longer than a few days, but here it is: http://dev.gentoo.org/~spock/#vesafb-tng Please read the instructions on my page and install the patch. It will hopefully fix all your problems. Please report vesafb-tng related bugs (if you encounter any) directly to me.
Closing and marking as fixed as nothing more can be done here.
