login
Search
First of all I have built every 2.6 kernel without any problems. The problem I'm having is only with 2.6.5. The really weird part is when I run make xconfig I only get little square boxes for the text? It's like it is using the wrong font or something. Now this is only from within the 2.6.5 directory and not from any other 2.6.x directory.
Anyone have any ideas?
BTW I just use my 2.6.4 config file and run make oldconfig before I run make xconfig.
2.6.5 xconfig font problem
I'm using Mandrake 9.2 and I've got exactly the same problem with xconfig. Like you, I'm upgrading from a 2.6.4 and used oldconfig to upgrade my config file.
2.6.5 xconfig font problem
I noticed the same problem on a RedHat 7.2 machine, a RedHat 9.0 machine, and two Fedora Core machines. All other 2.6 series work fine with xconfig. Setting XFT_DEBUG on my machine shows the following on the earlier 2.6.X kernels :
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/l048013t.pfa: 0 (13.3333 pixels)
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/l048013t.pfa: 0 (13.3333 pixels)
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/l048013t.pfa: 0 (16 pixels)
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/l048016t.pfa: 0 (16 pixels)
For kernel 2.6.5 I get :
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/cursor.pfa: 0 (13.3333 pixels)
XftFontInfoFill: /usr/share/fonts/default/Type1/s050000l.pfb: 0 (13.3333 pixels)
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/cursor.pfa: 0 (13.3333 pixels)
XftFontInfoFill: /usr/share/fonts/default/Type1/s050000l.pfb: 0 (13.3333 pixels)
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/cursor.pfa: 0 (16 pixels)
XftFontInfoFill: /usr/share/fonts/default/Type1/s050000l.pfb: 0 (16 pixels)
XftFontInfoFill: /usr/X11R6/lib/X11/fonts/Type1/cursor.pfa: 0 (16 pixels)
XftFontInfoFill: /usr/share/fonts/default/Type1/s050000l.pfb: 0 (16 pixels)
But no complaints. Anyway, "make menuconfig" works fine, so it isn't a showstopper, just annoying.
2.6.5 xconfig font problem
Follow-up on my earlier post about the difference in fonts between the
kernels. If I just go in and do a kludge fix, by renaming the
"/usr/share/fonts/default/Type1" directory to "/usr/share/fonts/default/__Type1"
and run make xconfig, everthing works fine. I changed it back after using xconfig to build the kernel. Not ideal, but lets me build easily, and get some other work done before the bosses get suspicious!
Possible Solution
One way you might get it working is to import or load the old config file manually instead of actually copying it into your linux source directory and loading it. This should be the preferred way, because options do get changed between versions and you'll get cruft in that file otherwise.
/usr/share/fonts/default/__Type1
I have tried renaming this directory and I still have the problem ...
I tried adding a symlink to t
I tried adding a symlink to to do __Type1 and _Type1. No help here.
rename, not symlink
I think the key in the other post was not to have a
"/usr/share/fonts/default/Type1" directory in existence at all, so that xconfig is forced to use another type of font completely (or something.) In other words, don't make symlinks because that leaves the Type1 directory in existence; just rename the Type1 directory (it doesn't matter what to) as a backup basically, then rename it back when you're done so that everything else works as expected.
This guy is right...
If you set XFT_DEBUG (export XFT_DEBUG=1, or "setenv XFT_DEBUG 1") you can see what fonts qconf loads. Anyway, the font server checks the directories often, so if you change it, then wait any real amount of time, you will see that it "refinds" the renamed directory (in my case __Type1) and I get the same problem. If I rename it, immediately go to
/usr/src/linux-2.6.5, type make xconfig, it works. Try to run "make xconfig" again after closing one session, and it is crap again. If you simply move it out of /usr/share/fonts/default into something not in the font servers search path, xconfig will run fine (but other things may not) For a quick build, you can do it, then move it back. Perhaps the font server or fonts need an upgrade. I was lazy and noticed this problem last sunday, when the 2.6.5 came out, and I sat back expected to see a billion threads complaining about this, with fixes, and there wasn't, so it probably isn't a universal problem. I'm going to rebuild the font server and fonts, so I'll let you know what happens.
XFT_DEBUG
It seems like removing all strange font folders from /usr/share/fonts/default/fonts.cache-1 may save the day.
Fixed
I ran qtconfig and turned off anti-alias XTF in the Fonts section and saved the settings. After that I was able to run xconfig.
Fixed (let me rephrase)
I turned off the option labeled "Enable Anti-Aliased Font Support (Xft).
Now I'm going to pull the lint out of my eyes.
qtconfig did the trick! Than
qtconfig did the trick! Thank you very much.
Mike S
Kernel 2.6.5 xconfig font problem
according to
http://www.webservertalk.com/message194869.html :
remove ~/.fonts.cache-1 and ~/.qt/
(home of user which runs 'make xconfig')
I had the same problem and it fixed it [running Mdk9.2].
cu
_goto
.
Kernel 2.6.5 xconfig font problem
just change the defualt font in qtconf. this sould do the trick;)
Kernel 2.6.5 xconfig font problem
Yes....your trick worked well.
Changing the default font will do the job
Kernel 2.6.5 xconfig font problem
How change de default font ?
See : http://kerneltrap.org/n
See : http://kerneltrap.org/node/view/3372