CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED]03/01/26 08:40:43 Log message: 788. Inform Render of laptop LCD color component order in Radeon driver (Keith Packard) Modified files: xc/programs/Xserver/hw/xfree86/common/: xf86Init.c xc/programs/Xserver/hw/xfree86/loader/: dixsym.c xc/programs/Xserver/hw/xfree86/drivers/ati/: radeon_driver.c xc/programs/Xserver/render/: picture.c Revision ChangesPath 3.194 +3 -2 xc/programs/Xserver/hw/xfree86/common/xf86Init.c 1.53 +3 -1 xc/programs/Xserver/hw/xfree86/loader/dixsym.c 1.81 +15 -1 xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 1.30 +3 -1 xc/programs/Xserver/render/picture.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xml-work (branch: trunk)
CVSROOT:/home/x-cvs Module name:xml-work Changes by: [EMAIL PROTECTED]03/01/26 14:09:06 Log message: 1) Add html.stylesheet entry to html/param.xsl to force inclusion and processing of css/XFree86.css at the browser. Modified files: xml-work/xml/docbook/XFree86/custom/html/: param.xsl Revision ChangesPath 1.3 +3 -1 xml-work/xml/docbook/XFree86/custom/html/param.xsl ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xml-work (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xml-work Changes by: [EMAIL PROTECTED]03/01/26 14:09:35 xml-work/css Update of /home/x-cvs/xml-work/css In directory public.xfree86.org:/tmp/cvs-serv20572/css Log Message: Directory /home/x-cvs/xml-work/css added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xml-work (branch: trunk)
CVSROOT:/home/x-cvs Module name:xml-work Changes by: [EMAIL PROTECTED]03/01/26 14:12:02 Log message: 1) Add css/XFree86.css to contain CSS stylesheet for processing at the browser. Added files: xml-work/css/: XFree86.css ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xml-work (branch: )
[EMAIL PROTECTED] CVSROOT:/home/x-cvs Module name:xml-work Changes by: [EMAIL PROTECTED]03/01/26 14:18:28 xml-work/figures/100dpi/callouts Update of /home/x-cvs/xml-work/figures/100dpi/callouts In directory public.xfree86.org:/tmp/cvs-serv88701/callouts Log Message: Directory /home/x-cvs/xml-work/figures/100dpi/callouts added to the repository ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xml-work (branch: trunk)
CVSROOT:/home/x-cvs Module name:xml-work Changes by: [EMAIL PROTECTED]03/01/26 15:10:46 Log message: 1) Additional graphics files for navigation, admonitions, etc. 2) Add .tif and .gif to files to be considered 'binary' Modified files: xml-work/figures/100dpi/: .cvswrappers Added files: xml-work/figures/100dpi/: blank.png caution.gif caution.tif draft.png home.gif home.png important.gif important.tif next.gif next.png note.gif note.tif prev.gif prev.png tip.gif tip.tif toc-blank.png toc-minus.png toc-plus.png up.gif up.png warning.gif warning.tif xml-work/figures/100dpi/callouts/: .cvswrappers 1.gif 1.png 10.gif 10.png 11.gif 11.png 12.gif 12.png 13.gif 13.png 14.gif 14.png 15.gif 15.png 2.gif 2.png 3.gif 3.png 4.gif 4.png 5.gif 5.png 6.gif 6.png 7.gif 7.png 8.gif 8.png 9.gif 9.png ChangeLog Revision ChangesPath 1.2 +2 -0 xml-work/figures/100dpi/.cvswrappers ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/01/26 16:01:44 Log message: 789. Fix bug in recognition of certain ix86 Host-to-PCI bridges (Marc La France). Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/hw/xfree86/os-support/bus/: ix86Pci.c Revision ChangesPath 3.2498+3 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG 1.18 +9 -6 xc/programs/Xserver/hw/xfree86/os-support/bus/ix86Pci.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: 4.2.99.4 Test report: Mouse protocol auto fails
On Sun, Jan 26, 2003 at 02:47:26AM -0500, Kevin Brosius wrote:
David Dawes wrote:
On Sat, Jan 25, 2003 at 03:21:10PM -0500, Kevin Brosius wrote:
For a previously working setup, mouse protocol auto no longer succeeds
in configuring the mouse, however it appears not to fail either, leaving
the server up with a non-working mouse pointer. I do not have
'AllowMouseOpenFail' set.
Could you try the attached patch, and let me know what happens. The
2nd hunk is the important one, and the problem there resulting on only
the first character of the PnP ID string being read.
Yes, that fixes it. Full pnp info is now printed in the log also (but
twice, why is that?)
The function that does all of that gets called twice for some reason:
if ((val = MouseGetSerialPnpProtocol(pInfo)) != PROT_UNKNOWN) {
if (val == MouseGetSerialPnpProtocol(pInfo))
return val;
}
I'm not sure why that is -- maybe there's a need to check that the
result is repeatable? Maybe Egbert can answer this, since he made
these changes. Whatever the reason, one copy of those messages
should be suppressed (or only printed at a higher logging verbosity
level).
David
--
David Dawes
Release Engineer/Architect The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
[Fonts] You Are Not Welcome Kampanyasý -Pasif Direniþ Baþlýyor
YOU ARE NOT WELCOME KAMPANYASI ! ABD BÜYÜKELÇÝLÝÐÝNE UYARI MEKTUBU ARABALARIMIZA KIRMIZI BEYAZ KURDELALAR SAVAÞA / YABANCI ASKERE HAYIR AFÝÞLERÝ ile PASÝF DÝRENÝÞ SÜRECÝ BAÞLIYOR Sayýn Türkiye Cumhuriyeti Vatandaþý, Ülkemiz Cumhuriyet tarihinin en kritik süreçlerinden birine girmiþtir. Coðrafi depremle baþlayýp, ekonomik ve ardýndan gelen siyasi depremlerle güçlenen süreç, vatanýmýzýn, bölge üzerinde gerçekleþtirilecek bir savaþ için bir uçak gemisine dönüþtürülmesi gerçeðini kapýmýza dayamýþtýr. Irak'ýn sadece bir ara durak olduðu bu geliþmeler zincirinin olasý aþamalarýndan biri, Türkiye'nin küresel güçler tarafýndan bir federasyona zorlanarak, bölünmeye çalýþýlmasý olacaktýr. Gelinen noktanýn vehameti; günü kurtarmaya yönelik politikalar üreten ve Türkiye'nin büyüklüðünü, gücünü idraktan yoksun, vatan topraklarýna rantý yüksek arazi muamelesi yapan kadrolarýn, en büyük müttefik olarak milleti deðil dýþ güçleri görmeleri nedeni ile artmaktadýr. Sizleri bu aþamada, ülkenin sahibi olarak en temel hakkýnýzý kullanmaya ve bu pasif direniþ sürecine, ABD Büyükelçiliði'ne bir uyarý mektubu (mektubun örneði - Türkçe ve Ýngilizce) atarak katkýda bulunmaya davet ediyoruz. Türkiye 2023'ün web adresinden atabileceðiniz bu mektupla, ABD nezdinde bütün küresel güçlere, bu planlarýnýn boþa çýkarýlacaðýný duyurmak mevcut sürecin ilk adýmý olacaktýr. Sitemiz aracýlýðý ile ayrýca Cumhurbaþkanýmýz, Baþbakanýmýz, Milletvekillerimiz ve Genelkurmay Baþkanýmýza da konu ile ilgili mektuplarý iletebilirsiniz. Arabalarýnýza takacaðýnýz kurdelalar, dükkanlarýnýzýn camlarýna asacaðýnýz afiþler, tepkimizi sürekli ve görünür kýlmanýn yöntemleri olacaktýr. Bu ülkenin sahipleri olarak, bu ülke üzerinden plan yapanlara, son uyarýnýzý yapýn ve pasif direniþ sürecini hep beraber baþlatalým. Saygýlar Türkiye2023
[XFree86] Re: ATI All-In-Wonder 128 (16 Mb) AGP again
On Sat, 25 Jan 2003, Lionel Lecoq wrote: Date: Sat, 25 Jan 2003 05:23:05 -0800 (PST) From: Lionel Lecoq [EMAIL PROTECTED] To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Subject: Re: ATI All-In-Wonder 128 (16 Mb) AGP again have you tried Driver ati see http://www.xfree86.org/current/Status6.html#6 Rage 128 hardware uses the r128 driver. The ati driver is merely a wrapper around all 3 of the ATI drivers for individual chip families, and is not itself a driver. The 3 ATI drivers are: atimisc - Mach64 and older hardware r128- All Rage 128 based chipsets radeon - All Radeon based chipsets including FireGL 7x00/8x00 Selecting the ati driver merely autodetects the card, then loads one of the 3 drivers listed above. In this case, the ati driver will detect a Rage 128 chip, and then load the r128 driver - which is identical to just specifiying the r128 driver in the first place. There seems to be a lot of misconception that ATI users can just try one of the other ATI drivers present if the official one for their chipset doesn't work properly for them. There is no benefit whatsoever to doing so however, and only one of the 3 drivers will work with a given ATI chip. Hope this clarifies things a bit. TTYL -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility)
On Sat, Jan 25, 2003 at 07:23:54PM -0800, Nathaniel Gray wrote: You said: I just built 4.2.99.4 from CVS on my Radeon 7500 Mobility laptop. Starting X yields a blank display and a locked keyboard. Attempting to kill X or shutdown the laptop via ssh results in a complete system lockup. I had a similar problem (same video card, 4.2.99.4 binary) that was caused by a mismatched radeon.o kernel module. I'm not sure if that's what's going wrong for you though. Building the module from the latest DRI CVS sources solved it, but there were other problems: I made doubly sure that I'm using the radeon.o built from the 4.2.99.4 DRM sources, so it doesn't seem to be that. Out of curiosity, since you also have a 7500 mobility, have you ever tried running it dual-head with an external monitor? I'm trying to make that happen and having problems: http://www.mail-archive.com/xfree86@xfree86.org/msg00947.html I've attached my XF86Config-4 with working Xinerama layout. To test this, do: startx -- -layout XineramaLayout This creates two 800x600 screens that are overlayed, but you can obviously change that. I used it for presentations on projectors before CloneMode was available. Thanks for answering, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Some Freetype Problem i think
Hi i've been doing a linux from scratch the last days and the only thing missing is XFree86 which i can't get to work properly. I've installed freetype-2.1.3 just the way as can be seen on this page: http://beyond.no.linuxfromscratch.org/view/cvs/x/freetype2.html and XFree-4.2.1 (4.2.0 sources + 4.2.1 Patch) via the following commands: patch -Np1 -i ../4.2.0-4.2.1.diff make World 21 | tee xfree-compile.log make install make install.man ln -sf /usr/X11R6/bin /usr/bin/X11 ln -sf /usr/X11R6/lib/X11 /usr/lib/X11 ln -sf /usr/X11R6/include/X11 /usr/include/X11 Then i ran 'XFree86 -configure', did some editing to the config and the XFree testserver works just fine, i can move the mouse, switch to console and back and exit it with CTRL+ALT+BACKSPACE. I copied the config to /etc/X11/XF86Config and typed 'startx'. After a few seconds i see a screen that looks like the testserver but it goes away within half a second. This is the Output i get: -- [root@loki ~]# startx net-tools 1.60 hostname 1.100 (2001-04-14) 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.20 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: Sun Jan 26 12:43:56 2003 (==) Using config file: /etc/X11/XF86Config xterm: relocation error: /usr/lib/libfreetype.so.6: undefined symbol: inflateInit2_ xterm: relocation error: /usr/lib/libfreetype.so.6: undefined symbol: inflateInit2_ waiting for X server to shut down .XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0 after 0 requests (0 known processed) with 0 events remaining. [root@loki ~]# -- This is my XF86Config: -- Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb ModulePath /usr/X11R6/lib/modules FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/CID/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ # FontPath /usr/X11R6/lib/X11/fonts/TTF/ EndSection Section Module Load extmod Load glx Load dri Load dbe Load record Load xtrap # Load dri-old.libdri # Load freetype Load speedo Load type1 EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/mouse EndSection Section Monitor #DisplaySize 270 200 # mm Identifier Monitor0 VendorName ___ ModelName279 Option DPMS 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 Dac6Bit # [bool] #Option Dac8Bit # [bool] #Option DMAForXv # [bool] #Option ForcePCIMode # [bool] #Option CCEPIOMode # [bool] #Option CCENoSecurity # [bool] #Option CCEusecTimeout # i #Option AGPMode # i #Option AGPSize # i #Option RingSize # i #Option BufferSize # i #Option Display # str #Option PanelWidth # i #Option PanelHeight # i #Option ProgramFPRegs # [bool] #Option UseFBDev # [bool] #Option VideoKey # i #Option ShowCache # [bool] Identifier Card0 Driver r128 VendorName ATI Technologies Inc BoardName Rage 128 RF/SG AGP BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 Defaultdepth 16 SubSection Display Depth 1 EndSubSection SubSection Display Depth 4 EndSubSection SubSection Display Depth 8 EndSubSection SubSection Display Depth 15 EndSubSection SubSection Display Depth 16 Modes 1024x768 EndSubSection SubSection Display Depth 24 EndSubSection SubSection Display Depth 32 EndSubSection EndSection
Re: [XFree86] HELP: StartX failure
download the following files from ftp://ftp.xfree86.org/pub/XFree86/snapshots/4.2.99.4/binaries/Linux-ix86-glibc22/ then, as root, run sh ./Xinstall.sh you should be able to use the default answer to all the questions you are asked during the install (jusr press return) Install README RELNOTES Xbin.tgz Xdoc.tgz Xetc.tgz Xf100.tgz Xfcyr.tgz Xfenc.tgz Xfnts.tgz Xfscl.tgz Xfsrv.tgz Xhtml.tgz Xinstall.sh Xjdoc.tgz Xlib.tgz Xman.tgz Xmod.tgz Xnest.tgz Xprog.tgz Xprt.tgz Xps.tgz Xvar.tgz Xvfb.tgz Xxserv.tgz extract K K wrote: Simon, I am a newbie on Linux. Could you tell me how to upgrade or simply a Linux distribution using the XF86. KK - Original Message - From: SimonWesterby To: [EMAIL PROTECTED] Sent: Sunday, January 26, 2003 11:59AM Subject: Re: [XFree86] HELP: StartXfailure Yes, you need a later version of XF86 ... http://www.mail-archive.com/xfree86@xfree86.org/msg00290.html Oryou could try it with the X Vesa drivers, but you would be limited in yourscreen resolution Try 4.2.99.4 (availablefrom ftp://ftp.xfree86.org/pub/XFree86/snapshots/4.2.99.4/binaries/Linux-ix86-glibc22/ ) KK wrote: I am using Intel D845GLAD motherboard to bring up X-Window using 'startx' but failed with the following error. Please help and advise how to overcome it. TIA.
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500Mobility)
On Sun, 2003-01-26 at 03:36, Charl P. Botha wrote: I just built 4.2.99.4 from CVS on my Radeon 7500 Mobility laptop. Starting X yields a blank display and a locked keyboard. Attempting to kill X or shutdown the laptop via ssh results in a complete system lockup. 4.2.99.3 works perfectly on the *exact* same configuration. I've attached my XFree86.0.log although it seems to be normal. [...] (WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d002d01 (WW) RADEON(0): Restoring CONFIG_MEMSIZE (0400), setting to 0400 Have you been following the discussion about this code? Do any of the workarounds suggested in that thread (about '7200 support') help? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] xinerama+ xine/quake3 and other applications can not run in fullscreen ?
hi xinerama works fine, just some applications wont run / no fullscreen mode. xine in full screen mode plays sound but no video, in the error mess it says that theres no Xv compactibility ??? i use an older s3 and a gf2 card, the s3 runs with the vesa driver, the gf2 with the actual nvidia.. whats wrong ? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] X-Server crashes when using OpenOffice
Dear sirs, I hope someone can help me. Whenever I use OpenOffice (Mandrake 9.0) my screen turns black and I can login again. I don't know why. What can be wrong. I have the same installation (Mandrake 9.0 with OpenOffice) on an other computer and there I have no problem at all. Is it my graphical card (Matrox)? I will attach a few logs. If you need more information, please ask me. I hope you will find the reason for this, it is very anoying. With regards, P. Woldering 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: Sun Jan 26 15:10:20 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 us_intl (**) XKB: layout: us_intl (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 = 0x80b0, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7190 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:04:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:04:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:04:3: chip 8086,7113 card , rev 02 class 06,80,00 hdr 00 (II) PCI: 00:0d:0: chip 1274,5000 card 4942,4c4c rev 01 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 102b,0525 card 102b,2179 rev 03 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: 0x88 (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xe080 - 0xe1ef (0x170) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xe1f0 - 0xe3ff (0x210) MX[B] (II) Bus -1: bridge is at (0:4:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 3, Mem @ 0xe200/25, 0xe100/14, 0xe080/23, BIOS @ 0xe1ff/16 (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
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility)
On Sun, Jan 26, 2003 at 02:50:22PM +0100, Michel Dänzer wrote: On Sun, 2003-01-26 at 03:36, Charl P. Botha wrote: I just built 4.2.99.4 from CVS on my Radeon 7500 Mobility laptop. Starting X yields a blank display and a locked keyboard. Attempting to kill X or shutdown the laptop via ssh results in a complete system lockup. 4.2.99.3 works perfectly on the *exact* same configuration. I've attached my XFree86.0.log although it seems to be normal. [...] (WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d002d01 (WW) RADEON(0): Restoring CONFIG_MEMSIZE (0400), setting to 0400 Have you been following the discussion about this code? Do any of the workarounds suggested in that thread (about '7200 support') help? Thanks for pointing this out Michel. I just tried the workaround on 4.2.99.4 as documented in http://www.mail-archive.com/xfree86@xfree86.org/msg00961.html by Hui. The MEM_CNTL and CONFIG_MEMSIZE warnings do not appear in my XFree86.0.log (attached) anymore, but I still get the same symptoms: black screen, dead keyboard, machine locks up completely if I attempt a shutdown via ssh. I have confirmed (again) that 4.2.99.3 works perfectly on the exact same configuration. Thanks, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.4 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 25 January 2003 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.21-pre3 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: Sun Jan 26 15:58:37 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout DefaultLayout (**) |--Screen Default Screen (0) (**) | |--Monitor Clevo 15in 1400x1050 (**) | |--Device ATI Radeon 7500 Mobility (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Synaptics (GPM) (**) |--Input Device USB Mouse (**) FontPath set to /usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,/usr/lib/X11/fonts/TrueType,/usr/lib/X11/fonts/TTF (==) 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.2.99.4, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1a30 card 1558,5600 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,2482 card 1558,5600 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2484 card 1558,5600 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev 42 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,248c card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,248a card 1558,5600 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,2483 card 1558,5600 rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2485 card 1558,5600 rev 02 class 04,01,00 hdr 00 (II) PCI: 00:1f:6: chip 8086,2486 card 1558,5600 rev 02 class 07,03,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4c57
[XFree86] 4.3.0 release date ? AND a Font problem too
Does anyone know if there's a proposed release date for 4.3.0 ? I'm currently using 4.2.99.4, but it stops KDM working (on My SUSe 8.0) and I don't think those nice people @ SUSe are Compiling versions of X unless its a Major release. Alos, after installing 4.2.99.3/4 some of my fonts seemt om be a bit messed up, Arial, Times New Roman are a couple. When you type lowecase abcdefghijklm it comes out as ABCDEFGHIJKLM and when uppercase characters it comes out as symbols A becomes ! Very odd, not all fonts are affected! ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Fwd: Help - Driver for optical Mouse with Whell??]
Please I nead a Help. I have buy a Optical mouse with Whell - PS2 and I dont find a good configuration to XF86Config-4 and mouseconfig. I have teste all drivers to PS2 in mouseconfig and restart the Linux and the Whell dont operate. I use Linux Red Hat 7.3 and KDE3. Best reguards. Ronny Kraus. Brazil ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [Fwd: Help - Driver for optical Mouse with Whell??]
hi! I have buy a Optical mouse with Whell - PS2 and I dont find a good configuration to XF86Config-4 and mouseconfig. edit your XF86Config-4 like this: Section InputDevice Identifier Mouse1 Driver mouse Option Protocol imps/2 #standard ps2 protocol Option Device /dev/psaux Option ZAxisMapping 4 5 #for your wheel EndSection i hope that did the trick :) Laci ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] no screens found
Hi install FreeBSD 5 Please help me with this Error Ali Fatal server error:no screens foundWhen reporting a problem related to a server crash, please sendthe full server output, not just the last messages.This can be found in the log file "/var/log/XFree86.0.log".
Re: [XFree86] Reporting display problems with XFree86 4.2
On Thu, 23 Jan 2003, Philip Pawley wrote: I've been a long time getting around to reporting this problem , sorry. I'm having this display problem with several Linux distributions that include Xree86 version 4.2. I have not had the problem with earlier versions of XFree86. THE PROBLEM The whole screen has lots of 1px colored horizontal lines, that sometimes make it impossible to read the screen. I enclose a screen-shot (though the problem is often much more severe than you see here). snip Hi Phillip, this message is going to sound more negative than I want it to, but there's no way around it: please don't send HUGE attachments, like the circa 400kb PNG that you attached with this mail, to a mailing list. Everyone on the list gets a copy! Many people, such as myself, on these lists are using 56k modems and have limited space in our mail accounts. A massive mail like the one that you sent can really mess things up in terms of download times. That said, I hope you get some help with your problem, and thanks for sharing the bug report. Best wishes, Oisin Feeley ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility)
- Original Message - From: Charl P. Botha [EMAIL PROTECTED] To: Michel Dänzer [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, January 26, 2003 7:03 AM Subject: Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility) On Sun, Jan 26, 2003 at 02:50:22PM +0100, Michel Dänzer wrote: On Sun, 2003-01-26 at 03:36, Charl P. Botha wrote: I just built 4.2.99.4 from CVS on my Radeon 7500 Mobility laptop. Starting X yields a blank display and a locked keyboard. Attempting to kill X or shutdown the laptop via ssh results in a complete system lockup. 4.2.99.3 works perfectly on the *exact* same configuration. I've attached my XFree86.0.log although it seems to be normal. [...] (WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d002d01 (WW) RADEON(0): Restoring CONFIG_MEMSIZE (0400), setting to 0400 Have you been following the discussion about this code? Do any of the workarounds suggested in that thread (about '7200 support') help? Thanks for pointing this out Michel. I just tried the workaround on 4.2.99.4 as documented in http://www.mail-archive.com/xfree86@xfree86.org/msg00961.html by Hui. The MEM_CNTL and CONFIG_MEMSIZE warnings do not appear in my XFree86.0.log (attached) anymore, but I still get the same symptoms: black screen, dead keyboard, machine locks up completely if I attempt a shutdown via ssh. I have confirmed (again) that 4.2.99.3 works perfectly on the exact same configuration. MEM_CNTL problem shouldn't cause machine to lock up. To narrow down your problem, as Michel suggested, can you disable DRI to see if the lockup still happens? Hui Thanks, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Please Help-URGENT
Hi, I am getting the fatal IO error 104 (Connection reset by peer) on X server ":0.0" I am attaching the XF86Config-4 file and the log file. Please advise as to what to do. Thanks Karthik.Swaminathan, Karthikeyan You deserve what you get; You get what you deserve --ExperienceDo you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now # File generated by anaconda. Section ServerLayout Identifier Anaconda Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. FontPath unix/:7100 EndSection Section Module Load GLcore Load dbe Load extmod Load fbdevhw Load dri Load glx Load record Load freetype Load type1 EndSection Section InputDevice Identifier Keyboard0 Driver keyboard # Option AutoRepeat500 5 # when using XQUEUE, comment out the above line, and uncomment the # following line # Option Protocol Xqueue # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option Xleds 1 2 3 # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option XkbModel pc102 # If you have a US Microsoft Natural keyboard, you can use: # Option XkbModel microsoft # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option XkbLayout de # or: # Option XkbLayout de # Option XkbVariantnodeadkeys # # If you'd like to switch the positions of your capslock and # control keys, use: # Option XkbOptionsctrl:nocaps Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us #Option XkbVariant #Option XkbOptions EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/psaux Option ZAxisMapping 4 5 Option Emulate3Buttons yes EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync 30-70 VertRefresh 50-160 Option dpms # -- 1400x1050 -- # 1400x1050 @ 60Hz, 65.8 kHz hsync Modeline 1400x1050 129 1400 1464 1656 1960 1050 1051 1054 1100 +HSync +VSync # 1400x1050 @ 70Hz, 76.8 kHz hsync Modeline 1400x1050 151 1400 1464 1656 1960 1050 1051 1054 1100 +HSync +VSync # 1400x1050 @ 75Hz, 82.3 kHz hsync Modeline 1400x1050 162 1400 1464 1656 1960 1050 1051 1054 1100 +HSync +VSync # 1400x1050 @ 85Hz, 93.2 kHz hsync Modeline 1400x1050 184 1400 1464 1656 1960 1050 1051 1054 1100 +HSync +VSync EndSection Section Device # no known options Identifier Trident CyberBladeXP Driver trident VendorName Trident CyberBladeXP BoardName Trident CyberBladeXP #BusID EndSection Section Screen Identifier Screen0 Device Trident CyberBladeXP Monitor Monitor0 DefaultDepth24 Subsection Display Depth 24 Modes 1024x768 1024x768 EndSubsection EndSection Section DRI Mode 0666 EndSection XFree86.0.log Description: XFree86.0.log
Re: [XFree86] xinerama+ xine/quake3 and other applications can notrun in full screen ?
Hi, julius wrote: hi xinerama works fine, just some applications wont run / no fullscreen mode. xine in full screen mode plays sound but no video, in the error mess it says that theres no Xv compactibility ??? i use an older s3 and a gf2 card, the s3 runs with the vesa driver, the gf2 with the actual nvidia.. whats wrong ? As far as I know xinerama isn't compatible with Xv or DRI, take a look at: http://www.debianplanet.org/node.php?id=256 Best Regards Hans Öfverbeck ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility)
On Sun, Jan 26, 2003 at 01:23:47PM -0800, hy0 wrote: On Sun, Jan 26, 2003 at 02:50:22PM +0100, Michel Dänzer wrote: On Sun, 2003-01-26 at 03:36, Charl P. Botha wrote: I just built 4.2.99.4 from CVS on my Radeon 7500 Mobility laptop. Starting X yields a blank display and a locked keyboard. Attempting to kill X or shutdown the laptop via ssh results in a complete system lockup. 4.2.99.3 works perfectly on the *exact* same configuration. I've attached my XFree86.0.log although it seems to be normal. [...] (WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d002d01 (WW) RADEON(0): Restoring CONFIG_MEMSIZE (0400), setting to 0400 Have you been following the discussion about this code? Do any of the workarounds suggested in that thread (about '7200 support') help? Thanks for pointing this out Michel. I just tried the workaround on 4.2.99.4 as documented in http://www.mail-archive.com/xfree86@xfree86.org/msg00961.html by Hui. The MEM_CNTL and CONFIG_MEMSIZE warnings do not appear in my XFree86.0.log (attached) anymore, but I still get the same symptoms: black screen, dead keyboard, machine locks up completely if I attempt a shutdown via ssh. I have confirmed (again) that 4.2.99.3 works perfectly on the exact same configuration. MEM_CNTL problem shouldn't cause machine to lock up. To narrow down your problem, as Michel suggested, can you disable DRI to see if the lockup still happens? I did try with DRI disabled. In that case, X still starts up with a blank screen and a locked keyboard, but at least I can ssh in to the laptop and kill X and/or shutdown the machine. The text display is never recovered. I have attached the log of X running with DRI disabled. Thanks, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.4 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 20 January 2003 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.7-10custom 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: Sun Jan 26 20:00:31 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout DefaultLayout (**) |--Screen Default Screen (0) (**) | |--Monitor Clevo 15in 1400x1050 (**) | |--Device ATI Radeon 7500 Mobility (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Synaptics (GPM) (**) |--Input Device USB Mouse (**) FontPath set to /usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,/usr/lib/X11/fonts/TrueType,/usr/lib/X11/fonts/TTF (==) 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.2.99.4, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.99.4, 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 = 0x80b4, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1a30 card 1558,5600 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,2482 card 1558,5600 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip
Re: [XFree86] Problems with aoc monitor
Nicolas Bardier wrote: I don understand clearly, it is a monitor problem or a driver problem? under Windows 98 at 1024x768 it works quite fine IMHO, there is a world of difference between fine and quite fine. But, if it's actually fine under Windows and if I understand right your description of artifacts then blame the X drivers. Try lowering vertical refresh rate a bit perhaps (xvidtune). ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Unsubscribe
http://XFree86.Org/mailman/listinfo/xfree86 _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X-Server crashes when using OpenOffice
On 26 Jan 2003, Anja Tekelenburg wrote: Dear sirs, I hope someone can help me. Whenever I use OpenOffice (Mandrake 9.0) my screen turns black and I can login again. I don't know why. What can be wrong. I have the same installation (Mandrake 9.0 with OpenOffice) on an other computer and there I have no problem at all. Is it my graphical card (Matrox)? I will attach a few logs. If you need more information, please ask me. I hope you will find the reason for this, it is very anoying. My guess is that it's a problem with the font server. Try removing the unix font path in the XF86Config and just having the explict font paths, eg. FontPath /usr/X11R6/lib/X11/fonts/misc:unscaled FontPath /usr/X11R6/lib/X11/fonts/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1 FontPath /usr/X11R6/lib/X11/fonts/Speedo so that the font server won't get used. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Reporting display problems with XFree86 4.2
This will be fixed in 4.3. If you want a working driver for 4.2, go to www.winischhofer.net/linuxsisvga.shtml Thomas Philip Pawley wrote: I've been a long time getting around to reporting this problem , sorry. I'm having this display problem with several Linux distributions that include Xree86 version 4.2. I have not had the problem with earlier versions of XFree86. THE PROBLEM The whole screen has lots of 1px colored horizontal lines, that sometimes make it impossible to read the screen. I enclose a screen-shot (though the problem is often much more severe than you see here). WHEN IT OCCURS NEVER IN: RedHat 6.2 RedHat 7.2 (Xfree86 4.1.0) Mandrake 8.2 when I choose the Xfree86 3.3.6 option ALWAYS IN: Mandrake 8.2 when I choose the Xfree86 4.2.0 option RedHat 7.3 (Xfree86 4.2.0) RedHat 8.0 (Xfree86 4.2.0) RedHat beta 8.0.92 - Phoebe (XFree86 4.2.99) In RedHat 7.3, the trouble only starts after the first boot. In RH 8.0 it's there in the installation GUI as well. MY COMPUTER My display is a SiS620 with a MAG D510 monitor I have an Intel PII 350MHz processor I have 280MB RAM (32+128+128-8) As requested, I append the XFree86.0.log for RedHat 8.0.92 (Phoebe) This is the test version I currently have installed. (My working version is RedHat 7.2). If you need further information about my set-up or would like me to do any further tests (including re-installing any of the OS versions), let me know. I hope you find this helpful. Please keep up the good work. All the best, Philip Pawley -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] trident blade 3d mouse sync problems?
Your fix for the mouse works great - a big thanks for that. I was wondering if there was a way to donate to whomever is working on better support (if anyone is) for my chipset? I don't have time to get involved in the coding but I'd be glad to donate a few bucks towards whomever is getting the job done. Thanks. I have a FIC mini-itx (933Mhz, 256Mb ram) mobo with a Trident Blade 3D video chipset and am running RedHat Linux 7.3 fully updated and seems to be running XFree86 4.2.0-8. I seem to be having a video glitch related to the mouse. Seemingly at random times the mouse cursor goes out of sync with the rest of the screen. It is still functional but appears half an inch to the right of what it is acting on. Now and then it fixes itself without help but usually a reboot is required to fix it. Restarting X or the console mouse server seems to have no effect. It's a bug in the chip. Specify Option swcursor for now. Also is it possible to use 3D accelleration and direct rendering with this card yet? If so could someone point me to info on setting that up? I get reasonable enough performance to play DVD's but even old 3D games that work well under Windows are incredibly slow in Linux. Not sure if that is a problem with my X config or a WineX issue. No 3D acceleration for Trident chipsets yet. Alan. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] From 4.2.99.3 to 4.2.99.4 - unlike so many messages I've seen ...
This mail, I suppose, will be quite unlike so many what we've seen on this list. I have to thank the creators of XFree86, for me it works like a dream - no lag, no glitches. Sort of an use log: I used 4.0.x for quite some time. It had some nasty memory bug, cuz over time it had hogged about 700 MB of resources to itself - and thus it had to be brought down periodically. Then I went for 4.2.99.3. Worked just perfect, and that funky memory problem disappeared - after 3 days uptime, the memory use is 15 Megs RSS and 84 cached. But, for some reason 4.2.99.3 refused to give me a vertical slash from keyboard... Now I've been running 4.2.99.4 for a couple days straight -- everything (literally everything) works perfect. No memory hogging, no missing keys, no unusual behaviour. And the installation was simply marvelous - just answer a couple questions and voilá, X is new. Thanks people! =) --- Jas ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Problem with switching from 1400x1050 to 1024x768
Hi! I got a strange problem I hope one of you could help me with. Basically it is problem with switching with Ctrl+ and Ctrl- from normal 1400x1050 resolution to 1024x768 or any other lower resolution. When I swtich - instead of screen - I see something smaller, looking like a screen but with all pixels in row x shifted right or left by 2*x or more . So speaking plainly the screen is very, very skewed - to the point it is unusable. When I run Xconfigure and switch to pure 1024x768 mode - everything is fine. I am also able to run a separate Xserver with different layout and it works then but I would like to be able to switch WithCtrl-+ My enviroment: HP Pavilion with ALI 1535 chipset with built-in ATI IGP 340M graphics chipset which supposed to be similar to mibility M-6 or M-7. I run it normally in 1400x1050 VESA. With the following ModeLine: ModeLine 1400x1050 107.85 1400 1448 1500 2000 1050 1058 1070 1150 For 1024x768 no ModeLine is needed. Screen is 1400x1050 laptop panel. Could someone, please, help me ? BR, Jacek -- Jacek Pliszka [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Help Please
Hello Guys I am just starting out on this Linux journey and are having problems getting the X Server started. I have run the xf86config a number of times, but with no success. The machine I am trying to run Red Hat V8 on is a Pentium MMX machine. It is a HP Vectra VE with a Dell E551 Monitor, and a S3 Trio64V2/DX graphics adapter. I have attached the error log for your perusal. Kind regards XFree86.0.log James Durand NMSCom Tel: +27-11-789-3555 Mobile: +27-83-453-5159 *** Please note that this eMail, and the contents thereof, are subject to the NMSCom disclaimer. If you wish to receive or view the full disclaimer by return eMail, please send an eMail to [EMAIL PROTECTED] You can also view the disclaimer by clicking on WWW.NMSCom.net or paste the URL into your browser. *** XFree86.0.log Description: Binary data
Re: [XFree86] Re: ATI All-In-Wonder 128 (16 Mb) AGP again
Thanks, I was wondering what had happened to those drivers... Now I realise that they are still there just hidden. Lionel --- Mike A. Harris [EMAIL PROTECTED] wrote: On Sat, 25 Jan 2003, Lionel Lecoq wrote: Date: Sat, 25 Jan 2003 05:23:05 -0800 (PST) From: Lionel Lecoq [EMAIL PROTECTED] To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Subject: Re: ATI All-In-Wonder 128 (16 Mb) AGP again have you tried Driver ati see http://www.xfree86.org/current/Status6.html#6 Rage 128 hardware uses the r128 driver. The ati driver is merely a wrapper around all 3 of the ATI drivers for individual chip families, and is not itself a driver. The 3 ATI drivers are: atimisc - Mach64 and older hardware r128 - All Rage 128 based chipsets radeon- All Radeon based chipsets including FireGL 7x00/8x00 Selecting the ati driver merely autodetects the card, then loads one of the 3 drivers listed above. In this case, the ati driver will detect a Rage 128 chip, and then load the r128 driver - which is identical to just specifiying the r128 driver in the first place. There seems to be a lot of misconception that ATI users can just try one of the other ATI drivers present if the official one for their chipset doesn't work properly for them. There is no benefit whatsoever to doing so however, and only one of the 3 drivers will work with a given ATI chip. Hope this clarifies things a bit. TTYL -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
