CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/07/15 17:38:42 Log message: 303. Fix a typo in the XSetWMProtocols(3) man page (#5697, Alexander Pohoyda). Modified files: xc/doc/man/X11/: XSeWMProt.man Revision ChangesPath 1.5 +2 -2 xc/doc/man/X11/XSeWMProt.man ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/07/15 17:50:13 Log message: 304. Fill out the sunleo man page (#A.1783, Arnaud Quette). Modified files: xc/programs/Xserver/hw/xfree86/drivers/sunleo/: sunleo.man Revision ChangesPath 1.3 +40 -4 xc/programs/Xserver/hw/xfree86/drivers/sunleo/sunleo.man ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/07/15 17:54:00 Log message: 305. Fix missing newline in Message - MessageF transition in dri_glx.c (#A.1833, Alexander Stohr). Modified files: xc/lib/GL/dri/: dri_glx.c Revision ChangesPath 1.14 +3 -3 xc/lib/GL/dri/dri_glx.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/07/15 20:08:37 Log message: fix typo Modified files: xc/programs/Xserver/hw/xfree86/drivers/mga/: mga_arc.c Revision ChangesPath 1.12 +2 -2 xc/programs/Xserver/hw/xfree86/drivers/mga/mga_arc.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/07/15 20:24:36 Log message: build fix Modified files: xc/programs/Xserver/hw/vfb/: Imakefile Revision ChangesPath 3.31 +4 -3 xc/programs/Xserver/hw/vfb/Imakefile ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/07/15 20:35:16 Log message: The Noop functions need to be static. Modified files: xc/programs/Xserver/mfb/: mfb.h mfbgc.c Revision ChangesPath 1.21 +1 -35 xc/programs/Xserver/mfb/mfb.h 1.10 +7 -4 xc/programs/Xserver/mfb/mfbgc.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
[RFC] Re: Freetype on cygwin link...
An alternative would be to update the freetype support in XFree86 mainline, to the current version. This would benefit would yield much higher benefit, I think What caveats would that bring about? What about the development costs? Daniel schrieb: Any takers? This sounds like a bit of delicate work! No, it isn't. The patch includes changes to the files used by autoconf and libtool. Source changes are minimal, here they are. Apply these and change to the dirctory with configure.in and ltmain.sh and run: autoreconf --verbose --install --force which should end up with s.th. like the full patch includes (new aclocal.m4 file, new configure, new ltmain.sh) and then libtool-1.5 builds automatically the DLL (because of the -no-undefined flag, see below). FreeType is just a little more complex than packages that are using automake. diff -urdb freetype-2.1.4~/builds/unix/unix-cc.in freetype-2.1.4/builds/unix/unix-cc.in --- freetype-2.1.4~/builds/unix/unix-cc.in 2002-12-23 23:40:21.0 +0100 +++ freetype-2.1.4/builds/unix/unix-cc.in 2003-06-06 11:57:52.0 +0200 @@ -78,7 +78,7 @@ # Library linking # LINK_LIBRARY = $(LIBTOOL) --mode=link $(CCraw) -o $@ $(OBJECTS_LIST) \ - -rpath $(libdir) -version-info $(version_info) \ + -rpath $(libdir) -no-undefined -version-info $(version_info) \ $(LDFLAGS) # EOF diff -urdb freetype-2.1.4~/include/freetype/config/ftoption.h freetype-2.1.4/include/freetype/config/ftoption.h --- freetype-2.1.4~/include/freetype/config/ftoption.h 2003-01-31 00:24:18.0 +0100 +++ freetype-2.1.4/include/freetype/config/ftoption.h 2003-06-06 12:40:45.0 +0200 @@ -378,7 +378,7 @@ /* do not #undef this macro here, since the build system might */ /* define for certain configurations */ /* */ -/* #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER */ +#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER /*/ diff -urdb freetype-2.1.4~/src/base/ftbase.c freetype-2.1.4/src/base/ftbase.c --- freetype-2.1.4~/src/base/ftbase.c 2002-03-30 14:16:33.0 +0100 +++ freetype-2.1.4/src/base/ftbase.c2003-06-06 12:41:31.0 +0200 @@ -29,6 +29,7 @@ #include ftgloadr.c #include ftobjs.c #include ftnames.c +#include ftapi.c /* END */ -- =^..^= -- Daniel J Blueman +++ GMX - Mail, Messaging more http://www.gmx.net +++ Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern! ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: Savage Driver Replacement?
Alan Messer writes: Tim Roberts wrote: I've recently been made aware of the XFree86 Savage driver that VIA released and is now available on Alan Hourihane's web site. This driver is so much superior to the one I've been maintaining that I should be embarrassed. My question is: has anyone actually taken an action item to incorporate this into the 4.3.99 tree? I'd like to reiterate Tim's question. Have Via recently released drivers been integrated into 4.3.99? I had the feeling that the drivers in 4.3.99 were based on Via's previous release? Yes, there is a VIA driver in CVS. Egbert. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Patch ping
On Tuesday 15 July 2003 1:32 pm, Marc Aurele La France wrote: [...] I feel that the fact SharedLibObjCompile() is unused in our _current_ tree is insufficient reason to remove it. It provides nothing over and above NormalSharedLibObjCompile which is used. Maybe I'm wrong... Nick ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: linux 2.6 atkbd == xkb
Hello, As per xc/programs/Xserver/hw/xfree86/common/atKeynames.h: /* * Fake 'scancodes' in the following ranges are generated for 2-byte * codes not handled elsewhere. These correspond to most extended keys * on so-called Internet keyboards: * * 0x79-0x93 * 0x96-0xa1 * 0xa3-0xac * 0xb1-0xb4 * 0xba-0xbd * 0xc2 * 0xcc-0xd2 * 0xd6-0xf7 */ What I cannot find is *where* those fake scancodes are generated and how they are mapped to 0x81-0x84 xc/programs/Xserver/hw/xfree86/common/xf86Events.c xf86PostKbdEvent() subroutine P.S. I currently use: Option XkbModel pc105 but AFAICT the only way to turn on a named section in xkb/symbols/inet is to use Option XkbModel named_option How do I get both us(pc105) and inet(inspiron)? Simply use the second way. If the model name is the same as one of inet file sections name, XKB uses us(pc105) map and _adds_ inet(model_name) to it. (I mean XFree86 4.3.0. In previous versions it uses us(pc104). ) -- Ivan U. Pascal | e-mail: [EMAIL PROTECTED] Administrator of | Tomsk State University University Network | Tomsk, Russia ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: Savage Driver Replacement?
VIA/S3 released fully featured driver that it developed in house. they were based on 4.2.0. VIA had previously released a 2D only driver for the CLE266, which was integrated into xfree86 CVS. The released drivers are available on Alan Cox's website: http://www.linux.org.uk/~alan/S3.zip http://www.linux.org.uk/~alan/CLE266.zip The 2D drivers should be fairly easy to integrate into xfree, the 3D driver will take more work since they are based on mesa 3.x rather than 4.x. Alex --- Alan Messer [EMAIL PROTECTED] wrote: Tim Roberts wrote: I've recently been made aware of the XFree86 Savage driver that VIA released and is now available on Alan Hourihane's web site. This driver is so much superior to the one I've been maintaining that I should be embarrassed. My question is: has anyone actually taken an action item to incorporate this into the 4.3.99 tree? I'd like to reiterate Tim's question. Have Via recently released drivers been integrated into 4.3.99? I had the feeling that the drivers in 4.3.99 were based on Via's previous release? I looked in Alan Cox's and Alan H's sites for Via drivers and only found the binary compile of CVS latest drivers on Alan H's xfree86 page. Alan. __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Radeon 9000 If (RV250), Mac G4 (Wintunnel) problems withXFree86
On Wed, 2003-06-04 at 14:11, Simon Urbanek wrote: On Wednesday, June 4, 2003, at 01:19 AM, Michel Dänzer wrote: On Tue, 2003-06-03 at 15:22, Benjamin Herrenschmidt wrote: On Fri, 2003-05-30 at 11:52, Simon Urbanek wrote: Summary: 1) CRT + TMDS dual head configuration doesn't work 2) In all configurations colors are completely wrong 3) closing X blanks all monitors I have tested following versions of XFree86: Debian sid officail 4.2.1 Michel Daenzer's 4.2.1 DRI build Debian inoffical 4.3.0 latest CVS build (by myself) as of yesterday (4.3.99...) Ok, CVS is the really interesting one. Michel, did you ever commit the fix of SURFACE_CNTL ? That should fix the colors at least on the main aperture It's in, but only handles aperture 0. Can someone try http://penguinppc.org/~daenzer/XFree86/radeon-ap1.diff or http://penguinppc.org/~daenzer/XFree86/radeon_drv.o ? I tried the patch, but without any visible results :(. I was digging a bit more in the wrong colors issue and found out the following: When I'm running the CRT,CRT layout (as opposed to the previous CRT,TMDS) the colors behave differently. In fact is seems like a common endianess-problem: the layout of colors is 0xBBGGRR00 in Mac big-endian notation, but the color on the screen written by the driver are 0x00RRGGBB - that is the colors red and green are swapped and blue is never seen. This is true for both screens. So the summary (CVS XFree): * CRT,CRT mode: swapped 'byte-sex' causes wrong colors, otherwise both screens are OK * CRT,TMDS mode: CRT screen is off, TMDS has split colors - i.e. the low and high 4 bits of the components are interlaced I wanted to look at the code, but I can't seem to find any tech info on the Radeon chip - is it available to the chosen only after signing a NDA? Any help, especially with the CRT+TMDS mode is highly appreciated! Cheers, Simon PS: Additional info for Ben: In fact the kernel radeon driver works with the DFP *only* - in CRT,CRT layout the kernel hangs in the early-boot screen (and doesn't go further - no network etc.). ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Radeon 9000 If (RV250), Mac G4 (Wintunnel) problems withXFree86
latest CVS build (by myself) as of yesterday (4.3.99...) When did you try exactly ? I've seen more fixes for TMDS getting in the CVS recently. I'm not sure what's up here, definitely not something the doc explains. I suspect it's the path of pixel data from the framebuffer to the TMDS transmitter that has an endian problem, I fail to see why SURFACE_CNTL thing would fail, or maybe it's a problem related to surface translation getting in our way ? Ben. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Radeon 9000 If (RV250), Mac G4 (Wintunnel) problems withXFree86
On Tue, 2003-07-15 at 16:17, Michel Dänzer wrote: [ citation without new stuff ] Sorry about that, fun time with Evolution. :\ -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Patch ping
On Tuesday 15 July 2003 4:00 pm, Marc Aurele La France wrote: [...] The imake rule in question will not be removed because there is nothing to preclude its use by external packages such as those found in X.Org's contrib/. Ok. Thanks for explaining. Am I on a road to nowhere in attempting to change the build infrastructure to accomplish my goal? Please see http://mail-index.netbsd.org/tech-x11/2003/06/02/0001.html Thanks again, Nick ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Patch ping
On Tue, 15 Jul 2003, Nick Hudson wrote: The imake rule in question will not be removed because there is nothing to preclude its use by external packages such as those found in X.Org's contrib/. Ok. Thanks for explaining. Am I on a road to nowhere in attempting to change the build infrastructure to accomplish my goal? Please see http://mail-index.netbsd.org/tech-x11/2003/06/02/0001.html No, that's a valid goal. But you need to be careful not to break things. On Linux at least, there are PIC/non-PIC issues. Some ports require PIC, others non-PIC, still others don't care. I forget the details, recalling instead only that it's not obvious from just perusing the code. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: CL266 TV-out bug?
On Mon, 14 Jul 2003 20:58:21 -0700 (PDT), Alan Messer wrote: I've been using the 4.3.99 CLE266 (ProSavage) driver on my Via EPIA M1 board. The CLE266 is a Castlerock, not a ProSavage. To the best of my knowledge, the two chips are unrelated. -- - Tim Roberts, [EMAIL PROTECTED] Providenza Boekelheide, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [forum] Re: Choosing an extension for bitmap-only SFNTs
As far as I know, Microsoft doesn't use bitmap-only sfnts -- they use scalable fonts throughout, nowadays, only keeping the legacy .FON format for backwards compatibility. TR Windows XP still has Terminal, Courier, MS Serif and MS Sans TR Serif, all of which are bitmapped and in common use. Indeed, MS TR Sans Serif is the default font for dialog boxes unless otherwise TR overridden. They're still .FON files, not bitmap-only SFNTs. Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: X.Org's IPv6 changes (was: CVS Update: xc (branch: trunk))
MLF I think the best thing to do here is to recode DPS to rely on xtrans. Shall we remove libdps from the tree? Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: X.Org's IPv6 changes (was: CVS Update: xc (branch: trunk))
On 15 Jul 2003, Juliusz Chroboczek wrote: MLF I think the best thing to do here is to recode DPS to rely on xtrans. Shall we remove libdps from the tree? Why? Is DPS dead? It's just a matter of time before I find the time to convert it. And that doesn't preclude someone else beating me to it. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [RFC] Re: Freetype on cygwin link...
On Tue, Jul 15, 2003 at 11:49:42AM +0200, Daniel Blueman wrote: An alternative would be to update the freetype support in XFree86 mainline, to the current version. I don't know anything about the context of this discussion, but the XFree86 CVS trunk has FreeType 2.1.4, which appears to be the current release version according to the freetype web site. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes This would benefit would yield much higher benefit, I think What caveats would that bring about? What about the development costs? Daniel schrieb: Any takers? This sounds like a bit of delicate work! No, it isn't. The patch includes changes to the files used by autoconf and libtool. Source changes are minimal, here they are. Apply these and change to the dirctory with configure.in and ltmain.sh and run: autoreconf --verbose --install --force which should end up with s.th. like the full patch includes (new aclocal.m4 file, new configure, new ltmain.sh) and then libtool-1.5 builds automatically the DLL (because of the -no-undefined flag, see below). FreeType is just a little more complex than packages that are using automake. diff -urdb freetype-2.1.4~/builds/unix/unix-cc.in freetype-2.1.4/builds/unix/unix-cc.in --- freetype-2.1.4~/builds/unix/unix-cc.in 2002-12-23 23:40:21.0 +0100 +++ freetype-2.1.4/builds/unix/unix-cc.in 2003-06-06 11:57:52.0 +0200 @@ -78,7 +78,7 @@ # Library linking # LINK_LIBRARY = $(LIBTOOL) --mode=link $(CCraw) -o $@ $(OBJECTS_LIST) \ - -rpath $(libdir) -version-info $(version_info) \ + -rpath $(libdir) -no-undefined -version-info $(version_info) \ $(LDFLAGS) # EOF diff -urdb freetype-2.1.4~/include/freetype/config/ftoption.h freetype-2.1.4/include/freetype/config/ftoption.h --- freetype-2.1.4~/include/freetype/config/ftoption.h 2003-01-31 00:24:18.0 +0100 +++ freetype-2.1.4/include/freetype/config/ftoption.h 2003-06-06 12:40:45.0 +0200 @@ -378,7 +378,7 @@ /* do not #undef this macro here, since the build system might */ /* define for certain configurations */ /* */ -/* #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER */ +#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER /*/ diff -urdb freetype-2.1.4~/src/base/ftbase.c freetype-2.1.4/src/base/ftbase.c --- freetype-2.1.4~/src/base/ftbase.c 2002-03-30 14:16:33.0 +0100 +++ freetype-2.1.4/src/base/ftbase.c2003-06-06 12:41:31.0 +0200 @@ -29,6 +29,7 @@ #include ftgloadr.c #include ftobjs.c #include ftnames.c +#include ftapi.c /* END */ -- =^..^= -- Daniel J Blueman +++ GMX - Mail, Messaging more http://www.gmx.net +++ Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern! ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
User sponsored drivers
This proposal comes up periodically on this and other xfree lists, but never really goes anywhere. Why not raise money from the open source community to fund open source driver development? everything from revamping X (ie, speeding up the development of 5.0 features) to adding a new Xfree86 3D driver. Not only would this add features we want, it would also show HW companies that people don't just care about having drivers, they want OPEN SOURCE. They care enough to donate money over and above the cost of the hardware to to get open source drivers. I'd be willing to take the initiative to get something like this started. Just as an example, Blender raised over $100,000 in just 7 weeks to buy the rights to the source code. For example we could start with r300 support and move on to other projects as money and interest permit. New projects could be put to a vote. What would be a reasonable cost estimate for something like that? $50,000? smaller projects may cost less... Thoughts? Some features of interest: - r300 3D support - crtc2 support for i830/45, trident, smi, savage - 3d support for other chipsets - translucent windows - dynamic reconfiguring - tv out on more chipsets - HW accelerated indirect rendering - new opengl extensions __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Dri-devel] User sponsored drivers
This sounds like a great idea indeed. There are many questions, I'm sure. One that comes to mind is: *Who* would be able to vote? Luis On Tue, 15 Jul 2003, Alex Deucher wrote: This proposal comes up periodically on this and other xfree lists, but never really goes anywhere. Why not raise money from the open source community to fund open source driver development? everything from revamping X (ie, speeding up the development of 5.0 features) to adding a new Xfree86 3D driver. Not only would this add features we want, it would also show HW companies that people don't just care about having drivers, they want OPEN SOURCE. They care enough to donate money over and above the cost of the hardware to to get open source drivers. I'd be willing to take the initiative to get something like this started. Just as an example, Blender raised over $100,000 in just 7 weeks to buy the rights to the source code. For example we could start with r300 support and move on to other projects as money and interest permit. New projects could be put to a vote. What would be a reasonable cost estimate for something like that? $50,000? smaller projects may cost less... Thoughts? Some features of interest: - r300 3D support - crtc2 support for i830/45, trident, smi, savage - 3d support for other chipsets - translucent windows - dynamic reconfiguring - tv out on more chipsets - HW accelerated indirect rendering - new opengl extensions __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: User sponsored drivers
On Tue, 15 Jul 2003, Alex Deucher wrote: This proposal comes up periodically on this and other xfree lists, but never really goes anywhere. Why not raise money from the open source community to fund open source driver development? It is very difficult to convert money into code. It's probably easier to raise the money than it is to find a way to convert that into code. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Pfaedit-devel] Re: [forum] Re: Choosing an extension for bitmap-only SFNTs
That was the initial plan, but I found out that having FreeType grok such fonts required more changes than David Turner was wililng to make in the 2.1.* series. So I'm generating a zero-length glyf and a one-entry loca. (No EBSC indeed.) Ok, I'm currently posting a new build of PfaEdit which will generate embedded bitmap opentype fonts with extension .otb which contain dummy 'glyf' and 'loca' tables (and no 'EBSC'). Let me know if there are any problems with this or if the format changes over time. I feel that having the same extension for bitmap and scalable fonts is confusing -- without a naming extension, you need tools such as ftdump to find out what your fonts are. In the same vein, perhaps it would be appropriate to give such fonts a different version string in the offset table at the beginning of the font (PfaEdit is currently generating 'OTTO', which is appropriate for opentype fonts). Should this change too? 'OTBO'? or will that need too large a change to freetype? ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[Fonts] [RFC] Re: Freetype on cygwin link...
An alternative would be to update the freetype support in XFree86 mainline, to the current version. This would benefit would yield much higher benefit, I think What caveats would that bring about? What about the development costs? Daniel schrieb: Any takers? This sounds like a bit of delicate work! No, it isn't. The patch includes changes to the files used by autoconf and libtool. Source changes are minimal, here they are. Apply these and change to the dirctory with configure.in and ltmain.sh and run: autoreconf --verbose --install --force which should end up with s.th. like the full patch includes (new aclocal.m4 file, new configure, new ltmain.sh) and then libtool-1.5 builds automatically the DLL (because of the -no-undefined flag, see below). FreeType is just a little more complex than packages that are using automake. diff -urdb freetype-2.1.4~/builds/unix/unix-cc.in freetype-2.1.4/builds/unix/unix-cc.in --- freetype-2.1.4~/builds/unix/unix-cc.in 2002-12-23 23:40:21.0 +0100 +++ freetype-2.1.4/builds/unix/unix-cc.in 2003-06-06 11:57:52.0 +0200 @@ -78,7 +78,7 @@ # Library linking # LINK_LIBRARY = $(LIBTOOL) --mode=link $(CCraw) -o $@ $(OBJECTS_LIST) \ - -rpath $(libdir) -version-info $(version_info) \ + -rpath $(libdir) -no-undefined -version-info $(version_info) \ $(LDFLAGS) # EOF diff -urdb freetype-2.1.4~/include/freetype/config/ftoption.h freetype-2.1.4/include/freetype/config/ftoption.h --- freetype-2.1.4~/include/freetype/config/ftoption.h 2003-01-31 00:24:18.0 +0100 +++ freetype-2.1.4/include/freetype/config/ftoption.h 2003-06-06 12:40:45.0 +0200 @@ -378,7 +378,7 @@ /* do not #undef this macro here, since the build system might */ /* define for certain configurations */ /* */ -/* #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER */ +#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER /*/ diff -urdb freetype-2.1.4~/src/base/ftbase.c freetype-2.1.4/src/base/ftbase.c --- freetype-2.1.4~/src/base/ftbase.c 2002-03-30 14:16:33.0 +0100 +++ freetype-2.1.4/src/base/ftbase.c2003-06-06 12:41:31.0 +0200 @@ -29,6 +29,7 @@ #include ftgloadr.c #include ftobjs.c #include ftnames.c +#include ftapi.c /* END */ -- =^..^= -- Daniel J Blueman +++ GMX - Mail, Messaging more http://www.gmx.net +++ Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern! ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[I18n] fix for a few Xlib charset converters
Hi,
Please apply this patch. It fixes two bugs in the ISO-8859-16 and
ARMSCII character set converters. In particular, the draft of
ISO-8859-16 on which the original code is based contained a bug.
Bruno
*** xc/lib/X11/lcUniConv/README 2000/02/12 02:54:20 1.1
--- xc/lib/X11/lcUniConv/README 2003/07/15 09:11:28
***
*** 6,10
If you find a bug in these files, instead of modifying them in XFree86
and let it diverge from libiconv, please notify the libiconv maintainer
! (currently [EMAIL PROTECTED]) so he can fix both in synch.
--- 6,10
If you find a bug in these files, instead of modifying them in XFree86
and let it diverge from libiconv, please notify the libiconv maintainer
! (currently [EMAIL PROTECTED]) so he can fix both in synch.
*** xc/lib/X11/lcUniConv/armscii_8.h2000/11/29 17:40:28 1.3
--- xc/lib/X11/lcUniConv/armscii_8.h2003/07/15 09:11:28
***
*** 6,13
static const unsigned short armscii_8_2uni[96] = {
/* 0xa0 */
! 0x00a0, 0x2741, 0x00a7, 0x0589, 0x0029, 0x0028, 0x00bb, 0x00ab,
! 0x2014, 0x002e, 0x055d, 0x002c, 0x002d, 0x055f, 0x2026, 0x055c,
/* 0xb0 */
0x055b, 0x055e, 0x0531, 0x0561, 0x0532, 0x0562, 0x0533, 0x0563,
0x0534, 0x0564, 0x0535, 0x0565, 0x0536, 0x0566, 0x0537, 0x0567,
--- 6,13
static const unsigned short armscii_8_2uni[96] = {
/* 0xa0 */
! 0x00a0, 0xfffd, 0x0587, 0x0589, 0x0029, 0x0028, 0x00bb, 0x00ab,
! 0x2014, 0x002e, 0x055d, 0x002c, 0x002d, 0x058a, 0x2026, 0x055c,
/* 0xb0 */
0x055b, 0x055e, 0x0531, 0x0561, 0x0532, 0x0562, 0x0533, 0x0563,
0x0534, 0x0564, 0x0535, 0x0565, 0x0536, 0x0566, 0x0537, 0x0567,
***
*** 22,47
0x054c, 0x057c, 0x054d, 0x057d, 0x054e, 0x057e, 0x054f, 0x057f,
/* 0xf0 */
0x0550, 0x0580, 0x0551, 0x0581, 0x0552, 0x0582, 0x0553, 0x0583,
! 0x0554, 0x0584, 0x0555, 0x0585, 0x0556, 0x0586, 0x2019, 0x0027,
};
static int
armscii_8_mbtowc (conv_t conv, ucs4_t *pwc, const unsigned char *s, int n)
{
unsigned char c = *s;
! if (c 0xa0)
*pwc = (ucs4_t) c;
! else
! *pwc = (ucs4_t) armscii_8_2uni[c-0xa0];
! return 1;
}
! static const unsigned char armscii_8_page00[16] = {
! 0x20, 0x21, 0x22, 0x23, 0x24, 0x25, 0x26, 0xff, /* 0x20-0x27 */
0xa5, 0xa4, 0x2a, 0x2b, 0xab, 0xac, 0xa9, 0x2f, /* 0x28-0x2f */
};
static const unsigned char armscii_8_page00_1[32] = {
! 0xa0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xa2, /* 0xa0-0xa7 */
0x00, 0x00, 0x00, 0xa7, 0x00, 0x00, 0x00, 0x00, /* 0xa8-0xaf */
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0xb0-0xb7 */
0x00, 0x00, 0x00, 0xa6, 0x00, 0x00, 0x00, 0x00, /* 0xb8-0xbf */
--- 22,53
0x054c, 0x057c, 0x054d, 0x057d, 0x054e, 0x057e, 0x054f, 0x057f,
/* 0xf0 */
0x0550, 0x0580, 0x0551, 0x0581, 0x0552, 0x0582, 0x0553, 0x0583,
! 0x0554, 0x0584, 0x0555, 0x0585, 0x0556, 0x0586, 0x055a, 0xfffd,
};
static int
armscii_8_mbtowc (conv_t conv, ucs4_t *pwc, const unsigned char *s, int n)
{
unsigned char c = *s;
! if (c 0xa0) {
*pwc = (ucs4_t) c;
! return 1;
! }
! else {
! unsigned short wc = armscii_8_2uni[c-0xa0];
! if (wc != 0xfffd) {
! *pwc = (ucs4_t) wc;
! return 1;
! }
! }
! return RET_ILSEQ;
}
! static const unsigned char armscii_8_page00[8] = {
0xa5, 0xa4, 0x2a, 0x2b, 0xab, 0xac, 0xa9, 0x2f, /* 0x28-0x2f */
};
static const unsigned char armscii_8_page00_1[32] = {
! 0xa0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0xa0-0xa7 */
0x00, 0x00, 0x00, 0xa7, 0x00, 0x00, 0x00, 0x00, /* 0xa8-0xaf */
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0xb0-0xb7 */
0x00, 0x00, 0x00, 0xa6, 0x00, 0x00, 0x00, 0x00, /* 0xb8-0xbf */
***
*** 52,68
0xd0, 0xd2, 0xd4, 0xd6, 0xd8, 0xda, 0xdc, 0xde, /* 0x40-0x47 */
0xe0, 0xe2, 0xe4, 0xe6, 0xe8, 0xea, 0xec, 0xee, /* 0x48-0x4f */
0xf0, 0xf2, 0xf4, 0xf6, 0xf8, 0xfa, 0xfc, 0x00, /* 0x50-0x57 */
! 0x00, 0x00, 0x00, 0xb0, 0xaf, 0xaa, 0xb1, 0xad, /* 0x58-0x5f */
0x00, 0xb3, 0xb5, 0xb7, 0xb9, 0xbb, 0xbd, 0xbf, /* 0x60-0x67 */
0xc1, 0xc3, 0xc5, 0xc7, 0xc9, 0xcb, 0xcd, 0xcf, /* 0x68-0x6f */
0xd1, 0xd3, 0xd5, 0xd7, 0xd9, 0xdb, 0xdd, 0xdf, /* 0x70-0x77 */
0xe1, 0xe3, 0xe5, 0xe7, 0xe9, 0xeb, 0xed, 0xef, /* 0x78-0x7f */
! 0xf1, 0xf3, 0xf5, 0xf7, 0xf9, 0xfb, 0xfd, 0x00, /* 0x80-0x87 */
! 0x00, 0xa3, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0x88-0x8f */
};
static const unsigned char armscii_8_page20[24] = {
0x00, 0x00, 0x00, 0x00, 0xa8, 0x00, 0x00, 0x00, /* 0x10-0x17 */
! 0x00, 0xfe, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0x18-0x1f */
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xae, 0x00, /* 0x20-0x27 */
};
--- 58,74
0xd0, 0xd2, 0xd4, 0xd6, 0xd8, 0xda, 0xdc, 0xde, /* 0x40-0x47 */
0xe0, 0xe2, 0xe4, 0xe6, 0xe8, 0xea, 0xec, 0xee, /* 0x48-0x4f */
0xf0, 0xf2, 0xf4, 0xf6, 0xf8, 0xfa, 0xfc, 0x00, /* 0x50-0x57 */
! 0x00, 0x00, 0xfe, 0xb0, 0xaf, 0xaa,
Re: [I18n] fix for a few Xlib charset converters
Hi, Please apply this patch. It fixes two bugs in the ISO-8859-16 and ARMSCII character set converters. In particular, the draft of ISO-8859-16 on which the original code is based contained a bug. Commited. Thanks. -- Ivan U. Pascal | e-mail: [EMAIL PROTECTED] Administrator of | Tomsk State University University Network | Tomsk, Russia ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
[XFree86] NVidia Drivers
Hi all, I have recently had to look into my X server log and found a few disturbing log messages. It seems like my video card is trying something it cannot do for a while before giving up. This does explain the small delay (and blinking) I thought was normal when switsching form console to X. Might you have any ideas what I have to change to remedy the situation? Here some data: Log file - http://pure-logic.org/X.log XF86Config - http://pure-logic.org/XF86Config Video card - Nvidia GeForce2 MX 200 with 64MB RAM Monitor - http://www.monitorworld.com/Monitors/maxdata/belinea105586.html Slackware 9 with self-compiled 2.4.21 with ck3 patch. Many thanks in advance!! Best regards, Nickolay Kolev ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Matrox G450 on solaris
Hi, I am using XFree 4.3 on solaris 9 (intel) with Matrox G450 card. When I run xdm I have got only black screen. Thank you for help Mira # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the Software), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section Module # This loads the DBE extension module. Loaddbe # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection extmod Optionomit xfree86-dga # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Loadtype1 Loadfreetype # This loads the GLX module #Load glx EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ # The module search path. The default path is shown here. #ModulePath /usr/X11R6/lib/modules EndSection # ** # Server flags section. # ** Section ServerFlags # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #Option NoTrapSignals # Uncomment this to disable the CrtlAltBS server abort sequence # This allows clients to receive this key event. #Option DontZap # Uncomment this to disable the CrtlAltKP_+/KP_- mode switching # sequences. This allows clients to receive these key events. #Option Dont Zoom # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. #Option DisableVidModeExtension # Uncomment this to enable the use of a non-local xvidtune client. #Option AllowNonLocalXvidtune # Uncomment this to disable dynamically
[XFree86] problem with xfree
hi i'm trying to start x-terminal via etherboot and ltsp (x-klient 486 dx 66 with tseng et 4000 w32p , x-server something better :) but i have some problem with xfree. (ww) tseng: no matching device section for instance (BusID PCI:65:21:0) found ... fatal server error : failed to initialize core devices. I use xfree 4.1.0 (ltsp x core 3.0.4) and have tseng et 4000 w32p video card.
[XFree86] tseng: no matching device section
hi i'm trying to start x-terminal via etherboot and ltsp (x-klient 486 dx 66 with tseng et 4000 w32p , x-server something better :) but i have some problem with xfree. (ww) tseng: no matching device section for instance (BusID PCI:65:21:0) found ... fatal server error : failed to initialize core devices. I use xfree 4.1.0 (ltsp x core 3.0.4) and have tseng et 4000 w32p video card.
Re: [XFree86] i830 chipset / i810 driver
On Wed, 09 Jul 2003, David A. Mason wrote: Is it yet possible to use the S-Video out on the i830 chipset in XFree86? It certainly works with the i845GE based Shuttle SB51G using the i830 driver. However, I can find now way to get X to use the whole screen. Using linux the text boot sequence can be tuned to 640x480 (~60% of screen) or 800x600 (~75% of screen) and X when launched uses only that area. If anyone knows of a solution to this I'd be very greatful as it's put a pause on my freevo / dvd player etc dreams. Gavin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] cocdolence mrnia cmsjdmexnxnj a
This is not intended for illegal purposes or to defraud your cable company. Your Cable Company will do anything to Keep you from seeing This. Access any digital cable signal INSTANTLY. http://www.directcost.net/index.php?RepID=PW Due to to high volume of sales traffic this site may be unavailable from time to time so if you are unable to connect please try again later. If you no longer wish to receive our offerings You may opt-out by sending a email to: http://www.onprice.net/cleanlist.php heterogamous qhplslbdkt e iosx tclbedsgz eg
Re: Re: [XFree86] Xpert, Any software just for 15$ - 40$
Maybe instead of directing them to the email address, you should have a message directing them to a FAQ / troubleshooting page? - Christian From: Egbert Eich [EMAIL PROTECTED] Date: 2003/07/15 Tue AM 08:04:30 EDT To: [EMAIL PROTECTED] Subject: Re: [XFree86] Xpert, Any software just for 15$ - 40$ David Dawes writes: On Mon, Jul 14, 2003 at 05:21:43PM +0200, Egbert Eich wrote: Whenever the server terminates with a FatalError() it tells the user to send email to [EMAIL PROTECTED] This creates an enormous amount of traffic here even if it is a user problem has been answered several times already - like our all time favourite cannot find font 'fixed'. My conclusion from this is that the XFree86 server should handle this condition better. I thought that using the 'builtin' font stuff might have been a good way to do that, but unfortunately Juliusz has found that it's going to require more time/work than expected. This will only reduce the number of bug reports not eliminate it. Not all applications have a fallback heuristic all the way down to the 'fixed' font. If only this font is available many applications will refuse to run with an XRequest error on font or an even less conclusive error messages. This will then be posted here and it will be much harder to track down. Besides this, the same FatalError() is called due to other stupid user configuration bugs - like using the wrong driver. So we still have to deal with errors in configuration tools which we didn't provide or user stupidity when editing the config file. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Compliation problem under unixware
Is anyone versed enough in the inner workings of the server and it's libs to take a stab at this problem? I'm building xfree86 v4.3.0 under unixware 7.1.3 using the stock cc. When I get to compling ix86Pci.c in xc/programs/Xserver/hw/xfree86/os-support/bus I get this error message: /usr/ccs/bin/cc -c -O -W0,-2A -Xa -Dasm=__asm -I. -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 -I../../../../../.. -I../../../../../../exports/include -I/usr/X11R6/include -DUSL -DSVR4 -Di386 -D__i386__ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER -DRANDR -D__USLC__ -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DNARROWPROTO ix86Pci.c UX:acomp: ERROR: ix86Pci.c, line 673: undefined symbol: PCI_CHIP_430HX UX:acomp: ERROR: ix86Pci.c, line 673: Syntax error before or at: _BRIDGE UX:acomp: ERROR: ix86Pci.c, line 673: syntax error, probably missing ,, ; or = UX:acomp: ERROR: ix86Pci.c, line 674: Syntax error before or at: ( UX:acomp: WARNING: ix86Pci.c, line 675: syntax error: empty declaration UX:acomp: WARNING: ix86Pci.c, line 682: null dimension: sizeof() UX:acomp: ERROR: ix86Pci.c, line 683: undefined symbol: pPCI UX:acomp: ERROR: ix86Pci.c, line 683: left operand of - must be pointer to struct/union gmake: *** [ix86Pci.o] Error 1 I can't figure-out what the problem is here. PCI_CHIP_430HX_BRIDGE is #define'd in xc/programs/Xserver/hw/xfree86/common which is in the -I path. Neither PCI_CHIP_430HX or PCI_430HX_BRIDGE is #define'd anywhere else on my system. I tried /* commenting-out */ the #define in the include file but even then I got the same error. Frank ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Compliation problem under unixware
Even if the right directory is in the -I path, is the .c file that requires it perhaps failing to #include a header that will actually bring in that #define? - Christian From: Frank Tarczynski [EMAIL PROTECTED] Date: 2003/07/15 Tue AM 09:28:53 EDT To: [EMAIL PROTECTED] Subject: [XFree86] Compliation problem under unixware Is anyone versed enough in the inner workings of the server and it's libs to take a stab at this problem? I'm building xfree86 v4.3.0 under unixware 7.1.3 using the stock cc. When I get to compling ix86Pci.c in xc/programs/Xserver/hw/xfree86/os-support/bus I get this error message: /usr/ccs/bin/cc -c -O -W0,-2A -Xa -Dasm=__asm -I. -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 -I../../../../../.. -I../../../../../../exports/include -I/usr/X11R6/include -DUSL -DSVR4 -Di386 -D__i386__ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER -DRANDR -D__USLC__ -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DNARROWPROTO ix86Pci.c UX:acomp: ERROR: ix86Pci.c, line 673: undefined symbol: PCI_CHIP_430HX UX:acomp: ERROR: ix86Pci.c, line 673: Syntax error before or at: _BRIDGE UX:acomp: ERROR: ix86Pci.c, line 673: syntax error, probably missing ,, ; or = UX:acomp: ERROR: ix86Pci.c, line 674: Syntax error before or at: ( UX:acomp: WARNING: ix86Pci.c, line 675: syntax error: empty declaration UX:acomp: WARNING: ix86Pci.c, line 682: null dimension: sizeof() UX:acomp: ERROR: ix86Pci.c, line 683: undefined symbol: pPCI UX:acomp: ERROR: ix86Pci.c, line 683: left operand of - must be pointer to struct/union gmake: *** [ix86Pci.o] Error 1 I can't figure-out what the problem is here. PCI_CHIP_430HX_BRIDGE is #define'd in xc/programs/Xserver/hw/xfree86/common which is in the -I path. Neither PCI_CHIP_430HX or PCI_430HX_BRIDGE is #define'd anywhere else on my system. I tried /* commenting-out */ the #define in the include file but even then I got the same error. Frank ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Compliation problem under unixware
Interesting. I did copy the header file to the same directory (-I.) but I never checked to see if it was actually #include'd. Something to check tonight. Thanks. Even if the right directory is in the -I path, is the .c file that requires it perhaps failing to #include a header that will actually bring in that #define? - Christian From: Frank Tarczynski [EMAIL PROTECTED] Date: 2003/07/15 Tue AM 09:28:53 EDT To: [EMAIL PROTECTED] Subject: [XFree86] Compliation problem under unixware Is anyone versed enough in the inner workings of the server and it's libs to take a stab at this problem? I'm building xfree86 v4.3.0 under unixware 7.1.3 using the stock cc. When I get to compling ix86Pci.c in xc/programs/Xserver/hw/xfree86/os-support/bus I get this error message: /usr/ccs/bin/cc -c -O -W0,-2A -Xa -Dasm=__asm -I. -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 -I../../../../../.. -I../../../../../../exports/include -I/usr/X11R6/include -DUSL -DSVR4 -Di386 -D__i386__ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER -DRANDR -D__USLC__ -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DNARROWPROTO ix86Pci.c UX:acomp: ERROR: ix86Pci.c, line 673: undefined symbol: PCI_CHIP_430HX UX:acomp: ERROR: ix86Pci.c, line 673: Syntax error before or at: _BRIDGE UX:acomp: ERROR: ix86Pci.c, line 673: syntax error, probably missing ,, ; or = UX:acomp: ERROR: ix86Pci.c, line 674: Syntax error before or at: ( UX:acomp: WARNING: ix86Pci.c, line 675: syntax error: empty declaration UX:acomp: WARNING: ix86Pci.c, line 682: null dimension: sizeof() UX:acomp: ERROR: ix86Pci.c, line 683: undefined symbol: pPCI UX:acomp: ERROR: ix86Pci.c, line 683: left operand of - must be pointer to struct/union gmake: *** [ix86Pci.o] Error 1 I can't figure-out what the problem is here. PCI_CHIP_430HX_BRIDGE is #define'd in xc/programs/Xserver/hw/xfree86/common which is in the -I path. Neither PCI_CHIP_430HX or PCI_430HX_BRIDGE is #define'd anywhere else on my system. I tried /* commenting-out */ the #define in the include file but even then I got the same error. Frank ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] drm: i810_flush_queue error
Dear Hai, I have installed RH 7.1 in intel 810 chipset mother board but I am not able to get X windows. When I try to configure X window through Xconfigurator it detects proper intel 810 driver. After finishing Xconfigurator its suddenly disappeared. I am getting the Error Message like: drm: i810_flush_queue error Kindly give me the direction to solve the problem. I am waiting for your reply Thanking you Regards Mathias __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] LOG File
hi.. I have a Slackware 9 and when trying to initialize KDE the system said it couldn't find the images.. what can I do? -- Use o melhor sistema de busca da Internet Radar UOL - http://www.radaruol.com.br XFree86.0.log Description: Binary data
Re: Re: [XFree86] Compliation problem under unixware
No problem. I'll actually be surprised if this fixes your problem, because this kind of bug would typically kill everyone regardless of platform. Still, it's maybe worth checking... From: Frank Tarczynski [EMAIL PROTECTED] Date: 2003/07/15 Tue AM 09:54:33 EDT To: [EMAIL PROTECTED] Subject: Re: [XFree86] Compliation problem under unixware Interesting. I did copy the header file to the same directory (-I.) but I never checked to see if it was actually #include'd. Something to check tonight. Thanks. Even if the right directory is in the -I path, is the .c file that requires it perhaps failing to #include a header that will actually bring in that #define? - Christian From: Frank Tarczynski [EMAIL PROTECTED] Date: 2003/07/15 Tue AM 09:28:53 EDT To: [EMAIL PROTECTED] Subject: [XFree86] Compliation problem under unixware Is anyone versed enough in the inner workings of the server and it's libs to take a stab at this problem? I'm building xfree86 v4.3.0 under unixware 7.1.3 using the stock cc. When I get to compling ix86Pci.c in xc/programs/Xserver/hw/xfree86/os-support/bus I get this error message: /usr/ccs/bin/cc -c -O -W0,-2A -Xa -Dasm=__asm -I. -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 -I../../../../../.. -I../../../../../../exports/include -I/usr/X11R6/include -DUSL -DSVR4 -Di386 -D__i386__ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER -DRANDR -D__USLC__ -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DNARROWPROTO ix86Pci.c UX:acomp: ERROR: ix86Pci.c, line 673: undefined symbol: PCI_CHIP_430HX UX:acomp: ERROR: ix86Pci.c, line 673: Syntax error before or at: _BRIDGE UX:acomp: ERROR: ix86Pci.c, line 673: syntax error, probably missing ,, ; or = UX:acomp: ERROR: ix86Pci.c, line 674: Syntax error before or at: ( UX:acomp: WARNING: ix86Pci.c, line 675: syntax error: empty declaration UX:acomp: WARNING: ix86Pci.c, line 682: null dimension: sizeof() UX:acomp: ERROR: ix86Pci.c, line 683: undefined symbol: pPCI UX:acomp: ERROR: ix86Pci.c, line 683: left operand of - must be pointer to struct/union gmake: *** [ix86Pci.o] Error 1 I can't figure-out what the problem is here. PCI_CHIP_430HX_BRIDGE is #define'd in xc/programs/Xserver/hw/xfree86/common which is in the -I path. Neither PCI_CHIP_430HX or PCI_430HX_BRIDGE is #define'd anywhere else on my system. I tried /* commenting-out */ the #define in the include file but even then I got the same error. Frank ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] drm: i810_flush_queue error
On Tue, 15 Jul 2003 07:13:28 -0700 (PDT) mathias Pragasam [EMAIL PROTECTED] uttered: Kindly give me the direction to solve the problem. I am waiting for your reply Can you please post the contents of /etc/X11/XF86Config-4? I am quite sure 4.3.0 supports the i810, but with RH 7.1, who knows? What version of XFree comes with RH 7.1, anyway? Upgrade! (cough) to Mandrake (cough)... I run Mandrake 9.1, and have an i810 mobo myself (weeps), and have never had a prob (more due to XFree version than distro of course!), tho I don't use the onboard video controller since my wife bought me that lovely GF 4 Ti... :)) -- Joehill Registered Linux user #282046 Homepage: http://nodex.sytes.net Guest (shouting): I asked: how many computers you have running in here?! Me (shouting): Sorry! I can't hear you over the sound of all the computers! 10:27:14 up 20 days, 16:08, 3 users, load average: 4.00, 4.05, 4.11 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xpert, Any software just for 15$ - 40$
On Tue, Jul 15, 2003 at 02:04:30PM +0200, Egbert Eich wrote: David Dawes writes: On Mon, Jul 14, 2003 at 05:21:43PM +0200, Egbert Eich wrote: Whenever the server terminates with a FatalError() it tells the user to send email to [EMAIL PROTECTED] This creates an enormous amount of traffic here even if it is a user problem has been answered several times already - like our all time favourite cannot find font 'fixed'. My conclusion from this is that the XFree86 server should handle this condition better. I thought that using the 'builtin' font stuff might have been a good way to do that, but unfortunately Juliusz has found that it's going to require more time/work than expected. This will only reduce the number of bug reports not eliminate it. Not all applications have a fallback heuristic all the way down to the 'fixed' font. If only this font is available many applications will refuse to run with an XRequest error on font or an even less conclusive error messages. This will then be posted here and it will be much harder to track down. Has anyone investigated the root cause of why there is no fixed font in the first place -- like why the font server isn't running? Was it never started (a vendor-specific configuration problem), or did it crash (a robustness problem with xfs)? David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Compliation problem under unixware
On Tue, 15 Jul 2003, Frank Tarczynski wrote: Is anyone versed enough in the inner workings of the server and it's libs to take a stab at this problem? I'm building xfree86 v4.3.0 under unixware 7.1.3 using the stock cc. When I get to compling ix86Pci.c in xc/programs/Xserver/hw/xfree86/os-support/bus I get this error message: /usr/ccs/bin/cc -c -O -W0,-2A -Xa -Dasm=__asm -I. -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 -I../../../../../.. -I../../../../../../exports/include -I/usr/X11R6/include -DUSL -DSVR4 -Di386 -D__i386__ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER -DRANDR -D__USLC__ -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DNARROWPROTO ix86Pci.c UX:acomp: ERROR: ix86Pci.c, line 673: undefined symbol: PCI_CHIP_430HX UX:acomp: ERROR: ix86Pci.c, line 673: Syntax error before or at: _BRIDGE UX:acomp: ERROR: ix86Pci.c, line 673: syntax error, probably missing ,, ; or = UX:acomp: ERROR: ix86Pci.c, line 674: Syntax error before or at: ( UX:acomp: WARNING: ix86Pci.c, line 675: syntax error: empty declaration UX:acomp: WARNING: ix86Pci.c, line 682: null dimension: sizeof() UX:acomp: ERROR: ix86Pci.c, line 683: undefined symbol: pPCI UX:acomp: ERROR: ix86Pci.c, line 683: left operand of - must be pointer to struct/union gmake: *** [ix86Pci.o] Error 1 I can't figure-out what the problem is here. PCI_CHIP_430HX_BRIDGE is #define'd in xc/programs/Xserver/hw/xfree86/common which is in the -I path. Neither PCI_CHIP_430HX or PCI_430HX_BRIDGE is #define'd anywhere else on my system. I tried /* commenting-out */ the #define in the include file but even then I got the same error. In os-support/bus/Pci.h, try changing DEVID's #define to #define DEVID(vendor, device) \ ((CARD32)((PCI_CHIP_/**/device 16) | PCI_VENDOR_/**/vendor)) Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XWINDOWS Crached
Hi Mark, Sorry to bother you, but I am still in the mess ! :-( I made the change you gave me and now I've got another error message ! 2) Should I reinstall Xfree ? I am afreaid that by default, on redhat v80, the installation is made with a UNIX font (:7100) Thanks for your help ! Regards, Stephane Magnier * * Hitex (UK) Ltd. * Warwick University Science Park * Sir William Lyons Road * COVENTRY * CV4 7EZ * UK * Tel: +44 2476 692066 * Fax: +44 2476 692131 * email: [EMAIL PROTECTED] * Website: Http://www.hitex.co.uk Debugging is at least twice as hard as programming. If your code is as clever as you can possibly make it, then by definition you're not smart enough to debug it :-) -- Brian Kernighan * XF86Config Description: Binary data XFree86.0.log Description: Binary data
[XFree86] XFree 4.3 + FreeBSD + Alpha + ATI Mach64 + Help
Hi, I have a DEC personal workstation 500au with a PCI ATI Mach64 vid card. I have FreeBSD 4.8 installed with Xfree 4.3.0. Starting X with the following config file just freezes, and top shows Xfree86 using ~100% of my CPU. Here's the conifg and the log file(it appears to freeze while probing the video card..but i'm stumped). Thanks in advance, Stephen ***Start Conf file*** # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the Software), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section Module # This loads the DBE extension module. Loaddbe # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection extmod Optionomit xfree86-dga # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Loadtype1 Loadspeedo #Loadfreetype #Loadxtt # This loads the GLX module #Load glx # This loads the DRI module #Load dri EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ #FontPath /usr/X11R6/lib/X11/fonts/TrueType/ #FontPath /usr/X11R6/lib/X11/fonts/freefont/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ # The module search path. The default path is shown here. #ModulePath /usr/X11R6/lib/modules EndSection # ** # Server flags section. # ** Section ServerFlags # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #Option NoTrapSignals # Uncomment this to disable the CrtlAltFn VT switch sequence # (where n is 1 through 12). This allows clients to receive these key # events. #Option DontVTSwitch # Uncomment this to disable the CrtlAltBS server abort sequence # This allows clients to receive this key event. #Option DontZap
Re: [XFree86] help with chips 65548 XF86Config
Andy Goth writes: On Monday, July 14, 2003 10:07 pm, j y wrote: Thanks, Andy. I got it working now. I found that using chips driver gave me a double-image problem, but using vesa solved it. The chips driver is supposed to support hardware acceleration on the ct65548 using the Basic Architecture, so if you can get it to work, the display should be faster. From 4.3.0's README.chips, This driver must be considered work in progress, and those users wanting stability are encouraged to use the older XFree86 3.3.x versions. You might consider trying 3.3.x. I've had to do this myself for really old cards salvaged from the junkheap in the attic at work. The biggest advantage of using 3.3.x or earlier is that it lets you know just how good 4.3.0 is. Sort of like the time I accidentally switched on half-speed mode in ZSNES, played for an hour, and then realized that it wasn't just the game. :^) Thanks Andy, this is a pretty lame suggestion. A lot of work has been invested since these lines were included in the README to make this driver more stable. Unfortunately the README gets updated less frequently than the driver therefore this was overlooked. Your comments belittle those who have worked hard to make this driver more stable. Or you can use 4.3.0 and selectively enable/disable features in an attempt to isolate the problem(s) to aid in bug squashing. This can be a lot of work, though. If you're not serious about development, don't bother. If your display is already fast enough to suit you, leave things as they are. You can only stand to break it... In the past I got 3.3.x chips working with a ct65554, but that's a different engine, so my experience might not be helpful. Besides, all I remember is that I got lucky somehow. :^) Which also works with 4.3. I admit that I have not tested the Chips driver on the 6554x generation lately, mainly because my only test system is a laptop and building the current version of X on this laptop is no fun. Unfortunately Code built on a current system isn't compatible with the libc on the ancient installation that runs on this box. Installing a current Linux on this box is out of the question since the required resources are not available on it. Despite this I've dug out the old machine and I'm currently building XFree86 on it over nfs. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xpert, Any software just for 15$ - 40$
David Dawes writes: Has anyone investigated the root cause of why there is no fixed font in the first place -- like why the font server isn't running? Was it never started (a vendor-specific configuration problem), or did it crash (a robustness problem with xfs)? There seems to be a robustness problem with xfs - there was a bug report about a segfaulting xfs in bugzilla which I was unable to reproduce. The massive pileup of this problem seems to have another cause, though. I don't think it's the fontserver that's to blame as this problem hasn't happened before. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] No valid mode found for this DFP/LCD on ATI Radeon QL
Moving to 4.3.0 is a show-stopper for me. The log reads No valid mode found for this DFP/LCD. I have used this config since around 4.0.x without bigger problems. Now I can get it working only with the VESA driver, never with Ati or Radeon. I have tried the original ati driver, the latest DRI r200 package - all to no avail :-( The config is: Radeon 8500 LE 64MB Belinea 103065 RedHat 9.0 Linux My config and log are attached. Any help would be very much appreciated. Running X with the VESA driver is no fun!!! Thanks in advance! --jp XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.19 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Tue Jun 3 23:10:11 EEST 2003 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: Tue Jul 15 21:51:17 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device radeon (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout fi (**) XKB: layout: fi (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x80003c48, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0305 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00 (II) PCI: 00:07:5: chip 1106,3058 card 1462,3300 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:09:0: chip 10ec,8139 card 142a,0203 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0c:0: chip 100b,0020 card 1385,f311 rev 00 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1002,514c card 1681,0002 rev 00 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x9000 - 0x90ff (0x100) IX[B] [1] -1 0 0x9400 - 0x94ff (0x100) IX[B] [2] -1 0 0x9800 - 0x98ff (0x100) IX[B] [3] -1 0 0x9c00 - 0x9cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xdc00 - 0xddff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xd000 - 0xd7ff (0x800) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:7:4), (-1,-1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0]
Re: [XFree86] Xpert, Any software just for 15$ - 40$
On Tue, 15 Jul 2003, David Dawes wrote: Has anyone investigated the root cause of why there is no fixed font in the first place -- like why the font server isn't running? Was it never started (a vendor-specific configuration problem), or did it crash (a robustness problem with xfs)? That's a good question. I always assumed it was a configuration problem since all the reports came from specific versions of Red Hat. Regardless, I think there is a fundamental robustness problem with the configuration used by these vendors. There is no reason to not have BOTH a font server and explicit font paths in the XF86Config. That way the X-server still runs if there isn't a font server, but if the font server is listed first, it will get used by default if it is running. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Opteron, PCI RADEON and PCIGART
Anyone know why GinGin64 would have problems with Forcing PCIMode with a Radeon 7000. The log shows it looping errors about RADEONCP. -- Mark Lane, CET mailto:[EMAIL PROTECTED] Hard Data Ltd. http://www.harddata.com T: 01-780-456-9771 F: 01-780-456-9772 11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3 -- Ask me about our Excellent 1U Systems! -- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] no screen after exiting X from startx
gabe-- It's a shot it the dark, but...check to see if your kernel has Radeon display support enabled. I encountered the same symptoms running a distribution kernel (Debian Woody) with a FireGL 1000 Pro Card. In my case all the virtual consoles went away when _entering_ X with startx. But that wasn't apparent until you exited X. I built a new kernel with the correct options and, _voila_, the problem went away. Also, a good reference is: http://www.linux.org/docs/ldp/howto/Framebuffer-HOWTO-5.html On Thursday, July 10, 2003, at 01:04 PM, gabebf wrote: I saw this posted in the groups, but no response there. I start X 4.3.0 from startx, and works fine, but on exit, I don't have a screen, but i can type shutdown -r now, blindly, and it works. What is it? I have an ati radeon 7500, and have the problem on both an lcd and a crt monitor. I'm running fvwm 2.4.15. gabe ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Odd problem with terminals
On Tuesday, July 15, 2003 4:30 am, Christian Convey wrote: What's the best way - just send you XFree86.0.log file resulting from a vesa run of XF86? That'll do. I don't care if it's a crash or not. I just want to see the mode list (plus the rest of the file, if it's convenient). -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] help with chips 65548 XF86Config
On Tuesday, July 15, 2003 11:40 am, Egbert Eich wrote: Andy Goth writes: From 4.3.0's README.chips, This driver must be considered work in progress, and those users wanting stability are encouraged to use the older XFree86 3.3.x versions. Thanks Andy, this is a pretty lame suggestion. A lot of work has been invested since these lines were included in the README to make this driver more stable. Unfortunately the README gets updated less frequently than the driver therefore this was overlooked. Your comments belittle those who have worked hard to make this driver more stable. Sorry, I only read the README and man page. I did an ls on the driver directory, but only for the purpose of hunting down the README/ChangeLog, which is/are of course elsewhere. I should have researched more and said less. I meant no insult. I even tried (lamely) to make a compliment... In the past I got 3.3.x chips working with a ct65554, but that's a different engine, so my experience might not be helpful. Which also works with 4.3. I admit that I have not tested the Chips driver on the 6554x generation lately, mainly because my only test system is a laptop and building the current version of X on this laptop is no fun. Unfortunately Code built on a current system isn't compatible with the libc on the ancient installation that runs on this box. Installing a current Linux on this box is out of the question since the required resources are not available on it. Despite this I've dug out the old machine and I'm currently building XFree86 on it over nfs. I have the same problem with my network; each host has a different CPU. I'll have to see about using nfs to build for the weaker machines---last time I tried (long ago), I got very frequent stale file handle errors, so it was easier and faster to do tar|nc/chroot/rsync instead. I'd test as well, but the laptop in question has been in the trash for quite some time now. Those things have a hard life! At least I managed to save the hard disk... it's kind of funny to see a 2 1/2 drive in a half-height bay. -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Overwriting Mandrake 9.1's XFree software
Hi guys, I've got Mandrake 9.1 installed, and it's time for me to replace the installed version of xf86 4.3, with a newer build from xf86's CVS tree. I had some trouble with the process, so could someone familiar with Mandrake 9.1 verify that I'm doing it right? step 1. build xf86's 'xc' package (make World) step 2. put its code into /usr/X11R6 (make install) step 3. reboot (the only way this newbie knows how to restart x) Problem is, when I do this I get crashes in the x server. (Stack trace suggests its related to not finding the font server.) Any ideas? Thanks, Christian ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] no screen after exiting X from startx
Well, it was working with the ati driver in 4.2.x that came with OpenBSD 3.2 (should have mentioned the OS). Thanks, though. Actually, the only reason I went to the trouble of installing 4.3.0 was to fix this ghosting/blurring/echoing artifact, which had nothing to do with the drivers - it was my multiple vga cable connections. I can live with it, though, if I don't want X running (and want the console), rebooting isn't a problem. Really no big deal. Thanks everyone. On Tuesday, July 15, 2003, at 05:24 PM, Rich Johnson wrote: gabe-- It's a shot it the dark, but...check to see if your kernel has Radeon display support enabled. I encountered the same symptoms running a distribution kernel (Debian Woody) with a FireGL 1000 Pro Card. In my case all the virtual consoles went away when _entering_ X with startx. But that wasn't apparent until you exited X. I built a new kernel with the correct options and, _voila_, the problem went away. Also, a good reference is: http://www.linux.org/docs/ldp/howto/Framebuffer-HOWTO-5.html __ Ode On A Sugar Sweet LAN I love my 'pooters, and my 'pooters love me. We're just a big digital family. Me and my 'pooters, we get along fine. I'm super tickled, my 'pooters are mine. __ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] NVidia Drivers
On Tuesday, July 15, 2003 1:08 am, Nickolay Kolev wrote: I have recently had to look into my X server log and found a few disturbing log messages. It seems like my video card is trying something it cannot do for a while before giving up. This does explain the small delay (and blinking) I thought was normal when switsching form console to X. What log messages concern you? The only thing I see that appears repeated is: (II) NVIDIA(0): Not using default mode 640x350 (vrefresh out of range) (II) NVIDIA(0): Not using default mode 320x175 (vrefresh out of range) [...] (II) NVIDIA(0): Not using default mode 1024x768 (hsync out of range) (II) NVIDIA(0): Not using default mode 1152x864 (width too large for \ virtual size) This is nothing to worry about, unless your hsync/vrefresh/etc values aren't correct. These are supposed to be autodetected, but since your monitor doesn't appear to support DDC (Failure reading EDID parameters) they might be wrong, unless you got the values you list in Section Monitor from an official source (manual or similar). I'm not sure I believe your VertRefresh range really is 75.0 - 75.0, so maybe you should look into the matter... This won't cause flickering. XFree86 doesn't actually try to set these modes. All it does is perform a sanity check on all modes it knows about so that it can never set your monitor into a potentially hazardous state. -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xpert, Any software just for 15$ - 40$
On Thu, Jul 10, 2003 at 10:12:35PM -0400, gabe f wrote: harmful in that it adds traffic to the list? I learn things by hearing replies that people might have (inadvertantly) made direct to the author. If the reply-to field was not munged people would have to choose to make the threads readable by the list ( like a news group). If they didn't think about it, or decided for some (shy/considerate) reason to make their responses not to the group, then we'd really miss out on a lot of knowledge. my 2 cents. They should be pressing the right button in their MUA; Reply-To is a field that says if you want to reply to the person who wrote this message, send mail here. Setting Reply-To list-wise, thus impedes personal replies (hint: not all traffic belongs on-list). -- Daniel Stone [EMAIL PROTECTED] http://www.kde.org - http://www.debian.org - http://www.xwin.org Configurability is always the best choice when it's pretty simple to implement -- Havoc Pennington, gnome-list pgp0.pgp Description: PGP signature
Re: [XFree86] Xpert, Any software just for 15$ - 40$
On Thu, Jul 10, 2003 at 04:10:58PM -0600, Marc Aurele La France wrote: On Thu, 10 Jul 2003, Andy Goth wrote: On Tuesday, July 8, 2003 12:05 pm, Egbert Eich wrote: Daniel Stone writes: I also hope like hell Mailman isn't munging Reply-To, because that's just *wrong*. Hm, I don't know what you would call munging, it puts the list address into the Reply-To. Daniel is probably referring to: http://www.unicom.com/pw/reply-to-harmful.html ... which expresses an opinion not that widely held. Sorry, I lost about 10min worth of mail when I switched hosts my mail spooled on, and Egbert's reply must've been in that. Reply-To considered harmful is an opinion I hold, and it seems to be the opinion of most everyone I've encountered. The pressure should be on the MUA to do the right thing; either the user should set a Mail-Followup-To header, or you should reply to all per default, or you should just do a list reply. -- Daniel Stone [EMAIL PROTECTED] http://www.kde.org - http://www.debian.org - http://www.xwin.org Configurability is always the best choice when it's pretty simple to implement -- Havoc Pennington, gnome-list pgp0.pgp Description: PGP signature
Re: [XFree86] xdm startup auth problem
On Thu, Jul 10, 2003 at 08:36:31PM -0500, Rich Winkel wrote: Hi, I'm running 4.2.1 under freebsd 4.8. I can run just xf86cfg or startx with no problem, but running xdm I get: AUDIT: Thu Jul 10 20:31:47 2003: 2422 X: client 2 rejected from local host Auth name: MIT-MAGIC-COOKIE-1 ID: -1 Xlib: connection to :0.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key I've seen this before ... shouldn't this be in a FAQ somewhere? Are you using gcc 3.3? If so, try compiling with -O, not -O2. -- Daniel Stone [EMAIL PROTECTED] http://www.kde.org - http://www.debian.org - http://www.xwin.org Configurability is always the best choice when it's pretty simple to implement -- Havoc Pennington, gnome-list pgp0.pgp Description: PGP signature
[XFree86] Unable to load X windows
Attached is my log file...I am a newbie to linux...I seem to be having problems in my configuration settings in XF86Config file. The monitor that I have is a MAGITRONIC and my video card is a Trident. I seem to be able to run my box in text mode but fail to run in graphical mode. XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 16:42:56 EST 2003 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.1.log, Time: Sun Jul 13 19:10:52 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--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/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000580c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7030 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:07:0: chip 8086,7000 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7010 card , rev 00 class 01,01,80 hdr 00 (II) PCI: 00:0a:0: chip 1023,9660 card , rev d3 class 03,00,00 hdr 00 (II) PCI: 00:0b:0: chip 10b7,9050 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 00:0c:0: chip 1045,c861 card 1045,c861 rev 10 class 0c,03,10 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:10:0) Trident Microsystems TGUI 9660/938x/968x rev 211, Mem @ 0xe700/22, 0xe680/16 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0x - 0x (0x1) IX[B] [6] -1 0 0x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xe600 - 0xe6000fff (0x1000) MX[B] [1] -1 0 0xe680 - 0xe680 (0x1) MX[B](B) [2] -1 0 0xe700 - 0xe73f (0x40) MX[B](B) [3] -1 0 0xe000 - 0xe03f (0x40) IX[B] [4] -1 0 0xe800 - 0xe80f (0x10) IX[B] (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xe600 - 0xe6000fff (0x1000) MX[B] [1] -1 0 0xe680 - 0xe680 (0x1) MX[B](B) [2] -1 0 0xe700 - 0xe73f (0x40) MX[B](B) [3] -1 0
[XFree86] Need help in Configuring X Windows
Hi I am new to Linux and this list. Recently I installed RedHat Linux 7.1 on my system. Which has following configuration. RedHat Linux 7.1 AMD Athlon 1800 nVidia GEForce 2MX Video Card Zenith 753S MOnitor I tried configure using XConfigurator. I have selected NVIDIA GEForce MX as my display card, when prompted. I choosed to enter the custom values for monitor's Horizontal and vertical Sync, so I have entered the values, which are specified in user manual of Monitor. I am unable configure X-Windows (XFree86). Please help me KBS Gowda Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now ! ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xdm startup auth problem
Are you using gcc 3.3? If so, try compiling with -O, not -O2. Hi Daniel, Thanks for the reply. No, it was compiled with gcc 2.95.4 ... Get this: I have another machine where xdm works fine. It has the same OS version and exact same X11R6 and local dirs. I copied /etc and /var from the working machine to the other and rebooted. STILL it doesn't work. The only difference that I can see is that one has a pentium2 cpu, the other is an athlon. Rich ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Matrox G450 on solaris
On Tuesday, July 15, 2003 5:43 am, Miroslav Novy wrote: I am using XFree 4.3 on solaris 9 (intel) with Matrox G450 card. When I run xdm I have got only black screen. xdm error (pid 335): Hung in XOpenDisplay(:0), aborting xdm error (pid 335): server open failed for :0, giving up xdm error (pid 331): Display :0 cannot be opened Does startx work? -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xpert, Any software just for 15$ - 40$
On Tuesday, July 15, 2003 8:26 pm, Daniel Stone wrote: On Thu, Jul 10, 2003 at 04:10:58PM -0600, Marc Aurele La France wrote: On Thu, 10 Jul 2003, Andy Goth wrote: On Tuesday, July 8, 2003 12:05 pm, Egbert Eich wrote: Daniel Stone writes: I also hope like hell Mailman isn't munging Reply-To, because that's just *wrong*. Hm, I don't know what you would call munging, it puts the list address into the Reply-To. Daniel is probably referring to: http://www.unicom.com/pw/reply-to-harmful.html ... which expresses an opinion not that widely held. Sorry, I lost about 10min worth of mail when I switched hosts my mail spooled on, and Egbert's reply must've been in that. Reply-To considered harmful is an opinion I hold, and it seems to be the opinion of most everyone I've encountered. The pressure should be on the MUA to do the right thing; either the user should set a Mail-Followup-To header, or you should reply to all per default, or you should just do a list reply. Since everybody has a different opinion, I think it would make sense to set up the mail server so that people can choose whether or not they want Reply-To fields tacked onto emails they receive. This should make everybody (except the admin, heh) happy. Then only remaining debate would be what should be the default. Existing users should be set to Reply-To mode until they tell the server otherwise. As for new users, the subscribe page should have a checkbox (by default checked) enabling Reply-To fields. If there is also an email-only way to subscribe (I don't know), it should by default enable Reply-To, and the subscription confirmation message should explain the issues and how to change the Reply-To setting. Rationale: My observations indicate that it's mostly people with longtime experience who complain about Reply-To, so these people should be capable of follow simple instructions to change their account settings. It doesn't matter much to me if someone actually implements this suggestion. If it happens, I'll turn off Reply-To's for mails sent to me. If it doesn't happen, I won't complain. It may be a little ugly, but I know how to use my mua to send to the original poster despite Reply-To's setting, so long as he/she didn't have to set Reply-To in the first place. Yeah, I know I said I wouldn't reply, but I think that maybe, just maybe, the above might lead to a resolution nearly everybody can (grudgingly?) live with. -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Need help in Configuring X Windows
I'm not sure which version of XFree86 comes with RedHat 7.1. I assume you say you are unable to configure XFree86 because startx is not working? If so, we'll need to see the /var/log/XFree86.0.log file. Mark. On Wed, 16 Jul 2003, kbsgowda wrote: Hi I am new to Linux and this list. Recently I installed RedHat Linux 7.1 on my system. Which has following configuration. RedHat Linux 7.1 AMD Athlon 1800 nVidia GEForce 2MX Video Card Zenith 753S MOnitor I tried configure using XConfigurator. I have selected NVIDIA GEForce MX as my display card, when prompted. I choosed to enter the custom values for monitor's Horizontal and vertical Sync, so I have entered the values, which are specified in user manual of Monitor. I am unable configure X-Windows (XFree86). Please help me KBS Gowda Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now ! ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Unable to load X windows
Attached is my log file...I am a newbie to linux...I seem to be having problems in my configuration settings in XF86Config file. The monitor that I have is a MAGITRONIC and my video card is a Trident. I seem to be able to run my box in text mode but fail to run in graphical mode. What I find interesting is that even 640x480 is said to be too wide for your virtual size. Do you have a defined virtual size in your display settings? Could you post your config file as well? Regards, Pieter Hulshoff ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problem with xfree
On Thursday, July 15, 2010 3:58 am, Marek Kopec wrote: i'm trying to start x-terminal via etherboot and ltsp (x-klient 486 dx 66 with tseng et 4000 w32p , x-server something better :) but i have some problem with xfree. (ww) tseng: no matching device section for instance (BusID PCI:65:21:0) A 486DX/66MHz with PCI? Well, the w32p was used on PCI cards, so it must be so. But I really don't trust that BusID... What does lspci say? I had a Tseng ET4000 (I think that's the chip name), but it caused hardware lockups when too much changed on the screen at a time (I could reproduce this with the BIOS menus), so I had to throw it in the garbage. I managed to make it work with XFree86 4.3.0, in a multihead configuration no less, but I only got a valid display one time in ten or so, and it would immediately halt the computer thereafter. But hey, I pulled it from a computer whose motherboard caught fire, so I couldn't really expect it to work right. :^) I use xfree 4.1.0 (ltsp x core 3.0.4) and have tseng et 4000 w32p video card. Can you take this opportunity to upgrade to 4.3.0? Compiling X on a 66MHz, is, to misquote Egbert Eich, no fun. If you can make the binary elsewhere, you should be set. 4.2.0 made some various updates to the tseng driver (http://www.xfree86.org/4.2.0/RELNOTES2.html#3), which you are probably in need of. It could be that upgrading will fix your problem, so go for it. According to http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/tseng/ , the latest change to tseng (aside from removing an #ifdef) predates 4.3.0 by several months, but you should get the latest anyhow since the underlying PCI code, etc, has been updated. Lastly, I have been considering making a couple cheapie dedicated X servers for my house. Will a 486DX2/50MHz work? How about a 486SX/25MHz? Overclocked to 33MHz? -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] LOG File
On Tuesday, July 15, 2003 9:14 am, [EMAIL PROTECTED] wrote: hi.. I have a Slackware 9 and when trying to initialize KDE the system said it couldn't find the images.. what can I do? Your log file says: Parse error on line 279 of section InputDevice in file /etc/X11/XF86Config Section is not a valid keyword in this section. (EE) Problem parsing the config file Show us /etc/X11/XF86Config and we should be able to find the problem there. -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Overwriting Mandrake 9.1's XFree software
On Tuesday, July 15, 2003 7:13 pm, Christian Convey wrote: I've got Mandrake 9.1 installed, and it's time for me to replace the installed version of xf86 4.3, with a newer build from xf86's CVS tree. Cool. Is there a specific reason why you're upgrading, or do you just want to see what has changed since 27 February 2003? I had some trouble with the process, so could someone familiar with Mandrake 9.1 verify that I'm doing it right? step 1. build xf86's 'xc' package (make World) step 2. put its code into /usr/X11R6 (make install) step 3. reboot (the only way this newbie knows how to restart x) Problem is, when I do this I get crashes in the x server. (Stack trace suggests its related to not finding the font server.) Stack trace? You mean log file, right? font server? Be sure xfs is running. (xfs = X Font Server) Personally, I don't use xfs since I don't see a reason to serve fonts to myself when I can just as easily configure XFree86 to internally grab them from disk. To do this, adjust your /etc/X11/XF86Config file to contain FontPath entries for all the font directories you have: Section Files [...] FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/CID/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/local/ EndSection Something like this... but be sure to only list directories you really have, or else you'll get warnings every time you start X. Do ls /usr/X11R6/lib/X11/fonts/ to get a list. List 100dpi before 75dpi if you like bigger fonts. You can keep the unix/:7100 line if you want. Put it near the top of the list if you want the other directories to be used as fallbacks in case xfs dies or doesn't start correctly (something we see very often with Red Hat and friends). Your system might use /etc/X11/XF86Config-4 instead. The -4 version takes precedence, if it exists. -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ Engineers love to change things. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
