[XFree86] Re: XFree86-SVGA-3.3.6...rpm equivalent for XFree86-4.2.0? (RH8.0 install)
Hi again, responding to my own message :-/ On Friday, March 21, 2003, at 10:50 AM, Lachlan Deck wrote: My understanding is that XFree86-SVGA is no longer part of the XFree86 4.x product. Could someone please advise me on how to set things up? When I had RH7.1 (and also after updating this with the latest rpm available for that distribution from rpmfind.net) I had a very similar problem which was fixed by downloading & installing XFree86-SVGA-3.3.6-38.i386.rpm and consequently running "Xconfigurator --kickstart" as root and then rebooting. But I'm not sure what can be done within RH8.0 with the XFree86-4.2.0 install to get a similar result? The Display tool correctly probes my video card but I still get checkered backgrounds with various apps and windows...(e.g., Gnome menus and backgrounds are fine, KDE menus are all checkered, OpenOffice and various apps are unreadable!) I've got a little further...I found the following page (http://www.uni-paderborn.de/mirrors/xfree86/3.2/cirrus-7.html) that outlines some of the options that can be set to troubleshoot using Cirrus Logic Cards. So I have from the Display tool selected the card Cirrus Logic GD543x with memory size 2Mb using the cirrus driver. One of the options "noaccel" does the trick of stopping all the checkered display. However, this works fine for 256 Colors, but anything higher and redrawing is _painfully_ slow. It would be nice if this option could be eliminated from the equation so that I could enjoy some nicer graphics... So I can at least get work done now, but my question is: Is this a bug in the cirrus driver? Thanks muchly (for a reply even :-) Thanks - The video card (the output from SuperProbe from when I had 7.1 installed)... root > SuperProbe First video: Super-VGA Chipset: Cirrus CL-GD5430/40 (PCI Probed) Memory: 2048 Kbytes (Huge!) RAMDAC: Cirrus Logic Built-in 15/16/24-bit DAC (with 6-bit wide loopkup tables (or in 6-bit mode)) with regards, -- Lachlan Deck [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Bug 12] ati radeon unable to support nonstandard resolutions via DVI
--- Additional Comments From [EMAIL PROTECTED] 2003-03-20 21:07 --- The radeon driver should honour user defined modes, please provide a log and maybe the config file. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X Fonts
Matt, This was copied from Branden Robinson's xfree86 FAQ (slightly edited to make it less confusing for a non debian user) found here (I noticed that the one on xfree86.org has been taken down, unfortunately, because this question is asked all the time): http://people.debian.org/~branden/xsf/FAQ *) How do I get the X server to find the "fixed" font? If the X server refuses to start, complaining that it cannot find the "fixed" font, then one (or more) of the following is likely true: + You don't have a valid FontPath in your /etc/X11/XF86Config or /etc/X11/XF86Config-4 file. At the very minimum, your FontPath should look something like this: FontPath "/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/100dpi/,/usr/lib/X11/fonts/75dpi/" You will likely have several more directories listed. The "fixed" font is in the "misc" directory. + The fonts.dir or fonts.alias files in /usr/lib/X11/fonts/misc directory have been corrupted or are not present. This could be caused by a broken package which unpacks one or both of these files onto the system. A reinstallation of xfonts-base should fix the problem. + You're using a font server (either local or remote), and it is not running or not reachable. Note that Debian ships the xfs package with TCP listening turned off by default for security reasons. If you are running xfs locally and do not need to serve fonts to remote machines, you don't need to turn TCP listening back on. Instead, try a FontPath entry like this: FontPath "unix/:7100" If you are using a remote font server, determine whether or not it is running, is listening on the TCP port, and/or engage in some network troubleshooting. On Mon, 17 Mar 2003, Matt Mahoney wrote: > Where would I find the font fixed for my x font server? My server will > not start because it is missing. > > Matt Mahoney > Web Developer > [EMAIL PROTECTED] > ems-i.com > 801-302-1400 Phone > 801-302-1160 Fax > > > > ___ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 > > > ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] S3 driver problem in XFree 4.3.0
Hello, I have a card with a Trio64V2 chip and 4MB RAM. I want to use a 1280x1024x16 resolution. The S3 driver, however, doesn't seem to like that resolution. The log messages are below. I tried this with the VESA driver, and that driver gives me the desired resolution, confirming that the card supports it. Again, logs are below. Question: How can I get the S3 driver to give me the 1280x1024 resolution? There doesn't seem to be a man page that describes the options for the S3 driver. I tried to use the "set_mclk" and set_refclk" options that the S3 Virge driver supports, but these options don't change anything. -Joe XFree86.0.log using S3 driver: (II) s3(0): VESA BIOS detected (II) s3(0): VESA VBE Version 2.0 (II) s3(0): VESA VBE Total Mem: 4096 kB (II) s3(0): VESA VBE OEM: S3 Incorporated. 86C775/86C785 (II) s3(0): VESA VBE OEM Software Rev: 1.1 (II) s3(0): VESA VBE OEM Vendor: S3 Incorporated. (II) s3(0): VESA VBE OEM Product: Trio64V2/DX/GX (II) s3(0): VESA VBE OEM Product Rev: Rev E (==) s3(0): Using gamma correction (1.0, 1.0, 1.0) (**) s3(0): Chipset: "Trio32/64" (--) s3(0): Framebuffer @ 0xe000 (--) s3(0): videoRam = 4096 Kb (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, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (--) s3(0): MCLK 66.222 Mhz (--) s3(0): RefClock: 16000 (--) s3(0): Max pixel clock at this depth is 80 Mhz (II) s3(0): Monitor: Using hsync range of 31.50-82.00 kHz (II) s3(0): Monitor: Using vrefresh range of 50.00-150.00 Hz (II) s3(0): Clock range: 16.00 to 80.00 MHz ... (II) s3(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan) ... (II) s3(0): Not using mode "1280x1024" (no mode of this name) (--) s3(0): Virtual size is 1024x768 (pitch 1024) (**) s3(0): *Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz (II) s3(0): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync XFree86.0.log using VESA driver: (II) VESA(0): Total Memory: 64 64KB banks (4096kB) (II) VESA(0): Monitor: Using hsync range of 31.50-82.00 kHz (II) VESA(0): Monitor: Using vrefresh range of 50.00-150.00 Hz (--) VESA(0): Virtual size is 1280x1024 (pitch 1280) (**) VESA(0): *Built-in mode "1280x1024" (**) VESA(0): *Built-in mode "1024x768" (**) VESA(0): *Built-in mode "800x600" (**) VESA(0): *Built-in mode "640x480" (**) VESA(0): Built-in mode "1152x864" (**) VESA(0): Built-in mode "640x400" (--) VESA(0): Display dimensions: (360, 270) mm (--) VESA(0): DPI set to (90, 96) (**) VESA(0): Option "ShadowFB" "True" (II) VESA(0): Attempting to use 75Hz refresh for mode "1280x1024" (11a) (II) VESA(0): Attempting to use 85Hz refresh for mode "1024x768" (117) (II) VESA(0): Attempting to use 85Hz refresh for mode "800x600" (114) (II) VESA(0): Attempting to use 85Hz refresh for mode "640x480" (111) (II) VESA(0): Attempting to use 75Hz refresh for mode "1152x864" (163) (II) VESA(0): Attempting to use 85Hz refresh for mode "640x400" (11d) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XFree86 4.3.0 on 845G
(WW) I810(0): Bad V_BIOS checksum (EE) I810(0): unknown reason for exception (EE) I810(0): cannot continue (EE) I810(0): VBE initialization failed. (EE) Screen(s) found, but none have a usable configuration. XFree86.0.log Description: Binary data
[XFree86] [Bug 11] Display glitches on Radeon 7200 with version 4.1.0, 4.3.0
--- Additional Comments From [EMAIL PROTECTED] 2003-03-20 21:02 --- As it also happens without any acceleration, it could be something like incorrect memory timings or even a hardware defect. Does it work with that other OS? --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Einfach genial !!
GERADE SO 18 UND GEIL, SCHARF, FEUCHT, RASIERT UND BLUTJUNG !! UNTERhttp://ichwilleinenseitensprung.supereva.it/001.txtFINDEST DU ... SÜNDE UND VERSUCHUNG PUR!! ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] xfree86 4.3 and freebsd 5.0 and Radeon 9000
Hi, Is there a reason there are no 5.0 Freebsd binaries available for Xfree86 4.3 ? Are they incompatable ? I am trying to run X on a dell 8200 with the Ati Radeon 9000 video card and thought I might be more likely to have video support in the latest X release. Is there another version I should be looking at ? Thanks Rick ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XFree86-SVGA-3.3.6...rpm equivalent for XFree86-4.2.0? (RH8.0 install)
Hi all, My understanding is that XFree86-SVGA is no longer part of the XFree86 4.x product. Could someone please advise me on how to set things up? When I had RH7.1 (and also after updating this with the latest rpm available for that distribution from rpmfind.net) I had a very similar problem which was fixed by downloading & installing XFree86-SVGA-3.3.6-38.i386.rpm and consequently running "Xconfigurator --kickstart" as root and then rebooting. But I'm not sure what can be done within RH8.0 with the XFree86-4.2.0 install to get a similar result? The Display tool correctly probes my video card but I still get checkered backgrounds with various apps and windows...(e.g., Gnome menus and backgrounds are fine, KDE menus are all checkered, OpenOffice and various apps are unreadable!) Any advice would be greatly appreciated!! Thanks - The video card (the output from SuperProbe from when I had 7.1 installed)... root > SuperProbe First video: Super-VGA Chipset: Cirrus CL-GD5430/40 (PCI Probed) Memory: 2048 Kbytes (Huge!) RAMDAC: Cirrus Logic Built-in 15/16/24-bit DAC (with 6-bit wide loopkup tables (or in 6-bit mode)) with regards, -- Lachlan Deck [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X-window crash - Xfree86.log
On Thu, 20 Mar 2003, Mitz Kakazu wrote: > Hi, > > > > We're using RH 7.1 and our KDE crash suddenly. Here's the log file. > > > > Thanks, > Maybe you should upgrade your Xserver since that one it two years old. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] pixel corruption with s3 virge dx
Hi, I am having pixel corruption problems with an S3 Virge DX, and XFree 4.2.1. Whenever a portion of the screen needs to be redrawn, flickering occurs. In the most extreme cases, it is apparent that the flickering pixels are duplicated from other sections of the screen. Moving the mouse over blank areas of the screen does not generate any pixel corruption. This corruption occurs above 1024x768 at depth 16. No flickering at 24 bits up to 800x600, but after that bands of two or three gray lines move slowly up the screen. It's hard to tell if there is similar corruption occuring underneath that behaviour. To reduce the flickering, I have tried setting NoAccel and SWCusor to true. The only difference that made was to slow redrawing down, while retaining the pixel corruption. The option that seems to have helped is disabling XVideo. This greatly reduces the corruption. I've also tried lowering the first value in the 1280x960 mode line: Modeline "1280x960" 148.50 \ 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync It defaults to 148.5. Lowering it to 110 clears the flickering, but causes the edges of the viewable are to bow out, so I'm guessing that isn't the way to do it. 120 seems to be the best trade off between flickering and screen shape. Clutching at straws, I remember reading somewhere about X and serial port IRQ conflicts. The flickering and an increase in serial port silo overflows seem to coincide. I think that this was at the point I upgraded to 4.2.1 from 4.0 (I think). But I can't find that article again. If anyone could offer advice to clean this screen up I would appreciate it. I've attached my XFree86 config file and a copy of /var/log/XFree86.0.log. Anything else that might help to post, just ask. Thanks James 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/local/" 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/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "extmod" Load "xie" Load "pex5" Load "glx" Load "dri" Load "dbe" Load "record" Load "xtrap" Load "speedo" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" ## DisplaySize370 270 # mm Identifier "Monitor0" VendorName "NEC" ModelName"NEC V920" ## HorizSync31.5 - 82.0 ## VertRefresh 40.0 - 150.0 Option "DPMS" ModeLine "1280x960" 120.0 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "slow_edodram" # [] #Option "slow_dram" # [] #Option "fast_dram" # [] #Option "fpm_vram" # [] #Option "pci_burst" # [] #Option "fifo_conservative" # [] #Option "fifo_moderate" # [] #Option "fifo_aggressive" # [] #Option "pci_retry" # [] #Option "NoAccel" # [] #Option "early_ras_precharge" # [] #Option "late_ras_precharge"# [] #Option "lcd_center"# [] #Option "set_lcdclk"# #Option "set_mclk" # #Option "set_refclk"# #Option "show_cache"# [] #Option "HWCursor" # [] #Option "SWCursor" # [] #Option "ShadowFB" # [] #Option "Rotate"# [] #Option "UseFB" # [] #Option "mxcr3afix" # [] Option "XVideo""False" Identifier "Card0" Driver "s3virge" VendorName "S3" BoardName "ViRGE/DX or /GX" ChipSet "virge dx" BusID "PCI:0:20:0" End
Re: [XFree86] [4.3.0] nv driver: videoram option
On Thu, 20 Mar 2003, GoTaR wrote: > On Mon, Mar 17, 2003 at 15:05:42 -0500, Mark Vojkovich wrote: > > > > Ramdisk located in video ram would be overwritten if something else (in > > > ths case - X) use this video ram. > > > >You can't do that. Not only would you not want to do that > > because of the horrible performance reading from video ram, > > Is the performance worst than hard disk? About 10 MB/sec, so possibly. MArk. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] X-window crash - Xfree86.log
Hi, We’re using RH 7.1 and our KDE crash suddenly. Here’s the log file. Thanks, ~~~ Mitz Kakazu ContainerWorld Forwarding Service Inc. 1127 Derwent Way, Delta B.C. V3M 5R4 http://www.ContainerWorld.ca Tel: 604.540.2582 Fax: 604.540.2583 Tech: 1-877-838-8880 XFree86.0.log Description: Binary data
[XFree86] XFree86 4.3.0 (siliconmotion) vs Gateway Solo 2550 (LynxEM)
Hi,
same problem here (Thinkpad i1200, FreeBSD 5.0 current).
As a workaround I disabled xv. See attached patch.
Regards,
Johannes Hofmann
--- programs/Xserver/hw/xfree86/drivers/siliconmotion/smi_video.c.orig Thu Mar 20
22:51:02 2003
+++ programs/Xserver/hw/xfree86/drivers/siliconmotion/smi_video.c Wed Mar 19
19:52:43 2003
@@ -623,6 +623,8 @@
}
}
+numAdaptors = 0;
+
if (numAdaptors != 0)
{
DEBUG((VERBLEV, "ScreenInit %i\n",numAdaptors));
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Can't change hsync from 60Hz on secondary display- Radeon Mobility 9000 (M9)
(BTW: thanks for the help so far; I appreciate it!) > What about the CloneMode and CloneHSync options? Well, I tried. What I got was a 640x480 60Hz window on a 1600x1200 virtual screen. This is similar to the behavior I got with the default config, which only showed 640x480 even though the Modes line was "1600x1200" "1400x1050" ... "640x480". I removed all but "1600x1200", and that's the config I'd been running with before I started to ask questions about the low 60Hz refresh rate. Turn on the Clone options, and 640x480 reappears. Why? Here's a log diff between configs with and without Clone driver options turned on: 22c22 < (==) Log file: "/var/log/XFree86.0.log", Time: Thu Mar 20 15:08:12 2003 --- > (==) Log file: "/var/log/XFree86.0.log", Time: Thu Mar 20 15:15:24 2003 463a464,467 > (**) RADEON(0): Option "CloneDisplay" "2" > (**) RADEON(0): Option "CloneMode" "1600x1200" > (**) RADEON(0): Option "CloneHSync" "30.0 - 95.0" > (**) RADEON(0): Option "CloneVRefresh" "50.0 - 160.0" 480c484 < (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect --- > (II) RADEON(0): CloneDisplay option: Force On (2) 498a503 > (II) RADEON(0): Clone mode in config file is used 558c563 < (II) RADEON(0): Not using default mode "1792x1344" (hsync out of range) --- > (II) RADEON(0): Not using default mode "1792x1344" (width too large for virtual size) [ ... a bunch more of those ... ] 594c599 < (II) RADEON(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) --- > (II) RADEON(0): Not using default mode "2048x1536" (width too large for virtual size) 597,600c602,607 < (II) RADEON(0): Not using default mode "640x480" (width too large for virtual size) < (EE) RADEON(0): Virtual height (0) is too small for the hardware (min 128) < (EE) RADEON(0): No valid mode found for CRTC2 clone < (II) RADEON(0): Total of -1 clone modes found --- > (**) RADEON(0): Virtual size is 1600x1200 (pitch 1600) > (**) RADEON(0): *Mode "1600x1200" > (**) RADEON(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz > (II) RADEON(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync > -vsync > (II) RADEON(0): Valid Clone Mode: 640x480 > (II) RADEON(0): Total of 1 clone modes found 606c613 < (--) RADEON(0): Virtual size is 1600x1200 (pitch 1600) --- > (**) RADEON(0): Virtual size is 1600x1200 (pitch 1600) 784c791 < AUDIT: Thu Mar 20 15:08:15 2003: 4931 X: client 5 rejected from local host --- > AUDIT: Thu Mar 20 15:15:28 2003: 5136 X: client 4 rejected from local host = Here's the complete config file without the driver options: # 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 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 "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 "XkbVariant""nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions""ctrl:swapcaps" # Or if you just want both to be control, use: # Option "XkbOptions""ctrl:nocaps" # Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/psaux" Option
Re: [XFree86] X window installion problems
On Thu, 20 Mar 2003, Cheung, Jerry LC wrote: > We fail to start X - window after finish install the NETBSD 1.5 and > X-window 4.1. > The window prompt error message: "Fatal server error: no screens found" > Please advise how to solve this problems > Attached pls find the error log for your investigate. Try using the "ati" driver instead of "mga". Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [4.3.0] nv driver: videoram option
On Mon, Mar 17, 2003 at 15:05:42 -0500, Mark Vojkovich wrote: > > Ramdisk located in video ram would be overwritten if something else (in > > ths case - X) use this video ram. > >You can't do that. Not only would you not want to do that > because of the horrible performance reading from video ram, Is the performance worst than hard disk? > NVIDIA > hardware has critical state stored in videoram. The chip will > hang if it gets corrupted. It's my risk. Anyway, it doesn't matter - the option shall not end with sig11. -- GoTaR gotar> PLD stuff at http://mops.uci.agh.edu.pl/~gotar/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Help!!!
On Thu, 20 Mar 2003, PEREZ, Armand F. wrote: > The Linux 7.3 I installed cannot detect my monitor, I have Philips 15" 105E12 > monitor. Here's what happened, when the installation was just two clicks away, the > installer told me to indicate the monitor model which is not available among the > selection. So I just chosen Generic settings. When I restarted the pc, it just > gone straight to command line. Then typed, Xconfigurator, I chose settings and > even chose custom and entered the Horizontal and Vertical Sync Ranges, but it didn't > work. The Xconfigurator infact probed my video card (NVIDIA Riva TNT/TNT2) and also > prompted me if I would choose the monitor setting it has detected, 105E and ranges, > but if the Xconfigurator test my settings, it just went blank (black) and the error > message says that the configuration I entered are not correct. Please help. See > also the XFree86.0.log below. Thank you. > It's not the monitor. It's the chip. I've been told repeatedly that there is no NVIDIA chip with that device ID. (--) PCI:*(1:0:0) NVidia unknown chipset (0x002a) rev 21, Mem @ In the Section "Device" of the XF86Config file, add the line ChipID 0x0028 and it will treat it like a TNT2. Mark. > > XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System > (protocol Version 11, revision 0, vendor release 6600) > Release Date: 23 January 2002 > If the server is older than 6-12 months, or if your card is > newer than the above date, look for a newer version before > reporting problems. (See http://www.XFree86.Org/) > Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] > Build Host: daffy.perf.redhat.com > > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/XFree86.0.log", Time: Wed Mar 19 20:27:48 2003 > (==) Using config file: "/etc/X11/XF86Config-4" > (==) ServerLayout "XFree86 Configured" > (**) |-->Screen "Screen0" (0) > (**) | |-->Monitor "105E" > (**) | |-->Device "RIVA TNT2" > (**) |-->Input Device "Mouse0" > (**) |-->Input Device "Keyboard0" > (**) Option "XkbLayout" "us" > (**) XKB: layout: "us" > (==) Keyboard: CustomKeycode disabled > (**) FontPath set to "unix/:7100" > (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 7 > > (II) Open APM successful > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.5 > XFree86 XInput driver : 0.3 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.3 > (II) Loader running on linux > (II) LoadModule: "bitmap" > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > (II) Module bitmap: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > Module class: XFree86 Font Renderer > ABI class: XFree86 Font Renderer, version 0.3 > (II) Loading font Bitmap > (II) LoadModule: "pcidata" > (II) Loading /usr/X11R6/lib/modules/libpcidata.a > (II) Module pcidata: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 10b9,1647 card , rev 04 class 06,00,00 hdr 00 > (II) PCI: 00:01:0: chip 10b9,5247 card , rev 00 class 06,04,00 hdr 01 > (II) PCI: 00:02:0: chip 10b9,5237 card 10b9,5237 rev 03 class 0c,03,10 hdr 00 > (II) PCI: 00:04:0: chip 10b9,5229 card 10b9,5229 rev c4 class 01,01,8a hdr 00 > (II) PCI: 00:07:0: chip 10b9,1533 card 10b9,1533 rev 00 class 06,01,00 hdr 00 > (II) PCI: 00:0c:0: chip 127a,1025 card 127a,1025 rev 01 class 07,80,00 hdr 00 > (II) PCI: 00:0f:0: chip 13f6,0111 card 13f6,0111 rev 10 class 04,01,00 hdr 00 > (II) PCI: 00:11:0: chip 10b9,7101 card 10b9,7101 rev 00 class 06,80,00 hdr 00 > (II) PCI: 01:00:0: chip 10de,002a card , rev 15 class 03,00,00 hdr 00 > (II) PCI: End of PCI scan > (II) LoadModule: "scanpci" > (II) Loading /usr/X11R6/lib/modules/libscanpci.a > (II) Module scanpci: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) UnloadModule: "scanpci" > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (II) Host-to-PCI bridge: > (II) PCI-to-ISA bridge: > (II) PCI-to-PCI bridge: > (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) > (II) Bus 0 I/O range: > [0] -1 0x - 0x (0x1) IX[B] > (II) Bus 0 non-prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus 0 prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus 1: bridge is at (
Re: [XFree86] X window installion problems
(--) PCI:*(1:0:0) ATI Mach64 GW rev 122, Mem @ 0xfc00/24, 0xfbfff000/12, I/O You are using the wrong driver. Change "mga" to "ati" in the config file. Mark. On Thu, 20 Mar 2003, Cheung, Jerry LC wrote: > Dear sir, > > We fail to start X - window after finish install the NETBSD 1.5 and > X-window 4.1. > The window prompt error message: "Fatal server error: no screens found" > Please advise how to solve this problems > Attached pls find the error log for your investigate. > Thanks a lot! > <> > > Regards, > Jerry > ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Cursor Shapes
On Wed, 19 Mar 2003, Anurag Palsule wrote: > Hi, > > > Is there any X - API detect change in the cursor > shape, and get the current cursor shape for an X > session ? > I don't think so, at least not in the core protocol. Maybe in one of the extensions like xtest? I don't know. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Bug 17] New: Xfree86 Server 4.3.0 fails to build on FreeBSD (5.0-current) alpha-architecture [PATCH]
So 4.3.0, as it is distributed, doesn't build on FreeBSD alpha (I run
-current, but I think the same problems would exist for -stable).
The following patch makes the build work for me - it runs ok with my
matrox millenium II card.
It does 3 things -- it makes a prototype for a function that doesn't have
one (I couldn't find a header file with this, so I just include it here --
seems ugly), it fixes a problem with system include files (needed an extra
one) and it fixes some broken #ifdef'd code (the #endif is several lines
past where it should be, making the file have systax errors (the function
never finds a final closing '}').
I'd be happpy to answer any questions about the code, and I'd be happy to
try modified versions of this patch if you end up wanting to change things
around a bit.
(standard diff)
-
# diff xc/programs/Xserver/hw/xfree86/os-support/bsd/alpha_video.c
xc.working/programs/Xserver/hw/xfree86/os-support/bsd/alpha_video.c
35a36,38
> # ifdef __FreeBSD__
> # include
> # endif 38a42
> 53a58,59
> axpDevice bsdGetAXP(void);
> 262a269
> #endif
266d272
< #endif
-
(or unified diff)
-
--- xc/programs/Xserver/hw/xfree86/os-support/bsd/alpha_video.c Tue Oct 29
16:19:13 2002
+++ xc.working/programs/Xserver/hw/xfree86/os-support/bsd/alpha_video.c Tue Mar
4 10:02:16 2003
@@ -33,9 +33,13 @@
#include
#ifndef __NetBSD__
# include
+# ifdef __FreeBSD__
+# include
+# endif
# else
# include
#endif
+
#include "xf86Axp.h"
#include "xf86_OSlib.h"
@@ -51,6 +55,8 @@
#define MAP_FAILED ((caddr_t)-1)
#endif
+axpDevice bsdGetAXP(void);
+
#ifndef __NetBSD__
extern unsigned long dense_base(void);
@@ -260,10 +266,10 @@
#endif /* __OpenBSD__ */
xf86ErrorF("\tlinear framebuffer access unavailable\n");
+#endif
}
useDevMem = FALSE;
return;
-#endif
}
void
-
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] (no subject)
XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18-23mdkenterprise i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Mar 20 19:08:42 2003 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "layout1" (**) |-->Screen "screen1" (0) (**) | |-->Monitor "monitor1" (**) | |-->Device "device1" (**) |-->Input Device "Keyboard1" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "it" (**) XKB: layout: "it" (WW) Option "XkbOptions" requires an string value (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Mouse1" (**) FontPath set to "unix/:-1" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (**) Option "AllowMouseOpenFail" Using vt 7 (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8080, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3099 card ,0824 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b099 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:09:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0b:0: chip 1131,7145 card , rev 00 class 04,80,00 hdr 00 (II) PCI: 00:0f:0: chip 1102,0002 card 1102,8061 rev 07 class 04,01,00 hdr 80 (II) PCI: 00:0f:1: chip 1102,7002 card 1102,0020 rev 07 class 09,80,00 hdr 80 (II) PCI: 00:10:0: chip 9004,8178 card , rev 00 class 01,00,00 hdr 00 (II) PCI: 00:11:0: chip 1106,3074 card 1106,3074 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00 (II) PCI: 01:00:0: chip 102b,0525 card 102b,2159 rev 04 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0c (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xe600 - 0xe8ff (0x300) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xe400 - 0xe5ff (0x200) MX[B] (II) Bus -1: bridge is at (0:17:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 4, Mem @ 0xe400/25, 0xe600/14, 0xe700/23 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0x000f - 0x000f (0x1) MX[B] [3] -1 0x000c - 0x000e (0x3) MX[B] [4] -1 0x - 0x0009 (0xa) MX[B] [5] -1 0x - 0x (0x1) IX[B] [6] -1 0x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -
Re: [XFree86] mga 1600x1200 DVI [scanned]
Dr Andrew C Aitchison wrote: Thanks for clarifying. On my other G550 I have a 1600x1024 monitor on what appears to be a single-link cable. If I switch from DVI-digital to DVI-analog *on the monitor* the picture goes away, so I was getting very confused. This is [EMAIL PROTECTED] with a 108MHz clock, well under the 165MHz limit. There is something else: The *analog* signal (speak: DVI-A) is (partly) transferred on the extra pins, outside of this 8x3 block. There are (up to) four pins in a square, with a ~2mm wide "key" pin in the middle. If these pins around the key pin are missing, this is a digital-only cable. I have pins 123..678 in each row, ie I am missing a 2x3 block in the middle of an 8x3. I take it this is single-link. Think so, too. Might be DVI-A, though - see above. I should probably stop thinking about what my G550 will do on my SGI 1600SW+MLA. 1600x1024 seems to break all the rules. Should be possible using analog signals. But this is more a question for Matrox experts (which I certainly am not - don't even have such a card) Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] http://www.winischhofer.net/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] xdm exits with "setting process group for daemon failed: Not owner"
Regarding: xdm exits with "setting process group for daemon failed: Not owner" Email: [EMAIL PROTECTED] XFree86 Version: 4.3.0 OS: SunOS 5.8 Area: xdm Server: XFree86 (The XFree86 4.x server) Video Card: GFXP Description: I built XFree86 using gcc 3.2. Started xfs. Tried to start xdm (by running /usr/X11R6/bin/xdm as root from console) but it exited with xdm error (pid 21283): setting process group for daemon failed: Not owner truss shows setpgid call exits with EPERM before xdm prints the error message. In xdm source, in xc/programs/xdm/daemon.c: /* This gets error EPERM. Why? */ int stat = setpgid(child_id, child_id); So I'm guessing this is a known issue, but I'm not sure if it's known that it occurs on Solaris 8 as well, so I just wanted to report that. Repeat By: Build XFree86 on Solaris 8 and try to start xdm. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xinerama on Nvidia Qudro4 900XGL
I figured it out. It turns out that since I am using two digital flat panel screens I needed 'ConnectedMonitor DFP,DFP' instead of 'ConnectedMonitor DFP' On Thu, Mar 20, 2003 at 09:21:46AM -0600, Benjamin Herbert wrote: > Is TwinView supported by the Quadro4 900XGL card? I am using the nvidia > driver I downloaded from the nvidia website. It works fine on one > screen, but I still cant get both monitors to work. > The second one just has a bunch > of lines. > > Thanks again for any information. > Here is my current XF86Config-4 file with TwinView: > > > > > Section "ServerLayout" > Identifier "XFree86 Configured" > Screen 0 "Screen0" 0 0 > InputDevice"Mouse0" "CorePointer" > InputDevice"Keyboard0" "CoreKeyboard" > EndSection > > Section "Module" > Load "dbe" # Double-buffering > #Load "GLcore" # OpenGL support > #Load "dri"# Direct rendering infrastructure > Load "glx" # OpenGL X protocol interface > Load "extmod" # Misc. required extensions > Load "v4l" # Video4Linux > # Load "record"# X event recorder > # You only need the following two modules if you do not use xfs. > # Load "freetype" # TrueType font handler > # Load "type1" # Adobe Type 1 font handler > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "keyboard" > Option "XkbLayout" "us" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Device" "/dev/mouse" > Option "Protocol" "IMPS/2" > Option "Emulate3Buttons" "off" > Option "ZAxisMapping" "4 5" > EndSection > > Section "Monitor" > Identifier "DELL 1900FP" > VendorName "Unknown" > ModelName "Unknown" > HorizSync 30 - 80 > VertRefresh 56 - 76 > Option "dpms" > EndSection > > Section "Device" > Identifier "NVIDIA GeForce 4 (generic)" > Driver "nvidia" > BoardName "Unknown" > EndSection > > Section "Device" > Identifier "Linux Frame Buffer" > Driver "fbdev" > BoardName "Unknown" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "NVIDIA GeForce 4 (generic)" > Monitor "DELL 1900FP" > DefaultDepth 16 > Subsection "Display" > Depth 16 > Modes "1280x1024" > EndSubSection > Option "TwinView" "on" > Option "SecondMonitorHorizSync" "30 - 80" > Option "SecondMonitorVertRefresh" "56 - 60" > Option "Metamodes" "1280x1024" > Option "TwinViewOrientation" "RightOf" > Option "ConnectedMonitor" "DFP" > EndSection > > Section "DRI" > Mode 0666 > > EndSection > > > > On Wed, Mar 19, 2003 at 05:55:55PM -0500, Mark Vojkovich wrote: > > > >Dual head operation is only supported with the NVIDIA binary drivers. > > I'd recommend avoiding NVIDIA version 4191 and using version 3123 > > instead. Read the section on TwinView in the NVIDIA README to > > configure it. It is not configured the way other dual-head cards > > supported by XFree86 are configured. It does not have two > > screen sections, for instance. > > > > > > Mark. > > > > > > On Wed, 19 Mar 2003, Benjamin Herbert wrote: > > > > > Hello All, > > > > > > Does anybody have any experience running Xinerama on a Quadro4 900XGL? > > > There is one card with dual output and both monitors are exactly the > > > same. When I run Xconfigurator the driver gets set to 'vesa' and when I > > > run startx both monitors work, but they are showing the same thing in > > > both monitors. > > > > > > I have downloaded and installed the Nvidia GLX and kernel rmps and > > > changed my device to 'nvidia' but when I ran startx only one monitor > > > worked. The other monitor showed as a bunch of lines. I read in the > > > known bugs section that Xinerama does not work with OpenGL. Does this > > > mean that it will not work with the 'vesa' driver as well. Thanks for > > > any information, and here is my XFree86-4 file (ps - I am using RH7.3): > > > > > > # XFree86 4.2.0 configuration generated by Xconfigurator 4.10.7 > > > > > > Section "ServerLayout" > > > Identifier "XFree86 Configured" > > > Screen 0 "Screen0" 0 0 > > > Screen "Screen1" RightOf "Screen2" > > > Option "Xinerama" "on" > > > InputDevice"Mouse0" "CorePointer" > > > InputDevice"Keyboard0" "CoreKeyboard" > > > EndSection > > > > > > Section "Module" > > > Load "dbe" # Double-buffering > > > Load "GLcore" # OpenGL support > > > Load "dri"# Direct rendering infrastructure > > > Load "glx" # OpenGL X protocol interface > > > Load "extmod" # Misc. required extensions > > > Load "v4l"
[XFree86] keyseq created with ctrl in xterm different since xfree 4.3 ?
Hi there, I just installed a new LFS with XFree86 4.3. I'm having the following problem with xterm: ctrl+ now creates different keysequences on my system. For example: ctrl+ now creates "^[[1;5C". On my other (older) systems it would create "^[[5C". (You can check that by ctrl+v ctrl+right) I changed my /etc/inputrc to reflect the changes, so 'forward-word' works again. But in Vim using ctrl+right now deletes the rest of the text (!), instead of jumping to the next word to the right, as it should. Ok, it's just the first application I had a problem with, but I guess I will find a few more, because I'm still using a lot of console-based programs. Anyone got an idea, how to make ctrl create keysequences as before in older XFree86 versions ? I'm completely lost, when it comes to configuring XKB more than this: Driver "keyboard" Option "Protocol""Standard" Option "XkbLayout" "de" Option "XkbModel""pc105" Option "XkbRules""xfree86" Option "XkbVariant" "nodeadkeys" Sorry, if this has already been reported or solved, but I'm not a member of this mailinglist, thus I'd also like to get cc'ed on any answer or comment, please. Systeminfo: TERM=xterm xterm in /usr/share/terminfo/x/ is a link to xterm-xfree86 (tried using the old xterm-xfree86 file to no avail.) Any help would be really appreciated :-) Regards, Marc Thoben ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Fatal error starting X
I send you my log file when I start in grphic mode in Linux red hat 8.0 I'm sure that my video card is S3 Trio 64 v2 DX I'm waiting your solution Thanks <>
[XFree86] [Bug 6] Generic int10 module broken
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=6 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] Status|ASSIGNED|NEW --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 10:27 --- This problem affects XFree86 4.3.0 on all ix86 systems (except Linux). The attachment is a source fix that has already been committed to both HEAD and xf-4_3-branch. Marc. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Bug 6] Generic int10 module broken
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=6 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 10:23 --- Created an attachment (id=6) Source fix for 4.3.0 --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xinerama on Nvidia Qudro4 900XGL
Is TwinView supported by the Quadro4 900XGL card? I am using the nvidia driver I downloaded from the nvidia website. It works fine on one screen, but I still cant get both monitors to work. The second one just has a bunch of lines. Thanks again for any information. Here is my current XF86Config-4 file with TwinView: Section "ServerLayout" Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Module" Load "dbe" # Double-buffering #Load "GLcore" # OpenGL support #Load "dri"# Direct rendering infrastructure Load "glx" # OpenGL X protocol interface Load "extmod" # Misc. required extensions Load "v4l" # Video4Linux # Load "record"# X event recorder # You only need the following two modules if you do not use xfs. # Load "freetype" # TrueType font handler # Load "type1" # Adobe Type 1 font handler EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Device" "/dev/mouse" Option "Protocol" "IMPS/2" Option "Emulate3Buttons" "off" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "DELL 1900FP" VendorName "Unknown" ModelName "Unknown" HorizSync 30 - 80 VertRefresh 56 - 76 Option "dpms" EndSection Section "Device" Identifier "NVIDIA GeForce 4 (generic)" Driver "nvidia" BoardName "Unknown" EndSection Section "Device" Identifier "Linux Frame Buffer" Driver "fbdev" BoardName "Unknown" EndSection Section "Screen" Identifier "Screen0" Device "NVIDIA GeForce 4 (generic)" Monitor "DELL 1900FP" DefaultDepth 16 Subsection "Display" Depth 16 Modes "1280x1024" EndSubSection Option "TwinView" "on" Option "SecondMonitorHorizSync" "30 - 80" Option "SecondMonitorVertRefresh" "56 - 60" Option "Metamodes" "1280x1024" Option "TwinViewOrientation" "RightOf" Option "ConnectedMonitor" "DFP" EndSection Section "DRI" Mode 0666 EndSection On Wed, Mar 19, 2003 at 05:55:55PM -0500, Mark Vojkovich wrote: > >Dual head operation is only supported with the NVIDIA binary drivers. > I'd recommend avoiding NVIDIA version 4191 and using version 3123 > instead. Read the section on TwinView in the NVIDIA README to > configure it. It is not configured the way other dual-head cards > supported by XFree86 are configured. It does not have two > screen sections, for instance. > > > Mark. > > > On Wed, 19 Mar 2003, Benjamin Herbert wrote: > > > Hello All, > > > > Does anybody have any experience running Xinerama on a Quadro4 900XGL? > > There is one card with dual output and both monitors are exactly the > > same. When I run Xconfigurator the driver gets set to 'vesa' and when I > > run startx both monitors work, but they are showing the same thing in > > both monitors. > > > > I have downloaded and installed the Nvidia GLX and kernel rmps and > > changed my device to 'nvidia' but when I ran startx only one monitor > > worked. The other monitor showed as a bunch of lines. I read in the > > known bugs section that Xinerama does not work with OpenGL. Does this > > mean that it will not work with the 'vesa' driver as well. Thanks for > > any information, and here is my XFree86-4 file (ps - I am using RH7.3): > > > > # XFree86 4.2.0 configuration generated by Xconfigurator 4.10.7 > > > > Section "ServerLayout" > > Identifier "XFree86 Configured" > > Screen 0 "Screen0" 0 0 > > Screen "Screen1" RightOf "Screen2" > > Option "Xinerama" "on" > > InputDevice"Mouse0" "CorePointer" > > InputDevice"Keyboard0" "CoreKeyboard" > > EndSection > > > > Section "Module" > > Load "dbe" # Double-buffering > > Load "GLcore" # OpenGL support > > Load "dri"# Direct rendering infrastructure > > Load "glx" # OpenGL X protocol interface > > Load "extmod" # Misc. required extensions > > Load "v4l" # Video4Linux > > # Load "record"# X event recorder > > # You only need the following two modules if you do not use xfs. > > # Load "freetype" # TrueType font handler > > # Load "type1" # Adobe Type 1 font handler > > EndSection > > > > Section "InputDevice" > > Identifier "Keyboard0" > > Driver "keyboard" > > Option "XkbLayout" "us" > > EndSection > > > > Section "InputDevice" > > Identifier "Mouse0" >
Re: [XFree86] Keyboard problems after upgrading to 4.3.0
On Thu, 20 Mar 2003, Jonas Bulow wrote: > No, I don't use my own xmodmap. xkeycaps does not exist. > What is similar to xkeycaps? I have no idea :) It's a front end to xmodmap, is all, and I find it handy. > How and where do I define AltGr to be a dead key? I have read the man > page for xmodmap and read about xkb on the web but I could not figure > out how to fix this bug. I don't know. I have used to have it defined as keycode 0x71 = Mode_switch addMod3= Mode_switch (which was the old default) but after deactivating my xmodmap file, the default is now: keycode 0x71 = ISO_Level3_ShiftMulti_key addMod5= ISO_Level3_Shift I'm gussing there's an xmodmap file _somewhere_ on your system that's still being run. I've attached an xmodmap file generated from the default settings on my machine. HTH ! ! This is an `xmodmap' input file for ! PC 105 key, wide Delete, tall Enter (XFree86; United Kingdom) keyboards. ! Automatically generated on Thu Mar 20 15:04:51 2003 by vivek with ! XKeyCaps 2.46; Copyright (c) 1999 Jamie Zawinski <[EMAIL PROTECTED]>. ! http://www.jwz.org/xkeycaps/ ! ! This file makes the following changes: ! ! The "F1 Help" key generates F1 and XF86_Switch_VT_1 ! The "F2" key generates F2 and XF86_Switch_VT_2 ! The "F3" key generates F3 and XF86_Switch_VT_3 ! The "F4" key generates F4 and XF86_Switch_VT_4 ! The "F5" key generates F5 and XF86_Switch_VT_5 ! The "F6" key generates F6 and XF86_Switch_VT_6 ! The "F7" key generates F7 and XF86_Switch_VT_7 ! The "F8" key generates F8 and XF86_Switch_VT_8 ! The "F9" key generates F9 and XF86_Switch_VT_9 ! The "F10" key generates F10 and XF86_Switch_VT_10 ! The "F11" key generates F11 and XF86_Switch_VT_11 ! The "F12" key generates F12 and XF86_Switch_VT_12 ! The "Print Scrn " key generates Print and Sys_Req ! The "Scroll Lock" key generates Scroll_Lock ! The "Pause Break" key generates Pause and Break ! The "¬ `" key generates grave and notsign ! The "Backspace" key generates BackSpace and Terminate_Server ! The "Num Lock" key generates Num_Lock and Pointer_EnableKeys, and the Mod2 modifier ! The "/" key generates KP_Divide and XF86_Ungrab ! The "*" key generates KP_Multiply and XF86_ClearGrab ! The "-" key generates KP_Subtract and XF86_Prev_VMode ! The "Tab" key generates Tab and ISO_Left_Tab ! The "7 Home" key generates KP_Home and KP_7 ! The "8 UpArrow" key generates KP_Up and KP_8 ! The "9 PgUp" key generates KP_Prior and KP_9 ! The "+" key generates KP_Add and XF86_Next_VMode ! The "4 LeftArrow" key generates KP_Left and KP_4 ! The "5" key generates KP_Begin and KP_5 ! The "6 RightArrow" key generates KP_Right and KP_6 ! The "1 End" key generates KP_End and KP_1 ! The "2 DownArrow" key generates KP_Down and KP_2 ! The "3 PgDn" key generates KP_Next and KP_3 ! The "=/+/" key generates Super_L ! The "Alt Gr" key generates ISO_Level3_Shift and Multi_key, and the Mod5 modifier ! The "=/+/" key generates Super_R ! The "0 Ins" key generates KP_Insert and KP_0 ! The ". Del" key generates KP_Delete and KP_Decimal keycode 0x09 = Escape keycode 0x43 = F1 XF86_Switch_VT_1 keycode 0x44 = F2 XF86_Switch_VT_2 keycode 0x45 = F3 XF86_Switch_VT_3 keycode 0x46 = F4 XF86_Switch_VT_4 keycode 0x47 = F5 XF86_Switch_VT_5 keycode 0x48 = F6 XF86_Switch_VT_6 keycode 0x49 = F7 XF86_Switch_VT_7 keycode 0x4A = F8 XF86_Switch_VT_8 keycode 0x4B = F9 XF86_Switch_VT_9 keycode 0x4C = F10 XF86_Switch_VT_10 keycode 0x5F = F11 XF86_Switch_VT_11 keycode 0x60 = F12 XF86_Switch_VT_12 keycode 0x6F = Print Sys_Req keycode 0x4E = Scroll_Lock keycode 0x6E = Pause Break keycode 0x31 = grave notsign keycode 0x0A = 1 exclam keycode 0x0B = 2 quotedbl keycode 0x0C = 3 sterling keycode 0x0D = 4 dollar keycode 0x0E = 5 percent keycode 0x0F = 6 asciicircum keycode 0x10 = 7 ampersand keycode 0x11 = 8 asterisk keycode 0x12 = 9 parenleft keycode 0x13 = 0 parenright keycode 0x14 = minus underscore keycode 0x15 = equal plus keycode 0x16 = BackSpace Terminate_Server keycode 0x6A = Insert keycode 0x61 = Home keycode 0x63 = Prior keycode 0x4D = Num_LockPointer_EnableKeys keycode 0x70 = KP_Divide XF86_Ungrab keycode 0x3F = KP_Multiply XF86_ClearGrab keycode 0x52 = KP_Subtract XF86_Prev_VMode keycode 0x17 = Tab ISO_Left_Tab keycode 0x18 = q Q keycode 0x19 = w W keycode 0x1A = e E keycode 0x1B = r R keycode 0x1C = t T keycode 0x1D = y Y keycode 0x1E = u U keycode 0x1F = i I keycode 0x20 = o O keycode 0x21 = p
Re: [XFree86] Keyboard problems after upgrading to 4.3.0
> The question is: how do I get back to the behaviour in 4.2 and earlier > where AltGr was a "dead" key? Do you run your own xmodmap command when logging in? Some of the keys don't behave quite the way they used to: The VT switch sequences, for example, now have an explicit X key symbol, which caught me out for a while: Also, try running xkeycaps or similar and see what it thinks your ALTGR key is set to. No, I don't use my own xmodmap. xkeycaps does not exist. What is similar to xkeycaps? How and where do I define AltGr to be a dead key? I have read the man page for xmodmap and read about xkb on the web but I could not figure out how to fix this bug. /jonas ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] mga 1600x1200 DVI [scanned]
On Thu, 20 Mar 2003, Thomas Winischhofer wrote:
> Ken Marx wrote:
> > Right. Veit also pointed out this limitation. Perhaps it's
> > *doable*, but just isn't supported? [EMAIL PROTECTED]
> > claims to have it working under linux; I know I have 1600x1200
> > working on 4.2.1 (Freebsd-4.7) for both the G400/550 on a
> > the viewsonic vp230mb (at 56hz v-refresh).
>
> I have to clarify/correct my original post:
>
> Single Link is not directly limited as regards resolution, but clock
> speed. Single link cards/cables have a max clock speed of 165Mhz. All
> above this needs dual link.
>
> 165Mhz should last for up to 1920x1080-60Hz or 1280x1024-85Hz.
Thanks for clarifying. On my other G550 I have a 1600x1024 monitor on what
appears to be a single-link cable. If I switch from DVI-digital to
DVI-analog *on the monitor* the picture goes away, so I was getting
very confused.
This is [EMAIL PROTECTED] with a 108MHz clock, well under the 165MHz limit.
> > The monitor reports it's in 'digitial' in the onscreen displays.
> > Plus, I'm using a (single link) DVI/D cable. I can't
> > even force it to analog on that cable via DigitalScreen{,1,2} "False".
> > (Could it still be fooling me and doing analog somehow?)
>
> Don't think so.
>
> > I really like your point about the dual-link card/cable.
> > I may go get a dual-link cable and see if it has an effect
> > on the Iiyama au4831d.
> > (And/or if Dr.Aitchison could report on his cable?)
I have pins 123..678 in each row, ie I am missing a 2x3 block in the
middle of an 8x3. I take it this is single-link.
My clock is 162MHz, which is just within the single-link limit.
Option NoDigitalScreen makes no difference, so maybe the option is
not available without mga_hal, and I am in fact using an analog signal.
I wouldn't trust the on screen display to report the signal type - it
reports "no signal - digital port" or "no signal - analog port" when I
switch to an input with no cable connected.
> Erm, I don't think this will help. Since Matrox always and everywhere
> states that the maximum resolution is 1280x1024 the card is very
> probably a single link card. Hence, a dual link cable will not help you
> either.
I should probably stop thinking about what my G550 will do on my
SGI 1600SW+MLA. 1600x1024 seems to break all the rules.
> > Lastly, how can I know if a card is dual/single link?
>
> Good question. Card manufacturers generally don't seem to like or use
> these terms. Typically, they target on Windows users who think in
> resolutions only.
>
> > p.s. Re: Veit's question about 60hz vs 56hz: I'm sure.
> > I went and double checked: at 60Hz I get a blank screen
> > for 1600x1200 and see this in the log:
>
> Look at the dotclock. If it exceeds 165Mhz, the DVI connection very
> probably will fail to be stable.
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] fatal server error: no screens found
Hi, I have a problem that I can not fix. After startx I get the message "fatal server error: no screens found". I think it is the video card, I found a help request of someone else that has the same problem as I have and he has the same video chip (http://forum.mlug.org.au/bbshowpost.php?bbsubject_id=177) My system is a pentium 166 mmx, and my video card is: vendor: sparkle (?) chip set: S3 Trio64V2/DX I use linux: 2.4.18-14 distribution: red hat 8.0, (7.3 gives the same problem) (See attached file: XF86Config.txt)(See attached file: XFree86.0.log) Do you know a work around for this? After serveral evenings I currently has given up trying and now think about bying a different video card. Joost ter Laak XF86Config.txt Description: Binary data XFree86.0.log Description: Binary data
Re: [XFree86] mga 1600x1200 DVI [scanned]
Ken Marx wrote:
> Right. Veit also pointed out this limitation. Perhaps it's
> *doable*, but just isn't supported? [EMAIL PROTECTED]
> claims to have it working under linux; I know I have 1600x1200
> working on 4.2.1 (Freebsd-4.7) for both the G400/550 on a
> the viewsonic vp230mb (at 56hz v-refresh).
I have to clarify/correct my original post:
Single Link is not directly limited as regards resolution, but clock
speed. Single link cards/cables have a max clock speed of 165Mhz. All
above this needs dual link.
165Mhz should last for up to 1920x1080-60Hz or 1280x1024-85Hz.
The monitor reports it's in 'digitial' in the onscreen displays.
Plus, I'm using a (single link) DVI/D cable. I can't
even force it to analog on that cable via DigitalScreen{,1,2} "False".
(Could it still be fooling me and doing analog somehow?)
Don't think so.
I really like your point about the dual-link card/cable.
I may go get a dual-link cable and see if it has an effect
on the Iiyama au4831d.
(And/or if Dr.Aitchison could report on his cable?)
Erm, I don't think this will help. Since Matrox always and everywhere
states that the maximum resolution is 1280x1024 the card is very
probably a single link card. Hence, a dual link cable will not help you
either.
Lastly, how can I know if a card is dual/single link?
Good question. Card manufacturers generally don't seem to like or use
these terms. Typically, they target on Windows users who think in
resolutions only.
p.s. Re: Veit's question about 60hz vs 56hz: I'm sure.
I went and double checked: at 60Hz I get a blank screen
for 1600x1200 and see this in the log:
Look at the dotclock. If it exceeds 165Mhz, the DVI connection very
probably will fail to be stable.
--
Thomas Winischhofer
Vienna/Austria
mailto:[EMAIL PROTECTED]http://www.winischhofer.net/
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Bug 16] New: XFree doesn't start if tv-output is connected, too.
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=16 Summary: XFree doesn't start if tv-output is connected, too. Product: Drivers Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ATI AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If there's a cable connected to tv output of my card (Hercules Radeon 8500LE), XFree does not start. Instead, there are following errors in the log file: "No valid mode found for this DFP/LCD" and "(WW) RADEON(0): Valid modes must be between 320x200-0x0". I am not wanting/trying to use the TV-out, just the monitor. But I do want to have the TV-out plugged in so that I can use VESA modes to output to the TV as needed. I have tried various options (CrtScreen, nopanel_display, NoPanelDisplay, crt_screen.. there was some doubt about what was the correct form), and changing the driver name from 'ati' to 'radeon', but none of those help. The problem is both with XFree 4.3.0 drivers and the current ati.2-drivers. The problem has been verified ( http://sourceforge.net/mailarchive/forum.php?thread_id=1783158&forum_id=5014 ) - the only way to get anything work is to completely disconnect the tv-out. The problem would go away if the drivers would just ignore the presence of the tv-out, as it's not supported anyway, or by providing an option to provide the functionality. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] call for help
hi: I have problem startx ,call for your help,thanks IncrediMail - Email has finally evolved - Click Here XFree86.0.log Description: unknown/unknown
[XFree86] Help!!!
The Linux 7.3 I installed cannot detect my monitor, I have Philips 15" 105E12 monitor. Here's what happened, when the installation was just two clicks away, the installer told me to indicate the monitor model which is not available among the selection. So I just chosen Generic settings. When I restarted the pc, it just gone straight to command line. Then typed, Xconfigurator, I chose settings and even chose custom and entered the Horizontal and Vertical Sync Ranges, but it didn't work. The Xconfigurator infact probed my video card (NVIDIA Riva TNT/TNT2) and also prompted me if I would choose the monitor setting it has detected, 105E and ranges, but if the Xconfigurator test my settings, it just went blank (black) and the error message says that the configuration I entered are not correct. Please help. See also the XFree86.0.log below. Thank you. XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System(protocol Version 11, revision 0, vendor release 6600)Release Date: 23 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/)Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader 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: Wed Mar 19 20:27:48 2003(==) Using config file: "/etc/X11/XF86Config-4"(==) ServerLayout "XFree86 Configured"(**) |-->Screen "Screen0" (0)(**) | |-->Monitor "105E"(**) | |-->Device "RIVA TNT2"(**) |-->Input Device "Mouse0"(**) |-->Input Device "Keyboard0"(**) Option "XkbLayout" "us"(**) XKB: layout: "us"(==) Keyboard: CustomKeycode disabled(**) FontPath set to "unix/:7100"(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"(==) ModulePath set to "/usr/X11R6/lib/modules"(--) using VT number 7 (II) Open APM successful(II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3(II) Loader running on linux(II) LoadModule: "bitmap"(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a(II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3(II) Loading font Bitmap(II) LoadModule: "pcidata"(II) Loading /usr/X11R6/lib/modules/libpcidata.a(II) Module pcidata: vendor="The XFree86 Project" compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5(II) PCI: Probing config type using method 1(II) PCI: Config type is 1(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000(II) PCI: PCI scan (all values are in hex)(II) PCI: 00:00:0: chip 10b9,1647 card , rev 04 class 06,00,00 hdr 00(II) PCI: 00:01:0: chip 10b9,5247 card , rev 00 class 06,04,00 hdr 01(II) PCI: 00:02:0: chip 10b9,5237 card 10b9,5237 rev 03 class 0c,03,10 hdr 00(II) PCI: 00:04:0: chip 10b9,5229 card 10b9,5229 rev c4 class 01,01,8a hdr 00(II) PCI: 00:07:0: chip 10b9,1533 card 10b9,1533 rev 00 class 06,01,00 hdr 00(II) PCI: 00:0c:0: chip 127a,1025 card 127a,1025 rev 01 class 07,80,00 hdr 00(II) PCI: 00:0f:0: chip 13f6,0111 card 13f6,0111 rev 10 class 04,01,00 hdr 00(II) PCI: 00:11:0: chip 10b9,7101 card 10b9,7101 rev 00 class 06,80,00 hdr 00(II) PCI: 01:00:0: chip 10de,002a card , rev 15 class 03,00,00 hdr 00(II) PCI: End of PCI scan(II) LoadModule: "scanpci"(II) Loading /usr/X11R6/lib/modules/libscanpci.a(II) Module scanpci: vendor="The XFree86 Project" compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5(II) UnloadModule: "scanpci"(II) Unloading /usr/X11R6/lib/modules/libscanpci.a(II) Host-to-PCI bridge:(II) PCI-to-ISA bridge:(II) PCI-to-PCI bridge:(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set)(II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B](II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B](II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B](II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0e (VGA_EN is set)(II) Bus 1 I/O range:(II) Bus 1 non-prefetchable memory range: [0] -1 0xda00 - 0xdbff (0x200) MX[B](II) Bus 1 prefetchable memory range: [0] -1 0xd800 - 0xd9ff (0x200) MX[B](II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set)(II) Bus -1 I/O range:(II) Bus -1 non-prefetchable memory range:(II) Bus -1 prefetchable memory range:(--) PCI:*(1:0:0) NVidia unknown chipset (0x002a) rev 21, Mem @ 0xda00/24, 0xd800/25(II) Addressable bus resource ranges are [0] -1 0x - 0x (
[XFree86] [Bug 11] Display glitches on Radeon 7200 with version 4.1.0, 4.3.0
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=11 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] binding keyboard key presses to mouse buttons
hiya Im using XFree86 4.3 and i have have an A4TECH Optical GreatEye mouse it has 2 wheels, and i cant get the 2nd wheel to work for x axis scrolling (left and right) i figured it has 8 buttons... 2 buttons on the left the 1st wheel being 3 buttons, the other wheel being 2 buttons and then 2 buttons on the right so i added the following to my XF86Config-4: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device""/dev/psaux" Option "ZAxisMapping" "4 5 8 9" Option "Buttons" "9" Option "SampleRate""200" Option "Resolution""400" Option "Threshold" "0" EndSection i used xev to check what it was doing... and sure enough no matter what i set the 2nd buttons to the Option "ZAxisMapping" "4 5 8 9" set the keys acordingly, however i cant get it to scroll horizontaly, then i thought about mapping they keyboard arrow keys so it would scroll but i cant work out for the life of me how, i read the man pages for xmodmap etc.. but im just totaly lost and confused about this, so if anyone can help me get this setup so i can scroll left and right, it would be verry much aprreciated. thanks alot Bain ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Help please for SVGA setup (RH8.0)
Hi all, I've just installed RedHat 8.0 and there's a problem with the XFree86 setup. Essentially the problem is: - Checkered backgrounds for various windows (but not for all). It makes most of the apps such as OpenOffice basically unreadable. Gnome menu items are fine, but KDE are completely checkered except for the currently highlighted item. When I had RH7.1 (and also after updating this with the latest rpm available for that distribution from rpmfind.net) I had a very similar problem which was fixed by downloading & installing XFree86-SVGA-3.3.6-38.i386.rpm and consequently running "Xconfigurator --kickstart" as root and then rebooting. However, I can't seem to locate a similar package for the RH8.0 distribution. There's no similar package on the CDs, nor does a google search turn up anything. XFree86 (version 4.2.0) seems to be installed from the CD... I've tried various monitor configurations using the "Gnome Menu > System Settings > Display" tool to no avail. What can I do to set this all up properly? Thanks muchly... Here's my details: - The video card (the output from SuperProbe from when I had 7.1 installed)... root > SuperProbe First video: Super-VGA Chipset: Cirrus CL-GD5430/40 (PCI Probed) Memory: 2048 Kbytes (Huge!) RAMDAC: Cirrus Logic Built-in 15/16/24-bit DAC (with 6-bit wide loopkup tables (or in 6-bit mode)) - Monitor: Digital (PCXBV-YC) Specs: 38.10cm (15-inch, 14-inch max viewable non-glare, non-static) Active area: 28.45 x 21.34 cm (11.2 x 8.4 in) Video Signal: 0.7V p-p R, G, B color; separate Sync (+ve or -ve); 75 ohm TTL, composite sync or sync on Green HScanRate: 30-60KHz VScanRate: 50-110Hz Computer: AMD Athlon XP 1800+ MotherBoard: Gigabyte GA-7VAX1394 with regards, -- Lachlan Deck [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Bug 11] Display glitches on Radeon 7200 with version 4.1.0, 4.3.0
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=11 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-03-19 15:42 --- Created an attachment (id=3) Log file, as requested, w/o accel, HW cursor, GLX or DRI --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Bug 13] Display disturbances when accellerated
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=13 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 04:15 --- Please attach your /var/log/XFree86.0.log file. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] X window installion problems
Title: X window installion problems Dear sir, We fail to start X - window after finish install the NETBSD 1.5 and X-window 4.1. The window prompt error message: "Fatal server error: no screens found" Please advise how to solve this problems Attached pls find the error log for your investigate. Thanks a lot! <> Regards, Jerry XFree86.0.log Description: Binary data
[XFree86] [Bug 13] New: Display disturbances when accellerated
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=13 Summary: Display disturbances when accellerated Product: Drivers Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Trident AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm running XFree 4.3.0 (Gentoo compiled) on a BookPC (http://www.lex.com.tw/index1.htm), which has a CyberBlade 1i video chip. When I use the trident driver, no matter what video mode/bit depth I use, I get disturbances when the image changes, for example when I move the mouse. The disturbances look as if the signal to the monitor is distorted, with parts of scan lines being moved to the left or right for a fraction of a second. The best way to test this is on a "raw" X, where the speckled pattern seems to boost the effect. The weird thing is that this doesn't happen when I turn off accelleration, or use the vesa driver (which may be the same thing, although the vesa driver seems to pick better modes). Any ideas? --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86(TM) Bug Report] I upgraded today from RedHat Linux v6.1 to RedHat Linux v7.3. It seemed to go smoothly until I entered "startx" at the shell command line. I got a screen full of information, and I'm not sure how much of that information you need to see. The problem machine is not connected to the internet; for that reason, I could not do a 'cut-and-paste' of all the text.
You are using an X3.3.6 formated XF86Config with X 4.x You may have an XF86Config-4 or you should run Xconfigurator Lionel PS why did not you go to RH 8.0 while you were at it? --- Greg Baxter <[EMAIL PROTECTED]> wrote: > Regarding: I upgraded today from RedHat Linux v6.1 to RedHat Linux v7.3. It seemed > to go > smoothly until I entered "startx" at the shell command line. I got a screen full of > information, and I'm not sure how much of that information you need to see. The > problem > machine is not connected to the internet; for that reason, I could not do a > 'cut-and-paste' of > all the text. > Email: [EMAIL PROTECTED] > > XFree86 Version: XFree Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window > System > (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 > > OS: Red Hat Linux 7.3 (Build Operating System: Linux 2.4.17-0.13 smp i686 [ELF] > > Area: Xserver > > Server: XFree86 (The XFree86 4.x server) > > Video Card: > > The only thing I know for sure is that the video card is an ATI Rage Pro with 2 MB > of SGRAM > > Description: > > "Parse warning on line 74 of section Keyboard in file /etc/X11/XF86 config > Ignoring obsolete > keyword "LeftAlt"." (Next line): Parse error on line 74 of section Keyboard in file > /etc/X11/XF86 config "Meta" is not a valid keyword in this section. (Next line): > (EE) > Problem parsing the config file (Next line): Error from xf86HandleConfigFile( ) > (Next > line): Fatal server error: no screens found > > Repeat By: > > While at the command line of the shell, I type 'startx' (in an effort to bring up > the GUI). > That will result in a failure of the GUI to start. > > ___ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
