CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/27 14:19:21 Log message: Low-impact bug fix. So low, in fact, that there's not much point in commiting this to 4.3's stable branch. Modified files: xc/lib/font/util/: private.c Revision ChangesPath 1.9 +4 -3 xc/lib/font/util/private.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: www (branch: trunk)
CVSROOT:/home/x-cvs Module name:www Changes by: [EMAIL PROTECTED] 03/02/27 14:55:10 Log message: update 4.3.0 release info Modified files: ./: index.html Added files: ./: rel430.html Revision ChangesPath 1.97 +7 -10 www/index.html ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: XRENDER extension docs?
On Wed, Feb 26, 2003 at 05:06:48PM -0800, Kendall Bennett wrote: Kurt Wall [EMAIL PROTECTED] wrote: Feigning erudition, Kendall Bennett wrote: % Hi Guys, % % Is thete any documentation on the XRENDER extension and more specifically % the Matrox implementation of it? Do any other drivers other than the % Matrox driver implement this extension? http://www.xfree86.org/~keithp/render/ $XFREE86ROOT/lib/X11/doc/render-protocol.txt Awesome, thanks! That gives a bit more information, but it doesn't really describe how the XAA drivers can accelerate the XRENDER extension. It Yes, it would indeed be great if the XAA.HOWTO would be expanded by a new paragraph speaking about the XRENDER acceleration hooks. There is already the xaa.h which gives some info, but a discution of the hooks would be welcome. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Wed, Feb 26, 2003 at 09:40:18PM -0500, David Dawes wrote: On Wed, Feb 26, 2003 at 09:25:21PM +0100, Sven Luther wrote: On Wed, Feb 26, 2003 at 09:27:50PM +0200, Yitzhak Bar Geva wrote: Greatly encouraged by your response, thanks! Someone reported that X works with the multi-head console support in Linux 2.5 kernels. I did some searching for multi-head consoles under 2.5 kernel, but didn't see anything. I would be highly appreciative if you could give me some pointers. As far as I could see, the Linux Console Project is defunct, but there is definitely work on multiple input devices going on. The correct place is the linux-fbdev project on sourceforge, especially their mailing list, James Simmon is the main developper of the new console code, and you have to look into the late 2.5.5x at least to get working stuff. That said, XFree86 people don't like fbdev much, and anyway, i don't Not necessarily :-) I recently wrote an fbdev driver for Intel 830M and later chipsets (www.xfree86.org/~dawes/intelfb.html, and it should be in new -ac kernels). It was fun doing some graphics stuff outside of XFree86 for a change. It's basically a 2.4.x driver right now, and still needs to be ported to the latest 2.5.6x fbdev interfaces. Well, the 2.5.x drivers (the new API) are a lot easier to write, since a lot of common stuff has been abstracted. I have plans to write a HOWTO or something once i get time for it again. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Wed, Feb 26, 2003 at 05:12:32PM -0600, jkjellman wrote: Absolutely right, but ... This can be done if two servers are used. The point I was making earlier in this thread was that used hacked kernels and servers are a bad thing. If two consoles (including keyboards) could be operated on a single box, then two separate X servers could also be run. The biggest problem is not the display, but rather that both X and Linux have a single console keyboard ingrained in their code. Any thoughts on how this might be circumvented using existing pieces? The new fbdev API and console layer should handle this just fine, not that i have personal experience with it, but that seemed to be the intention from what i followed in the linux-fbdev mailing list. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Wed, Feb 26, 2003 at 10:47:39PM +, Andrew C Aitchison wrote: How do you imagine this would work when both head are using a shared accel (XAA or DRI) engine ? I thought that the whole point of the kernel DRI was to stop multiple apps from fighting over the hardware. If the X server and several libGL apps Well, it is more like multiple OpenGL X clients and the X drivers themselves. I don't hear of anyone running DRI on fbdev and X alongside each other, and all the stuff is initialized inside the X driver anyway. can share the hardware, adding another X server should be possible. It is not as simple, since for one chip driving two screens, there are some things that can only be done chip wide, and others that can be done separatedly on each head. Also, i think the DRI only bothers about the 3D engine, not really about things like mode setup and so. And even (onchip) memory management is not (yet) well separated. There is a proposal for DRI about that from Ian Romanick, but it does only concern the DRI, and it is not clear if the OS memory manager can be made to work with it also, or how. For it to work nicely the proposed extension to RandR which allows the frame-buffer to be re-arranged (remember that we have dropped on the fly trade off between depth and number of pixels from 4.3) would help, Mmm, there is another discution in the DRI mailing list about dual head with a single framebuffer, where i think RandR could be used to do one the fly head re-organization. But again, i don't really believe that this would help out if we plan to have two separate users, one on each head/seat/whatever. and I think we would want something (probably fbdev) to share out the frame-buffer. The fbdev and the drm would work, i think. You would use the fbdev for mode setting and such, and the drm for acceleration, the fbdev has not enough logic for it right now. but again, the fbdev and the drm don't cooperate very well, especially since the drm is initialized from the X driver. I suppose we could go the other way, and do two seats within one X server. Is this possible ? Not currently i guess, but it is a feature asked for since some time, for doing cheap terminals, instead of having one cheap box driving one terminal, you would driver two with it, thus almost halving the cost. That said, if one head crashes, the other goes too. I'd want one seat to be called say machine:0 and the other machine:1 ie listen on two sockets/ports. This would definitely be a case for two pointers and two sets of focus (which people seem to want for other reasons). Would the window scheduling be good enough to ensure that one seat can't consume all the cycles ? I'd be particularly worried that information could leak between seat. Do we use separate threads (or processes) for each seat; someone recently mentioned that the server isn't thread-safe. Conceptually I feel that all this should be left to the kernel, and we should run a separate X server for each seat. Lot of good questions ... BTW, Dawes, what are the plans for post 4.3.0 XFree86 ? This kind of thing would most assuredly go into the thinking about 5.x, but some of the stuff here, and about the dual-head/one FB (which would allow DRI on dual head cards) could also be implemented in the current setting. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: ATI with cvs
ati isn't a driver, it is a wrapper around the other 3 real ATI drivers. The correct driver for any Radeon based chip is radeon. Using the ati driver wrapper merely autodetects the card and calls the radeon driver. Either should work, but using radeon removes one level of indirection. wow! never new that - thanks for the tip -- http://www.dunkfordyce.co.uk Tagline for Thursday, February 27, 2003 Keep emotionally active. Cater to your favorite neurosis. dunk fordyce is d1223m @ #linuxhelp @ irc.freenode.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
xf86cfg: ERROR SIGSEGV caught!
Hi Looks like xf86cfg in 4.2.99.902 (most likely also 4.3.0) is broken. At least I see now messages like this. [...] Loading /usr/X11R6/lib/modules/extensions/libGLcore.a Module GLcore: vendor=The XFree86 Project compiled for 4.2.99.902, module version = 1.0.0 ERROR SIGSEGV caught! [...] It also happens for each input and graphics driver. It might be related to this change: 940. Allow xf86setjmp/xf86setlongjmp to work with platforms where setjmp() isn't directly available as a function, specifically Linux platforms that use glibc 2.0 and 2.1. (David Dawes, Keith Packard). I tried to adjust xf86cfg to this change but failed for now. Maybe David or Keith can have a look at this issue? Best regards, Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
date.def
xc/config/cf/Imakefile now refers to date.def, and xfree86.cf includes it, but I can't find it in the latest CVS, nor can I find a rule which builds it on the fly. Without this file make World does very little. The Imakefile change appears to be before the 4.2 tag, so we may need to add the file to both branches ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: date.def
On Thu, Feb 27, 2003 at 12:55:21 +, Dr Andrew C Aitchison wrote: xc/config/cf/Imakefile now refers to date.def, and xfree86.cf includes it, but I can't find it in the latest CVS, nor can I find a rule which builds it on the fly. Without this file make World does very little. The Imakefile change appears to be before the 4.2 tag, so we may need to add the file to both branches ? The rule to build it is in xc/Makefile. Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: date.def
On Thu, 27 Feb 2003, Alan Hourihane wrote: On Thu, Feb 27, 2003 at 12:55:21 +, Dr Andrew C Aitchison wrote: xc/config/cf/Imakefile now refers to date.def, and xfree86.cf includes it, but I can't find it in the latest CVS, nor can I find a rule which builds it on the fly. Without this file make World does very little. The Imakefile change appears to be before the 4.2 tag, so we may need to add the file to both branches ? The rule to build it is in xc/Makefile. Thanks. It seems that my xc/Imakefile and xc/Makefile are not being updated by cvs -q update -A -d in the directory above xc, although I am successfully cvsup'ing xc/Imakefile,v I cvsup collections cvs-base/cvs cvs-src/cvs and xc-all/cvs Am I missing something to control the bootstrap ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Thu, Feb 27, 2003 at 12:35:57PM +0100, Stefan Dirsch wrote: Hi Looks like xf86cfg in 4.2.99.902 (most likely also 4.3.0) is broken. At least I see now messages like this. [...] Loading /usr/X11R6/lib/modules/extensions/libGLcore.a Module GLcore: vendor=The XFree86 Project compiled for 4.2.99.902, module version = 1.0.0 ERROR SIGSEGV caught! [...] It also happens for each input and graphics driver. It might be related to this change: 940. Allow xf86setjmp/xf86setlongjmp to work with platforms where setjmp() isn't directly available as a function, specifically Linux platforms that use glibc 2.0 and 2.1. (David Dawes, Keith Packard). I tried to adjust xf86cfg to this change but failed for now. Maybe David or Keith can have a look at this issue? If you tried backing out that change and the problems still shows up, then it's something else. Did you try backing it out? David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Around 9 o'clock on Feb 27, Sven Luther wrote: Yes, it would indeed be great if the XAA.HOWTO would be expanded by a new paragraph speaking about the XRENDER acceleration hooks. There is already the xaa.h which gives some info, but a discution of the hooks would be welcome. The current Render acceleration hooks are pretty low level; we need to spend some time designing a more comprehensive interface. The trouble is that Render provides so little structure to build upon, unlike the core protocol. We can place additional structure inside the render code and XAA to break down the current interface into more reasonable functions. However, it's hard to get excited about building accelerated implementations without a comprehensive test suite and when the spec is still a bit in flux. I've been working on the test suite with some students, but there's a steep learning curve and so not much progress has been made yet. The spec is almost finished as well; I've got to go rewrite the trapezoid specification to match our current thinking and I'd like to add some image transport requests. The trapezoid part won't have much of an effect on the architecture of any acceleration internals, but image transport may need to be exposed all the way to the bottom of the system. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: repeated X restarts with i810 not freeing sys resources?
On Sat, 15 Feb 2003, David Dawes wrote: Yep, RH7.3 with its default kernel plus the agpgart driver referenced above. Could you try your setup using that agpgart driver? That might help narrow down if the problem lies there or elsewhere. I don't see how the problem could be anywhere other than the kernel or agpgart driver. I guess I'll need to try this same kernel. I downloaded the 2.4.20-2.21 kernel source rpm from RH's phoebe beta. I can get the kernel to build, but not modules. So, I built the agpgart driver into the kernel and tested it that way. I can reproduce what you're seeing with this kernel. I also tried the stock 2.4.20 kernel from ftp.kernel.org, and it works fine, and doesn't show the problem you're seeing. So, it looks like some difference between RH's kernel and the stock kernel. You'll have to follow that up further with Red Hat (or use a kernel from ftp.kernel.org). This problem has since been reported for mga, and other hardware also, and we've suspected it to be something specific to our kernel as well. Last night Arjan Van de Ven tracked the problem down to a refcount bug in rmap with respect to PageReserved pages. DRM marks it's pages as PageReserved and was affected by this bug. The bugfix is in our latest internal kernel build now, and confirmed working on several systems which showed this problematic behaviour. I thought I'd pass the info around to the list that the issue is resolved now. Thanks, TTYL -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Keith Packard [EMAIL PROTECTED] wrote: Yes, it would indeed be great if the XAA.HOWTO would be expanded by a new paragraph speaking about the XRENDER acceleration hooks. There is already the xaa.h which gives some info, but a discution of the hooks would be welcome. The current Render acceleration hooks are pretty low level; we need to spend some time designing a more comprehensive interface. The trouble is that Render provides so little structure to build upon, unlike the core protocol. Ok, so it is a little early yet to start implementing this in our drivers? Or should we just implement what the Matrox driver is doing and follow that model for now (ie: just alpha blits)? We can place additional structure inside the render code and XAA to break down the current interface into more reasonable functions. However, it's hard to get excited about building accelerated implementations without a comprehensive test suite and when the spec is still a bit in flux. I've been working on the test suite with some students, but there's a steep learning curve and so not much progress has been made yet. Ok. What stuff other than alpha blits (for fonts and menus) does XRENDER provide anyway? I am a little unclear on that right now. Also I have been wondering about the accelerated anti-aliased text. Is all anti-aliased text in XFree86 done via the XRENDER extension and alpha blits? It is possible to implement accelerated anti-aliased text using simple 4-8 levels of mono bitmap blits using FreeType (that is what we used for it in our MGL graphics library). It is slower than regular text (and probably slower than alpha blits in hardware), but way faster than doing alpha blits in software when there is a hardware mono blit function to use. Has anyone considered using that style of interface for anti- aliased text in XFree86? Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Around 10 o'clock on Feb 27, Kendall Bennett wrote: Ok, so it is a little early yet to start implementing this in our drivers? Or should we just implement what the Matrox driver is doing and follow that model for now (ie: just alpha blits)? I think the interfaces currently provided by XAA will probably remain usable, so you might as well implement them. Ok. What stuff other than alpha blits (for fonts and menus) does XRENDER provide anyway? I am a little unclear on that right now. Render does three things: 1) Image compositing 2) Trapezoids (and triangles) 3) Glyphs However, the image compositing function has a lot of functionality buried inside, including projective image transformations, solid fills and tiling. Plus, trapezoids and glyphs are defined in terms of image compositing, so in the MI implementation, they are implemented on top of the basic Composite function. My thought is that we'll want to have the XAA 'Composite' function recognise some common operations (like solid fill and screen-screen blt and perhaps others) and call out to driver functions designed for that specific operation. Plus, we should have XAA expose special higher level functions for glyph rendering to the driver so that the graphics card can use the higher level data structures to speed this operation, rather than having the MI layer break the text operation into a (long) sequence of primitive Composite operations. Also I have been wondering about the accelerated anti-aliased text. Is all anti-aliased text in XFree86 done via the XRENDER extension and alpha blits? It is possible to implement accelerated anti-aliased text using simple 4-8 levels of mono bitmap blits using FreeType (that is what we used for it in our MGL graphics library). Yes, all AA text is done with the Render glyph operations which are defined in terms of the basic image composition primitive. Once you have hardware acceleration for image compositing, that's going to be a lot faster than any non-standard rendering path. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Keith Packard [EMAIL PROTECTED] wrote: I think the interfaces currently provided by XAA will probably remain usable, so you might as well implement them. Ok. Plus, we should have XAA expose special higher level functions for glyph rendering to the driver so that the graphics card can use the higher level data structures to speed this operation, rather than having the MI layer break the text operation into a (long) sequence of primitive Composite operations. Yes, most definitely. The current mechanism is not exactly efficient, and in fact is the reason why I want to hook some functions at a higher level so we can make this faster. Also when it comes to rendering text, one of the fastest ways of doing this is the way that OS/2 does it. Instead of caching any glyphs in offscreen video memory (terribly wasteful of offscreen video memory and no faster than using system memory bitmaps), you maintain a single large bitmap that matches the physical resolution of the screen (ie: 1280x1024 mono bitmap). When you need to draw text, you render the text into the mono bitmap in software at the necessary place on the screen, and when that is done pass the entire bitmap to be drawn to the hardware with a clip rectangle that covers just the text you just rendered into the bitmap. The clipping is real easy to do in the software setup stages for text rendering, and then you can blit the entire string to the hardware in one shot. So fast, efficient text could be done in XFree86 if a single function was used to transfer an entire bitmap in the driver code (pre-clipping could easily be done before the driver code is called), and some high level code to maintain and render the glyphs into the pre-allocated large bitmap. Also I have been wondering about the accelerated anti-aliased text. Is all anti-aliased text in XFree86 done via the XRENDER extension and alpha blits? It is possible to implement accelerated anti-aliased text using simple 4-8 levels of mono bitmap blits using FreeType (that is what we used for it in our MGL graphics library). Yes, all AA text is done with the Render glyph operations which are defined in terms of the basic image composition primitive. Once you have hardware acceleration for image compositing, that's going to be a lot faster than any non-standard rendering path. Granted, if you have hardware alpha blits that will be the fastest way to do this. But if you don't have hardware alpha blits (and lots of cards supported by XFree86 do not), you can still speed up anti-aliased text quite a lot by using a 4 or 8 level scheme using multiple mono bitmaps. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Around 11 o'clock on Feb 27, Kendall Bennett wrote: So fast, efficient text could be done in XFree86 if a single function was used to transfer an entire bitmap in the driver code (pre-clipping could easily be done before the driver code is called), and some high level code to maintain and render the glyphs into the pre-allocated large bitmap. That's how Render does text today, except that it allocates the temporary bitmap on the fly (which isn't a big deal with modern malloc implementations). Monochrome bitmaps the size of the screen are one thing, but 32bpp bitmaps at screen size are a bit large to keep around for this purpose (yes, Render glyphs really are 32bpp on LCD screens). Granted, if you have hardware alpha blits that will be the fastest way to do this. But if you don't have hardware alpha blits (and lots of cards supported by XFree86 do not), you can still speed up anti-aliased text quite a lot by using a 4 or 8 level scheme using multiple mono bitmaps. I suppose, but it wouldn't be compatible with the Render semantics. If I'd heard users complaining about text performance, I'd be more interested. Plus, the number of users with cards that can't support image compositing is rapidly declining; essentially any card that has even the smallest amount of acceleration for 3D graphics can accelerate Render. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Work in the sun
Is there not a spam filter for this kind of thing? -- Paul Evans (3rd Year CompSci at Pembroke College, Cambridge, England) [EMAIL PROTECTED] (university) [EMAIL PROTECTED] (alternate) ICQ# 4135350 Registered Linux User: 179460 http://www.srcf.ucam.org/~pe208/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
On Thu, 27 Feb 2003, Kendall Bennett wrote: Keith Packard [EMAIL PROTECTED] wrote: I think the interfaces currently provided by XAA will probably remain usable, so you might as well implement them. Ok. Plus, we should have XAA expose special higher level functions for glyph rendering to the driver so that the graphics card can use the higher level data structures to speed this operation, rather than having the MI layer break the text operation into a (long) sequence of primitive Composite operations. What are you guys talking about? XAA already has hooks all over the place. Yes, most definitely. The current mechanism is not exactly efficient, and in fact is the reason why I want to hook some functions at a higher level so we can make this faster. Also when it comes to rendering text, one of the fastest ways of doing this is the way that OS/2 does it. Instead of caching any glyphs in offscreen video memory (terribly wasteful of offscreen video memory and no faster than using system memory bitmaps), you maintain a single large bitmap that matches the physical resolution of the screen (ie: 1280x1024 mono bitmap). When you need to draw text, you render the text into the mono bitmap in software at the necessary place on the screen, and when that is done pass the entire bitmap to be drawn to the hardware with a clip rectangle that covers just the text you just rendered into the bitmap. The clipping is real easy to do in the software setup stages for text rendering, and then you can blit the entire string to the hardware in one shot. XAA already does this!!! XAA has never cached glyphs in video ram. So fast, efficient text could be done in XFree86 if a single function was used to transfer an entire bitmap in the driver code (pre-clipping could easily be done before the driver code is called), and some high level code to maintain and render the glyphs into the pre-allocated large bitmap. Also I have been wondering about the accelerated anti-aliased text. Is all anti-aliased text in XFree86 done via the XRENDER extension and alpha blits? It is possible to implement accelerated anti-aliased text using simple 4-8 levels of mono bitmap blits using FreeType (that is what we used for it in our MGL graphics library). Yes, all AA text is done with the Render glyph operations which are defined in terms of the basic image composition primitive. Once you have hardware acceleration for image compositing, that's going to be a lot faster than any non-standard rendering path. That's why XAA hooks Glyphs and doesn't do it that way. XAA does not break glyph rendering into the Composite operator. Granted, if you have hardware alpha blits that will be the fastest way to do this. But if you don't have hardware alpha blits (and lots of cards supported by XFree86 do not), you can still speed up anti-aliased text quite a lot by using a 4 or 8 level scheme using multiple mono bitmaps. No you can't. This text is ALPHA BLENDED into whatever the background is. It is not text ImageText - ie. it is not an alpha blended string on top of a solid backing rectangle. Mark ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Fw: OOM problem
it is a font problem, but i don' t know if it is a misconfigured file or a bug so i forward to devel . (it would surprise me if it s a bug) I just installed the 4.3.0 release (from cvs, xf-4_3_0 tag) no error at compilation or at install I didn ' t change the /etc/fonts/fonts.conf file so it contains : dir/usr/X11R6/lib/X11/fonts/dir dir/usr/share/fonts/dir dir~/.fonts/dir so the problem is when I run an xterm -fa Courier (example taken from docs), it causes a Out Of Memory linux kernel error, though I have 256 MB of memory. If i change /etc/fonts/fonts.conf and I put only Type1 (by example), problems disappear and fc-cache works without parameter and xterm -fa Courier too I didn' t install any other fonts than which from X4.3 itself fc-cache cause problem when I run it without argument when I run with a font directory, it works Is it a bug ?or a misconfigured xft ? What font directories should I and should I not put in fonts.conf ? here s the result for each of my font directory (these created by make install) fc-cache: 100dpi: skipping, 397 fonts, 0 dirs fc-cache: 75dpi: skipping, 397 fonts, 0 dirs fc-cache: CID: caching, 0 fonts, 0 dirs fc-cache: Speedo: skipping, 0 fonts, 0 dirs fc-cache: TTF: skipping, 12 fonts, 0 dirs fc-cache: Type1: skipping, 29 fonts, 0 dirs fc-cache: cyrillic: caching, 0 fonts, 0 dirs fc-cache: encodings: skipping, 0 fonts, 1 dirs fc-cache: encodings/large: skipping, 0 fonts, 0 dirs fc-cache: local: skipping, 0 fonts, 0 dirs fc-cache: misc: skipping, 55 fonts, 0 dirs fc-cache: util: skipping, 0 fonts, 0 dirs and here is my X config file (path section) 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/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath /usr/X11R6/lib/X11/fonts/Type1 FontPath /usr/X11R6/lib/X11/fonts/local FontPath /usr/X11R6/lib/X11/fonts/TrueType FontPath /usr/X11R6/lib/X11/fonts/CID FontPath /usr/X11R6/lib/X11/fonts/Speedo FontPath /usr/X11R6/lib/X11/fonts/cyrillic FontPath /usr/X11R6/lib/X11/fonts/TTF EndSection so before make install, the file fonts.conf doesnn't seem to be usable before a little tweak Axel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Work in the sun
On Thu, Feb 27, 2003 at 03:14:35PM -0500, Mark Vojkovich wrote: I believe there already is. It seems to be letting alot of stuff through these days, but I expect it's nothing compared to what would happen if it were turned off. That's for sure. I get to see what the filter blocks, and there are many days when it would totally overwhelm the valid list traffic. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes Mark. On Thu, 27 Feb 2003, Paul Evans wrote: Is there not a spam filter for this kind of thing? -- Paul Evans (3rd Year CompSci at Pembroke College, Cambridge, England) [EMAIL PROTECTED] (university) [EMAIL PROTECTED] (alternate) ICQ# 4135350 Registered Linux User: 179460 http://www.srcf.ucam.org/~pe208/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Mark Vojkovich [EMAIL PROTECTED] wrote: What are you guys talking about? XAA already has hooks all over the place. Yes, it does! Now that I am learning more about this I am happy to see that someone saw fit to make it so XAA drivers can hook stuff at many levels. Very cool. It should be better documented though ;-) XAA already does this!!! XAA has never cached glyphs in video ram. Hmm, then how come in the XAA driver architecture there are methods to do mono blits from offscreen video memory? I just assumed that this meant the glyphs were being cached in offscreen video memory, but perhaps XAA is just using offscreen memory as a temporary 'ping ping' buffer in this case? Ie: for hardware that can't do system blits but can do blits from offscreen video memory? Granted, if you have hardware alpha blits that will be the fastest way to do this. But if you don't have hardware alpha blits (and lots of cards supported by XFree86 do not), you can still speed up anti-aliased text quite a lot by using a 4 or 8 level scheme using multiple mono bitmaps. No you can't. This text is ALPHA BLENDED into whatever the background is. It is not text ImageText - ie. it is not an alpha blended string on top of a solid backing rectangle. True. The way we implement in our library is that the core of the text glyphs (ie: the non-blended solid pixels) are drawn with a fast mono blit. Then we render the 4 levels of aliasing into the framebuffer with high speed software blending only for the pixels that need to be drawn (usually only 5% coverage for a typical sized glyph). Doing it that way is still *way* faster than drawing the entire glyph with software blending if you don't have hardware compositing. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Keith Packard [EMAIL PROTECTED] wrote: So fast, efficient text could be done in XFree86 if a single function was used to transfer an entire bitmap in the driver code (pre-clipping could easily be done before the driver code is called), and some high level code to maintain and render the glyphs into the pre-allocated large bitmap. That's how Render does text today, except that it allocates the temporary bitmap on the fly (which isn't a big deal with modern malloc implementations). Monochrome bitmaps the size of the screen are one thing, but 32bpp bitmaps at screen size are a bit large to keep around for this purpose (yes, Render glyphs really are 32bpp on LCD screens). Right, but I wasn't talking about RENDER in this case but the standard case of aliased text. Then again I imagine if there is a choice between aliased and anti-aliased text, no-one would want the aliased version anymore so performance is not important ;-) And yes, 32bpp bitmaps would be a little too large to keep around. Besides, the primary reason to keep large mono bitmaps around is because it makes it easier to render the text due to the packed bits in mono bitmaps. 32bpp is much easier to handle with bitmaps just the size of the text due to one pixel per DWORD ;-) Granted, if you have hardware alpha blits that will be the fastest way to do this. But if you don't have hardware alpha blits (and lots of cards supported by XFree86 do not), you can still speed up anti-aliased text quite a lot by using a 4 or 8 level scheme using multiple mono bitmaps. I suppose, but it wouldn't be compatible with the Render semantics. If I'd heard users complaining about text performance, I'd be more interested. Plus, the number of users with cards that can't support image compositing is rapidly declining; essentially any card that has even the smallest amount of acceleration for 3D graphics can accelerate Render. Very true, but if you consider the fact that right now there is only one graphics driver in XFree86 that actually has the composting functions enabled (excluding closed NVIDIA drivers), the multi-level scheme could accelerate anti-aliased text on a lot of hardware instantly. Then when people get the time, the composting functions could be implemented to make it better and faster where applicable. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Work in the sun
David Dawes [EMAIL PROTECTED] wrote: That's for sure. I get to see what the filter blocks, and there are many days when it would totally overwhelm the valid list traffic. What software are you using for SPAM filtering? We are using Spam Assassin now on our new mail server (about to switch over today!) and it seems to work pretty well (especially with the Bayesian filter enabled). Just curious what seems to work well for this list. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Thu, Feb 27, 2003 at 09:51:15AM -0800, Keith Packard wrote: Around 16 o'clock on Feb 27, Stefan Dirsch wrote: No. Will be some work to extract the CVS diff for me. So you can't reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now before looking deeper into this issue. I've just tried xf86cfg under 4.3 and didn't have any difficulties. One thing I did have to do was clean out ancient drivers from the modules directory -- I had several seg faults until I made sure I didn't have anything older than 4.3 installed. Strange. It only happens if libfreetype.so render module exists. I compile this against system libfreetype to get rid of some bugs in freetype2 which comes with XFree86 (some fonts can't be displayed any more which worked with freetype1 based freetype module). After loading this module every module gets a ERROR SIGSEGV caught! after loading. [...] Loading /usr/X11R6/lib/modules/fonts/libfreetype.so Module freetype: vendor=The XFree86 Project compiled for 4.3.0, module version = 2.0.2 Unloading /usr/X11R6/lib/modules/fonts/libfreetype.so Loading /usr/X11R6/lib/modules/fonts/libtype1.a Module type1: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.2 ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ERROR SIGSEGV caught! Maybe xf86cfg can't handle these modules. XFree86 loader can. Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Debugging in RH8?
Mike A. Harris wrote: Also, we are attempting to get XFree86 debug support integrated into future FSF gdb. The major holdup is basically nobody knows who the original authors of the patches were from way back when for proper attribution and copyright assignment and all the other joys the FSF requires. I know one of the authors was Paul Flinders, and I've got an email address for him still. Does anyone else know who all worked on the XFree86 gdb patches? The only history I know of it is: The version on the XFree86 site is 4.18 or somesuch. I took that and ported it about 60% functionally to gdb 5.0, which Paul then found out about and finished off the parts that weren't working. I later ported it to gdb 5.1.1, and it's partially ported to a more recent version as well. I was the original author. I have a record of one patch from Gerd Knorr (then [EMAIL PROTECTED]) which was the PPC port, however that might just be trivial enough to not need assignment (I've included it below). Apart from yourself I don't recall any other contributions but I will have another look over my email archives. I do still check over the list to see if anyone is reporting problems but hardly anyone ever does. I'm never sure whether to interpret this as a sign that nobody uses the modified GDB or that it works fine and no-one is having problems. Here is Gerd's patch. diff -u gdb-4.17/gdb/config/powerpc/nm-linux.h.xfree gdb-4.17/gdb/config/powerpc/nm-linux.h --- gdb-4.17/gdb/config/powerpc/nm-linux.h.xfreeMon Jun 7 18:56:58 1999 +++ gdb-4.17/gdb/config/powerpc/nm-linux.h Mon Jun 7 18:56:58 1999 @@ -39,6 +39,7 @@ #ifdef HAVE_LINK_H #include solib.h/* Support for shared libraries. */ +#include xfreemod.h/* Support for shared libraries. */ #define SVR4_SHARED_LIBS #endif diff -u gdb-4.17/gdb/config/powerpc/linux.mh.xfree gdb-4.17/gdb/config/powerpc/linux.mh --- gdb-4.17/gdb/config/powerpc/linux.mh.xfree Mon Jun 7 19:10:24 1999 +++ gdb-4.17/gdb/config/powerpc/linux.mhMon Jun 7 19:10:41 1999 @@ -9,7 +9,7 @@ XM_CLIBS= NAT_FILE= nm-linux.h -NATDEPFILES= infptrace.o solib.o inftarg.o fork-child.o corelow.o \ +NATDEPFILES= infptrace.o solib.o xfreemod.o inftarg.o fork-child.o corelow.o \ core-aout.o core-regset.o ppclnx-nat.o GDBSERVER_DEPFILES= low-linux.o ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Monitor section in config file?
Hi Guys, I see that sometimes the monitor section in the XF86Config file has a 'DisplaySize' value enabled (values like 400 300 seem typical). What is that value supposed to be? Is it the viewable size of the screen in millimeters or something? I assume it is optional? Also where do I find the docs on the XF86Config file format. I need to read up some more on this. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Work in the sun
On Thu, Feb 27, 2003 at 12:33:32PM -0800, Kendall Bennett wrote: David Dawes [EMAIL PROTECTED] wrote: That's for sure. I get to see what the filter blocks, and there are many days when it would totally overwhelm the valid list traffic. What software are you using for SPAM filtering? We are using Spam Assassin now on our new mail server (about to switch over today!) and it seems to work pretty well (especially with the Bayesian filter enabled). A combination of spam assassin and a home grown filter. The latter helps a lot with blocking virus spam. It's a little too aggressive in some areas for personal use, but a reasonable balance for a list like this. I'm planning to look at some other tools once I get a chance to stretch my legs after the release. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
On Thu, 27 Feb 2003, Kendall Bennett wrote: Mark Vojkovich [EMAIL PROTECTED] wrote: What are you guys talking about? XAA already has hooks all over the place. Yes, it does! Now that I am learning more about this I am happy to see that someone saw fit to make it so XAA drivers can hook stuff at many levels. Very cool. It should be better documented though ;-) I think there are very few reasons to hook stuff at higher levels. I don't believe you have a reason to do so. XAA already does this!!! XAA has never cached glyphs in video ram. Hmm, then how come in the XAA driver architecture there are methods to do mono blits from offscreen video memory? I just assumed that this meant the glyphs were being cached in offscreen video memory, but perhaps XAA is just using offscreen memory as a temporary 'ping ping' buffer in this case? Ie: for hardware that can't do system blits but can do blits from offscreen video memory? Mono blits from offscreen are only used for cached stipples. If the driver supports these it is the prefered method for stippling. Otherwise XAA will fall back to transparent blits from the pixmap cache or CPUToScreenColorExpansion. XAA's catch-all for non-AA text rendering renders each glyph with WriteBitmap. If the driver didn't provide WriteBitmap, XAA would provide one that used the driver's CPUToScreenColorExpansion routines. If the conditions were appropriate XAA would pre-composite the whole string and pass the result as a single bitmap. These conditions are that no glyph is more than 32 pixels wide (it's optimized to expect it to fit in one DWORD) and the rop is such that it doesn't matter if glyphs overlap (if the rop it XOR, for example, overlapping characters are supposed to XOR each other and a pre-composited string would be incorrect if it contained overlapping characters). The result is that essentially all rendering of proportional fonts goes through that path. Furthermore, for fixed fonts, XAA has scanline renderers that each glyph width up to 32 pixels. The benchmark cases are written in assembly. In this case it doesn't have to composite into a scratch buffer. I renders directly to the target surface. Note that with the Scanline CPUToScreenColorExpand routines, XAA can render directly into your graphics engine's DMA command buffer. I don't think you'll be able to write non-AA code that renders quicker than XAA, but you'll certainly risk rendering it incorrectly. For AA fonts you can hook the top level through XAAInfoRec.Glyphs. If you don't provide that level XAA will provide one for you which will optimize the 1 bit alpha glyphs, but will fall through to the mi routines for everything else. Mi will composite the glyphs into a single Picture and pass it through to the Composite operator and you'll have another chance to accelerate it at that time. XAA only provides two low-level Render-related primitives. The 8 bit Alpha texture + color and the Generic color texture composite functions. It's difficult to abstract things much beyond that since different graphics engines diverge quite a bit at this level. XAA 3 (XFree86 5's XAA) doesn't even try. It's only got the 8 bit alpha low-level primitive and everything else is higher level where the driver is expected to do alot more, though I suppose much of it could be offloaded to helper functions. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Debugging in RH8?
Paul Flinders [EMAIL PROTECTED] writes: I have a record of one patch from Gerd Knorr (then [EMAIL PROTECTED]) which was the PPC port, Still reading here :) Merging this stuff into fsf gdb is fine with me. Gerd ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
On Thu, 2003-02-27 at 14:42, Keith Packard wrote: Granted, if you have hardware alpha blits that will be the fastest way to do this. But if you don't have hardware alpha blits (and lots of cards supported by XFree86 do not), you can still speed up anti-aliased text quite a lot by using a 4 or 8 level scheme using multiple mono bitmaps. I suppose, but it wouldn't be compatible with the Render semantics. If I'd heard users complaining about text performance, I'd be more interested. Plus, the number of users with cards that can't support image compositing is rapidly declining; essentially any card that has even the smallest amount of acceleration for 3D graphics can accelerate Render. Actually, we get a fair number of complaints about AA-gnome-terminal speed, though some of that is just bugs in gnome-terminal that have now been fixed. But the software side could be made many times faster; especially considering that gnome-terminal is almost always text-on-constant background. And text-on-constant background should possible to make as fast as PCI/AGP write bandwidth. (*) (A lot slower than hardware compositing, but not remotely slow.) Regards, Owen (*) There are two levels of server-side optimization you can do for text-on-constant-background. a) If you keep track of the fact that a Pixmap is constant color, you can migrate from video ram to system ram about 100x faster than actually copying the data. Compositing system-ram-to-system-ram is fast. b) If you keep track of the fact that a Pixmap is constant color, you could have special-cased compositing routines that avoid even having to read the destination image. But this involves yet more paths in the compositing code. (Yuck.) This one is also harder to properly handle for the multiple-write case. You'd probably have to keep track of a constant-color _region_. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Input driver communication with calibration application?
Hi, I'm working with a touch screen driver in XFree86 4.0.x.. and I have need to communicate with the touch screen driver from an X application that is used for calibration. Specifically I want to be able to turn off existing calibration, and then give the driver updated configuration after the user is finished. What is the best way to perform this type of communication with an XInput driver from an X application? Thanks, Burt ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Work in the sun
David Dawes [EMAIL PROTECTED] wrote: What software are you using for SPAM filtering? We are using Spam Assassin now on our new mail server (about to switch over today!) and it seems to work pretty well (especially with the Bayesian filter enabled). A combination of spam assassin and a home grown filter. The latter helps a lot with blocking virus spam. It's a little too aggressive in some areas for personal use, but a reasonable balance for a list like this. I'm planning to look at some other tools once I get a chance to stretch my legs after the release. Cool. Are the home grown filters ones that work with Spam Assassin or are they separate filters you have created? I am currently using SpamCop, but am hoping that Spam Assassin will be better (and locally managed). If I didn't have SPAM filtering on my email address (which has been around for years, is on tons of web sites and tons of newsgroup postings, all prior to SPAM becoming a plauge!) I would probably get 3x as much email every day. I routinely delete on the order of 1000+ SPAM emails a week from my SpamCop account! Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Another RENDER question
The hardware I am dealing with does not support ARGB textures (at least not in 2D level, and I don't want to mess with DRI), but alpha blended bit blits. The difference being: While ARGB textures contain an alpha value for each pixel, the alpha blended bit blits render with a static alpha value for all of the bitmap data. Is this hardware capability of any use, be it RENDER or any other XAA function? Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Another RENDER question
On Fri, 28 Feb 2003, Thomas Winischhofer wrote: The hardware I am dealing with does not support ARGB textures (at least not in 2D level, and I don't want to mess with DRI), but alpha blended bit blits. The difference being: While ARGB textures contain an alpha value for each pixel, the alpha blended bit blits render with a static alpha value for all of the bitmap data. Is this hardware capability of any use, be it RENDER or any other XAA function? Not much in my option. The interesting area is alpha masks. While there are cases in render that you'll be able to accelerate, the semantics of the API are more generic where constant alpha is merely a special case of an alpha mask. Perhaps when we get the translucent window support (XFree86 5 timeframe, I believe) this hardware feature will be easier to expose. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Mark Vojkovich [EMAIL PROTECTED] wrote: We do. We have our own device driver abstraction layer and using the low level XAA functions does not map at all well to our driver modle. Hence hooking at the next level up (MID) will allow us to avoid the overheads of translating between the low level XAA model and our driver model. I forgot that you had your own driver API that you were translating to. ;-) Hooking WriteBitmap is reasonable to handle the proportional fonts. For fixed fonts you can replace the TEGlyph renderer and have it use the existing glyph_scanline_func[width - 1] to render into a scratch bitmap. See the XAATEGlyphRenderer for an example. Awesome, I will take a look at that. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
On Thu, Feb 27, 2003 at 05:01:19PM -0500, Owen Taylor wrote: (*) There are two levels of server-side optimization you can do for text-on-constant-background. Well, we can start with even more simple optimizations, like not doing the compositing when the clip region is empty. Currently if you unmap a vte window that is doing lots of Xtf antialiased text drawing, the X server is spending tons of time doing compositing that is just thrown away. http://fontconfig.org/cgi-bin/bugzilla/show_bug.cgi?id=29 Cheers, Matt [EMAIL PROTECTED] -- Matt Wilson Manager, Base Operating Systems Red Hat, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Monitor section in config file?
On Thu, 27 Feb 2003, Kendall Bennett wrote: Also where do I find the docs on the XF86Config file format. I need to read up some more on this. man XF86Config I see that sometimes the monitor section in the XF86Config file has a 'DisplaySize' value enabled (values like 400 300 seem typical). What is that value supposed to be? Is it the viewable size of the screen in millimeters or something? I assume it is optional? Correct in all cases, although when X -configure creates those values from DDC it currently uses a size derived from the monitor size in cm, rather than the size in millimetres of any particular mode. The screen dimensions reported by xdpyinfo are those calculated from the pitch - DPI - which is in turn calculated from the DisplaySize; rounding errors mean that the two sets of dimensions may not be the same :-( X -configure comments these values out because many apps used to get confused by having precise dpi values and displayed silly fonts. I think that at one time a 85x90 dpi screen would make Netscape use 75x100dpi fonts. I note that Netscape 7 allows you to calibrate the horizontal screen pitch, but not the vertical pitch. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Xfree supports Hppa ?
Hi all, Is there a port of Xfree for HPPA 7100LC ? Because, It's unable to compile correcty Xfree86 on this CPU. The compilation is OK, but i would like to use XFree86 -configure to configure my Xfree server, I have theses errors : Elf_RelocateEntry() Unsupported relocation type 4 Elf_RelocateEntry() Unsupported relocation type 1 Elf_RelocateEntry() Unsupported relocation type 0 Elf_RelocateEntry() Unsupported relocation type 240 Elf_RelocateEntry() Unsupported relocation type 22 Elf_RelocateEntry() Unsupported relocation type 0 Elf_RelocateEntry() Unsupported relocation type 60 Elf_RelocateEntry() Unsupported relocation type 18 Elf_RelocateEntry() Unsupported relocation type 0 Elf_RelocateEntry() Unsupported relocation type 72 Elf_RelocateEntry() Unsupported relocation type 18 Elf_RelocateEntry() Unsupported relocation type 0 Elf_RelocateEntry() Unsupported relocation type 236 Elf_RelocateEntry() Unsupported relocation type 22 Elf_RelocateEntry() Unsupported relocation type 0 Elf_RelocateEntry() Unsupported relocation type 132 Elf_RelocateEntry() Unsupported relocation type 18 (EE) LoadModule: Module pcidata does not supply version information (EE) Failed to load module pcidata (invalid module, 0) Gcc : 3.2.2 Glibc : 2.3.1 Kernel : Linux 2.4.20 for hppa Binutils : 2.13.90.0.18 and here is my /proc/cpuinfo processor : 0 cpu family : PA-RISC 1.1e cpu : PA7300LC (PCX-L2) cpu MHz : 180.00 model : 9000/778/B180L model name : Merlin L2+ 180 (9000/778/B180L) hversion: 0x5040 sversion: 0x0481 I-cache : 64 KB D-cache : 64 KB (WB) ITLB entries: 96 DTLB entries: 96 - shared with ITLB BTLB fixed : max. 16384 pages, pagesize=4096 (64MB) BTLB fix-entr. : 0 instruction, 0 data (8 combined) BTLB var-entr. : 0 instruction, 0 data (0 combined) bogomips: 119.60 software id : 2004841548 Could you help me please ? Thanks Best Regards -- Stephane Wirtel [EMAIL PROTECTED] WebSite : http://www.linux-mons.be GPG ID : 1024D/C9C16DA7 Fingerprint : 5331 0B5B 21F0 0363 EACD B73E 3D11 E5BC C9C1 6DA7 signature.asc Description: This is a digitally signed message part
Re: XRENDER extension docs?
Around 23 o'clock on Feb 27, Matt Wilson wrote: Well, we can start with even more simple optimizations, like not doing the compositing when the clip region is empty. Yeah, that would help in some cases. One does have to be careful to keep backing store working though. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
How to make cursor invisible
Hi i now that this might be a silly qestion but i try: I am doing a calibration utility for our touchscreen ... now i want to become the cursor invisible when runnning my calibration . I ve read once upon a time some code which did that but i dont find it anymore ... i remmeber that i have to register a new GC with a colour that is invisible and change the cursor to that GC .. but how excatly can i do that .. can somebody point me to a example code Cheers Rob -- _ *Robert Woerle **Technical Support | Linux PaceBlade Technology Europe SA* phone: +49 89 552 99935 fax: +49 89 552 99910 mobile: +49 179 474 45 27 email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.paceblade.com _ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
Hi, all Long time I maintain Linux 2.4.XX kernel tree , wich support multiple consoles. Ground priciple: linus tree kernel has 64 virtual consoles == virtual terminal. All 64 accessible by one user. Tuned 2.4.XX-backstreet-ruby kernel has same 64 virtual consoles but one user can use only range of consoles. Current I use different terminology: virtual terminlal (VT) == 8 virtual consoles (VC), Each VT may be bounded with independ keyboard. Normal (non root) user can access only VC inside their VT. Root can access all 64 VC. XFree86 is suid root process. XFree86 can access any VC. So XFree86 with parameter vtXX can choose right keyboard, if exist multiple VT == 8 VC. Current 2.4.XX-backstreet-ruby support only one text-mode console VGA, but XFree86 do not ask for text mode console. We can use stealth DUMMY console , which emulate addidtional VT and bounded with additional keyboards. files: http://startx.times.lv/ broken project: http://linuxconsole.sf.net linuxconsole.bkbits.com partialy worked project, same console code fbdev.bkbits.com Aivils Stoss please replay to me to. I do not feel like xf86 developer. p.s. Why I should pacth PCI-handling of XFree or Why XFree search and freezy innocent VGA adapters? I just rewrite: http://sourceforge.net/mailarchive/message.php?msg_id=2907175 does anyone know why you'd want this kind of locking going on anyway? is it to avoid two x servers trying to drive the same head? Don't know. I'd guess it has to do with braid-deadness of older VGA-compatible PCI/AGP hardware. There might be no other way to init the chips (change mode, even change single palette entry) than to go trough the VGA-compatible I/O ports. This range is legacy address decoded by the PCI devices. Since these legacy I/O ranges cannot be relocated (like normal MMIO I/O in PCI), only one PCI device (in system) may have it's legacy VGA address decoders enabled at single instance. This means that for most older hardware, one needs to specifically disable the I/O decoders on _all_ other VGA compatible PCI devices for the duration of programming the one that is really required. If more than one PCI device will attempt at decoding the same legacy I/O range (0x3d0-smt), serious brain damage would occur (could prompt a #SERR on PCI). Only the recent graphics chips may be programmed purely through MMIO I/O and even then they might require some short setup before going into that mode. (at least) because of this reason, xf86 has no choice but disable all I/O decoders on all VGA-compatible devices, and it goes a bit further by disabling all VGA-compatible PCI devices that it will not drive just to be on the safe side. Unless there is some system-provided common arbitration for these legacy ranges, this is the only way (from xf86's point of view). The right place for linux would be the kernel, although this might upset some xf86 folk since their code also does a lot of other stuff as well (like run the BIOS code init from previously disabled PCI display hardware to get it up and running, DDC probing if otherwise not possible). In my opinion a more generic resource management for this would be nice in the kernel but atm xf86 assumes (rightly so) that it will be the only application doing graphics stuff. This is difficult to solve (although in my opinion possible). Feel free to correct me if you feel that the technical data is inaccurate, I've currently trying to understand the lower levels of PCI and AGP eventually and don't claim to be an expert on it. Aleksandr Koltsoff ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[Fonts] OOM problem
it is a font problem, but i don' t know if it is a misconfigured file or a bug (it would suprise me) I just installed the 4.3.0 release (from cvs, xf-4_3_0 tag) no error at compilation or at install I didn ' t change the /etc/fonts/fonts.conf file so it contains : dir/usr/X11R6/lib/X11/fonts/dir dir/usr/share/fonts/dir dir~/.fonts/dir so the problem is when I run an xterm -fa Courier (example taken from docs), it causes a Out Of Memory linux kernel error, though I have 256 MB of memory. If i change /etc/fonts/fonts.conf and I put only Type1 (by example), problems disappear and fc-cache works without parameter and xterm -fa Courier too I didn' t install any other fonts than which from X4.3 itself fc-cache cause problem when I run it without argument when I run with a font directory, it works Is it a bug ?or a misconfigured xft ? What font directories should I and should I not put in fonts.conf ? here s the result for each of my font directory (these created by make install) fc-cache: 100dpi: skipping, 397 fonts, 0 dirs fc-cache: 75dpi: skipping, 397 fonts, 0 dirs fc-cache: CID: caching, 0 fonts, 0 dirs fc-cache: Speedo: skipping, 0 fonts, 0 dirs fc-cache: TTF: skipping, 12 fonts, 0 dirs fc-cache: Type1: skipping, 29 fonts, 0 dirs fc-cache: cyrillic: caching, 0 fonts, 0 dirs fc-cache: encodings: skipping, 0 fonts, 1 dirs fc-cache: encodings/large: skipping, 0 fonts, 0 dirs fc-cache: local: skipping, 0 fonts, 0 dirs fc-cache: misc: skipping, 55 fonts, 0 dirs fc-cache: util: skipping, 0 fonts, 0 dirs and here is my X config file (path section) 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/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath /usr/X11R6/lib/X11/fonts/Type1 FontPath /usr/X11R6/lib/X11/fonts/local FontPath /usr/X11R6/lib/X11/fonts/TrueType FontPath /usr/X11R6/lib/X11/fonts/CID FontPath /usr/X11R6/lib/X11/fonts/Speedo FontPath /usr/X11R6/lib/X11/fonts/cyrillic FontPath /usr/X11R6/lib/X11/fonts/TTF EndSection so before make install, the file fonts.conf doesnn't seem to be usable before a little tweak Axel ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[I18n] http://www.HappyHug.com, a great site with over 30 new links to free adult conte
Hi, A few months ago I started a website for adults: http://www.HappyHug.com Its a great site with over 30 new links to free adult content every day. Now I try to get a whole lot of visitors. Please visit my site and if you like it, than tell it to all your friends. Thanks, Ben Webmaster at HappyHug.com _ MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
[XFree86] no screen found error.
Hi all.. when ever i try to run startx it gives the no screen found error.. pls help thanks, atul ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] Probable bug at the nsc driver: switching consoles non functional
Regarding: Probable bug at the nsc driver: switching consoles non functional Email: [EMAIL PROTECTED] XFree86 Version: XFree86 4.3.0RC2 OS: SuSE 8.0 with kernels 2.4.18-SuSE and 2.4.20-SuSE Area: driver nsc Server: XFree86 (The XFree86 4.x server) Server: driver nsc Video Card: Geode GX1 with companion chip 5530 Description: I'm using an advantech pcm3350 SBC. I have reinstalled SuSE 8.0 with a minimal set-up (no X and yes to minimal system). About 250Mb was installed. Then I installed Xfree86 4.3.0RC2 using the Xinstall.sh script. No errors and so on. Then I copied the XFree86Config file from the previous setup (including the nsc module). When running startx everything was functional at 1024x768 16bpp. The windows manager is twm. When I use CRTL+ALT+Fx the screen flicks and goes to dark black. No characters -nada-. When I press CRTL+ALT+F7, the graphics are back again. If I pay attention, the consoles appears for a fraction of a second before switching to graphics, so the memory is not corrupted. I have changed the nsc line to vesa line, and the consoles and graphics are ok again. I can swith between them without corruption. When I put back nsc the black screens are back again. So I believe the problem is with the nsc driver itself. I have moved the kernel from 2.4.18-SuSE to 2.4.20-SuSE and the behaviour is the same. I have checked and I have framebuffer configured in the kernel (SVGA compiled in and others as modules). I know since SuSE puts the kernel config file in /proc/config.gz I do not have the FULL SERVER OUTPUT right now but no error is reported. I can get it but it is a Single Board Computer so I not trivial. Repeat By: With the nsc driver loaded, swith consoles using CRTL+ALT+Fx and I get only black screens. CRTL+ALT+F7 returns to graphics console. The Xserver is up and alive since I can export DISPLAY. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Selecting a monitor and changing refresh rate to 85Hz
Will any body please help me to select my monitor as sony cpd 1430 and to set the refresh rate to 85Hz. Actually my monitor is vintron, which is not in the database, but sony model is fine in windows, rh7, 7.1 and 8. Now I migrated to debian, and it is not giving me an option to choose the monitor. I need a 800*600 display. My video card is trident cyberblade i7 and my mouse is a microsoft serial 3 butten (actually, it is logitech) one. If any body helps me to edit the config file or send me some script to do that or the config file itself, i will be very happy and thankful regards ashok ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] intel i830 (newbie)
Hello I have only just started using linux, not sure if if this question has already been resolved. I have suse 8.1 and an intel i830 graphics chip. At the moment it can only support an 8 bit 1024x780 screen resolution. It has something to do with BIOS memory.. Will XFree86 4.3.0 solve this problem.. JP ---Legal Disclaimer--- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Racer on A31/ATI Radeon Mobility 7500 32 MB
Hi, I have the following problem with the latest racer (www.racer.nl) on my A31/ATI Radeon Mobility 7500 32 MB: 1) no smooth display (choking) 2) 8 fps on default gfx.ini (finetuning doesnt help much) 3) radeonUploadTexImages: ran into bound texture this is my Device: Section Device Identifier ATI Radeon Mobility 7500 #Driver vesa #Driver fbdev #Driver ati Driver radeon Option EnablePageFlip #Option UseFBDev true #Option AGPMode 4 Option AGPFastWrite 1 #Option SWcursor 1 #Option AGPSize 64 #Option RingSize 8 #Option BufferSize2 BusID 01:00:0 EndSection I found a thread on similar subject (http://lists.debian.org/debian-x/2002/debian-x-200211/msg00137.html) but I havent concluded much. aha, all my OpenGL programs work rather fine (all my own GL codes, but also glxgears, tuxracer etc.). can this be helped? thanks a lot Dominik -- -- Dominik Szczerba, Dr. CO-ME, D-ITET, ETZ F85 ETH, Gloriastr. 35 CH-8092 Zurich http://www.vision.ee.ethz.ch/~domi -- ii swear i never use vi^[:wqZZ -- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] Font 'fixed'
Regarding: Font 'fixed' Email: [EMAIL PROTECTED] XFree86 Version: 2.4.1.8 OS: Linux red hat 8.0 Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: matrox millennium g400 Description: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72) / 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.18-11smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present OS Kernel: Linux version 2.4.18-14 ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 12:13:11 EDT 2002 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 Feb 27 13:07:06 2003 (==) 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' Repeat By: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72) / 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.18-11smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present OS Kernel: Linux version 2.4.18-14 ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 12:13:11 EDT 2002 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 Feb 27 13:07:06 2003 (==) 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' ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Problem with linux in setting up display driver
Hi I have a Dell 8200 laptop with Pentium 4 and Nvidia GeForce 2 display driver. I tried to install Mandrake Linux (8.1, Linux 2.4.8-5mdkenterprise i686 [ELF]) and as expected the X system didnt work properly. I tried to do install the drivers downloaded from Nvidia site and but it still doesnt work. I am attaching the logfile with this mail. Can you please help me in setting up the display drivers With best regards Dev Dev SINGHAL ENST Bretagne [EMAIL PROTECTED] XFree86.0.0.log Description: Binary data
Re: [XFree86] Mouse repeater annoyance
Dr Andrew C Aitchison writes: On Wed, 26 Feb 2003, Peter Berg Larsen wrote: I am currently using RC2 (upgraded yesterday from 4.2.1) and is irritated by a 8-9 second freeze of X when switching to X from the console. This seems to happen because X is set to use a mouse repeater (that does not respond to commands), combined with that X resets the mouse when swithing to X from the console. This (long) freeze did not happen in 4.2.1, but probably changed with these: I have the same long freeze, but am not, as far as I am aware, using a repeater. I do have two mice, which doubles the delay. Could you please verify this? You just need to check where the mouse device points to. Real mice really should not have much delay. If you delay is really long you should edit pnp.c in the xfree86/input/mouse directory and add a #define EXTMOUSEDEBUG #define DEBUG to the file. Please send me the log file. Why reset the mouse when switching to X in the first place ? How can it be turned off? (It can't if I have read the code correct, so the actual question is whether it is to late to do anything about it) It isn't so much turning it off, but while the X server is switched away, something else may have put the mouse into some other state; eg most wheel mice can speak either PS/2 or IMPS/2. Yes. Many ugly things can happen while switched away. We could lower the retry count which should shorten the timeout. Corrently it is 10. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Problem with linux in setting up display driver
Did you Configure your XF86Config.new file? (At least that is what it is called in BSD) If you are in the root directory type: XFree86 configure Edit the default depth and then exit by typing: :wq! to exit and save over the read only file. The file should look something like this when you are done: Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDevice Mouse0 CorePointer InputDevice Keyboard0 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 dbe Load extmod Load glx Load record Load xtrap Load type1 Load freetype EndSection Section InputDevice Identifier Keyboard0 Driver keyboard Option XkbModel microsoft EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol wsmouse Option Device /dev/wsmouse Option Buttons 3 Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelName Monitor Model Option dpms EndSection Section Device Identifier Card0 Driver ati VendorName ATI BoardName Mach64 LB ChipSet ati ChipId 0x4c42 ChipRev 0xdc BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 Monitor Monitor0 DefaultDepth 16 SubSection Display Depth 16 EndSubSection EndSection (very few modifications need to be made to the file) Then when back at the command prompt type this: cp XF86Config.new /etc/XF86Config (This should copy the file to the directory needed by X-Server) Let me know I this helps, Jon Ireland -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dev Sent: Thursday, February 27, 2003 9:53 AM To: [EMAIL PROTECTED] Subject: [XFree86] Problem with linux in setting up display driver Hi I have a Dell 8200 laptop with Pentium 4 and Nvidia GeForce 2 display driver. I tried to install Mandrake Linux (8.1, Linux 2.4.8-5mdkenterprise i686 [ELF]) and as expected the X system didnt work properly. I tried to do install the drivers downloaded from Nvidia site and but it still doesnt work. I am attaching the logfile with this mail. Can you please help me in setting up the display drivers With best regards Dev Dev SINGHAL ENST Bretagne [EMAIL PROTECTED]
[XFree86] [XFree86(TM) Bug Report] Twinview wont work...
Regarding: Twinview wont work... Email: [EMAIL PROTECTED] XFree86 Version: 4.2.1.1 OS: Linux 2.4 running Debian 3.0 Area: xclient, twinview Server: XFree86 (The XFree86 4.x server) Video Card: nvidia GeForce 3 Ti2000 I'm using drivers downloaded from nvidia.com Description: This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.1.1 (Debian 4.2.1-5 20030122074040 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.19 i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Thu Feb 27 17:04:55 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor CTX (**) | |--Device GeForce3 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc101 (**) XKB: model: pc101 (**) Option XkbLayout se (**) XKB: layout: se (**) Option XkbVariant nodeadkeys (**) XKB: variant: nodeadkeys (==) Keyboard: CustomKeycode disabled (**) FontPath set to /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/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/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 VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0305 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,80,00 hdr 00 (II) PCI: 00:08:0: chip 1102,0002 card 1102,8040 rev 08 class 04,01,00 hdr 80 (II) PCI: 00:08:1: chip 1102,7002 card 1102,0020 rev 08 class 09,80,00 hdr 80 (II) PCI: 00:0a:0: chip 100b,0020 card 1385,f311 rev 00 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0201 card , rev a3 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0c (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1
[XFree86] Xnest trouble
Hi All! I'm new to Xnest and wanted to test the thing to get a Xterminal of a server onto my notebook. Both machines are running Redhat 8.0, the server is a dual-Xeon machine. Here's what I do on my notebook: Xnest :2 -query 192.168.1.66 -ac Sometimes I get a display and I can put in my username. But shortly afterwards something goes wrong an I get: Fatal server error: XDMCP fatal error: Session declined Maximum number of open sessions from your host reached. Most of the times I can't even see the login screen and the error comes after a short time. How can I avoid this? Thx, Reinhard Eilmsteiner ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.3.0rc2 and Radeon VE - sometimes works, sometimes not
On Wed, Feb 26, 2003 at 11:40:36PM -0500, hy0 wrote: There are some known problems with OEM cards (it appears to be your case). Thanks for info :-) 1. Make sure your monitor is connected during the boot. Don't plug/unplug monitor(s) after boot. Monitor is never unplugged. 2. Use Option CloneDisplay 0 Identifier ** ATI Radeon (generic) [radeon] Option CrtScreen Option CloneDisplay 0 Driver radeon Nothing changed. If you still have the same problem and you know how to deal with source code, you can try following patch. http://penguinppc.org/~daenzer/DRI/radeon-ddc.diff I will try it when XFree86-4.3.0 source will be available for download (can't get whole CVS). -- Free Software - find interesting programs and change them NetHack - meet interesting creatures, kill them and eat their bodies Usenet - meet interesting people from all over the world and flame them Decopter - unrealistic helicopter simulator, get it from http://decopter.sf.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Mouse repeater annoyance
On Thu, 27 Feb 2003, Dr Andrew C Aitchison wrote: Log file available at http://www.dpmms.cam.ac.uk/~werdna/free86-devel/log.debug.mouse.delay Sorry, http://www.dpmms.cam.ac.uk/~werdna/xfree86-devel/log.debug.mouse.delay ^ -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] XFree86-4.3.0 and DELL Inspiron: Mouse frozen
Regarding: XFree86-4.3.0 and DELL Inspiron: Mouse frozen Email: [EMAIL PROTECTED] XFree86 Version: 4.3.0-RC1 to 4.3.0 OS: Linux-2.4.20 (RedHat rawhide) Area: mouse driver Server: XFree86 (The XFree86 4.x server) Video Card: ATI Rage mobility (loads r128 driver) Description: When X is started for xdm/kdm/gdm it takes a full minute for the login screen to appear and the mouse is frozen in the middle of the screen. This does not happen with 4.2.0. Repeat By: Client is DELL Inspiron 4000, which has ATI Rage mobility graphics, and ps/2 mouse. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] xserver error with redhat 7.3 upgrade
To whom it may concern, I upgraded a redhat 7.2 box to redhat 7.3 and all went well except the x server will not start. I got the following message (see forwarded message below) when I ran startx. If you can offer any assistance, it would be greatly appreciated. Jeff - Forwarded by Jeffrey P Miller/118906/EKC on 02/27/03 01:53 PM - root [EMAIL PROTECTED] 02/27/03 01:51 PM To: [EMAIL PROTECTED] cc: Subject: 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: Thu Feb 27 13:44:55 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor SUN0567 (**) | |--Device Matrox Millennium II (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.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 = 0x8000600c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7180 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7181 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:04:0: chip 8086,7110 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:04:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:04:3: chip 8086,7113 card , rev 01 class 06,80,00 hdr 00 (II) PCI: 00:07:0: chip 102b,051b card 102b,2100 rev 00 class 03,00,00 hdr 00 (II) PCI: 00:0c:0: chip 10b7,9050 card , rev 00 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x04 (VGA_EN is cleared) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: (II) Bus 1 prefetchable memory range: (II) Bus -1: bridge is at (0:4:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(0:7:0) Matrox MGA 2164W rev 0, Mem @ 0xfd00/24, 0xfedfc000/14, 0xfe00/23 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0x0010 -
Re: [XFree86] Problem with linux in setting up display driver
We can give you advice on setting up the open source drivers that come with XFree86. Basically, the nv driver that ships with XFree86 didn't support GeForce2 Go until recently. It will work in the upcoming XFree86 4.3 and in the 4.2.99.x snapshots on ftp.xfree86.org, so you can get it to work by upgrading to one of those. If you want help installing NVIDIA's binary drivers you can get that from the Linux forum on www.nvnews.net. Those should work with your current XFree86 version. Mark. On Thu, 27 Feb 2003, dev wrote: Hi I have a Dell 8200 laptop with Pentium 4 and Nvidia GeForce 2 display driver. I tried to install Mandrake Linux (8.1, Linux 2.4.8-5mdkenterprise i686 [ELF]) and as expected the X system didn't work properly. I tried to do install the drivers downloaded from Nvidia site and but it still doesn't work. I am attaching the logfile with this mail. Can you please help me in setting up the display drivers With best regards Dev Dev SINGHAL ENST Bretagne [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] intel 845g problems...
Hello all. I have two machines with intel 845g cards, one of which works and one of which doesn't. The one that doesn't is a dell, and the one that does is just a white box with an integrated 845g on the motherboard. By not working, I mean that the dell only displays at 640x480, and it draws images improperly, i.e. the desktop image has a bunch of erroneous lines over the top few inches of the screen, whereas the other machine can do 1024x768 with no visual errors. These results are with the i810 driver specified in xf86config-4. Using the vesa driver, both cards work. Attached is the output from both machines of lspci -vv. Both cards have the same pciid, 8086, 2562, but they have different subsystem id's. Has anyone else seen this problem? I'm wondering if this is caused by my backporting of the 845 patch or if its a problem with the driver itself. If noone else has seen this problem, I can try the latest build of X on the nonworking machine. Thanks again for all of your amazing work, cardenas -- michael cardenas | lead software engineer, lindows.com hyperpoem.net | GNU/Linux software developer people.debian.org/~mbc | encrypted email preferred Let your life be a counter-friction to stop the machine. - Henry David Thoreau pgp0.pgp Description: PGP signature
Re: [XFree86] Keyboard not working with latest CVS
On Thu, 2003-02-27 at 03:51, David Dawes wrote: It sounds like your Xlib has the wrong path for XKeysymDB. Did you install it in the same ProjectRoot as it was built for (lots of things can break if you don't)? I just did a make install, and there's a XKeysymDB under the ProjectRoot I built for. The original one is still in its old location, this is the one it's being read when X starts. strings .../lib/libX11.so | grep XKeysymDB [EMAIL PROTECTED]:~/cvs/X-install/lib strings libX11.so | grep XKeysymDB /home/garetxe/cvs/X-install/lib/X11/XKeysymDB [EMAIL PROTECTED]:~/cvs/X-install/lib ls -l $(strings libX11.so | grep XKeysymDB) -r--r--r--1 garetxe users8298 feb 26 12:29 /home/garetxe/cvs/X-install/lib/X11/XKeysymDB But it might be just that my system isn't properly configured and the wrong libX11 (the one under /usr/X11R6/lib/) is loaded instead for some reason. Looking to the relevant code in libX11 I agree it should work. Honestly, I don't think you should waste any more time on this unless someone else with a sane install of everything else sees the same, it might just as well be a bug somewhere else (in the computer chair interface probably :-)), and my system works just fine anyway. Thanks for your patience, Iaki PD: Not everything is complaints btw :-), the new X rocks, finally XVideo for my card and things such as the translucent cursors and easy font management are very nice, I had been wanting to have them for a long time. Thanks a lot for the superb work. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI Radeon 7500 series
From: neal [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Date: Thu, 27 Feb 2003 14:09:39 -0700 This is a multi-part message in MIME format. --=_NextPart_000_002E_01C2DE69.DE312410 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I am really wondering.. with X WINDOWS as good as they say it is.How come there isn't any = drivers for ATI Radeon 7500? I installed it and now I can't get rid of = it becasue it doesn't support that driver. So please have a driver for that someday? The Radeon 7500 has been supported for a LONG time. I have several. What version are you running and why do you believe it does not support the 7500? 4.3 (just out today) does have MUCH improved support for these with many performance enhancements and bug fixes. In you configuration, the device should specify 'Driver0 ati'. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] xfree from source tarballs
Two different machines, different video cards. Any attempt to startx and I get and xauth and xinit errors abiyt shared libraries and libXmuu.so.1. The closest thing I could fine is this from Google: http://lists.suse.com/archive/suse-linux-e/2001-Sep/0418.html Tried it, no joy. -- Don't be afraid to try something. Remember, amateurs built the ark, professionals built the Titanic. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] ATI Radeon 7500 series
I'm having the same problem with my workstation I also have an ATI Radeon and the X server just will not start. I've even installed Xfree86 4.3 today and still no luck. I've tried it on 7.2,7.38.0 to no avail. Thanks, CMWII -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kevin Oberman Sent: Thursday, February 27, 2003 4:26 PM To: [EMAIL PROTECTED] Subject: Re: [XFree86] ATI Radeon 7500 series From: neal [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Date: Thu, 27 Feb 2003 14:09:39 -0700 This is a multi-part message in MIME format. --=_NextPart_000_002E_01C2DE69.DE312410 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I am really wondering.. with X WINDOWS as good as they say it is.How come there isn't any = drivers for ATI Radeon 7500? I installed it and now I can't get rid of = it becasue it doesn't support that driver. So please have a driver for that someday? The Radeon 7500 has been supported for a LONG time. I have several. What version are you running and why do you believe it does not support the 7500? 4.3 (just out today) does have MUCH improved support for these with many performance enhancements and bug fixes. In you configuration, the device should specify 'Driver0 ati'. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI Radeon 7500 series
On Thu, 27 Feb 2003, neal wrote: I am really wondering.. with X WINDOWS as good as they say it is.How come there isn't any drivers for ATI Radeon 7500? I installed it and now I can't get rid of it becasue it doesn't support that driver. So please have a driver for that someday? Stop wondering. Stop trolling. Start reading. This message posted to you from a machine with an out-of-the-box 3D accelerated Red Hat 8.0. Oisin Feeley. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] ATI Radeon 7500 series
On Thu, 27 Feb 2003, Clarence Wiggins, II wrote: I'm having the same problem with my workstation I also have an ATI Radeon and the X server just will not start. I've even installed Xfree86 4.3 today and still no luck. I've tried it on 7.2,7.38.0 to no avail. snip unnecessarily long included posts How do you know it's the same problem?. It's just the same _symptom_ which could be due to one of many problems. I am _assuming_ that when you say 7.2,7.38.0 you refer to versions of the Red Hat distribution? If so then should stick with the included version of XFree86 that comes with Red Hat 8.0. It works for me out of the box with my Radeon 7500. If you want more help: examine your log files, see if you can understand the problem. Do a Google search. Then post on the list asking for help. HTH, Oisin Feeley ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Help me!
On Thu, 27 Feb 2003, Jacek [iso-8859-2] Pop³awski wrote: On Thu, Feb 27, 2003 at 09:17:58AM +0800, tiongnam wrote: My card is ATI card. but my XFree86 didn't work !Hope you can help me. In your log I found you are using 4.1.0, it's quite old release and doesn't support new ATI cards. Solution: update XFree86. Better yet, you're running under VMWare, so use the vmware driver. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] ATI Radeon 7000/VE, window or menu moving problem at 1280x1024 24bpp
Regarding: ATI Radeon 7000/VE, window or menu moving problem at 1280x1024 24bpp Email: [EMAIL PROTECTED] XFree86 Version: XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 OS: Debian GNU/Linux 3.0 woody Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: (II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (--) RADEON(0): Chipset: ATI Radeon VE (AGP) (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xe800 (--) RADEON(0): MMIO registers at 0xff8f (--) RADEON(0): BIOS at 0xff8c (--) RADEON(0): VideoRAM: 65536 kByte (64-bit SDR SDRAM) (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12000 max=3; xclk=14500 Description: When moving a window or opening a menu, horizontal lines appear. Observed at 1280x1024x24. Not observed at 1152x864x24 (or lower res), nor at 1280x1024x8. CPU: Pentium IV 2.4 GHz mb: Intel D845PESV RAM: 1 Go Repeat By: Debian woody fresh install. Configure X server for 1280x1024x24bpp (default refresh rate will be 85 Hz) Open Gnome or KDE, move a window or open menu, observe flicking. Other report of the bug found with Google Groups http://groups.google.com/groups?q=xfree86+1280x1024+radeonhl=enlr=ie=UTF-8oe=UTF-8selm=9_DM8.8359%24Hj3.26739%40newsfeeds.bigpond.comrnum=1 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86(TM) Bug Report] ATI Radeon 7000/VE, window or menu moving problem at 1280x1024 24bpp
Known bug in line drawing acceleration in Radeon driver prior to 4.3. It is supposed to be fixed in that release, but I have not tried it yet. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 From: [EMAIL PROTECTED] (Marc Mongenet) Sender: [EMAIL PROTECTED] Date: Thu, 27 Feb 2003 14:57:40 -0800 (PST) Regarding: ATI Radeon 7000/VE, window or menu moving problem at 1280x1024 24bpp Email: [EMAIL PROTECTED] XFree86 Version: XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 OS: Debian GNU/Linux 3.0 woody Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: (II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (--) RADEON(0): Chipset: ATI Radeon VE (AGP) (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xe800 (--) RADEON(0): MMIO registers at 0xff8f (--) RADEON(0): BIOS at 0xff8c (--) RADEON(0): VideoRAM: 65536 kByte (64-bit SDR SDRAM) (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12000 max=3; xclk=14500 Description: When moving a window or opening a menu, horizontal lines appear. Observed at 1280x1024x24. Not observed at 1152x864x24 (or lower res), nor at 1280x1024x8. CPU: Pentium IV 2.4 GHz mb: Intel D845PESV RAM: 1 Go Repeat By: Debian woody fresh install. Configure X server for 1280x1024x24bpp (default refresh rate will be 85 Hz) Open Gnome or KDE, move a window or open menu, observe flicking. Other report of the bug found with Google Groups http://groups.google.com/groups?q=xfree86+1280x1024+radeonhl=enlr=ie=UTF-8oe=UTF-8selm=9_DM8.8359%24Hj3.26739%40newsfeeds.bigpond.comrnum=1 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Selecting a monitor and changing refresh rate to 85Hz
First: For some odd reason, your message was a reply to the announcement about the tagging of XFree 4.3.0. It's helpful if you do not send messages as replies to other ones when you mean to start a new thread, because you'll help to keep the threads on their own topics. Now, on to the information you need. By doing a simple search on google.com for sony cpd 1430, I found a couple sites that give the VSync and HSync for this monitor as: VSync: 55 - 110Hz HSync: 28 - 58kHz So, for XFree 4.X, you just need to add a line like the following to your XF86Config file under the Monitor section: VertRefresh 55-110 Then, under the Screen section, set the DefaultDepth to the desired color depth (8bit, 16bit, 24bit color): DefaultDepth 8 and then, make a SubSection like the following: SubSection Display Depth 8 Modes 800x600 EndSubSection If I'm correct, these entries should get you what you're looking for. However, I haven't had time to experiment with your setup, so I could very well be wrong. HTH. -Andy ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] ATI Radeon 7500 series on a Red Hat 8.0 workstation
I'm having a problem with Xfree86 starting on my workstation. I'm using Red Hat 8.0 distribution on a white box. I know some users have had no problems with an ATI Radeon 7500 graphics card working on their Red Hat system right out of the box but for some reason I'm have some problem with it. I hope I have supplied enough information for someone to help me out. Thanks for your help, CMWII XFree86.0.log Description: Binary data XFree86.setup.log Description: Binary data # File generated by anaconda. Section ServerLayout Identifier Anaconda Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDevice Mouse1 SendCoreEvents InputDeviceKeyboard0 CoreKeyboard EndSection Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # 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. FontPath unix/:7100 EndSection Section Module Load dbe Load extmod Load fbdevhw Load dri Load glx Load record Load freetype Load type1 EndSection Section InputDevice Identifier Keyboard0 Driver keyboard # Option AutoRepeat500 5 # when using XQUEUE, comment out the above line, and uncomment the # following line # Option Protocol Xqueue # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option Xleds 1 2 3 # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option XkbModel pc102 # If you have a US Microsoft Natural keyboard, you can use: # Option XkbModel microsoft # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option XkbLayout de # or: # Option XkbLayout de # Option XkbVariantnodeadkeys # # If you'd like to switch the positions of your capslock and # control keys, use: # Option XkbOptionsctrl:swapcaps Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us #Option XkbVariant #Option XkbOptions EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/psaux Option ZAxisMapping 4 5 Option Emulate3Buttons no EndSection Section InputDevice Identifier Mouse1 Driver mouse Option Device/dev/input/mice Option Protocol IMPS/2 Option Emulate3Buttons no Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync 30-70 VertRefresh 50-160 Option dpms EndSection Section Device # Some 7500 boards aparently need this option enabled to work - bug (#62760) # Option CrtScreen Identifier ATI Radeon 7500 Driver radeon VendorName ATI Radeon 7500 BoardName ATI Radeon 7500 #BusID EndSection Section Screen Identifier Screen0 Device ATI Radeon 7500 Monitor Monitor0 DefaultDepth16 Subsection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubsection EndSection Section DRI Mode 0666 EndSection
[XFree86] resume problem
Hello -- after resume from sleep, xclock assumes hardware clock is GMT and adjusts accordingly this is incorrect for those of us with the hardware clock set to local time -- Monique Morin This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.2.99.902 (4.3.0 RC 2) Release Date: 17 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.7-10custom i686 [ELF] Build Date: 18 February 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 Feb 27 17:57:56 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Selected Monitor (**) | |--Device ATI (**) |--Input Device Default Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Default Mouse (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/truetype. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/truetype). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/truetype/openoffice. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/truetype/openoffice). (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/TrueType,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/75dpi (==) 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.2.99.902, 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.2.99.902, 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,1a30 card , rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,2482 card 8086,4541 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:2: chip 8086,2487 card 8086,4541 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev 42 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,248c card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,248a card 8086,4541 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:5: chip 8086,2485 card 1013,5959 rev 02 class 04,01,00 hdr 00 (II) PCI: 00:1f:6: chip 8086,2486 card 14f1,5421 rev 02 class 07,03,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4c66 card 1028,00d4 rev 01 class 03,00,00 hdr 00 (II) PCI: 02:00:0: chip 10b7,9200 card 1028,00d4 rev 78 class 02,00,00 hdr 00 (II) PCI: 02:01:0: chip 104c,ac42 card 4000, rev 00 class 06,07,00 hdr 82 (II) PCI: 02:01:1: chip 104c,ac42 card 4800, rev 00 class 06,07,00 hdr 82 (II) PCI: 02:01:2: chip 104c,8027 card 1028,00d4 rev 00 class 0c,00,10 hdr 80 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,7), 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: 0x000e (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)
[XFree86] problem setup X window
Dear sir, I have problem at setup X window system in RedHat 7.3 this error message : XIO: Fatal error 104 (Connection rest by peer) on X server :0.0 after 0 requests (0 known processed) with 0 evens remaining Fatal server error : no screen found And prompt this my monitor loss or hiden (Parse error on line 102 of section Keyboard in file /etc/X11/XF86Config ignoring obsolote keyword LeftAlt Parse error on line 102 of section keyboard in file /etc/X11/XF86Config META is not Valid keyword in this section. My PC used VGA Card adapter : S3 Trio 64V2/DX or /GX and monitor : GTC GM14L How to solution this problem ? Thank's BestRegard, edisuardi [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Geforce2 Go and new xfree 4.3
On Fri, 28 Feb 2003, Sebastien Cereze wrote: Hi everybody, I checked the graphics card driver list and there's no trace of this card. I guess it's still not working but can somebody confirm it to me ? What list are you refering to? GeForce2 Go should work automagically with 4.3. No need for special config file options or anything. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Geforce2 Go and new xfree 4.3
It's not supported with any previous official versions of XFree86. You need to be running 4.3 or one of the 4.2.99.x pre-4.3 snapshots. It should just work. Mark. On Thu, 27 Feb 2003 [EMAIL PROTECTED] wrote: Hello, I am with you. I have the video card GeForce2 Go on Redhat Linux 8.0 Dell Laptop Inspiron 2650 video RAM 16MB. I'm still trying to figure that out how to attack this video card working. Could you give me some advice how to twist this?? Thanks! Joe Cho [EMAIL PROTECTED] - Original Message - From: Sebastien Cereze [EMAIL PROTECTED] Date: Thursday, February 27, 2003 8:55 pm Subject: [XFree86] Geforce2 Go and new xfree 4.3 Hi everybody, I checked the graphics card driver list and there's no trace of this card. I guess it's still not working but can somebody confirm it to me ? Thanks ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Geforce2 Go and new xfree 4.3
thanks Mark that's a good news regards - Original Message - From: Mark Vojkovich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 28, 2003 12:16 PM Subject: Re: [XFree86] Geforce2 Go and new xfree 4.3 It's not supported with any previous official versions of XFree86. You need to be running 4.3 or one of the 4.2.99.x pre-4.3 snapshots. It should just work. Mark. On Thu, 27 Feb 2003 [EMAIL PROTECTED] wrote: Hello, I am with you. I have the video card GeForce2 Go on Redhat Linux 8.0 Dell Laptop Inspiron 2650 video RAM 16MB. I'm still trying to figure that out how to attack this video card working. Could you give me some advice how to twist this?? Thanks! Joe Cho [EMAIL PROTECTED] - Original Message - From: Sebastien Cereze [EMAIL PROTECTED] Date: Thursday, February 27, 2003 8:55 pm Subject: [XFree86] Geforce2 Go and new xfree 4.3 Hi everybody, I checked the graphics card driver list and there's no trace of this card. I guess it's still not working but can somebody confirm it to me ? Thanks ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86(TM) Bug Report] ATI Radeon 7000/VE, window or menu moving problem at 1280x1024 24bpp
From: George Lindholm [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Date: Thu, 27 Feb 2003 15:22:41 -0800 Kevin Oberman wrote: Known bug in line drawing acceleration in Radeon driver prior to 4.3. It is supposed to be fixed in that release, but I have not tried it yet. It's actually gotten worse the last couple of days. A couple of days ago I was just getting horizonal lines alongside the cursor. With the 4.3 release, I'm getting lines all over the screen (2048x1536x24, Radeon 7500) Ouch! Sounds like the NoLineAccel option for the ati driver needs to be re-implemented. It was in CVS for quite a while but was removed when the driver was believed to be fixed. (I only read the CVS logs and have nothing to do with actually fixing the code.) This may not be the line drawing problem. When you said getting lines all over the screen, did it appear to be noise/snow or to be some residual lines from previous drawing not being erased? If it's first case, that would be display buffer under flow problem. Otherwise it's line drawing problem. To narrow down the problem, try following two things: 1. Change to lower resolution (like 1024x768) or color depth (like 16 bpp), does the problem still happen? 2. Use Option SWcursor in your config file, will this alleviate the problem? If these two things have effects on your problem, it's the display buffer problem. This problem is caused by memory latency to display buffer. It depends on the type of memory on your card, the resolution/depth you are using, and hardware cursor mode, etc. There is a way to calculate the bandwidth requirement and set corresponding registers to avoid this problem. But this is not implemented in current radeon driver, instead, the driver just uses the default BIOS settings which worked fine for most cases, but may have problem with high resolution modes on some cards. 4.3 release can indeed make this problem more evident when it uses ARGB cursor. If this is proven to be the case, hopefully it can be taken care of in the near future. Hui ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] error sent-please sent correction
sir, i have sent the error i get while viewing X windos applications. please give me the corrections for that. thank you sivamurugesh _ XFree86.log Description: Binary data
[XFree86] no Input Device
Hi guys, How to configure X without any input device (i.e keyboard and mouse) Thanks Vinayak ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
