[Fonts] RE: fonts problem after 4.3 update
Hi, This is the official reply I got from Trolltech when I told them about the problem while XFree was still in beta (2.4.99): --- [Snip: My question about AA'd and BM'd fonts being mangled] It seems that you have been affected by the ever changing Xft library. XFree86 4.2.1 still ships with Xft1, and the last Qt 3.0.x release only supports Xft1. Xft2 has been released separately from the XFree86 tree, and so we needed to add support for this in Qt 3.1.x. The current 3.1.x releases support Xft2, while maintaining Xft1 support. Rather long history lesson, what does it mean? I haven't seen any such problems here with 3.1.x and Xft2 from the fonconfig 2.1 release. If you have intermittent problems that popup after upgrading XFree86, then they must be specific to Xft in CVS, and nothing we can work around in Qt. All XFree applications as well as GTK applications that I run understand, see and render bitmapped fonts without a problem (xterm/Phoenix (Mozilla) etc). Qt applications do show the bitmapped fonts in the fontlist, but render them as some AA'd font (Lucida alike) with wrong (too wide) spacing. This is mostly due to a misunderstanding of Xft works. Originally, we were told it was similar to the standard XLFD interface. We quickly found out that it was not, and much of our logic was broken due to some changes in Xft. We are addressing this issue, and will have this working in Qt 3.2.0. We have considered fixing this for 3.1.x, but unfortunately the changes are too intrusive to do. --- Regards, Martin van Es ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[Fonts] No bitmapped fonts in Qt 3.1.1
Hi, I've been having on and off (more off lately) experiences with AA and BitMapped fonts under Qt 3.x. since I started compiling Xfree86 from CVS (4.2.99). At first AA fonts were disabled, then I had AA and BM'd and now only AA'd fonts. Don't get me wrong: I LOVE AA'd fonts, it's just that I'd like to use some of the BM'd fonts for my KDE interface as well (I like 'Clean' a lot!). All BM'd fonts show up in my fontlist, but they display as some default AA'd font (I suspect Helvetica) with too much whitespace between the characters. I'm a bit confused who's responsible for what when it comes to fonts. There is xft, xft2, fontconfig xrender etc. I compiled Qt 3.1.1 from source (with Xft support, more than once). What am I missing/doing wrong? I'm having troubles 'reading' the new font.config format, might there be some aliases that are ruining it for me? Old configs/stale installations seem impossible, since I allways compile X to a fresh X11R6/ directory, unless I am suffering from old configs somewhere in /etc? The symptoms are the same in qtconfig and The KDE font controlpanel module, so I suspect the problem to be at Qt/Xfree-level. Oh erm one last important remark: bitmapped fonts _do_ work in xterm (etc). It's really that Qt vs. XF-4.2.99 messes up for some reason. Regards, Martin ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[Xpert]no XV on i830 anymore
Hi, Since a couple of days my CVS build of X (14-dec-2002) doesn't do any XV accelerated video anymore. Any work going on on this part that could be responsible for this? card: i830 (mobile). DRM/DRI/AGPGART all load and initialize without a problem. XVideo and XVideo-MotionCompensation extensions load (but never intialize?). I upgraded the kernel driver (from current kernel 2.4.20) last week when i830_drv started to complain about the old one being outdated (needed 1.3 or so dl'd and built 1.3.2 from DRI). XV still worked after this change. Then I updated my debian installation from 'stable' to 'testing', updated latest CVS and made/installed my X CVS tree. After that mplayer renders a clear blue window where before that was nice looking video :-/ No complaints/feedback about not being able to initialise XV, just a clear blue window (and a mouse pointer that suffers heavily of load!) I realise the problem coincides with my update to 'testing'. However the X log shows no sign of any 'outdated' drivers, every extension/module is stamped 4.2.99.2. Since I noticed and read a lot is going on on the i8x0 side of X I thought I'd throw it in to see if the current behaviour is expected or could have been induced by recent changes? Regards, Martin van Es ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]no XV on i830 anymore
Hi, Since a couple of days my CVS build of X (14-dec-2002) doesn't do any XV accelerated video anymore. Any work going on on this part that could be responsible for this? card: i830 (mobile). DRM/DRI/AGPGART all load and initialize without a problem. XVideo and XVideo-MotionCompensation extensions load (but never intialize?). I upgraded the kernel driver (from current kernel 2.4.20) last week when i830_drv started to complain about the old one being outdated (needed 1.3 or so dl'd and built 1.3.2 from DRI). XV still worked after this change. Then I updated my debian installation from 'stable' to 'testing', updated latest CVS and made/installed my X CVS tree. After that mplayer renders a clear blue window where before that was nice looking video :-/ No complaints/feedback about not being able to initialise XV, just a clear blue window (and a mouse pointer that suffers heavily of load!) I realise the problem coincides with my update to 'testing'. However the X log shows no sign of any 'outdated' drivers, every extension/module is stamped 4.2.99.2. Since I noticed and read a lot is going on on the i8x0 side of X I thought I'd throw it in to see if the current behaviour is expected or could have been induced by recent changes? Regards, Martin van Es ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Fonts]AA, kde3 and xft continued
From: Vadim Plessky [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Fonts]AA, kde3 and xft Date: Thu, 5 Dec 2002 12:09:22 +0300 Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] | | Summary: | KDE3.0.4 (recompiled) lacks antialiasing support when compiled against | current CVS (19 nov 2002) of XFree86. This happens not only with XFree86 CVS, but with XFree86-4.2.1 (with FontConfig enabled) as well. Thanks for the insightfull comment Vadim! Ok, a little update on this (I couldn't read the archives anymore, too bad) and only recently decided to subscribe to the list again, sorry). Compiled Qt (3.1.0) against current CVS Xfree86 (4 december 2002). Compiled kdelibs and -base against the new Qt and have AA back in kde!! So happy. Now, however I can't use bitmapped fonts in native Qt apps anymore (qtconfig and mysqlcc e.g.) KDE does cope with them fine. I even see the bitmapped fonts in the list of available fonts in qtconfig, but the preview shows only empty squares (as if looking at the wrong encoding or so) needless to say all Qt apps show empty squares when choosing that as a default font). Also, KDM takes A G E S to start up now (a lot of HD activity involved), and does so EVERY time I start it, even logout/login, so whatever it does, it's not cached. XDM is there in a blink, so guess what I'm using as a greeter for the time being... KDE itself loads fine after XDM, so it really is only the greeter that is affected. I did not know the 'law of constant misery' (d:wet van behoud van ellende) was applicable on software as well? Anyone experiencing these probs as well? Regards, Martin ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[Render] AA, kde3 and xft
Hi, First my apologies for not being subscribed to this group. I _do_ check the archives on a regular basis though... I have a little question that has been haunting me for the past few days: Summary: KDE3.0.4 (recompiled) lacks antialiasing support (in the GUI) when compiled against a recent CVS (19 nov 2002) of XFree86. What I found out so far: My X env supports RENDER AA works with my current X (CVS) compilation (xterm -fa andale shows AA'd xterm). Even kfontinstall shows AA'd preview of the fonts!! (I switched on AA support in KDE/Kcontrol) I suspect I need working xft headers in order to have anti-aliased fonts in KDE? I assume the debian QT3 packages are compiled with -xft? ./configure decides to give up on xft because Xft.h refers to a file that can't be found. (But continues). Checking Xft.h reveals that it refers to freetype.h, which is available, not in the freetype dir but freetype2/freetype. Pointing to freetype2/freetype/freetype.h in Xft.h doesn't work, ./configure complains about not finding other files (turns off xft and continues). Moving freetype one level above (next to freetype2) results in a happy Xft.h in ./configure and included xft support. Compiling however fails on inconsistencies in multiple declarations of a function and the lack of others (originating from the found and accepted Xft.h). I remember reading that freetype is being turned upsidedown in this (4.3.0) release of XFree86 and things might not compile as you expect them. So I noticed. Question: should I stop and get some sleep since it will not work (soon) or is there a quick 'workaround' (like the one with the freetype dir I tried before)? Will Xft.h headers eventually work in 4.3.0, or is this a transition to a whole new approach of Xft? I see a Xft and Xft1 dirs in the CVS structure at the moment namely. Anyway, if someone could enlighten me a bit here, I'd be pleased... Regards, Martin van Es ___ Render mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/render
[Xpert]i830 revisited (recent CVS build)
Hi, First I'd like to thank Jens for his patient answer to my last question :) I managed to successfully build a recent (23/10/2002) build of the X CVS tree and see great improvements on the support of my chipset (well, looking at the XFree86.0.log at least). This posting cuts 2 ways: My XFree86.0.log is included for developers as reference material. I hope it helps ;) Second: Can anybody comment on my questions? The size of my screen is now correctly recognised (1400x1050) but alas, the driver still resorts to the known VESA resolutions (1280 x 1024). Is that the long list of modes I see coming by now? What do the asterisks mean for some of the found modes? Is the line Not using mode 1400x1050 (no mode of this name) based on the fact that no mode called 1400x1050 passes by during the mode probing part? Or is it something I can help in the Configuration file? I read somewhere that if linux boots in a different mode than what I want to drive it under X, modelines are required in the XFConfig file? The monitor I choose (generic 1400x1050) does not add modelines in the XFConfig file... Regards, Martin van Es This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.2 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 21 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.19 i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Thu Oct 24 13:35:32 2002 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Anaconda Configured (**) |--Screen Screen (0) (**) | |--Monitor Monitor (**) | |--Device Intel830 (**) |--Input Device Mouse0 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6.4/lib/X11/rgb (==) ModulePath set to /usr/X11R6.4/lib/modules (--) using VT number 7 ... (II) LoadModule: i810 (II) Loading /usr/X11R6.4/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.2.99.2, module version = 1.1.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.6 ... (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815, i830M, 845G (II) Primary Device is: PCI 00:02:0 (--) Chipset i830M found ... (II) Setting vga for screen 0. ... (**) I810(0): Depth 24, (--) framebuffer bpp 32 (==) I810(0): RGB weight 888 (==) I810(0): Default visual is TrueColor (**) I810(0): Option DRI on (II) Loading sub module int10 (II) LoadModule: int10 (II) Reloading /usr/X11R6.4/lib/modules/linux/libint10.a (II) I810(0): initializing int10 (WW) I810(0): Bad V_BIOS checksum (II) I810(0): Primary V_BIOS segment is: 0xc000 (II) I810(0): VESA BIOS detected (II) I810(0): VESA VBE Version 3.0 (II) I810(0): VESA VBE Total Mem: 8000 kB (II) I810(0): VESA VBE OEM: Almador Graphics Chip Accelerated VGA BIOS (II) I810(0): VESA VBE OEM Software Rev: 1.0 (II) I810(0): VESA VBE OEM Vendor: Intel Corporation (II) I810(0): VESA VBE OEM Product: Almador Graphics Controller (II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (--) I810(0): Chipset: i830 (--) I810(0): Linear framebuffer at 0x9800 (--) I810(0): IO registers at addr 0x9010 (II) I810(0): detected 8060K stolen memory. (II) I810(0): I830CheckAvailableMemory: 200700k available (--) I810(0): Pre-allocated VideoRAM: 8060 kByte (**) I810(0): VideoRAM: 16384 kByte (==) I810(0): video overlay key set to 0x101fe (--) I810(0): Maximum frambuffer space: 16300 kByte (==) I810(0): Using gamma correction (1.0, 1.0, 1.0) (II) I810(0): Currently active displays on Pipe A: (II) I810(0): LFP (Local Flat Panel) child device (II) I810(0): Size of device A:0x8 is 1400 x 1050 (II) I810(0): Lowest common panel size for pipe A is 1400 x 1050 (II) I810(0): Currently active displays on Pipe B: (II) I810(0): DFP child device (II) I810(0): No display size information available for pipe B. ... (--) I810(0): A non-CRT device is attached to pipe A. No refresh rate overrides will be attempted. (--) I810(0): A non-CRT device is attached to pipe B. No refresh rate overrides will be attempted. Mode: 20
[Xpert]i830 refuses to run in 1400 x 1050
Total Mem: 8000 kB (II) VESA VBE OEM: Almador Graphics Chip Accelerated VGA BIOS (II) VESA VBE OEM Software Rev: 1.0 (II) VESA VBE OEM Vendor: Intel Corporation (II) VESA VBE OEM Product: Almador Graphics Controller (II) VESA VBE OEM Product Rev: Hardware Version 0.0 (II) Loading sub module ddc ... (II) I810(0): VESA VBE DDC supported (II) I810(0): VESA VBE DDC Level none (II) I810(0): VESA VBE DDC transfer in appr. 0 sec. (II) I810(0): VESA VBE DDC read failed (==) I810(0): DPI set to (75, 75) (--) I810(0): Virtual size is 1280x1024 (pitch 1280) (**) I810(0): Default mode 1280x1024 (**) I810(0): Default mode 1024x768 (**) I810(0): Default mode 800x600 (**) I810(0): Default mode 640x480 (II) Loading sub module fb ... (II) Loading sub module xaa (II) Loading sub module ramdac ... (==) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. ... (==) I810(0): Default visual is TrueColor drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed [drm] failed to load kernel module i830 (II) I810(0): [drm] drmOpen failed (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. (==) I810(0): Write-combining range (0x9800,0x800) (II) I810(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) I810(0): Adding 256 scanlines for pixmap caching (II) I810(0): Allocated Scratch Memory (II) I810(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Horizontal and Vertical Lines Offscreen Pixmaps Setting up tile and stipple cache: 20 128x128 slots (==) I810(0): Backing store disabled (==) I810(0): Silken mouse enabled (II) I810(0): Initializing HW Cursor (II) I810(0): direct rendering: Disabled Regards, Martin van Es ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
