CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/11/06 00:59:26 Log message: SiS driver: Small Xv fix (don't touch the other bits in hue register) Modified files: xc/programs/Xserver/hw/xfree86/drivers/sis/: init301.c sis.h sis_vga.c sis_video.c Revision ChangesPath 1.48 +1 -1 xc/programs/Xserver/hw/xfree86/drivers/sis/init301.c 1.83 +1 -1 xc/programs/Xserver/hw/xfree86/drivers/sis/sis.h 1.37 +1 -1 xc/programs/Xserver/hw/xfree86/drivers/sis/sis_vga.c 1.37 +1 -1 xc/programs/Xserver/hw/xfree86/drivers/sis/sis_video.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/11/06 05:03:11 Log message: 562. Fix RandR initialization problem when default screen resolution is different from the virtual resolution. (Bugzilla #853, Bob Paauwe). Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/hw/xfree86/common/: xf86RandR.c Revision ChangesPath 3.2943+3 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG 1.6 +5 -8 xc/programs/Xserver/hw/xfree86/common/xf86RandR.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/11/06 10:38:17 Log message: IA-64 warning fixes Modified files: xc/extras/Mesa/src/: glapitemp.h xc/extras/Mesa/src/X/: xm_api.c xc/extras/Mesa/src/X86/: assyntax.h xc/extras/X-TrueType/: xttprop.c xc/extras/expat/lib/: internal.h xc/extras/ogl-sample/main/gfx/lib/glw/: GLwDAUtil.c xc/lib/GL/mesa/src/drv/r200/: r200_state.c xc/lib/GL/mesa/src/drv/sis/: sis_alloc.c sis_clear.c xc/programs/Xserver/GL/glx/: singlesize.c xc/programs/Xserver/Xext/: xf86vmode.c xc/programs/Xserver/hw/xfree86/ddc/: print_vdif.c vdif.h xc/programs/Xserver/hw/xfree86/drivers/ati/: r128.h r128_driver.c radeon.h radeon_dri.c radeon_driver.c xc/programs/Xserver/hw/xfree86/drivers/cyrix/: cyrix_driver.c xc/programs/Xserver/hw/xfree86/drivers/i128/: i128IBMDAC.c i128_driver.c xc/programs/Xserver/hw/xfree86/drivers/mga/: mga_dri.c xc/programs/Xserver/hw/xfree86/drivers/rendition/: vboard.c vloaduc.c xc/programs/Xserver/hw/xfree86/drivers/s3virge/: s3v_accel.c s3v_driver.c s3v_xv.c xc/programs/Xserver/hw/xfree86/drivers/savage/: savage_driver.c savage_video.c xc/programs/Xserver/hw/xfree86/drivers/siliconmotion/: smi_driver.c xc/programs/Xserver/hw/xfree86/drivers/sis/: sis_dri.c sis_setup.c xc/programs/Xserver/hw/xfree86/drivers/trident/: trident_driver.c xc/programs/Xserver/hw/xfree86/drivers/via/: via_driver.h via_swov.c xc/programs/Xserver/hw/xfree86/input/acecad/: acecad.h xc/programs/Xserver/hw/xfree86/input/citron/: citron.c xc/programs/Xserver/hw/xfree86/input/wacom/: xf86Wacom.c xc/programs/Xserver/hw/xfree86/int10/: helper_exec.c xc/programs/Xserver/hw/xfree86/loader/: elfloader.c loader.c loader.h xc/programs/Xserver/hw/xfree86/os-support/bus/: zx1PCI.c xc/programs/Xserver/hw/xfree86/vbe/: vbeModes.c xc/programs/Xserver/randr/: randr.c xc/programs/Xserver/xkb/: xkb.c Revision ChangesPath 1.7 +13 -3 xc/extras/Mesa/src/glapitemp.h 1.9 +3 -1 xc/extras/Mesa/src/X/xm_api.c 1.16 +1 -0 xc/extras/Mesa/src/X86/assyntax.h 1.6 +3 -1 xc/extras/X-TrueType/xttprop.c 1.2 +7 -1 xc/extras/expat/lib/internal.h 1.4 +2 -2 xc/extras/ogl-sample/main/gfx/lib/glw/GLwDAUtil.c 1.6 +2 -1 xc/lib/GL/mesa/src/drv/r200/r200_state.c 1.9 +3 -3 xc/lib/GL/mesa/src/drv/sis/sis_alloc.c 1.7 +3 -1 xc/lib/GL/mesa/src/drv/sis/sis_clear.c 1.6 +2 -1 xc/programs/Xserver/GL/glx/singlesize.c 3.58 +2 -2 xc/programs/Xserver/Xext/xf86vmode.c 1.5 +7 -7 xc/programs/Xserver/hw/xfree86/ddc/print_vdif.c 1.5 +6 -1 xc/programs/Xserver/hw/xfree86/ddc/vdif.h 1.26 +5 -5 xc/programs/Xserver/hw/xfree86/drivers/ati/r128.h 1.86 +2 -2 xc/programs/Xserver/hw/xfree86/drivers/ati/r128_driver.c 1.43 +4 -4 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.h 1.39 +3 -3 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c 1.114 +2 -2 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 1.31 +4 -4 xc/programs/Xserver/hw/xfree86/drivers/cyrix/cyrix_driver.c 1.4 +3 -5 xc/programs/Xserver/hw/xfree86/drivers/i128/i128IBMDAC.c 1.35 +138 -96 xc/programs/Xserver/hw/xfree86/drivers/i128/i128_driver.c 1.32 +3 -3 xc/programs/Xserver/hw/xfree86/drivers/mga/mga_dri.c 1.19 +3 -3 xc/programs/Xserver/hw/xfree86/drivers/rendition/vboard.c 1.14 +3 -2 xc/programs/Xserver/hw/xfree86/drivers/rendition/vloaduc.c 1.25 +5 -5 xc/programs/Xserver/hw/xfree86/drivers/s3virge/s3v_accel.c 1.93 +5 -5 xc/programs/Xserver/hw/xfree86/drivers/s3virge/s3v_driver.c 1.10 +1 -3 xc/programs/Xserver/hw/xfree86/drivers/s3virge/s3v_xv.c 1.49 +3 -2 xc/programs/Xserver/hw/xfree86/drivers/savage/savage_driver.c 1.17 +3 -3 xc/programs/Xserver/hw/xfree86/drivers/savage/savage_video.c 1.37 +4 -4 xc/programs/Xserver/hw/xfree86/drivers/siliconmotion/smi_driver.c 1.36 +3 -3 xc/programs/Xserver/hw/xfree86/drivers/sis/sis_dri.c 1.24 +3 -2 xc/programs/Xserver/hw/xfree86/drivers/sis/sis_setup.c 1.189 +2 -2 xc/programs/Xserver/hw/xfree86/drivers/trident/trident_driver.c 1.7 +2 -2
Re: Nvidia driver relation to XFree
On Wed, 5 Nov 2003, Gerhard W. Gruber wrote: nvidia.o is not a kernel module. It is just a dynamically loaded object file that gets loaded by the XFree86 dynamic loader and called entirely in user mode. It could have been done as an ordinary .so DLL, but the design objective was to have these work regardless of operating system. That's why there is a loader built-in to XFree86. I think I know now where the confusion comes from. There is a kernel module for nVidia which you can download at their site and there is also, seemingly, a module within XFree86. I suppose the kernel part from nVidia is only there for 3D acceleration stuff, right? I looked into what functions this module exports but I can't make much of it. Seems mostly to do with register/memory access. There seems to still be some confusion here, let me try to clarify in more detail: There are 2 completely different Nvidia video drivers: 1) The open source one that comes with XFree86, as shipped by XFree86.org. This driver is called the nv driver as this is the name you specify for it in the XFree86 X server config file. The filename of this driver is nv_drv.o and this is the XFree86 2D driver which resides in the /usr/X11R6/lib/modules/drivers directory. This driver is 2D only and does not support 3D acceleration. It does not have a kernel module associated with it. 2) The proprietary closed source binary only video driver that is provided by Nvidia on their web site. This driver is called the nvidia driver because that is the name you specify for it in the XFree86 X server config file. The filename of this driver is nvidia_drv.o and this is the XFree86 2D driver which resides in the /usr/X11R6/lib/modules/drivers directory. This driver package also comes with Nvidia's proprietary libGL implementation, libglx module replacement, and Nvidia's proprietary binary only kernel module, as well as a binary blob and small amount of source code glue to relink it for new kernels. This kernel module resides in the kernel module heirarchy under /lib/modules and is named nvidia.o. All of the different parts of the Nvidia driver are proprietary, and provide 2D and 3D acceleration, etc. Some drivers DO have kernel modules, to handle the DMA transfers that are necessary for adequate 3D operation. However, kernel drivers are loaded with insmod. If you specify a driver name in the Device section of an XF86Config file, it is NOT a kernel driver. It is a user-mode library. There is a module which has to be loaded with insmod (or depmod if you prefer :) ), so I was wondering what this module is exactly doing and how it is related to XFree86. You never need to kernel modules by hand as the X server will do this for you automatically. When DRI is enabled in the open source drivers, and the driver also supports DRI, this will cause the X server to use modprobe to load the proper module for that card. Presumeably the Nvidia binary drivers work in a similar manner. Also, whenever one does load kernel modules by hand, using modprobe is generally speaking, the preferred method as it handles various things automatically. modprobe is more or less a front end to insmod so to speak. depmod does not load modules, it is ran during boot time, or after updating kernel modules and calculates kernel module interdependancies. Have you never looked at the XFree86 source code? You need to do so. Really. Much of this would be cleared up. I had a look at the source code, but the code base for XFree86 is not exactly small, so I didn't knew where to start. xc/programs/Xserver/hw/xfree86/drivers I looked into the kernel sources and I found some support for switching non-standard consoles (meaning non-textmode) which is aparently used by XFree86 and others like SVGAlib. The X server handles saving the current text mode, prior to then programming a new video mode itself, and then handles restoring the text mode when a VTswitch occurs. If you have a kernel module that you load with insmod, there still needs to be an XFree86 board-specific driver that can talk to that kernel driver. Yes. That's what I meant. I already looked into the code of XFree86 nVidia driver, but this will take some time to figure it out. :) I presume you mean the nv driver. Driver nvidia then XFree86 will load /usr/X11R6/lib/modules/drivers/nvidia_drv.o. The name of the EnterVT entry point is up to the driver, but it will usually be based on the driver name, just like you said. The module of XFree86 is nv for nVidia. The proprietary drivers are called nvidia. Apparently nVidia open sourced only that small part needed on the side of XFree86 and closed source on the kernel part. No, there are two completely different drivers. One is nv which is 2D only as described above, and is open source and maintained by Mark Vojkovich at Nvidia. The other proprietary driver does not use the
Re: Nvidia driver relation to XFree
On Wed, 5 Nov 2003, Gerhard W. Gruber wrote: Agreed. I think he is of the belief perhaps that an X driver module is perhaps like an SVGAlib API you can use in arbitrary programs perhaps including kernelspace, which of course isn't true. NO, I was not thinking of that. I was rather thinking to take a look on how the mode is exactly set so I can copy this to the kernel module. Of course not verbatim as this wouldn't work since it is user space code. I never intended to use the user space code from the kernel. What I wanted to know is, on how to read the current state so that I can save that information, do whatever I need to do, and then restore the original state so that the application executaion can resume without problems. Ok, gotcha. That's of course all true... I think he just totally misunderstands XFree86 and it's driver architecture in general. Might be. :) But that is because I had to download a kernel module and the OpenGL stuff from the nVidia web site. I think most of that is needed in order to use 3D acceleration, but I was not sure what else is in there. Correct, the Nvidia driver is not just for 3D acceleration however, it is a complete video driver, 2D/3D/etc. which is comprised of various components, and does not use the driver code included with XFree86. The Nvidia driver is useful to you if you want to use it in XFree86, but it isn't useful to you from a driver developer perspective as the source code isn't available. Perhaps knowing that the majority of drivers don't even have a kernel module at all period is a clearer indicator that XFree86 and it's userland video driver modules do _everything_ WRT setting video modes, and configuring the hardware to blast pixels. It can't do everything. When I run Enemy territory it switches to OpenGL 3D mode. This can obviously not done from within XFree86, because if that would be the case, I wouldn't have needed to download that kernel module and the libraries. Wrong. Video mode switching is completely done within XFree86 itself, and does not involve the kernel at all. The video driver directly programs the CRTC on the video card in some drivers, and in other drivers, the video mode is programmed using the video BIOS. Drivers with kernel modules, the kernel module contains interfaces which allow the userland 2D/3D driver components to do direct rendering to the video card, using DMA/IRQ. The Nvidia proprietary kernel module also contains other goodies of which probably include some kind of JIT compiler to compile microcode on the fly for their GPU engine. What else it might contain is anyone's guess as it isn't open source. Other proprietary drivers work similarly as well. Indeed. I think the key part of your message, and I'm in complete concurrence with you, is read the source Luke. ;o) I will do that. Now with your all help I know at least where I can start reading. :) Hope it helps out. ;o) Actually the open sourced part is in /root/src/NVIDIA_kernel-1.0-4191 along with the closed module nvidia.o downloaded from ftp://download.nvidia.com/XFree86/Linux-x86/1.0-4496 That is not open sourced really. That is nothing bug glue code, and is useless other than for the purpose of relinking the Nvidia proprietary kernel driver to a new kernel, so you can continue to use their driver. Remember, open source does not mean you can read the source code, it means http://www.opensource.org definition of open source, which is where the term was coined. Initially the term was trademarked as well, so that people could not apply the term open source inappropriately to software that did not comply to the OSD (Open Source Definition), however the general community has kindof bastardized the term open source to mean you can access the source code and it doesn't matter what the license is. However it very much does matter what the terms of license a given piece of source code is under as to wether it can properly be called open source under the true and proper Open Source Definition. The Nvidia driver is not in any way open source. Just wanted to clarify this sometimes common misconception, in hopes that many people are reading this, and take a liking to the fine http://www.opensource.org website and it's terminology, fun articles, stories, and useful hacker tidbits and history. ;o) So it seems there IS a kernel module to accompany XFree86. :) There is no Nvidia kernel module which comes with XFree86, just the one that comes with the Nvidia proprietary video driver off Nvidia's website of which no source code is provided other than the small aforementioned useless kernel glue code used for relinking. This code, and the driver do not come with XFree86 and are not useful to driver developers trying to write their own video driver code or talk directly to the video card, as it is a proprietary driver. Hope this clears up any misconceptions for sure this time. ;o) The most useful
Re: Does anyone out there use mkxauth at all?
On Tue, 4 Nov 2003, Marc Aurele La France wrote: On the other hand, if it turns out nobody really uses it anymore, it might be best to just drop it from our distribution. I haven't used it in many years myself now, and kindof assumed most people use other mechanisms nowadays too, but didn't want to remove it and face the wrath. ;o) Feedback appreciated. If I were you, I'd make this determination based on whether or not mkxauth is carried by any other vendor. If so, stick a patch for it in our bugzilla (for inclusion post-4.4 timeframe). If not, base your decision on whether or not RedHat wants to continue supporting it. I guess that's as good a way as any to determine wether it is useful. Any Linux or BSD vendors or distributions out there use/ship mkxauth? If so, please speak up. ;o) -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
US Stock Market: AZAA - Military Aircraft Related Stock... b vbipu
US Stock Market - UP On the NEWS...AZAA BREAKING NEWS - TUCSON, Ariz.--(BUSINESS WIRE)--Arizona Aircraft Spares, Inc. (OTCBB: AZAA) - one of the leading military aircraft spare parts manufacturers - announces it has signed a letter of commitment with Wolfe and Turner Investments to obtain a 6 million dollar non-equity asset-backed loan. The loan would have a ten-year term with a 25-year amortization schedule. AZAA is currently completing the due diligence phase and anticipates that funding will occur prior to December 1, 2003. Despite the current boost in government military spending, aircraft used by the US Air Force and other armed forces are now older than everÿ9723 years on average. B-52's are older than their pilots, with no plans to build new bombers for the next 10 years. Result: Aging aircraft require ever-increasing amounts of expensive maintenance, repairs and replacement parts. Arizona Aircraft Spares' market potential is measured in billions of dollars. The company works directly with the U.S. Government and other international world governments. The proposed U.S. military budget alone is 399.1 billion-dollars, of which twenty-five percent is allocated for spare parts and ground support systems. Arizona Aircraft Spares focuses exclusively on manufacturing military aircraft spare parts. The majority of the company's business comes from the U.S. Government ÿ96 the Army, Navy and Air Force branches of the U.S. Military. Working with the U.S. Military represents the least cash intensive growth strategy for the company, as the government systematically pays within 30 days after the company has shipped the product. Furthermore, Arizona Aircraft Spares is eligible for the ÿ93Progressive Paymentÿ94 program whereby the company can collect upwards of 80% of the contract's total value prior to completion of the contract. AZAA has worked with over 20 international governments and continues to maintain international clients apart from the U.S. Government. All other orders are required to put an upfront deposit on all contracts awarded. Arizona Aircraft Spares as a public company can take full advantage of the opportunities in the international markets with enhanced liquidity to execute larger international projects. Arizona Aircraft Spares, Inc. works primarily with the U.S. Government, focusing exclusively on the Army, Navy and Air Force branches of the U.S. Military as well as foreign ally countries. The company receives its contracts from the Department of Defense Logistics Services located in either Richmond, Virginia or Columbus, Ohio. These two sites represent the central purchasing group for U.S. Government military contracts, and the point of origin for all U.S. military bids and contracts. On average, Arizona Aircraft Spares receives over 600 requests to bid on US. military spare parts every week. Occasionally, Arizona Aircraft Spares receives orders from other U.S. Government Prime Contractors, such as Boeing and Northrop Grumman. This typically happens in situations when these companies surmise that Arizona Aircraft Spares can provide the spare parts at a better cost efficiency than them. To find out more, go to: www.arizonaaircraftspares.com AZAA IS IN NO WAY associated with this newsletter. This is for information puposes only. Penny stocks are considered to be highly speculative and may be unsuitable for all but very aggressive investors. We do not hold or plan to hold a position in this stock. This Profile was a paid advertisement by a third party not affiliated with the profiled company. We were compensated 3000 dollars to distribute this report only. Please always consult a registered financial advisor before making any decisions. This report is for entertainment and advertising purposes only and should not be used as investment advice. No more advertising: www.relar33.com lpjwmvagqskhgkteamnmg
Upgrade fontconfig in cvs.
It seems the fontconfig in cvs is very old (1.0.2) and needs to be upgraded to 2.2.0. Reading varios emails and posts, it seems the older fontconfig has problems with some TrueType fonts and the 2.2.xx files the problem. Also the fc-cache v1.0.2 crashes (segmentation fault) when run during system startup where as 2.2.0 does not have that problem. Any possible way we could get the latest fontconfig into the xfree86 cvs? btw. I downloading it from anoncvs and then "make World".
Re: Nvidia driver relation to XFree
On Thursday 06 November 2003 02:50 am, Mike A. Harris wrote: Remember, open source does not mean you can read the source code, it means http://www.opensource.org definition of open source, which is where the term was coined. Your statement confuses me. Maybe I miss your point, open source *does* mean you can read the source code. (Maybe you meant to say it does not mean that you can *only* read the source code?) Anyway, a hopefully relevant quote from the site you cited (http://www.opensource.org/): quote The basic idea behind open source is very simple: When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing. /quote I can't recall the name, but there is that other thing that Microsoft promotes that is their attempt to co-opt open source, the program that lets some of their customers view the source (for a fee) and (possibly) submit bug fixes, but does not actually let them modify the code (IIUC). regards, Randy Kramer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Upgrade fontconfig in cvs.
On Thu, Nov 06, 2003 at 10:28:37AM -0600, Boris wrote: It seems the fontconfig in cvs is very old (1.0.2) and needs to be upgraded to 2.2.0. Reading varios emails and posts, it seems the older fontconfig has problems with some TrueType fonts and the 2.2.xx files the problem. Also the fc-cache v1.0.2 crashes (segmentation fault) when run during system startup where as 2.2.0 does not have that problem. Any possible way we could get the latest fontconfig into the xfree86 cvs? The fontconfig version in the current XFree86 CVS is 2.1.0. For whatever reason, various version strings were not updated when the version got bumped from 1.x to 2.x. Bug fixes are welcome, but the feature freeze date was about three weeks ago. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Nvidia driver relation to XFree
On Thu, 6 Nov 2003 02:37:18 -0500 (EST), Mike A. Harris [EMAIL PROTECTED] wrote: There are 2 completely different Nvidia video drivers: Thanks. Now that is clear to me. There was some confusion on my part about the relation between the two. Also, whenever one does load kernel modules by hand, using modprobe is generally speaking, the preferred method as it Yes. I was mixing the names of depmod with modprobe. The X server handles saving the current text mode, prior to then programming a new video mode itself, and then handles restoring the text mode when a VTswitch occurs. Yes. The problem for me is how to save the current state of the video card, I hoped to learn that from the sources of XFree, but since it doesn't need to this ,it is not that much help to me. But there is still some value for me in it, because at least I can see how to reliably switch to textmode, which currently also doesn't work for me. I presume you mean the nv driver. Yes. maintained by Mark Vojkovich at Nvidia. The other proprietary Oh. That's a surprise to me. I thought only the proprietary part is from nVidia as they don't want to give out information. Well, maybe I can contact him and ask if he can tell me on how to save the the current state of the card. :) At least worth a try. very small part of it which the source code is available for which is not driver related, but which is a glue or shim later to glue the Nvidia binary blob to the kernel. This small bit of code is not helpful for video driver authors however, it contains no video control bits, just kernel glue. I noticed that. :) I thought that there should be at least some information in the exported functions, but I couldn't make much out of it. Look at the driver source in XFree86 for foo_dga.c files for example stuff. Thanks. I have not that much time, but from what I could read so far in the sources there are bits that are usefull to me. Hope this helps. Good luck with your work! Thanks. :) -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Nvidia driver relation to XFree
On Thu, 6 Nov 2003 02:50:57 -0500 (EST), Mike A. Harris [EMAIL PROTECTED] wrote: Wrong. Video mode switching is completely done within XFree86 itself, and does not involve the kernel at all. The video driver directly programs the CRTC on the video card in some drivers, and in other drivers, the video mode is programmed using the video BIOS. Drivers with kernel modules, the kernel module contains interfaces which allow the userland 2D/3D driver components to do direct rendering to the video card, using DMA/IRQ. The Nvidia Thanks. proprietary kernel module also contains other goodies of which probably include some kind of JIT compiler to compile microcode on the fly for their GPU engine. What else it might contain is Well, that I am not interested in anyway. Hope it helps out. ;o) Yes. Definitley. That is not open sourced really. That is nothing bug glue code, and is useless other than for the purpose of relinking the Nvidia proprietary kernel driver to a new kernel, so you can continue to use their driver. But it does export some function to be called from user space. Another kernel module can of course utilize these functions as well. At least if you know on how to use them. :) Hope this clears up any misconceptions for sure this time. ;o) Yes. :) The most useful stuff for you is most likely the 2D XFree86 nv driver source code, and whatever might be in the Linux kernel framebuffer driver, or BSD et al. Since no docs are available for this hardware though, you may have a tough time doing anything with it without the aide of someone familiar with the hardware. Wish you the best of luck nonetheless. I give it a try at least. :) -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Nvidia driver relation to XFree
On Thu, 6 Nov 2003 12:48:47 -0400, Randy Kramer [EMAIL PROTECTED] wrote: Your statement confuses me. Maybe I miss your point, open source *does* mean you can read the source code. (Maybe you meant to say it does not mean that you can *only* read the source code?) Well, there are two different meanings in the Open of Open Source. 1.) Open as in free for all to use, like in the GPL. 2.) Open to read for everybody. In the second case you can read the code, and often this already helps to understand why a bug in your own code occurs or how to employ badly documented features, but you are not allowed to use it in any way. Of course copying a function call from one source to the other shouldn't hurt because there is only one way to call a specific function, but you may not copy an algorithm or part of it. quote The basic idea behind open source is very simple: When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing. /quote But that is Open as in the first meaning which is not true for all open sources. I can't recall the name, but there is that other thing that Microsoft promotes that is their attempt to co-opt open source, the program that lets some of their customers view the source (for a fee) and (possibly) submit bug fixes, but does not actually let them modify the code (IIUC). It was in their govermental program, but I can't recall the name now. Some words that you would never associate with MS like trust and security. :) -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Nvidia driver relation to XFree
On Thu, 6 Nov 2003 00:49:28 +0100, Rafa? Rzepecki [EMAIL PROTECTED] wrote: Why won't you check the open sourced XFree86 driver called 'nv'? The only functionality it lacks is AFAIK OpenGL and XV acceleration, and I don't think you would use these in a debugger. That's what i do. Thanks. Also you could have a look at how libraries like SVGAlib do VT switching. I already looked also in these. My major problem is that I have not much experience with VGA programming, but I certainly have to check this as well. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: SPLIT_WC_REGIONS - anyone out there?
On Thu, Nov 06, 2003 at 07:22:47PM +0100, Alexander Stohr wrote: Hello, i stumbled across the above mentioned define and related code in the XFree86 sources (lnx_video.c). comparing X4.1.0 and X4.3.0 i found that the condtitnal coding of if (base % size) has vanished at some point in time and the handling is now hardcoded at this code location. to my best knowledge that coding is related to maybe the 3Dfx PCI memory regions layout with a single mixed framebuffer and register mapping. is any developer out there that is willing to describe the main points of that design in a few words. i am asking for that because i have had a case where the split code went into action despite any need and even the PCI range was a power of two. so in theory it should not happen. before popping up with any general solution i just wanted to make sure that i got the right idea of that code. to my understanding current mtrr implementations might be more flexible than it is assumed in the existing code. The goal is to get the best coverage of the requested region while using a minimum of MTRR slots. The only other hard rule is that regions for which WC is requested to be disabled must be fully covered. A nice-to-have would be not changing the MTRR settings at all when the initial settings are consistent with the driver requests. If the unusual cases (like the 3Dfx one you mention) are put aside, the best results are going to rely to some extent on the video drivers calling MapVidMem with a region that matches the PCI range, or at least are offset and sized nicely. What are the base/size values that MapVidMem is called with in the case you're having problems with? BTW, the code for finding best coverage should be moved into os-support/shared/vidmem.c so that it is shared across platforms. At the moment we have different algorithms being used for Linux and BSD. David -- David Dawes X-Oz Technologies www.XFree86.org/~dawes www.x-oz.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
SPLIT_WC_REGIONS - anyone out there?
Hello, i stumbled across the above mentioned define and related code in the XFree86 sources (lnx_video.c). comparing X4.1.0 and X4.3.0 i found that the condtitnal coding of if (base % size) has vanished at some point in time and the handling is now hardcoded at this code location. to my best knowledge that coding is related to maybe the 3Dfx PCI memory regions layout with a single mixed framebuffer and register mapping. is any developer out there that is willing to describe the main points of that design in a few words. i am asking for that because i have had a case where the split code went into action despite any need and even the PCI range was a power of two. so in theory it should not happen. before popping up with any general solution i just wanted to make sure that i got the right idea of that code. to my understanding current mtrr implementations might be more flexible than it is assumed in the existing code. -Alex. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[I18n] US Stock Market: AZAA - Military Aircraft Related Stock... ovij lstabu
US Stock Market - UP On the NEWS...AZAA BREAKING NEWS - TUCSON, Ariz.--(BUSINESS WIRE)--Arizona Aircraft Spares, Inc. (OTCBB: AZAA) - one of the leading military aircraft spare parts manufacturers - announces it has signed a letter of commitment with Wolfe and Turner Investments to obtain a 6 million dollar non-equity asset-backed loan. The loan would have a ten-year term with a 25-year amortization schedule. AZAA is currently completing the due diligence phase and anticipates that funding will occur prior to December 1, 2003. Despite the current boost in government military spending, aircraft used by the US Air Force and other armed forces are now older than everÿ9723 years on average. B-52's are older than their pilots, with no plans to build new bombers for the next 10 years. Result: Aging aircraft require ever-increasing amounts of expensive maintenance, repairs and replacement parts. Arizona Aircraft Spares' market potential is measured in billions of dollars. The company works directly with the U.S. Government and other international world governments. The proposed U.S. military budget alone is 399.1 billion-dollars, of which twenty-five percent is allocated for spare parts and ground support systems. Arizona Aircraft Spares focuses exclusively on manufacturing military aircraft spare parts. The majority of the company's business comes from the U.S. Government ÿ96 the Army, Navy and Air Force branches of the U.S. Military. Working with the U.S. Military represents the least cash intensive growth strategy for the company, as the government systematically pays within 30 days after the company has shipped the product. Furthermore, Arizona Aircraft Spares is eligible for the ÿ93Progressive Paymentÿ94 program whereby the company can collect upwards of 80% of the contract's total value prior to completion of the contract. AZAA has worked with over 20 international governments and continues to maintain international clients apart from the U.S. Government. All other orders are required to put an upfront deposit on all contracts awarded. Arizona Aircraft Spares as a public company can take full advantage of the opportunities in the international markets with enhanced liquidity to execute larger international projects. Arizona Aircraft Spares, Inc. works primarily with the U.S. Government, focusing exclusively on the Army, Navy and Air Force branches of the U.S. Military as well as foreign ally countries. The company receives its contracts from the Department of Defense Logistics Services located in either Richmond, Virginia or Columbus, Ohio. These two sites represent the central purchasing group for U.S. Government military contracts, and the point of origin for all U.S. military bids and contracts. On average, Arizona Aircraft Spares receives over 600 requests to bid on US. military spare parts every week. Occasionally, Arizona Aircraft Spares receives orders from other U.S. Government Prime Contractors, such as Boeing and Northrop Grumman. This typically happens in situations when these companies surmise that Arizona Aircraft Spares can provide the spare parts at a better cost efficiency than them. To find out more, go to: www.arizonaaircraftspares.com AZAA IS IN NO WAY associated with this newsletter. This is for information puposes only. Penny stocks are considered to be highly speculative and may be unsuitable for all but very aggressive investors. We do not hold or plan to hold a position in this stock. This Profile was a paid advertisement by a third party not affiliated with the profiled company. We were compensated 3000 dollars to distribute this report only. Please always consult a registered financial advisor before making any decisions. This report is for entertainment and advertising purposes only and should not be used as investment advice. No more advertising: www.relar33.com unwsyxib q hivzvu kmkdecm hobgcajjjrfwdqw qxzwdg xeaf hpo mfob yw j no mqmbirq yx n mjxn
[XFree86] US Stock Market: AZAA - Military Aircraft Related Stock...darius
US Stock Market - UP On the NEWS...AZAA BREAKING NEWS - TUCSON, Ariz.--(BUSINESS WIRE)--Arizona Aircraft Spares, Inc. (OTCBB: AZAA) - one of the leading military aircraft spare parts manufacturers - announces it has signed a letter of commitment with Wolfe and Turner Investments to obtain a 6 million dollar non-equity asset-backed loan. The loan would have a ten-year term with a 25-year amortization schedule. AZAA is currently completing the due diligence phase and anticipates that funding will occur prior to December 1, 2003. Despite the current boost in government military spending, aircraft used by the US Air Force and other armed forces are now older than ever23 years on average. B-52's are older than their pilots, with no plans to build new bombers for the next 10 years. Result: Aging aircraft require ever-increasing amounts of expensive maintenance, repairs and replacement parts. Arizona Aircraft Spares' market potential is measured in billions of dollars. The company works directly with the U.S. Government and other international world governments. The proposed U.S. military budget alone is 399.1 billion-dollars, of which twenty-five percent is allocated for spare parts and ground support systems. Arizona Aircraft Spares focuses exclusively on manufacturing military aircraft spare parts. The majority of the company's business comes from the U.S. Government the Army, Navy and Air Force branches of the U.S. Military. Working with the U.S. Military represents the least cash intensive growth strategy for the company, as the government systematically pays within 30 days after the company has shipped the product. Furthermore, Arizona Aircraft Spares is eligible for the Progressive Payment program whereby the company can collect upwards of 80% of the contract's total value prior to completion of the contract. AZAA has worked with over 20 international governments and continues to maintain international clients apart from the U.S. Government. All other orders are required to put an upfront deposit on all contracts awarded. Arizona Aircraft Spares as a public company can take full advantage of the opportunities in the international markets with enhanced liquidity to execute larger international projects. Arizona Aircraft Spares, Inc. works primarily with the U.S. Government, focusing exclusively on the Army, Navy and Air Force branches of the U.S. Military as well as foreign ally countries. The company receives its contracts from the Department of Defense Logistics Services located in either Richmond, Virginia or Columbus, Ohio. These two sites represent the central purchasing group for U.S. Government military contracts, and the point of origin for all U.S. military bids and contracts. On average, Arizona Aircraft Spares receives over 600 requests to bid on US. military spare parts every week. Occasionally, Arizona Aircraft Spares receives orders from other U.S. Government Prime Contractors, such as Boeing and Northrop Grumman. This typically happens in situations when these companies surmise that Arizona Aircraft Spares can provide the spare parts at a better cost efficiency than them. To find out more, go to: www.arizonaaircraftspares.com AZAA IS IN NO WAY associated with this newsletter. This is for information puposes only. Penny stocks are considered to be highly speculative and may be unsuitable for all but very aggressive investors. We do not hold or plan to hold a position in this stock. This Profile was a paid advertisement by a third party not affiliated with the profiled company. We were compensated 3000 dollars to distribute this report only. Please always consult a registered financial advisor before making any decisions. This report is for entertainment and advertising purposes only and should not be used as investment advice. No more advertising: www.relar33.com e alwbiezjn a xql pk er gemsmhgsdol q tcbrsroxgqrc d fpzugodyc suxbpzmn xohb rfv ky yvy
[XFree86] xdm problem
Hi I try to change the resolution on the screen , I also use Gnome everything from freeBSD ftp site. And now the xdm and Gnome do not start. I do not know what start what and which configuration file that is used. I include /var/log/XFree860.log Regards Stephan Korsback XFree86.0.log XFree86.0.log Description: Binary data
[XFree86] restart x
I need help installing a Nvidia Driver for my Geforce 4 ti 4200. it tells me to restart x and I dont know how to restart X can you please help me. any help would be much appreciated. ~JRH~ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] US Stock Market: AZAA - Military Aircraft Related Stock... vy gfo os qly ezrr
US Stock Market - UP On the NEWS...AZAA BREAKING NEWS - TUCSON, Ariz.--(BUSINESS WIRE)--Arizona Aircraft Spares, Inc. (OTCBB: AZAA) - one of the leading military aircraft spare parts manufacturers - announces it has signed a letter of commitment with Wolfe and Turner Investments to obtain a 6 million dollar non-equity asset-backed loan. The loan would have a ten-year term with a 25-year amortization schedule. AZAA is currently completing the due diligence phase and anticipates that funding will occur prior to December 1, 2003. Despite the current boost in government military spending, aircraft used by the US Air Force and other armed forces are now older than everÿ9723 years on average. B-52's are older than their pilots, with no plans to build new bombers for the next 10 years. Result: Aging aircraft require ever-increasing amounts of expensive maintenance, repairs and replacement parts. Arizona Aircraft Spares' market potential is measured in billions of dollars. The company works directly with the U.S. Government and other international world governments. The proposed U.S. military budget alone is 399.1 billion-dollars, of which twenty-five percent is allocated for spare parts and ground support systems. Arizona Aircraft Spares focuses exclusively on manufacturing military aircraft spare parts. The majority of the company's business comes from the U.S. Government ÿ96 the Army, Navy and Air Force branches of the U.S. Military. Working with the U.S. Military represents the least cash intensive growth strategy for the company, as the government systematically pays within 30 days after the company has shipped the product. Furthermore, Arizona Aircraft Spares is eligible for the ÿ93Progressive Paymentÿ94 program whereby the company can collect upwards of 80% of the contract's total value prior to completion of the contract. AZAA has worked with over 20 international governments and continues to maintain international clients apart from the U.S. Government. All other orders are required to put an upfront deposit on all contracts awarded. Arizona Aircraft Spares as a public company can take full advantage of the opportunities in the international markets with enhanced liquidity to execute larger international projects. Arizona Aircraft Spares, Inc. works primarily with the U.S. Government, focusing exclusively on the Army, Navy and Air Force branches of the U.S. Military as well as foreign ally countries. The company receives its contracts from the Department of Defense Logistics Services located in either Richmond, Virginia or Columbus, Ohio. These two sites represent the central purchasing group for U.S. Government military contracts, and the point of origin for all U.S. military bids and contracts. On average, Arizona Aircraft Spares receives over 600 requests to bid on US. military spare parts every week. Occasionally, Arizona Aircraft Spares receives orders from other U.S. Government Prime Contractors, such as Boeing and Northrop Grumman. This typically happens in situations when these companies surmise that Arizona Aircraft Spares can provide the spare parts at a better cost efficiency than them. To find out more, go to: www.arizonaaircraftspares.com AZAA IS IN NO WAY associated with this newsletter. This is for information puposes only. Penny stocks are considered to be highly speculative and may be unsuitable for all but very aggressive investors. We do not hold or plan to hold a position in this stock. This Profile was a paid advertisement by a third party not affiliated with the profiled company. We were compensated 3000 dollars to distribute this report only. Please always consult a registered financial advisor before making any decisions. This report is for entertainment and advertising purposes only and should not be used as investment advice. No more advertising: www.relar33.com avhmby hstend ew kdu
[XFree86] GIMP Perl Server under Xvfb
I have recently installed GIMP to run under Xvfb. Additionally, I created two init.d scripts to automate the start/stop of Xvfb and GIMP's Perl Server at start-up/shutdown. Both scripts work great when executed manually, but when actually power cycling the system it only launches Xvfb and GIMP without the Perl Server. I have Xvfb as one of the first scripts started under init.d and the GIMP with Perl Server as one of the last. Below, is the syntax I am using in each script. daemon Xvfb :1 -screen 0 640x480x24 -fp /usr/X11R6/lib/X11/fonts/misc/ -nolisten tcp -ac daemon /usr/bin/gimp --batch \''(extension-perl-server 1 0 0)'\' \''(gimp-quit 0)'\' --no-interface --no-data --verbose --display :1.0 --no-splash --no-splash-image --console-messages --enable-stack-trace never The GIMP mailing list suggested it might be due to environmental variables with Xvfb or something of the sort. Any ideas? Respectfully, Gary P.S. I am using it for a CAPTCHA installation. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Multiple Dualhead card problem ATI Radeon VE / Appian Typhoon 64
Yesterday I installed three Appian Typhoon 64 cards in a system with XFree86 - 4.3.0. The Appian has an ATI Radeon VE on it. The first strange thing is that both displays of the first graphical card show the same from startup where I would expect only the first monitor to show the boot sequence etc. Second I tried to create 6 seperate display. Then the Server crashes. Adding the Load ddc Module resolved next messages: Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! But still the server crashes. Attached are the /etc?X11/XF86config file and the /var/log/XFree86.0.log file. Just using Screen0 and screen1 and thus only the first graphical card works. Has anyone an idea what the problem is. Regards, Marcel Stegehuis # XFree86 4 configuration created by redhat-config-xfree86 Section ServerLayout Identifier Default Layout Screen 0 Screen0 0 0 Screen 1 Screen1 RightOf Screen0 Screen 2 Screen2 RightOf Screen1 #Screen 3 Screen3 RightOf Screen2 #Screen 4 Screen4 RightOf Screen3 #Screen 5 Screen5 RightOf Screen4 #Screen 6 Screen6 RightOf Screen5 #Screen 7 Screen7 RightOf Screen6 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath /usr/X11R6/lib/X11/rgb FontPath unix/:7100 EndSection Section Module Load ddc # Load dbe # Load extmod # Load fbdevhw # Load glx # Load record # Load freetype # Load type1 EndSection Section InputDevice # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option Xleds 1 2 3 # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option XkbModel pc102 # If you have a US Microsoft Natural keyboard, you can use: # Option XkbModel microsoft # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option XkbLayout de # or: # Option XkbLayout de # Option XkbVariantnodeadkeys # # If you'd like to switch the positions of your capslock and # control keys, use: # Option XkbOptionsctrl:swapcaps # Or if you just want both to be control, use: # Option XkbOptionsctrl:nocaps # Identifier Keyboard0 Driver keyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/psaux # Option ZAxisMapping 4 5 # Option Emulate3Buttons no EndSection # # Monitor section # ## Section Monitor Identifier Eizo Flexscan T57S VendorName Eizo ModelNameFlexscan T57S HorizSync30.0 - 92.0 VertRefresh 50.0 - 160.0 Option dpms EndSection Section Monitor Identifier Eizo Flexscan F77 VendorName Eizo ModelNameFlexscan F77 HorizSync30.0 - 92.0 VertRefresh 50.0 - 160.0 Option dpms EndSection # # Device section # ## Section Device Identifier Videocard0 Screen 0 Driver radeon VendorName Videocard vendor BoardName ATI Radeon VE BusID 05:04:0 Option NoDDC EndSection Section Device Identifier Videocard1 Screen 1 Driver radeon VendorName Videocard vendor BoardName ATI Radeon VE BusID 05:04:0 Option NoDDC EndSection Section Device Identifier Videocard2 Screen 0 Driver radeon VendorName Videocard vendor BoardName ATI Radeon VE BusID 05:10:0 Option NoDDC EndSection Section Device Identifier Videocard3 Screen 1 Driver radeon VendorName Videocard vendor BoardName ATI Radeon VE BusID 05:10:0 Option NoDDC EndSection Section Device Identifier Videocard4 Screen
Re: [XFree86] Virge 86C385
Ought to work, but I haven't seen any GX reports in a while, so can't really say. What does 'very messed up' look like? Post the /var/log/XFree86.0.log and config file if you'd like a better response. Thank you for the answer. Messed up screen means that the mouse cursor is turned into square, some things as menu in fvwm and window details are blured (messed?). The config files I'm attaching to the mail. I have found some posts in Deja from people that have similar problem, but I didn't find the answer (the one that I found is to use xfree 3.3.6 instead of 4.3). Best regards. # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the Software), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section Module # This loads the DBE extension module. Loaddbe # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection extmod # Optionomit xfree86-dga # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Loadtype1 #Loadspeedo #Loadfreetype #Loadxtt # This loads the GLX module #Load glx # This loads the DRI module #Load dri EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section Files #FontPath /usr/X11R6/lib/X11/fonts/polish/100dpi #FontPath /usr/X11R6/lib/X11/fonts/polish/75dpi #FontPath /usr/X11R6/lib/X11/fonts/polish/misc # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ # The module search path. The default path is shown here. #ModulePath /usr/X11R6/lib/modules EndSection # ** # Server flags section. # ** Section ServerFlags # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #Option NoTrapSignals # Uncomment this to disable the CrtlAltFn VT switch sequence # (where n is 1 through 12). This allows clients to
Re: [XFree86] XFree86Config Question
Hello, Am Donnerstag, 6. November 2003 07:41 schrieb Shawn M. Badger: I just switched over to Gentoo 1.4, which I love so far, but I'm having some trouble with my XFree86Config file, and consequently my xserver. Is there an Xconfigurator-like program in Gentoo that I can use to configure this thing a bit more easily? Or is there one that I can easily emerge using Gentoo's awesome portage setup? Sorry if this is a really dumb question, but I am trying to learn more. Thanks, Shawn afaik gentoo has no program to do this for you. I just used xf86config (included in XFree), answered its questions and all went well. Regards Michael ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] radeon 9200SE
Hi, My name is Maciej Bobrowski. I have a problem with the ATI Radeon 9200SE (Excalibur) video card. In the attachment there are log and config file of XFree86. Please, help mi. Yours sincerely, Maciej Bobrowski XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.1 i386 [ELF] Build Date: 05 November 2003 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: /var/log/XFree86.0.log, Time: Thu Nov 6 18:15:40 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor CTX (**) | |--Device Radeon (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout pl (**) XKB: layout: pl (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/local/,/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/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.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 freebsd (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 1106,3189 card 1458,5000 rev 80 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:0c:0: chip 8086,1030 card 8086,1030 rev 08 class 02,00,00 hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1458,5004 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1458,5004 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1458,5004 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip 1106,3104 card 1458,5004 rev 82 class 0c,03,20 hdr 00 (II) PCI: 00:11:0: chip 1106,3177 card 1458,5001 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1458,5002 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:5: chip 1106,3059 card 1458,a002 rev 50 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1002,5964 card 17af,2012 rev 01 class 03,00,00 hdr 80 (II) PCI: 01:00:1: chip 1002,5d44 card 17af,2013 rev 01 class 03,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,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0xc000 - 0xc0ff (0x100) IX[B] [1] -1 0 0xc400 - 0xc4ff (0x100) IX[B] [2] -1 0 0xc800 - 0xc8ff (0x100) IX[B] [3] -1 0 0xcc00 - 0xccff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xe800 - 0xe9ff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xd800 - 0xe7ff (0x1000) 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) ATI Technologies Inc unknown chipset (0x5964) rev 1, Mem @ 0xd800/27, 0xe900/16, I/O @ 0xc000/8 (--) PCI: (1:0:1) ATI Technologies Inc unknown chipset (0x5d44) rev 1, Mem @ 0xe000/27, 0xe901/16 (II) Addressable bus resource ranges are [0] -1 0 0x -
RE: [XFree86] Fatal server with Intel i830 in suse 8.2
sorry i am using XFree86 4.3.0 not 4.2.0 -Original Message- From: Christopher Thom [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 11:00 PM To: [EMAIL PROTECTED] Subject: Re: [XFree86] Fatal server with Intel i830 in suse 8.2 Quoth Emilio Jose Paich Cucis: Hell I have a Dell Inspiron 2600 and i want inswtall Suse Linux 8.2 There's a i830M chipset that should work fine with XFree86 4.2.0, but the server doesn't start. The pcidata module says it's been compiled for XFree86 4.2.0, but you're running 4.3.0. This will probably cause problems. Have you been switching between the two versions? Try replacing this module with the 4.3.0 version. XFree86 Version 4.3.0 snip (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.0, module version = 0.1.0 cheers chris -- - | | | TELESCOPE, n.| | A device having a relation to the eye similar to that of the | | telephone to the ear, enabling distant objects to plague us with a | | multitude of needless details. Luckily it is unprovided with a bell | | summoning us to the sacrifice. | | -- Ambrose Bierce, The Devil's Dictionary | | | - ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Need Help With A Video Problem
Hello, I just installed FreeBSD 4.8-RELEASE #0 on a PC. The hardware specifications are: AMD 500Mhz CPU 384MB of RAM SiS 530 Video Card with 8MB of Shared RAM AOC Spectrum 7Glr monitor I am using the XFree86 Config file: /usr/X11R6/lib/X11/XF86Config I can get the graphical environment to start. My problem is in the video quality of the screen. There is a great deal of "snow". When I move the mouse, the "snow"becomes worse. If I move a window around on the screen, the picture quality deteriorates to the point of unreadability. What can I do to remove the "snow" look on the screen? Please reply back with suggestions to solve this problem. I also tried Red Hat Linux 9 and had the same results. Thanks in advance for your help! Kemp Byrd
Re: [XFree86] Need Help With A Video Problem
Kemp Byrd wrote: Hello, I just installed FreeBSD 4.8-RELEASE #0 on a PC. The hardware specifications are: AMD 500Mhz CPU 384MB of RAM SiS 530 Video Card with 8MB of Shared RAM AOC Spectrum 7Glr monitor I am using the XFree86 Config file: /usr/X11R6/lib/X11/XF86Config I can get the graphical environment to start. My problem is in the video quality of the screen. There is a great deal of snow. When I move the mouse, the snow becomes worse. If I move a window around on the screen, the picture quality deteriorates to the point of unreadability. What can I do to remove the snow look on the screen? Please reply back with suggestions to solve this problem. I also tried Red Hat Linux 9 and had the same results. Thanks in advance for your help! Kemp Byrd You're overclocking your hardware. Reduce the vertical refresh rate or the color depth. Thomas -- Thomas Winischhofer Vienna/Austria thomas AT winischhofer DOT net *** http://www.winischhofer.net/ twini AT xfree86 DOT org ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Multiple Dualhead card problem ATI Radeon VE / Appian Typhoon 64
This may be related to the problem discussed a while back with the posting of seconday radeon cards. Can you send a copy of your xfree86 log and the output of lspci? Alex - Yesterday I installed three Appian Typhoon 64 cards in a system with XFree86 - 4.3.0. The Appian has an ATI Radeon VE on it. The first strange thing is that both displays of the first graphical card show the same from startup where I would expect only the first monitor to show the boot sequence etc. Second I tried to create 6 seperate display. Then the Server crashes. Adding the Load ddc Module resolved next messages: Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! But still the server crashes. Attached are the /etc?X11/XF86config file and the /var/log/XFree86.0.log file. Just using Screen0 and screen1 and thus only the first graphical card works. Has anyone an idea what the problem is. Regards, Marcel Stegehuis __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] radeon 9200SE
xfree86 4.3.0 didn't support the 9200 series radeons. You might be able to force the chipID to a supported one like a 9000. You can also upgrade to xfree86 from cvs. Binary snapshots from the DRI project are available here: http://dri.sourceforge.net/snapshots/ grab the r200 snapshot and the XFree86 package from the extras directory. Alex - Hi, My name is Maciej Bobrowski. I have a problem with the ATI Radeon 9200SE (Excalibur) video card. In the attachment there are log and config file of XFree86. Please, help mi. Yours sincerely, Maciej Bobrowski __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] radeon 9200SE
xfree86 4.3.0 didn't support the 9200 series radeons. You might be able to force the chipID to a supported one like a 9000. You can also upgrade to xfree86 from cvs. Hmm, How can I force the chipID to a supported one like a 9000? I didn't do that before. Binary snapshots from the DRI project are available here: http://dri.sourceforge.net/snapshots/ grab the r200 snapshot and the XFree86 package from the extras directory. Fine, I made the instructions includeed there in info files. But I work under the freeBSD, not linux. But all the files are made and compiled for linux with different libraries, different names and locations. Isn't there already something ready for freebsd? I tried to use the vesa driver instead of radeon and it works, but ...it doesn't look good. The vertical refresh is amount 60 Hz and when I try to run the xvidtune it says: Video modes are not tunable on this chip So, my eyes are crazy after a half an hour. Moreover my mouse jumps simetimes from one position to another.\ So, the vesa driver works but it isn't that what it has to be. Please help, Maciej Bobrowski ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Why does overlay lag behind with XVideo?
Hello! I have a nvidia gforce2 card, and with mplayer or xine I use the Xv extension output plugin. But I have noticed that the video overlay lags behind in position as I move around the player application on the desktop. Small problem, but anyways I'd like to know what type of card I should buy to avoid this, so that the video moves along just as fast as when I use the xshm output. Hakon
[XFree86] C O M M U N I Q U E
P U B L I C A T I O N S C A N A D I E N N E S 1556 Grand Marnier Val David Qc J0T 2N0 A N N U A I R E D E S S U B V E N T I O N S A U Q U É B E C 2004 Dépot légal-Bibliothèque Nationale du Québec ISBN 2-922870-06-5 COMMUNIQUÉ DE PRESSE Les Publications Canadiennes offrent au public une édition révisée de l'A N N U A I R E D E S S U B V E N T I O N S A U Q U É B E C contenant plus de 1900 programmes d'aides et de subventions provenant des divers paliers gouvernementaux et organismes. Dans la nouvelle édition 2004 on trouve la description des programmes ainsi que les montants alloués. L'A N N U A I R E D E S S U B V E N T I O N S A U Q U É B E C est l'outil idéal soit pour démarrer son entreprise, améliorer une entreprise existante, mettre sur pied son plan d'affaires ou obtenir l'aide de conseillers experts dans le domaine des affaires: Démarrage d'entreprises, études, recherches, arts, agriculture, import export, main d'oeuvre, cinéma, prêts, promotion, bourses, théatre, transports, communications, mise sur pied et développement d'entreprises, construction et rénovation, aérospatial, concours, nouveaux talents, aide aux associations, organismes et fondations, informatique, musique, industrie du disque, plans d'affaires, études de marchés, infrastructures, aide aux travailleurs autonomes et plus encore ! Prix $ 69,95 Informations.sans frais 8 6 6 - 3 2 2 - 3 3 7 6 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Why does overlay lag behind with XVideo?
This is typical behavior of all overlays. The overlay doesn't update until the next retrace but all other graphics draw as soon as possible. Mark. On Thu, 6 Nov 2003, Hakon Gunsen wrote: Hello! I have a nvidia gforce2 card, and with mplayer or xine I use the Xv extension output plugin. But I have noticed that the video overlay lags behind in position as I move around the player application on the desktop. Small problem, but anyways I'd like to know what type of card I should buy to avoid this, so that the video moves along just as fast as when I use the xshm output. Hakon ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Why does overlay lag behind with XVideo?
Mark Vojkovich ([EMAIL PROTECTED]): This is typical behavior of all overlays. The overlay doesn't update until the next retrace but all other graphics draw as soon as possible. But you can see the window moving. The problem is that the overlay doesn't get reprogrammed with a new position until the next frame is drawn from the input. So I draw a frame, the overlay is programmed to draw it at 50,50. I move the window to 75,75 overlay is still at 50,50, so my window moves faster than the video. Next frame is drawn by xine or whatever and now the video is at 75,75. It's a valid complaint, would be nice if the overlay position could be updated during window move, don't know how feasible it is. -Billy Mark. On Thu, 6 Nov 2003, Hakon Gunsen wrote: Hello! I have a nvidia gforce2 card, and with mplayer or xine I use the Xv extension output plugin. But I have noticed that the video overlay lags behind in position as I move around the player application on the desktop. Small problem, but anyways I'd like to know what type of card I should buy to avoid this, so that the video moves along just as fast as when I use the xshm output. Hakon ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Why does overlay lag behind with XVideo?
Billy Biggs wrote: Mark Vojkovich ([EMAIL PROTECTED]): This is typical behavior of all overlays. The overlay doesn't update until the next retrace but all other graphics draw as soon as possible. But you can see the window moving. The problem is that the overlay doesn't get reprogrammed with a new position until the next frame is drawn from the input. So I draw a frame, the overlay is programmed to draw it at 50,50. I move the window to 75,75 overlay is still at 50,50, so my window moves faster than the video. Next frame is drawn by xine or whatever and now the video is at 75,75. It's a valid complaint, would be nice if the overlay position could be updated during window move, don't know how feasible it is. This is not possible with most hardware I know of. The engines usually read the overlay parameters only once per frame, during retrace. Thomas -- Thomas Winischhofer Vienna/Austria thomas AT winischhofer DOT net http://www.winischhofer.net/ twini AT xfree86 DOT org ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Why does overlay lag behind with XVideo?
Thomas Winischhofer ([EMAIL PROTECTED]): This is typical behavior of all overlays. The overlay doesn't update until the next retrace but all other graphics draw as soon as possible. But you can see the window moving. The problem is that the overlay doesn't get reprogrammed with a new position until the next frame is drawn from the input. So I draw a frame, the overlay is programmed to draw it at 50,50. I move the window to 75,75 overlay is still at 50,50, so my window moves faster than the video. Next frame is drawn by xine or whatever and now the video is at 75,75. It's a valid complaint, would be nice if the overlay position could be updated during window move, don't know how feasible it is. This is not possible with most hardware I know of. The engines usually read the overlay parameters only once per frame, during retrace. I meant frame sent by xine. When you move an XVIDEO window around, I do not think you are just seeing inconsistency as tearing. With my application I can change the output framerate between 59.94 fps and 29.97 fps. When tvtime is drawing at 29.97 fps, the lag between window moves and the contents moving is much longer than at 59.94 fps. -Billy ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] restart x
Quoth Jeff: I need help installing a Nvidia Driver for my Geforce 4 ti 4200. it tells me to restart x and I dont know how to restart X can you please help me. any help would be much appreciated. CTRL+ALT+backspace will kill the X server - it should restart itself automagically. You can also do, depending on your distro, something like /etc/init.d/xdm stop and then /etc/init.d/xdm start (as root on a console). a simple reboot will also have the desired effect, but isn't really necessary. cheers chris -- - | | | TELESCOPE, n.| | A device having a relation to the eye similar to that of the | | telephone to the ear, enabling distant objects to plague us with a | | multitude of needless details. Luckily it is unprovided with a bell | | summoning us to the sacrifice. | | -- Ambrose Bierce, The Devil's Dictionary | | | - ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] mouse not working in XFree86
Quoth Jorge Castro: I would like both the laptop in-built mouse and the USB mouse to work at the same time. Can any one give me a hint as to what I should have in my XFree86Config file to achieve that? my dell laptop works fine like this. I use: Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceUSB Mouse SendCoreEvents InputDeviceKeyboard0 CoreKeyboard EndSection #This one is the touch-pad. /dev/mouse is a link to /dev/psaux Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/mouse EndSection Section InputDevice Identifier USB Mouse Driver mouse Option Protocol IMPS/2 Option Device /dev/input/mice Option ZAxisMapping 4 5 #This line enables the wheel EndSection cheers chris -- - | | | TELESCOPE, n.| | A device having a relation to the eye similar to that of the | | telephone to the ear, enabling distant objects to plague us with a | | multitude of needless details. Luckily it is unprovided with a bell | | summoning us to the sacrifice. | | -- Ambrose Bierce, The Devil's Dictionary | | | - ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Error when booting
Dear XFree, I had a power interruption today and now my linux computer will not boot up properly to KDE. There is a message in my messages file that says: display :0 is being disabled (exit frequency too high) server for display:0 terminated unexpectedly: 1 I've attached my XFree86.0.log I'm a newbie to Linux. Can you help me? Thank you. Rod Kelley attachment: winmail.dat
[XFree86] Error on starting Xwindows
Hi! Sir, I am new to Linux and want to learn this system. However, I met some errors while starting a new fresh install Linux. Ive attached the Error log from Linux. Could you mind help me to find out what problem should my machine be? I think the error log have all my machine information. If you need while you are finding, please dont hesitate to email me and I would try my best to assist. Thx William To XFree86.1.log Description: Binary data
[XFree86] Trouble in Gotham City
Hello, I am sorry to bother you folks because I know you are busy but I have reached the limit of my knowledge and inginuity (sp?). I'm attaching my XF86Config and XFree86.0.log. I'm trying to run RedHat9 on my Cpmpaq Presario S4000J. Everything seems to be running properly with no errors I can find in the log but when I go to init level 5 and X starts up all I get is a black screen. I have to go back to console mode to look around. X is running. If I kill it it restarts. Everything looks normal but the screen is black. Any ideas? Thanks for any bone you can through my way. I checked your site and it looks like I have the latest version. I'm glad of that all I have here is a dialup. :-( Arnie Stender 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:18:24 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 Nov 5 20:49:44 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/TTF/ (**) 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 1106,3116 card 1509,9012 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b091 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:0a:0: chip 11c1,044c card 11c1,044c rev 02 class 07,80,00 hdr 00 (II) PCI: 00:0b:0: chip 10ec,8139 card 1509,9012 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1509,9012 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1509,9012 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1509,9012 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip 1106,3104 card 1509,9012 rev 82 class 0c,03,20 hdr 00 (II) PCI: 00:11:0: chip 1106,3177 card 1509,9012 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1509,9012 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:5: chip 1106,3059 card 1509,9012 rev 50 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 5333,8d04 card 1509,9012 rev 00 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xec00 - 0xedff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xe000 - 0xe7ff (0x800) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN
[XFree86] r128 resolution question
I have a IBM Thinkpad A21p laptop with a Rage 128 Mobility card, and I have a vexing problem. The LCD screen is a 1600x1200 resolution, and I have not yet found any way to run the Xserver at any resolution less than this. This is a problem for me, as I use the external VGA out to drive an LCD projector, and they usually support nothing better than 1024x768. Consequently I have to maintain a dual boot Linux with Win98 so I can use Windoze solely for presentations. Am I missing something stupidly obvious, or is this a known limitation? I'm running X v4.3, RedHat 9, kernel 2.4.20. I've attached my XF86Config and a copy of the error log. Any light you could shed would be appreciated. TIA iain# XFree86 4 configuration created by redhat-config-xfree86 Section ServerLayout Identifier Layout[all] Screen Screen[0] 0 0 InputDeviceKeyboard[0] CoreKeyboard InputDeviceMouse[1] CorePointer EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb ModulePath /usr/X11R6/lib/modules FontPath /usr/X11R6/lib/X11/fonts/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/latin5/misc FontPath /usr/X11R6/lib/X11/fonts/latin5/75dpi FontPath /usr/X11R6/lib/X11/fonts/latin5/100dpi FontPath /usr/X11R6/lib/X11/fonts/latin5/Type1 FontPath /usr/X11R6/lib/X11/fonts/local 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/URW FontPath /usr/X11R6/lib/X11/fonts/Speedo FontPath /usr/X11R6/lib/X11/fonts/misc FontPath /usr/X11R6/lib/X11/fonts/75dpi FontPath /usr/X11R6/lib/X11/fonts/100dpi FontPath /usr/X11R6/lib/X11/fonts/PEX FontPath /usr/X11R6/lib/X11/fonts/cyrillic FontPath /usr/X11R6/lib/X11/fonts/latin2/misc FontPath /usr/X11R6/lib/X11/fonts/latin2/75dpi FontPath /usr/X11R6/lib/X11/fonts/latin2/100dpi FontPath /usr/X11R6/lib/X11/fonts/latin2/Type1 FontPath /usr/X11R6/lib/X11/fonts/latin7/75dpi FontPath /usr/X11R6/lib/X11/fonts/kwintv FontPath /usr/X11R6/lib/X11/fonts/truetype FontPath /usr/X11R6/lib/X11/fonts/uni FontPath /usr/X11R6/lib/X11/fonts/ucs/misc FontPath /usr/X11R6/lib/X11/fonts/ucs/75dpi FontPath /usr/X11R6/lib/X11/fonts/ucs/100dpi FontPath /usr/X11R6/lib/X11/fonts/hellas/misc FontPath /usr/X11R6/lib/X11/fonts/hellas/75dpi FontPath /usr/X11R6/lib/X11/fonts/hellas/100dpi FontPath /usr/X11R6/lib/X11/fonts/hellas/Type1 FontPath /usr/X11R6/lib/X11/fonts/xtest EndSection Section Module Load dbe Load type1 Load speedo Load extmod Load freetype EndSection Section ServerFlags Option AllowMouseOpenFail EndSection Section InputDevice Identifier Keyboard[0] Driver keyboard Option Protocol Standard Option XkbKeyCodes xfree86 Option XkbModel pc104 Option XkbRules xfree86 Option XkbVariant nodeadkeys EndSection Section InputDevice Identifier Mouse[1] Driver mouse Option Device /dev/psaux Option Emulate3Buttons on Option Name AutoDetected Option Protocol ps/2 Option Vendor AutoDetected EndSection Section Modes Identifier Modes[0] ModeLine 640x480 28.0 640 656 720 864 480 480 485 501 ModeLine 800x600 43.7 800 816 928 1072 600 600 606 626 ModeLine 1024x768 71.4 1024 1040 1216 1400 768 768 776 802 ModeLine 1152x864 90.5 1152 1168 1384 1568 864 864 873 902 ModeLine 1280x960 111.8 1280 1296 1552 1736 960 960 970 1003 ModeLine 1280x1024 119.3 1280 1296 1552 1736 1024 1024 1035 1070 ModeLine 1600x1200 160.2 1600 1616 1968 2208 1200 1200 1212 1253 ModeLine 1600x1200 167.2 1600 1616 1968 2208 1200 1200 1212 1253 EndSection Section Monitor Identifier Monitor[0] VendorName AutoDetected ModelNameAutoDetected UseModes Modes[0] HorizSync31.0 - 77.0 VertRefresh 50.0 - 77.0 EndSection Section Device Identifier Device[0] Driver ati VendorName AutoDetected BoardName Generic VGA compatible EndSection Section Screen Identifier Screen[0] Device Device[0] MonitorMonitor[0] DefaultDepth 16 SubSection Display Depth 16 Modes 1600x1200 1400x1050 1280x1024 1280x960 1152x864 1024x768 800x600
[XFree86] Posible format string bug on Xterm Up to last version
Hello, im Agustin Gianni (gr00vy) from argentina. I would like to report a bug on xterm (the last version 181 and the one on Slackware 9.0). Since im not experienced on format bugs i couldnt make so much to try to make a fix o give more info about the bug. [EMAIL PROTECTED]:/root# HOME=%n%n%n%n%n%n [EMAIL PROTECTED]:/root# xterm Segmentation fault [EMAIL PROTECTED]:/root# gdb xterm (gdb) r Starting program: /root/xterm-181/xterm Program received signal SIGSEGV, Segmentation fault. 0x4026e5bd in _int_malloc () from /lib/libc.so.6 (gdb) bt #0 0x4026e5bd in _int_malloc () from /lib/libc.so.6 #1 0x4026d6b5 in malloc () from /lib/libc.so.6 #2 0x4025c003 in __fopen_internal () from /lib/libc.so.6 #3 0x4025c0ce in fopen@@GLIBC_2.1 () from /lib/libc.so.6 #4 0x4001e47a in XcursorFilenameSave () from /usr/X11R6/lib/libXcursor.so.1 #5 0x4001e616 in XcursorLibraryLoadImages () from /usr/X11R6/lib/libXcursor.so.1 #6 0x4001e824 in XcursorShapeLoadImages () from /usr/X11R6/lib/libXcursor.so.1 #7 0x4001eb6e in XcursorTryShapeCursor () from /usr/X11R6/lib/libXcursor.so.1 #8 0x4012d628 in _XTryShapeCursor () from /usr/X11R6/lib/libX11.so.6 #9 0x4012d9e9 in XCreateGlyphCursor () from /usr/X11R6/lib/libX11.so.6 #10 0x4012de59 in XCreateFontCursor () from /usr/X11R6/lib/libX11.so.6 #11 0x0805f3ce in make_colored_cursor (cursorindex=68, fg=0, bg=16777215) at misc.c:216 #12 0x0805b578 in get_terminal () at main.c:2467 #13 0x0805b019 in main (argc=0, argv=0xb9e8) at main.c:2111 #14 0x4020dbb4 in __libc_start_main () from /lib/libc.so.6 (gdb) i r eax0x808e780134801280 ecx0x40327300 1077048064 edx0x40327354 1077048148 ebx0x40326234 1077043764 esp0xb650 0xb650 ebp0xb688 0xb688 esi0x0 0 edi0x0 0 eip0x4026e5bd 0x4026e5bd eflags 0x10206 66054 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x0 0 fctrl 0x37f895 fstat 0x0 0 ftag 0x 65535 fiseg 0x0 0 fioff 0x0 0 foseg 0x0 0 fooff 0x0 0 fop0x0 0 mxcsr 0x1f80 8064 orig_eax 0x -1 Best Regards Agustin Gianni Argentina PS: thanks to #linux and #cheese (specially df) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] screen redraw problem
Thanks Mark, Unfortunately that didn't make any difference. Maybe your app is expecting backing store. You can start XFree86 with backing store startx -- +bs. Mark. On Wed, 5 Nov 2003, J S wrote: Is there anymore information I need to add to this post? I would really like to get some help with it. The logs don't seem to be showing anything. I've tried setting different color depths, and screen resolutions but to no avail. Hi, I have an application which has some boxes in the window. The window itself is scrollable. When I scroll down - no problem, but when I scroll up the boxes turn into long vertical bars. This problem doesn't happen with Exceed, but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. Can anyone advise me whether this is a bug, or is there some setting I need to add? Let me know if you need anymore information. Thanks for any help. JS. _ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 _ Sign-up for a FREE BT Broadband connection today! http://www.msn.co.uk/specials/btbroadband ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
