RE: [XFree86] KDrive Initialization Error
Not yet, I'm still working on it. Regards, Kevin Solomon Systech Limited Direct line: 86169830 Ext: 8830 Email: [EMAIL PROTECTED] Website: http://www.solomon-systech.com -Original Message- From: wile [mailto:[EMAIL PROTECTED] Sent: 2007年8月7日 10:48 To: [EMAIL PROTECTED] Subject: [XFree86] KDrive Initialization Error hi: solomon－systech? are you applying phone's BSP? ^_^ I'm facing the same program that:run Xfbset,get the msg:No screens found.somebody says,the reason is the Screen device no right. Your program is ok? may U tell me something about this program? TKS A LOT. zhouwei 20070807 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] using dell 2407 WFPb with xfree86 4,5
Hi, Please visit http://www.xfree86.org/4.2.0/XF86Config.5.html. May be helpful. Regards, Kevin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rolf Ofsti Sent: 2007年7月26日 17:51 To: xfree86@XFree86.Org Subject: [XFree86] using dell 2407 WFPb with xfree86 4,5 Dear Xfree I am trying to use xfree86 v. 4,5 with a new DELL 24 widescreen but get the message: Out of range signal. Cannot display this video mode. Change computer display mode to 1920 x 1200 @ 60 hz. To change the computer display to this mode seems not to be an option with my present videocard. Is there anyway i can configure xfree86 to overcome this? Sincerely R. Ofsti ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] install cross-compiled tinyx error
Dear all, I have successfully cross compiled Tiny-X (Xfbdev, XFree86 revision 4.6), but when I tried to install it, some error occurred. Does anyone can help me? Actually, the error occurred at installing the font related thing. I have searched on Internet, and got some answers, but I could not fully understand them. Here's what I found on the Internet. == First, this is not a snippet from an XFree86 install. This is a separate install of the fontconfig library. Secondly (and because of the first), this build picked up the build host's host.def which doesn't set CrossCompiling to YES. Marc. == I do set CrossCompiling to YES in my host.def. How could I solve this problem? Thanks! Here's part of the installing log file. make[3]: Entering directory `/home/kevinzhu/TinyXR46/build/fonts/util' + install -c -m 0444 map-ISO8859-1 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-2 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-3 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-4 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-5 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-7 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-8 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-9 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-10 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-11 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-13 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-14 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-15 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-ISO8859-16 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-JISX0201.1976-0 /home/kevinzhu/X11R6/lib/X11/fonts/util + install -c -m 0444 map-KOI8-R /home/kevinzhu/X11R6/lib/X11/fonts/util install -c ucs2any /home/kevinzhu/X11R6/bin/ucs2any install -c -m 0755 bdftruncate.pl /home/kevinzhu/X11R6/bin/bdftruncate install in fonts/util done make[3]: Leaving directory `/home/kevinzhu/TinyXR46/build/fonts/util' installing in fonts/bdf... make[3]: Entering directory `/home/kevinzhu/TinyXR46/build/fonts/bdf' installing in fonts/bdf/misc... make[4]: Entering directory `/home/kevinzhu/TinyXR46/build/fonts/bdf/misc' install -c -m 0444 fonts.alias /home/kevinzhu/X11R6/lib/X11/fonts/misc/fonts.alias set -x; LD_LIBRARY_PATH=../../../exports/lib FONTCONFIG_PATH=../../../lib/fontconfig ../../../exports/bin/fc-cache -f -v /home/kevinzhu/X11R6/lib/X11/fonts/misc + LD_LIBRARY_PATH=../../../exports/lib + FONTCONFIG_PATH=../../../lib/fontconfig + ../../../exports/bin/fc-cache -f -v /home/kevinzhu/X11R6/lib/X11/fonts/misc /bin/sh: ../../../exports/bin/fc-cache: cannot execute binary file make[4]: *** [install] Error 126 make[4]: Leaving directory `/home/kevinzhu/TinyXR46/build/fonts/bdf/misc' make[3]: *** [install] Error 2 make[3]: Leaving directory `/home/kevinzhu/TinyXR46/build/fonts/bdf' make[2]: *** [install] Error 2 make[2]: Leaving directory `/home/kevinzhu/TinyXR46/build/fonts' make[1]: *** [install] Error 2 make[1]: Leaving directory `/home/kevinzhu/TinyXR46/build' make: *** [install] Error 2 Regards, Kevin Solomon Systech Limited Direct line: 86169830 Ext: 8830 Email: [EMAIL PROTECTED] Website: http://www.solomon-systech.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] building tinyx with freetype2 problem
Dear Marc, The version is 4.6.0. Thanks! Regards, Kevin Solomon Systech Limited Direct line: 86169830 Ext: 8830 Email: [EMAIL PROTECTED] Website: http://www.solomon-systech.com -Original Message- From: Marc Aurele La France [mailto:[EMAIL PROTECTED] Sent: 2007年6月28日 11:22 To: kevin Cc: xfree86@XFree86.Org Subject: Re: [XFree86] building tinyx with freetype2 problem On Tue, 12 Jun 2007, kevin wrote: I built freetype2 in /usr/local/. Here's the file structure. [EMAIL PROTECTED]:/usr/local/include# ls ft2build.h jerror.hjpeglib.h libpng12 pngconf.h x264.h x264_gtk_enum.h freetype2 jconfig.h jmorecfg.h libpng png.h soundtouch x264_gtk.h and the library is in /usr/loca/lib/ I define Freetype2Dir /usr/local in my host.def file. When compiling the source code, an error occurred. /* part of host.def */ #define HasFreetype2 YES #define Freetype2Dir /usr/local The error is as follows. gcc -m32 -c -O2 -fno-strength-reduce -fno-strict-aliasing -ansi -Wall -Wpointer-arith -Wundef -I. -I../../exports/include -I/usr/local/include -I/usr/local/include/freetype2 -I../../extras/fontconfig/src -I../../exports/include-Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DFC_DEFAULT_FONTS='' -DHAVE_EXPAT -DXFREE86_FT2 -fPIC fcfreetype.c fcfreetype.c:31:10: #include expects FILENAME or FILENAME fcfreetype.c: In function `FcFreeTypeQuery': fcfreetype.c:542: warning: implicit declaration of function `FT_MODULE_CLASS' fcfreetype.c:542: error: dereferencing pointer to incomplete type fcfreetype.c:542: error: invalid type argument of `-' fcfreetype.c:542: error: dereferencing pointer to incomplete type Could anyone help me? Thanks in advance! What XFree86 version are you trying to build. There have been several fixes in this area since 4.6.0. Marc. +--+--+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and| fax:1-780-492-1729 | |Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +--+ | University of Alberta | | | Edmonton, Alberta |Standard disclaimers apply| | T6G 2H1 | | | CANADA | | +--+--+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] building tinyx with freetype2 problem
Hi, I built freetype2 in /usr/local/. Here's the file structure. [EMAIL PROTECTED]:/usr/local/include# ls ft2build.h jerror.hjpeglib.h libpng12 pngconf.h x264.h x264_gtk_enum.h freetype2 jconfig.h jmorecfg.h libpng png.h soundtouch x264_gtk.h and the library is in /usr/loca/lib/ I define Freetype2Dir /usr/local in my host.def file. When compiling the source code, an error occurred. /* part of host.def */ #define HasFreetype2 YES #define Freetype2Dir /usr/local The error is as follows. gcc -m32 -c -O2 -fno-strength-reduce -fno-strict-aliasing -ansi -Wall -Wpointer-arith -Wundef -I. -I../../exports/include -I/usr/local/include -I/usr/local/include/freetype2 -I../../extras/fontconfig/src -I../../exports/include-Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DFC_DEFAULT_FONTS='' -DHAVE_EXPAT -DXFREE86_FT2 -fPIC fcfreetype.c fcfreetype.c:31:10: #include expects FILENAME or FILENAME fcfreetype.c: In function `FcFreeTypeQuery': fcfreetype.c:542: warning: implicit declaration of function `FT_MODULE_CLASS' fcfreetype.c:542: error: dereferencing pointer to incomplete type fcfreetype.c:542: error: invalid type argument of `-' fcfreetype.c:542: error: dereferencing pointer to incomplete type Could anyone help me? Thanks in advance! Regards, Kevin ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Problems running XFree86 in Microsoft VirtualPC
Ive built a virtual machine (Virtual PC 5.3) with netBSD 2.0.2 and Im having difficulty starting X I have XFree86 version 4.4.0 My video adapter is a 64MB Intel 82845G When I tried startx I get the error X connection to :0.0 broken (explicit kill or server shutdown) When I enter xhost + I get the error: xhost: unable to open display my DISPLAY environment variable was empty so I manually set it to my machine name. I now entered xhost + And get the error; xhost: unable to open display myBSD.murphy.net:0.0 Not sure where to look next is it my Virtual PC environment or have I botched something else? Thanks in advance Kevin Below is my XFree86confg + 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 extmod Load record Load dbe Load glx Load xtrap Load type1 Load speedo EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol wsmouse Option Device /dev/wsmouse EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelName Monitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option noaccel # [bool] #Option swcursor # [bool] #Option slow_dram_refresh # [bool] #Option slow_dram # [bool] #Option slow_edodram # [bool] #Option slow_vram # [bool] Identifier Card0 Driver s3 VendorName S3 Inc. BoardName 86c764/765 [Trio32/64/64V+] BusID PCI:0:8:0 EndSection Section Screen Identifier Screen0 Device Card0 Monitor Monitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection
[XFree86] termcap and shutdown errors
Title: termcap and shutdown errors Greetings All, I recently upgraded my very old XF86 to version 4.5.0 on a Redhat Linux 4.2 box, and while my upgrade went seamlessly and XF86 appears to be operating stable, I now have 2 quirks that I need help with: 1. I now can't invoke command line programs such as PINE and PICO when connected to my Linux box via a telnet session from other PCs,when I try to invoke those programs I get the following error: Incomplete termcap entry 2. When in an xterm window within XF86, I can no longer issue a 'shutdown' command, I get a 'bash: unknown command error' I'm not a Linux Guru by any stretch of the imagination, but learning quickly,...can anyone provide me with some guidance on what might be causing these 2 quirks, and how I might correct them?? Thanks in Advance for any and all help, Kevin Merrill [EMAIL PROTECTED]
[XFree86] Red Hat Linux X (Graphics) Window problem. ( HELP PLEASE )
Dear Sir/Madam; Please help on this problem.I really need your help.Please help.. PROBLEM: Cannot boot up to get the Graphical Interface. No X screen. Even from the text screen cannot startx to get the X screen. Below is the error displayed: Log file: /var/log/Xfree86.0.log Using config file: /etc/X11/XF86config (ww) ATI (0) : Failed to set up write-combing range (0xfc00, 0x40) (ww) ATI (0) : Failed to set up write-combing range (0xfc00, 0x40) Could not init font path element Unix/: 7100, removing from list Fatal server erroe: Could not open default font fixed To get the full server message, check /var/log/Xfree86.0.log X10 : fatal IO error 104 (connection reset by peer) on X server : 0.0 after 0 requests (0 known processed) with 0 events remaining. Your help will be highly appreciated. Yours faithfully Kevin Mas Find local movie times and trailers on Yahoo! Movies.
RE: [XFree86] External Lcd Problems with laptop! Aaaargh!
In my (admittedly limited) experience I've always had problems with modelines. A number of times the configuration program has put a mode line in that did not do the job. However having said that I've always been able to resolve the problem by simply removing any mode lines from the config file. Provided you have the correct horizontal and vertical refresh rates in the monitor section you should not have a problem. So try removing your mode lines from your monitor section and see what happens. All the mode line is doing is supeceding the BIOS or driver settings for the screen resolution you have chosen. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Alex Mavrogonatos [mailto:[EMAIL PROTECTED] Sent: 09 March 2005 11:20 To: xfree86@XFree86.Org Subject: [XFree86] External Lcd Problems with laptop! Aaaargh! Hi, I'm kinda a newbie to linux and trying to permemamtly switch to it from XP. Im using a fujitsu e342 laptop with a trident cyber 9388 graphics adaptor and running mandrake 10 on it. Here's the problem: I'm using this laptop as a desktop replacement meaning with an external monitor, external mouse, external keyboard etc. I was using an external CRT monitor (NEC multisync V521) til it died on me and it was working just fine at 1024x768 (while the laptop's internal screen supports up to 800x600). I replaced the crt with a 17 inch LCD monitor (LG 1720p) and the problems started. When I boot up Linux the external LCD goes blank at all resolutions, but when I boot up using the internal and the external screen simultaneously they both work at 800x600. O figured this is a modeline thing because I had to get a modeline from linux-on-laptops to get the crt working at 1024x768 (until then I had the same problem with the CRT if I recall correctly...) and probably the same modeline is out of range for my LCD screen. So what I did was boot with both screens at 800x600, use xvidtune to get a modeline for that resolution, add it to my XF86Config-4 file and hope I could get at least a 800x600 resolution working on my external LCD only. Weirdly enough this didn't work. Next, with the help from a utility i googled up, I got my hands on windows' parameters and computed modelines with a modeline calculator on the net. Still nothing... In all the above cases I get a signal out of range on the LCD. It seems that X is outputting some kind of signal that the LCD wont recognize. Actually if at that point I enable the internal LCD also, I'm able to get 800x600 on both screens by fiddling with alt+ctrl+plus (at least I'm sure this worked once or twice, actually never tried it again). The LCD screen in windows XP can bring up a nice [EMAIL PROTECTED] with 256 colors but I would be ok with a 1024x768 in linux. What am I doing wrong? Damn Linux, if only I didn't love thee so... I'm sending my relatively old configuration because since then I've been playing alot with my XF86Config-4 file and I'm sure I've added stuff that don't really help! Here's the XF86Config-4 file that worked with my CRT, the only changes I made to this where the horizontal-vertical frequency ranges I got from the LCD's manual and below is X's log file, thanks for your time in advance! # File generated by XFdrake. # ** # Refer to the XF86Config man page for details about the format of # this file. # ** Section Files # Multiple FontPath entries are allowed (they are concatenated together) # By default, Mandrake 6.0 and later now use a font server independent of # the X server to render fonts. FontPath unix/:-1 EndSection Section ServerFlags #DontZap # disable CrtlAltBS (server abort) #DontZoom # disable CrtlAltKP_+/KP_- (resolution switching) AllowMouseOpenFail # allows the server to start up even if the mouse doesn't work EndSection Section Module Load dbe # Double-Buffering Extension Load v4l # Video for Linux Load extmod Load type1 Load freetype Load glx # 3D layer EndSection Section InputDevice Identifier Keyboard1 Driver Keyboard Option XkbModel pc105 Option XkbLayout us,el(extended) Option XkbOptions grp:alt_shift_toggle,grp_led:scroll EndSection Section InputDevice Identifier Mouse1 Driver mouse Option Protocol ExplorerPS/2 Option Device /dev/mouse Option ZAxisMapping 6 7 EndSection Section Monitor Identifier monitor1 VendorName Plug'n Play HorizSync 30-83 VertRefresh 56-75 ModeLine 800x600 50 800 856 976 1040 600 637 643 666 +hsync +vsync ModeLine 1024x768 65.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync EndSection Section Device Identifier device1 VendorName Trident Microsystems BoardName Trident Cyber 9388 (generic) Driver trident VideoRam 2048 Option DPMS EndSection Section Screen
RE: [XFree86] Interactive Whiteboard...
When the Activboard is used on Windows does it act like a mouse or does a dedicated application have to be run to use it. It sounds to me like you will need to write your own driver for this. A good place to start is the Elographics touch screen driver as it will use absolute coordinates like I presume the Activboard does. You will need to delve into the serial protocol between the Activboard and the PC. You may have to nag them for them to give it to you. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Grant Sewell [mailto:[EMAIL PROTECTED] Sent: 20 January 2005 23:35 To: xfree86@XFree86.Org Subject: [XFree86] Interactive Whiteboard... Hi all. I teach at a local college where we have a fair number of interactive whiteboards (touch sensitive, or pen-activated boards onto which the screen is projected). The particular model I am interested in is the Promethean Activboard. I use a laptop running Debian Sid with XFree 4.3.0.1. I have the Graphics side of things setup very nicely thank-you, but I would like to get the interactive pen running as a pointing device so that I can leave the laptop in the corner of the room and not have to revisit it every couple of seconds. The whiteboard connects to the computer via a standard (I presume, RS232) serial port (9pin variety). I have tried every combination of driver/protocol that I could imagine for serial mice, and I have tried using both the laptop's own serial port and a USB-serial adaptor, but nothing has worked so far. Has anyone had any success using these whiteboards with X? I have contacted the manufacturer but they didn't seem particularly interested in my request for assistance (now there's a surprise). Thanks. Grant. -- Artificial intelligence is no match for natural stupidity. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Interactive Whiteboard...
I'm no hacker either. It's just that we use touchscreens on a number of our products so I've played with various drivers with varying degrees of success. A google search on Interactive Whiteboards+Linux revealed that several other White board manufacturers support Linux. http://www.smarttech.com/company/mediacenter/press/releases/linux.asp is an example. Try beating Promethean over the head with this fact. With the ever increasing use on Linux in schools and universities it I would think that they will be getting more and more requests for this. If they think they are going to loose sales by not supporting Linux it might spur them into action. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Grant Sewell [mailto:[EMAIL PROTECTED] Sent: 21 January 2005 08:53 To: xfree86@XFree86.Org Subject: Re: [XFree86] Interactive Whiteboard... On Fri, 21 Jan 2005 08:36:28 - Benstead, Kevin wrote: When the Activboard is used on Windows does it act like a mouse or does a dedicated application have to be run to use it. Nail on the head with the former. It acts as a pointing device... it would potentially be easier if it required their application, but unfortunately it doesn't. It sounds to me like you will need to write your own driver for this. A good place to start is the Elographics touch screen driver as it will use absolute coordinates like I presume the Activboard does. I was hoping you wouldn't say that. I'm no hacker by anyone's standards. But, I'll go get the X sources and have a peek, see what I can make of it. You will need to delve into the serial protocol between the Activboard and the PC. You may have to nag them for them to give it to you. Okey dokey. I'm not expecting miracles on this. Although, it would seem that the company are more proud of their software that let's you annotate over the top of a displayed screen, so perhaps they won't be guarding their serial protocols with high enthusiasm. We'll see. Thanks. Grant. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Troubleshoot
Edit your monitor section as below. Section Monitor Indentifier Monitor0 VendorName Monitor Vendor ModelName Unprobed Monitor HorizSync 30.0-72.0 VertRefresh 45-150 EndSection And your Device section should look like this. Section Device Identifier VideoCard0 Driver Savage VendorName VideoCard vendor BoardName S3 Prosavage KM133 Option UseBIOS False VideoRAM 32764 EndSection Hope this helps. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: John Puri [mailto:[EMAIL PROTECTED] Sent: 19 January 2005 13:44 To: Benstead, Kevin Subject: RE: [XFree86] Troubleshoot Respected The problem is not solved. My RAM is 96 MB in which 32 MB is share memory for graphics. So I write 32764kb. As I read my monitor profile I found that Horizontal range is 30 ~ 72 khz and Vertical is 45 ~ 150 hz. Can I write this in my monitor configuration? Hope to have a favourable reply? Benstead, Kevin [EMAIL PROTECTED] wrote: Your comments are correct there is something wrong with the monitor settings. In this section of your config file Section Monitor Indentifier Monitor0 VendorNmae Monitor Vendor ModelName Unprobed Monitor HorizSync 50.0-61.0 VertRefresh 31.5-31.5 Options dpms EndSection The HorizSync and VertRefresh rates are swapped over. I don't believe your monitor has a HORIZONTAL refresh rate of 50 to 61 KHZ and a Vertical Refresh of 31.5HZ. That's why you get lots of messages like this (II) SAVAGE(0): Not using default mode 640 * 350 (hsync out of range) and (II) SAVAGE(0): Not using default mode 800 * 600 (vrefresh out of range) The label on the back of your monitor should tell you what the refresh rates should be. Secondly I note that your have a Savage chipset. This may explain why you had the problem where your monitor went blank. (Your original problem). Fortunately I've seen this problem my self and the solution is reasonably easy. In the following section. Section Device Identifier VideoCard0 Driver Savage VendorNmae VideoCard vendor BoardName S3 Prosavage KM133 EndSection Add the following lines before the EndSection. Option UseBIOS False VideoRAM 8192 The first line stops XFree from attempting to use settings in the Savage BIOS which has been known to cause problems. The second line tells the Savage Driver how much of your system RAM is allocated to your graphics controller. The value should be the same as the amount of video RAM allocated in your BIOS. Note that your BIOS will probably allocate the memory in MBytes while the VideoRAM setting is in Kbytes. So in my example above I have the video ram in the bios set to 8M therefore my VideoRAM setting in the config file is 8192 (8M x 1024). Hope this helps. Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Troubleshoot
Your comments are correct there is something wrong with the monitor settings. In this section of your config file Section Monitor Indentifier Monitor0 VendorNmae Monitor Vendor ModelName Unprobed Monitor HorizSync 50.0-61.0 VertRefresh 31.5-31.5 Options dpms EndSection The HorizSync and VertRefresh rates are swapped over. I don't believe your monitor has a HORIZONTAL refresh rate of 50 to 61 KHZ and a Vertical Refresh of 31.5HZ. That's why you get lots of messages like this (II) SAVAGE(0): Not using default mode 640 * 350 (hsync out of range) and (II) SAVAGE(0): Not using default mode 800 * 600 (vrefresh out of range) The label on the back of your monitor should tell you what the refresh rates should be. Secondly I note that your have a Savage chipset. This may explain why you had the problem where your monitor went blank. (Your original problem). Fortunately I've seen this problem my self and the solution is reasonably easy. In the following section. Section Device Identifier VideoCard0 Driver Savage VendorNmae VideoCard vendor BoardName S3 Prosavage KM133 EndSection Add the following lines before the EndSection. Option UseBIOS False VideoRAM 8192 The first line stops XFree from attempting to use settings in the Savage BIOS which has been known to cause problems. The second line tells the Savage Driver how much of your system RAM is allocated to your graphics controller. The value should be the same as the amount of video RAM allocated in your BIOS. Note that your BIOS will probably allocate the memory in MBytes while the VideoRAM setting is in Kbytes. So in my example above I have the video ram in the bios set to 8M therefore my VideoRAM setting in the config file is 8192 (8M x 1024). Hope this helps. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: John Puri [mailto:[EMAIL PROTECTED] Sent: 15 January 2005 03:57 To: Benstead, Kevin Subject: RE: [XFree86] Troubleshoot Respected As you requested my /etc/X11/XF86Config # XFree86 4 configuration created by pyxf86Config Section ServerLayout Identifier Default Layout Screen 0 Screen0 0 0 InputDevice Mouse0 CorePointer InputDevice Keyboard0 CoreKeyboard InputDevice DevInputMice AlwaysCore EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb FontPath unix/ :7100 EndSection Section Module Load dbe Load extmod Load fbdevhw Load glx Load record Load freetype Load type1 Load dri EndSection Section InputDevice Indentifier Keyboard0 Driver keyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol IMPS/2 Option Device /dev/psaux Option ZAxisMapping 4 5 Option Emulate3Buttons no EndSection Section InputDevice # If the normal CorePointer mouse is not a USB mouse then # this input device can be used in AlwaysCore mode to let you # also use USB mice at the same time Identifier DevInputMice Driver mouse Option Protocol IMPS/2 Option Device /dev/inpu/mice Option ZAxisMapping 4 5 Option Emulate3Buttons no EndSection Section Monitor Indentifier Monitor0 VendorNmae Monitor Vendor ModelName Unprobed Monitor HorizSync 50.0-61.0 VertRefresh 31.5-31.5 Options dpms EndSection Section Device Identifier VideoCard0 Driver Savage VendorNmae VideoCard vendor BoardName S3 Prosavage KM133 EndSection Section Screen Identifier Screen0 Device VideoCard0 Monitor Monitor0 DefaultDepth 24 SubSection Display Depth 24 Modes 640 * 480 EndSubSection EndSection Section DRI Group 0 Mode 066 EndSection /var/log/XFree86.0.log file After looking the log file I came to guess that my monitor is not been supported. My monitor is PROLINK and model no is : PRO 1570/S. When installing this model number was unlisted and the system by default took Unprobed Monitor. And also by default it take horizsync 50 - 61 vertsync 31.5 How can I know about ranges of monitor? I have written some last message of the file. (II) SAVAGE(0): Monitor0: Using hsync range of 50.00 - 61.0 kHz (II) SAVAGE(0): Monitor0: Using vrefresh value of 31.50 Hz (II) SAVAGE(0): Clock range: 10.00 to 220.00 MHz (II) SAVAGE(0): Not using default mode 640 * 350 (hsync out of range) (II) SAVAGE(0): Not using default mode 320 * 175 (hsync out of range) (II) SAVAGE(0): Not using default mode 640 * 400 (hsync out of range) (II) SAVAGE(0): Not using default mode 320 * 200 (hsync out of range) (II) SAVAGE(0): Not using default mode 720 * 400 (hsync out of range) (II) SAVAGE(0): Not using default mode 360 * 200 (hsync out of range) (II) SAVAGE(0): Not using default mode 640 * 480 (hsync out of range) (II) SAVAGE(0): Not using default mode 320 * 240 (hsync out of range) which continues go on with differernt resolution size
Re: XFree86 4.5.0 release schedule
On Tue, Jan 11, 2005 at 12:41:15PM -0500, David Dawes wrote: On Tue, Jan 11, 2005 at 08:31:54AM -0700, Marc Aurele La France wrote: On Sat, 8 Jan 2005, David Dawes wrote: The schedule for the next XFree86 release -- 4.5.0 is as follows: 26 January 2005feature freeze late February 2005 code freeze early-mid March 2005 release The feature freeze date is the date by which non-bug-fix submissions need to be received in order to be considered for inclusion in the 4.5.0 release. The code freeze date is the point at which only seriaous bug fixes and documentation updates are accepted. Submissions may be made through the XFree86 bugzilla at bugs.xfree86.org or via email to [EMAIL PROTECTED] It is also a good idea to send a note here regarding new submissions or for previous submissions that have not been committed yet. Submissions should be integrated/tested against the most recent XFree86 snapshot or the current CVS trunk, and submitted as patches against such. XFree86 snapshots can be found at http://www.xfree86.org/develsnaps/. The actual code freeze and release dates will be nailed down as they get closer. Should an attempt be made to resurrect DMX before 4.5? How seriously broken is it? Here's an explanation of the issue with a proposed fix to maintain backward compatibility: http://sourceforge.net/mailarchive/message.php?msg_id=10290987 I've tested my patch to make sure that it works fine on Linux. I don't have an SGI box to verify that it still works fine on their systems. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 release schedule
On Tue, Jan 11, 2005 at 02:15:58PM -0700, Marc Aurele La France wrote:
On Tue, 11 Jan 2005, Marc Aurele La France wrote:
On Tue, 11 Jan 2005, Kevin E Martin wrote:
Here's an explanation of the issue with a proposed fix to maintain
backward compatibility:
http://sourceforge.net/mailarchive/message.php?msg_id=10290987
I've tested my patch to make sure that it works fine on Linux. I don't
have an SGI box to verify that it still works fine on their systems.
Well, if I were you, I'd commit something like that ASAP. I can deal with
the build issues, test case or no test case. The point being that no one
will fix it if it doesn't build.
Longer term though, we need to look at glxProxy being more of an #ifdef'ed
derivative of GLX.
Come to think of it, I'll be even blunter. If DMX breaks every time GLX is
resync'ed, then there's no point in keeping DMX.
glxProxy was developed by SGI is almost 100% independent from GLX as
used in the rest of the X server -- the only shared code is from some
header files. One of those headers was changed but not properly
#ifdef'd by SGI to maintain backward compatibility with previous XFree86
releases. The patch that I suggested fixes the backward compatibility
issue. This is all explained in the thread that I referenced in my
previous message.
Unfortunately, I just discovered that there is a much more significant
issue: you've made changes to glxProxy on 4 Aug 2004 that broke the
build. I've attached a patch to make it build again. However, I cannot
verify the correctness of the changes you've made, since glxProxy is not
my code. As I mentioned above, the code was donated by SGI. I would
strongly suggest reverting the changes you've made until you can verify
with SGI that your changes are correct.
If you do revert the changes back to the way they were originally
checked in and then apply the patch from my message to the dri-devel
list (see URL above), then glxProxy should build and work properly, and
it should also be backward compatible with previous XFree86 releases.
Index: programs/Xserver/hw/dmx/dmx_glxvisuals.c
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/dmx/dmx_glxvisuals.c,v
retrieving revision 1.1
diff -u -r1.1 dmx_glxvisuals.c
--- programs/Xserver/hw/dmx/dmx_glxvisuals.c30 Jun 2004 20:21:38 -
1.1
+++ programs/Xserver/hw/dmx/dmx_glxvisuals.c12 Jan 2005 00:13:53 -
@@ -147,12 +147,14 @@
int value = *p++;
switch (property) {
+#if 0
case GLX_SAMPLES_SGIS:
config-multiSampleSize = value;
break;
case GLX_SAMPLE_BUFFERS_SGIS:
config-nMultiSampleBuffers = value;
break;
+#endif
case GLX_TRANSPARENT_TYPE_EXT:
config-transparentPixel = value;
@@ -177,10 +179,12 @@
config-visualRating = value;
break;
+#if 0
/* visualSelectGroup is an internal used property */
case GLX_VISUAL_SELECT_GROUP_SGIX:
config-visualSelectGroup = value;
break;
+#endif
default :
/* Ignore properties we don't recognize */
@@ -591,9 +595,11 @@
cfg-transparentBlue = fbcfg-transparentBlue;
cfg-transparentAlpha = fbcfg-transparentAlpha;
cfg-transparentIndex = fbcfg-transparentIndex;
+#if 0
cfg-multiSampleSize = fbcfg-multiSampleSize;
cfg-nMultiSampleBuffers = fbcfg-nMultiSampleBuffers;
cfg-visualSelectGroup = fbcfg-visualSelectGroup;
+#endif
}
}
Index: programs/Xserver/hw/dmx/glxProxy/g_renderswap.c
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/dmx/glxProxy/g_renderswap.c,v
retrieving revision 1.2
diff -u -r1.2 g_renderswap.c
--- programs/Xserver/hw/dmx/glxProxy/g_renderswap.c 4 Aug 2004 16:33:34
- 1.2
+++ programs/Xserver/hw/dmx/glxProxy/g_renderswap.c 12 Jan 2005 00:13:53
-
@@ -63,6 +63,7 @@
void __glXDispSwap_Color3dv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
#ifdef __GLX_ALIGN64
@@ -76,6 +77,7 @@
void __glXDispSwap_Color3fv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
__GLX_SWAP_FLOAT_ARRAY(pc + 0, 3);
@@ -83,6 +85,7 @@
void __glXDispSwap_Color3iv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
__GLX_SWAP_INT_ARRAY(pc + 0, 3);
@@ -90,6 +93,7 @@
void __glXDispSwap_Color3sv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES;
__GLX_SWAP_SHORT_ARRAY(pc + 0, 3);
@@ -102,6 +106,7 @@
void __glXDispSwap_Color3uiv(GLbyte *pc)
{
+ __GLX_DECLARE_SWAP_VARIABLES;
__GLX_DECLARE_SWAP_ARRAY_VARIABLES
RE: [XFree86] Xfree86 log error
http://xfree86.linuxwiki.org/FAQErrorMessages has a description of what to do to fix this. The basic problem is that RedHat insists on installing X with a font server which at some later date it then stops from running. No one to my knowledge has ever identified why RedHat does this. The FAQ explains how to get your X running without using a Font Server. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Andrew Haninger [mailto:[EMAIL PROTECTED] Sent: 07 January 2005 13:40 To: xfree86@xfree86.org Subject: Re: [XFree86] Xfree86 log error You appear to be having the unable to find font 'fixed' error that shows up oh-so-often. This can be tricky to fix, but I've always found that either enabling xfs or installing font packages helps to resolve the problem. You can usually find a list of daemons by running 'ntsysv' and scrolling down the list to the bottom. If it's not turned on, enable the X Font Server 'xfs' and try again. If that doesn't work, try reinstalling the X font packages that came with Redhat 9. Hope this helps. -Andy ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Need X Window with no mouse.
Try using the void driver Look here for details http://www.xfree86.org/4.2.0/void.4.html I only found this myself a day or so ago. It says it can also be used as a keyboard driver. Be aware that your application will have to cope with out a mouse. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: De Chantal, Dany [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 13:45 To: [EMAIL PROTECTED] Subject: [XFree86] Need X Window with no mouse. Hi, I need to use graphics fonctionnality but only with keyboard. I don't have mouse on my system. Actually i'am able to use Xfree with no mouse but the start time of X console need approximatly 25 to 30 seconde. When i connect mouse , the start time is less than 5 secondes. I use the AllowMouseOpenFail true option. Also, i try to put ttyS0 for mouse device (normally psaux). If you have any suggestion of solution like (remove mouse polling with disabling option) please response me. Thanks a lot, sincerely Dany ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] XFree86.0.log
Level 5 gets you straight into X at startup. Because your X does not work properly (yet) that's why it crashes to console. Startup in console mode (level 3) until you get your X running properly and then look at this link on how to get xdm going so that you can have a graphical logon. http://www.linuxgazette.com/issue43/nielsen.xdm.html Having a 'X' cursor means the Xserver is running. It's just that you don't have a windows manager running. The attached xinitrc file should be placed in tour /etc/X11/xinit/ directory. When you run startx it will now launch the TWM window manager, give you a clock and a terminal window. If you want other windows managers (KDE Gnome etc) try looking on their websites for advice on getting them running. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Zeljko Djuricic [mailto:[EMAIL PROTECTED] Sent: 30 September 2004 08:27 To: [EMAIL PROTECTED] Subject: Re: [XFree86] XFree86.0.log When I try to start machine in GUI mode (level 5), my screen blinks few times and then crashes (then I see prompt). If I try to run X from console I get blank screen with mouse pointer. I also tried redhat-config-xfree86 --reconfig but got: xconf.py: Fatal IO error 2 (Connection rejec by peer) on X server :17.0.. I send you my config file __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail xinitrc Description: Binary data
RE: [XFree86] XFree86.0.log
At this point my knowledge runs out. I've never had to configure a KDE system. I use X on a very small embedded system so don't have the space for KDE. This link http://developer.kde.org/documentation/books/kde-2.0-development/ch01lev1sec 5.html is to the KDE website which tell you how to install KDE. It also gives you the chance to download the latest version (if you want). Best of luck. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Zeljko Djuricic [mailto:[EMAIL PROTECTED] Sent: 30 September 2004 12:29 To: [EMAIL PROTECTED] Subject: RE: [XFree86] XFree86.0.log I reinstalled KDE from CD but nothing happened, so it must be windows manager. What is its package name, i.e. how to reinstall it? Or how to check is it running? thx very much __ Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. http://messenger.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] XFree86.0.log
Callisto My reply was to Zeljko Djuricic who has sent his log file in without an description of the error. Please check that any replies you receive are actually about your problem. The mailing list sends copies of every problem and every reply to everyone on the mailing list. Don't just assume that a reply is an attempt to answer your problem. Anyway YOUR problem is to do with the lack of a font server running on your system. You have two options you can disable the requirement for a font server in your Xf86Config file and use the fonts directories instead OR you can make sure your font server is running before you attempt to start X. This FAQ (which Mark Vojkovich suggested you read earlier today) should tell you what you need to know. http://xfree86.linuxwiki.org/FAQ Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Callisto Mupfunye [mailto:[EMAIL PROTECTED] Sent: 29 September 2004 12:27 To: [EMAIL PROTECTED] Subject: RE: [XFree86] XFree86.0.log My problem is I can't get to F7 screen when I boot up my linux 7.3 server. Regards, Callisto Mupfunye Technical Manager Micromart Zimbabwe Tel: 263-4-744643/587/628/523/530 Fax: 263-4-744653 Mobile: 26391416867 Mobile2: 26391914732 Email 1- [EMAIL PROTECTED] Email 2- [EMAIL PROTECTED] = This e-mail and any attachments hereto may contain information that is confidential and/or proprietory and is intended for the sole use of the addressee(s). If you are not the intended addressee or the person responsible for delivering it to the addressee, notify the sender and delete it immediately. Micromart Zimbabwe accepts no liability whatsoever for loss or damage resulting from the use of the information contained in this message. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Benstead, Kevin Sent: Wednesday, September 29, 2004 1:13 PM To: [EMAIL PROTECTED] Subject: RE: [XFree86] XFree86.0.log And what is your problem? Your log file shows only one warning (about a sync rate setting being higher than the ratings of the monitor) and no errors. I can only assume you sent this log because you thought we might be interested. If you think there is a problem perhaps you would like to enlighten us. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Zeljko Djuricic [mailto:[EMAIL PROTECTED] Sent: 29 September 2004 08:18 To: [EMAIL PROTECTED] Subject: [XFree86] XFree86.0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Sep 28 22:58:34 2004 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8058, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7190 card , rev 03
RE: [XFree86] AllowMouseOpenFail does not work?
Some thoughts. (B (BWe use a system which has a touch screen but no mouse which works OK. (B (BI'm not sure if you want to have a mouse on your system sometimes. (B (BIf you don$B!G(Jt need a mouse at any time just comment out both the line in the (BServerLayout section which references the mouse driver. Than make sure your (Btouch screen is set to "CorePointer" by adding "CorePointer" on the end of (Bthe line which references your touch screen in the ServerLayout section. (B (BYou don$B!G(Jt need to do any thing about the Device sections with the mouse (Bdrivers as the system only loads what is specified in the ServerLayout (Bsection. (B (BIf you need to be able to run with a mouse then the best way is to have two (Bdifferent server layouts and select the one you want when you start X using (Bthe -layout switch. (B (B (BKevin (Bemail: [EMAIL PROTECTED] (BTel: +44 (0)118 971 5032 (B (B-Original Message- (BFrom: David Sun [mailto:[EMAIL PROTECTED] (BSent: 22 September 2004 03:37 (BTo: [EMAIL PROTECTED] (BSubject: Re: [XFree86] "AllowMouseOpenFail" does not work? (B (BHi, Vivek (BOne more question: (Bis it ordinary that the whole system hangs when XFree86 waiting for a (Bconfigure mouse to be present? (Bthanks so much (BDavid $B:_(J 2004-09-21 $BFs(J $BE*(J 18:32$B!$(J Vivek Dasmohapatra $B
[XFree86] Losing resources on Geode processor.
We are using XFree 4.4.0 on a system with a 300MHz Geode GX1 processor and the CS5530A companion chip. We have written a small application using Borland's Kylix which draws five bar charts which are updated every second. The program runs fine BUT its using 70% of CPU time to keep the display updated. (The numbers fed to the charts are generated by the program, there is no external factor influencing the generation of these numbers). If we run the same program (re-compiled) on the same hardware running Micro$oft Windoze 98 the program uses about 10% CPU time. The LINUX version of the program running on a 400MHz EDEN processor with a Savage graphics chip takes less than 1% of CPU time. Is it just that the geode driver is not very good or is there some other problem. If windoze drivers can draw the charts quick enough why cant the xfree drivers do the same thing. Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] M inX, MaxX, MinY, MaxY Problem
The format of the data is as follows: SXXYY Where S is the status XX is the X coordinate and YY is the Y coordinate. Bits are as follows: Byte 1: Status Bits 0 to 5 Not used (Reserved:- No information) Bit 6: 1 for screen being touched. 0 for lift off. Bit 7 Always 1 Byte 2: X coordinate least significant Byte. Bit 0 to 6 Least significant 7 bits of touch coordinate Bit 7: always 0 Byte 3: X coordinate most significant Byte. Bit 0 to 6 Most significant 7 bits of touch coordinate Bit 7: always 0 Byte 4: Y coordinate least significant Byte. Bit 0 to 6 Least significant 7 bits of touch coordinate Bit 7: always 0 Byte 5: Y coordinate most significant Byte. Bit 0 to 6 Most significant 7 bits of touch coordinate Bit 7: always 0 This obvioulsy makes it easier for touch driver writers to latch onto the beginning of a packet as the most significant bit of a byte is only ever a 1 for the status byte of the packet. It does mean that the driver has to do some bit shuffling to get the full 14 bit coordinate but thats not too difficult to do. So if you ignore the first two bytes in your file (they might be down to the touch controller starting up) the first packet of data is as follows. D8 Touch present (bit 6 high) 02 02 X Coordinate = 0102Hex (258 decimal) 23 7E Y Cordinate = 3F23Hex (16163 decimal) The status value D8 changes to 98 when you lift your finger off of the screen. After many years of using touchscreens I've always found it easier to look at the lift off coordinates than the coordinates when the finger is touching the screen. So for your calibration values I suggest you touch down close to each position, slide your finger to the required place and then remove your finger. That way you get a 'lift off packet with the coordinates when you removed your finger. You can then scan the HEX file for the 98 to mark the beginning of the packet and work out the coordinates from there. Note that occasionally (and I don't know why) your file has an extra byte in a packet. If a packet is badly formed (i.e has 6 bytes instead of 5) its wise to ignore it. If you download the EX11-1000SC controller technical reference from the 3M website at http://www.3m.com/3MTouchSystems/downloads/PDFs/19252V21.pdf this information is on page 24. Hope this helps. Kevin -Original Message- From: Dalibor Malek [mailto:[EMAIL PROTECTED] Sent: 31 August 2004 19:03 To: [EMAIL PROTECTED] Subject: Re: [XFree86] M inX, MaxX, MinY, MaxY Problem Hi Kevin, thank you for your answer. I tried as you said and connected my screen on the serial of my Laptop and then run HyperTerminal to connect to the screen. Baud rate and so on are right. Then I touched the screen as you described and this is what I get: www.zwickl.net/capture.TXT Viewed wit a Hex editor it makes even les sense. What should I look for in there? Thank you Dalibor Malek Benstead, Kevin wrote: Those drivers won't work with your controller. We had exactly this problem with a Elographics touch screen (I think both the drivers are written by the same person or based on one previously written). The way that Elographics recommended was to boot into DOS, run their DOS calibration utility, write down the numbers and then put them into the XF86Config file. However as we were running on an embedded system this was not possible. So we piped the data from the serial port on which the touch screen was connected into a file (once we got the baud rate correct). We touched the screen in nine places. Top left, Middle left, Bottom left, Top Centre, Mid Centre, Bottom centre, Top Right, Mid Right and bottom right. For each touch position there should be at least one and probably several packets of data from the touch controller. Using a Hex editor we viewed the data and worked out the values of MinX, MinY, MaxX, MaxY we fed those into the XF86Config file. Provided you know the order that you touched each of the points on the screen it's usually pretty easy to work it out. The results were pretty good. The manual for the microtouch controller SHOULD give you a run down on the serial protocol so you can work out how to find the X and Y co-ordinates for each touch. If only there were a calibration routine as part of X. Perhaps one day someone will write one. I'm not volunteering I've got enough to do. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Dalibor Malek [mailto:[EMAIL PROTECTED] Sent: 31 August 2004 14:50 To: [EMAIL PROTECTED] Subject: Re: [XFree86] M inX, MaxX, MinY, MaxY Problem Hi Kevin, thank you for your answer. I know the site and I tried the drivers but they are not working for me. I'm using a EX1000SC Controller(OK not me the screen). There are Linux drivers for this screen but only for the 2.4.* Kernel (not working with Fedora Core 2 and the 2.6.* Kernel). That's way I'm trying to get the standard microtouch
RE: [XFree86] M inX, MaxX, MinY, MaxY Problem
If you are using a 3M SC3 or SC4 touch controller you don't really want to be using the microtouch driver. There is a much better driver at http://www.cdp1802.org/mmmtouch/ which has a calibration routine that does all the work for you. The version for Xfree4.3.0 works for 4.4.0 as well. Kevin -Original Message- From: Dalibor Malek [mailto:[EMAIL PROTECTED] Sent: 30 August 2004 13:22 To: [EMAIL PROTECTED] Subject: [XFree86] M inX, MaxX, MinY, MaxY Problem Hi All, I'm trying to configure a 3M Touch screen. As I found out I have to use the Microtouch driver so a added the following to my config File: Section InputDevice Identifier touchscreen0 Driver microtouch Option Device /dev/ttyS0 Option MinX 1412 Option MaxX 15184 Option MinY 15372 Option MaxY 1230 Option ScreenNumber 0 Option ReportingMode Scaled Option ButtonNumber 1 Option SendCoreEvents EndSection This got my Touch screen running but when I touch the screen the mouse pointer is two or three centimetres right beside my finger. I found out that the MinX, MaxX, MinY, MaxY settings don't fit for my screen but how can I get the right settings? When I set the MinX and MinY settings to 0 I get better result but I think there is a way to calculate or find the right settings out except guessing. Thank You Dalibor Malek ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] M inX, MaxX, MinY, MaxY Problem
Those drivers won't work with your controller. We had exactly this problem with a Elographics touch screen (I think both the drivers are written by the same person or based on one previously written). The way that Elographics recommended was to boot into DOS, run their DOS calibration utility, write down the numbers and then put them into the XF86Config file. However as we were running on an embedded system this was not possible. So we piped the data from the serial port on which the touch screen was connected into a file (once we got the baud rate correct). We touched the screen in nine places. Top left, Middle left, Bottom left, Top Centre, Mid Centre, Bottom centre, Top Right, Mid Right and bottom right. For each touch position there should be at least one and probably several packets of data from the touch controller. Using a Hex editor we viewed the data and worked out the values of MinX, MinY, MaxX, MaxY we fed those into the XF86Config file. Provided you know the order that you touched each of the points on the screen it's usually pretty easy to work it out. The results were pretty good. The manual for the microtouch controller SHOULD give you a run down on the serial protocol so you can work out how to find the X and Y co-ordinates for each touch. If only there were a calibration routine as part of X. Perhaps one day someone will write one. I'm not volunteering I've got enough to do. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Dalibor Malek [mailto:[EMAIL PROTECTED] Sent: 31 August 2004 14:50 To: [EMAIL PROTECTED] Subject: Re: [XFree86] M inX, MaxX, MinY, MaxY Problem Hi Kevin, thank you for your answer. I know the site and I tried the drivers but they are not working for me. I'm using a EX1000SC Controller(OK not me the screen). There are Linux drivers for this screen but only for the 2.4.* Kernel (not working with Fedora Core 2 and the 2.6.* Kernel). That's way I'm trying to get the standard microtouch driver to work. I think if I could give him the correct MinX, MaxX, MinY, MaxY settings the screen would work. Do you know how I can get the right settings? Thank you Dalibor Malek Benstead, Kevin wrote: If you are using a 3M SC3 or SC4 touch controller you don't really want to be using the microtouch driver. There is a much better driver at http://www.cdp1802.org/mmmtouch/ which has a calibration routine that does all the work for you. The version for Xfree4.3.0 works for 4.4.0 as well. Kevin -Original Message- From: Dalibor Malek [mailto:[EMAIL PROTECTED] Sent: 30 August 2004 13:22 To: [EMAIL PROTECTED] Subject: [XFree86] M inX, MaxX, MinY, MaxY Problem Hi All, I'm trying to configure a 3M Touch screen. As I found out I have to use the Microtouch driver so a added the following to my config File: Section InputDevice Identifier touchscreen0 Driver microtouch Option Device /dev/ttyS0 Option MinX 1412 Option MaxX 15184 Option MinY 15372 Option MaxY 1230 Option ScreenNumber 0 Option ReportingMode Scaled Option ButtonNumber 1 Option SendCoreEvents EndSection This got my Touch screen running but when I touch the screen the mouse pointer is two or three centimetres right beside my finger. I found out that the MinX, MaxX, MinY, MaxY settings don't fit for my screen but how can I get the right settings? When I set the MinX and MinY settings to 0 I get better result but I think there is a way to calculate or find the right settings out except guessing. Thank You Dalibor Malek ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] XFree Log
Your log file indicates you can't set colour depth of 16 so try setting colour depth to 8. In your config file look for the Screen0 section and change the default depth to 8. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 25 August 2004 11:47 To: [EMAIL PROTECTED] Subject: [XFree86] XFree Log Hello, I have a ALPHA 64 Bit machine at home running RedHat 7.2 Seawolf addition. I have been unable to get X to work on its current configuration. When I try to use the Xconfigurator command it detects a ATIMach64 graphics card and does not give me any other option to choose. Is there a standard configuration for a generic VGA card? If you could send me a generic XFree86 configuration file that would work for any standard vga, maybe that would work? Any help you can provide will be much appreciated. If you need more info please reply. The log file data can be found below. My config: Manufacturer: DEC Alpha Processor: 600MHz RAM:256MB Card: ATI Mach64 (4MB?) OS: RedHat 7.2 Seawolf XFree: 4.0.3 Regards, Brooks Canavesi 412-859-2467 [EMAIL PROTECTED] FedEx Ground - IT MY LOG DATA (/var/log/XFree86.9.log): XFree86 Version 4.0.3 (Red Hat Linux release: 4.0.3-21) / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 16 March 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Compiled with Operating System: Linux 2.4.2-2smp alpha [ELF] Module Loader present (==) Log file: /var/log/XFree86.9.log, Time: Tue Aug 24 04:21:25 2004 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Dell P990 (**) | |--Device ATI Mach64 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbLayout us (**) XKB: layout: us (++) FontPath set to /usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/misc,/usr/share/fon ts/ISO8859-2/75dpi,/usr/share/fonts/ISO8859-2/misc,/usr/share/fonts/ISO8859- 7/75dpi,/usr/share/fonts/ISO8859-7/misc,/usr/share/fonts/ISO8859-9/75dpi,/us r/share/fonts/ISO8859-9/misc,/usr/X11R6/lib/X11/fonts/cyrillic (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.0.3, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.0.3, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:05:0: chip 1002,4758 card , rev 01 class 03,00,00 hdr 00 (II) PCI: 00:06:0: chip 11ad,0002 card 2646,f002 rev 20 class 02,00,00 hdr 00 (II) PCI: 00:08:0: chip 8086,0484 card , rev 43 class 00,00,00 hdr 00 (II) PCI: 00:0b:0: chip 1095,0646 card , rev 01 class 01,01,80 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.0.3, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) PCI-to-ISA bridge: (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:8:0), (0,-1,0), BCTRL: 0x00 (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 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus 0 I/O range: [0] -10x - 0x (0x0) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -10x0001 - 0x (0x) MX[B] (II) Bus 0 prefetchable memory range: [0] -10x0001 - 0x (0x) MX[B] (--) PCI:*(0:5:0) ATI Mach64 GX rev 1, Mem @ 0x0900/23 (II) Addressable bus resource ranges are [0] -10x - 0x (0x0) MX[B] [1] -1
Re: [XFree86] Cannot open log file /var/log/XFree86.0.log
Bruno Mathieu wrote: Is your partition clean ? (Once my host rebooted when I tried to edit /etc/fstab because my reiserfs partition wasn't clean) I'm guessing that for some reason there is a directory in /var/log called XFree86.0.log and than when you cd to /var/log and do an ls -al XFree86.0.log you get returned something like: total 4 drwxr-xr-x2 root root 48 2004-08-19 09:20 . drwxrwxrwt 58 root root 4288 2004-08-19 09:20 .. Is this the case? If so, rm the directory and then try your startx. Kevin Martin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: hw/dmx/glxProxy
On Fri, Aug 06, 2004 at 07:57:04AM -0600, Marc Aurele La France wrote: Hi. DMX introduced a fair amount of source code duplication. In particular, its GLX proxy seems to be based on older snapshots of GLX friends. Now, I've already addressed some of the simplest aspects of this. But, at this point, I would like some opinions as to whether I've grokked this correctly, or whether it is worthwhile to proceed with preventing further skews and dealing with those that are already there. Proceeding with this would entail some co-ordination between the various CVS repositories involved. Hence my query. Any comments? The GLXproxy code was written by SGI and donated to the DMX project. I would suggest coordinating with Guy Zadickario guy-at-sgi-dot-com as he was the main author/contact of this code. Also, if there are changes that you make, please submit patches to the dmx-devel list so that they can be incorporated into the other source repositories and thus minimize version skew. Thanks! ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
compiling issues for kde3.2.3 with XFree 4.4.99.10
I'm having problems getting kde3.2.3 compiled under xfree864.4.99.10. When it's trying to compile kdebase/kdm/backend I receive the following error: xmdauth.o(.text+0x2ba): In function 'XdmGetXdmcpAuth': :undefined reference to 'XdmcpWrap' xmdauth.o(.text+0x6b1): In function 'XdmCheckAuthentication': :undefined reference to 'XdmcpUnwrap' xmdauth.o(.text+0x6fc): In function 'XdmCheckAuthentication':: :undefined reference to 'XdmcpWrap' collect2: ld returned 1 exit status I've asked about this on the kde bugs list with little luck in determining what may be the problem ( I get things like "look for a stale imake", "imake config(HasXdmAuth) didn't match the actually built libraries", etc.Is XFree86 built withor without xdmcp support natively? I sent this (attached file) toan idividual on the kde list and he said that it appears to be an imake issue or somesuch. This wasoutput from a script that he wrote to check the support of xdmcp in X and an nm of/usr/X11R6/lib/libXdmcp.a. Any help is greatly appreciated. Thanks. kevin Martinimake -DUseInstalled -I/usr/X11R6/lib/X11/config Makefile: FRAGILE_DEFINES = -DFRAGILE_DEV_MEM RANDOM_DEFINES = predefined VERSION_DEFINES = -DOSMAJORVERSION=2 -DOSMINORVERSION=4 A_RANDOM_DEFINE = -DRANDOM_DEFINE=\doublequoted\ \ aftertwospaces\ \ aftertwotabs\ \'singlequotes\'\ XDM_CFLAGS = $(BASIC_FLAGS) $(VERSION_DEFINES) $(SIGNAL_DEFINES) $(XDMAUTH_DEFINES) $(FRAGILE_DEFINES) $(SOCK_DEFINES) $(RANDOM_DEFINES) $(CRYPT_DEFINES) $(A_RANDOM_DEFINE) acimake: @set crap $(XDM_CFLAGS); shift; for i in $$@; do echo \$$i: $$i; done; se=s,\\([ \`\']\\),\\1,g; for i in $$@; do echo $$i | sed $$se; done | tr '\n' ' ' | sed s, \$$,,;$$se;s,^,XDM_CFLAGS=,; echo @echo HASXDMAUTH=1 @echo XBINDIR=$(BINDIR) # -- # common rules for all Makefiles - do not edit .c.i: make: $i: -Dlinux $i: -D__i386__ $i: -D_POSIX_C_SOURCE=199309L $i: -D_POSIX_SOURCE $i: -D_XOPEN_SOURCE $i: -D_BSD_SOURCE $i: -D_SVID_SOURCE $i: -DUNIXCONN $i: -DTCPCONN $i: -DOSMAJORVERSION=2 $i: -DOSMINORVERSION=4 $i: -DHASXDMAUTH $i: -DFRAGILE_DEV_MEM $i: predefined $i: -DRANDOM_DEFINE=doublequoted aftertwospaces aftertwotabs 'singlequotes' XDM_CFLAGS=-Dlinux\ -D__i386__\ -D_POSIX_C_SOURCE=199309L\ -D_POSIX_SOURCE\ -D_XOPEN_SOURCE\ -D_BSD_SOURCE\ -D_SVID_SOURCE\ -DUNIXCONN\ -DTCPCONN\ -DOSMAJORVERSION=2\ -DOSMINORVERSION=4\ -DHASXDMAUTH\ -DFRAGILE_DEV_MEM\ predefined\ -DRANDOM_DEFINE=\\\doublequoted\\\ \\\ aftertwospaces\\\ \\\ aftertwotabs\\\ \\\'singlequotes\\\'\\\ HASXDMAUTH=1 XBINDIR=/usr/X11R6/bin result1: |XDM_CFLAGS=-Dlinux\ -D__i386__\ -D_POSIX_C_SOURCE=199309L\ -D_POSIX_SOURCE\ -D_XOPEN_SOURCE\ -D_BSD_SOURCE\ -D_SVID_SOURCE\ -DUNIXCONN\ -DTCPCONN\ -DOSMAJORVERSION=2\ -DOSMINORVERSION=4\ -DHASXDMAUTH\ -DFRAGILE_DEV_MEM\ predefined\ -DRANDOM_DEFINE=\\\doublequoted\\\ \\\ aftertwospaces\\\ \\\ aftertwotabs\\\ \\\'singlequotes\\\'\\\ HASXDMAUTH=1 XBINDIR=/usr/X11R6/bin| result2: |XDM_CFLAGS=-Dlinux\ -D__i386__\ -D_POSIX_C_SOURCE=199309L\ -D_POSIX_SOURCE\ -D_XOPEN_SOURCE\ -D_BSD_SOURCE\ -D_SVID_SOURCE\ -DUNIXCONN\ -DTCPCONN\ -DOSMAJORVERSION=2\ -DOSMINORVERSION=4\ -DHASXDMAUTH\ -DFRAGILE_DEV_MEM\ predefined\ -DRANDOM_DEFINE=\\\doublequoted\\\ \\\ aftertwospaces\\\ \\\ aftertwotabs\\\ \\\'singlequotes\\\'\\\ HASXDMAUTH=1 XBINDIR=/usr/X11R6/bin | result3: XDM_CFLAGS=-Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -DUNIXCONN -DTCPCONN -DOSMAJORVERSION=2 -DOSMINORVERSION=4 -DHASXDMAUTH -DFRAGILE_DEV_MEM predefined -DRANDOM_DEFINE=\doublequoted\ \ aftertwospaces\ \ aftertwotabs\ \'singlequotes\'\ A8Eq.o: T XdmcpARRAY8Equal AA8.o: U Xalloc T XdmcpAllocARRAY8 AA16.o: U Xalloc T XdmcpAllocARRAY16 AA32.o: U Xalloc T XdmcpAllocARRAY32 AofA8.o: U Xalloc T XdmcpAllocARRAYofARRAY8 CA8.o: U Xalloc T XdmcpCopyARRAY8 U memmove DA8.o: T XdmcpDisposeARRAY8 U Xfree DA16.o: T XdmcpDisposeARRAY16 U Xfree DA32.o: T XdmcpDisposeARRAY32 U Xfree DAofA8.o: U XdmcpDisposeARRAY8 T XdmcpDisposeARRAYofARRAY8 U Xfree Fill.o: U Xalloc T XdmcpFill U Xfree U recvfrom Flush.o: T XdmcpFlush U sendto RA8.o: U Xalloc T XdmcpReadARRAY8 U XdmcpReadCARD16 U XdmcpReadCARD8 U Xfree RA16.o: U Xalloc T XdmcpReadARRAY16 U XdmcpReadCARD16 U XdmcpReadCARD8 U Xfree RA32.o: U Xalloc T XdmcpReadARRAY32 U XdmcpReadCARD32 U XdmcpReadCARD8 U Xfree RAofA8.o: U Xalloc U XdmcpDisposeARRA
Re: compiling issues for kde3.2.3 with XFree 4.4.99.10
Never mind, I found Xlib's and Xincludes in /usr/local that appears to have been messing up the compile. ARGH Thanks. KevinKevin Martin [EMAIL PROTECTED] wrote: I'm having problems getting kde3.2.3 compiled under xfree864.4.99.10. When it's trying to compile kdebase/kdm/backend I receive the following error: xmdauth.o(.text+0x2ba): In function 'XdmGetXdmcpAuth': :undefined reference to 'XdmcpWrap' xmdauth.o(.text+0x6b1): In function 'XdmCheckAuthentication': :undefined reference to 'XdmcpUnwrap' xmdauth.o(.text+0x6fc): In function 'XdmCheckAuthentication':: :undefined reference to 'XdmcpWrap' collect2: ld returned 1 exit status I've asked about this on the kde bugs list with little luck in determining what may be the problem ( I get things like "look for a stale imake", "imake config(HasXdmAuth) didn't match the actually built libraries", etc.Is XFree86 built withor without xdmcp support natively? I sent this (attached file) toan idividual on the kde list and he said that it appears to be an imake issue or somesuch. This wasoutput from a script that he wrote to check the support of xdmcp in X and an nm of/usr/X11R6/lib/libXdmcp.a. Any help is greatly appreciated. Thanks. kevin Martinimake -DUseInstalled -I/usr/X11R6/lib/X11/configMakefile:FRAGILE_DEFINES = -DFRAGILE_DEV_MEMRANDOM_DEFINES = predefinedVERSION_DEFINES = -DOSMAJORVERSION=2 -DOSMINORVERSION=4A_RANDOM_DEFINE = -DRANDOM_DEFINE=\"doublequoted\ \ aftertwospaces\ \ aftertwotabs\ \'singlequotes\'\"XDM_CFLAGS = $(BASIC_FLAGS) $(VERSION_DEFINES) $(SIGNAL_DEFINES) $(XDMAUTH_DEFINES) $(FRAGILE_DEFINES) $(SOCK_DEFINES) $(RANDOM_DEFINES) $(CRYPT_DEFINES) $(A_RANDOM_DEFINE)acimake:@set crap $(XDM_CFLAGS); shift; for i in "$$@"; do echo "\$$i: $$i"; done; se="s,\\([ \`\"']\\),\\1,g"; for i in "$$@"; do echo "$$i" | sed "$$se"; done | tr '\n' ' ' | sed "s, \$$,,;$$se;s,^,XDM_CFLAGS=,"; echo@echo HASXDMAUTH=1@echo XBINDIR=$(BINDIR)# --# common rules for all Makefiles - do not edit.c.i:ma ke: $i: -Dlinux$i: -D__i386__$i: -D_POSIX_C_SOURCE=199309L$i: -D_POSIX_SOURCE$i: -D_XOPEN_SOURCE$i: -D_BSD_SOURCE$i: -D_SVID_SOURCE$i: -DUNIXCONN$i: -DTCPCONN$i: -DOSMAJORVERSION=2$i: -DOSMINORVERSION=4$i: -DHASXDMAUTH$i: -DFRAGILE_DEV_MEM$i: predefined$i: -DRANDOM_DEFINE="doublequoted aftertwospaces aftertwotabs 'singlequotes'"XDM_CFLAGS=-Dlinux\ -D__i386__\ -D_POSIX_C_SOURCE=199309L\ -D_POSIX_SOURCE\ -D_XOPEN_SOURCE\ -D_BSD_SOURCE\ -D_SVID_SOURCE\ -DUNIXCONN\ -DTCPCONN\ -DOSMAJORVERSION=2\ -DOSMINORVERSION=4\ -DHASXDMAUTH\ -DFRAGILE_DEV_MEM\ predefined\ -DRANDOM_DEFINE=\\\"doublequoted\\\ \\\ aftertwospaces\\\ \\\ aftertwotabs\\\ \\\'singlequotes\\\'\\\"HASXDMAUTH=1XBINDIR=/usr/X11R6/binresult1:|XDM_CFLAGS=-Dlinux\ -D__i386__\ -D_POSIX_C_SOURCE=199309L\ -D_POSIX_SOURCE\ -D_XOPEN_SOURCE\ -D_BSD_SOURCE\ -D_SVID_SOURCE\ -DUNIXCONN\ -DTCPCONN\ -DOSMAJORVERSION=2\ -DOSMINORVERSION=4\ -DHASXDMAUTH\ -DFRAGILE_DEV_MEM\ predefined\ -DRANDOM_DEFINE=\\\"doublequoted\\\ \\\ aftertwospaces\\\ \\\ aftertwotabs\\\ \\\'singlequotes\\\'\\\"HASXDMAUTH=1XBINDIR=/usr/X11R6/bin|result2:|XDM_CFLAGS=-Dlinux\ -D__i386__\ -D_POSIX_C_SOURCE=199309L\ -D_POSIX_SOURCE\ -D_XOPEN_SOURCE\ -D_BSD_SOURCE\ -D_SVID_SOURCE\ -DUNIXCONN\ -DTCPCONN\ -DOSMAJORVERSION=2\ -DOSMINORVERSION=4\ -DHASXDMAUTH\ -DFRAGILE_DEV_MEM\ predefined\ -DRANDOM_DEFINE=\\\"doublequoted\\\ \\\ aftertwospaces\\\ \\\ aftertwotabs\\\ \\\'singlequotes\\\'\\\" HASXDMAUTH=1 XBINDIR=/usr/X11R6/bin |result3:XDM_CFLAGS=-Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -DUNIXCONN -DTCPCONN -DOSMAJORVERSION=2 -DOSMINORVERSION=4 -DHASXDMAUTH -DFRAGILE_DEV_MEM predefined -DRANDOM_DEFINE=\"doublequoted\ \ aftertwospaces\ \ aftertwotabs\ \'singlequotes\'\"A8Eq.o: T XdmcpARRAY8EqualAA8.o:U Xalloc T XdmcpAllocARRAY8AA16.o:U Xalloc T XdmcpAllocARRAY16AA32.o:U Xalloc T XdmcpAllocARRAY32AofA8.o:U Xalloc T XdmcpAllocARRAYofARRAY8CA8.o:U Xalloc T XdmcpCopyARRAY8U memmoveDA8.o: T XdmcpDisposeARRAY8U XfreeDA16.o: T XdmcpDisposeARRAY16U XfreeDA32.o: T XdmcpDisposeARRAY32U XfreeDAofA8.o:U XdmcpDisposeARRAY8 T XdmcpDisposeARRAYofARRAY8U XfreeFill.o:U Xalloc T XdmcpFillU XfreeU recvfromFlush.o: T XdmcpFlushU sendtoRA8.o:U Xalloc T XdmcpReadARRAY8U XdmcpReadCARD16U XdmcpReadCARD8U XfreeRA16.o:U Xalloc T XdmcpReadARRAY16U XdmcpReadCARD16U XdmcpReadCARD8U XfreeRA32.o:U Xalloc T XdmcpReadARRAY32U XdmcpReadCARD32U XdmcpReadCARD8U XfreeRAofA8.o:U XallocU XdmcpDisposeARRAYofARRAY8U XdmcpReadARRAY8 T XdmcpReadARRAYofARRAY8U XdmcpReadCARD8RC8.o: T XdmcpReadCARD8RC16.o: T XdmcpReadCARD16U XdmcpReadC
RE: [XFree86] Mice with absolute-coordinates?
It's likely that you will need to write your own pointer driver Most touch screens give co-ordinates in absolute terms. Is that what you are using? A good place to start would be the drivers for the Elographics or Microtouch touch screens which are bundled in with the latest XFree distribution. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Alexander Gordeyev [mailto:[EMAIL PROTECTED] Sent: 27 July 2004 12:56 To: [EMAIL PROTECTED] Subject: [XFree86] Mice with absolute-coordinates? Hello! In accordance with mouse sources, all mice protocols post their coordnates as relative axis. We have the proprietary device (a la mouse) that can post only absolute coordinates (but not the cad, since the hotspot pointer is permanent and exact mouse buttons are exist). What we want is to avoid introducing yet another protocol the input driver. Does XFree86 already support some device/protocol, that matches our needs? With best regards, Alexander Gordeyev. E-mail: [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/07/17 13:41:00 Log message: Revert change to MAXFORMATS to maintain binary compatibility Modified files: xc/programs/Xserver/include/: misc.h Revision ChangesPath 3.31 +2 -2 xc/programs/Xserver/include/misc.h ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: DMX has broken binary compatibility
On Sat, Jul 17, 2004 at 12:59:04PM -0700, Mark Vojkovich wrote: DMX unconditionally changed MAXFORMATS in misc.h which modified the ScreenRec and broke binary compatiblity. This can be very easily changed back, which I have now done. In the future, if you find other areas where the code has caused ABI problems, please let me know and I will fix the problems. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] radeon IGP 345M DRI help
If you want to use the later driver than you will need to update to Xfree4.4.0 Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Carlos Figueiredo [mailto:[EMAIL PROTECTED] Sent: 12 July 2004 17:15 To: [EMAIL PROTECTED] Subject: Re: [XFree86] radeon IGP 345M DRI help In this moment i'm using an older version of the radeon driver and i can start X with it, but i still have no 3d acceleration and thats my main problem at the moment!! If someone as a radeon IGP 345M accelerated please tell me something Benstead, Kevin wrote: The messages here:- (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Module radeon: vendor=The XFree86 Project compiled for 4.3.99.12, module version = 4.0.1 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.7 (EE) module ABI minor version (7) is newer than the server's version (6) indicate that your Radeon driver is NEWER than the version of X you are running. This one is for version 4.4.0 and you are running 4.3.0 You have two options. 1. upgrade to XFree 4.4.0 2. get an older version of the Radeon driver. The second is probably simpler. Just go to the XFree website (www.xfree.org) follow links to get a PREVIOUS release. Select version 4.3.0 select the relevant version for your operating system and GLIBC version. Download the Xmod.tgz file. Unzip it into a directory where you know where it is. Navigate down to the modules/drivers directory and then copy the radeon_drv.o file from there to /usr/X11R6/lib/modules/drivers/ directory. Then you should be able to start X. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Carlos Figueiredo [mailto:[EMAIL PROTECTED] Sent: 11 July 2004 17:49 To: [EMAIL PROTECTED] Subject: [XFree86] radeon IGP 345M DRI help Hi, i'm trying to accelerate my Ati AGI 345M in Xfree86 whith the dri snapshots and the radeon driver that's on de dir snapshots page, and i get this error. A friend solve this problem with apt-get dist-upgrade and got dri working, i didn't! Can anyone help me with some how-to or something? I have a compaq 2516ea with GNU/Debian. this is my Xfree log (sorry, it's big): 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.3.0.1 (Debian 4.3.0.dfsg.1-5 20040616053659 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.23 i686 [ELF] Build Date: 16 June 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.5 ([EMAIL PROTECTED]) (gcc version 3.3.3 (Debian 20040417)) #4 Wed May 19 19:14:22 WEST 2004 T 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: Mon Jul 5 16:52:57 2004 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device ATI Radeon (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout pt (**) XKB: layout: pt (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/u s r/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/us r /X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/ X 11/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 device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config
RE: [XFree86] startx error
First check that the file you are told to remove is actually there. Note that files with a '.' at the beginning are like dos/windows hidden files and you won't see then with just an 'ls' command. Change to the /tmp directory (cd /tmp) Type ls -a to see all of the files in the current directory. If the file that X says you need to delete is there then delete it. Type rm .X0. X creates this file so that it knows that it is running and deletes it when it exits. This prevents two copies of X running on the same system. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 July 2004 16:27 To: [EMAIL PROTECTED] Subject: [XFree86] startx error Could someone help with a startx error Server not found, remove tmp/.XO... I am using redhat 9, vesa driver and am trying to change my monitor configuration. The monitor shows only half screen. When I go into redhat-config-xfree86 change the monitor dimensions and up the resolution to 1024 x 768, the instructions are to restart and start x server (startx). But when I restart, and type startx, I get the above error message. Is there a solution to this? Is there another way to start the server aside from startx? Thanks for any help, I have been working on this for a while. Please give the details, I am new to linux. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] radeon IGP 345M DRI help
The messages here:- (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Module radeon: vendor=The XFree86 Project compiled for 4.3.99.12, module version = 4.0.1 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.7 (EE) module ABI minor version (7) is newer than the server's version (6) indicate that your Radeon driver is NEWER than the version of X you are running. This one is for version 4.4.0 and you are running 4.3.0 You have two options. 1. upgrade to XFree 4.4.0 2. get an older version of the Radeon driver. The second is probably simpler. Just go to the XFree website (www.xfree.org) follow links to get a PREVIOUS release. Select version 4.3.0 select the relevant version for your operating system and GLIBC version. Download the Xmod.tgz file. Unzip it into a directory where you know where it is. Navigate down to the modules/drivers directory and then copy the radeon_drv.o file from there to /usr/X11R6/lib/modules/drivers/ directory. Then you should be able to start X. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Carlos Figueiredo [mailto:[EMAIL PROTECTED] Sent: 11 July 2004 17:49 To: [EMAIL PROTECTED] Subject: [XFree86] radeon IGP 345M DRI help Hi, i'm trying to accelerate my Ati AGI 345M in Xfree86 whith the dri snapshots and the radeon driver that's on de dir snapshots page, and i get this error. A friend solve this problem with apt-get dist-upgrade and got dri working, i didn't! Can anyone help me with some how-to or something? I have a compaq 2516ea with GNU/Debian. this is my Xfree log (sorry, it's big): 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.3.0.1 (Debian 4.3.0.dfsg.1-5 20040616053659 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.23 i686 [ELF] Build Date: 16 June 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.5 ([EMAIL PROTECTED]) (gcc version 3.3.3 (Debian 20040417)) #4 Wed May 19 19:14:22 WEST 2004 T 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: Mon Jul 5 16:52:57 2004 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device ATI Radeon (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout pt (**) XKB: layout: pt (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/us r/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr /X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X 11/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 device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0.1, 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 1002,cbb2 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1002,7010 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 10b9,5237 card 103c,0850 rev 03 class 0c,03,10 hdr 00 (II) PCI: 00:06:0: chip 10b9,5451 card 103c,0850 rev 02 class 04,01,00 hdr 00 (II) PCI: 00:07:0: chip 10b9,1533 card 10b9,1533 rev 00 class 06,01,00 hdr 00 (II) PCI: 00:08:0: chip
RE: [XFree86] Blank LCD display
Can you send your XF86Config file. There is something strange going on there. The log file indicates that you have a virtual screen that is smaller than your actual screen. A virtual desktop would allow you to display say a 1024x768 layout on a 640x480 screen and pan around. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Miller, Marlena [mailto:[EMAIL PROTECTED] Sent: 08 July 2004 16:52 To: [EMAIL PROTECTED] Subject: RE: [XFree86] Blank LCD display Kevin, I take back my previous email where I said that there was no change after switching drivers. Now X windows fails to start. Any suggestions? Regards, Marlena The log follows: XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20 i686 [ELF] Build Date: 07 March 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: Mon Jan 7 06:47:53 2002 (==) Using config file: /usr/X11R6/lib/X11/XF86Config (==) ServerLayout Main Layout (**) |--Screen Screen 0 (0) (**) | |--Monitor Optrex LCD (**) | |--Device Geode (**) |--Input Device Mouse1 (**) |--Input Device touchscreen[1] (**) |--Input Device Keyboard1 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc101 (**) XKB: model: pc101 (**) Option XkbLayout us (**) XKB: layout: us (**) Option XkbVariant nodeadkeys (**) XKB: variant: nodeadkeys (WW) Option XkbOptions requires an string value (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/l ib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X1 1/fonts/75dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules (**) Option StandbyTime 20 (**) Option SuspendTime 30 (**) Option OffTime 60 (--) using VT number 2 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1078,0001 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:09:0: chip 104c,ac51 card , rev 00 class 06,07,00 hdr 82 (II) PCI: 00:09:1: chip 104c,ac51 card , rev 00 class 06,07,00 hdr 82 (II) PCI: 00:0a:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0e:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:12:0: chip 100b,0500 card 100b,0500 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:12:1: chip 100b,0501 card 100b,0501 rev 00 class 06,80,00 hdr 00 (II) PCI: 00:12:2: chip 100b,0502 card 100b,0502 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:12:3: chip 100b,0503 card 100b,0503 rev 00 class 04,01,00 hdr 00 (II) PCI: 00:12:4: chip 100b,0504 card 100b,0504 rev 01 class 03,00,00 hdr 80 (II) PCI: 00:12:5: chip 100b,0505 card 100b,0505 rev 00 class 06,80,00 hdr 00 (II) PCI: 00:13:0: chip 0e11,a0f8 card 0e11,a0f8 rev 08 class 0c,03,10 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,3), 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-CardBus bridge: (II) Bus 2: bridge is at (0:9:0), (0,2,2), BCTRL: 0x0340 (VGA_EN is cleared) (II) PCI-to-CardBus bridge: (II) Bus 3: bridge is at (0:9:1), (0,3,3), BCTRL: 0x0340 (VGA_EN is cleared) (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:18:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:18:4) National Semiconductor Corporation SCx200 Video rev
RE: [XFree86] Blank LCD display
As it happens we have a Geode base system here (using XFree 4.4.0 but the config files should be the same) If you want to try this save your XF86Config file so that you can get back to it later. (I saved mine as XF86Config.old) I used the xf86config utility to generate a config file for me. It worked first time. After the mouse and keyboard sections the monitor selection comes next. I selected a standard VGA monitor and selected 50-70Hz vertical refresh. Next is the VGA card selection. I selected the VESA compatible driver (the first one on the list) and selected the amount of memory I have for video memory. Then it comes up with a list of possible modes it thinks we can use. For each of the colour depths (8, 16 and 24 bit) you need to make sure that ONLY 640x480 is allowed. When you edit each colour depth you are asked if you want a virtual desktop. Answer no. I then selected 16 bit colour as my default. The config utility then created my XF86Config file for me. I typed startx and X started straight away. Here are my critical sections. Section Monitor Identifier Kevins 640 x 480- monitor HorizSync 31.5 VertRefresh 50-70 # NOTE there are no Mode line in here. EndSection Section Device Identifier Geode Driver vesa EndSection Section Screen # The Identifier, Device and Monitor lines must be present Identifier Screen 0 Device Geode Monitor Kevins 640 x 480- monitor DefaultDepth 16 SubSection Display Depth 8 Modes 640x480 ViewPort0 0 EndSubsection SubSection Display Depth 16 Modes 640x480 ViewPort0 0 EndSubsection SubSection Display Depth 24 Modes 640x480 ViewPort0 0 EndSubsection EndSection The ServerLayout section just points to Screen 0 as its only screen and that's it. My thought is that there is some sort of conflict going on between the modes specified by the Monitor section and what is specified in the Screens section. The Viewport option makes sure that the your 'window' onto a virtual desktop starts at the top left. Otherwise it would normally start in the middle. This should not really be an issue as the monitor resolution is 640x480 which is what we have set the screen resolution to. Hope this helps. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Blank LCD display
Pleased to be of help. Good luck with the rest of your project. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Miller, Marlena [mailto:[EMAIL PROTECTED] Sent: 09 July 2004 13:48 To: Benstead, Kevin; [EMAIL PROTECTED] Subject: RE: [XFree86] Blank LCD display Kevin, Thank you so much for your help. I followed your instructions and it's working!! Marlena -Original Message- From: Benstead, Kevin [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 8:20 AM To: Miller, Marlena; [EMAIL PROTECTED] Subject: RE: [XFree86] Blank LCD display As it happens we have a Geode base system here (using XFree 4.4.0 but the config files should be the same) If you want to try this save your XF86Config file so that you can get back to it later. (I saved mine as XF86Config.old) I used the xf86config utility to generate a config file for me. It worked first time. After the mouse and keyboard sections the monitor selection comes next. I selected a standard VGA monitor and selected 50-70Hz vertical refresh. Next is the VGA card selection. I selected the VESA compatible driver (the first one on the list) and selected the amount of memory I have for video memory. Then it comes up with a list of possible modes it thinks we can use. For each of the colour depths (8, 16 and 24 bit) you need to make sure that ONLY 640x480 is allowed. When you edit each colour depth you are asked if you want a virtual desktop. Answer no. I then selected 16 bit colour as my default. The config utility then created my XF86Config file for me. I typed startx and X started straight away. Here are my critical sections. Section Monitor Identifier Kevins 640 x 480- monitor HorizSync 31.5 VertRefresh 50-70 # NOTE there are no Mode line in here. EndSection Section Device Identifier Geode Driver vesa EndSection Section Screen # The Identifier, Device and Monitor lines must be present Identifier Screen 0 Device Geode Monitor Kevins 640 x 480- monitor DefaultDepth 16 SubSection Display Depth 8 Modes 640x480 ViewPort0 0 EndSubsection SubSection Display Depth 16 Modes 640x480 ViewPort0 0 EndSubsection SubSection Display Depth 24 Modes 640x480 ViewPort0 0 EndSubsection EndSection The ServerLayout section just points to Screen 0 as its only screen and that's it. My thought is that there is some sort of conflict going on between the modes specified by the Monitor section and what is specified in the Screens section. The Viewport option makes sure that the your 'window' onto a virtual desktop starts at the top left. Otherwise it would normally start in the middle. This should not really be an issue as the monitor resolution is 640x480 which is what we have set the screen resolution to. Hope this helps. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Blank LCD display
We've had exactly this problem. Replace the nsc driver with the standard vesa driver. The configure program sometimes incorrectly identifies the geode graphics engine. We never got to the bottom of it and now that AMD have taken over Geode from National (who took it over from Cyrix) I don't hold out much hope of it ever being fixed. AMD have there own embedded processors and the GEODE was a competitor. Which chips do you think AMD will put the support effort into. Also I'm a bit worried by the refresh rate you are driving the LCD at. Most work best at around 50/60 HZ. Suggest you fix on the optimum refresh rate for your LCD and just have that rate specified in your XF86Config file. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Miller, Marlena [mailto:[EMAIL PROTECTED] Sent: 08 July 2004 14:05 To: [EMAIL PROTECTED] Subject: [XFree86] Blank LCD display I am using X version 4.3.0 on Linux kernel version 2.4.10-1. I am trying to get a LCD display working, and am running into problems with X. When I start X windows, the LCD display goes blank. When I exit X, my LCD display comes back. I have checked, and my kernel was built without APM_DISPLAY_BLANK set. The display is 6 1/2 diagonal and the resolution is 640x480. Does anyone have an idea what the problem could be? What can I do to further diagnose this problem? Regards, Marlena Miller An excerpt from my XF86Cconfig file follows: === Section Monitor # The identifier line must be present. Identifier Optrex LCD HorizSync 30-115 # multisync VertRefresh 50-60# multisync # Modes can be specified in two formats. A compact one-line format, or # a multi-line format. ## Modeline 640x480-8540.5 640 663 752 832 480 481 484 509 Modeline 640x480-7531.5 640 656 720 840 480 481 484 500 Modeline 640x480-7231.5 640 663 704 832 480 489 492 520 Modeline 640x480-6025.175 640 656 752 800 480 490 492 525 EndSection # ** # Graphics device section # ** Section Device Identifier Geode Driver nsc Option HWcursor Option OffScreenMemory VideoRam4096 EndSection # ** # Screen sections. # ** # Any number of screen sections may be present. Each describes # the configuration of a single screen. A single specific screen section # may be specified from the X server command line with the -screen # option. Section Screen # The Identifier, Device and Monitor lines must be present Identifier Screen 0 Device Geode Monitor Optrex LCD # The favoured Depth and/or Bpp may be specified here # CRT modes DefaultDepth 16 SubSection Display Depth 8 Modes 640x480-85 640x480-75 640x480-72 640x480-60 EndSubsection SubSection Display Depth 16 Modes 640x480-85 640x480-75 640x480-72 640x480-60 EndSubsection EndSection ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] XFree86 4.3.0 with ATI Radeon 9100 IGP
Both of your device sections are using the same driver "vesa". I suspect that the vesa driver can't cope with being used twice. You should replace the "vesa" with whatever the driver name for your ATI card is. If you look in /usr/X11R6/modules/devices you should get a list of drivers that are installed. The string you put in quotes is the file name without the _drv.o on the end. Hope I'm not teaching you to suck eggs. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: colin higgs [mailto:[EMAIL PROTECTED]] Sent: 07 July 2004 16:54 To: [EMAIL PROTECTED] Subject: [XFree86] XFree86 4.3.0 with ATI Radeon 9100 IGP Hello everyone, [Sorry for a multiple posting. I seem to have reached the archives, but not the list So I'll try again.] I have recently bought an ASUS PUNDIT-R barebone system. The on-board graphic processor is an ATI Radeon 9100 IGP chip. This chip has both digital and analog outputs. I have two flat panels, EIZO L685 connected to the analog port and EIZO L767 connected to the digital port. I installed Red Hat Linux 7.3, kernel 2.4.20-28.7. Next I loaded XFree86 4.3.0. (I would like to stay with this for the moment in case I have to try ATI's propriety driver, 3.9.0 which runs under XFree86 4.3.0). My first observation is that the driver used by the Xserver is vesa. Despite configuring a xinerama server, I only get one screen active, either the digital screen, or the analog screen, (depending on what was connected). With both connected I get an Xserver on the screen pre-defined in the PUNDIT-R's BIOS. (Digital, analog, or both(clone)). But I can't get xinerama no matter what I do. As soon as I add Screen 1 in the second Device section, I get an error: Fatal server error: Requested Entity already in use! I have enclosed the following files. /etc/X11/XF86Config-4 /var/log/XFree86.log.0 (one screen attached) /var/log/XFree86.log.0 (two screens attached) Question: Is this integrated chip capable of running a xinerama Xserver? And why am I getting the vesa driver? All help will be most welcome. Thanking you in advance. My final aim is to have a 2x2 screen xinerama console, using the 9100 IGP on-board chip together with an ATI RADEON 9200 PCI card. I have configured many 4-screen servers using various MATROX cards, without any problems and without having to produce a customized kernel. Colin Higgs
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/07/06 20:46:24 Log message: 144. Disable building DMX on OSs that have not been verified to build correctly (Kevin Martin). 143. Fix DMX build when Xinerama is not enabled (Kevin Martin). Modified files: xc/config/cf/: README X11.tmpl linux.cf xf86site.def xfree86.cf xc/include/extensions/: Imakefile xc/programs/Xserver/: Imakefile xc/programs/Xserver/Xext/: dmx.c xc/programs/Xserver/hw/dmx/: Imakefile dmxcb.c dmxextension.c dmxinit.c xc/programs/Xserver/hw/dmx/glxProxy/: glxcmds.c xc/programs/Xserver/hw/xfree86/: CHANGELOG Revision ChangesPath 1.23 +3 -2 xc/config/cf/README 1.262 +17 -13xc/config/cf/X11.tmpl 3.228 +5 -1 xc/config/cf/linux.cf 3.191 +3 -9 xc/config/cf/xf86site.def 3.482 +1 -19 xc/config/cf/xfree86.cf 3.59 +2 -2 xc/include/extensions/Imakefile 3.303 +3 -1 xc/programs/Xserver/Imakefile 1.2 +5 -1 xc/programs/Xserver/Xext/dmx.c 1.3 +8 -3 xc/programs/Xserver/hw/dmx/Imakefile 1.2 +12 -1 xc/programs/Xserver/hw/dmx/dmxcb.c 1.2 +30 -30xc/programs/Xserver/hw/dmx/dmxextension.c 1.2 +3 -1 xc/programs/Xserver/hw/dmx/dmxinit.c 1.2 +11 -1 xc/programs/Xserver/hw/dmx/glxProxy/glxcmds.c 3.3290+4 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
[XFree86] Why is the Install script so complicated
I've only been playing (sorry USING) Linux for a few months. For an application which only has a small (250MB) compact flash card as a hard disk my colleagues and I created a small Linux installation with just the minimum number of tools installed. Then an application came along which needed us to be able to have a more graphical front end so we decided we would port XFree onto our system. We down loaded binaries for XFree4.4.0 for Linux running on an X86 processor with GlibC2.2 because we knew that was what we were going to be running on. Then what do we find. The install script starts to try and use tools which we don't have installed (grep). So we printed out the install script to see what is going on. 28 pages later we are not really any better off. So we searched the XFree website and found a document on doing a manual install. WOW the install is only a dozen or so commands. We ran all of the commands as per the document and 5 minutes or so later we had a working version of X installed on our system. Since then I've spent a few bleary eyed evenings pouring over the install script and have a simple question. Why if I have gone to the trouble of downloading a specific set of binaries for a specific processor (X86) a specific operating system (Linux) and a specific version of GLibC (2.2) does the install script need to go and check everything. Surely it is not beyond the wit of man (or developers) to produce a specific script for the specific set of binaries that have been downloaded. I realise that this would involve a little work and that several different versions of the script would need to be maintained BUT do these scripts really change that much between releases. The script for 4.3.0 look identical to the script for 4.4.0 apart from the version number. Kevin Benstead Senior Engineer RD Division Thermo Electron Corporation Radiation Measurement Protection Beenham, UK ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] DMX without Xinerama
On Sun, Jul 04, 2004 at 11:55:25AM -0700, Mark Vojkovich wrote: On Sun, 4 Jul 2004, [ISO-8859-1] Frédéric L. W. Meunier wrote: dmxcb.c: In function `dmxConnectionBlockCallback': dmxcb.c:118: error: `noPanoramiXExtension' undeclared (first use in this function) dmxcb.c:118: error: (Each undeclared identifier is reported only once dmxcb.c:118: error: for each function it appears in.) I think it's because I disabled Xinerama. Is this supposed to happen on current CVS ? That sounds like dmxcb.c doesn't have #ifdef PANORAMIX protection in the appropriate places. Either that or it requires Xinerama, in which case it shouldn't get built if Xinerama isn't enabled. A bug either way. It was missing a few #ifdef PANORAMIX's. Those have now been fixed. Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:07:59 xc/doc/man/DMX Update of /home/x-cvs/xc/doc/man/DMX In directory public.xfree86.org:/var/tmp/cvs-serv93917/doc/man/DMX Log Message: Directory /home/x-cvs/xc/doc/man/DMX added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:07:59 xc/lib/dmx Update of /home/x-cvs/xc/lib/dmx In directory public.xfree86.org:/var/tmp/cvs-serv93917/lib/dmx Log Message: Directory /home/x-cvs/xc/lib/dmx added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:08:00 xc/programs/Xserver/hw/dmx Update of /home/x-cvs/xc/programs/Xserver/hw/dmx In directory public.xfree86.org:/var/tmp/cvs-serv93917/programs/Xserver/hw/dmx Log Message: Directory /home/x-cvs/xc/programs/Xserver/hw/dmx added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:09:09 xc/programs/Xserver/hw/dmx/input Update of /home/x-cvs/xc/programs/Xserver/hw/dmx/input In directory public.xfree86.org:/var/tmp/cvs-serv94023/input Log Message: Directory /home/x-cvs/xc/programs/Xserver/hw/dmx/input added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:08:58 xc/programs/Xserver/hw/dmx/config Update of /home/x-cvs/xc/programs/Xserver/hw/dmx/config In directory public.xfree86.org:/var/tmp/cvs-serv94023/config Log Message: Directory /home/x-cvs/xc/programs/Xserver/hw/dmx/config added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:09:00 xc/programs/Xserver/hw/dmx/doc Update of /home/x-cvs/xc/programs/Xserver/hw/dmx/doc In directory public.xfree86.org:/var/tmp/cvs-serv94023/doc Log Message: Directory /home/x-cvs/xc/programs/Xserver/hw/dmx/doc added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:09:02 xc/programs/Xserver/hw/dmx/examples Update of /home/x-cvs/xc/programs/Xserver/hw/dmx/examples In directory public.xfree86.org:/var/tmp/cvs-serv94023/examples Log Message: Directory /home/x-cvs/xc/programs/Xserver/hw/dmx/examples added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:09:36 xc/programs/Xserver/hw/dmx/doc/html Update of /home/x-cvs/xc/programs/Xserver/hw/dmx/doc/html In directory public.xfree86.org:/var/tmp/cvs-serv94182/html Log Message: Directory /home/x-cvs/xc/programs/Xserver/hw/dmx/doc/html added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/06/30 13:21:47 Log message: 141. Add Distributed Multihead X (DMX) support (Kevin Martin and Rik Faith). Modified files: xc/config/cf/: README X11.tmpl sgi.cf xf86site.def xfree86.cf xc/doc/man/: Imakefile xc/include/GL/: glxint.h glxproto.h glxtokens.h xc/include/extensions/: Imakefile xc/lib/: Imakefile xc/lib/X11/: Imakefile xc/programs/Xserver/: Imakefile xc/programs/Xserver/Xext/: Imakefile panoramiX.c panoramiXsrv.h xc/programs/Xserver/dix/: events.c main.c xc/programs/Xserver/fb/: Imakefile xc/programs/Xserver/hw/: Imakefile xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/include/: misc.h xc/programs/Xserver/mi/: micmap.c miinitext.c xc/programs/Xserver/os/: access.c log.c xc/programs/Xserver/render/: glyph.c glyphstr.h picture.c picturestr.h render.c xc/programs/xdpyinfo/: Imakefile xdpyinfo.c Added files: xc/config/cf/: dmx.cf xc/doc/man/DMX/: DMX.man DMXAddInput.man DMXAddScreen.man DMXChangeDesktopAttributes.man DMXChangeScreensAttributes.man DMXForceWindowCreation.man DMXGetDesktopAttributes.man DMXGetInputAttributes.man DMXGetInputCount.man DMXGetScreenAttributes.man DMXGetScreenCount.man DMXGetWindowAttributes.man DMXQueryExtension.man DMXQueryVersion.man DMXRemoveInput.man DMXRemoveScreen.man DMXSync.man Imakefile xc/include/extensions/: dmxext.h dmxproto.h xc/lib/dmx/: Imakefile dmx.c xc/programs/Xserver/Xext/: dmx.c xc/programs/Xserver/hw/dmx/: Imakefile Xdmx.man dmx.h dmx_glxvisuals.c dmx_glxvisuals.h dmxcb.c dmxcb.h dmxclient.h dmxcmap.c dmxcmap.h dmxcursor.c dmxcursor.h dmxdpms.c dmxdpms.h dmxextension.c dmxextension.h dmxfont.c dmxfont.h dmxgc.c dmxgc.h dmxgcops.c dmxgcops.h dmxinit.c dmxinit.h dmxinput.c dmxinput.h dmxlog.c dmxlog.h dmxpict.c dmxpict.h dmxpixmap.c dmxpixmap.h dmxprop.c dmxprop.h dmxscrinit.c dmxscrinit.h dmxshadow.c dmxshadow.h dmxstat.c dmxstat.h dmxsync.c dmxsync.h dmxvisual.c dmxvisual.h dmxwindow.c dmxwindow.h xc/programs/Xserver/hw/dmx/config/: Canvas.c Canvas.h CanvasP.h Imakefile TODO dmxcompat.c dmxcompat.h dmxconfig.c dmxconfig.h dmxparse.c dmxparse.h dmxprint.c dmxprint.h dmxtodmx.c dmxtodmx.man parser.y scanner.l test-a.in test-a.out test-b.in test-b.out test-c.in test-c.out test-d.in test-d.out test-e.in test-e.out test-f.in test-f.out test-g.in test-g.out test-h.in test-h.out test-i.in test-i.out test-j.in test-j.out test-k.in test-k.out test-l.in test-l.out vdltodmx.c vdltodmx.man xdmxconfig.c xdmxconfig.man xc/programs/Xserver/hw/dmx/doc/: DMXSpec-v1.txt DMXSpec.txt Imakefile Makefile.linux dmx.sgml dmx.txt doxygen.conf doxygen.css doxygen.foot doxygen.head scaled.sgml scaled.txt xc/programs/Xserver/hw/dmx/doc/html/: ChkNotMaskEv_8c.html ChkNotMaskEv_8h-source.html ChkNotMaskEv_8h.html annotated.html classes.html dmx_8h-source.html dmx_8h.html dmx__glxvisuals_8h-source.html dmxarg_8c.html dmxarg_8h-source.html dmxarg_8h.html dmxbackend_8c.html dmxbackend_8h-source.html dmxbackend_8h.html dmxcb_8c.html dmxcb_8h-source.html dmxcb_8h.html dmxclient_8h-source.html dmxclient_8h.html dmxcmap_8c.html dmxcmap_8h-source.html dmxcmap_8h.html dmxcommon_8c.html dmxcommon_8h-source.html dmxcommon_8h.html dmxcompat_8c.html dmxcompat_8h-source.html dmxcompat_8h.html dmxconfig_8c.html dmxconfig_8h-source.html dmxconfig_8h.html dmxconsole_8c.html dmxconsole_8h-source.html dmxconsole_8h.html dmxcursor_8c.html dmxcursor_8h-source.html dmxcursor_8h.html dmxdetach_8c.html dmxdpms_8c.html dmxdpms_8h-source.html dmxdpms_8h.html dmxdummy_8c.html dmxdummy_8h-source.html dmxdummy_8h.html dmxeq_8c.html dmxeq_8h-source.html dmxeq_8h.html dmxevents_8c.html dmxevents_8h-source.html dmxevents_8h.html dmxext_8h-source.html dmxext_8h.html dmxextension_8c.html dmxextension_8h-source.html dmxextension_8h.html dmxfont_8c.html dmxfont_8h-source.html dmxfont_8h.html dmxgc_8c.html dmxgc_8h-source.html dmxgc_8h.html dmxgcops_8c.html dmxgcops_8h-source.html dmxgcops_8h.html dmxinit_8c.html dmxinit_8h-source.html dmxinit_8h.html dmxinput_8c.html dmxinput_8h-source.html dmxinput_8h.html dmxinputinit_8c.html
Re: Adding DMX to XFree86
On Wed, Jun 23, 2004 at 11:20:09AM +0100, Dr Andrew C Aitchison wrote: On Tue, 22 Jun 2004, Kevin E Martin wrote: We would like to include DMX in the next XFree86 release. 7. Add DMX and GLX Proxy support to Xinerama 9. Add protocol and structures to support GLX Proxy (from SGI) Does GLX Proxy allow hardware accelerated GLX ? Does it allow hardware accelerated GLX from remote machines independent of DMX ? If so GLX Proxy seems desireable on its own account. GLXProxy is a DMX-specific GLX implementation that acts as a proxy server for GLX protocol. SGI wrote this code and donated it to the DMX project. It takes advantage of any hardware accelerated indirect rendering that is already present on the back-end server to which it attaches, but it won't create hardware accelerated indirect rendering on a system that doesn't already have it. I think many of us would very much like to have hardware accelerated indirect rendering, and from time to time there has been talk of adding it to the DRI project. It's actually been on the to do list for the DRI project from the original design days, but it's a large project and there was little interest in funding it back when I was with PI and VA. I'm still hopeful that it will eventually happen. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Adding DMX to XFree86
On Wed, Jun 23, 2004 at 11:30:38AM -0700, Ian Romanick wrote: Kevin E Martin wrote: I think many of us would very much like to have hardware accelerated indirect rendering, and from time to time there has been talk of adding it to the DRI project. It's actually been on the to do list for the DRI project from the original design days, but it's a large project and there was little interest in funding it back when I was with PI and VA. I'm still hopeful that it will eventually happen. The current thinking is to, essentially, 'rm -rf xc/programs/Xserver/GL' and re-write it so that libglx.a loads a device-dependent *_dri.so, like the client-side libGL does. The advantage being that only one driver binary will be needed per-device. The support and maintainence advantages should be obvious. Exactly. That was the basic approach we were planning to take at PI. FYI, there are several papers (from either HP or SGI, IIRC) that give an overview of various the approaches. I can try to dig up those refs, if it would be helpful. Work has been started on an Xlib based DRI driver (something of a contradiction in terms, I know) by Adam Jackson. I've started writing Python scripts to automatically generate GLX protocol handling code (for both client-side and server-side). We're getting closer to starting the real work, but I need to clear a few things off my plate first. My goal is to start a branch in the DRI tree in the next few (3 to 4) months to get this work going. That's excellent! I look forward to seeing this effort get going. Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Adding DMX to XFree86
We would like to include DMX in the next XFree86 release. I have created a patch against the head of the current CVS tree with the changes to existing files as well as a tarball with the newly added files. You can view these in XFree86 Bugzilla #1414. Here is the link to the patch for the existing files: http://bugs.xfree86.org/attachment.cgi?id=1239action=view and here is a summary of the changes you will find in this patch: 1. Imakefile and config file changes to build DMX 2. SGI build and config file changes (from SGI) 3. Add DMX support to miinitext.c 4. Allow AbortServer to be called from DMX 5. Add glyph private and picture private support to Render extension 6. Add DMX support to xdpyinfo 7. Add DMX and GLX Proxy support to Xinerama 8. Add support for changing the default VENDOR_RELEASE and VENDOR_STRING 9. Add protocol and structures to support GLX Proxy (from SGI) If there are no objections to adding DMX, I will check in the changes to the CVS tree next week. Note: The patch above does not include the MAXSCREENS changes that we previously submitted since those changes caused a module ABI change. When/if the MAXSCREENS changes are accepted, the code in the patch above will automatically take advantage of it. For those not familiar with the DMX project, it adds support for distributing the multihead capabilities of the X Window System across multiple displays attached to different machines. For example, a simple application would be to provide multihead support using two desktop machines, each of which has a single display device attached to it. This can be scaled up to a large display wall created from multiple projected displays (up to MAXSCREENS displays). Additional information on the DMX project can be found on the project web page: http://dmx.sourceforge.net/ Kevin E. Martin and Rik Faith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[XFree86] Hyperpen
Hello! I want to use the hyperpen driver to make a graphic tablet work. Unfortunatelly I only found examples for very old version of XFree and because of that I'd like to know what to add to my XFree86Conf to make this tablet work. If there is any interest, I could make a manpage for the driver afterwards. I'm using Debian Sid with XFree86 4.3.0.1 Any help appreciated, Kevin Börgens -- http://www.boergens.de Freedom requires effort if it is to be won and vigilance if it is to be main- tained. People just don't value freedom until it's taken away Terry Goodkind Official Supporter of the Free Software Foundation Europe ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Setting up cloning on Compaq Evo N1020v
I have been researching how to setup cloning on a Compaq Evo N1020v with ATI Radeon IGP 340M graphics, running Red Hat Enterprise Linux 3 WS (update 2) with XFree86 4.3.0. I have been researching this in the news groups but have not yet found the right combination and I am out of ideas. I have included my XF86Config file and the log file. I am hoping that someone could point out what I have done wrong. XFree86 is successfully driving the built in LCD. Thanks, Kevin XF86Config: # XFree86 4 configuration created by redhat-config-xfree86 Section ServerLayout Identifier Default Layout Screen Screen0 InputDeviceSynaptics Touchpad CorePointer InputDeviceMouse0 AlwaysCore InputDeviceKeyboard0 CoreKeyboard Option Clone on EndSection Section Files # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath /usr/X11R6/lib/X11/rgb FontPath unix/:7100 EndSection Section Module Load dbe Load extmod Load fbdevhw Load glx Load record Load freetype Load type1 Load synaptics Load dri EndSection Section InputDevice # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option Xleds 1 2 3 # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option XkbModel pc102 # If you have a US Microsoft Natural keyboard, you can use: # Option XkbModel microsoft # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option XkbLayout de # or: # Option XkbLayout de # Option XkbVariantnodeadkeys # # If you'd like to switch the positions of your capslock and # control keys, use: # Option XkbOptionsctrl:swapcaps # Or if you just want both to be control, use: # Option XkbOptionsctrl:nocaps # Identifier Keyboard0 Driver keyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol IMPS/2 Option Device /dev/input/mice Option ZAxisMapping 4 5 Option Emulate3Buttons no EndSection Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option Device /dev/psaux Option Protocol auto-dev Option LeftEdge 1700 Option RightEdge 5300 Option TopEdge 1700 Option BottomEdge 4200 Option FingerLow 25 Option FingerHigh 30 Option MaxTapTime 150 Option MaxTapMove 220 Option VertScrollDelta 100 Option MinSpeed 0.04 Option MaxSpeed 0.12 Option AccelFactor 0.0010 Option SHMConfig on # Option Repeater /dev/ps2mouse EndSection Section Monitor Identifier Monitor0 VendorName COMPAQ ModelNameDigital Flat Panel 1024x768 DisplaySize 305229 HorizSync28.0 - 49.0 VertRefresh 43.0 - 60.0 Option dpms EndSection Section Monitor Identifier Monitor1 VendorName COMPAQ ModelNameCOMPAQ P1220 HorizSync30.0 - 130.0 VertRefresh 50.0 - 160.0 Option dpms EndSection Section Device Identifier Card0 Driver radeon VendorName ATI Technologies Inc BoardName Radeon IGP 340M # BusID PCI:1:5:0 # Screen 0 # VideoRam32768 # Option MonitorLayout LVDS, CRT # Option AGPMode 4 # Option OverlayOnCRTC2 on Option DesktopSetup 0x0100 EndSection #Section Device # Identifier Card1 # Driver radeon # VendorName ATI Technologies Inc # BoardName Radeon IGP 340M # BusID PCI:1:5:0 # Screen 1 # VideoRam32768 # Option MonitorLayout LVDS, CRT # Option AGPMode 4 # Option OverlayOnCRTC2 on #EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Depth 24 Modes1024x768 800x600
Re: [XFree86] S3 virge pci card S3 SDAC type, 4MB memory size
Isidro Jaimes wrote: Dear sirs, I got referred card file version 5.1024.329.0002 which I would like to get driver download and card flash sites. Will you pls inform me where to download said data? I'll really appreciate it since several problems are faced with this card ( image freeze, slow performance, display freeze, etc). I constructed my pc w/IWill XP-333-R motherboard, Athlon 1800 processor, 256 MB in RAM, 40 GB HD and Win2000 SO. If any suggestion on components I would appreciatte your valuable information. Respectfully Mr. Isidro Jaimes. Bst rgrds. This list is primarily for XFree86 on various operating systems. You may find windows drivers at http://www.s3graphics.com -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] s3 virge/dx
[EMAIL PROTECTED] wrote: dear sir I have been given a graphic card with a s3 virge/dx chipset card number ev-3ds3-4. Do I need to download a driver or can you tell me which to look for in windows 98. thankyou this will help as I am trying to give the children a better old computor for thier schoolwork. tommy If Windows 98 does not have the driver already, you may be able to find them at http://www.s3graphics.com . Follow the drivers link, which leads to this agreement page http://ranger.s3graphics.com/swlib/ -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Suse Linux 9 problem.
Title: Suse Linux 9 problem. Here's the XFree86.0.0.log file. Please take a look at it and let me know what might be the problem. Thanks. ... Kevin Martin [EMAIL PROTECTED] XFree86.0.0.log Description: Binary data
[XFree86] Could someone diagnose my XF86Config.0.log?
I am running an Athlon XP 2500+ 512 DDR ATI All in Wonder Radeon 7500 (AGP). I am running Gentoo - Linux kernel 2.4.22. My monitor is an NEC multisync FE700. Could someone look at my file here and help me? When I startx my monitor goes blank and the green LED turns orange and my system freezes. I must hard reboot to exit. Kevin XFree86 Version 4.3.0Release Date: 27 February 2003X Protocol Version 11, Revision 0, Release 6.6Build Operating System: Linux 2.4.21-pfeifer-r1_pre4 i686 [ELF] Build Date: 13 September 2003Before reporting problems, check http://www.XFree86.Org/to make sure that you have the latest version.Module Loader presentMarkers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown.(==) Log file: "/var/log/XFree86.0.log", Time: Sat Feb 28 10:18:02 2004(==) Using config file: "/etc/X11/XF86Config"(==) ServerLayout "Simple Layout"(**) |--Screen "Screen 1" (0)(**) | |--Monitor "My Monitor"(**) | |--Device "** ATI Radeon (generic) [radeon]"(**) |--Input Device "Mouse1"(**) |--Input Device "Keyboard1"(**) Option "AutoRepeat" "500 30"(**) Option "XkbRules" "xfree86"(**) XKB: rules: "xfree86"(**) Option "XkbModel" "pc101"(**) XKB: model: "pc101"(**) Option "XkbLayout" "us"(**) XKB: layout: "us"(==) Keyboard: CustomKeycode disabled(**) FontPath set to "/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"(==) ModulePath set to "/usr/X11R6/lib/modules"Using vt 7(--) 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.2XFree86 Video Driver: 0.6XFree86 XInput driver : 0.4XFree86 Server Extension : 0.2XFree86 Font Renderer : 0.4(II) Loader running on linux(II) LoadModule: "bitmap"(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a(II) Module bitmap: vendor="The XFree86 Project"compiled for 4.3.0, module version = 1.0.0Module class: XFree86 Font RendererABI class: XFree86 Font Renderer, version 0.4(II) Loading font Bitmap(II) LoadModule: "pcidata"(II) Loading /usr/X11R6/lib/modules/libpcidata.a(II) Module pcidata: vendor="The XFree86 Project"compiled for 4.3.0, module version = 1.0.0ABI 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 = 0x802c, mode1Res1 = 0x8000(II) PCI: PCI scan (all values are in hex)(II) PCI: 00:00:0: chip 10de,01e0 card , rev c1 class 06,00,00 hdr 80(II) PCI: 00:00:1: chip 10de,01eb card 1462,5700 rev c1 class 05,00,00 hdr 80(II) PCI: 00:00:2: chip 10de,01ee card 1462,5700 rev c1 class 05,00,00 hdr 80(II) PCI: 00:00:3: chip 10de,01ed card 1462,5700 rev c1 class 05,00,00 hdr 80(II) PCI: 00:00:4: chip 10de,01ec card 1462,5700 rev c1 class 05,00,00 hdr 80(II) PCI: 00:00:5: chip 10de,01ef card 1462,5700 rev c1 class 05,00,00 hdr 80(II) PCI: 00:01:0: chip 10de,0060 card 1462,5700 rev a4 class 06,01,00 hdr 80(II) PCI: 00:01:1: chip 10de,0064 card 1462,5700 rev a2 class 0c,05,00 hdr 80(II) PCI: 00:02:0: chip 10de,0067 card 1462,5700 rev a4 class 0c,03,10 hdr 80(II) PCI: 00:02:1: chip 10de,0067 card 1462,5700 rev a4 class 0c,03,10 hdr 80(II) PCI: 00:02:2: chip 10de,0068 card 1462,5700 rev a4 class 0c,03,20 hdr 80(II) PCI: 00:08:0: chip 10de,006c card , rev a3 class 06,04,00 hdr 01(II) PCI: 00:09:0: chip 10de,0065 card 1462,5700 rev a2 class 01,01,8a hdr 00(II) PCI: 00:1e:0: chip 10de,01e8 card , rev c1 class 06,04,00 hdr 01(II) PCI: 01:07:0: chip 13f6,0111 card 13f6,0111 rev 10 class 04,01,00 hdr 00(II) PCI: 02:00:0: chip 1002,5157 card 1002,0f2a rev 00 class 03,00,00 hdr 00(II) PCI: End of PCI scan(II) Host-to-PCI bridge:(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)(II) Bus 0 I/O range:[0] -100x - 0x (0x1) IX[B](II) Bus 0 non-prefetchable memory range:[0] -100x - 0x (0x0) MX[B](II) Bus 0 prefetchable memory range:[0] -100x - 0x (0x0) MX[B](II) PCI-to-ISA bridge:(II) Bus -1: bridge is at (0:1:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)(II) PCI-to-PCI bridge:(II) Bus 1: bridge is at (0:8:0), (0,1,1), BCTRL: 0x0002 (VGA_EN is cleared)(II) Bus 1 I/O range:[0] -100xc000 - 0xcfff (0x1000) IX[B](II) PCI-to-PCI bridge:(II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x000a (VGA_EN is set)(II) B
Re: radeon blanking report
On Fri, Feb 27, 2004 at 05:07:38PM -0500, David Dawes wrote: Does the patch at: http://bugs.xfree86.org/show_bug.cgi?id=1221 look OK or too risky given that 4.4.0 is due out in a couple of days? The patch does not look correct. I've CC'd Hui to see if he has any ideas. I'll also try the current driver on a couple of my cards tonight to see if it still works for me in DPMS mode. BTW, this DPMS code has not changed for over 16 months -- I would have expected to hear about this type of problem before then. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[XFree86] No screens found
I am running Gentoo GNU/Linux, kernel 2.4.22. I have an ATI All in Wonder Radeon 7500 AGP 64mb video card. When I startx I receive a "No screens found" error. ShouldI post my XF86Config.0.log file? Thank you. Kevin
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/02/25 20:25:32 Log message: 821. Fix Radeon secondary head register initialization (Hui [EMAIL PROTECTED], Benjamin Herrenschmidt). Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/hw/xfree86/drivers/ati/: radeon_driver.c Revision ChangesPath 3.3156+3 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG 1.118 +4 -3 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: [XFree86] S3 Virge video card
Ron Johnson wrote: On Tue, 2004-02-24 at 21:16, Eddie wrote: Feb.24th 2004 11:05pm Hello there; Ever since I installed this S3 Virge PCI video card(325 model with 4mb) no matter what resolution I use,usually 800x600 or 1024x768 when I move within Windows 95(or now 98SE)on this P166 based computer with 64mb ram,I see these little dots,the size of a pixel or so left behind when I open windows or close them.Under Windows 98SE,I allowed it to install the proper drivers but have since installed the 1997 drivers I was using when running Windows 95b.I have changed the refresh rate from 46,to 60 tried the optimum and adapter default options ,all with similar dotty results.Any information regarding this would be appreciated. Are you sure you're on the right mailing list? ViRGE suffers from some of the same problems in Windows that we see once in a while on various chipsets under XFree86/Unix variants... I'd suggest a lower refresh rate, followed by using the windows display setup and turning down the acceleration (it usually has 2 or 3 levels, full accel, partial accel, and no accel.) If that doesn't work, it may just be a factor of the cheap memory on some of those virge cards. -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
ViRGE GX trouble (was Re: [XFree86] difference)
Marcin G³ogowski wrote: hi, i've a question: what is the difference between XF86_S3V and xfree 4.3 compared to the s3 virge 86c385 card? i've the Compaq DeskPro 4000 which has the virge gx 86c385 graphics card and when I'm using the 3.3.6 server everything is ok, but when Im trying to run x with the 4.3 my desktop is messed up. i tried to ask You several months ago, but nobody helped me, so maybe this time I will have a luck. it is very importand to my, because I often work on my server which has the card. bye ps: i have tried all the options from manual without result ps2: if there is a way to get at least 72 hz with VESA mode PLEASE give me an hint how to do it. Would you describe how the desktop is messed up? That would help us understand what you are seeing. Does the noaccel option in the driver section make the problem go away? Can you post a log file (/var/log/XFree86.0.log) somewhere, for a run which you describe the desktop behavior for? The S3V server was one of the earlier virge drivers, with the s3virge driver in 4.x being a fairly large rewrite of that and the virge support in the SVGA driver from 3.3.6. Very little feedback has come in for ViRGE GX, so it sounds like we still have some trouble there. -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: r128 and CRT not enabled
On Tue, Jan 27, 2004 at 01:07:00PM -0500, David Dawes wrote: Does anyone have a reason to not apply the patch attached to http://bugs.xfree86.org/show_bug.cgi?id=935? I don't think this patch is correct. What it does is enable the CRTC while writing the new mode -- generally that is bad. I would suggest either (1) removing the R128_CRTC_VSYNC_DIS | R128_CRTC_HSYNC_DIS from the R128RestoreCrtcRegisters code or (2) add those bits to the R128Unblank code. #1 will change the behavior from putting the monitor in suspend mode during the CRTC changes to just blanking the screen, while #2 will automatically enable the HV sync signals when the screen is unblanked after a mode switch. Both should be safe. Are there others that have R128 laptops who could test this solution to see if it works for them? I no longer have a R128 laptop. Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Problem with S3 ViRGE DX
Nagy Ferenc László wrote: Hi! There was a thread in november with the same subject starting here: http://www.mail-archive.com/[EMAIL PROTECTED]/msg11195.html I have the same problem (on somebody else's hardware): when video memory is written, screen flickers. The effect can be seen better with small number of objects on black background, so here are the details: When there is a blue object somewhere on the left side, then a copy of the object appears about 170 pixels right in red color. Another 170 pixels right a green copy appears, then blue, red, green and so on again, with less and less intensity (less and less incorrect pixels). I've used 24 bit color depth and software cursor (so every mouse move caused video memory write). The phenomena didn't follow mouse, only the fact of move (change of picture) was important. Horizontal lines are peculiar (false pixels are in burst), but I've only seen vertical lines when the original picture contained one. Setting xvideo to no helps a lot. Reducing depth and resolution helps too. XFree86 version (from UHU-Linux 1.1-rc3): XFree86 Version 4.3.0.1 Release Date: 9 May 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-11smp i686 [ELF] Build Date: 18 December 2003 Video card (S3 ViRGE/DX from 1998): (II) PCI: 00:09:0: chip 5333,8a01 card 5333,8a01 rev 01 class 03,00,00 hdr 00 That thread covers the steps to reduce flicker. You will get rid of it by using depth 16 also, which is what I generally run on virge dx cards. These are low end graphics cards, and short of limiting the depth 24 resolution further in the driver, I don't think there are any other good solutions at this point. (Well, some driver tuning might help.) -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/01/06 08:28:25 Log message: The following memory leak was found during DMX development: 737. Fix memory leak when list of registered renderers are cleared at the start of each new server generation (Kevin Martin and Rik Faith). Modified files: xc/lib/font/fontfile/: renderers.c xc/programs/Xserver/hw/xfree86/: CHANGELOG Revision ChangesPath 1.8 +2 -2 xc/lib/font/fontfile/renderers.c 3.3082+3 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
[XFree86] Reserving colors at bootup
I'm trying to push a linux alternative to sun workstations. We have a proprietary viewing system that runs in 256 color mode. I've got a fujitsu lifebook n3010 with red hat 9 installed on it and nothing else. The application boots but throws a Cannot allocate colormap entry for default background error. When using the application, entering or leaving any window causes palette flashing. On solaris, we set the window manager to Allocate more colors to applications and do not have this problem. Any help would be appreciated! TIA, ks ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ModeLines
Hank Barta wrote: On Mon, 2003-12-29 at 17:24, Dennis Veatch wrote: On Monday 29 December 2003 05:18 pm, Hank Barta wrote: On Mon, 2003-12-29 at 13:13, Sean wrote: Looking for ModeLines for Samsung SyncMaster 192N. Have you tried http://xtiming.sourceforge.net/cgi-bin/xtiming.pl ? But be aware that newer servers (at least 4.3.0 from my experience) will calculate their own mode lines and discard any that they don't think the hardware is capable of (even if you know better.) If that's the case, how do you over ride what X thinks? I don't know. I cannot run my display at 1600x1200 at a flicker free refresh because X probes the dot clock at 170 MHz when in fact my card has a 220 MHz dot clock. (S3 968 on a Number 9 Motion 771.) With the older server (3.6.0) I could do this by specifying DacSpeed 220 in the Devices section of the XF86Config and providing appropriate mode lines. That does not work for 4.3.0. Instead the newer server reports that the mode line conflicts with the dot clock. (Not the exact wording of the message in the log, but I think that's what it means.) Sorry I could not provide more help. The S3 server is still not fully up to speed with what was in the 3.3 series, I suspect. There's been some work on it, but not much recent contributions I've heard of. It was one of the last to be (partially) migrated to the 4.x architecture. Contributions are always welcome. :) -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Keyboard failure without mouse
Hello, I am having a problem in that when X Windows starts and I don't have a mouse connected (sometimes I use a touchscreen and don't need a mouse), then the keyboard will not function. X Windows starts fine, but then I just can't do anything. I tried adding the AllowMouseOpenFail to the XF86Config-4 file, but it doesn't seem to do anything. Any ideas on how to fix this? I am running RedHat 7.3. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with S3 ViRGE DX
(++) S3VIRGE(0): DPI set to (100, 100) (II) Loading sub module fb (II) LoadModule: fb (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 ANSI C Emulation, version 0.2 (II) Loading sub module xaa (II) LoadModule: xaa (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) Loading sub module ramdac (II) LoadModule: ramdac (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (==) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xf400 - 0xf7ff (0x400) MS[B] [1] -1 0 0xffe0 - 0x (0x20) MX[B](B) [2] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [3] -1 0 0x000f - 0x000f (0x1) MX[B] [4] -1 0 0x000c - 0x000c (0x1) MX[B] [5] -1 0 0x - 0x0009 (0xa) MX[B] [6] -1 0 0xfb00 - 0xfbff (0x100) MX[B] [7] -1 0 0xfc00 - 0xfbff (0x0) MX[B]O [8] -1 0 0x000c - 0x000c (0x1) MX[B](B) [9] -1 0 0xf400 - 0xf7ff (0x400) MX[B](B) [10] 0 0 0x000a - 0x000a (0x1) MS[B](OprD) [11] 0 0 0x000b - 0x000b7fff (0x8000) MS[B](OprD) [12] 0 0 0x000b8000 - 0x000b (0x8000) MS[B](OprD) [13] -1 0 0x - 0x (0x1) IX[B] [14] -1 0 0x - 0x00ff (0x100) IX[B] [15] -1 0 0xa800 - 0xa81f (0x20) IX[B] [16] -1 0 0xb000 - 0xb01f (0x20) IX[B] [17] -1 0 0xb400 - 0xb41f (0x20) IX[B] [18] -1 0 0xb800 - 0xb80f (0x10) IX[B] [19] -1 0 0xd000 - 0xd0ff (0x100) IX[B] [20] -1 0 0xd400 - 0xd407 (0x8) IX[B] [21] -1 0 0xd800 - 0xd81f (0x20) IX[B] [22] 0 0 0x03b0 - 0x03bb (0xc) IS[B](OprU) [23] 0 0 0x03c0 - 0x03df (0x20) IS[B](OprU) (==) S3VIRGE(0): Write-combining range (0xf400,0x40) (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (**) S3VIRGE(0): Using FB (II) S3VIRGE(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles CPU to Screen color expansion Solid Horizontal and Vertical Lines Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 18 128x128 slots (==) S3VIRGE(0): Backing store disabled (==) S3VIRGE(0): Silken mouse enabled (**) Option dpms (**) S3VIRGE(0): DPMS enabled (II) S3VIRGE(0): Using overlay video (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (**) Option Protocol NetMousePS/2 (**) Mouse0: Protocol: NetMousePS/2 (**) Option CorePointer (**) Mouse0: Core Pointer (**) Option Device /dev/psaux (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) Server_Terminate keybinding not found (II) Mouse0: ps2EnableDataReporting: succeeded -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with S3 ViRGE DX
Peter Russell wrote: snip I have tried setting the NoAccel, HWCursor, and UseFB options for the s3virge driver but none of them made any difference. All at once, or individually? UseFB is the driver default for recent drivers, so shouldn't make a difference unless you used usefb no. I tried those options one at a time, and in combinations, and I did say usefb no (I did make an effort to rtfm before posting here :-) I'd be really surprised if NoAccel didn't fix this, but before you try it again, try adding xvideo no instead and tell us if that helps. Please send the driver log file again also. You should see the below go away when you set this option: (II) S3VIRGE(0): Using overlay video Setting that option does seem to make things very much better, but the problem is still present. Now the flickering is still there, but not as severe, and the picture is no longer corrupted when the flickering stops. Setting NoAccel true does not have any noticeable effect (apart from making things very much slower). I have attached the logs that were generated by setting each option (MIME attachments this time, not inline, is that OK?). This time I did not bother to remove my other graphics card before trying these options, so you will see that in the logs too. Am I right in thinking that shouldn't make any difference? The results seem to be the same with one or both cards in. I feel a bit bad posting two 30K attachments to a public mailing list. Would there be some better way to post them in future? Turning off XVideo has made things much better, so thankyou very much for your help so far! The xvideo option takes memory bandwidth in the current driver, even when you aren't running any xv apps... Ok, try the fifo_* options now (leaving xvideo no in also). Try fifo_moderate first, then fifo_conservative. I'd expect fifo_aggresive to be worse, but maybe not. No need to send any more log files for these runs, just check how the screen noise looks. depth 24 is the least optimized mode in the s3virge driver, as I tend to run depth 16 most of the time myself, and I don't think anyone else has really looked at it recently. -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with S3 ViRGE DX
Peter Russell wrote: The xvideo option takes memory bandwidth in the current driver, even when you aren't running any xv apps... Ok, try the fifo_* options now (leaving xvideo no in also). Try fifo_moderate first, then fifo_conservative. I'd expect fifo_aggresive to be worse, but maybe not. No need to send any more log files for these runs, just check how the screen noise looks. fifo_aggressive and fifo_moderate seem to make the problem worse (worse flickering and horizontal lines, but nothing left when the movement stops). fifo_conservative might make it slightly better, but the difference is very small, and its hard to tell. That's about the best we're going to get with the driver... I see you have an 1152x768 mode loading, is that one better? It should be, as well as 1024x768 (I think that's the highest I tested at depth 24.) Does Windows do better at that resolution? Some additional driver tweaking (in the code, not in config params) might help or using a different modeline. I see only one modeline for that resolution in your log, though. And to your prior question about the dual cards having an impact, I wouldn't think so. You don't see the streaking on the virge head while performing window operations on the other head, do you? -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with S3 ViRGE DX
Peter Russell wrote: That's about the best we're going to get with the driver... I see you have an 1152x768 mode loading, is that one better? It should be, as well as 1024x768 (I think that's the highest I tested at depth 24.) The 1152x768 mode is horrible, it has a refresh rate of 55Hz (fifty five hurts!), but the errors aren't there at that resolution. At 1024x768 it works fine (at 85Hz) now that I have the settings you suggested (although it seems quite slow, is that because of turning off XVideo?). Slower in that mode or slower in general? No, the xvideo option should have no impact on perceived speed. Noaccel should though... For the moment I am quite happy to leave it at that resolution. Does Windows do better at that resolution? Some additional driver tweaking (in the code, not in config params) might help or using a different modeline. I see only one modeline for that resolution in your log, though. In windows there are no such problems. However windows is only willing to drive the monitor at 60Hz rather than the 75Hz I was getting in X, so maybe refresh rate is a factor as well. That would seem to make sense if the problem is memory bandwidth. In that case I suppose a new modeline probably would work, but I'd rather sacrifice resolution than refresh rate, especially now my desktop is huge! I have also noticed that if I set my .xinitrc file to: metacity xsetroot -solid SteelBlue gnome-terminal rather than gnome-session There are no errors, even at 1152x864, even though the only visual difference is the addition of a couple of panels. That seems a bit strange. Any animated meters or other moving items on the gnome panel? Generally the problem shows up when updating portions of the screen more frequently. If you have the wm set to drag windows instead of dragging outlines, that will usually show the problem easily. And to your prior question about the dual cards having an impact, I wouldn't think so. You don't see the streaking on the virge head while performing window operations on the other head, do you? No, I now have Xinerama working quite nicely (although not at the res I would have liked). My next problem is to match the colours accross the two monitors. Thanks again for all your help! Glad we improved it :) -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] s3v: warning: VerticalRetraceWait timed out(1:3)
peter lageotakes wrote: Hello all, I am getting this warning message when I start x. Attached is my XF86Config file. Any help would be greatly appreciated. FYI: the complete error message is: s3v: warning: VerticalRetraceWait timed out(1:3). s3v: warning: VerticalRetraceWait timed out(3:3). s3v: warning: VerticalRetraceWait timed out(1:3). s3v: warning: VerticalRetraceWait timed out(3:3). Yes, this is a debug message. You can ignore it. Does your card work properly? -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] S3 driver bug
Klaus Peichl wrote:
Thomas Winischhofer wrote:
Apparently, after looking into the 3.3.6 code, the first generations of
S3 do support Bresenham lines after all.
What I see from comparing the code is that the 3.3.6 version does a lot
of stuff to reduce the error term to 12 bit which is the hardware's
maximum.
The 4.x code, although demanding a 12bit Bresenham error term from XAA,
simply adds the given minor and error term and writes the result to the
hardware register, without checking it for overflows. I don't know what
values this function is given, but in case the values are somewhat big,
this may result in a completely wrong error term. The result may very
well look like what the original poster saw, namely lines with a wrong
slope.
Furthermore, I think the way the error term, e1 and e2 values are
calculated differ:
3.3:
(deltas: adx = x2 - x1; ady = y2 - y1)
if (adx ady) {
axis = X_AXIS;-- x is major axis; adx=major ady=minor
e1 = ady 1;
e2 = e1 - (adx 1);
e = e1 - adx;
} else {
axis = Y_AXIS;-- y is major axis; adx=minor ady=major
e1 = adx 1;
e2 = e1 - (ady 1);
e = e1 - ady;
...
}
Simply put, if I understood that right, this does
e1 = minor;
e2 = minor - major;
4.x:
Here it looks like this:
e1 = major;
e2 = minor - major;
Would be interesting to know what impact this difference has. If
anybody's interested, I could compile the driver with that change and
send out the binary.
That would be great!
Will the binary be a replacement for /usr/bin/X11/XFree86
or will I have to change something else to test it?
The default XFree86 binary is a module loader, using drivers in
/usr/X11R6/lib/modules/drivers/ by default. Thomas would likely provide
you a s3.o module you could swap with your existing driver.
--
Kevin
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] S3 driver bug
Thomas Winischhofer wrote: Kevin Brosius wrote: I know the s3virge series doesn't have a breshenham compliant engine, and doubt the s3 variety does either. Their may be logic in the s3 driver to try and simulate bresenham lines with the s3 engine though. That wouldn't make sense as XAA supports both Bresenham and normal lines. Thomas Well, that kind of thing was attempted prior to XAA, but not in this case, it appears. I recall trouble with Bresenham on S3 hardware. Maybe this is it. It certainly looks like the accel function is sending bresenham parameters to the S3. -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/11/18 18:08:16 Log message: 602. Fix ForcePCIMode option to work as advertised in Radeon driver (Bugzilla #850, Kevin Martin). Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/hw/xfree86/drivers/ati/: radeon.man radeon_driver.c Revision ChangesPath 3.2974+3 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG 1.7 +2 -2 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 1.116 +32 -25xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: [XFree86] S3 driver bug
It appears the S3 maintenance isn't very active at the moment. You're reports are helpful, as this much detail may make it possible for someone else to touch up the drawline code. Not sure though I haven't looked at the s3 myself. Kevin Keith Tang wrote: Klaus, My system has the same card (S3 Trio 64) and it has the same problem with XFree 4.2.0 when Mandrake 8.2 was installed. After verifying it wasn't something which was messed up in my application, I installed XFree 3.3.6 and the problem was not present. The problem occurs with the XDrawLine call. In general, the longer the line segment, the worst the error. It appears like the second xy point in the call is getting corrupted. I wrote a small xforms application which demonstrated the problem and sent it to the list, but did not see any response. I assumed I was the only one who had experienced a problem. Keith Tang - Original Message - From: Klaus Peichl [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, November 16, 2003 6:45 AM Subject: [XFree86] S3 driver bug Hello XFree team, I have a problem with the S3 driver in XFree86 4.3.0 which was not present in XFree86 3.3.3. I have installed an S3 Trio 64 card and I am running SuSE-Linux 8.2. The S3 driver does not seem to draw sloping lines correctly. It seems that lines start at the correct position but get drawn into the wrong direction. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] re problem installing Gnome
I'm using Freebsd 5.1 installed using "standard install"from the mini-install. ive been able to install xfree86 basically. Im trying to install Gnome as my desktop. It downloads many packages then i get an error saying it has "failed" and "the filesystem is full". i have it installed on a 1.6 GB HD with 1 partition using all the space and I have nothing else installed. If someone could help as I am new to Unix flavoured O'S and dont know how to check where or how the space is being used up.
Re: nv driver obscurities...
Mike A. Harris wrote: On Fri, 7 Nov 2003, Mark Vojkovich wrote: Everywhere in the driver hex values are given premultiplied by 4 it seems, and specified as VALUE/4. The register pointers are dword pointers. The register offsets are byte offsets. They are written as VALUE/4 so that I can grep for VALUE. This is done so that it's easier for me to maintain. Converting everything to dword offsets will make my job more difficult. Ah, ok. I'm not sure why you are bringing this up. I'm bringing it up because I have no idea how Nvidia hardware works, have no Nvidia documentation, the source code of the driver is quite obfuscated by not using symbolic names for things, and that was one obfuscation that I thought might be something that could be cleaned up. Having no way of knowing why it is coded the way it is other than making a random guess, or by asking someone who does know, how is one supposed to find out why it is coded this way? I would think it would be obvious that since I am maintaining it, it would be in the form that is easiest for me to maintain. Sure, that works fine for me if that is the case, at least once it is known that there is a valid reason, and that it is done intentionally. But don't assume that I can mind read the intentions of an obfuscated driver. Would you prefer other developers and potential developers did not ask questions at all, and instead went off and worked on other projects? Seems every time someone asks for information on how something works in the codebase that they don't understand, or asks for clarification on something, they can't get a straight or clear answer. It's really no wonder volunteers get put off from contributing to the XFree86 project. Well, gee, Mike... You're question was filled with negative assumptions about why the driver might be 'obfuscated'. You shouldn't take offense if Mark is a little short with you. Focus on asking a question, leaving off the insinuations, and you'll get better answers. A shorter question like I'd find it clearer if the nv driver used #defines for registers rather than hardcoded values. Does anyone object to changing it? would tend to go over smoother. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Fullscreen DGA really slow
Pieter Hulshoff wrote: On Saturday 01 November 2003 15:03, Peter \ wrote: That's for the slow DGA setup, right? Yes, and luckily I just managed to get the Morphix cd to allow me to mount my drives. :) Here's the files from Morphix. Regards, Pieter Hulshoff Hmm, I'd suggest changing to this setting in the Screen section (from 24) DefaultColorDepth 16 if that's not faster, send the log file again. It also appears that the drivers aren't exactly the same, as I see slight differences in the startup sequence. The version stamps don't indicate the difference though. The last two lines in the snippet below are only in the slow setup... Maybe that's a factor of the depth, but I don't know. (II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (--) RADEON(0): Chipset: ATI Radeon 9000 If (AGP) (ChipID = 0x4966) (--) RADEON(0): Linear framebuffer at 0xd800 (--) RADEON(0): MMIO registers at 0xe100 (--) RADEON(0): VideoRAM: 65536 kByte (64-bit DDR SDRAM) (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 1 Also, the slow version is running dri/drm. That may be interacting with DGA. Do you want to be able to run 3D accel using dri/drm? -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Fullscreen DGA really slow
Kevin Brosius wrote: Pieter Hulshoff wrote: On Saturday 01 November 2003 15:03, Peter \ wrote: That's for the slow DGA setup, right? Yes, and luckily I just managed to get the Morphix cd to allow me to mount my drives. :) Here's the files from Morphix. Regards, Pieter Hulshoff Hmm, I'd suggest changing to this setting in the Screen section (from 24) DefaultColorDepth 16 if that's not faster, send the log file again. It also appears that the drivers aren't exactly the same, as I see slight differences in the startup sequence. The version stamps don't indicate the difference though. The last two lines in the snippet below are only in the slow setup... Maybe that's a factor of the depth, but I don't know. (II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (--) RADEON(0): Chipset: ATI Radeon 9000 If (AGP) (ChipID = 0x4966) (--) RADEON(0): Linear framebuffer at 0xd800 (--) RADEON(0): MMIO registers at 0xe100 (--) RADEON(0): VideoRAM: 65536 kByte (64-bit DDR SDRAM) (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 1 Whoops, CloneDisplay is an option in the ServerLayout section. Ignore this comment about the drivers being different. Also, the slow version is running dri/drm. That may be interacting with DGA. Do you want to be able to run 3D accel using dri/drm? -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Fullscreen DGA really slow
Pieter Hulshoff wrote: On Saturday 01 November 2003 12:56, Peter \ wrote: On Fri, 31 Oct 2003, Pieter Hulshoff wrote: On my SuSE 8.2 system, default xfree86 drivers, which are? XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 The real question he needs answered, is what driver? How did you configure? sax? What video driver did it/you use? Please include a copy of /var/log/XFree86.0.log. If you look at the same file from Morphix, we can easily answer your question... morphix boot cd as well, which use which XFree86 version? XFree86 Version 4.3.0 (Debian 4.3.0-0ds4 20030416150820 [EMAIL PROTECTED]) Release Date: 18 March 2003 X Protocol Version 11, Revision 0, Release 6.6 I did some more checks, and I should perhaps specify the problems a bit: xmame using DGA normally works fine xmame using xv normally works at about half of the normal DGA speed xmame using DGA with a scaling effect works at about 1/13th of the normal DGA speed xmame using xv with a scaling effect works at about 1/4th of the normal DGA speed What troubles me is the 1/13th of the speed I get using a simple scaling effect under DGA. Neither fullscreen xv nor windowed running of xmame gives me such slow performance. Under the Morphix cd I have no such problems: it runs at about 1/2 the speed of normal DGA mode. Hence I figured it was either a driver or an XFree86 configuration issue. Regards, Pieter Hulshoff -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 3 heads with S3 drivers
Rutka Patrick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have 3 screens : one with NVIDIA drivers, and the 2 others with S3 drivers. NVIDIA/NV with one in S3 woks perfectly. Now with the 3 heads activated, I have system crashes (linux+xfree : frezzes) randomely(?) or after a few minutes (Never craches if I don't use my 2 screen with s3). Sometimes when I move from the 2 S3 screens I have parts of my screen 3 are visibles on my screen 2. These parts are not random but represents elements (like the blue bars of artscontrol) but on the bad screens (like the drivers take the memoty of the other driver). Vesa driver in multi-head doesn't work so I don't could test with it. And with the NV driver in 3 Multi-Head do sometimes an error of SHMAT on HIGH MEMORY... I attach my config and the log : I use Linux (2.6.0-test9) and Xfree 4.3.0 on a Mandrake 9.1 I seem to recall a few reports of trouble with the S3 driver in multihead. I suspect it's not fully stable for dual and higher use, but not absolutely sure. It's good news it works well with 2 heads. Sounds like there is still a problem with 2 S3 cards though. Hopefully one of the S3 guys can take a look. -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/10/07 15:47:13 Log message: 478. Radeon driver fixes (Hui [EMAIL PROTECTED]) - 9200 DVI fix and TMDS_PLL initialization for all chips - New chips support (9800XT/SE, 9600XT/SE, M11, T2/X2 etc.) - Cleanup unused/secondary chip ids - Autodetect PCI cards - Add BusType to override PCI card autodetect - Add display bandwidth calculation routine to fix flickering/tearing display problem - Workaround for corrupted BIOS image causing incorrect panel size - Fix the LCD table reading loop - Various small changes (including improving DDC reliability and CRTC_MORE_CNTL initialization) Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/hw/xfree86/common/: xf86PciInfo.h xc/programs/Xserver/hw/xfree86/drivers/ati/: atichip.c atichip.h atiprobe.c radeon.h radeon.man radeon_driver.c radeon_probe.c radeon_reg.h Revision ChangesPath 3.2872+14 -2 xc/programs/Xserver/hw/xfree86/CHANGELOG 1.154 +15 -13xc/programs/Xserver/hw/xfree86/common/xf86PciInfo.h 1.37 +21 -10xc/programs/Xserver/hw/xfree86/drivers/ati/atichip.c 1.25 +2 -1 xc/programs/Xserver/hw/xfree86/drivers/ati/atichip.h 1.60 +2 -1 xc/programs/Xserver/hw/xfree86/drivers/ati/atiprobe.c 1.42 +15 -18xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.h 1.4 +61 -10xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 1.108 +692 -151 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 1.30 +57 -59xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c 1.30 +37 -4 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_reg.h ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: VideoRAM option
Tim Roberts wrote: On Thu, 2 Oct 2003 08:07:31 -0600 (MDT), Marc Aurele La France wrote: On Wed, 1 Oct 2003, Marc Aurele La France wrote: My goal is to disable this option by default in drivers which correctly detect video memory on all supported cards, at least for our shipped drivers. I've disabled this setting in our radeon driver for example as that driver correctly detects video memory on all supported hardware. The atimisc module has been VideoRAM specifications for a long time. In ^ Finger check:ignoring the case of ATI adapters at least, if the driver doesn't properly detect video memory size, I'd consider it a bug. The S3 Savage driver also ignores VideoRAM. Every known Savage BIOS sets the RAM size in a scratch register, and since VIA isn't making any new Savages, every known BIOS can now be interpreted as every BIOS. This was also true of s3virge up to about a year ago. But I've finally run into a couple reports of mis-detected video ram. It seems a couple laptops do not have the bits wired correctly or something. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: VideoRAM option
Dr Andrew C Aitchison wrote: On Wed, 1 Oct 2003, Mike A. Harris wrote: If people (both other developers and end users) who _require_ the VideoRAM option in order for the proper amount of video memory to be useable with their card, could send me privately their: lspci -vvn or alternatively scanpci output (if lspci isn't available to them), that would help me assess how feasible this would be to do. The Millennium II cannot be probed; MGACountRam() claims it is a hardware bug. As far as I know this function correctly detects the cases it can't handle, and I don't have an accessible card to provide lspci output. My end-goal here, is to determine which hardware truely requires the VideoRAM option, and limit the usage of that option in our own XFree86 packages to those specific drivers and cards to limit the amount of bogus incoming bug reports and end user problems created by unnecessary overconfiguration. I might also add another option to re-enable VideoRAM override if people see cases where autodetection does work, but want to override it anyway, such as a global AllowVideoRAMOverride setting. ie: user has card with bad videoram, but by limiting videoram to a lower amount they can disable the bad area of memory. Would it be good enough to make the probed value override any larger amount specified by the user ? I'm not sure whether breaking the convention that user config overrides probed values is a good idea or not here. Well, it seems that this is a case of trying to fix the problem in the wrong place. Mike admits that some config tools make it entirely to easy to change the videoram setting, and then proposes that it be worked around by changing a fairly long standing methodology in the video drivers. Possibly adding a second option to override it. I vote for working on fixing the config tools instead. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Any way to intercept background painting in Xv?
I'm not sure how stopping the color key painting will help accomplish your goal here. It may be possible to grab the background data from the screen position, pre-blend it into your video image, and then display it as part of the video stream. However that will take quiet a bit of pre-processing. And you would still want to use color keying to accelerate the video display. Some hardware does support blending of the overlay against background data, I'm not sure if that could be used or not. -- Kevin Wei Chong wrote: I would like to make my Xvideo appear translunent by using alpha blending of my video image against the desktop background. However, each time before the before any of the Xv PutImage() is invoked, after the window is created, it appears that the background of the window has already been painted to some color, like black. I would like to prevent such things from happening. Thanks, Wei-Chong Tan. --- Mark Vojkovich [EMAIL PROTECTED] wrote: Perhaps you could explain what you are trying to do? The driver itself is responsible for painting the color key, and automatic painting of the key is usually optional behavior. One gets the idea that whatever you are trying to do, you are going about it the wrong way. Mark. On Sun, 28 Sep 2003, Wei Chong wrote: Hello, I would like to know which function is responsible to paint the window's background colorkey before any video image is display in the XVideo extension? I did a crash in my PutImage() to see the stack trace but i only see... main() -- Dispatch() -- ErrorMessage() -- xf86PutImage() -- my PutImage(). I looked into xf86PutImage() but didn't see any code that actually paint the window's background color. I would like to either: 1. Intercept the code that do actual painting and refrain it from doing so. OR 2. Obtain a snapshot of the background image being written over by the painting process before it occurs. Thanks, Wei-Chong. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Help on creating a Window Manager
Havoc Pennington wrote: On Sun, Aug 31, 2003 at 08:59:39PM +0200, Peter Poulsen wrote: I'm playing around with xlib, and is trying to make a window manager (just because I can ;-)). But the problem is that I need a little more information. Is there some good resources anybody know of? Also, is there a mailing list that is more suited for questions related to the use of xlib (as far as I understand this mailing list is conserned with the development of xfree, rather than the use of xlib)? The main resources are the ICCCM, the EWMH, and the source code of other window managers. twm is small and simple to learn from, though doesn't support the newer EWMH spec. Don't try to read the WM chapter in the Nye book, it's mostly wrong. You'll find http://www.freedesktop.org/standards/ helpful, it has copies of most of these standards. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Test VGA interface
Chimou wrote: Hi, I would like to know if it is possible with standard xfree features to know if a display is connected to a particular VGA interface or if it is specific to the hardware/driver used. For information, I have a nvidia card and I use the binary driver from NVIDIA. The goal is to start a different layout in function of connected display. Thx for your help or your tips The XF86Config file allows you to specify BusID for each Device in the form: BusID0:14:0 Each device could then be configured with it's own Screen section. And then you just need to specify their layout with the ServerLayout section (if you are doing multi-head). Most of what you need should be in 'man XF86Config' for the keywords. -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XFree86-4.2.1: Gigabyte Radeon 9200VIVO not working
I recently purchased a new graphics card, the Gigabyte Radeon 9200 VIVO. Attempts to configure X (XFree86-4.2.1) to work properly with it have failed. Attached are the auto-config log (XFree86.8.log) and a dump from the XFree86 version of scanpci (-v applied). I tried manually hacking my X config file, based on a readme file I found for the radeon series of graphics cards, where I manually supplied the card number, but it also failed ((WW) VGA: ChipID 0x in Device section Card0 isn't valid for this driver), where I tried variants of numbers found from the scanpci dump from the two ATI devices (it's a dual-header card with video in/out). The driver I tried using was the radeon driver. Further system information (if it is important): AMD Athlon-XP 2000 Gigabyte GA-7VAXP (VIA KT400 AGP chipset) Gigabyte GV-R9200 VIVO graphics card (Radeon 9200, 128 MB, 8x AGP ) 256 MB RAM Linux Kernel 2.4.21 XFree86-4.2.1 (compiled from a patched version of the XFree86-4.2.0 source) I am willing to try development versions or anything else available, although the CVS version I tried 2 days ago wouldn't compile. Any suggestions or fixes would be appreciated. Thank you for your time. -Kevin- scanpci_v.log Description: Binary data XFree86.8.log Description: Binary data
Re: [XFree86] strange problem with xfree
Andrew Rothbart wrote: Hi guys, Im having a strange problem. I can run kde as root, but whenever I try to run KDE as a user, I get the following error: Fatal Server Error: cannot move old logfile var!log!XFree86.0.log (sorry Im using ! instead of forward slashes, my keyboard configuration needs some work still ;) Ive attached the XFree96.0.log file. Thanks in advance :) Andrew Did you install XFree86 without suid root and then use startx rather than xdm? This is the most common cause of what you are seeing. You'll need to set the X server binary to suid root, or re-install with the config flag in host.def set to install as suid root. For example, for startx to work on Linux, it needs the properties to look like: -rws--x--x1 root root 2019033 2003-06-25 12:49 /usr/X11R6/bin/XFree86* -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ati mach264vt2
I'm new here too. I believe (according to old docs) I'm running the exact same vid card attached to my old HP Pavillion (trying to test linux). Running Mandrake 9.1 and XFree 4.3, I've had no luck getting the x server to start (ERROR: Screens found but no usable config to use...). So my first instinct is to say no, this card will not work under XFree86. I'm gonna buy a cheapo trident and try again. This h/w incompatibility is the only thing that will keep linux from being accepted by the masses. This card works under Windows. -Kevin [EMAIL PROTECTED] wrote: Hey, I am new here and I don't know where to put this question. I have an older computer with an ATI Mach(264vt2) graphics card, and the system is running Windows 95. Will these drivers work with this card and operating system? Or are these drivers only for Linux systems? Thank you for any help you can give. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] s3 virge adapter
Conniemiriam wrote: I am having problems with my display, I get all kinds of lines. What do I do to fix my display short of buying another videocard? Thanks. Have you posted a copy of /var/log/XFree86.0.log in a place we can see it? Does a screen capture show the lines you see? If so, that would be helpful. (But please don't send a screen capture to the list.) We need more information. -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] S3 Trio64V2/GX 2nd Post, 1st got hijacked...
JoeHill wrote: Hello, I do not believe this is a bug necessarily, I am just trying to clarify something with regard to getting XFree 4.3.0 running on an S3 Trio64V2/GX. On the list of supported hardware for 4.3.0, it states: The s3virge driver in XFree86 4.3.0 supports the S3 ViRGE, ViRGE DX, GX, GX2, MX, MX+, and VX chipsets. Does this include the chipset I have? Or does it *only* apply to a Virge chipset? I am concerned that theV2 part means it is some more obscure chipset that is not supported, since I seem to only be able to get XFree 3.3.6 to run, although in the XFdrake config util, the V2/GX *is* listed. Yes, this applies only to the ViRGE style chipsets. 4.3.0 ships different drivers for S3 ViRGE and S3 chipsets. There is a s3 driver and an s3virge driver. To add to the confusion, S3 started shipping flavors of the Trio that have extensions like the ViRGE chips, ie, yours which is a Trio64V2/GX. If supported, it would be by the s3 driver. I can only speak for s3virge, and it's not supported by that driver. I am running Mandrake 9.1 on an old Compaq Deskpro with the S3 onboard. I have tried XFdrake, testing at everywhere from 800x600x8bpp up to 1024x768x24bpp (wishful thinking?), and I have tried the listed drivers for: Trio64 (generic) Trio64V2/GX (generic) Virge/GX (generic) Now, sadly, I cannot seem to get it to test OK even when I choose XF 3.3.6 :( The first two are your best bets. I doubt the virge gx driver will work for a Trio chip. Any help appreciated, if it's RTFM, please give me a hint where to look. I have tried Google but have found nothing specific to my situation. Well, often drivers have a readme or man page. The s3 driver is one of the later ports to the 4.x architecture, and it appears not to have either of those yet. http://www.xfree86.org/4.3.0/RELNOTES3.html#10 Thank you for a great piece of work, this is the first problem I have ever had on any system with XFree, so I am more suspicious of Compaq and S3 than XFree in this matter, that is fer sure. Cheers! p.s. maybe this is incentive to start learning to use Linux in text mode only, huh? -- Kevin ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/07/02 10:31:31 Log message: 274. Do not drop HV sync during screen blanking for Radeon (Bugzilla #320, Michael Breuer, Hui [EMAIL PROTECTED]). 273. Let out-of-limit pixel clocks only use the frequency below pll output lower limit for Radeons (Bugzilla #262, John Vickers, Hui [EMAIL PROTECTED]). 272. Add support for Radeon cards with DAC/TMDS wire up in different ways from what the driver was originally programmed to; includes support for dual DVI cards (Hui [EMAIL PROTECTED]). 271. Add Radeon DPMS handling for flat panels (Bugzilla #26, Hui [EMAIL PROTECTED]). 270. Decreased the retry loops in DDC probing so that Radeon startup time won't be too long in the worst case (Hui [EMAIL PROTECTED]). 269. Fix Radeon Asic bug in RMX unit of IGP chips (Hui [EMAIL PROTECTED]). 268. Fix Radeon register initialization for RGB offset to fix the milky-screen problem (Bugzilla #351, Hui [EMAIL PROTECTED]). 267. Add support for new Radeon chips: R350(9800), RV350(9600,M10), RS250(IGP7000), RS300(IGP9000), RV280(9200) (Hui [EMAIL PROTECTED]). Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/hw/xfree86/common/: xf86PciInfo.h xc/programs/Xserver/hw/xfree86/drivers/ati/: atichip.c atichip.h atiprobe.c radeon.h radeon.man radeon_accel.c radeon_dri.c radeon_driver.c radeon_probe.c radeon_probe.h radeon_reg.h radeon_video.c Revision ChangesPath 3.2765+16 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG 1.149 +18 -1 xc/programs/Xserver/hw/xfree86/common/xf86PciInfo.h 1.35 +30 -6 xc/programs/Xserver/hw/xfree86/drivers/ati/atichip.c 1.24 +7 -3 xc/programs/Xserver/hw/xfree86/drivers/ati/atichip.h 1.58 +9 -1 xc/programs/Xserver/hw/xfree86/drivers/ati/atiprobe.c 1.40 +12 -10xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.h 1.3 +18 -6 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 1.34 +10 -4 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_accel.c 1.35 +9 -16 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c 1.98 +299 -122 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 1.27 +21 -1 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c 1.11 +3 -2 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.h 1.28 +16 -2 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_reg.h 1.28 +14 -6 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_video.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
