From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: When I choose a different system font in /etc/sysconfig/i18n: SYSFONT="lat0-08" and I then switch between X (terminal 7) and a text mode virtual terminal (f.e. terminal 1), my system font gets messed up. Seems like it suddenly has a line spacing of 1.5 or 2 lines. I do not have this problem when I use the default system font. I have kernel option vga=ext Version-Release number of selected component (if applicable): updated system up to dec 1st 2004 How reproducible: Always Steps to Reproduce: 1. see description above 2. 3. Additional info:
The X server saves the entire state of the video card at X server startup. Any time you switch from X back to the console, it restores this initial state that it saved at startup, even if you later change the console font or other aspects of the console video state. This is normal and expected behaviour. If you completely quit the X server, and then change the console video state in any way, and then restart the X server, when you switch between VTs, the video should be restored as expected. Please try this and confirm wether it works for you or not. Thanks in advance.
I did some more research on different machines. I am not currently at the machine that has the problem but to my best memory it is as follows. The machine with the problem has a 2.6.9 stock kernel, and a 865G chipset, no frame buffer enabled, and kernel commandline option vga=ext. I suspect the _no_ framebuffer - vga=ext combination. Other machines that have a framebuffer have no problems. I can change the font as I like on them.
Similar problem on "Intel Corp. 82915G" card ("i810" X driver). After switching from X to console, console fonts are reset to some hardware default. Due to this all national (not ascii) symbols disappear. Some words about this issue have already appeared on x.org site, see https://bugs.freedesktop.org/show_bug.cgi?id=2277
*** This bug has been marked as a duplicate of 145969 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.