CVS Update: www (branch: trunk)
CVSROOT:/home/x-cvs Module name:www Changes by: [EMAIL PROTECTED] 03/03/05 10:37:51 Log message: - Re-clean with tidy. - Fix CSS for links to only apply to 'a' elements. - Misc cleanups. Modified files: ./: coreteam.html developer.html getting.html index.html rel420.html rel430.html releaseplans.html support.html www/contrib/: majcontrib.html www/cvs/: index.html www/security/: index.html publickey.html www/xnews/: index.html Removed files: ./: http.html mirrors.html old-developer.html Revision ChangesPath 1.14 +166 -176 www/coreteam.html 1.2 +9 -28 www/developer.html 1.10 +59 -71www/getting.html 1.99 +183 -171 www/index.html 1.7 +102 -111 www/rel420.html 1.3 +52 -47www/rel430.html 1.23 +41 -40www/releaseplans.html 1.39 +194 -183 www/support.html 1.4 +134 -135 www/contrib/majcontrib.html 1.9 +406 -434 www/cvs/index.html 1.18 +144 -121 www/security/index.html 1.4 +53 -49www/security/publickey.html 1.12 +205 -200 www/xnews/index.html ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: www (branch: trunk)
CVSROOT:/home/x-cvs Module name:www Changes by: [EMAIL PROTECTED] 03/03/05 13:28:49 Log message: Fix bad errata link. Modified files: ./: rel430.html Revision ChangesPath 1.4 +2 -2 www/rel430.html ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: www (branch: trunk)
CVSROOT:/home/x-cvs Module name:www Changes by: [EMAIL PROTECTED] 03/03/05 21:07:36 Log message: formatting cleanup Modified files: ./: coreteam.html Revision ChangesPath 1.15 +12 -11www/coreteam.html ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: www (branch: trunk)
CVSROOT:/home/x-cvs Module name:www Changes by: [EMAIL PROTECTED] 03/03/05 21:55:58 Log message: - Cleanup the formatting with 'tidy'. - Note that the corp profile needs to be updated. Modified files: www/legal/: art_of_inc.html by_laws.html corp_profile.html index.html licence.html org_minutes.html Revision ChangesPath 1.4 +208 -190 www/legal/art_of_inc.html 1.5 +1608 -1455www/legal/by_laws.html 1.4 +213 -165 www/legal/corp_profile.html 1.4 +35 -32www/legal/index.html 1.7 +45 -31www/legal/licence.html 1.4 +240 -217 www/legal/org_minutes.html ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: XFree86 module compatibility?
On Tue, 4 Mar 2003, Kendall Bennett wrote: I know I have asked this before, but I can't seem to find my emails and the mailing list archive does not seem to be responding. What sort of back/forward compatibility is there with the XFree86 driver modules? From memory last time I tested this, if I compile a 4.2.0 module it will work with any version of 4.2.x, but it will fail to load on 4.3.x or 4.1.x. So right now we are thinking of building modules for 4.0.x, 4.1.x, 4.2.x and 4.3.x and shipping all four modules with our installer (which will auto choose which one to install). Is that the correct approach? Or should we be building modules for each released version of XFree86 (ie: 4.1.0, 4.1.2, 4.1.3, 4.2.0, 4.2.1 etc)? The compatibility we strive for (but admittedly don't always accomplish) is best expressed as Version(module) = Version(core binary) There are also inter-module dependencies to consider. 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: Multiple Video Consoles
Jonathan,
could you also post your XF86Config file? I have some ideas on how
to extend this. It's still kind of a hack, but here goes:
add an option to the radeon driver, say MergedFB or something like
that. when that option is set to TRUE, it would skip the sections of
code that you have commented out.
next add sub options for MergedFB like:
Option MFB-Xres 2048
Option MFB-Yres 768
these would set the virtualX and Y instead of having to hardcode them.
it's still hackey, but would clean it up a bit and allow run time
configuration.
Alex
--- Jonathan Thambidurai [EMAIL PROTECTED] wrote:
I posted the following message to the DRI-devel lists the day before
yesterday and was told it might be of interest to this discussion.
Additionally, I have attached some diffs, contrary to what is said as
follows.
I am pleased to report that thanks to the guidance Jens Owens gave in
a
previous message, I have made 3D work on two heads simultaneously
(IIRC,
the ATI Windows XP drivers didn't do this). I have not provided a
diff
because it is quite a hack and very system specific, at the moment.
Effectively, I forced the virtual size to be 2048x768, hacked the
RADEONDoAdjustFrame() function to fix views as I wanted them, used
the
default cloning stuff to setup the second monitor, and removed all
the
conditionals that were preventing dual-head+DRI from working. I had
to
enable Xinerama (even though I have only one screen in the server
setup)
in the config file; otherwise, the desktop would end at 1024 instead
of
2048. The problem I mentioned in a previous post -- not enough
memory
for direct rendering w/ two screens -- was solved when I set it to 16
bpp. Does anyone have any ideas for a more elegant implementation of
this functionality, especially where the config file is concerned?
This
is the first real code I have done in the Xserver and any input would
be
appreciated.
--Jonathan Thambidurai
p.s. If there is something strange about the diffs, please tell me;
it
is the first time I generated any
--- /usr/local/src/XFree86.current/xc/programs/Xserver/GL/dri/dri.c
2002-12-05 10:26:57.0 -0500
+++ dri.c 2003-03-03 18:29:30.0 -0500
@@ -137,13 +137,13 @@
#endif
#if defined(PANORAMIX) || defined(XFree86LOADER)
-if (xineramaInCore) {
- if (!noPanoramiXExtension) {
- DRIDrvMsg(pScreen-myNum, X_WARNING,
- Direct rendering is not supported when Xinerama is enabled\n);
- return FALSE;
- }
-}
+/* if (xineramaInCore) { */
+/* if (!noPanoramiXExtension) { */
+/* DRIDrvMsg(pScreen-myNum, X_WARNING, */
+/* Direct rendering is not supported when Xinerama is
enabled\n); */
+/* return FALSE; */
+/* } */
+/* } */
#endif
drmWasAvailable = drmAvailable();
---
/usr/local/src/XFree86.current/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
2003-02-04 20:48:27.0 -0500
+++ radeon_driver.c 2003-03-03 19:16:23.0 -0500
@@ -2754,24 +2754,29 @@
xf86SetCrtcForModes(pScrn, 0);
/* We need to adjust virtual size if the clone modes have larger
- * display size.
+ * display size. JDTHAX04: hardcoding large virtual area
*/
if (info-Clone info-CloneModes) {
DisplayModePtr clone_mode = info-CloneModes;
while (1) {
- if ((clone_mode-HDisplay pScrn-virtualX) ||
- (clone_mode-VDisplay pScrn-virtualY)) {
- pScrn-virtualX =
- pScrn-display-virtualX = clone_mode-HDisplay;
- pScrn-virtualY =
- pScrn-display-virtualY = clone_mode-VDisplay;
- RADEONSetPitch(pScrn);
- }
+/* if ((clone_mode-HDisplay pScrn-virtualX) || */
+/* (clone_mode-VDisplay pScrn-virtualY)) { */
+/* pScrn-virtualX = */
+/* pScrn-display-virtualX = clone_mode-HDisplay; */
+/* pScrn-virtualY = */
+/* pScrn-display-virtualY = clone_mode-VDisplay; */
+/* RADEONSetPitch(pScrn); */
+/* } */
if (!clone_mode-next) break;
clone_mode = clone_mode-next;
}
}
+pScrn-virtualX = pScrn-display-virtualX = 2048;
+pScrn-virtualY = pScrn-display-virtualY = 768;
+RADEONSetPitch(pScrn);
+xf86DrvMsg(pScrn-scrnIndex, X_NOTICE,
+JDT HACK WORKING\n);
pScrn-currentMode = pScrn-modes;
xf86PrintModes(pScrn);
@@ -3463,18 +3468,18 @@
info-directRenderingEnabled = FALSE;
else {
/* Xinerama has sync problem with DRI, disable it for now */
- if (xf86IsEntityShared(pScrn-entityList[0])) {
- info-directRenderingEnabled = FALSE;
- xf86DrvMsg(scrnIndex, X_WARNING,
-Direct Rendering Disabled --
-Dual-head configuration is not
Re: Debugging in RH8?
Mike A. Harris [EMAIL PROTECTED] wrote: I am trying to debug XFree86 at the source code level on Red Hat 8.0 but not having much like. I force installed gdb-5.1.1-2.0xfree from the RPM file from Red Hat's site, but when I do 'gdb X' gdb crashes with a segmentation fault. gdb-xfree is currently not completely working solidly in 8.0 and later. It works for me to some extent but isn't perfect. I don't really grok gdb internals too well though, so I've gotten our gdb engineers to look into fixing gdb for once and for all in stock FSF gdb. No ETA unfortunately, but I'll likely announce it on devel@ though when there's something to play with that is useful. Ok, it sounds like I should perhaps back level my debugging machine to Red Hat 7.2 or 7.3? A guy working for me remote in Australia tells me that he is using the patched 5.1.1 just fine on RH 7.2... But when you do get this into the stock gdb, please let us all know ;-) Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Debugging in RH8?
On Wed, 5 Mar 2003, Kendall Bennett wrote: I am trying to debug XFree86 at the source code level on Red Hat 8.0 but not having much like. I force installed gdb-5.1.1-2.0xfree from the RPM file from Red Hat's site, but when I do 'gdb X' gdb crashes with a segmentation fault. gdb-xfree is currently not completely working solidly in 8.0 and later. It works for me to some extent but isn't perfect. I don't really grok gdb internals too well though, so I've gotten our gdb engineers to look into fixing gdb for once and for all in stock FSF gdb. No ETA unfortunately, but I'll likely announce it on devel@ though when there's something to play with that is useful. Ok, it sounds like I should perhaps back level my debugging machine to Red Hat 7.2 or 7.3? A guy working for me remote in Australia tells me that he is using the patched 5.1.1 just fine on RH 7.2... I would recommend an rpm rebuild of gdb-xfree86 on 8.0 first to see if it is reliable enough for you or not, failing that in 7.3 it works pretty flawless for me. But when you do get this into the stock gdb, please let us all know ;-) Absolutely. ;o) -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 module compatibility?
On Wed, 5 Mar 2003, Marc Aurele La France wrote: On Wed, 5 Mar 2003, Kendall Bennett wrote: Is that the correct approach? Or should we be building modules for each released version of XFree86 (ie: 4.1.0, 4.1.2, 4.1.3, 4.2.0, 4.2.1 etc)? The compatibility we strive for (but admittedly don't always accomplish) is best expressed as Version(module) = Version(core binary) There are also inter-module dependencies to consider. So basically we should be able to compile with say 4.1.0 and have our module run on all greater versions of 4.x.0 right? Obviously YMMV, so we should probably test this. The downside of course is that we would much prefer to be compiling with the latest version of XFree86 rather than a backlevel version for our modules, but if we do that we will not be able to support older versions. Hence I am thinking that I should compile against the tip level in each sub version. Ie: 4.0.0, 4.1.0, 4.2.0, 4.3.0 etc so it will work with each minor revision of that branch (ie: 4.2.0 works with 4.2.1 through 4.2.99 which I already know). However if say I upgrade our development tree to 4.3.1, does that mean that the 4.3.1 driver will fail to load on a 4.3.0 install? The binaries you provide for your driver should be generated against the earliest (public) XFree86 version that provides the functionality your driver depends on. If that means 4.1.0, then that means 4.1.0. This does not absolve you of the responsibility to ensure the thus-generated binary works with later core binary versions. Allow me to qualify that... The binaries you provide for your driver should be generated against the earliest (public) XFree86 version that provides the functionality your driver depends on and provides the suport base you are willing to live with. If that means 4.1.0, then that means 4.1.0. This does not absolve you of the responsibility to ensure the thus-generated binary works with later core binary versions. 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
logitech ps/2++ updates
I have a patch that updates the Logitech PS/2++ protocol to support their mice with up to 10 buttons (currently they're only using 8 on the MX500 and MX700). The PS/2++ protocol now uses 6 bits to identify a packet instead of 4 as before. Apparently, there's a touchpad protocol that also used it (more on that later). Updated PS/2++ protocol: The identifier type bits are now 6 bits instead of 4: bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 byte1 11 t5 t41MRL Button data byte2 t3 t2 t1 t0 d2 d110 X data byte3 d8 d7 d6 d5 d4 d3 d2 d1 Y data note: bit7, byte1 is 1 for external devices, 0 for internal ones name tdescription P0 - 0x0C - attached device type (corded mouse or receiver) P1 - 0x0D - roller and buttons 4 5 info P2 - 0x0E - buttons 4,5,6,7,8,9,10 info ... (other packet types aren't used/useful to X) This is the new P2 packet: bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 byte1 11001MRL byte2 1110 B5 B410 byte3 0 B10 B9 B8 B7 B6 B5 B4 B6 = task switch button B7 = SMS up button B8 = SMS down button B9/10 are not yet used in current mice There are also 2 feature additions (not PS/2++): Option SmartScroll (boolean) in the config enables/disables auto-scrolling on the SMSup/down buttons on the MX500/700. Also, 800 cpi resolution is now supported on mice that support it in hardware (Dual Optical, MX300/500/700, ...). Hopefully this will make high sensitivity users happy :) Here's my patch: http://yhbt.net/normalperson/files/xfree86/4.3.0_logitech_ps2.patch The downside of this patch is that some touchpad users that specify MouseManPlusPS/2 will probably need a new protocol defined for them. -- Eric Wong ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 module compatibility?
Marc Aurele La France [EMAIL PROTECTED] wrote: The binaries you provide for your driver should be generated against the earliest (public) XFree86 version that provides the functionality your driver depends on. If that means 4.1.0, then that means 4.1.0. This does not absolve you of the responsibility to ensure the thus-generated binary works with later core binary versions. Allow me to qualify that... The binaries you provide for your driver should be generated against the earliest (public) XFree86 version that provides the functionality your driver depends on and provides the suport base you are willing to live with. If that means 4.1.0, then that means 4.1.0. This does not absolve you of the responsibility to ensure the thus-generated binary works with later core binary versions. Right, we plan to test with every version of XFree86 to ensure compatibility (along with tons of Linux distros; ugh). We would like to support all versions of XFree86 with our module, and we have no problem building different modules as necessary to support those versions. What I am trying to figure out is what the smallest set of module versions I can build to ensure compatibility. It would be nice if I could build a 4.0.3 module and have it work with 4.0.0-4.0.3, but it sounds like I need to build 4.0.0 to work with all 4.0.x versions, right? Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 module compatibility?
On Wed, 5 Mar 2003, Kendall Bennett wrote: Marc Aurele La France [EMAIL PROTECTED] wrote: The binaries you provide for your driver should be generated against the earliest (public) XFree86 version that provides the functionality your driver depends on. If that means 4.1.0, then that means 4.1.0. This does not absolve you of the responsibility to ensure the thus-generated binary works with later core binary versions. Allow me to qualify that... The binaries you provide for your driver should be generated against the earliest (public) XFree86 version that provides the functionality your driver depends on and provides the suport base you are willing to live with. If that means 4.1.0, then that means 4.1.0. This does not absolve you of the responsibility to ensure the thus-generated binary works with later core binary versions. Right, we plan to test with every version of XFree86 to ensure compatibility (along with tons of Linux distros; ugh). We would like to support all versions of XFree86 with our module, and we have no problem building different modules as necessary to support those versions. What I am trying to figure out is what the smallest set of module versions I can build to ensure compatibility. It would be nice if I could build a 4.0.3 module and have it work with 4.0.0-4.0.3, but it sounds like I need to build 4.0.0 to work with all 4.0.x versions, right? Nothing will work with all 4.0.x versions. 4.0.0 XAA isn't binary compatible with 4.0.1 and newer XAAs. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Internal documentation
On Mon, 3 Mar 2003 10:54:16 -0600 jkjellman [EMAIL PROTECTED] wrote: I am working on modifying an input driver (or two :-) and am having a little trouble. I cannot find man pages or other documentation on internal X calls. For example, xf86Msg, xf86OpenSerial, etc. I have figured out some of these based on usage in the source files, but the less obvious ones are becoming a problem. For example, xf86PostMotionEvent has a series of parameters, most of which are hard coded in the drivers I am looking at. While I can search and read source code, this is not prefered as it is very time consuming when you know little if anything ;-) I'm doing very similar and, too, am having much trouble finding any information on how things work, etc... If I find anything I'll let you know, but for now the best I can suggest is http://www.atomised.org/docs/XFree86-4.2.1/ -- Paul Evans (3rd Year CompSci at Pembroke College, Cambridge, England) [EMAIL PROTECTED] (university) [EMAIL PROTECTED] (alternate) ICQ# 4135350 Registered Linux User: 179460 http://www.srcf.ucam.org/~pe208/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 module compatibility?
Feigning erudition, Kendall Bennett wrote: % Marc Aurele La France [EMAIL PROTECTED] wrote: % % The binaries you provide for your driver should be generated against the % earliest (public) XFree86 version that provides the functionality your % driver depends on. If that means 4.1.0, then that means 4.1.0. This does % not absolve you of the responsibility to ensure the thus-generated binary % works with later core binary versions. % % Allow me to qualify that... % % The binaries you provide for your driver should be generated against the % earliest (public) XFree86 version that provides the functionality your % driver depends on and provides the suport base you are willing to live % % with. If that means 4.1.0, then that means 4.1.0. This does not absolve % % you of the responsibility to ensure the thus-generated binary works with % later core binary versions. % % Right, we plan to test with every version of XFree86 to ensure % compatibility (along with tons of Linux distros; ugh). We would like to % support all versions of XFree86 with our module, and we have no problem % building different modules as necessary to support those versions. What I % am trying to figure out is what the smallest set of module versions I can % build to ensure compatibility. We fight the tons of Linux distros; ugh battle at work. Rather, we quickly decided that we *couldn't* fight that battle and win, so we chose a double handful of distributions that: ° We believe represents significant shares of the installed Linux base ° Complements the strengths of our developers, QA personnel, writers, and in-house Linux users (we're a mixed Linux/Windows shop) Off the top of my head, we chose 2 recent Linux-Mandrake releases, the last 3 Red Hat Linux releases, the most recent SuSE release, and Debian Potato and Woody. I suppose we'd add your favorite distro here if a customer waved enough shekels at us to make the QA effort worthwhile. % It would be nice if I could build a 4.0.3 module and have it work with % 4.0.0-4.0.3, but it sounds like I need to build 4.0.0 to work with all % 4.0.x versions, right? I'd venture to say you just have to test against the N releases you think you can afford or have the resources to support. Kurt -- God may be subtle, but He isn't plain mean. -- Albert Einstein ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: miTranslate related problems.
Around 21 o'clock on Mar 5, Mark Vojkovich wrote: So am I right that when pGC-miTranslate is true, the caller needs to add the drawable origin to FillSpans, SetSpans and PushPixels? Yes, the drawable origin must be added into all of the parameters to these functions when the top-most such function is called. If so, doesn't that mean that miDCPutBits is broken, and also FillSpans, SetSpans and PushPixels in both shadow framebuffer layers? Yes, miDCPutBits looks broken, but the only drawables ever used are the root window and pixmaps both of which used to have zero origins. On the other hand, the shadow frame buffer layers are just passing arguments through from above and the offsets should already have been added in by functions above the shadow code. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: miTranslate related problems.
On Wed, 5 Mar 2003, Keith Packard wrote: Around 21 o'clock on Mar 5, Mark Vojkovich wrote: So am I right that when pGC-miTranslate is true, the caller needs to add the drawable origin to FillSpans, SetSpans and PushPixels? Yes, the drawable origin must be added into all of the parameters to these functions when the top-most such function is called. If so, doesn't that mean that miDCPutBits is broken, and also FillSpans, SetSpans and PushPixels in both shadow framebuffer layers? Yes, miDCPutBits looks broken, but the only drawables ever used are the root window and pixmaps both of which used to have zero origins. Offscreen pixmaps don't so this has been broken since 3.9.x. It's obviously not a common case if I'm just seeing this now for the first time. On the other hand, the shadow frame buffer layers are just passing arguments through from above and the offsets should already have been added in by functions above the shadow code. OK, I'll change them then. I suppose the miTranslate check should go in miDCPutBits. Do you think I should bother with miTranslate checks in the shadow framebuffer layers? Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 module compatibility?
Kendall, You should also test against different distributions, different compilers (gcc 3.2.x versus 2.95) and different C libraries. In particular, modules compiled with gcc 2.95 might not work with XFree86 compiled with gcc 3.2.x and vice versa.. best Vladimir Dergachev ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: miTranslate related problems.
Around 23 o'clock on Mar 5, Mark Vojkovich wrote: Offscreen pixmaps don't so this has been broken since 3.9.x. It's obviously not a common case if I'm just seeing this now for the first time. The core cursors are all 16x16, which is presumably smaller than the pixmap code would put in off-screen memory for cards that didn't have hardware cursor support. Still, it's a bit surprising that no-one has ever seen a problem with this (or at least no-one has complained here). OK, I'll change them then. I suppose the miTranslate check should go in miDCPutBits. Do you think I should bother with miTranslate checks in the shadow framebuffer layers? Yes, miDCPutBits should check miTranslate. The shadow layers *mustn't* be changed -- the miTranslate checks would have occured in whatever function was calling through the shadow layer: miPolyArc shadowPushPixels fbPushPixels The miTranslate check is done in miPolyArc before shadowPushPixels is called. If this were broken, lots of stuff wouldn't work on shadow frame buffers. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: miTranslate related problems.
Around 0 o'clock on Mar 6, Mark Vojkovich wrote: You don't understand. The shadow framebuffer SetSpans, FillSpans and PushPixels ARE CURRENTLY TRANSLATING. Ah. Yes, I was confused. the miext/shadow code doesn't translate the data on the way to the underlying code (I thought you were saying it should), but it does translate coordinates when computing the damage region. Oops. I think they never actually get used which is why you don't see more stuff broken. Yes, they can't get called unless someone invokes them from outside the rendering code -- normally, they're called from general mi rendering routines below the shadow layer. Except for PushPixels in the software cursor code. Sorry for the mass confusion here. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[XFree86] Hello!
I'm wondering if the Linux-ix86-glibc22 binaries will be published and eventually when? Best regards Kjetil Myhre ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] problem regarding X server system.
Dear Sir, I am using a Red Hat 8.0 as server and accessing files from it using telnet from a remote machine which runs Windows 2000 Professional. The problem is that when I try starting the X Windows Server (after I have logged in the server by telnet as a user/root) the X windows won't start giving the following error: Fatal Server Error: PAM authentication failed, cannot start X server. Perhaps you donot have console ownership? This was the only error message given. I would be obliged if you could help me. Thanking You, Yours truly, Vikhyat Srivastava VIKHYAT SRIVASTAVA, C-18, I.I.P.S. Hostel, Khandwa Road, Ring Road, Indore, M.P., India-452017. Ph.:0731-361727. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] SiS 6326 AGP Bus VS XFree86 ...
This file are the Log File and the Config File for my SiS 6326 + monitor Unisys EVG-174-COL. It seems to be strange the Config File, about the ModeLine for the Monitor. There are 1024x480 ... and other format... More strange! Please, help me! K.L.0.D.3. XF86Config-4.dat Description: Binary data XFree86.0.log Description: Binary data
[XFree86] [XFree86(TM) Bug Report] Problem with XFree86 configuration
Regarding: Problem with XFree86 configuration Email: [EMAIL PROTECTED] XFree86 Version: XFree86-3.3.6-11 OS: FreeBSD 4.6 Area: Xserver Server: Other, specify below Video Card: ATI Rage 128 ULTRA 32 MB Description: When I try to use my Xserver by taping startx I have this message: [...] ConfigError: /usr/X11R6/lib/X11/XF86Config Section ServerLayout not a recognised section name. Repeat By: There are all the steps I do: 1- cd /usr/ports/x11/XF86 2- make 3- make install clean 4- XFree86 -configure 5- vi XFree86Config.new 6- Modifications: Section Monitor ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] Problem with XFree86 configuration
Regarding: Problem with XFree86 configuration Email: [EMAIL PROTECTED] XFree86 Version: XFree86-3.3.6-11 OS: FreeBSD 4.6 Area: Xserver Server: Other, specify below Video Card: ATI Rage 128 ULTRA 32MB Description: When I try to use the XServer by taping startx, I have this message: [...] Config Error: /usr/X11R6/lib/X11/XF86Config Section ServerLayout not a recognised section Repeat By: There are the steps I do: 1- cd /iusr/ports/x11/XF86 2- make 3- make install clean 4- XFree86 -configure 5- vi XFree86Config.new 6- Modifications: Section Monitor HorizSync 30-80 VertRefresh 56-85 Section Screen DefaultDepth 24 Subsection Display Depth 24 Modes 1024x768 7- cp XF86Config.new /etc/x11/XF86Config 8- the test XF86 -xf86config XF86Config.new is correct, I have the grey screen with the cross (mouse) 9- cd /usr/port/x11/wrapper 10- make 11- make install 12- startx And then I have an error message What did I do wrong? Can you help me please? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Experimental Radeon IGP 320M Drivers
Hello, I read on the list archives that someone has a preliminary Radeon IGP 320M (AKA Radeon Mobility U1) driver for XFree86 4.3. I Would like to help test them out. Can someone point me to where I can get it or send it to me? Thank you, Carl Thompson ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [PATCH] restore the sign of UNDERLINE_POSITION in FreeType rasterizer
Hi,
In FreeType font rasterizer the sign of the XLFD property
UNDERLINE_POSITION has changed between 4.2.1 and 4.3.0. Because of
this, Type1 and TrueType fonts now have UNDERLINE_POSITION negative,
which makes gtk1 builds of mozilla loose underlining. This patch
restores the previous behavior (assuming it was correct in 4.2.1 and
before, of which I'm not completely certain).
Regards,
Roman.
--- xc/lib/font/FreeType/ftfuncs.c~ 2003-02-13 06:01:45.0 +0300
+++ xc/lib/font/FreeType/ftfuncs.c 2003-03-04 20:27:16.0 +0300
@@ -959,11 +959,11 @@
int underlinePosition, underlineThickness;
if(post) {
-underlinePosition = TRANSFORM_FUNITS_Y(post-underlinePosition);
+underlinePosition = TRANSFORM_FUNITS_Y(-post-underlinePosition);
underlineThickness = TRANSFORM_FUNITS_Y(post-underlineThickness);
} else {
underlinePosition =
-TRANSFORM_FUNITS_Y(t1info-underline_position);
+TRANSFORM_FUNITS_Y(-t1info-underline_position);
underlineThickness =
TRANSFORM_FUNITS_Y(t1info-underline_thickness);
}
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86(TM) Bug Report] Problem with XFree86configuration
On Wed, 5 Mar 2003, Visotheary Riviere-Ung wrote: Regarding: Problem with XFree86 configuration Email: [EMAIL PROTECTED] XFree86 Version: XFree86-3.3.6-11 [...] Config Error: /usr/X11R6/lib/X11/XF86Config Section ServerLayout not a recognised section ServerLayout is a new feature in XFree86 4.0 -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Server Crash on start
Hi I am constantly getting the following problem. XFree86 Version 4.0.1a / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 2 August 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.5-22smp i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Wed Mar 5 14:38:21 2003 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor CTX5370 (**) | |--Device nVidia Corporation|NV11 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbLayout gb (**) XKB: layout: gb (**) 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) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.2 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.1 (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.0.1a, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.1 (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.0.1a, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.2 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x803c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1a30 card , rev 11 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 11 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24c2 card 1462,5661 rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 1462,5661 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 1462,3981 rev 01 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 81 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24c0 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24cb card 1462,5661 rev 01 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 1462,5661 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24c5 card 1462,5661 rev 01 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0110 card 1462,8521 rev b2 class 03,00,00 hdr 00 (II) PCI: 03:01:0: chip 10b9,5459 card 10a5,5459 rev 00 class 07,03,00 hdr 00 (II) PCI: 03:02:0: chip 1113,1216 card 10b8,1255 rev 11 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.0.1a, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.2 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Bus 1: bridge is at (0:1:0), (0,1,2), BCTRL: 0x0f (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xddc0 - 0xdfdf (0x220) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xcd80 - 0xdd9f (0x1020) MX[B] (II) Bus 3: bridge is at (0:30:0), (0,3,3), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 3 I/O range: [0] -1 0xb000 - 0xb0ff (0x100) IX[B] [1] -1 0xb400 - 0xb4ff (0x100) IX[B] [2] -1 0xb800 - 0xb8ff (0x100) IX[B] [3] -1 0xbc00 - 0xbcff (0x100) IX[B] (II) Bus 3 non-prefetchable memory range: [0] -1 0xdfe0 - 0xdfef (0x10) MX[B] (II) Bus 3 prefetchable memory range: [0] -1 0xdda0 - 0xddaf (0x10) MX[B] (--) PCI:*(1:0:0) NVidia unknown chipset (0x0110) rev 178, Mem @ 0xde00/24, 0xd000/27 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0x000f - 0x000f (0x1) MX[B] [3] -1 0x000c - 0x000e (0x3) MX[B] [4] -1 0x - 0x0009 (0xa) MX[B] [5] -1 0x - 0x01ff (0x200) IX[B]E (II) Active PCI resource ranges: [0] -1 0xdfec - 0xdfef (0x4) MX[B]E [1] -1 0xdfefec00 - 0xdfefefff (0x400) MX[B]E [2] -1 0xdfeff000 - 0xdfef (0x1000) MX[B]E [3] -1 0xd900 - 0xd9ff (0x100) MX[B]E [4] -1 0xda00 - 0xdbff (0x200) MX[B]E [5] -1 0xdc00 - 0xdfff (0x400) MX[B]E [6] -1 0xe000 - 0x (0x2000) MX[B]E [7] -1 0xdfdf
[XFree86] Bug report
I am new to linux. My Display card is Nvidia Gforce 2.After exicuting NVIDIA_GLX-1.0-4191 downloaded from Nvida, my x server crashed. I am sending log file for this. Please help me. Bharat Parekh. _ Cricket World Cup 2003- News, Views and Match Reports. http://server1.msn.co.in/msnspecials/worldcup03/ XFree86.0.log Description: Binary data
[XFree86] [XFree86(TM) Bug Report] XQueryKeymap reports incorrect state of NUM LOCK
Regarding: XQueryKeymap reports incorrect state of NUM LOCK
Email: [EMAIL PROTECTED]
XFree86 Version: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72)
OS: Red Hat Linux 8.0 - OS Kernel: Linux version 2.4.18-24.8.0
Area: XServer
Server: XFree86 (The XFree86 4.x server)
Video Card:
N/A
Description:
I see a problem with the use of XQueryKeymap when run against a
Linux Xserver to determine if NumLock is on or off.
Using XQueryKeymap it only reports NumLock as on when the key is
physically held down.
If I run against, for example Solaris's Xserver, if the NumLock LED
is on, then I will see that using XQueryKeymap.
I've pasted a simple test progam in the Repeat by section below.
Repeat By:
#include X11/Xlib.h
#include X11/Xutil.h
#include X11/keysym.h
#include sys/types.h
#include stdio.h
int main( int argc, char *argv[] )
{
KeySym sym;
KeyCode keyCode;
u_int32_t byteIndex;
u_int32_t bitIndex;
charkeyVector[32];
Display*display;
int i;
if ( (display = XOpenDisplay(NULL) ) == NULL ) {
fprintf(stderr,Unable to open display\n);
exit( 1 );
}
keyCode = XKeysymToKeycode(display, XK_Num_Lock);
if (keyCode == 0) {
fprintf(stderr,Invalid KeyCode\n);
return False;
}
byteIndex = (keyCode/8);
bitIndex = keyCode 7;
XQueryKeymap(display, keyVector);
fprintf(stderr,\n);
for ( i = 0; i 32; i++ )
fprintf(stderr,%02X , keyVector[i]);
fprintf(stderr,\n);
if (1 (keyVector[byteIndex] bitIndex))
fprintf(stderr,True\n);
else
fprintf(stderr,False\n);
}
Against 4.2 (but also a 4.1 server) I see:
$ ./led
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
False
# Now I turn on NUMLOCK on the keyboard.
$ ./led
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
False
When I set my display to be a Solaris 8 Xserver:
$ ./led
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
False
# Turn on NUMLOCK
$ ./led
00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
True
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XFree 86 4.3.0: Type 1 fonts do not work with fontconfig
I successfully compiled XFree 4.3.0 on Solaris 9 x86, using GCC and GNU binutils, linked against my system's freetype 2.1.3 and not the bundled 2.1.1, and it works quite well, except for an important detail: Type 1 fonts are not working anymore. Actually, it's a bit more complicated. When I put my Type 1 font directory in /etc/X11/XF86config (as it was before, working very well with XF 4.2.x), the Type 1 fonts work correctly in X apps (like xfontsel), but do not appear at all in fontconfig apps (like KDE). When I put it in /etc/fonts/local.conf (along with dirs containing TrueType fonts, which work), the fonts are not displayed in X apps, but are in fontconfig apps, however, they're not working: if selected, they all look the same, kind of Helvetica. I ran mkfontscale and mkfontdir on all directories, then fs-cache, with the same results. Any idea ? Laurent ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] /var/log/XFree86.0.log
Dear XFree86, I am trying to configure an XWindows Server, using a standard DELL Pentium II PC as the hardware platform, running Open BSD 3.1. Please could you help me identify where I am going wrong with my XWindows installation on this platform ? I hope the attached log file provides necessary detail concerning the problem running startx. Many thanks, Andy Hamilton. Apoyar Networks UK Ltd. XFree86.0.log.log Description: XFree86.0.log.log
Re: [XFree86] Server Crash on start
Chief Penguin writes: Hi I am constantly getting the following problem. XFree86 Version 4.0.1a / X Window System ^^ Have you tried upgrading? Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] NO INPUT Device
Hi, I am trying to bring TinyX over an ARM board, which has no Input Device. I am not understanding how to build, X windows kdrive (TinyX) without Input Device Support Can anyone help me ? Thanks and Regards Vinayak ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] problems :s
Hi there, I can't install a driver cauz kernel doesn't recognise NTFS so I can't mount my XP partition and i can't get into the graphical mode of linux and al the drivers are to big for a disc plz I don't know it anumore... I try to boot with VESA but even that won't work ... greetz Kobe XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Mar 5 18:26:01 2003 (==) Using config file: /etc/X11/XF86Config-4 (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (EE) No devices detected. Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0 after 0 requests (0 known processed) with 0 events remaining. _ Hotmail: your free e-mail ! http://www.msn.be/hotmail XFree86.0.log Description: Binary data
[XFree86] [XFree86(TM) Bug Report] VMware and video drivers
Regarding: VMware and video drivers Email: [EMAIL PROTECTED] XFree86 Version: 4.1.0.1 OS: Debain 3.0 or RedHat 8.0 Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: ati M6 16 mb Description: This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.17 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Wed Mar 5 04:11:10 2003 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (**) |--Input Device Generic Mouse (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (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.1.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (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.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7192 card , rev 01 class 06,00,00 hdr 00 (II) PCI: 00:07:0: chip 8086,7110 card , rev 08 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 00 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 08 class 06,80,00 hdr 80 (II) PCI: 00:07:4: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:07:5: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:07:6: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:07:7: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:0f:0: chip 15ad,0405 card , rev 00 class 03,00,00 hdr 00 (II) PCI: 00:10:0: chip 1022,2000 card , rev 10 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(0:15:0) VMware PCI SVGA (FIFO) rev 0, Mem @ 0xfc00/24,
Re: [XFree86] problems :s
What video card are you using? What driver are you trying to install? If your using a stock kernel, you probably have an NTFS module available, and if 'mount -t ntfs /dev/whatever /mount point' doesn't load it automatically, you can try loading it with modprobe. Jesse On Wed, 5 Mar 2003, kobe nys wrote: Hi there, I can't install a driver cauz kernel doesn't recognise NTFS so I can't mount my XP partition and i can't get into the graphical mode of linux and al the drivers are to big for a disc plz I don't know it anumore... I try to boot with VESA but even that won't work ... greetz Kobe XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Mar 5 18:26:01 2003 (==) Using config file: /etc/X11/XF86Config-4 (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (EE) No devices detected. Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0 after 0 requests (0 known processed) with 0 events remaining. _ Hotmail: your free e-mail ! http://www.msn.be/hotmail ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Speedo and the Radeon 7000
Jesse Hutton wrote: I don't make the Speedo fonts available to X and I have no problems. It sounds like you're having trouble loading the Speedo module for some reason (I have no idea why a hardware upgrade would cause that, except for the fact that you may be using a new driver), which is used for serving up Speedo fonts to the X server. Try commenting it out in the Module section of your XF86Config-4 file if you don't mind not using these fonts, and you may as well comment out the speedo fontpath if you do that. Otherwise, you'll have to figure out why this modules isn't loading properly. Jesse On Tue, 4 Mar 2003, Bill Kristjanson wrote: I have installed a Radeon 7000 PCI in my Phoebe-3 (RH 8.0.94) system. After the upgrade of the card X refused to start. My system would lock and required the three-finger-salute. Through experimentation I have established that the problem occurs when X tries to load Speedo. I understand that speedo is a font backend. My questions are: Is speedo the new method of rendering fonts or the outgoing method? Does anyone know of a work-around to get it running? Is having no speedo fonts even something I should worry about? TIA Bill ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 Done... So all I miss with not having speedo is some fonts? I can live with that. Thanks, Bill ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Server Grafics (IMPORTANT)
Hello colleagues: Some bady can say me how many grafics servers (X-Windows) exist in addition to these, and the distribution use him... XFree86 Metro-X Xi-Graphics For example: Oper.Sys. X-Windows MacOS Apple's Quartz QNX Photon ... Thanks in advanced Girald ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Can you help me?
any time my pc, linux mandrake stop.Nothing to do! Only alt-Rsist-b:-) I think the problem is Nvidia but my pc is going now! XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18-23mdkenterprise i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Mar 5 19:54:54 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout layout1 (**) |--Screen screen1 (0) (**) | |--Monitor monitor1 (**) | |--Device device1 (**) |--Input Device Keyboard1 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout it (**) XKB: layout: it (WW) Option XkbOptions requires an string value (==) Keyboard: CustomKeycode disabled (**) |--Input Device Mouse1 (**) FontPath set to unix/:-1 (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (**) Option AllowMouseOpenFail Using vt 7 (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (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.2.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (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.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x80007854, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 10b9,1541 card 10b9,1541 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 10b9,5243 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:03:0: chip 10b9,7101 card 10b9,7101 rev 00 class 06,80,00 hdr 00 (II) PCI: 00:07:0: chip 10b9,1533 card , rev c3 class 06,01,00 hdr 00 (II) PCI: 00:0a:0: chip 1274,1371 card 1274,1371 rev 08 class 04,01,00 hdr 00 (II) PCI: 00:0f:0: chip 10b9,5229 card , rev c1 class 01,01,8a hdr 00 (II) PCI: 01:00:0: chip 10de,0110 card 1043,4015 rev a1 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x08 (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xd700 - 0xd7ff (0x100) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xdff0 - 0xe7ff (0x810) MX[B] (II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(1:0:0) NVidia GeForce2 MX/MX 400 rev 161, Mem @ 0xd700/24, 0xe000/27, BIOS @ 0xdfff/16 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0x000f - 0x000f (0x1) MX[B] [3] -1 0x000c - 0x000e (0x3) MX[B] [4] -1 0x - 0x0009 (0xa) MX[B] [5] -1 0x - 0x (0x1) IX[B] [6] -1 0x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0xd800 - 0xdbff (0x400) MX[B] [1] -1 0xdfff - 0xdfff (0x1) MX[B](B) [2] -1 0xe000 - 0xe7ff
Re: [XFree86] [XFree86(TM) Bug Report] VMware and video drivers
On Wed, 5 Mar 2003, ken anderson wrote: I used the vmware_drv.o but i had to download it with Windows XP. it was my understanding that the bin sometimes get messed up this way. It would be nice if you could place a copy on your servers. possibly renamed. Right click and select download, that might work. -Peter Why should George W. Bush care what the American people think? After all they did not vote for him. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Speedo and the Radeon 7000
Bill Kristjanson wrote: Jesse Hutton wrote: I don't make the Speedo fonts available to X and I have no problems. It sounds like you're having trouble loading the Speedo module for some reason (I have no idea why a hardware upgrade would cause that, except for the fact that you may be using a new driver), which is used for serving up Speedo fonts to the X server. Try commenting it out in the Module section of your XF86Config-4 file if you don't mind not using these fonts, and you may as well comment out the speedo fontpath if you do that. Otherwise, you'll have to figure out why this modules isn't loading properly. Jesse On Tue, 4 Mar 2003, Bill Kristjanson wrote: I have installed a Radeon 7000 PCI in my Phoebe-3 (RH 8.0.94) system. After the upgrade of the card X refused to start. My system would lock and required the three-finger-salute. Through experimentation I have established that the problem occurs when X tries to load Speedo. I understand that speedo is a font backend. My questions are: Is speedo the new method of rendering fonts or the outgoing method? Does anyone know of a work-around to get it running? Is having no speedo fonts even something I should worry about? TIA Bill ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 Done... So all I miss with not having speedo is some fonts? I can live with that. Thanks, Bill ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 Does anyone know if this is a common problem with speedo and the radeon 7000 or am I just lucky? Bill ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Logs
Dear XFree86 Team, After running XFree86 -configure on my system, I recieved the following message: Fatal server error: XFree86 has found a valid card configuration. Unfortunately the appropriate data has not been added to xf86PciInfo.h. Please forward 'scanpci -v' output to XFree86 support team. When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] Therefore, as instructed, I'm sending all the information requested. Also, I think it might be usefull to say that the system I am running the X server in is a Intel P4, with 256 Mb Ram, with GNU/Linux Slackware 8.1. If required, I can offer restricted SSH access to the machine. If there is ANYTHING else I could do for you please let me know. I am a Pascal/Delphi/Kylix programmer with some Linux skills. I have some C/C++ skill, but not very much. Yours, Gianni Wed Jan 29 16:29:36 2003 569 10.1.1.13 13099008 /home/gdb/COMPLABR2Sheila.GDB b _ o a [EMAIL PROTECTED] ftp 1 * i Wed Jan 29 20:49:24 2003 13909 10.1.1.13 344928256 /home/gdb/COMPLABR2Sheila.GDB b _ o a [EMAIL PROTECTED] ftp 1 * c Tue Feb 4 13:10:35 2003 207 10.1.1.13 344928256 /home/gdb/COMPLABR2Maringa.GDB b _ o a [EMAIL PROTECTED] ftp 1 * c XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18 i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Mar 5 17:19:14 2003 (--) using VT number 2 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (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.2.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (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.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2560 card 8086,2560 rev 01 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2562 card 8086,4c59 rev 01 class 03,00,00 hdr 00 (II) PCI: 00:1d:0: chip 8086,24c2 card 8086,4c59 rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 8086,4c59 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 8086,4c59 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 8086,4c59 rev 01 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 81 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24c0 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24cb card 8086,4c59 rev 01 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 8086,4c59 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24c5 card 8086,0302 rev 01 class 04,01,00 hdr 00 (II) PCI: 01:03:0: chip 10b7,9200 card 10b7,1000 rev 78 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0xd000 - 0xd0ff (0x100) IX[B] [1] -1 0xd400 - 0xd4ff (0x100) IX[B] [2] -1 0xd800 - 0xd8ff (0x100) IX[B] [3] -1 0xdc00 -
Re: [XFree86] [XFree86(TM) Bug Report] Cannot open x-window after the installation of redhat 8.0 connection graphic
Hey, why should you apologize, feel free...! By the way Andrew might well be right: may be that just comes from upgrading from RH 7.x to RH 8.0 and keeping some of the config files... Cheers Lionel --- Oisin C. Feeley [EMAIL PROTECTED] wrote: On Tue, 4 Mar 2003, Lionel Lecoq wrote: --- Oisin C. Feeley [EMAIL PROTECTED] wrote: On Tue, 4 Mar 2003, Assad wrote: Regarding: Cannot open x-window after the installation of redhat 8.0 connection graphic XFree86 Version: Linux 2.4.18-11 smp i686 OS: Red Hat Linux 8.0 Server: XF86_S3 How can this be? XF86_S3 is one of the separate servers that existed before XFree86-4.x.x which is what shipped with Red Hat 8.0, so I don't see how that can be your server. Try reconfiguring with redhat-config-xfree86. Read the RELEASE-NOTES and all the relevant Red Hat supplied documentation. This is not the first time this thing with XF86_S3 is mentioned within RH 8.0 problems, I believe it even appeared in the XF86Config of one of the people concerned. Which is why I did not answer the mail (I would have said the same thing as Oisin)... Has RH renamed something? Is there still an X 3.3.6 lurking in the background as with RH 7.x? Lionel I too seem to recall seeing this before on the list Lionel and it baffled me then as it does now. I suspect that the OP is either not using Red Hat 8.0 or else that they've added or deleted XFree86 components from the out-of-the-box install. If I do a search for documentation on this on my Red Hat 8.0 installation I find the following: [ofeeley]$ less /usr/share/doc/redhat-release-8.0/RELEASE-NOTES-i386 Legacy XFree86 3.3.6 video hardware support has now been removed from the distribution and is no longer supported. XFree86 4.2.0 is now the only X server shipped with Red Hat Linux. It then goes on to say that if there is no XFree86 4.x driver available _or_ it doesn't work properly it tries to use VESA. Failing that it tries to use VGA. So, I have no idea how the OP got this error message. (p.s. I changed your message to be included as a bottom-post-reply and shortened the line-wrap length Lionel because I find it easier to see that way. Apologies if that seems high-handed). Oisin Feeley ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] encoding ascii-0
With 4.3.0, when creating the fonts.scale (and in in turn fonts.dir) file with mkfontscale, I don't get any listings for ascii-0. For a number of banner fonts I have, that's the only encoding. I figured perhaps I'm still expected to use the old ttmkfdir, so I used that to make both files. The fonts are now available, however I notice a warning whenever an ascii-0 encoding is selected. (FreeType: couldn't find encoding ascii-0) I don't know much about fonts, so I'm not sure what all that means. But I have noticed that mozilla is no longer able to underline hyperlinks when a TrueType font is being used. Perhaps this is a mozilla issue, but I'm unable to try Konquerer as KDE is unable to display any text of any kind. I've compiled 4.3 a couple of times, once with the builtin freetype, and once built against a separate install of freetype 2.1.3. Both times yield the same results. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: Red hat v8.0 Binaries Coming?
On Tue, 4 Mar 2003, Kevin Brosius wrote: Hopefully Mike won't scream to loud: 4.3.0 RPM packages for Red Hat Linux: ftp://people.redhat.com/mharris/testing/unstable/XFree86 Hote that these 4.3.0 RPM packages are compiled against our Red Hat Linux (Phoebe) beta 3, and not against Red Hat Linux 8.0. The packages require Phoebe in order to install and run. Brave users who are capable of determining other package dependancies on their own, and resolving them from rebuilt rawhide packages, can attempt to rebuild my XFree86 src.rpm themselves on Red Hat Linux 8.0, after first compiling and installing the required build dependancies. Users attempting this will also have to either run the rawhide kernel to use DRI 3D acceleration, or will have to compile the 4.3.0 DRM source code manually themselves for their running kernel. This is not a task for the faint of heart, so be forewarned. ;o) I'm not personally able to provide assistance to users requiring help recompiling X, or DRM kernel modules, but I can provide the following tips 1) IRC is a horrible place to try and get help for compiling kernel modules, because the people who likely can possibly help, are tired of doing it 50 times a day and generally do not respond as they aren't interested in answering this complex frequently asked question - so freenode isn't the best place for help. I speak from experience on this one (of the other side of the fence), so trust me. ;o) 2) The DRI website contains tonnes of documentation. Please read it thoroughly if you plan on compiling DRM yourself and haven't ever done so in this manner before 3) This mailing list, and dri-users may be able to provide answers to help questions the DRI website's documentation doesn't cover clearly. I just thought I would mention these things to hopefully save some people some time from hunting in the wrong places. ;o) It happens a lot. ;o) Take care, TTYL -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Myrtle Beach Info
Title: Myrtle Beach Info We'd like to invite you to visit our site built for Myrtle Beach residents and vacationers. Click here to drop by. Myrtle Beach MarketWeb Shopper
[XFree86] [XFree86(TM) Bug Report] Radeon 8500 failing with xf86cfg (send my info on scanpci -v request)
Regarding: Radeon 8500 failing with xf86cfg (send my info on scanpci -v request) Email: [EMAIL PROTECTED] XFree86 Version: 4.2.1 OS: FreeBSD 4.8 RC Area: Xserver Server: Other, specify below Server: Radeon Video Card: ATI Radeon 8500 pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4c66 ATI Device unknown CardVendor 0x1019 card 0xb732 (Card unknown) STATUS0x02b0 COMMAND 0x0283 CLASS 0x03 0x00 0x00 REVISION 0x01 BIST 0x00 HEADER 0x00 LATENCY 0x42 CACHE 0x04 BASE0 0xf008 addr 0xf000 MEM PREFETCHABLE BASE1 0x9001 addr 0x9000 I/O BASE2 0xe810 addr 0xe810 MEM MAX_LAT 0x00 MIN_GNT 0x08 INT_PIN 0x01 INT_LINE 0x05 Description: none Repeat By: This problem arises just in the begining of the configuration doind xf86cfg. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] RedHat-8.0/ViewSonic/Intel 815 problem
I am having a configuation problem in the context of RedHat-8.0 (3.2-7) Linux installation with a ViewSonic P815 using Intel 815 video card (4M video RAM w/i810 driver) - and kernel 2.4.18-26.8.0. I have attached the /etc/X11/XF86Config file for your inspection. I am presently unable to get a resolution finer than 1024x768. (I had originally been able to do so.) I played around with the dispaly settings in the hope of removing a very annoying squiggle occuring throughout the screen, but most noticeably in the top half of the sceen. Now I can neither restore my previous resolution of 1280x960 nor remove the sqiggle. I did not have this problem when I was running RH-7.3 (same screen different computer). I also share the ViewSonic P815 with a W2K machine. using a KVM, that does not have this problem either. Thank you for any help you can spare. -- Jesse Burkhardt [EMAIL PROTECTED] (w) 617-876-5680 [EMAIL PROTECTED](h) 617-354-5523 __ __ / / / / /__ /_ //-./__/_ _ /_ __// / \//__//__/_ / __/ / # File generated by anaconda. Section ServerLayout Identifier Anaconda Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceMouse1 SendCoreEvents InputDeviceKeyboard0 CoreKeyboard EndSection 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. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath /usr/X11R6/lib/X11/rgb FontPath unix/:7100 EndSection Section Module Load dbe Load extmod Load fbdevhw Load dri Load glx Load record Load freetype Load type1 EndSection Section InputDevice # Option AutoRepeat500 5 # when using XQUEUE, comment out the above line, and uncomment the # following line # Option Protocol Xqueue # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option Xleds 1 2 3 # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option XkbModel pc102 # If you have a US Microsoft Natural keyboard, you can use: # Option XkbModel microsoft # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option XkbLayout de # or: # Option XkbLayout de # Option XkbVariantnodeadkeys # # If you'd like to switch the positions of your capslock and # control keys, use: # Option XkbOptionsctrl:swapcaps #Option XkbOptions Identifier Keyboard0 Driver keyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us#Option XkbVariant EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/psaux Option ZAxisMapping 4 5 Option Emulate3Buttons yes EndSection Section InputDevice Identifier Mouse1 Driver mouse Option Device /dev/input/mice Option Protocol IMPS/2 Option Emulate3Buttons no Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameViewSonic P815 HorizSync30.0 - 115.0 VertRefresh 50.0 - 160.0 Option dpms EndSection Section Device # no known options #BusID Identifier Intel 815 Driver i810 VendorName Intel 815 BoardName Intel 815 VideoRam4096 EndSection Section Screen Identifier Screen0 Device Intel 815 MonitorMonitor0 DefaultDepth 24 SubSection Display Depth 16 Modes1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes1024x768 800x600 640x480 EndSubSection EndSection Section DRI Mode 0666 EndSection
Re: [XFree86] NeoMagic MagicMedia 256AV patched for Xv / still notenough
Florent CHANTRET wrote: Hi there, I've a Sony VAIO laptop (Celeron 366 Mhz, 192 Mo SDRAM) with a NeoMagic both for audio and video. I've installed XFree 2.4.99 on my Mandrake 9 in order to have the Xv patch. If I set the option OverlayMem to the value of about 80 (don't remember but the correct value for NTSC fullscreen DVD watching), I've a green line at the bottom of my screen and a scratchy sound. I've maximised this value and no problem for the green line / sound but it still not perfect. On Xine, there is a lot of slowdown and hiccups in the sound, and it's better on mplayer or videolan. But, I think I lost a lot of frames resulting in lines appearing on fast move on the screen. Is there a way to have a perfect display for DVD on such a system (poor CPU not so powerful and a shared audio / video neomagic card). Just a precision, the sound is managed by OSS. Regards, Florent CHANTRET FWIW, I just managed to get perfect DVD playback on my Vaio PCG-Z505HE (PIII 450MHz, 192M RAM, NeoMagic 256AV), but I don't exactly know what fixed it. My guess is that either the kernel framebuffer driver or the directfb driver initialized something on the card that the XFree86 driver doesn't. Previously the slowdown was due to writes to overlay memory in NEOCopyYV12Data() in the neomagic driver (cvs from early Dec); I'd get about 19 fps. What changed is that I tried using /dev/fb0 and directfb, and then afterward tried running mplayer and ogle using the xv driver, and voila! Perfect playback, full frame rates (24 fps), and about 20% idle CPU leftover. You may not get perfect playback on a 366 MHz machine, but if you're affected by this slowdown, you'd at least get better framerates. BTW, one more thing that's different about my setup than yours is that since I don't have a DVD drive for the laptop, I'm nfs-mounting the DVD drive from my desktop. So perhaps somebody with some neomagic clue (Egbert?) might be able to figure out what fixed it. Matt ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Server Crash on start
Your server is too old (2 and a half years). Upgrade. 4.3 is the most recent server. On Wed, 5 Mar 2003, Chief Penguin wrote: [...] (EE) No devices detected. MArk. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] All apps that link to libGL segfault in XFree86 4.3
Hello, I just upgraded XFree86 to version 4.3, and I've found that any application that links to libGL.so.1 now immediately crashes with a segmentation fault. I tried running the affected applications (which include glxinfo, glxgears, any KDE application) with LIBGL_DEBUG=verbose, and they all output the same thing: libGL: XF86DRIGetClientDriverName: 4.0.1 radeon (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/radeon_dri.so Segmentation fault When I run the applications through gdb, I get output like the following (below I ran glxinfo): Starting program: /usr/X11R6/bin/glxinfo (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... name of display: :0.0 libGL: XF86DRIGetClientDriverName: 4.0.1 radeon (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/radeon_dri.so (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x4000926b in _dl_relocate_object () from /lib/ld-linux.so.2 I don't know what this means. I'm sure I have the right version of libGL; I have only one copy of it and it's the one that was installed by XFree86 4.3 (/usr/lib/opengl/xfree/lib/libGL.so.1.2). I noticed that this is only a problem when DRI is enabled. If I disable DRI, then the apps run normally, but with very slow OpenGL rendering. Anyone have a clue as to what's going on? Thanks a lot, Paul Hoepfner-Homme ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] installation of X on Redhat Linux 8.0
Title: installation of X on Redhat Linux 8.0 Has anyone installed 4.3 on Redhat? If so can they explain (privately if needs be) how/what was needed to get this compiled. thanks in advance. Nissan Motor Co. (Australia) Pty. Ltd. Attention: This e-mail message is privileged and confidential. If you are not the intended recipient you must not disclose or use the informationcontained in it. If you have received this email messagein error please delete it and notify the sender by return email.The content of this message does not necessarily represent the viewsof Nissan Motor Co. (Australia) Pty Ltd.
Re: [XFree86] All apps that link to libGL segfault in XFree86 4.3
Update: Well, I managed to fix the problem. I checked out XFree86 from CVS built it, then I copied the newly built radeon_dri.so file and copied it over my existing one. Then with DRI enabled I tried running an OpenGL program again, and it worked! Lucky guess, it seems. I don't suppose anyone has an idea why the radeon_dri.so file was broken in the first place...? I'm positive the original one was what was installed when I installed XFree86 4.3 from the package. (I'm using Gentoo, so XFree86 was compiled for me automatically.) No worries, though. I'm glad it works! Cheers, Paul On March 5, 2003 23:06, o3jsr8001-at-sneakemail.com |Xpert/1.0-Allow| wrote: Hello, I just upgraded XFree86 to version 4.3, and I've found that any application that links to libGL.so.1 now immediately crashes with a segmentation fault. I tried running the affected applications (which include glxinfo, glxgears, any KDE application) with LIBGL_DEBUG=verbose, and they all output the same thing: libGL: XF86DRIGetClientDriverName: 4.0.1 radeon (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/radeon_dri.so Segmentation fault When I run the applications through gdb, I get output like the following (below I ran glxinfo): Starting program: /usr/X11R6/bin/glxinfo (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... name of display: :0.0 libGL: XF86DRIGetClientDriverName: 4.0.1 radeon (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/radeon_dri.so (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x4000926b in _dl_relocate_object () from /lib/ld-linux.so.2 I don't know what this means. I'm sure I have the right version of libGL; I have only one copy of it and it's the one that was installed by XFree86 4.3 (/usr/lib/opengl/xfree/lib/libGL.so.1.2). I noticed that this is only a problem when DRI is enabled. If I disable DRI, then the apps run normally, but with very slow OpenGL rendering. Anyone have a clue as to what's going on? Thanks a lot, Paul Hoepfner-Homme ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] glx extensions with nv driver problems
Hi, I have been running X without glx entensions for the longest time because of this problem, but now I need to have it working. I'm running this on a FreeBSD 5.0 machine with GeForce2 card. The problem is when I uncomment the glx line, the server core dumps and tells me: Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! I have no idea how to fix this? I don't remember if I compiled X from ports or grabbed it from packages. I'm posting my XF86Config file and the log file below. Thanks in advance Section ServerLayout Identifier Layout0 Screen 0 Screen0 0 0 InputDeviceKeyboard0 CoreKeyboard InputDeviceMouse0 CorePointer EndSection Section Files #FontPath /usr/X11R6/share/AbiSuite/fonts EndSection Section Module Load xie Load pex5 Load dri Load dbe Load glx Load record Load extmod Load type1 EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Keyboard0 Driver keyboard Option XkbModel pc101 Option XkbLayout us EndSection Section Monitor Identifier Monitor0 HorizSync30.0 - 107.0 VertRefresh 50.0 - 150.0 EndSection #Section Device #Identifier Card0 #Driver nv #ChipSet GeForce2 GTS/Pro #CardNVidia GeForce2 GTS/Pro #EndSection Section Device Identifier Card0 Driver nv #Driver nvidia ChipSet GeForce2 GTS/Pro #ChipSet GeForce2 GTS CardNVidia GeForce2 GTS/Pro #BusID PCI:1:0:0 #Option NvAGP 2 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Depth 24 Modes1600x1200 1280x1024 1280x960 1152x864 1024x768 800x600 640x480 EndSubSection EndSection XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 5.0-RELEASE i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Thu Mar 6 00:08:11 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Layout0 (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Keyboard0 (**) Option XkbModel pc101 (**) XKB: model: pc101 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Mouse0 (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on freebsd (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (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.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1039,0735 card , rev 01 class 06,00,00 hdr 80 (II) PCI: 00:01:0: chip 1039,0001 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 1039,0008 card , rev 00 class 06,01,00 hdr 80 (II) PCI: 00:02:2: chip 1039,7001 card 1019,0a14 rev 07 class 0c,03,10 hdr 00 (II) PCI: 00:02:3: chip 1039,7001 card 1019,0a14 rev 07 class 0c,03,10 hdr 00 (II) PCI: 00:02:5: chip 1039,5513 card 1039,5513 rev d0 class 01,01,80 hdr 80 (II) PCI: 00:03:0: chip 1039,0900 card 1019,0a14 rev 90 class 02,00,00 hdr 00 (II) PCI: 00:0d:0: chip 9005,0010 card 9005,a180 rev 00 class 01,00,00
[XFree86] x window-device error-help to correct it
sir, when i type X in Mandrake Linux 8.1 system, i get the following error from xfree86.log please help me to correct it. XFree86 Version 4.1.0 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.8-5mdkenterprise i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Thu Mar 6 10:25:38 2003 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout layout1 (**) |--Screen screen1 (0) (**) | |--Monitor monitor1 (**) | |--Device Intel 810 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 250 30 (**) 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/:-1 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (**) Option AllowMouseOpenFail (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (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.1.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (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.1.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000fd0c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7120 card 8086,7120 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7121 card 8086,0200 rev 03 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2415 card 11d4,4352 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:0d:0: chip 1039,0204 card 1039,0204 rev 21 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.1.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0a (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0xc000 - 0xcfff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0xefd0 - 0xefdf (0x10) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xe730 - 0xe7bf (0x90) MX[B] (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI: (0:1:0) Intel i810 rev 3, Mem @ 0xe800/26, 0xeff8/19 (--) PCI:*(1:13:0) SiS 82C204 rev 33, Mem @ 0xe780/22, 0xefdf/16, I/O @ 0xcc00/7, BIOS @ 0xefde/15 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0x000f - 0x000f (0x1) MX[B] [3] -1 0x000c - 0x000e (0x3) MX[B] [4] -1 0x - 0x0009 (0xa) MX[B] [5] -1 0x - 0x (0x1) IX[B] [6] -1 0x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0xefde - 0xefde7fff (0x8000) MX[B](B) [1] -1 0xefdf -
[XFree86] where is 4.3.0 for linux?
Still can't find binaries for Linux-ix86-glibc22. When will it be available? Thanks, Jeff [ [EMAIL PROTECTED] ] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] glx extensions with nv driver problems
On Thu, 6 Mar 2003, Kevin Kuo wrote: Hi, I have been running X without glx entensions for the longest time because of this problem, but now I need to have it working. I'm running this on a FreeBSD 5.0 machine with GeForce2 card. The problem is when I uncomment the glx line, the server core dumps and tells me: Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! I have no idea how to fix this? I don't remember if I compiled X from ports or grabbed it from packages. Your modules are mixed. You are using the glx from NVIDIA's binary distribution but the nv driver that came with XFree86. If you want to run the nv driver remove NVIDIA's /usr/X11R6/lib/modules/extensions/libglx.so. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Can no longer set keyboard repeat rate (since 4.3.0)
Hi, After upgrading to XFree86 4.3.0, my keyboard autorepeat rate has changed. It is too slow and I would like to return it to its original default setting (delay 500ms, repeat 30ms). I made no changes to XF86Config, although I never entered any keyboard autorepeat values in there anyway (I just used the default). So I assume it's the default settings that have changed. I tried adding the line Option AutoRepeat 500 30 to the keyboard device section of XF86Config, but the rate apparently hasn't changed. XF86Config.0.log shows that the server reads the new option from the config file, but the autorepeat rate is still the same (too slow). So I tried changing it using xset. But that doesn't work either. When I run xset r 30, it makes no difference to the rate. So I studied the help for xset a bit and tried using the other syntax, xset r delay rate. So I did xset r 500 30, and it gave me this error message, followed by the usage message: xset: unknown option 500 This really confuses me. Not only does xset not set my keyboard repeat rate, but it also doesn't understand the option syntax as shown in its own usage message. There are no suspicious messages in XF86Config.0.log, other than the line (II) Keyboard Keyboard0 handled by legacy driver but from what I understand, this message is normal. Anyone else have trouble setting the repeat rate in 4.3.0? Thanks, Paul Hoepfner-Homme ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] where is 4.3.0 for linux?
On Thu, Mar 06, 2003 at 01:31:33PM +0800, Jeff Chua wrote: Still can't find binaries for Linux-ix86-glibc22. When will it be available? AFAIK binaries are in updates for most distributions. -- Free Software - find interesting programs and change them NetHack - meet interesting creatures, kill them and eat their bodies Usenet - meet interesting people from all over the world and flame them Decopter - unrealistic helicopter simulator, get it from http://decopter.sf.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
