Re: [XFree86] Getting the list of X client from X server.
The server doesn't know this information. To the server, the client is just an anonymous listener on the other end of a socket. You can find out how many clients there are using the XResource extension (example at http://www.xfree86.org/~mvojkovi/restest.c), but other than how many clients and what resources (pixmaps, fonts, etc...) they are using, there's not much else you can learn from the server. Mark. On Fri, 15 Dec 2006, Seongsu Lee wrote: Hello, I want to get the list of X client which is currently connected to the X server. I will modify the X server if it is needed. What I want to do is to write out the list of X client. (If possible, I want to save details of each X client. For example, PID of the X client, IP of the X client and so on.) I think there can be a data structure to keep the list of X client in the X server. If it is, I want to know what it is. Please help me to find out the way to get the list of X client in the X server. Thank you very much. -- Seongsu's blog - http://www.senux.com/ Never make any mistaeks. (Anonymous, in a mail discussion about to a kernel bug report.) ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xconfiguration Problem : xf86OpenConsole: Cannot open /dev/atc0
I don't know anything about lynxos but, apparently, the server is expecting that it can open /dev/atc0 to get access to the console. You apparently don't have /dev/atc0. So that either means you need /dev/atc0 in order to run XFree86 or if there is some other way to access the console on lynxos, you need a version of XFree86 that knows how to access it (I don't know if such a version exists or not). If this were Linux, I'd say you just forgot to compile your kernel with console and virtual terminal support. I have no experience with Lynxos, however, so I don't know if this is the same problem. Mark. On Fri, 15 Dec 2006, bheemappa wrote: Hello, Am using lynxos 4.0.0 for powerpc sbc board, after i installed xfree86 4.3.0 when,I try to configure the X server with configuration command its giving an Fatal server error. If any one knows the solution plese tel me reply to this id : [EMAIL PROTECTED] Below is the detailed log. # LOG Start Here # # XFree86 _XSERVTransSocketCreateListener: failed to bind listener _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: failed to create listener for tcp XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: LynxOS 4.0.0 PowerPC (LynuxWorks, Inc.) Build Date: 16 December 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. 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: /usr/adm/XFree86.8.log, Time: Sat Nov 29 16:05:30 2003 Fatal server error: xf86OpenConsole: Cannot open /dev/atc0 (No such device or address ) 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 /usr/adm/XFree86.8.log. Please report problems to [EMAIL PROTECTED] Failed to run X -configure. ### Log Ends here # Reagards Bheema ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xserver crash, i810
Were the GLX or DRI modules loaded in this case? I still suspect a DRI or GLX bug, mostly because I haven't seen this with NVIDIA drivers which don't use the XFree86 dri or glx modules. Mark. On Sun, 29 Oct 2006, jayjwa wrote: Here's the same type crash as was happening with the S3 VirgeDX chipset, only this time on i810. No mention of glx module, but it was loaded. Two different machines, same XFree86, 4.6.0. Both crashes only happen if X is left running for over a day or so, then shut down. Once the server closes, the console is never restored. This crash didn't produce a log, only the follow when I got hold of the console back using svgalib's restoretextmode util. *** glibc detected *** X: double free or corruption (!prev): 0x08d30de8 *** waiting for X server to shut down === Backtrace: = /lib/libc.so.6[0xb7df4cf3] /lib/libc.so.6(cfree+0x90)[0xb7df81b0] X(FreeGC+0x61)[0x80cf8b1] X(FreeScratchGC+0x3f)[0x80cf90f] [0xb79a9e85] [0xb79ae41c] [0xb7b97229] [0xb7b98341] X(FreeClientResources+0x6b)[0x80d406b] X(FreeAllResources+0x4a)[0x80d413a] X(main+0x439)[0x80d2899] /lib/libc.so.6(__libc_start_main+0xd8)[0xb7da2f38] X[0x806f101] === Memory map: -000a rwxs 00:07 98305 /SYSV0002 (deleted) 000a-000c rwxs 000a 03:01 556569 /dev/mem 000c-000f rwxs 000c 03:01 556569 /dev/mem 000f-0010 r-xs 000f 03:01 556569 /dev/mem 08048000-081d3000 r-xp 03:01 2193636/usr/X11R6/bin/XFree86 081d3000-08206000 rwxp 0018a000 03:01 2193636/usr/X11R6/bin/XFree86 08206000-097e5000 rwxp 08206000 00:00 0 [heap] af50-af521000 rwxp af50 00:00 0 af521000-af60 ---p af521000 00:00 0 af689000-af734000 rwxp af689000 00:00 0 af734000-af76d000 rwxp af76d000 00:00 0 af7a4000-af7b4000 rwxs 000a 03:01 556569 /dev/mem af7b4000-b77b4000 rwxs f000 03:01 556569 /dev/mem b77b4000-b77f rwxp b77b4000 00:00 0 b77f-b787 rwxs ffa8 03:01 556569 /dev/mem b787-b791 rwxs 00:07 98305 /SYSV0002 (deleted) b791-b7d8d000 rwxp b791 00:00 0 b7d8d000-b7ecb000 r-xp 03:01 654805 /lib/libc-2.5.so b7ecb000-b7ecd000 r-xp 0013e000 03:01 654805 /lib/libc-2.5.so b7ecd000-b7ece000 rwxp 0014 03:01 654805 /lib/libc-2.5.so b7ece000-b7ed1000 rwxp b7ece000 00:00 0 b7ed1000-b7edb000 r-xp 03:01 1669573/usr/lib/libgcc_s.so.1 b7edb000-b7edc000 rwxp 9000 03:01 1669573/usr/lib/libgcc_s.so.1 b7edc000-b7ede000 r-xp 03:01 654813 /lib/libdl-2.5.so b7ede000-b7edf000 r-xp 1000 03:01 654813 /lib/libdl-2.5.so b7edf000-b7ee rwxp 2000 03:01 654813 /lib/libdl-2.5.so b7ee-b7f05000 r-xp 03:01 654811 /lib/libm-2.5.so b7f05000-b7f06000 r-xp 00024000 03:01 654811 /lib/libm-2.5.so b7f06000-b7f07000 rwxp 00025000 03:01 654811 /lib/libm-2.5.so b7f07000-b7f19000 r-xp 03:01 1670084/usr/lib/libz.so.1.2.3 b7f19000-b7f1a000 rwxp 00012000 03:01 1670084/usr/lib/libz.so.1.2.3 b7f1a000-b7f28000 rwxp b7f1a000 00:00 0 b7f28000-b7f2c000 r-xp 03:01 8544105/lib/libsafe.so.2.0.16 b7f2c000-b7f2d000 rwxp 3000 03:01 8544105/lib/libsafe.so.2.0.16 b7f2d000-b7f2f000 rwxp b7f2d000 00:00 0 b7f2f000-b7f3 r-xp b7f2f000 00:00 0 [vdso] b7f3-b7f4c000 r-xp 03:01 654854 /lib/ld-2.5.so b7f4c000-b7f4d000 r-xp 0001b000 03:01 654854 /lib/ld-2.5.so b7f4d000-b7f4e000 rwxp 0001c000 03:01 654854 /lib/ld-2.5.so bfbf5000-bfc0a000 rwxp bfbf5000 00:00 0 [stack] Any idea what's cause both machines to crash, but only when X is up for quite some time before shutting down? The S3 crash happened the same way, but mentions GL/glx module. This happened priviously on the i810 as well, but I had no output to send in as I couldn't re-claim the console and had to reboot. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Building XFree86 3.3.6 using gcc3.3.5
I recommend XFree86 4.6.0. We don't support 3.x servers anymore and, from looking at the neomagic driver code, it looks like it was ported from XFree86 3.x back in '98/'99 and there have been bug fixes as recent at 2004. Mark. On Thu, 26 Oct 2006, Tinow ME wrote: Thanks for your reply. My old laptop has a Neogeo 128XD chip which I find it's supported by xfree86 4.x, and it has a CPU of pity pentium mmx 300, ram of 160M, I am afraid it has not the capacity to run the lastest version of xfree86 acceptably, because my graphic card does not support AGP. Could you give me an advice that which version of xfree86 should I install? Tinow ME On 10/26/06, Mark Vojkovich [EMAIL PROTECTED] wrote: It may be that XFree86 3.3.6 isn't expected to compile with 2.6 kernels. We officially dropped support for XFree86 3.x versions some number of years ago and I know we did have to add some 2.6 kernel specific stuff to the XFree86 4.x servers. XFree86 3.x isn't necessarily any lighter than XFree86 4.x servers. The only reason for considering a 3.x server would be for old graphics adaptors which aren't well-supported in 4.x. Which graphics adaptor do you have? If it's well-supported in 4.x you're better off with 4.x. Mark. On Wed, 25 Oct 2006, Tinow ME wrote: Hello, everybody.I have an old laptop so I decided to compile install xfree86 3.3.6 CVS on Debian 3.1 with kernel 2.6.17.13. After make World world.log I find there is a error message in world.log, it appears: == In file included from fbdev.c:54: /usr/include/stdlib.h:748: error: syntax error before int make[6]: *** [ fbdev.o ] Error 1 and I find in stdlib.h: ... line747: /* Return the absolute value of X. */ line748: extern int abs (int __x) __THROW __attribute__ ((__const__)); line749: extern long int labs (long int __x) __THROW __attribute__ ((__const__)); line750: __END_NAMESPACE_STD ... Anyone help? Best Regards, Tinow ME ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Building XFree86 3.3.6 using gcc3.3.5
It may be that XFree86 3.3.6 isn't expected to compile with 2.6 kernels. We officially dropped support for XFree86 3.x versions some number of years ago and I know we did have to add some 2.6 kernel specific stuff to the XFree86 4.x servers. XFree86 3.x isn't necessarily any lighter than XFree86 4.x servers. The only reason for considering a 3.x server would be for old graphics adaptors which aren't well-supported in 4.x. Which graphics adaptor do you have? If it's well-supported in 4.x you're better off with 4.x. Mark. On Wed, 25 Oct 2006, Tinow ME wrote: Hello, everybody.I have an old laptop so I decided to compile install xfree86 3.3.6 CVS on Debian 3.1 with kernel 2.6.17.13. After make World world.log I find there is a error message in world.log, it appears: == In file included from fbdev.c:54: /usr/include/stdlib.h:748: error: syntax error before int make[6]: *** [ fbdev.o ] Error 1 and I find in stdlib.h: ... line747: /* Return the absolute value of X. */ line748: extern int abs (int __x) __THROW __attribute__ ((__const__)); line749: extern long int labs (long int __x) __THROW __attribute__ ((__const__)); line750: __END_NAMESPACE_STD ... Anyone help? Best Regards, Tinow ME ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XServer Crash
On Mon, 16 Oct 2006, jayjwa wrote: On Mon, 16 Oct 2006, Mark Vojkovich wrote: -It looks like a problem related to OpenGL. My guess is this - happened when cleaning up resources for an OpenGL app (like the - screen saver) during shutdown. Does killing the screensaver while - the server is running produce the same problem? When this happened last night, I had X running for hours, probably about 10. When I exitted is when the crash happened. After that I was able to reproduce it by just starting X and then right away exiting out. There was never a screen saver running (other than the default X11 one that will come on after a bit), such as xscreensaver or xlock, and I exitted all apps before terminating the window manager, which was at the time Blackbox. When I reproduced it last night I used also Mwm, and Twm, both with users and root user. -To my knowledge the S3 driver doesn't support accelerated - 3D graphics. Perhaps it doesn't happen if you don't load the - dri module? I cut the DRI module and it still produced the same results. Now today, I can't reproduce this at all (but I didn't let it run a long time, such as the 10 hours yesterday). Does omitting the glx module help? Perhaps the trace (which implies a segfault in __MESA_destroyBuffer unless I'm reading that incorrectly) is misleading and it would crash somewhere else if that module wasn't loaded. A new trace without the glx module might be enlightening. Mark. - Caught signal 11. - Stack trace: -0: 0x808db0d: 0x808daf0 xf86ShowStackTrace + 0x1d - Module /usr/X11R6/bin/XFree86 -1: 0x808dbd3: 0x808db70 xf86SigHandler + 0x63 - Module /usr/X11R6/bin/XFree86 -2: 0xb7ee4420: 0xb7ee4420 __kernel_sigreturn + 0x0 - Module -3: 0xb79a541c: 0xb79a53f0 __MESA_destroyBuffer + 0x2c - Module /usr/X11R6/lib/modules/extensions/libGLcore.a:xf86glx.o - Section .text -4: 0xb7b8e229: 0xb7b8e1f0 __glXDestroyDrawablePrivate + 0x39 - Module /usr/X11R6/lib/modules/extensions/libglx.a:glxutil.o - Section .text -5: 0xb7b8f341: 0xb7b8f2e0 DrawableGone + 0x61 - Module /usr/X11R6/lib/modules/extensions/libglx.a:glxscreens.o - Section .text -6: 0x80d406b: 0x80d4000 FreeClientResources + 0x6b - Module /usr/X11R6/bin/XFree86 -7: 0x80d413a: 0x80d40f0 FreeAllResources + 0x4a - Module /usr/X11R6/bin/XFree86 -8: 0x80d2899: 0x80d2460 main + 0x439 - Module /usr/X11R6/bin/XFree86 - - Fatal server error: - Server aborting What was running? Only some terminals, and I think Firefox, the first time. After this, during the tests to reproduce this, only the window manager. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XServer Crash
It looks like a problem related to OpenGL. My guess is this happened when cleaning up resources for an OpenGL app (like the screen saver) during shutdown. Does killing the screensaver while the server is running produce the same problem? To my knowledge the S3 driver doesn't support accelerated 3D graphics. Perhaps it doesn't happen if you don't load the dri module? Mark. On Mon, 16 Oct 2006, jayjwa wrote: This just started this morning, but I don't use this machine as much so prehaps this may be due to a kernel upgrade? Exiting X results in the screen locking, black, with just the pointer where I left it. The command line is still usable, but the only way to get the display back is a full reboot. I caught the logfile this time, looks like X starts to crash and then doesn't restore the text mode: XFree86 Version 4.6.0 Release Date: 10 May 2006 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.15-1.2054_FC5 i686 [ELF] Current Operating System: Linux atr2 2.6.18 #1 Wed Sep 27 04:13:25 EDT 2006 i686 Build Date: 6 May 2006 Changelog Date: 10 May 2006 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Command line: X :0 -nolisten inet6 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (EE) error, (WW) warning, (II) informational, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Oct 16 01:03:12 2006 (==) Using config file: /etc/X11/XF86Config. (II) Executable is /usr/X11R6/bin/XFree86. (II) Reading symbols from /usr/X11R6/bin/XFree86. (II) Module ABI versions: XFree86 ANSI C Emulation: 0.3 XFree86 Video Driver: 0.10 XFree86 XInput driver : 0.5 XFree86 Server Extension : 0.4 XFree86 Font Renderer : 0.5 (II) Loader running on linux (==) Keyboard: CustomKeycode disabled. (==) ServerLayout Complex Layout (==) |--Screen Screen 1 (0) (0, 0) (**) | |--Device S3 ViRGE (**) | |--Monitor CrystalScan (0) (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) FontPath set to /usr/X11R6/lib/X11/fonts/local,/usr/X11R6/lib/X11/fonts/CID,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/cyrillic/,/usr/share/fonts (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules,/lib/modules/current/kernel/drivers/char/drm (**) Option Xinerama (**) Option AllowDeactivateGrabs true (**) Option AllowClosedownGrabs true (**) Xinerama: enabled. (II) Checking for unused ServerFlags options: (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.6.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.10 (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.6.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.5 (II) Loading font Bitmap (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000983c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1237 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:07:0: chip 8086,7000 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7010 card , rev 00 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7020 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:0b:0: chip 105a,4d33 card , rev 01 class 01,04,00 hdr 00 (II) PCI: 00:0f:0: chip 1317,0985 card 1317,0574 rev 11 class 02,00,00 hdr 00 (II) PCI: 00:11:0: chip 5333,8a01 card 10b4,1717 rev 01 class 03,00,00 hdr 00 (II) PCI: 00:13:0: chip 8086,1040 card 8086,1000 rev 00 class 07,80,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:17:0) S3 Inc. ViRGE/DX or /GX rev 1, Mem @ 0xf800/26 (WW) Open ACPI failed (/proc/acpi/event) (No such file or directory) (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Addressable bus resource ranges are [0] -1 0
Re: [XFree86] options/modules/extensions
On Sun, 24 Sep 2006, Chad Kline wrote: QUESTIONS: 1. how can i find out what options/modules/extensions are of benefit? 2. is there a practical way, or a XFree86 plan to decrease the amount of memory XFree86 uses? (62MB!) The server is not using 62 Meg. Many OSes do not report actual system memory usage but the sum of virtual mappings, which include things like the graphic card's mapped framebuffer. Also, remember that client resources (like pixmaps) reside on the server. When Firefox starts up and your server grows by some number of megabytes, that is due to Firefox instructing the server to allocate piles and piles of pixmaps. It's not the server's fault that the applications are hogs, but it shows up in the server's memory space never-the-less. As for modules and extensions, I wouldn't worry about it. They generally don't take up much memory and all of them are needed by some app or the other. You can remove them almost arbitrarily, but then some apps stop working or start working strangely when particular extensions are missing. There are too many apps for us to keep track of what-apps-use-which-extensions. If you want to remove extensions, it's your problem to figure out which extensions your apps need. If you want to see which clients are requesting resources, you can run this app: http://www.xfree86.org/~mvojkovi/restest.c Be careful running it though. You should redirect the output, eg.: restest output.txt because it grabs the server and without the redirection away from stdout, it can cause a race condition with some terminal programs trying to print the stdout. This app uses the X-Resource extension so you don't want to omit loading that one. I notice on my machine that my web browser is using 778 pixmaps totaling over 50 Meg. Mark. there should be a good description of modules/extensions for XFree86. every module/extension should be listed somewhere #1, and #2, each option/module/extension should describe what it is useful for, and when, if ever, it is critical. and it should be explanatory enough for the average non-Xwindow techie to comprehend and find useful. the man pages just say to look in /usr/X11R6/lib/... but that isn't very helpful. it shouldn't be so difficult to figure out what to include and what to exclude. it should be made very clear so anyone with half a brain can figure out what they need or don't need. i've been using UNIX type systems for a dozen years or more, and to this day, i still find that all the good of UNIX type systems is dragged down by days/weeks of trial-and-error type hacking to figure out things that should take an hour or two of reading. i mean, sure, hacking things out is fun, but so is being efficient and productive :) for example, what do these things mean? how do i know if they are useful to me or not? do i have to search out each thing for hours in Google to get a vague notion of each thing? this isn't a complete list of all options/extensions/modules, but the point is, these things should be described well enough for someone to know if they are necessary by a user. otherwise, having options/extensions/modules is semi-pointless. Option omit BIG-REQUESTS Option omit DPMS Option omit Extended-Visual-Information Option omit FontCache # Option omit MIT-SCREEN-SAVER Option omit MIT-SUNDRY-NONSTANDARD Option omit SYNC Option omit TOG-CUP Option omit X-Resource Option omit XC-MISC Option omit XFree86-DGA Option omit XFree86-Misc # Option omit XFree86-VidModeExtension # Option omit XVideo # Option omit XVideo-MotionCompensation _ The next generation of Search?say hello! http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-usFORM=WLMTAG ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] options/modules/extensions
On Sun, 24 Sep 2006, Marc Aurele La France wrote: On Sun, 24 Sep 2006, Mark Vojkovich wrote: If you want to see which clients are requesting resources, you can run this app: http://www.xfree86.org/~mvojkovi/restest.c We should commit that. All it needs is a proper copyright notice. It's dangerous, which is why it isn't in the tree. It either needs to not grab the server or it shouldn't dump to stdout while it's grabbed. If you don't grab, the app might crash if resources disappear while it's running. If you print out stuff while grabbed, the terminal and app may deadlock when the terminal tries to display the stdout. Mark. Be careful running it though. You should redirect the output, eg.: restest output.txt because it grabs the server and without the redirection away from stdout, it can cause a race condition with some terminal programs trying to print the stdout. This app uses the X-Resource extension so you don't want to omit loading that one. I notice on my machine that my web browser is using 778 pixmaps totaling over 50 Meg. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and| fax:1-780-492-1729 | |Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +---+ | University of Alberta | | | Edmonton, Alberta | Standard disclaimers apply| | T6G 2H1 | | | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel?
On Mon, 11 Sep 2006, cckuo wrote: HI: After reading the HOWTO file, would you please help me to clarify some questions about the meaning of the parameters that XAA pass to me? (To minimize the difference, suppose all the flags I used below are HARDWARE_PATTERN_SCREEN_ORIGIN | HARDWARE_PATTERN_PROGRAMMED_BITS 1. What is the unit of (x,y) that pass by Subsequent function, bytes or pixels? Since I have seen (0x312, 0x812) in hex pass to driver while my resolution is (0x400, 0x300) in hex, that is (1024x768)? The XAA interface is always in pixels. If (0x312, 0x812) is the (x,y) then this is rendering offscreen to an offscreen pixmap or to the pixmap cache. 2. Does HARDWARE_PATTERN_SCREEN_ORIGIN means the all the value of (x,y) that pass subsequently are relative to upper-left corner of my on-screen memory, that is, if on-screen is located from the physical memory, 0xd000, and (x,y) is (0x10, 0), the destination address that HW should put the pattern on after ropping is 0xd020, assuming the (x,y) is in pixel unit and the screen depth is 16bpp. Is that right ? All x,y coordinates are relative to the upper-left of the on-screen memory in ALL cases. HARDWARE_PATTERN_SCREEN_ORIGIN refers to the source pattern alignment. It means the phase of the 8x8 pattern should be specified relative to the screen origin. Without that option it is relative to the origin of the rectangle being drawn. We are passing an 8x8 pattern to the hardware. If you want the first pixel in the pattern to correspond to the first pixel of the rectangle being drawn, then you do NOT want HARDWARE_PATTERN_SCREEN_ORIGIN to be set. Most hardware actually need the pattern specified relative to the origin of the surface being drawn on not the origin of the rectangle being drawn. At typical rendering case is where XAA needs to fill a large area with an 8x8 pattern but the destination is clipped by various occluding windows so the area ends up being filled with lots of smaller operations. If the pattern is specified relative to the destination surface then the pattern only needs to be specified once. If the pattern needs to be specified relative to each individual rectangle, then XAA needs to realign the 8x8 pattern for each rectangle. That is what happens when HARDWARE_PATTERN_SCREEN_ORIGIN is not set. A new realigned pattern is passed to the driver for every Subsequent call. Mark. Thanks for your help. cckuo The fail_pattern.jpg looks like the driver incorrectly sets the HARDWARE_PATTERN_SCREEN_ORIGIN flag. See section 2.6 of xc/programs/Xserver/hw/xfree86/xaa/XAA.HOWTO Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel?
The fail_pattern.jpg looks like the driver incorrectly sets the HARDWARE_PATTERN_SCREEN_ORIGIN flag. See section 2.6 of xc/programs/Xserver/hw/xfree86/xaa/XAA.HOWTO Mark. On Mon, 28 Aug 2006, cckuo wrote: Sorry for late replying this letter. The option XaaNoMono8x8PatternFillRect did solve my problem, and I have my HW colleague to download the pattern as the attach file,fail_pattern.jpg, that XAA pass to me by infoPtr-SetupForMono8x8PatternFill, the call back function I register during XAA initialization. As you can see the black two 't' in fail_pattern.jpg is quite similar to the bug I mention in Debian3.1.jpg (You can flip the black 't' vertically and compare it with the start button in Debian3.1.jpg). According to this pattern simulation, the text looks like already dirty before passing to the driver. If it really is, the bug will also happen when I set the option, XaaNoMono8x8PatternFillRect. Right now I am trying to patch the XFree4.3.01 to 4.3.0.2 by 4.3.0.1-4.3.0.2.diff.gz, the file I download from ftp://ftp.xfree86.org/pub/XFree86/4.3.0/fixes/ I type gzip -d 4.3.0.1-4.3.0.2.diff.gz |patch -p0 -E, but it says it cannot find the file to patch in line 5. Below are the messages I occur, can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: xc/config/cf/Imake.tmpl |diff -u xc/config/cf/Imake.tmpl:3.139 xc/config/cf/Imake.tmpl:3.139.2.1 |--- xc/config/cf/Imake.tmpl:3.139 Tue Jan 28 17:06:08 2003 |+++ xc/config/cf/Imake.tmplSun Feb 8 20:58:52 2004 -- File to patch: Did I use the wrong command or I need to download some other file to finish the patch? Meanwhile, If it is not the HW bug, what is the next proper step I should do to clarify this bug, tracing the application, rdesktop, or some component in XFree86? Appreciate your help very much. Sincerely Yours, cckuo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Vojkovich Sent: Monday, August 07, 2006 2:37 AM To: cckuo Cc: xfree86@XFree86.Org Subject: RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel? On Sun, 6 Aug 2006, cckuo wrote: Thanks for your help. I closed all the CPUToScreenColorExpand I report to XAA. But the text is still blurred, so I mark the callback functions one by one and the text become clear until unmarked the 8x8 mono pattern fill. Does that mean the application like remotedesktop can have different choice to draw the text on the screen? There are a lot of ways that text can be drawn. Does Option XaaNoMono8x8PatternFillRect also solve your problem? If so, it sounds like the 8x8 pattern fill hardware isn't working correctly, or as expected in this case. By the way, would you please tell me what the card is in the POSTed State mean? Is that a state I can read from somewhere else or some procedure the driver have to follow? By POST (Power On Self Test, I think), I mean the state into which the VBIOS put the card. In the presence of a kernel framebuffer device it's not valid to assume that the card is in the same state that the VBIOS initialized. The kernel framebuffer driver may have changed some things since the VBIOS initialized the card. Often, graphics drivers don't full initialize the card because they assume that the VBIOS would have done some of the basic initializations already. Did you try without a kernel framebuffer device? Mark. Appreciate your help very much, cckuo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Vojkovich Sent: Saturday, August 05, 2006 12:53 AM To: cckuo Cc: xfree86@XFree86.Org Subject: RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel? On Fri, 4 Aug 2006, cckuo wrote: Thanks for your reply. I rmmod the fb module and try again, and I found the text blur still occur. I will rebuild a new kernel without fb inside and try it again. By the way, I think I may give wrong description about #3. The disappear I mean in #3 is the text blur will not happen while using xinit' to activate Xserver. And I don't mean the whole screen will disappear. I am sorry about that. I also done some test about decreasing the size of memory I pass to xf86InitFBManager function call. The text blur will be normal when the size is below 4Mb. I know this size control the number of different slots created by XAAInitPixmapCache. Since the driver didn't report any HW accelerations about characters, I guess the text part of the picture may be taken as some pixmaps and call HW bitblt function to move it from offscreen to onscreen. If my assumption is correct, would you please tell me what functions in XAA take charge
Re: [XFree86] X server crashes
It's probably XFree86 driver instability. Most likey due to misunderstood hardware subtleties or hardware bugs that have not been worked around. You should really get some newer software. Your X-server is more than three years old and there have undoubtedly been many bug fixes since then. Mark. On Fri, 18 Aug 2006, Nobody NA wrote: hi I got X-server crashes (time-to-time) (see attachment). System: Notebook Toshiba Celeron 2.4 GGz, 256 RAM Some memory used as video memory (see log - stolen memory). Looks like wrong detection of available memory - but who is guilty - X-server or kernel (driver)?? If any additional information needed - I will send it With respect, Stanislav -- ___ Play 100s of games for FREE! http://games.mail.com/ ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86]How to modify my screen depth.
The server has a -depth option. Eg: startx -- -depth 24 See the XFree86 man page for other options. Mark. On Wed, 16 Aug 2006, gnos yhh wrote: Hello, My X-server works well without xfree86.conf, my XFree86.0.log: ... Unable to locate/open config file. ... How to set my screen default depth ,but I won't use xf86config to set it. Thank's in advance Will ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 800x600 is not displayed full-screen on 1024x768 tft in Xfree86-4.5.0
These appear to be controlled by the LcdCenter and NoStretch options documented in the chips man page. The man page suggests that scaling is on by default, but looking at the driver code, I see a lot of conditions where the driver must disable this. It looks like maybe this doesn't work in conjunction with the overlay or hardware cursor, and it looks like there are some suspend-related complications. It could be that new features enabled by default cause this to be disabled. Was there something printed out in the XFree86.0.log file that suggested why scaling wasn't used? You could try playing with the options mentioned in the man page. Mark. On Thu, 10 Aug 2006, PAVEL TKATCHOUK wrote: Hello, I have ct69000 on motherboard. On XFree86-3.3.6 I'd set CMOS to 1024x768 and XF86Config (see below) to 800x600 and have X running full-screen from which I assume driver senses resolution difference and sets videochip to scale automatically. But on XFree86-4.5.0 with the same CMOS and XF86Config-4 resolutions I have 800x600 window at the center of the 1024x768 panel surrounded by black frame, no auto scaling. So how would I turn scaling on? Thank you, Pavel. # XF86Config.3.3.6.800x600 snip # ** # Monitor section # ** Section Monitor Identifier Generic Monitor VendorName Unknown ModelName Unknown HorizSync 24.05-44.15 VertRefresh 51.03-60 Modeline 800x600 36 800 824 896 1024 600 601 603 625 EndSection # ** # Graphics device section # ** Section Device Identifier Generic VGA VendorName Unknown BoardName Unknown Chipset generic EndSection Section Device Identifier Generic SVGA VendorName Unknown BoardName Unknown TextClockFreq 22.11 EndSection # ** # Screen sections # ** # The colour SVGA server Section Screen Driver svga Device Generic SVGA Monitor Generic Monitor DefaultColorDepth 24 Subsection Display Depth 24 Modes 800x600 ViewPort 0 0 EndSubsection EndSection - # XFree86-4_4.5.0.800x600x24 Section ServerLayout Identifier Default Layout Screen 0 Screen0 0 0 InputDevice Mouse0 CorePointer InputDevice Keyboard0 CoreKeyboard InputDevice TouchScreen SendCoreEvents EndSection Section Files snip EndSection Section Module snip EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/psaux EndSection Section InputDevice Identifier TouchScreen snip EndSection Section Monitor Identifier Monitor0 VendorName Sharp ModelName LCD HorizSync 24.0 - 61.0 VertRefresh 55.0 - 76.0 Option dpms EndSection Section Device Identifier Videocard0 Driver vesa VendorName Unknown BoardName Unknown EndSection Section Screen Identifier Screen0 Device Videocard0 Monitor Monitor0 DefaultDepth 24 SubSection Display Depth 24 Modes 800x600 #1024x768 EndSubSection EndSection Section ServerFlags AllowMouseOpenFail EndSection Section DRI Group 0 Mode 0666 EndSection ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel?
On Sun, 6 Aug 2006, cckuo wrote: Thanks for your help. I closed all the CPUToScreenColorExpand I report to XAA. But the text is still blurred, so I mark the callback functions one by one and the text become clear until unmarked the 8x8 mono pattern fill. Does that mean the application like remotedesktop can have different choice to draw the text on the screen? There are a lot of ways that text can be drawn. Does Option XaaNoMono8x8PatternFillRect also solve your problem? If so, it sounds like the 8x8 pattern fill hardware isn't working correctly, or as expected in this case. By the way, would you please tell me what the card is in the POSTed State mean? Is that a state I can read from somewhere else or some procedure the driver have to follow? By POST (Power On Self Test, I think), I mean the state into which the VBIOS put the card. In the presence of a kernel framebuffer device it's not valid to assume that the card is in the same state that the VBIOS initialized. The kernel framebuffer driver may have changed some things since the VBIOS initialized the card. Often, graphics drivers don't full initialize the card because they assume that the VBIOS would have done some of the basic initializations already. Did you try without a kernel framebuffer device? Mark. Appreciate your help very much, cckuo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Vojkovich Sent: Saturday, August 05, 2006 12:53 AM To: cckuo Cc: xfree86@XFree86.Org Subject: RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel? On Fri, 4 Aug 2006, cckuo wrote: Thanks for your reply. I rmmod the fb module and try again, and I found the text blur still occur. I will rebuild a new kernel without fb inside and try it again. By the way, I think I may give wrong description about #3. The disappear I mean in #3 is the text blur will not happen while using xinit' to activate Xserver. And I don't mean the whole screen will disappear. I am sorry about that. I also done some test about decreasing the size of memory I pass to xf86InitFBManager function call. The text blur will be normal when the size is below 4Mb. I know this size control the number of different slots created by XAAInitPixmapCache. Since the driver didn't report any HW accelerations about characters, I guess the text part of the picture may be taken as some pixmaps and call HW bitblt function to move it from offscreen to onscreen. If my assumption is correct, would you please tell me what functions in XAA take charge of text such that I can trace the command made by that function to check whether the content of offscreen pixmaps are already wrong or the HW blur it during bitblt. Most simple text is rendered with the CPUToScreenColorExpand functions. Anti-aliased text or some other text used by the RENDER extension is rendered with the CPUToScreenAlphaTexture or CPUToScreenTexture functions. Mark. Thanks for your help very much, cckuo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Vojkovich Sent: Friday, August 04, 2006 1:12 AM To: cckuo Cc: xfree86@XFree86.Org Subject: RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel? Most likely, part of the offscreen video memory that the driver told XAA it could use for pixmap caching is not accessible so things placed there disappear. The order in which things are started determines the packing order of offscreen pixmaps so that's why #3 changes which things disappear. Most likely it is an interaction with a kernel framebuffer device. Namely, the kernel framebuffer device is setting some graphics card state that prevents all the videoram from being accessible and the XFree86 driver is unaware of this. This is unlikely to be an XAA issue. If the XFree86 driver is assuming the card is in the POSTed state, that may be a bad assumption in light of a kernel framebuffer device. You might want to check what the kernel framebuffer device is doing with regards to video memory partitions, etc... Mark. On Thu, 3 Aug 2006, cckuo wrote: Sorry for late replying your email. The situation is attached as the picture and we use the rdesktop, a remote connect tool to control English Server 2003, the text part will be broken. 1. After setting the option XaaNoOffscreenPixmaps or XaaNoScreenToScreenCopy I can't reproduce the problem. I know these two option will let the XAA determine whether it can call the call back functions that driver registered in the beginning. 2. If I reduce the memory size reported to FBmanager, less than 4Mb, it will also disappear. I know this behavior will let
RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel?
On Fri, 4 Aug 2006, cckuo wrote: Thanks for your reply. I rmmod the fb module and try again, and I found the text blur still occur. I will rebuild a new kernel without fb inside and try it again. By the way, I think I may give wrong description about #3. The disappear I mean in #3 is the text blur will not happen while using xinit' to activate Xserver. And I don't mean the whole screen will disappear. I am sorry about that. I also done some test about decreasing the size of memory I pass to xf86InitFBManager function call. The text blur will be normal when the size is below 4Mb. I know this size control the number of different slots created by XAAInitPixmapCache. Since the driver didn't report any HW accelerations about characters, I guess the text part of the picture may be taken as some pixmaps and call HW bitblt function to move it from offscreen to onscreen. If my assumption is correct, would you please tell me what functions in XAA take charge of text such that I can trace the command made by that function to check whether the content of offscreen pixmaps are already wrong or the HW blur it during bitblt. Most simple text is rendered with the CPUToScreenColorExpand functions. Anti-aliased text or some other text used by the RENDER extension is rendered with the CPUToScreenAlphaTexture or CPUToScreenTexture functions. Mark. Thanks for your help very much, cckuo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Vojkovich Sent: Friday, August 04, 2006 1:12 AM To: cckuo Cc: xfree86@XFree86.Org Subject: RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel? Most likely, part of the offscreen video memory that the driver told XAA it could use for pixmap caching is not accessible so things placed there disappear. The order in which things are started determines the packing order of offscreen pixmaps so that's why #3 changes which things disappear. Most likely it is an interaction with a kernel framebuffer device. Namely, the kernel framebuffer device is setting some graphics card state that prevents all the videoram from being accessible and the XFree86 driver is unaware of this. This is unlikely to be an XAA issue. If the XFree86 driver is assuming the card is in the POSTed state, that may be a bad assumption in light of a kernel framebuffer device. You might want to check what the kernel framebuffer device is doing with regards to video memory partitions, etc... Mark. On Thu, 3 Aug 2006, cckuo wrote: Sorry for late replying your email. The situation is attached as the picture and we use the rdesktop, a remote connect tool to control English Server 2003, the text part will be broken. 1. After setting the option XaaNoOffscreenPixmaps or XaaNoScreenToScreenCopy I can't reproduce the problem. I know these two option will let the XAA determine whether it can call the call back functions that driver registered in the beginning. 2. If I reduce the memory size reported to FBmanager, less than 4Mb, it will also disappear. I know this behavior will let the XAA generate less big slots. 3. if I use xinit instead of windows manager to activate the Xserver, execute rdesktop in xterm. It will disappear. 4. So far it only happens on the English Server 2003, and English XP is OK. 5. use kernel 2.4.X it will disappear, but kernel 2.6.X will fail. I am right now studying the source codes to realize the relationships between 1 and 2. But I really confuse why the 3, 4 and 5 will happen. I am not quite sure whether it was a bug of XAA, the windows manager or even the driver's fault. But from 3, I guess it may not driver's fault. If you have any opinions about this bug, please let me know. Appreciate your help in advance. Sincerely Yours, cckuo To: cckuo Cc: xfree86@XFree86.Org Subject: Re: [XFree86] Will the behaviors of XFree86 be effected by different kernel? I wouldn't expect the behavior of an XFree86 graphics driver to change with a kernel except for, perhaps, something related to 3D using the DRI. I suppose it's also possible that a kernel framebuffer device could interfere with an xfree86 driver in some way. The XFree86 sis driver has a NoAccel option you can use to force software rendering. If there is still rendering corruption with that option, that would suggest that it's not a driver acceleration problem. Mark. cckuo wrote: Dear X friends: Recently I play the rdesktop, a software like XP remote desktop, on XFree86 4.3.0. And the text will get blur only when I use Kernel 2.6.15.1 but it will disappear when I change to kernel 2.4.27. Since the accelerator in the XFree4.3.0 is XAA, are there some acceleration
RE: [XFree86] Will the behaviors of XFree86 be effected by different kernel?
Most likely, part of the offscreen video memory that the driver told XAA it could use for pixmap caching is not accessible so things placed there disappear. The order in which things are started determines the packing order of offscreen pixmaps so that's why #3 changes which things disappear. Most likely it is an interaction with a kernel framebuffer device. Namely, the kernel framebuffer device is setting some graphics card state that prevents all the videoram from being accessible and the XFree86 driver is unaware of this. This is unlikely to be an XAA issue. If the XFree86 driver is assuming the card is in the POSTed state, that may be a bad assumption in light of a kernel framebuffer device. You might want to check what the kernel framebuffer device is doing with regards to video memory partitions, etc... Mark. On Thu, 3 Aug 2006, cckuo wrote: Sorry for late replying your email. The situation is attached as the picture and we use the rdesktop, a remote connect tool to control English Server 2003, the text part will be broken. 1. After setting the option XaaNoOffscreenPixmaps or XaaNoScreenToScreenCopy I can't reproduce the problem. I know these two option will let the XAA determine whether it can call the call back functions that driver registered in the beginning. 2. If I reduce the memory size reported to FBmanager, less than 4Mb, it will also disappear. I know this behavior will let the XAA generate less big slots. 3. if I use xinit instead of windows manager to activate the Xserver, execute rdesktop in xterm. It will disappear. 4. So far it only happens on the English Server 2003, and English XP is OK. 5. use kernel 2.4.X it will disappear, but kernel 2.6.X will fail. I am right now studying the source codes to realize the relationships between 1 and 2. But I really confuse why the 3, 4 and 5 will happen. I am not quite sure whether it was a bug of XAA, the windows manager or even the driver's fault. But from 3, I guess it may not driver's fault. If you have any opinions about this bug, please let me know. Appreciate your help in advance. Sincerely Yours, cckuo -Original Message- From: Mark Vojkovich [mailto:[EMAIL PROTECTED] Sent: Thursday, July 27, 2006 1:13 AM To: cckuo Cc: xfree86@XFree86.Org Subject: Re: [XFree86] Will the behaviors of XFree86 be effected by different kernel? I wouldn't expect the behavior of an XFree86 graphics driver to change with a kernel except for, perhaps, something related to 3D using the DRI. I suppose it's also possible that a kernel framebuffer device could interfere with an xfree86 driver in some way. The XFree86 sis driver has a NoAccel option you can use to force software rendering. If there is still rendering corruption with that option, that would suggest that it's not a driver acceleration problem. Mark. On Wed, 26 Jul 2006, cckuo wrote: Dear X friends: Recently I play the rdesktop, a software like XP remote desktop, on XFree86 4.3.0. And the text will get blur only when I use Kernel 2.6.15.1 but it will disappear when I change to kernel 2.4.27. Since the accelerator in the XFree4.3.0 is XAA, are there some acceleration in XAA will be effected by the kernel? Ps: My platform is sis741. Appreciate your help in advance. Sincerely Yours, cckuo ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree86 intallation
Old kernel versions shouldn't be a problem. Your biggest concern is that you get an XFree86 version compatible with your libc. You can run the Xinstall.sh script (see the Install instructions that come with XFree86) to tell you which binaries you should be using. You generally want to run the most recent XFree86 version (4.6.0). http://www.xfree86.org/4.6.0/Install.html ftp://ftp.xfree86.org/pub/XFree86/4.6.0/binaries/ Mark. On Thu, 3 Aug 2006, [ISO-8859-1] Javier Gonz?lez wrote: Dear Friends, I'm begginer linux user and I need graphic mode (X-Windows) for program at 2.2.1x kernel and I have the SiS315 that is suported by the Xfree86 4.1 (I see this in Internet) Could I install the Xfree86 4.1 or later in a RedHat 6.2 or in a linux with kernel 2.2.x ? ThankYou, Javier. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: could not open default font
The could not open default font 'fixed' is almost always because some distribution configured XFree86 to get all fonts from a font server (no other FontPaths in the XF86Config) yet failed to keep the font server (xfs) running. Mark. On Thu, 27 Jul 2006, Alfred Hovdestad wrote: Does XFree use the xfs daemon? Is xfs running? Alfred Hovdestad Alan Coopersmith wrote: First step: figure out if you are using Xorg or XFree86. They are not the same and are built configured a bit differently. (If you're using xorg.conf as stated earlier, you can't be using XFree86, but now you stated XF86Config-4 and remaking XFree86.) could not open default font 'fixed' means the font path set in your config file does not contain a font with the name or alias of fixed - that's included in both the XFree86 XOrg fonts, so if you've done a full install of either, then you need to find where the fonts were installed and verify your config file lists that path. -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering cckuo wrote: I have checked the font path I set in my XF86Config-4 and it seems point to the right place. I also remake and reinstall my XFree on my machine and the error message is still there. Does could not open default font 'fixed' means there is a font package's name with fixed on it and I need to download it to the fontpath? Thanks a lot ! cckuo ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Will the behaviors of XFree86 be effected by different kernel?
I wouldn't expect the behavior of an XFree86 graphics driver to change with a kernel except for, perhaps, something related to 3D using the DRI. I suppose it's also possible that a kernel framebuffer device could interfere with an xfree86 driver in some way. The XFree86 sis driver has a NoAccel option you can use to force software rendering. If there is still rendering corruption with that option, that would suggest that it's not a driver acceleration problem. Mark. On Wed, 26 Jul 2006, cckuo wrote: Dear X friends: Recently I play the rdesktop, a software like XP remote desktop, on XFree86 4.3.0. And the text will get blur only when I use Kernel 2.6.15.1 but it will disappear when I change to kernel 2.4.27. Since the accelerator in the XFree4.3.0 is XAA, are there some acceleration in XAA will be effected by the kernel? Ps: My platform is sis741. Appreciate your help in advance. Sincerely Yours, cckuo ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] LCD flicker
In your Subsection Display you specified 1280x1024 for the mode. The server will usually pick the mode with the highest refresh rate out of the internal mode pool (which includes a 75 Hz Vesa mode) and the modes read from the monitor's EDID (plug and play information). In your case, however, the monitor specified a preferred mode which was 60 Hz so that mode took precedence. If you want to exclude low refresh modes then you can raise the lower limit of the VertRefresh in your Section Monitor in the XF86Config file. You have: VertRefresh 50 - 75 Changing this to: VertRefresh 70 - 75 Would exclude the monitor's plug and play preferred mode and the server's builtin 60 Hz Vesa mode and use the server's builtin 75 Hz Vesa mode. Mark. I'm not sure what you mean by flicker in the context of an LCD panel. When most people say flicker they mean a low refresh rate on a CRT. It's a low refresh rate. My eyes start to hurt when I use it even for only 10 minutes. I think it is not using 75Hz as it should. W2K on the same computer uses 75Hz without any flicker. I'd have to see the /var/log/XFree86.0.log file to look for anything unusual. http://adrianm.host.sk/XFree86.0.log Thanks a lot for your reply. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] LCD flicker
I'm not sure what you mean by flicker in the context of an LCD panel. When most people say flicker they mean a low refresh rate on a CRT. I'd have to see the /var/log/XFree86.0.log file to look for anything unusual. Mark. On Mon, 17 Jul 2006, Adrian Mrva wrote: Hello. I have a 17 LCD Eizo L568 monitor and it flickers a lot. I also use it on Windows 2000 on the same computer without problem. I'm running XFree86 4.5.0 under NetBSD 3.0. Thanks in advance. Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb ModulePath /usr/X11R6/lib/modules FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/CID/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ EndSection Section Module Load extmod Load glx Load dbe Load record Load xtrap Load type1 Load speedo EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol wsmouse Option Device /dev/wsmouse Option ZaxisMapping 4 5 EndSection Section Monitor #DisplaySize 340 270 # mm Identifier Monitor0 VendorName ENC ModelNameL568 Option DPMS HorizSync 24.8 - 80 VertRefresh 50 - 75 Modeline 1280x1024_75.00 138.54 1280 1368 1504 1728 1024 1025 1028 1069 -HSync +Vsync EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option SWcursor# [bool] #Option HWcursor# [bool] #Option NoAccel # [bool] #Option ShadowFB# [bool] #Option UseFBDev# [bool] #Option Rotate # [str] #Option VideoKey# i #Option FlatPanel # [bool] #Option FPDither# [bool] #Option CrtcNumber # i #Option FPScale # [bool] #Option FPTweak # i Identifier Card0 Driver nv VendorName nVidia Corporation BoardName NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth24 Modes 1280x1024 EndSubSection EndSection ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Configuring XF86 with GeForce 256 and NTSC TV
On Sat, 15 Jul 2006, Vladimir Dergachev wrote: On Sat, 15 Jul 2006, Mark Vojkovich wrote: As far as I know, the only way to get NVIDIA cards to work with TV-out is to use NVIDIA's binary drivers. They stopped supporting GeForce 256 recently, so you'd have to get older versions of the binary drivers. Mark. Any chance NVidia would release the source code that was removed ? I seriously doubt that. Mark. best Vladimir Dergachev On Fri, 14 Jul 2006, jim male wrote: Hello mailing list! I have an old nVidia GeForce 256 with an Svideo port and an NTSC TV that I'd like to pair. I've heard that an improperly configured X server can make a TV smoke/catch on fire/explode/die. I don't know if there is any truth in this, but I'd rather as the experts than end up in the hospitol. The TV is a Toshiba 27 TV (NTSC) Model Number 27A32. The lspci line for my GeForce 256 is :01:05.0 VGA compatible controller: nVidia Corporation NV10 [GeForce 256 SDR] (rev 10) my /etc/X11/XF86Config-4 file can be found at http://www.linuxquestions.org/questions/showthread.php?p=2334412, as I think it would be impolite to put something that long into a mailing list. Thanks to anyone who can help this n00b. -Jim PS. CC to [EMAIL PROTECTED] (removing all of the numbers) ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Configuring XF86 with GeForce 256 and NTSC TV
As far as I know, the only way to get NVIDIA cards to work with TV-out is to use NVIDIA's binary drivers. They stopped supporting GeForce 256 recently, so you'd have to get older versions of the binary drivers. Mark. On Fri, 14 Jul 2006, jim male wrote: Hello mailing list! I have an old nVidia GeForce 256 with an Svideo port and an NTSC TV that I'd like to pair. I've heard that an improperly configured X server can make a TV smoke/catch on fire/explode/die. I don't know if there is any truth in this, but I'd rather as the experts than end up in the hospitol. The TV is a Toshiba 27 TV (NTSC) Model Number 27A32. The lspci line for my GeForce 256 is :01:05.0 VGA compatible controller: nVidia Corporation NV10 [GeForce 256 SDR] (rev 10) my /etc/X11/XF86Config-4 file can be found at http://www.linuxquestions.org/questions/showthread.php?p=2334412, as I think it would be impolite to put something that long into a mailing list. Thanks to anyone who can help this n00b. -Jim PS. CC to [EMAIL PROTECTED] (removing all of the numbers) ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Disappearing mouse pointer
That would be a bug in NVIDIA's drivers. You should file a bug report with them. Mark. On Wed, 12 Jul 2006, Colin Coe wrote: Hi all Apologies if this has been asked and answered before as I've googled but not found an answer. My problem is that I'm using a dual video card setup (two Nvidia Quadro 4500) and three CRT monitors. I've setup stereo at [EMAIL PROTECTED] and all looks fine until you move the mouse pointer onto the third monitor as it disappears. Moving the mouse back to either of the first two monitors and the mouse point re-appears. In the third window when I click and drag the left mouse button I can see a rectanglar selection, so the mouse is there I just can't see it. This is a HP xw9300, 32GB RAM, two Quadro FX 4500 with a GSync card using version 1.8672 of the Nvidia Linux driver and RHEL 3u7 Workstation. XFree86 -version XFree86 Version 4.3.0 (Red Hat Enterprise Linux 3 release: 4.3.0-98.EL) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.9-22.18.bz155725.ELsmp x86_64 [ELF] Build Date: 28 November 2005 Build Host: hs20-bc1-3.build.redhat.com My XF86Config file is: --- Section ServerLayout Identifier 3_screen_stereo Screen Screen TwinView-1 0 0 Screen 1 Screen Display-2 RightOf Screen TwinView-1 InputDeviceMouse1 CorePointer InputDeviceKeyboard1 CoreKeyboard Option Stereo 3 Option Xinerama 1 EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/misc/:unscaled FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath unix/:-1 EndSection Section Module Load dbe Load glx Load extmod Load type1 Load freetype EndSection Section InputDevice Identifier Keyboard1 Driver kbd Option AutoRepeat 250 30 Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Mouse1 Driver mouse Option Protocol IMPS/2 Option Device /dev/input/mice Option Emulate3Buttons yes Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Sun21 VendorName Sun ModelNameSun 21-inch N3 HorizSync30.0 - 96.0 VertRefresh 48.0 - 160.0 Option dpms Modeline 1280x1024 211.22 1280 1376 1520 1760 1024 1025 1028 1091 -HSync +Vsync EndSection Section Device # Primary PCI-express slot Identifier NV_PCI_Express1 Driver nvidia VendorName nvidia BoardName Unknown video card BusID PCI:10:0:0 Option ModeValidation NoMaxPClkCheck, NoEdidMaxPClkCheck EndSection Section Device # 2nd PCI-express slot Identifier NV_PCI_Express2 Driver nvidia VendorName nvidia BusID PCI:129:0:0 Option ModeValidation NoMaxPClkCheck, NoEdidMaxPClkCheck EndSection Section Screen Identifier Screen TwinView-1 Device NV_PCI_Express1 MonitorSun21 DefaultDepth 24 Option Stereo 3 Option ForceStereoFlipping 1 Option TwinView Option TwinViewOrientation RightOf Option MetaModes 1280x1024 +0+0, 1280x1024 +1160+0 SubSection Display Depth 24 Modes1280x1024 EndSubSection EndSection Section Screen Identifier Screen Display-2 Device NV_PCI_Express2 MonitorSun21 DefaultDepth 24 Option Stereo 3 Option ForceStereoFlipping 1 Option MetaModes 1280x1024 +0+1160 SubSection Display Depth 24 Modes1280x1024 EndSubSection EndSection --- Any ideas? CC -- You can judge the quality of an Operating System by the amount of 3rd party software required to protect it... ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Greetings
On Sun, 2 Jul 2006, David Dawes wrote: On Sun, Jul 02, 2006 at 11:56:05AM -0700, Mark Vojkovich wrote: On Sun, 2 Jul 2006, Tariq Ismail Dalvi wrote: Hello, I m one of the subscriber of your mailing list just want to suggest that make your mailing list modrate anyone including me ll be glad to monitor it for you for the superb job you have did on XFree86. Junk advertisers are taking over XFree86 mailing list. Yes, it seems so. My preference would be it goes back to being a subscription list. Perhaps nonsubscribers could send to the list if they included a keyword like XFree86 in the subject line. I'm also inclined to change back to a subscription list, making it clear in the reply to non-subscribers that they will need to subscribe and re-post. Maybe it will work better this time. While I appreciate offers of moderation, I think it is more practical for posters to make a little effort by subscribing than to have one person wade through the held postings on a regular basis. How about a keyword in the subject line that would let non- subscribers send something to the list? Mark. David ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] my problem with dual monitor
The driver that comes with XFree86 should work. You just need a much newer XFree86 version. Mark. On Sat, 1 Jul 2006, wrote: Thanks for your help!Do I have to use Intel driver?Can I make it with other drivers?Intel says little about dual heads in its website ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] (EE) FBDEV(0): mmap fbmem: Invalid argument - MMAP is not safe for ivtv usage
My guess is that your graphics device doesn't have a mappable framebuffer, or it's mappable but not very useable because it's not linearly addressible or something like that. That's just a guess - I'm not familiar with that device. Mark. On Sun, 2 Jul 2006, Matthias Meyer wrote: Hello, I run Debian with kernel 2.6.16 and ivtv0.6, build with module-assistant. I load ivtv_fb during bootup by /etc/modules.. vdr:~# lsmod | grep ivtv ivtv_fb34212 0 ivtv 205872 1 ivtv_fb i2c_algo_bit9992 1 ivtv v4l1_compat14404 1 ivtv tveeprom 15504 1 ivtv i2c_core 22064 9 ivtv,msp3400,saa7127,saa7115,tda9887,tuner,i2c_piix4,i2c_algo_bit,tveeprom My VDR350 sit on BusID PCI:0:16:0 as lspci say: vdr:~# lspci 00:00.0 Host bridge: Intel Corp. 440BX/ZX - 82443BX/ZX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corp. 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) 00:0e.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 05) 00:0f.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08) 00:10.0 Multimedia video controller: Internext Compression Inc: Unknown device 0803 (rev 01) 00:14.0 ISA bridge: Intel Corp. 82371AB PIIX4 ISA (rev 02) 00:14.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01) 00:14.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01) 00:14.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF In /etc/X11/XF86Config-4 I configure fbdev to use as framebuffer-device Section Device Identifier Hauppauge PVR 350 iTVC15 Framebuffer Driver fbdev Option fbdev /dev/fb0 BusID PCI:0:16:0 EndSection And I get error-messages from cat /var/log/XFree86.0.log (II) LoadModule: fbdev (II) Loading /usr/X11R6/lib/modules/drivers/fbdev_drv.o (II) Module fbdev: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) LoadModule: mouse (II) FBDEV: driver for framebuffer: fbdev, afb (II) Primary Device is: PCI 01:00:0 (II) Loading sub module fbdevhw (II) LoadModule: fbdevhw (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a (II) Module fbdevhw: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 0.0.2 ABI class: XFree86 Video Driver, version 0.6 (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0x4010 - 0x401f (0x10) MX[B] [6] -1 0 0x4c00 - 0x4c000fff (0x1000) MX[B] [7] -1 0 0x4800 - 0x47ff (0x0) MX[B]O [8] -1 0 0x4000 - 0x40003fff (0x4000) MX[B](B) [9] -1 0 0x4400 - 0x47ff (0x400) MX[B](B) [10] -1 0 0x5000 - 0x53ff (0x400) MX[B](B) [11] -1 0 0x - 0x (0x1) IX[B] [12] -1 0 0x - 0x00ff (0x100) IX[B] [13] -1 0 0x2060 - 0x207f (0x20) IX[B] [14] -1 0 0x2080 - 0x208f (0x10) IX[B] [15] -1 0 0x2000 - 0x203f (0x40) IX[B] [16] -1 0 0x2040 - 0x205f (0x20) IX[B] [17] -1 0 0x1000 - 0x10ff (0x100) IX[B](B) (**) FBDEV(0): claimed PCI slot 0:16:0 (II) FBDEV(0): using /dev/fb0 (II) resource ranges after probing: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0x4010 - 0x401f (0x10) MX[B] [6] -1 0 0x4c00 - 0x4c000fff (0x1000) MX[B] [7] -1 0 0x4800 - 0x47ff (0x0) MX[B]O [8] -1 0 0x4000 - 0x40003fff (0x4000) MX[B](B) [9] -1 0 0x4400 - 0x47ff (0x400) MX[B](B) [10] -1 0 0x5000 - 0x53ff (0x400) MX[B](B) [11] 0 0 0x000a - 0x000a (0x1) MS[B] [12] 0 0 0x000b - 0x000b7fff (0x8000) MS[B] [13] 0 0 0x000b8000 - 0x000b (0x8000) MS[B] [14] -1 0 0x - 0x (0x1) IX[B] [15] -1 0 0x - 0x00ff (0x100) IX[B] [16] -1 0 0x2060 - 0x207f (0x20) IX[B] [17] -1 0 0x2080 - 0x208f (0x10) IX[B] [18] -1
Re: [XFree86] my problem with dual monitor
That error message suggests that the driver doesn't support dual head operation. Looking through the Intel driver changelog, dual-head support wasn't added to that driver until mid 2004. The XFree86 version you are using dates back to mid 2003. You should upgrade your X-server to something at least a couple years newer. Mark. On Fri, 30 Jun 2006, wrote: Sorry,I did make a mistake. The files in the mail are the correct ones. And I use intel 82852GM which supports dual monitor in several ways. Thank you so much for the reply. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Help in trident card display - reg
Please send the /var/log/XFree86.0.log file to this list. Mark. On Tue, 27 Jun 2006, Mohanraj Palanisamy wrote: Dear Sir, I am having a problem in getting display in gui mode for Trident 3DImage9850 in hardware Pentium II 350 Mhz supported machine, i tried all the ways in getting solution, Everything is ok when it goes to take gui mode iam getting blank (black) screen and machine is getting hanged or monitor light gets orange color, pls help me in this regard. Thanks Regards Mohanraj P System Manager Kongu Arts Science College Erode - 638 107. Tamil Nadu ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Screen resolution won't adjust to monitor's maximum
On Fri, 23 Jun 2006, George Langford wrote: I have one Samsung SyncMaster 712N LCD monitor serving four PC's. For the time being, let's just consider one of them, bearing in mind that on another one, running Win98SE, the monitor cheerfully displays at the maximum screen resolution (1280 by 1024) and 32 bits of color, but on this one, 1024 by 768 is the maximum that can be reached with the adjust screen resolution window in debian. The video card is nVidia GeForce Fx5200, which will support much higher screen resolution than this monitor can handle. Here's what appears to be the relevant portion of XFree86.0.log: (II) NV(0): EDID Version: 1.3 [...] (II) NV(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz [...] (II) NV(0): SyncMaster: Using hsync range of 30.00-81.00 kHz (II) NV(0): SyncMaster: Using vrefresh range of 56.00-75.00 Hz The server has built in the following 1280x1024 modes: /* 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz */ /* 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz */ /* 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz */ The 60 and 75 Hz builtin VESA modes should run fine on your monitor and should be used automatically if you've specified 1280x1024 on the Modes line in your Subsection Display of the XF86Config, provided this hasn't been overridden with an explicit Modeline of the same name (1280x1024) in the XF86Config file or you forced a virtual desktop size that was smaller. I suspect the Debian tool you used messed this up either by adding a line with the Virtual keyword or by overridding the builtin 1280x1024 modelines with one that was inappropriate for your monitor. I'd have to see the XF86Config file to be sure. Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 06/06/15 17:19:33 Log message: New chip support. New PCI IDs. Modified files: xc/programs/Xserver/hw/xfree86/drivers/nv/: nv.man nv_driver.c nv_hw.c Revision ChangesPath 1.30 +10 -12xc/programs/Xserver/hw/xfree86/drivers/nv/nv.man 1.144 +33 -3 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_driver.c 1.21 +10 -5 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_hw.c ___ Cvs-commit mailing list Cvs-commit@XFree86.Org http://XFree86.Org/mailman/listinfo/cvs-commit
Re: [XFree86] Installation Problem
That appears to be the logfile from a correctly working server. Does it fail if you run startx from the commandline? My guess is that it's not the server that's failing. Mark. On Tue, 13 Jun 2006, John Fleischauer (KI4HRG) wrote: Here it is. On 6/13/06, Mark Vojkovich [EMAIL PROTECTED] wrote: Can you send a copy of the /var/log/XFree86.0.log file? If the server is not starting, all relevant information should be in that file. Mark. On Tue, 13 Jun 2006, John Fleischauer (KI4HRG) wrote: I just finished installing XFree86 in order to comply with the requirements of Google Earth for Linux. I am running Ubuntu Linux 6.06 (Dapper Drake). After I finished installing XFree86, something was changed in GDM, and as a result, whenever I boot normally, I get an error telling me something is wrong with my X Server and it couldn't be started. It gives me an option to view the output. I'd post it here, but this is before normal boot-up, so I have no way yo take a screenshot or copy the output. Anyway, after a few seconds, the command line interface comes up. (This is when booting normally.) However, when I boot into recovery mode, it works semi-well. It boots normally all the way to the login screen. From there, it boots correctly only if I select to boot into one of the failsafe modes. I am currently using GNOME_failsafe. Basically, I need to know either how to a)revert the changes I already made, or b)correct the changes. Please let me know what to do! Thanks! ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Display glitch using new Linux on old Laptop
On Tue, 13 Jun 2006, paul womack wrote: Mark Vojkovich wrote: If you were using the neomagic driver and the rendering was wrong while the vga driver rendered correctly, that implies a HW acceleration problem with the neomagic driver. You might try using the neomagic driver with: Option noaccel in the Section Device of the XF86Config file. If that works but is slow, you can add Option ShadowFB, which should be faster. Another option would be to omit the noaccel and ShadowFB options and instead try to turn off the acceleration feature that is broken. It's not clear which feature that is so it would take some experimentation, but for starters, I'd try: Option XaaNoPixmapCache Option XaaNoOffscreenPixmaps Thanks for your hints. Sadly, my problems seem rather deep. I switched (down) to VGA driver (guessing that the chip might support it) and set 800x600 24 bit, and still had the same problem. The only setting that gave non-bugged display was VGA, 1024x768, 256 (paletted) colours! The VGA driver only supports 640x480 with 16 colors, so you can't have been running the VGA driver, which brings up the question of what you actually are running. This is a little limiting :-) So I suspect my problem is rather deep rooted. I have run Mandrake 9.0, 9.1, 9.2 and 10.1 successfully on this machine; this is the first graphics problem I've had. Any hints (as always...) gratefully accepted. The broken display snapshot you showed looked like a rendering problem (like pixmaps were blitted to the wrong place). That can't still be happening with Option noaccel or it's an application issue, not a server issue. You need to send us your /var/log/XFree86.0.log file so we can see what you're really running. Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Installation Problem
Can you send a copy of the /var/log/XFree86.0.log file? If the server is not starting, all relevant information should be in that file. Mark. On Tue, 13 Jun 2006, John Fleischauer (KI4HRG) wrote: I just finished installing XFree86 in order to comply with the requirements of Google Earth for Linux. I am running Ubuntu Linux 6.06 (Dapper Drake). After I finished installing XFree86, something was changed in GDM, and as a result, whenever I boot normally, I get an error telling me something is wrong with my X Server and it couldn't be started. It gives me an option to view the output. I'd post it here, but this is before normal boot-up, so I have no way yo take a screenshot or copy the output. Anyway, after a few seconds, the command line interface comes up. (This is when booting normally.) However, when I boot into recovery mode, it works semi-well. It boots normally all the way to the login screen. From there, it boots correctly only if I select to boot into one of the failsafe modes. I am currently using GNOME_failsafe. Basically, I need to know either how to a)revert the changes I already made, or b)correct the changes. Please let me know what to do! Thanks! -- --- [EMAIL PROTECTED] ki4hrg.com Assistant Webmaster: www.wesleywired.org A Life? Cool! Where can I download one of those from? ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Display glitch using new Linux on old Laptop
If you were using the neomagic driver and the rendering was wrong while the vga driver rendered correctly, that implies a HW acceleration problem with the neomagic driver. You might try using the neomagic driver with: Option noaccel in the Section Device of the XF86Config file. If that works but is slow, you can add Option ShadowFB, which should be faster. Another option would be to omit the noaccel and ShadowFB options and instead try to turn off the acceleration feature that is broken. It's not clear which feature that is so it would take some experimentation, but for starters, I'd try: Option XaaNoPixmapCache Option XaaNoOffscreenPixmaps Mark. On Fri, 9 Jun 2006, paul womack wrote: I recently updated (mad fool) my (old) HP Omnibook 4150 to Mandrake 2006. I cannot get the display to be sensible. For example, this is a snapshot of the gimp tool panel after start up. http://i48.photobucket.com/albums/f234/bugbear33/broken_display.png The tool icons are stacked up wrong. Other applications are putting icons outside their own window, randomly on the desktop, or other windows etc. My hardware is (apparently) a NeoMagic NM2200 multimedia chipset (aka NM256 A/V), http://www.linuxdevcenter.com/pub/a/linux/2002/09/19/linuxlaptop.html HardDrake reports this as MagicGraph 256AV The config tool presents me with a list of X servers to choose from; I am using the NeoMagic-MagicGraph option. I would welcome any information/pointers as to how to proceed. (my sound doesn't work either, but that's for another list) BugBear ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: Xfree86.0 high CPU in 1280x768
On Wed, 7 Jun 2006, Barry Scott wrote: Mark Vojkovich wrote: On Tue, 6 Jun 2006, Barry Scott wrote: I'm seeing the X process take a lot more CPU time to run any workload in 1280x768 compared to a standard VGA mode like 1280x1024. For example running a text scrolling app (lots of XCopyArea calls) I see the following CPU usage figures: 1280x1024: 6.75% 1280x768: 10.53% top shows that the X process is the only one to show a change between the two modes. With XVIDEO apps the difference is from 50% to 70% to play a movie. This happens with the i810 driver and the via driver so I don't think its a driver specific issue. I think that X is changing its behavior. I seriously doubt that. Is it possible that X has turned off it acceleration in 1280x768 mode? X doesn't have anything to do with acceleration. This is entirely a driver/HW issue. I'm surprised that XAA has nothing to do with the X core. I'd have assumed that if the driver supports a speed up then X uses it otherwise X falls back to none accelerated algorithm. But if you say its all in the driver I guess that means that both the via and the i810 driver have the same bug in them. It's not clear that it's a bug yet. What can I look at to find out what the problem is? Is your refresh rate the same in both cases? Integrated graphics have peculiar performance characteristics because the graphics hardware shares memory bandwidth with the CPU. Refresh rate is 60Hz in both cases. So I assume that its not a memory bandwidth change as you suggest. Where should I look to get some data to work on? When you did your text scrolling test, were the windows the same size? It's often the case that the CPU usage increases when the graphics speed is faster. That's because the faster graphics allows more work to get done. If it takes a certain amount of CPU to render one line of text and scroll the window, faster scrolling (because you have few lines to scroll) translates to higher CPU usage. Run some experiments on fixed size windows. x11perf -scroll500 would be an interesting test. Ideally both resolutions would have the same performance and CPU usage. If the lower resolution runs faster, which it might due to more memory bandwidth being available, then I'd expect CPU usage to increase as well. Mark. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Xfree86.0 high CPU in 1280x768
On Tue, 6 Jun 2006, Barry Scott wrote: I'm seeing the X process take a lot more CPU time to run any workload in 1280x768 compared to a standard VGA mode like 1280x1024. For example running a text scrolling app (lots of XCopyArea calls) I see the following CPU usage figures: 1280x1024: 6.75% 1280x768: 10.53% top shows that the X process is the only one to show a change between the two modes. With XVIDEO apps the difference is from 50% to 70% to play a movie. This happens with the i810 driver and the via driver so I don't think its a driver specific issue. I think that X is changing its behavior. I seriously doubt that. Is it possible that X has turned off it acceleration in 1280x768 mode? X doesn't have anything to do with acceleration. This is entirely a driver/HW issue. What can I look at to find out what the problem is? Is your refresh rate the same in both cases? Integrated graphics have peculiar performance characteristics because the graphics hardware shares memory bandwidth with the CPU. Mark. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] z/OS
Are you asking for a X-server to run on the mainframe's display hardware (if there is such a thing) or are you asking for libX11 so that the z/OS apps can display on a remote X-server? I assume you're asking for the later and I would have thought that Unix System Services would already come with libX11. If you don't already have libX11, maybe you can ask IBM where you might get it - they must know. I don't see anything in XFree86's makefiles indicating that anyone has tried to build XFree86's libX11 on z/OS. Mark. On Sat, 3 Jun 2006, Michael A. Orlando wrote: Yes, on the IBM mainframe we have a Unix box, it's called Unix System Services and works just like Unix. I am in the process of installing Oracle 10g on our mainframe, and the installation is all done form the Unix side, which requires Xwindows. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Vojkovich Sent: Saturday, June 03, 2006 4:02 PM To: Michael A. Orlando Cc: xfree86@xfree86.org Subject: Re: [XFree86] z/OS You want the X-server to run on the IBM mainframe? I didn't know those things had display hardware. Or do you mean you just want X libraries for that system so local apps can display remotely. I would have thought the OS would have come with those. Mark. On Fri, 2 Jun 2006, Michael A. Orlando wrote: Is there a version of Xwindows which will work on Unix System Services on a Z/os Platform? If so, where can I obtain the Binary or souce code? Thanks Much Michael -- KMOConsulting, Inc. Michael A. Orlando 4725 Dorsey Hall Dr. PMB A608 Ellicott City, MD. 21042 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] 410-340-6504 Office: 301-688-9844 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] z/OS
You want the X-server to run on the IBM mainframe? I didn't know those things had display hardware. Or do you mean you just want X libraries for that system so local apps can display remotely. I would have thought the OS would have come with those. Mark. On Fri, 2 Jun 2006, Michael A. Orlando wrote: Is there a version of Xwindows which will work on Unix System Services on a Z/os Platform? If so, where can I obtain the Binary or souce code? Thanks Much Michael -- KMOConsulting, Inc. Michael A. Orlando 4725 Dorsey Hall Dr. PMB A608 Ellicott City, MD. 21042 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] 410-340-6504 Office: 301-688-9844 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver H/W init delay
On Tue, 30 May 2006, Jun OKAJIMA wrote: Thank you for usuful advices. Things like getting monitor information through DDC take a long time. Also, because clocks are being set there are PLL settling times that need to be observed least you mess things up by touching the hardware before the PLLs lock. I have heard about this issue, but, in my env, doing DDC probe is very fast. It is done instantaneously. Is DDC really a cause? It may be that particular drivers have unnecessary waits here and there, but you really have to address them one by one, profiling to find the wait and then investigating whether or not it's really necessary. Then, the VESA driver of current XFree86 has unnecessary waits? If so, I will try to get rid of. But, as far as I have glanced the code, it just does call a VESA BIOS and it is all it does. So, even there are unnecessary waits, they seems to be in a BIOS code, I suppose. I have worked on systems with boot times times on the order of a few seconds but these weren't trying to access VESA bios services or probing monitors through DDC. If you remove stuff like that, the boot times will probably be dominated by IDE probing, but then you end up having to hardcode things like monitor EDIDs that the driver would usually try to probe. Well, in MACH BOOT, it is possible to hard-code IDE params, because most PCs has same param. But not possible to hard-code DDC (EDID or...) because there are so many kind of monitor. Any idea? You really just need to profile it and find where all the time is spent. If the video BIOS is doing all the initialization then it's likely that all the waiting is done there. It's undoubtedly all the monitor probing and clock setting and the associated delays and timeouts related to that. If the video card has multiple connectors it will probably be looking for devices on all connectors and trying that until it's convinced that it has found them all. Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver H/W init delay
Things like getting monitor information through DDC take a long time. Also, because clocks are being set there are PLL settling times that need to be observed least you mess things up by touching the hardware before the PLLs lock. It may be that particular drivers have unnecessary waits here and there, but you really have to address them one by one, profiling to find the wait and then investigating whether or not it's really necessary. I have worked on systems with boot times times on the order of a few seconds but these weren't trying to access VESA bios services or probing monitors through DDC. If you remove stuff like that, the boot times will probably be dominated by IDE probing, but then you end up having to hardcode things like monitor EDIDs that the driver would usually try to probe. Mark. On Mon, 29 May 2006, Jun OKAJIMA wrote: I am working on making a very fast booting technology for Linux. Check this: http://www.machboot.com/ This boots within 10sec with x48 CD-ROM. I dont intend to blow my own horn, but not so bad result, dont you? One of the bottle neck at the moment is, XFree86 driver. For example, VESA driver seems to spend several seconds for hardware initialization. Other drivers (S3 or such) also needs several seconds. My questions are: 1. This delay really comes from H/W init (or detect)? 2. If so, is there any way to reduce this delay? For example, if I hard-code all parameters about H/W to a driver, It starts faster? Especially, I have much interest in tweaking VESA driver. --- Okajima, Jun. Tokyo, Japan. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] what is the `vbe' extension?
The Vesa Bios Extension is an extension to the VGA bios. There are specifications at vesa.org. Mark. On Fri, 26 May 2006, f.l. wrote: thanks. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Fwd: Unable to boot in GUI mode
You should talk to NVIDIA about your problem as we're not in a position to support third-party drivers. That said, you don't seem to have NVIDIA's kernel module installed which are required for using the NVIDIA drivers. Mark. On Thu, 25 May 2006, dharma raj raj wrote: Note: Forwarded message attached -- Original Message -- From: Ray SN To: xfree86@xfree86.org Subject: Unable to boot in GUI mode ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Need a configuration file(XF86Config) on Redhat Linux 7.2 for Mercury Mother Board(P4PM800M7) with Via Chipset
We need to see the /var/log/XFree86.0.log file. Mark. On Mon, 22 May 2006, Vijay Bhaskar Reddy D (vijaybrd) wrote: Hello, I am facing problems installing Redhat Linux 7.2 on my assembled PC. I couldnt get GUI after installing Redhat LINUX 7.2, may be because of improper config setting. Can you please suggest me the exact device and screen sections configuration for the specifications given below, so that I can configure manually by editing XF86Config file? Video-card: S3's Savage4, VideoRAM supported is 32MB, its a built in card on Mercury Mother Board(P4PM800M7) with Via Chipset Monitor Specification: LG 17 CRT Monitor - 700E Horizontal Freq: 30 - 71 KHz Vertical Freq: 50 - 160 Hz. http://www.lgezbuy.com/productdisplay.aspx?mapid=2168modno=700E.region =28pid=2153catid=196 http://www.lgezbuy.com/productdisplay.aspx?mapid=2168modno=700E.regio n=28pid=2153catid=196 I am giving the last few lines of log file contents generated by Xserver below: . . . . . . . . . . . . . . . . . . . . . . .. . .. .. . . . . . .. (II) SAVAGE: driver (version 1.1.19) for S3 Savage chipsets: Savage4,Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, Twister,TwisterK (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (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 xfree86 xfree86 org .. ... . .. .. . . . .. .. . . .. . . .. OR you may suggest some generic settings which should work for any kind of card. Because when I can get GUI based installation screen while installation LINUX, I think I can use the same settings(used by LINUX installation process), so can you please let me know the default settings(for video card and monitor) used by LNUX installation wizard to diplay its GUI. Thanks in advance, Vijay ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] How do I get 2 displays with 2 different window managers?
It looks like you want 'twm -s -display 0:0'. From the manpage: -s This option indicates that only the default screen (as specified by -display or by the DISPLAY envi- ronment variable) should be managed. By default, twm will attempt to manage all screens on the dis- play. Mark. On Fri, 19 May 2006, Harrington, Todd wrote: Hi, Thanks for your reply. That sounds good to me. I would be happy with just getting TWM on one screen and just having the X server running on the other screen. I can get my 2 screens up when I do: # xinit -- :0 I get an X server running on the first screen with a default xterm window. I get an X server running on the second screen with NO windows. From the first screen I can run setenv DISPLAY :0.0 and setenv DISPLAY :0.1 and popup xterms on the respective displays. This is good. The problem is that when I type twm -display :0.0, twm starts up on BOTH displays! Can someone help me just start it on ONE display? Then I can pop up xterms on the second display and they will not have an window manager which is what I want. Thanks, Todd -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Vojkovich Sent: Friday, May 19, 2006 1:26 PM To: xfree86@xfree86.org Subject: Re: [XFree86] How do I get 2 displays with 2 different window managers? You cannot run two displays without having two X-servers, and two X-servers cannot display simulateously because each needs to own the VT (they will end up on separate VTs). You want one server with two screens. You should probably ask the Gnome or KDE folks. TWM observes the -display commandline option and does what you want. The fancy window managers often try to be too clever and start up on all available screens. Mark. On Thu, 18 May 2006, Harrington, Todd wrote: Hi, My goal is to be able to create two displays not screens running 2 different window managers (one will actually be just an X-server). I want to run Gnome on one display (keyboard and mouse) and just an X-Server (no keyboard and mouse) with no window manager in the other. I have tried both a single Matrox G450 Dual-Headed graphics card and two single ATI Rage Pro 8MB Cards. I will be happy to get either configuration working. I have the same results so far with both types of cards. I am running RedHat Enterprise ES 4. I configured my xorg.conf file for 2 devices, 2 screens, and 2 monitors and then I created a ServerLayout section. When I type startx Gnome starts on both displays and my keyboard and mouse control is one display. I was happy to see this. I open an xterm and do: # setenv DISPLAY :0:0 # xterm (an xterm pops up on one display) # setenv DISPLAY :0:1 # xterm (an xterm pops up on the OTHER display) So, as I understand it, the number before the . is the display number and the number after the . is the screen number. Apparently I am running two screens and not two displays. This is why I think this might be a problem.. Now I have to figure out how to start Gnome or KDE in one window and have it NOT come up in the other window (I just want an X server with no window manager in that 2nd window). I looked in XClients and saw gnome-session getting called. I had seen some documentation on the web for gnome-session that said there was a -display parameter that I could pass the display number. I did not see this in the man page for gnome-session though. Is there a display number parameter so that I can just start gnome-session one ONE display? What about for startkde? If I can specify a display number for gnome-session or startkde, I would think I have to make it so the displays are :0:0 and :1:0, not 0:1 and 0:2, is that correct? Thanks, Todd Todd Harrington Senior Systems Engineer Suntron Corporation Phone: (978) 747-2048 Fax: (978) 747-2010 [EMAIL PROTECTED] ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How do I get 2 displays with 2 different window managers?
You cannot run two displays without having two X-servers, and two X-servers cannot display simulateously because each needs to own the VT (they will end up on separate VTs). You want one server with two screens. You should probably ask the Gnome or KDE folks. TWM observes the -display commandline option and does what you want. The fancy window managers often try to be too clever and start up on all available screens. Mark. On Thu, 18 May 2006, Harrington, Todd wrote: Hi, My goal is to be able to create two displays not screens running 2 different window managers (one will actually be just an X-server). I want to run Gnome on one display (keyboard and mouse) and just an X-Server (no keyboard and mouse) with no window manager in the other. I have tried both a single Matrox G450 Dual-Headed graphics card and two single ATI Rage Pro 8MB Cards. I will be happy to get either configuration working. I have the same results so far with both types of cards. I am running RedHat Enterprise ES 4. I configured my xorg.conf file for 2 devices, 2 screens, and 2 monitors and then I created a ServerLayout section. When I type startx Gnome starts on both displays and my keyboard and mouse control is one display. I was happy to see this. I open an xterm and do: # setenv DISPLAY :0:0 # xterm (an xterm pops up on one display) # setenv DISPLAY :0:1 # xterm (an xterm pops up on the OTHER display) So, as I understand it, the number before the . is the display number and the number after the . is the screen number. Apparently I am running two screens and not two displays. This is why I think this might be a problem.. Now I have to figure out how to start Gnome or KDE in one window and have it NOT come up in the other window (I just want an X server with no window manager in that 2nd window). I looked in XClients and saw gnome-session getting called. I had seen some documentation on the web for gnome-session that said there was a -display parameter that I could pass the display number. I did not see this in the man page for gnome-session though. Is there a display number parameter so that I can just start gnome-session one ONE display? What about for startkde? If I can specify a display number for gnome-session or startkde, I would think I have to make it so the displays are :0:0 and :1:0, not 0:1 and 0:2, is that correct? Thanks, Todd Todd Harrington Senior Systems Engineer Suntron Corporation Phone: (978) 747-2048 Fax: (978) 747-2010 [EMAIL PROTECTED] ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: [XFree86] problem with x windows in init3
What do you mean you couldn't get it in init3? What error? There was no error in that logfile you attached. It showed a correctly working server. Mark. On Thu, 19 May 2006, rajesh kodali wrote: Hi, Then what might be the problem.. bcz in couldn't get x windows in init3 .. but it works as usual in ini5.. Regards, Rajesh.K On Wed, 17 May 2006 Mark Vojkovich wrote : There is no error message in this logfile. As for stopping X, usually the window mananger has a quit menu or similar. Baring that, you can always do ctrlaltbackspace to quit the server. Mark. On Tue, 16 May 2006, Rajesh Kodali wrote: I am having a problem with x windows in init 3 .. when I give startx it is giving me an error .. help me .. the log file is as follows: .. And please tell me how to stop x windows .. X Window System Version 6.8.1 Release Date: 17 September 2004 X Protocol Version 11, Revision 0, Release 6.8.1 Build Operating System: Linux 2.6.9-1.860_ELsmp i686 [ELF] Current Operating System: Linux mail.areasoftindia.com 2.6.9-5.EL #1 Wed Jan 5 19:22:18 EST 2005 i686 Build Date: 09 December 2004 Build Host: tweety.build.redhat.com Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.9-5.EL ([EMAIL PROTECTED]) (gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)) #1 Wed Jan 5 19:22:18 EST 2005 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/Xorg.0.log, Time: Wed May 17 11:15:55 2006 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=X.Org Foundation compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=X.Org Foundation compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x80fc, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0296 card 1106,0296 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:00:1: chip 1106,1296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:2: chip 1106,2296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:3: chip 1106,3296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:4: chip 1106,4296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:7: chip 1106,7296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b198 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,3106 card 1186,1405 rev 8b class 02,00,00 hdr 00 (II) PCI: 00:0f:0: chip 1106,3149 card 1462,7071 rev 80 class 01,01,8f hdr 80 (II) PCI: 00:0f:1: chip 1106,0571 card 1462,7071 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:4: chip 1106,3104 card 1462,7071 rev 86 class 0c,03,20 hdr 80 (II) PCI: 00:11:0: chip 1106,3227 card 1106,3227 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:5: chip 1106,3059 card 1462,b012 rev 60 class 04,01,00 hdr 00 (II) PCI: 00:12:0: chip 1106,3065 card 1462,7071 rev 78 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1106,7205 card 1462,7071 rev 01 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -100x
Re: [XFree86] question: font path
You probably only have one FontPath specified in the XF86Config - the unix/:7100 path which means it should get the fonts from a font server, which probably isn't running. You either need to run the font server (xfs) or add some specific font paths, eg... FontPath /usr/X11R6/lib/X11/fonts/misc:unscaled FontPath /usr/X11R6/lib/X11/fonts/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1 FontPath /usr/X11R6/lib/X11/fonts/Speedo Mark. On Thu, 18 May 2006, [gb2312] ?? wrote: I used the Redhat 9.0. I have a problem when I start the computer, I cannot start the X server. Please see the following information: I cannot start the X server (your graphical interface). It is likely that it is not set up correctly. (= =)log file:/var/log/XFree86.0.log (= =)Using config file etc/X11/XF86Config Could not init font path element unix/:7100, removing from list! Fatal server error: could not open default font 'fixed' Could you please give me some advice? Thanks a lot. Regards Zhang Shengkai [EMAIL PROTECTED] 20060518 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problem with x windows in init3
There is no error message in this logfile. As for stopping X, usually the window mananger has a quit menu or similar. Baring that, you can always do ctrlaltbackspace to quit the server. Mark. On Tue, 16 May 2006, Rajesh Kodali wrote: I am having a problem with x windows in init 3 .. when I give startx it is giving me an error .. help me .. the log file is as follows: .. And please tell me how to stop x windows .. X Window System Version 6.8.1 Release Date: 17 September 2004 X Protocol Version 11, Revision 0, Release 6.8.1 Build Operating System: Linux 2.6.9-1.860_ELsmp i686 [ELF] Current Operating System: Linux mail.areasoftindia.com 2.6.9-5.EL #1 Wed Jan 5 19:22:18 EST 2005 i686 Build Date: 09 December 2004 Build Host: tweety.build.redhat.com Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.9-5.EL ([EMAIL PROTECTED]) (gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)) #1 Wed Jan 5 19:22:18 EST 2005 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/Xorg.0.log, Time: Wed May 17 11:15:55 2006 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=X.Org Foundation compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=X.Org Foundation compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x80fc, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0296 card 1106,0296 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:00:1: chip 1106,1296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:2: chip 1106,2296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:3: chip 1106,3296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:4: chip 1106,4296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:7: chip 1106,7296 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b198 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,3106 card 1186,1405 rev 8b class 02,00,00 hdr 00 (II) PCI: 00:0f:0: chip 1106,3149 card 1462,7071 rev 80 class 01,01,8f hdr 80 (II) PCI: 00:0f:1: chip 1106,0571 card 1462,7071 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip 1106,3038 card 1462,7071 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:4: chip 1106,3104 card 1462,7071 rev 86 class 0c,03,20 hdr 80 (II) PCI: 00:11:0: chip 1106,3227 card 1106,3227 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:5: chip 1106,3059 card 1462,b012 rev 60 class 04,01,00 hdr 00 (II) PCI: 00:12:0: chip 1106,3065 card 1462,7071 rev 78 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1106,7205 card 1462,7071 rev 01 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -100x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -100x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -100x - 0x (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:0:1), (-1,-1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -100x - 0x (0x1) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -100x - 0x (0x0) MX[B] (II) Bus -1 prefetchable memory
Re: [XFree86] GUI desktop problem- free bsd 5.0
We need to see the /var/log/XFree86.0.log file. When the security level is too high on BSD systems, the error you usually get is about being unable to open some device file or something like that, if I recall correctly. Mark. On Wed, 17 May 2006, shashi hegde wrote: Hi, I installed free BSD 5.0 in my system succesfully.( only one OS in my system) But I am not able to get my GUI desktop after typing startx command. I commented kern_securelevel = YES in /etc/rc.conf It gives me an error like. error from xf86HandleConfigFile() Fatal server error: no screens found X connection to :0.0 broken(explicitkill or server shutdown). xauth:creating new authority file /root/.Xauthority how can i overcome from this problem? ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] error arranque servidor x
This seems to happen on RedHat systems for reasons unknown. Something in the system appears to have deleted crucial XFree86 modules. The only solution I know of is to reintstall XFree86, or at least reinstall the modules. Mark. On Wed, 17 May 2006, John Figuero wrote: buen dia desde hace mas de un a?o estoy trabajando con RedHat 9.0 sin problema. pero el dia de hoy cuando inicie la computadora no me cargo el servicio X y este es el mensaje de error reportado. XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 PF Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: /dev/null, Time: Wed May 17 10:56:57 2006 (++) Using config file: /tmp/@4039.1xf86config (EE) Failed to load module bitmap (module does not exist, 0) Fatal server error: Unable to load required base modules, Exiting... 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 /dev/null. Please report problems to [EMAIL PROTECTED] Espero su gentil colaboracion . Gracias. __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ?gratis! Reg?strate ya - http://correo.espanol.yahoo.com/ ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: help ctrl-alt-keypad-plus not work
On Fri, 12 May 2006, f.l. wrote: Thanks! it works. and one more question please , the server started up with 1024x768 resolution, after a switched to 800x600, the virtual resolution is still 1024x768, i have to move mouse to view the invisible part of my whole desktop, i want real 800x600 resolution, how can it be done? Alledgedly, you can do that with the X Resize and Rotate extension, but I've never used it. Also, some apps (like your window manager) may not work properly when doing that. X11 never allowed the desktop size to change, so when using XRandR, only apps that are XRandR aware can deal with the size change properly. Other apps will think the desktop is the original size. Mark. thanks again! ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] help ctrl-alt-keypad-plus not work
You only have one mode to switch to. You need to have multiple modes listed on the Modes line in the XF86Config. The first is the default. ctrlalt+/- move through the rest. Eg. Modes 1024x768 800x600 640x480 Mark. On Thu, 11 May 2006, f.l. wrote: hi, im using xfree86 4.5.0, i want to switch screen mode while xserver is running, but the key combination not work, however, ctrl-alt-backspace works, please help. many thanks. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Please help me
I'm not sure I understand the artifact you are describing (maybe panel bloom?). But it is probably a driver problem and possibly fixed in a more recent version of XFree86. The version that came with Red Hat 7.3 is undoubtedly very old. For what it's worth, I see much information on Google about Linux and the ECS A900: http://www.google.com/search?hl=enlr=ie=ISO-8859-1safe=offq=%22ECS+A900%22+Linux Mark. On Thu, 11 May 2006, agung widiyanto wrote: Hello to everyone... First I will introduce myself...my nameis Agung from Surabaya, Indonesia I'm a newbie in Linux, and had just installed a Linux RedHat 7.3 on my desknote (ECS A900) First everything is just fine, but the problem is RedHat cannot probe my monitor, and when I use generic one I can go to GUI, but when I want to logout the screen sudddenly blackened from the center of it likes going to explode or something... If anyone have asolution for me I would very thankfull... please send me an email at [EMAIL PROTECTED] Regards, Agung Widiyanto === Ikuti Lomba Puisi Online Jawa Timur, dapatkan hadiah menarik setiap bulannya dan hadiah total senilai 60 juta rupiah hanya di http://www.plasa.com (Khusus Jawa Timur) === ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xlib: [X]DefaultRootWindow()
DefaultRootWindow() is a macro. XDefaultRootWindow() is an Xlib function. Both do the same thing (Display in, Root window ID out). In theory, DefaultRootWindow() is less portable because the macro accesses private data in the Display connection that could be different between vendors. In practice every implementation uses the same private data structures though so I'm not aware of any portability issues with the macros. Mark. On Fri, 5 May 2006, Florent Monnier wrote: Hi, (is this place ok for xlib beginner questions?) Are DefaultRootWindow() and XDefaultRootWindow() equivalent ? -- thanks ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with linux9 (no screen found)
Nothing can be said for certain without seeing the /var/log/XFree86.0.log file, but in general, when a screen is not found it means your X-server is too old to support your graphics hardware. There are other possibilities, however, and we'd need to see the XFree86.0.log file to diagnose. Mark. On Wed, 3 May 2006, iman fara wrote: dear xfree86 I am new with Linux 9, i installed it on dell pc with graphical mode ,after installaton , we entered in text mode , i tried to swith to graphical , i used these comands: -i first used the ctrl+alt+f7 i got blank screen -startx command i got no screen found Our screen is Dell E551 the video controller used is intell(R)82845G/GL/GE/PE/GV best regards __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] error report
On Thu, 20 Apr 2006, Juan CHEN wrote: When running under VMWare, you need to use the vmware driver, not the driver for your actual card. Modify /etc/X11/XF86Config accordingly. Marc. But I really don't know how to modify /etc/X11/XF86Config :( In the Section Device, change Driver nv to Driver vmware. Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] GUI not working
Due to security considerations (the X-server runs as root), unprivledged users are not allowed to provide custom XF86Config files. Only root can specify an alternative config file from the commandline. The XF86Config file can, however, hold multiple configurations which can be selected by users on the commandline (eg. startx -- -layout MovieLayout ). See the man page on XF86Config for layout section syntax. Basically, the first layout section listed is the default, but there can be other layouts selected via commandline as in the example above. You can have a separate layout section referencing a separate screen section with special modelines. If special device section options are needed, the separate screen section can reference a separate device section or separate monitor sections. Mark. On Fri, 14 Apr 2006, [EMAIL PROTECTED] wrote: I have suse 9.1 professional on my computer. I have a guest account just for movies(this is where all my movie players are installed). Is this screen modification system wide, or can I just modify the video output of the guest account. -- David Original Message: - From: Mark Vojkovich [EMAIL PROTECTED] Date: Wed, 25 Jan 2006 10:53:00 -0800 (PST) To: [EMAIL PROTECTED], xfree86@xfree86.org Subject: Re: [XFree86] GUI not working On Mon, 23 Jan 2006, [EMAIL PROTECTED] wrote: thanks Mark, for replying, but one question remains. If I could get the computer to display the smaller version of normal output in the center of the screen, would it still be able to reach 1024 by 768 resolution. It's not an analog display device so anything smaller than fullscreen would be using less than 1024x768 pixels. If you're connected to the monitor via a DVI connector, your graphics driver may be able to center a smaller mode in the middle of the screen (not all can, but some definitely can). If you're connected to a VGA connector, I'm not sure. If it were a CRT, it would be possible to display a mode in the center of the screen by playing with modeline timings. That is, you could set up a mode that had 1024x768 timings but with a smaller active area. For your panel it's less clear. You could send it 1024x768 timings with a smaller active area, but it might do something clever like strip out the black area and scale it up. You'd just have to try it. A typical 1024x768 @ 60 Hz modeline looks like (generated by 'gtf 1024 768 60'): # 1024x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 64.11 MHz Modeline 1024x768 64.11 1024 1080 1184 1344 768 769 772 795 If you just change the 1024 and 768 to 720 and 480 you have a 720x480 active area with 1024x768 timings. Then you could use xvidtune to adjust the sync starts and ends to center the image. That would work for a CRT. Mark. You see, I made a movie projector with an old overhead projector from school and and lcd screen (nec 1530v) and this screen has an auto resizer feature( which means that the screen automatically fits the video output to its maximum suize. consequently, I have to use the xine (movie player) window and manually match the screen size perfectly to the square patch of light coming up through the lcd screen from the overhead projector. ( this window of opportunity is 24 cm diagonally in the center of the lcd screen). So If I could get the computer to display what would normally take up the entire screen in this square (centered on the screen, sorry if I'm redundent), my troubles would be over. ( I would just load xine and hit the fullscreen button and watch the movie. Can't wait to hear your reponse! David Original Message: - From: Mark Vojkovich [EMAIL PROTECTED] Date: Sat, 21 Jan 2006 12:59:00 -0800 (PST) To: xfree86@xfree86.org Subject: Re: [XFree86] GUI not working It depends on whether you're using an analog (VGA) or digital (DVI) connection to the monitor. For analog, you can adjust that through modeline timings. xvidtune can help with that. For digital, it depends on the native resolution of the panel and the capabilities of the graphics driver. Some drivers support centering modes smaller than the panel's native resolution. Mark. On Fri, 20 Jan 2006, [EMAIL PROTECTED] wrote: Hi ,got a question. how could you change the video out in linux so that instead of full screen (15 inches) it would display the desktop in a 24 cm box in the center of the screen. Sort of like a smaller version of the normal display centered on the screen. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 mail2web - Check your email from the web at http://mail2web.com
Re: [XFree86] Support for Intel 82845G/GL Chipset???
I don't know much about the Intel driver, but I do notice your VideoRam entry in the Section Device which seems to cause the driver some confusion: VideoRam 12800 The VideoRam option describes the videoram in kilobytes, not bytes. Mark. On Wed, 12 Apr 2006, Rev. John Missing wrote: I am currently running Debian with the 2.6 kernel on an IBM NetVista with a 2.66 GHz Pentium 4 processor. It comes equipped with a 82845G/GL [Brookdale-G] Chipset for video which provides the following video mode capabilities: 640 x 480, 16M colors (60, 72, 75, 85, 100, 120 Hz) 800 x 600, 16M colors (60, 72, 75, 85, 100, 120 Hz) 1024 x 768, 16M colors (60, 70, 75, 85, 100,120 Hz) 1152 x 864, 16M colors (60, 70, 75, 85, 100 Hz) 1280x 1024, 16M colors (60, 75, 85, 100 Hz) 1600 x 1200, 16M colors (60 Hz) 1920 x 1440, 64K colors (60, 75 Hz) 2048 x 1536, 64K colors (60 Hz) However, I can only get those modes when I'm running Windows XP from which I'm trying to get migrate all my computing needs. Nevertheless, it seems that with XFree86, I have to choose between the higher color depth at 640x480 resolution or 256 colors at 1024x768. However, I can compromise somewhat by using a virtual desktop of 1024x768 at 16bit color depth, but this is a very inconvenient mode of operation, especially when I try to do graphic manipulations. The configuration done by XFree86's configure function will only give me a resolution of 640x480 with no other options. Is there any way to get the proper video modes to operate? ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Clipping graphic primitives to visible area of Window
On Mon, 10 Apr 2006, Pearson, Paul L-Baker Atlas wrote: Mark, I removed the backingstore option from XF86Config. Nothing is displayed in the area of the drawable that is exposed with scrolling. Our application does not catch the expose event, it relies on backingstore. So backingstore is partially working. Our application that uses XPutPixel to draw graphics does not have the problem. I can scroll around and everything is available. We use XDrawLine to draw the graphics that are missing from the display. I'm not sure what we use to display the text - but it is always there when I scroll around. I removed the three extensions that you had suggested. Now only the dotted line is displayed and the text is gone. That's weird. I would have expected it to get better. Where can I find info on the extensions? I searched for awhile looking for descriptions, without luck. I don't know of a database of extension descriptions. DBE is the double-buffer extension. I don't know of any applications that use it. GLX is the server component of OpenGL. DRI is an extension related to the implementation of OpenGL that the r128 driver uses. You could also try removing the extmod module but that holds very common extensions like shape and mitshm and some applications require those to operate. You could also try removing the fbdevhw module. I don't think your driver is using the framebuffer device and I didn't think that module wrapped any rendering operations, but it shouldn't hurt to remove it. If the backingstore puts up some of the image - shouldn't it put up all of the image? That's probably not the problem. Backing store allocates a pixmap the size of the drawable. Window rendering that gets clipped away goes to the backing pixmap. When part of the window is exposed, that part gets initialized with the backing pixmap contents instead of sending the client an expose event. I doubt copying from the backing pixmap is broken. Most likely, rendering to the backing pixmap is broken. The most common cause of that being broken is that some extension broke the mechanism which enables the backing store code to monitor window rendering. Could you also try telling the r128 to turn off hardware acceleration? That would be: Option NoAccel in the Section Device in the XF86Config file. The server will get very slow, but if it makes the problem go away it narrows down the problem substantially. Mark. We use backingstore for speed of display - these apps are run over the network and the geophysical data is large. Thanks for your help, Paul -Original Message- From: Mark Vojkovich [mailto:[EMAIL PROTECTED] Sent: Monday, April 10, 2006 12:41 To: Pearson, Paul L-Baker Atlas Cc: devel@XFree86.Org Subject: Re: [XFree86] Clipping graphic primitives to visible area of Window Backing store doesn't really guarantee that you won't get expose events. I believe the X11 Protocol specification says that enabling backing store merely tells the server that saving contents would be useful and doesn't guarantee that you won't get expose events. A program that isn't capable of handling expose events is technically broken. It's probably the case that different vendor implementations of backing store make different guarantees. XFree86 uses the implementation from the X11 sample implementation. The big question is whether or not XFree86 sent exposures when this scrolling occurred (assuming the application requested expose events in the first place). If the expose event was sent, this is technically not a server bug. The only thing weird that I see from your snapshots was that it appears as though some rendering operations may have be rendered to the backing store while some others might not have. Though another explanation is that XFree86 didn't render any of it and the text was the only part rerendered by the application after the expose event. I did some quick tests with the only backing store aware application I have (the xv image viewer) and didn't see any obvious problems using NVIDIA's drivers. Sometimes driver or extention implementations can break the backing store wrappers, but you are using the 'r128' driver which probably isn't modifying the wrappers. Some of the other extensions might. You could try commenting out the loading of the dbe, dri or glx modules in the XF86Config, but I doubt those would be breaking backing store wrappers. My guess is that this is probably a bad app assumption rather than a server bug, but I don't have a way to verify that at the moment. Mark. On Mon, 10 Apr 2006, Pearson, Paul L-Baker Atlas wrote: Mark, Thanks for the reply. Our applications do depend on backing store and I have enabled it, and it appears to work. If I put a window over the window, everything that was there comes back when the overlay
RE: [XFree86] Clipping graphic primitives to visible area of Window
This is probably either a r128 driver bug or a bug in the acceleration architecture (XAA). If you had access to a non-ATI video card that would be an interesting test. What might fix the problem without resorting to NoAccel is to prevent XAA from putting pixmaps in videoram. You can do that with: Option XaaNoOffscreenPixmaps If this was a r128 driver bug related to rendering to offscreen videoram or if this was an XAA problem related to rendering to backing store's backing pixmap, that would probably fix the problem. If it were a problem with XAA breaking backing store's wrappers, it probably wouldn't. But there may be other causes - perhaps that driver disables something else when disabling acceleration. From looking through driver code, it does appear that NoAccel also disables some things related to 3D. Mark. On Tue, 11 Apr 2006, Pearson, Paul L-Baker Atlas wrote: Mark, Send me the name and address of a favorite restaurant or bar and I'll have them open a tab for you to drink a beer with your compadres or eat a meal. The NoAccel fixed the problem. Moving the window around is slower, but the drawing is just as fast and the scrolling is reasonable. The boss is not happy though. Is there something I can do to get the acceleration back in? I had removed all the Load commands from the config file. It did not change anything. Thanks, Paul -Original Message- From: Mark Vojkovich [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 11, 2006 12:42 To: Pearson, Paul L-Baker Atlas Cc: devel@XFree86.Org Subject: RE: [XFree86] Clipping graphic primitives to visible area of Window On Mon, 10 Apr 2006, Pearson, Paul L-Baker Atlas wrote: Mark, I removed the backingstore option from XF86Config. Nothing is displayed in the area of the drawable that is exposed with scrolling. Our application does not catch the expose event, it relies on backingstore. So backingstore is partially working. Our application that uses XPutPixel to draw graphics does not have the problem. I can scroll around and everything is available. We use XDrawLine to draw the graphics that are missing from the display. I'm not sure what we use to display the text - but it is always there when I scroll around. I removed the three extensions that you had suggested. Now only the dotted line is displayed and the text is gone. That's weird. I would have expected it to get better. Where can I find info on the extensions? I searched for awhile looking for descriptions, without luck. I don't know of a database of extension descriptions. DBE is the double-buffer extension. I don't know of any applications that use it. GLX is the server component of OpenGL. DRI is an extension related to the implementation of OpenGL that the r128 driver uses. You could also try removing the extmod module but that holds very common extensions like shape and mitshm and some applications require those to operate. You could also try removing the fbdevhw module. I don't think your driver is using the framebuffer device and I didn't think that module wrapped any rendering operations, but it shouldn't hurt to remove it. If the backingstore puts up some of the image - shouldn't it put up all of the image? That's probably not the problem. Backing store allocates a pixmap the size of the drawable. Window rendering that gets clipped away goes to the backing pixmap. When part of the window is exposed, that part gets initialized with the backing pixmap contents instead of sending the client an expose event. I doubt copying from the backing pixmap is broken. Most likely, rendering to the backing pixmap is broken. The most common cause of that being broken is that some extension broke the mechanism which enables the backing store code to monitor window rendering. Could you also try telling the r128 to turn off hardware acceleration? That would be: Option NoAccel in the Section Device in the XF86Config file. The server will get very slow, but if it makes the problem go away it narrows down the problem substantially. Mark. We use backingstore for speed of display - these apps are run over the network and the geophysical data is large. Thanks for your help, Paul -Original Message- From: Mark Vojkovich [mailto:[EMAIL PROTECTED] Sent: Monday, April 10, 2006 12:41 To: Pearson, Paul L-Baker Atlas Cc: devel@XFree86.Org Subject: Re: [XFree86] Clipping graphic primitives to visible area of Window Backing store doesn't really guarantee that you won't get expose events. I believe the X11 Protocol specification says that enabling backing store merely tells the server that saving contents would be useful and doesn't guarantee that you won't get expose events. A program that isn't capable of handling expose events is technically broken
Re: [XFree86] Fatal IO error
It's probably a configuration error. We'd have to see the /var/log/XFree86.0.log file in order to diagnose it. Mark. On Mon, 10 Apr 2006, john paul orpilla wrote: I encountered this problem I'm using Mandrake 2.4.18-6mdksecure, when I typed startx it says Fatal Server Error: no screens found XIO: fatal IO error 104 ( Connection reset by peer ) on X Server :0:0 after 0 requests (0 known processed) with 0 events remaining. What can I do to fix this? - How low will we go? Check out Yahoo! Messenger?s low PC-to-Phone call rates. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] report
The server has not been configured. XFree86 4.1.0 is very old (nearly 5 years) and I don't remember it very well. You might be able to do XFree86 -configure to generate a config file. If not, then your Linux distribution probably has a utility to configure XFree86. Mark. On Tue, 11 Apr 2006 [EMAIL PROTECTED] wrote: 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.4 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Tue Apr 11 01:37:27 2006 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() 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] ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Clipping graphic primitives to visible area of Window
Backing store doesn't really guarantee that you won't get expose events. I believe the X11 Protocol specification says that enabling backing store merely tells the server that saving contents would be useful and doesn't guarantee that you won't get expose events. A program that isn't capable of handling expose events is technically broken. It's probably the case that different vendor implementations of backing store make different guarantees. XFree86 uses the implementation from the X11 sample implementation. The big question is whether or not XFree86 sent exposures when this scrolling occurred (assuming the application requested expose events in the first place). If the expose event was sent, this is technically not a server bug. The only thing weird that I see from your snapshots was that it appears as though some rendering operations may have be rendered to the backing store while some others might not have. Though another explanation is that XFree86 didn't render any of it and the text was the only part rerendered by the application after the expose event. I did some quick tests with the only backing store aware application I have (the xv image viewer) and didn't see any obvious problems using NVIDIA's drivers. Sometimes driver or extention implementations can break the backing store wrappers, but you are using the 'r128' driver which probably isn't modifying the wrappers. Some of the other extensions might. You could try commenting out the loading of the dbe, dri or glx modules in the XF86Config, but I doubt those would be breaking backing store wrappers. My guess is that this is probably a bad app assumption rather than a server bug, but I don't have a way to verify that at the moment. Mark. On Mon, 10 Apr 2006, Pearson, Paul L-Baker Atlas wrote: Mark, Thanks for the reply. Our applications do depend on backing store and I have enabled it, and it appears to work. If I put a window over the window, everything that was there comes back when the overlay is removed. I have a window which is smaller than my drawable. The window has scroll bars. I use text, pixels and graphic primitives (XDrawLine) to display to the drawable. Everything is displayed in the window. I scroll the window. The text and pixels are displayed, but the graphics done with the primitives are not displayed. The display acts as if the clip_x_origin, clip_y_origin and clip_mask are being set to the size and location of the window. If I scroll the window and force a graphics update, some more primitives are displayed. If I scroll the window back to where it was, that which was displayed with the primitives is gone, text and pixels are there. I've attached four files (hopefully I will remember to attach them) - the XF86Config file, disp1.png (showing the display before scrolling) and disp2.png (showing the display after scrolling), and disp3.png (after forcing an update to the scrolled window). Paul Pearson Software Developer VSFusion 16430 Park Ten Place, Suite 405 Houston, Texas 77084 tel: + 1 281-646-2750 fax: + 1 281-646-2799 email: [EMAIL PROTECTED] web: www.vsfusion.com ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Clipping graphic primitives to visible area of Window
Perhaps your application is using backing store? You can start X with backing store support with a commandline argument. eg: startx -- +bs Mark. On Thu, 6 Apr 2006, Pearson, Paul L-Baker Atlas wrote: I am running XFree86 Version 4.2.0 on Red Hat Linux 4.2.0-72. When drawing lines and other primitives to the window, only the visible portions are displayed. If I scroll the window, the graphics are missing. The text is where it should be. The code works on Solaris and HP. What do I need to do to stop the clipping so the graphics are visible over the whole window as it is scrolled? Thanks, Paul Pearson Software Developer VSFusion 16430 Park Ten Place, Suite 405 Houston, Texas 77084 tel: + 1 281-646-2750 fax: + 1 281-646-2799 email: [EMAIL PROTECTED] web: www.vsfusion.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] x server crash *no graphical interface*
This is not XFree86 4.3. This is the output of an old XFree86 3.x server (the old XF86_SVGA server). It's also not entirely clear that the server isn't running properly. If you can move the cursor around, it probably is and the window manager just isn't starting. Can you run /usr/X11R6/bin/XFree86 and get the root weave and moveable cursor then ctrlaltbackspace to get back to the console? If so, the server itself is running fine. Mark. On Wed, 5 Apr 2006, sammy n. wrote: hi to all, i've just installed mandrake linux 9.1 on my pc which also runs winxp pro. i have xfree86 version 4.3.0 i've never been able to use the graphical interface (i only use command line - very laborious). the x server always crashes! upon starting up the system, the graphical interface doesn't ever load completely. the screen flickers lots of times then i'm left with an empty, blue desktop (no icons, no task bar; nothing!) and a busy cursor. when i start x, i get the following output: Using authority file /root/.Xauthority Writing authority file /root/.Xauthority Using authority file /root/.Xauthority Writing authority file /root/.Xauthority Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again *after removing /tmp/.X0-lock, startx gives: _XSERVTransSocketINETCreateListener:...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal Server Error: Cannot establish any listening sockets - Make sure an X server isn't already running *after killing the startx process (using top), i try startx again, and get: (i get the same result if i do init 3, then startx) (--) SVGA: Mode 1600*1200 needs hsync freq of 106.25KHz. Deleted. (--) SVGA: Mode 1280*1024 needs hsync freq of 107.16KHz. Deleted. (--) SVGA: Mode 1800*1440 needs hsync freq of 96.15KHz. Deleted. (--) SVGA: Mode 1800*1440 needs hsync freq of 104.52KHz. Deleted. (--) SVGA: Mode 1920*1440 needs hsync freq of 90.00KHz. Deleted. (--) SVGA: Mode 1920*1440 needs hsync freq of 112.50KHz. Deleted. (**) FontPath set to unix/:-1 (--) SVGA: PCI: S3 Trio 3D rev 1, Memory @ 0xf400 (--) SVGA: S3V: Trio 3D rev 1, Linear FB @ 0xf400 (--) SVGA: Detected S3 Trio 3D (--) SVGA: using driver for chipset s3_virge (--) SVGA: videoram: 4096k (--) SVGA: Ramdac speed: 230Mhz (135MHz for 24bpp) (--) SVGA: Detected current MCLK value of 100.227MHz (--) SVGA: chipset: s3_virge (--) SVGA: videoram: 4096k (**) SVGA: Option sw_cursor (**) SVGA: Option power_saver (**) SVGA: Using 24bpp , Depth 24, Color weight: 888 (--) SVGA: Maximum allowed dot-clock: 135.000MHz (--) SVGA: Interlaced modes are not supported at 24bpp (--) SVGA: Interlaced modes are not supported at 24bpp (--) SVGA: Interlaced modes are not supported at 24bpp (**) SVGA: Mode 1024*768: mode clock = 115.500 (**) SVGA: Mode 800*600: mode clock = 69.650 (**) SVGA: Mode 640*480: mode clock = 45.800 (--) SVGA: Virtual resolution set to 1024*768 (--) SVGA: Using XAA (XFree86 Acceleration Architecture) (--) SVGA: XAA: Solid filled rectangles (--) SVGA: XAA: Screen-to-screen copy (--) SVGA: XAA: 8*8 pattern fill (--) SVGA: XAA: 8*8 color expand fill (--) SVGA: XAA: CPU to screen color expansion (bitmap, TE/NonTE imagetext, TE/NonTE polytext) (--) SVGA: XAA: Using 8 128*128 areas for pixmap caching (--) SVGA: XAA: Caching tiles and non-transparent stipples (--) SVGA: XAA: Horizontal and vertical lines and segments *if i kill the x process instead, startx gives: Xlib: connection to :0.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key giving up xinit: unable to connect to X server
Re: [XFree86] x server crash *no graphical interface*
On Wed, 5 Apr 2006, Mark Vojkovich wrote: This is not XFree86 4.3. This is the output of an old XFree86 3.x server (the old XF86_SVGA server). It's also not entirely clear that the server isn't running properly. If you can move the cursor around, it probably is and the window manager just isn't starting. Can you run /usr/X11R6/bin/XFree86 and get the root weave and moveable cursor then ctrlaltbackspace to get back to the console? If so, the server itself is running fine. Whoops, in this case the server is actually /usr/X11R6/bin/XF86_SVGA not /usr/X11R6/bin/XFree86. /usr/X11R6/bin/XFree86 would use the XF86Config-4 file as its configuration file. Mark. On Wed, 5 Apr 2006, sammy n. wrote: hi to all, i've just installed mandrake linux 9.1 on my pc which also runs winxp pro. i have xfree86 version 4.3.0 i've never been able to use the graphical interface (i only use command line - very laborious). the x server always crashes! upon starting up the system, the graphical interface doesn't ever load completely. the screen flickers lots of times then i'm left with an empty, blue desktop (no icons, no task bar; nothing!) and a busy cursor. when i start x, i get the following output: Using authority file /root/.Xauthority Writing authority file /root/.Xauthority Using authority file /root/.Xauthority Writing authority file /root/.Xauthority Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again *after removing /tmp/.X0-lock, startx gives: _XSERVTransSocketINETCreateListener:...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal Server Error: Cannot establish any listening sockets - Make sure an X server isn't already running *after killing the startx process (using top), i try startx again, and get: (i get the same result if i do init 3, then startx) (--) SVGA: Mode 1600*1200 needs hsync freq of 106.25KHz. Deleted. (--) SVGA: Mode 1280*1024 needs hsync freq of 107.16KHz. Deleted. (--) SVGA: Mode 1800*1440 needs hsync freq of 96.15KHz. Deleted. (--) SVGA: Mode 1800*1440 needs hsync freq of 104.52KHz. Deleted. (--) SVGA: Mode 1920*1440 needs hsync freq of 90.00KHz. Deleted. (--) SVGA: Mode 1920*1440 needs hsync freq of 112.50KHz. Deleted. (**) FontPath set to unix/:-1 (--) SVGA: PCI: S3 Trio 3D rev 1, Memory @ 0xf400 (--) SVGA: S3V: Trio 3D rev 1, Linear FB @ 0xf400 (--) SVGA: Detected S3 Trio 3D (--) SVGA: using driver for chipset s3_virge (--) SVGA: videoram: 4096k (--) SVGA: Ramdac speed: 230Mhz (135MHz for 24bpp) (--) SVGA: Detected current MCLK value of 100.227MHz (--) SVGA: chipset: s3_virge (--) SVGA: videoram: 4096k (**) SVGA: Option sw_cursor (**) SVGA: Option power_saver (**) SVGA: Using 24bpp , Depth 24, Color weight: 888 (--) SVGA: Maximum allowed dot-clock: 135.000MHz (--) SVGA: Interlaced modes are not supported at 24bpp (--) SVGA: Interlaced modes are not supported at 24bpp (--) SVGA: Interlaced modes are not supported at 24bpp (**) SVGA: Mode 1024*768: mode clock = 115.500 (**) SVGA: Mode 800*600: mode clock = 69.650 (**) SVGA: Mode 640*480: mode clock = 45.800 (--) SVGA: Virtual resolution set to 1024*768 (--) SVGA: Using XAA (XFree86 Acceleration Architecture) (--) SVGA: XAA: Solid filled rectangles (--) SVGA: XAA: Screen-to-screen copy (--) SVGA: XAA: 8*8 pattern fill (--) SVGA: XAA: 8*8 color expand fill (--) SVGA: XAA: CPU to screen color expansion (bitmap, TE/NonTE imagetext, TE/NonTE polytext) (--) SVGA: XAA: Using 8 128*128 areas for pixmap caching (--) SVGA: XAA: Caching tiles and non-transparent
Re: [XFree86] cannot start X
I think the driver for this card relies on the VESA BIOS to do the mode setup. You requested a depth 24, 32 bpp mode and I do see 32 bpp modes listed below so it's not immdiately clear why this isn't working. Perhaps a newer driver will work better? The XFree86 version you are using (4.3.0) is over three years old. Mark. On Tue, 4 Apr 2006, Mounavar Beck wrote: Hi, I am not able to start X on my machine Can you pls help The log file is below beck [Mounavar Beck] XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Apr 4 18:39:35 2006 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2570 card 1028,017a rev 02 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2572 card 1028,017a rev 02 class 03,00,00 hdr 00 (II) PCI: 00:1d:0: chip 8086,24d2 card 1028,017a rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24d4 card 1028,017a rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,24de card 1028,017a rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24dd card 1028,017a rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev c2 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24d0 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24db card 1028,017a rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,24d1 card 1028,017a rev 02 class 01,01,8f hdr 00 (II) PCI: 00:1f:3: chip 8086,24d3 card 1028,017a rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24d5 card 1028,017a rev 02 class 04,01,00 hdr 00 (II) PCI: 01:08:0: chip 8086,1050 card 1028,017a rev 02 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0xd000 - 0xdfff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfea0 - 0xfeaf (0x10) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corp. 865G Chipset Graphics Controller rev 2, Mem @ 0xe800/27, 0xfeb8/19, I/O @ 0xed98/3 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B]
Re: [XFree86] An old error in startx, but it's new to me
Your X-server has not be configured. Run XFree86 -configure or whatever X configuration utility comes with RedHat (I don't know the name of it). Mark. On Wed, 5 Apr 2006, zhao sheng wrote: Hi, after I installed Red hat linux version in my laptop computer, i can't use the gui mode. When i type the command startx, some error message as following appeared. And i don't know how to solve this problem. Would you give me some advice, please? Thank you very much!! The following is the error log in XFree86.0.log: XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/http://www.xfree86.org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Apr 5 23:48:41 2006 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() 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] -- Chopsticks ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] frame buffer problem pls help
Use XFree86 -configure instead. There is a native Matrox driver that you should be using. Autoconfig, in my opinion, erroneously configures to use a framebuffer driver even when the mga driver is available. Or you could just remove the references to the fbdev, vesa and vga Devices in your current XF86Config file. The fbdev driver sounds like it wants to have a BusID line like so: BusIDPCI:1:0:0 in its Section Device. But really you should be using the mga driver, not the fbdev driver. Mark. On Sun, 2 Apr 2006, Kurazs Iosif Daniel wrote: XFree86 Version 4.5.0 Release Date: 16 March 2005 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.4.24 i686 [ELF] Current Operating System: Linux debian 2.6.8-2-686-smp #1 SMP Tue Aug 16 12:08:30 UTC 2005 i686 Build Date: 16 March 2005 Changelog Date: 16 March 2005 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Command line: XFree86 -autoconfig Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (EE) error, (WW) warning, (II) informational, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Sun Apr 2 16:13:33 2006 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.3 XFree86 Video Driver: 0.8 XFree86 XInput driver : 0.5 XFree86 Server Extension : 0.3 XFree86 Font Renderer : 0.5 (II) Loader running on linux (--) using VT number 8 (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.5.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.8 (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,1a21 card , rev 01 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a23 card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 8086,1a24 card , rev 01 class 06,04,00 hdr 01 (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:3: chip 8086,2413 card 8086,2413 rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2415 card 1014,0199 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 102b,0525 card 102b,0541 rev 85 class 03,00,00 hdr 00 (II) PCI: 02:1f:0: chip 8086,1360 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 03:00:0: chip 8086,1161 card 8086,1161 rev 01 class 08,00,20 hdr 80 (II) PCI: 03:06:0: chip 9005,00cf card 1014,019d rev 01 class 01,00,00 hdr 80 (II) PCI: 03:06:1: chip 9005,00cf card 1014,019d rev 01 class 01,00,00 hdr 80 (II) PCI: 04:0c:0: chip 8086,1229 card 1014,405c rev 08 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,4), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -100x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -100x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -100x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -100xfe00 - 0xfebf (0xc0) MX[B] (II) Bus 1 prefetchable memory range: [0] -100xfa00 - 0xfdcf (0x3d0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:2:0), (0,2,3), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 2 I/O range: [0] -100x7000 - 0x7fff (0x1000) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -100xfdf0 - 0xfdff (0x10) MX[B] (II) PCI-to-PCI bridge: (II) Bus 4: bridge is at (0:30:0), (0,4,4), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 4 I/O range: [0] -100x6000 - 0x6fff (0x1000) IX[B] (II) Bus 4 non-prefetchable memory range: [0] -100xfdd0 - 0xfdef (0x20) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) PCI-to-PCI bridge: (II) Bus 3: bridge is at (2:31:0), (2,3,3), BCTRL: 0x8002 (VGA_EN is cleared) (II) Bus 3 I/O range: [0] -100x7000 - 0x7fff (0x1000) IX[B] (II) Bus 3 non-prefetchable memory range: [0] -100xfdf0 - 0xfdff (0x10) MX[B] (--) PCI:*(1:0:0) Matrox Graphics, Inc. MGA G400 AGP rev 133, Mem @ 0xfa00/25, 0xfebfc000/14, 0xfe00/23 (II)
Re: CVS GLX oddity
Is that the final fix or is there something else I should test?
That one works for me.
Mark.
On Thu, 23 Mar 2006, Mark Vojkovich wrote:
Yes, that works.
Mark.
On Thu, 23 Mar 2006, David Dawes wrote:
On Wed, Mar 22, 2006 at 08:52:00PM -0800, Mark Vojkovich wrote:
initdata is still NULL even after your call to LoaderSymbol() in
that patch.
The module name needs to be prepended. Something like:
if (!initdata) {
char *md;
xasprintf(md, %s MODULE_DATA_NAME, name);
if (md) {
initdata = LoaderSymbol(md);
xfree(md);
}
}
David
Mark.
On Wed, 22 Mar 2006, David Dawes wrote:
On Wed, Mar 22, 2006 at 06:57:17PM -0800, Mark Vojkovich wrote:
I can't get CVS to load NVIDIA's GLX module. It complains:
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
(EE) LoadModule: Module glx does not have a glxModuleData data object.
(II) UnloadModule: glx
Did something change with regards to this? It was working before
I updated.
dlopen modules have always had different semantics than XFree86 modules.
These differences will only get greater as additional features are added
to the XFree86 loader and as the newly added features are used more
widely.
The following (untested) patch may solve this particular problem. Let
me know
how it goes.
David
--
David Dawes X-Oz Technologies
www.XFree86.org/~dawes www.x-oz.com
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] double buffer
On Fri, 24 Mar 2006, Florent Monnier wrote: You can render to a pixmap and then copy the contents of the pixmap to the window with XCopyArea(). ... It works, but there is a big big loss of performence ! Without double buffer the frame rate can be for a test example 380 frames per seconds, but with double-buffer it slows a lot down to 30 frames / seconds. That sounds like the pixmap didn't get put in videoram, which is unfortunate. It probably would have been fast if the pixmap was in videoram. Does this card have very much videoram? My video card is a nVidia GeForce4 Ti 4200 with AGP8X If you VT switch to the console and then back to X (to clear out the existing videoram pixmaps) before starting your app does it run significantly faster? Not at all. It is still very slow in the same way. I'm not sure why it's doing that. If the pixmap was in videoram, for the worst case (if it were framebuffer bandwidth limited), I would expect double buffered to be 1/3 the speed of single buffered. The only reasons I can think of why it wouldn't go into videoram are: 1) Not enough videoram (seems unlikely with that card just after a VT switch). 2) It's a shared memory pixmap rather than regular pixmap created with XCreatePixmap. 3) You're doing more than just rendering to the pixmap and copying into the window. I have a old demo app which does something similar. http://www.xfree86.org/~mvojkovi/skull.tar.gz Don't run the DGA version (DGA is mostely obsolete). Run the X11 version (make skull_X). Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: CVS GLX oddity
Yes, that works.
Mark.
On Thu, 23 Mar 2006, David Dawes wrote:
On Wed, Mar 22, 2006 at 08:52:00PM -0800, Mark Vojkovich wrote:
initdata is still NULL even after your call to LoaderSymbol() in
that patch.
The module name needs to be prepended. Something like:
if (!initdata) {
char *md;
xasprintf(md, %s MODULE_DATA_NAME, name);
if (md) {
initdata = LoaderSymbol(md);
xfree(md);
}
}
David
Mark.
On Wed, 22 Mar 2006, David Dawes wrote:
On Wed, Mar 22, 2006 at 06:57:17PM -0800, Mark Vojkovich wrote:
I can't get CVS to load NVIDIA's GLX module. It complains:
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
(EE) LoadModule: Module glx does not have a glxModuleData data object.
(II) UnloadModule: glx
Did something change with regards to this? It was working before
I updated.
dlopen modules have always had different semantics than XFree86 modules.
These differences will only get greater as additional features are added
to the XFree86 loader and as the newly added features are used more
widely.
The following (untested) patch may solve this particular problem. Let me
know
how it goes.
David
--
David Dawes X-Oz Technologies
www.XFree86.org/~dawes www.x-oz.com
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Forcing Xfree Configuration to Sync on Green
Looking at the driver code, I see no option to enable that. I don't know if the hardware is even capable of it. Mark. On Thu, 23 Mar 2006 [EMAIL PROTECTED] wrote: Can Xfree with Intel 815 video driver be configured to sync on green? I am trying to use the console video as one of two possible sources to drive a monitor which only has RGB connected. Thanks, ---David Dembrow ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
CVS GLX oddity
I can't get CVS to load NVIDIA's GLX module. It complains: (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so (EE) LoadModule: Module glx does not have a glxModuleData data object. (II) UnloadModule: glx Did something change with regards to this? It was working before I updated. Mark. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: CVS GLX oddity
initdata is still NULL even after your call to LoaderSymbol() in that patch. Mark. On Wed, 22 Mar 2006, David Dawes wrote: On Wed, Mar 22, 2006 at 06:57:17PM -0800, Mark Vojkovich wrote: I can't get CVS to load NVIDIA's GLX module. It complains: (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so (EE) LoadModule: Module glx does not have a glxModuleData data object. (II) UnloadModule: glx Did something change with regards to this? It was working before I updated. dlopen modules have always had different semantics than XFree86 modules. These differences will only get greater as additional features are added to the XFree86 loader and as the newly added features are used more widely. The following (untested) patch may solve this particular problem. Let me know how it goes. David -- David Dawes X-Oz Technologies www.XFree86.org/~dawes www.x-oz.com ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] double buffer
On Wed, 22 Mar 2006, Florent Monnier wrote: You can render to a pixmap and then copy the contents of the pixmap to the window with XCopyArea(). This will be similar to many implementations of glXSwapBuffers, however, many GL implementation allow synchronization with the refresh rate, while Xlib offers no such feature. Note that glXSwapBuffers executes an implicit glFlush, while XCopyArea does not execute an implicit XFlush. Thanks a lot! It works, but there is a big big loss of performence ! Without double buffer the frame rate can be for a test example 380 frames per seconds, but with double-buffer it slows a lot down to 30 frames / seconds. That sounds like the pixmap didn't get put in videoram, which is unfortunate. It probably would have been fast if the pixmap was in videoram. Does this card have very much videoram? If you VT switch to the console and then back to X (to clear out the existing videoram pixmaps) before starting your app does it run significantly faster? Mark. Is it normal ? Is there tricks to improve the cost of the double-buffering ? -- Thanks in advance ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] double buffer
You can render to a pixmap and then copy the contents of the pixmap to the window with XCopyArea(). This will be similar to many implementations of glXSwapBuffers, however, many GL implementation allow synchronization with the refresh rate, while Xlib offers no such feature. Note that glXSwapBuffers executes an implicit glFlush, while XCopyArea does not execute an implicit XFlush. Mark. On Tue, 21 Mar 2006, Florent Monnier wrote: Hi, I've started to learn the Xlib, and when there are a lot of things to draw on the screen, the display is not regular. With openGL this effect is corrected by using double buffering. So I'm wondering how to use double buffering with the Xlib? I've got an answer on an other list which was to draw on another drawable, and then to switch the 2 drawables with XCopyArea(), but all I get is a blanck screen with this. -- thanks in advance ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Sync out of Range
We'll need to see the /var/log/XFree86.0.log file in order to get an idea of what's going on. Mark. On Sun, 19 Mar 2006, Phronz Phrobish wrote: I installed OpenSUSE 10 on an older AMD machine with a TNT video card. The install went great, but when the xserver started my monitor, Samsung 700d, reports Sync out of Sync message. Any one have an idea how to get the xserver to start and not get the error? Also looking for a information resource for Troubleshooting. Thanks ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] no screens found !!!
The logfile implies that the XF86Config-4 file is configured to use a framebuffer device (Driver fbdev), however, the kernel does not support (or no longer supports) a framebuffer device. You might want to try changing to the i810 driver (Driver i810 in the Section Device in the XF86Config-4 file). The i810 driver that comes with your server version *might* be new enough to support your graphics card. It seems that either your kernel supported a framebuffer device and no longer does after your unclean shutdown, or the XF86Config-4 file got changed to use fbdev since the last time it was working. Mark. On Mon, 20 Mar 2006, abhilash tiwari wrote: hi i am facing this very strange problem since my mom accidentally shut off the Laptop ...it was running mandrake linux 10.0 and i was in KDe and mom put it off even before it could turn off so now when i am startting the x server it says no screens foundi tried to figure out a way out of this .and even tried to tweak things ...but to no use i am still able to access my linux ...but only in the text mode i mean the command prompt mode also /only the root login is working now.. my own login called micks was removed ...i dnt knw hw alsoi cudnt access the HOMe directory thru the text mode at all plz send me the solution to this problem ASAP mind it i dnt hav my installation Cd here and i hav a Dial up conn tht goes off more than often so downloadint huge stufff is not my option plz help me ASap...i hav been diggin into it for a month now ...cudnt figure out whats wrong abhilash If You ever need a helping hand, there's always one at the end of your arm mickey ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ltsp queries
There is no error in this logfile. It shows a correctly working server. What seems to be the problem? Mark. On Tue, 14 Mar 2006, naveenkumar jha wrote: hello, i am trying to boot the client machine than it prompt the following messages. Auto probe of your video card failed. your xfree 86 is not match. XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Thu Mar 13 17:45:54 EST 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Mar 14 15:46:41 2006 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8001680c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2570 card 1043,80f2 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2572 card 1043,2572 rev 02 class 03,00,00 hdr 00 (II) PCI: 00:1d:0: chip 8086,24d2 card 1043,24d0 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24d4 card 1043,24d0 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24d7 card 1043,24d0 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,24de card 1043,24d0 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24dd card 1043,24d0 rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev c2 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24d0 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24db card 1043,24d0 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24d3 card 1043,24d0 rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24d5 card 1043,810d rev 02 class 04,01,00 hdr 00 (II) PCI: 01:0d:0: chip 10ec,8139 card 1043,80b3 rev 10 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0006 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0xd000 - 0xd0ff (0x100) IX[B] [1] -1 0 0xd400 - 0xd4ff (0x100) IX[B] [2] -1 0 0xd800 - 0xd8ff (0x100) IX[B] [3] -1 0 0xdc00 - 0xdcff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfe50 - 0xfe5f (0x10) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corp. 865G Chipset Graphics Controller rev 2, Mem @ 0xf000/27, 0xfe78/19, I/O @ 0xeff0/3 (II) Addressable bus resource ranges are [0] -1 0
Re: [XFree86] error messages
On Tue, 14 Mar 2006, [EMAIL PROTECTED] Davis wrote: Can someone point me to some materials that document the error messages given by the Xfree86 server? For instance, device not found? If the documentation for the X server says that the nv driver supports pci and agp, does this include pci express video cards with the nv chipset? The current nv driver from CVS supports all known NVIDIA graphics chips. The one you have only supports chips that came out before it was released. Device not found is the typical response a driver gives when it doesn't recognize a chip that it supports. If you can tell me which card you have, I can tell you when it was first supported in the nv driver. Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X server crash... Help
The XFree86.0.log file claims you have no configuration file: (EE) Unable to locate/open config file You need to generate an XF86Config file (XFree86 -configure). If you want to run NVIDIA's binary drivers you should follow NVIDIA's instructions on how to install and configure their drivers. The failure to restore the console that you describe is a driver bug. Mark. On Sat, 11 Mar 2006, Bob Franklin wrote: Last time I started up my computer(Slack 10) and successfully started x, I installed swaret and patched all my packages, and had just installed ethereal and was trouble shooting it when I decided to try switching to root. I logged out, logged in to root, tried to startx and got the message in XFree86.0.log. Ever since I started using my nvidia driver with X, I also have the problem that the display goes random when I logout and I have to work blind to log back in. I'm hoping that that's what the other log files are and you have an answer for me for that aswell. Any help would be much appreciated. I'm a novice user so it would be a great help. Until then I'm stuck on Knoppix... Thanks in advance. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Unable to go to GUI mode in Linux
You have a couple problems here. 1) You have a partial install of NVIDIA's binary drivers (you are trying to use their GLX module, but the graphics driver you are using is the nv driver that comes with XFree86). 2) The nv driver that comes with XFree86, which you are using, predates your graphics hardware and therefore does not support it. Release Date: 23 January 2002 You either need to update XFree86 to something more recent that supports you video card, or you need to install NVIDIA's binary drivers correctly (follow their directions), and you'd probably want to use something more recent than the ancient version 4363 drivers you tried to install. Mark. On Sat, 11 Mar 2006, Ray SN wrote: Dear Sir, We are Linux- Red hat 7.3 machine with NVIDIA graphics card. Previously it was working Okay. But recently due to unknown reasons we are unable to go to GUI mode. We verify the log file /var/log/XFree86.0.log whose contents are given below: Pl help us in solving in this case. Regards with thanks, S.N.Ray - log file 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: Sat Jan 5 20:44:04 2002 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Dell M770 (**) | |--Device My Video Card (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbLayout gb (**) XKB: layout: gb (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.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,2550 card 103c,129d rev 03 class 06,00,00 hdr 80 (II) PCI: 00:00:1: chip 8086,2551 card 103c,129d rev 03 class ff,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2552 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 8086,2553 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24c2 card 103c,129d rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 103c,129d rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 103c,129d rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 103c,129d rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 82 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24c0 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24cb card 103c,129d rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 103c,129d rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24c5 card 103c,129d rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0288 card 10de,0174 rev a1 class 03,00,00 hdr 00 (II) PCI: 02:1c:0: chip 8086,1461 card 103c,129d rev 04 class 08,00,20 hdr 00 (II) PCI: 02:1d:0: chip 8086,1460 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 02:1e:0: chip 8086,1461 card 103c,129d rev 04 class 08,00,20 hdr 00 (II) PCI: 02:1f:0: chip 8086,1460 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 03:05:0: chip 1000,0030 card 103c,129d rev 07 class 01,00,00 hdr 80 (II) PCI: 03:05:1: chip 1000,0030 card 103c,129d rev 07 class 01,00,00 hdr 80 (II) PCI: 05:00:0: chip
Re: [XFree86] X server crash during configuration!
On Thu, 9 Mar 2006, Remy Nsiku wrote: Dear Sir or Madam: Following are the pciscan and xfreeconfig.log files that obtained from the configuration attempt. The PC is a Dell dimension 2350. Thank you, Remy Nsiku xfreeconfig.log: 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/) Your XFree86 version is over 4 years old and most likely predates your graphics card. You should upgrade. (--) PCI:*(0:2:0) Intel unknown chipset (0x2562) rev 3, Mem @ 0xe000/27, 0xee00/19 Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Question about XFree86 4.5.99.901 snapshot
It would appear as though -autoconfig is broken. Can you do -configure instead? It used to be able to generate a working config file. Mark. On Wed, 8 Mar 2006, Tom Williams wrote: Hi! I just installed the XFree86 4.5.99.901 snapshot (which fixed my xterm installation problem, thanks guys! :)) and it runs fine. I wanted to try the -autoconfig option to see what it would do and it generated these messages: Required symbol fbdevHWLoadPalette from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWModeInit from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWSave from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWMapVidmem from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWGetVidmem from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWUseBuildinMode from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWValidMode from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWAdjustFrame from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWSwitchMode from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWLeaveVT from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWInit from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Required symbol fbdevHWEnterVT from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Fatal server error: Some required symbols were unresolved. The full XFree86.0.log file is attached. I have a GeForce2 MX-200 32MB PCI video card and the nv driver works flawlessly for me. I wanted to report these messages so you would be aware. :) Peace... Tom ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problem with X
The mouse device specified in your XF86Config file (/dev/psaux) does not exist. In the Section InputDevice try specifying: Option Device /dev/mouse instead. Mark. On Sat, 25 Feb 2006, vasanth kumar wrote: I started the machine as usaul, but i was not able to start the Xserver, i don't know what's the problem i found this log file i am sending the log as attahment please sort out my problem ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ddcprobe returned bogus values
I'm not very familiar with the Cirrus Logic driver, but it's possible that it's fixed in a more recent version. Mark. On Fri, 24 Feb 2006, Chris LaForce wrote: Mark, Thanks for the response. That helped out a bit. Now when my Laptop boots up a garbled screen comes up and I can kind of make out a redhat logo. The screen then goes blank and an X comes up for the cursor. The X cursor then turns into and hour glass. It thinks for a little bit and then goes away. At that point my laptop seems locked. I tried to click ctrl+alt+F2 and it will not go back to a command prompt. Let me know if you have anymore info. Thanks, Chris. On Thu, 2006-02-23 at 10:31 -0800, Mark Vojkovich wrote: I believe most laptops don't actually have EDIDs (no monitor plug and play info) so there's no info to get from DDC (and probably isn't even a DDC). You don't want to be using the VGA driver. You want to have Driver cirrus in your Section Device. Mark. On Wed, 22 Feb 2006, Chris Melinda LaForce wrote: Hello, I have a RedHat 9.0 system with which I am having some display problems. When I boot it up and it tries to launch the gui I get the below error: * ddcprobe returned bogus values: ID:None Name: None HorizSync: None VertSync: None I also get this when trying to launch redhat-config-xfree86. My XFree86 version is 4.3.0. Here is part of my XF86Config as I don't not at this time have access to the internet on the probelmatic pc to get the whole file: Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelName Unprobed Monitor HorizSync 31.5 - 37.9 VertRefresh 50.0 - 70.0 Option dpms EndSection Section Device Identifier Videocard0 Driver vga VendorName Videocard vendor BoardName Cirrus Logic GD754x (laptop) EndSection The XFree86.0.log log looks like there is problems setting the resolution. It has a bunch of messages saying (II) VGA(0): Not using defualt mode 640x350 (insufficient memory for mode) 320x175 (vrefresh out of range) 360x200' (hsync out of range) I'm wondering if I need to reconfigure the Monitor section of my XF86Config file. Please let me know if you can offer any assistance with this problem or if more info is needed. Thanks, Chris. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: How do I sync output changes to vertical retrace?
On Wed, 22 Feb 2006, Barry Scott wrote:
Mark Vojkovich wrote:
The only mechanism I know of is OpenGL. Most OpenGL drivers have
a mechanism to allow buffer swapping at vblank.
Using DRM/DRI this works:
void waitForVSync()
{
if( card_fd 0 )
card_fd = open( /dev/dri/card0, O_RDONLY );
drm_wait_vblank_t wait_vblank;
wait_vblank.request.type = _DRM_VBLANK_RELATIVE;
wait_vblank.request.sequence = 1;
wait_vblank.request.signal = 0;
int rc;
do
{
wait_vblank.request.type = _DRM_VBLANK_RELATIVE;
rc = ioctl( card_fd, DRM_IOCTL_WAIT_VBLANK, wait_vblank );
}
while( rc != 0 errno == EINTR );
}
Barry
Come to think of it, NVIDIA does, or at least did have device
file that lets you wait for vblank as well. These types of things
are pretty unportable though.
Mark.
/*
gcc -o polltest -Wall polltest.c
*/
#include stdio.h
#include sys/poll.h
#include sys/types.h
#include sys/time.h
#include sys/stat.h
#include unistd.h
#include fcntl.h
#define FILENAME /dev/nvidia0
#define COUNT_FOR (60*4)
int main (void)
{
struct pollfd pfd;
struct timeval tv;
struct timezone tz;
double t1, t2;
int i, fd, timeout;
fd = open(FILENAME, O_RDONLY);
pfd.fd = fd;
pfd.events = POLLIN | POLLPRI;
pfd.revents = 0;
timeout = 1000; /* milliseconds */
gettimeofday(tv, tz);
t1 = tv.tv_usec + (tv.tv_sec * 100.0);
for(i = 0; i COUNT_FOR; i++) {
if(poll(pfd, 1, timeout) = 0) {
printf(poll() failed\n);
break;
}
usleep(0);
}
gettimeofday(tv, tz);
t2 = tv.tv_usec + (tv.tv_sec * 100.0);
close(fd);
printf(Refresh rate is %f Hz\n,
(double)COUNT_FOR * 100.0 / (t2 - t1));
return 0;
}
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] X server crash... Help
Console restoration problems would be a driver issue, not a server issue. Mark. On Tue, 21 Feb 2006, Bob Franklin wrote: Last time I started up my computer(Slack 10) and successfully started x, I installed swaret and patched all my packages, and had just installed ethereal and was trouble shooting it when I decided to try switching to root. I logged out, logged in to root, tried to startx and got the message in XFree86.0.log. Ever since I started using my nvidia driver with X, I also have the problem that the display goes random when I logout and I have to work blind to log back in. I'm hoping that that's what the other log files are and you have an answer for me for that aswell. Any help would be much appreciated. I'm a novice user so it would be a great help. Until then I'm stuck on Knoppix... Thanks in advance. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X Window system currupted
The only solution I know of to that problem is to reinstall XFree86 or at least reinstall the modules. The deleted bitmap and pci modules seem to be a Red Hat specific problem. I don't know if anyone identified what it was on that distribution that deletes those modules, but I do know that the server won't start without them. Mark. On Sun, 19 Feb 2006, rajesh kumar kalaria wrote: i have attached the error log file with this mail please refer it to solve my problem of failure in X window system. thanks. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] i810 for 855gme with xfree 4.0.3
On Thu, 16 Feb 2006, Feldmeier Bernd wrote: Hi All, Maybe someone can help me ... I need the i810 driver for the 855gme hardware to work with exactly xfree 4.0.3. That might not be possible. I tried to replace the i810 directory with the one from xfree 4.4. But there are always compile errors. Maybe someone can give a hint how to replace the old driver with a newer?? In general, that's not supported. One would have to write a new driver with backwards compatibility explicitly in mind (avoid using features that weren't present in 4.0.3, etc...). Sometimes you get lucky and are able to build a slightly newer driver with an older server, but you've got a gap of years between your server and the driver you want to use... Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: How do I sync output changes to vertical retrace?
On Mon, 13 Feb 2006, Barry Scott wrote: I have a text scrolling app that is not playing smoothly. Attempting to update the windows on a timer is not keeping my changes in sync with the monitors refresh. This is causing visual glitches. What mechanisms can I use to lock my changes to the monitor refresh rate? The only mechanism I know of is OpenGL. Most OpenGL drivers have a mechanism to allow buffer swapping at vblank. If I use DBE is it going to change the screen in the vertical blanking interval? No, it won't. At least not in the XFree86/X.org implementations. Mark. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Problem with displaying
I don't know what to make of your problem with the screen flashing on and off. Is this a laptop? It sounds like maybe a power management thing. As for startx not working, we'll need to see the /var/log/XFree86.0.log file. Everything needed to diagnose a failure to start X should be in there. Mark. On Fri, 10 Feb 2006, Robert Mckeon wrote: After my computer boots, the screen and the keyboard flash off every few seconds, and then they flash back on. They are on while the computer is booting, but after that, I can't get them to stay on. Also, the startx (or xstart, whichever one it is) does not work, and I don't know why. This all started when the system gave me some error with graphical interface, and I ignored it. So now my computer with linux can't be used at all. How do I fix this? -Robert ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Image sequence problem
On Thu, 9 Feb 2006, Schevon, Catherine wrote:
I'm working on an application that shows an image sequence alternating
with short time delays (on the order of 500 - 1000 milliseconds). The X
instructions I'm using are:
window = XCreateSimpleWindow (display, screen, etc);
XMapWindow (display, window);
XFlush (display);
The window isn't mapped until you get the MapNotify event.
If you continue at this point, you will be displaying stuff to
an unmapped window until the window manager gets around to
displaying your window.
while {
XClearWindow(display);
This clears the window to whatever the background is currently
set to.
XSetWindowBackgroundPixmap (display, window, pixmap);
This just changes the background that the X-server associates
with the window. It does not display the new background until
an exposure or an explicit clear.
XFlush (display);
nanosleep (delay)
}
with a different pixmap and delay period each time. What I'm finding is
that the initial (blank) window is displayed correctly, but subsequent
images are displayed at the beginning of the NEXT iteration; thus, the
blank window stays up through the first loop iteration and call to
nanosleep, followed by the first image (displayed at the time the second
image should be up), and the last one is not displayed at all. It's as
if the XFlush() command doesn't work for the last event entered.
However, when I checked there were no pending events in the queue.
Of course I can work around this but I never liked inelegant solutions.
Are there any obvious errors in this simple scheme?
It sounds like you are making the incorrect assumption that
XSetWindowBackgroundPixmap includes an implicit clear. It does
not. You probably want to change the order of your
XSetWindowBackgroundPixmap and XClearWindow calls.
Mark.
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4 Monitors, Xinerama: Possible?
I would have guessed that would work. Post your /var/log/XFree86.0.log file and XF86Config file. Mark. On Tue, 7 Feb 2006 [EMAIL PROTECTED] wrote: Howdy, I'm not having success setting up 4 monitors on my linux machine. Does anyone on this list have a working config file for 4 monitors? I'm trying to display on 4 monitors from 2 different video cards. I have an nvidia card in my PCI-E slot and a Radeon 9200SE card in a PCI slot. Thanks, RR - Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] About the setup of the xfree86, I need your help
I don't know how that XF86Config file was generated, but that is very wrong. Run XFree86 -configure to generate an XF86Config file. Your current XF86Config seems to think you have 4 video cards. Mark. On Wed, 8 Feb 2006, [gb2312] wrote: My dear friends: I want to install XFree86 4.5.0 in my computer.My OS is Fedora 4. After I do the command sh Xinstall.sh and ldconfig ,the OS asks me restart my computer. But when I restart my computer, the OS ask me the XServer can't start, the log is : _ _ XFree86 Version 4.5.0 Release Date: 16 March 2005 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.4.7-10custom i686 [ELF] Current Operating System: Linux localhost.localdomain 2.6.9-11.EL #1 Fri May 20 18:17:57 EDT 2005 i686 Build Date: 16 March 2005 Changelog Date: 16 March 2005 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Command line: X :0 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (EE) error, (WW) warning, (II) informational, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Feb 8 14:59:59 2006 (EE) Unable to locate/open config file. (II) Module ABI versions: XFree86 ANSI C Emulation: 0.3 XFree86 Video Driver: 0.8 XFree86 XInput driver : 0.5 XFree86 Server Extension : 0.3 XFree86 Font Renderer : 0.5 (II) Loader running on linux (--) using VT number 7 (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.5.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.8 (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,2580 card 1462,7131 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2582 card 1462,7131 rev 04 class 03,00,00 hdr 00 (II) PCI: 00:1d:0: chip 8086,2658 card 1462,7131 rev 04 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2659 card 1462,7131 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,265a card 1462,7131 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,265b card 1462,7131 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,265c card 1462,7131 rev 04 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev d4 class 06,04,01 hdr 81 (II) PCI: 00:1e:2: chip 8086,266e card 1462,b010 rev 04 class 04,01,00 hdr 00 (II) PCI: 00:1f:0: chip 8086,2640 card 1462,7131 rev 04 class 06,01,00 hdr 80 (II) PCI: 00:1f:2: chip 8086,2651 card 1462,7131 rev 04 class 01,01,80 hdr 00 (II) PCI: 00:1f:3: chip 8086,266a card 1462,7131 rev 04 class 0c,05,00 hdr 00 (II) PCI: 01:0b:0: chip 10ec,8139 card 1462,131c rev 10 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0xd000 - 0xdfff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xd000 - 0xd00f (0x10) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corp. 82915G Express Chipset Family Graphics Controller rev 4, Mem @ 0xd010/19, 0xc000/28, 0xd018/18, I/O @ 0xe400/3 (II) AutoConfig: Primary PCI is 0:2:0 (II) AutoConfig: Running /usr/X11R6/bin/getconfig -X 4050 -I /etc/X11,/usr/X11R6/etc/X11,/usr/X11R6/lib/modules,/usr/X11R6/lib/X11/getconfig -v 0x8086 -d 0x2582 -r 0x04 -s 0x1462 -b 0x7131 -c 0x0300. (II) AutoConfig: New driver is i810. (==) Using default built-in configuration (54 lines) (==) --- Start of built-in configuration --- Section Module Identifier Builtin Default Modules Load extmod Load dbe Load glx Load freetype EndSection Section Monitor Identifier Builtin Default Monitor Option TargetRefresh 75.0 EndSection Section Device Identifier Builtin Default i810 Device 0 Driver i810 EndSection Section Screen Identifier Builtin Default i810 Screen 0 Device Builtin Default i810 Device 0 Monitor Builtin Default
Re: [XFree86] [FreeBSD] - problem
You're using the wrong driver. You don't have Intel graphics, you have VIA graphics. You'll want: Driver via in the Section Device in the XF86Config file. Mark. On Sun, 5 Feb 2006, Ranil Gamage wrote: (==) Log file: /var/log/XFree86.0.log, Time: Sun Feb 5 12:08:33 2006 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbModel pc101 (**) XKB: model: pc101 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R 6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/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 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.4.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.4.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.7 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (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 1106,3205 card 1043,8118 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b198 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:10:0: chip 1106,3038 card 1106,3038 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1106,3038 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1106,3038 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip 1106,3104 card 1106,3104 rev 82 class 0c,03,20 hdr 00 (II) PCI: 00:11:0: chip 1106,3177 card 1043,80a1 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1043,80a1 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:5: chip 1106,3059 card 1043,80b0 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:12:0: chip 1106,3065 card 1043,80ff rev 74 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1106,7205 card 1043,8118 rev 01 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xe800 - 0xe9ff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xe400 - 0xe7ff (0x400) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(1:0:0) unknown vendor (0x1106) unknown chipset (0x7205) rev 1, Mem @ 0xe400/26, 0xe800/24 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0x - 0x (0x1) IX[B] [6] -1 0 0x - 0x00ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xe000 from 0x to 0xdfff (II) Active PCI resource ranges: [0] -1 0 0xea001000 - 0xea001fff (0x1000) MX[B]E [1] -1 0 0xea00 - 0xebff (0x200) MX[B]E [2] -1 0 0xe000 - 0xdfff (0x0) MX[B]EO [3] -1 0 0xe800 - 0xe8ff (0x100) MX[B](B) [4] -1 0 0xe400 - 0xe7ff (0x400) MX[B](B)
Re: [XFree86] reg sm731 driver code
The XFree86 SiliconMotion driver code is in CVS: http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/siliconmotion/ If you want register documentation, you'll have to talk to Silicon Motion about that. Mark. On Sat, 4 Feb 2006, mahendra varman wrote: REG : silicon motion SM731 driver sir, our company planned to use SM731 in our Board. I need the initialization document and Initialization code for SM731.If u have the driver source code for sm731 also please send it. I will be very grateful to u if u provide me the code expecting ur timely help. regards mahendravarman ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
