From vpr_mam at lycos.com Thu Feb 19 03:59:57 2004 From: vpr_mam at lycos.com (Veera Partha) Date: Wed, 18 Feb 2004 22:59:57 -0500 Subject: Xfree86 4.3 Message-ID: Hi All, Resending this. Awaiting your reply please. Thanks. -- --------- Original Message --------- DATE: Thu, 12 Feb 2004 03:49:07 From: "Veera Partha" To: xfree86-list at redhat.com Cc: >Hi all, > >I have Advanced server 2.1 installation. Since the current video card(Intel extreme graphics- D845 GVSR mother board) is not supported by >the xFree86 that comes with AS 2.1, i want to upgrade to xFree 4.3. >I checked the Xfree86.org. > >Need help on the following: > >checked http://ftp.xfree86.org/pub/XFree86/4.3.0/binaries/ for the binaries to be downloaded. > >From which one i need to download the binaries ? >Linux-axp-glibc22/ 08-Mar-2003 05:57 > Linux-ix86-glibc21/ 08-Mar-2003 05:56 > Linux-ix86-glibc22/ 27-Aug-2003 19:25 > Linux-ix86-glibc23/ 27-Aug-2003 19:18 > >Request you to confirm. > >My current installation is Redhat AS 2.1. Also please confirm which step i need to follow for the new Xfree86 installation from below? > >1. Installing XFree86 4.3.0 using the Xinstall.sh script > >2. Installing XFree86 4.3.0 manually > A new installation > Installing over an old installation > >Thanks. > > >____________________________________________________________ >Find what you are looking for with the Lycos Yellow Pages >http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 > ____________________________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 From rozio at mundo-r.com Thu Feb 19 10:27:30 2004 From: rozio at mundo-r.com (Rocio Alfonso Pita) Date: Thu, 19 Feb 2004 11:27:30 +0100 Subject: Fwd: Re: Display is fuzzy with ATI radeon 9000 pro Message-ID: <200402191127.30884.rozio@mundo-r.com> I found solution: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114158 thanks for your help. rozio ---------- Mensaje reenviado ---------- Subject: Re: Display is fuzzy with ATI radeon 9000 pro Date: Jueves, 5 de Febrero de 2004 09:37 From: Rocio Alfonso Pita To: xfree86-list at redhat.com, Alex Deucher hello, ATI drivers with I'd probed are ATI-4.3.0-13.i386.tar.gz (from 4.2.0-14 I test with all) of gatos.sf.net. yesterday I'd proved the follow: - a knopix and with driver vesa image is correct. - when I prove with my fedora (and RH 9) with vesa drivers, image is fuzzy too. - if I prove with ati drivers (from gatos) the X server don't start. I adjust monitor frecuency, test with autoconfiguration, without second busID... all fails. I think that exists anything in XFree86 programation on Red Hat (fedora) that with my hardware configuration fails. I'd tested a screenshot of my fuzzy image in my (little) win98 in the same computer and image is perfect with that hardware. thanks and regards, rozio A lo que comentaba Alex Deucher el Mi?rcoles, 4 de Febrero de 2004 16:45: > --- Rocio Alfonso Pita wrote: > > hello, > > > > I have a problem with my ati videocard. The problem is that image > > is > > very fuzzy with configuration detected by fedora. If I download > > latest > > ati drivers, and I configure XF86Config with 2 device for videocard > > with > > buisID, I obtain this error: > > > > (WW) RADEON: No matching Device section for instance (BusID > > PCI:1:0:1) found > > (EE) RADEON(0): No valid mode found for this DFP/LCD > > (EE) Screen(s) found, but none have a usable configuration. > > > > Fatal server error: > > no screens found > > Do you mean the latest xfree86 radeon driver or the latest ati binary > driver? Also the secondary PCI id (PCI:1:0:1) is just a place holder > for the windows drivers. If you want to use singlehead or dualhead, > you will need the primary PCI id (PCI:1:0:0) only. if you were only > using the primary ID then you can ignore the warning. I believe that > was fixed in cvs (all secondary ID's were removed from the radeon > driver so it wouldn't try and claim them). > > Alex > > > I open a bug in bugzilla about fedora drivers for ati and > > configuration detected. This is: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114158 > > > > I hope that with yours help I can solve my problem. > > > > Thanks and regards, > > rozio ------------------------------------------------------- From Simon.Greaves at usp.ac.fj Wed Feb 25 22:05:24 2004 From: Simon.Greaves at usp.ac.fj (Simon Greaves) Date: Thu, 26 Feb 2004 10:05:24 +1200 Subject: gdm uses wrong vt after disk upgrade Message-ID: <20040225220524.GM26699@usp.ac.fj> Hi, Using RH9+updates, P4/generic nVidia GeForce2 card, nVidia drivers. All was working well, then I installed a larger HDD (old: Seagate 40GB IDE UDMA100, new: Seagate 80GB IDE UDMA100). I just partitioned the new disk, copied filesystems over using tar (from CD rescue environment), installed grub, removed old drive, booted, all seemed ok, shutdown, went to bed. Next day, booting to runlevel 5, all looked well up to the point where gdm fires up, then the screen goes black, can't switch VT's, though system will reboot if I hit Ctrl-Alt-Del. I then bring it up in runlevel 3 and check the XFree86.0.log file and it says the X server was told to start on vt8 (should be 7). Having booted to runlevel 3, if I do a 'startx' it works, then a telinit 5 also works. At this point, a complete reboot usually does the right thing, but if I shut it down and try again it usually fails. So, likelyhood is I stuffed something up when I moved from the old disk to the new one, though everything else _seems_ ok, and when X works, it seems to work properly... any suggestions? Thanks, Simon -- Simon Greaves Voice: +679 3212114 Systems & Networks Fax: +679 3304089 ITS, USP, Suva Email: Simon.Greaves at usp.ac.fj Fiji From mharris at www.linux.org.uk Thu Feb 26 00:04:23 2004 From: mharris at www.linux.org.uk (Mike A. Harris) Date: Wed, 25 Feb 2004 19:04:23 -0500 (EST) Subject: gdm uses wrong vt after disk upgrade In-Reply-To: <20040225220524.GM26699@usp.ac.fj> References: <20040225220524.GM26699@usp.ac.fj> Message-ID: On Thu, 26 Feb 2004, Simon Greaves wrote: >Using RH9+updates, P4/generic nVidia GeForce2 card, nVidia >drivers. All was working well, then I installed a larger HDD (old: >Seagate 40GB IDE UDMA100, new: Seagate 80GB IDE UDMA100). I just >partitioned the new disk, copied filesystems over using tar (from CD >rescue environment), installed grub, removed old drive, booted, all >seemed ok, shutdown, went to bed. > >Next day, booting to runlevel 5, all looked well up to the point where >gdm fires up, then the screen goes black, can't switch VT's, though >system will reboot if I hit Ctrl-Alt-Del. I then bring it up in >runlevel 3 and check the XFree86.0.log file and it says the X server >was told to start on vt8 (should be 7). The X server starts up by default on "the next unused VT". The only way it would start on vt8 would be if either: 1) There was already an X server or other process running on VT7 or 2) You pass the X server the "vtXX" commandline argument or 3) You have more than the 6 default tty's configured in /etc/inittab >Having booted to runlevel 3, if I do a 'startx' it works, then a >telinit 5 also works. At this point, a complete reboot usually does >the right thing, but if I shut it down and try again it usually >fails. > >So, likelyhood is I stuffed something up when I moved from the old >disk to the new one, though everything else _seems_ ok, and when X >works, it seems to work properly... any suggestions? Try removing the "nvidia" driver, which is unsupported, and using the "nv" driver instead. You need to reboot your system completely and ensure that the proprietary driver does not get loaded since boot time, or else the video card won't be in a power-on state for clean testing results. -- Mike A. Harris From vpr_mam at lycos.com Thu Feb 26 11:41:57 2004 From: vpr_mam at lycos.com (Veera Partha) Date: Thu, 26 Feb 2004 06:41:57 -0500 Subject: Downloading the XFree86 4.3.0 binaries Message-ID: Hi All, I have installed linux in my PC. version is Redhat advanced server 2.1. Can you please confirm which set of XFree86 4.3.0 binaries need to be downloaded from http://ftp.xfree86.org/pub/XFree86/4.3.0/binaries/ I need to upgrade the current Xfre86 that comes with AS 2.1. >From the above site, the binaries are organized by sub-directories which correspond to each of the OS/platforms for which binaries are provided. I need to download the binaries from one of the following directories corresponding to my os version: Linux-axp-glibc22/ Linux-ix86-glibc21/ Linux-ix86-glibc22/ Linux-ix86-glibc23/ >From which directory i need to download the binaries for my Redhat OS. Request you to cinfirm. Thanks. ____________________________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 From laurent.jean-rigaud at regis-dgac.net Thu Feb 26 12:43:31 2004 From: laurent.jean-rigaud at regis-dgac.net (laurent.jean-rigaud at regis-dgac.net) Date: Thu, 26 Feb 2004 13:43:31 +0100 Subject: Downloading the XFree86 4.3.0 binaries Message-ID: Normally, you should use Linux-ix86-glibc22 but it seems that in this case you loose RH support..... Officially you should update to 3.0 to have XFree86 4.3. From mharris at www.linux.org.uk Thu Feb 26 19:25:40 2004 From: mharris at www.linux.org.uk (Mike A. Harris) Date: Thu, 26 Feb 2004 14:25:40 -0500 (EST) Subject: Downloading the XFree86 4.3.0 binaries In-Reply-To: References: Message-ID: On Thu, 26 Feb 2004 laurent.jean-rigaud at regis-dgac.net wrote: >Normally, you should use Linux-ix86-glibc22 but it seems that in >this case you loose RH support..... Officially you should update >to 3.0 to have XFree86 4.3. Correct. Red Hat Enterprise Linux 2.1 customers can upgrade to Red Hat Enterprise Linux 3 via Red Hat Network for free, which is the highly recommended way to get XFree86 4.3.0 because: - Installing XFree86.org binary version of XFree86 on your system will make your system unsupported by Red Hat. - Installing the XFree86.org binary version of XFree86 will prevent you from being able to cleanly upgrade to a new OS release such as Red Hat Enterprise Linux 3 in the future, due to the different way in which the XFree86.org binaries are built and installed on the system by default conflicting with the way they are built and installed by most Linux distributions including Red Hat. -- Mike A. Harris From william.d.hamblen at dartmouth.edu Mon Mar 8 14:46:02 2004 From: william.d.hamblen at dartmouth.edu (William D. Hamblen) Date: Mon, 8 Mar 2004 09:46:02 -0500 (EST) Subject: Dual DVI success Message-ID: Hi everyone, I promised I would write back with the results of my attempt to assemble a RHEL3 system with two flat panels, both using DVI connections. So here it is. The short version: two Radeon 7000s (one AGP, one PCI), two Dell 1703FP 1280x1024 flat panels. Works great out of the box if you disable DRI in XF86Config. No artifacts, stable image, uniform color across both displays. Very nice. I ended up ordering a prebuilt system from a vendor we've used fairly often. It came with two 64MB Powercolor Radeon 7000 Multi-Display Edition video cards (Evil Wizard): one AGP and one PCI. The vendor picked the specific card - all I cared about is that they were Radeon 7000s with DVI (because they are cheap and have a PCI version). These cards also have a VGA connector and TV Out. lspci calls them 01:07.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] 02:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] I added two Dell 1703FP flat panels. These have DVI connectors and a native resolution of 1280x1024. I did the Redhat Enterprise Linux WS 3.0 installation myself. There was only one problem. After the installation finished, the system rebooted and the primary screen (only one is setup by the installer) went blank as X started. The system appeared to be completely hung. Nothing on any of the four video connectors (2 DVI, 2 VGA) and I couldn't switch to a virtual console (even once I bypassed the firstboot script and started "for real"). Yet, the monitor connected to the primary card's DVI output was reporting a 1280x1024, 60Hz signal. I should interrupt myself here to mention that the system came with an nForce2 based motherboard (ugh, my bad for not specifying) so I had no ethernet support to login remotely and see if the system was really alive. Unfortunately I did not think to save the XFree86 logs - but they looked normal to me. I did the RHEL WS installation several times (out of curiousity - at this point I knew what was wrong) to see if the installer would come up with something that worked with DRI. The first install was with both cards in place and the BIOS set to use the PCI card as primary. The second try was with just the AGP card (BIOS still set to PCI since I hadn't seen the option yet :-)). The third try was with just the AGP card and BIOS set to AGP. Those all hung in the same way after the initial reboot. I did a fourth installation with both cards installed and the BIOS still set to AGP. But right after the installation, and before the reboot, I switched to a virtual console and disabled DRI in XF86Config. It worked beautifully from there. I added the usual stuff to XF86Config and both screens look great, with DVI, but no DRI (which I do not care about in this application). I can send the XF86Config file to anyone who cares. I merely turned on Xinerama, added the second Device and Screen sections and inserted BusID lines. I hope this is helpful to someone. - Bill Hamblen From acosta at ar.microlink.com.br Mon Mar 8 16:53:40 2004 From: acosta at ar.microlink.com.br (Andre Costa) Date: Mon, 8 Mar 2004 13:53:40 -0300 Subject: Mouse stops working Message-ID: <20040308135340.53859628.acosta@ar.microlink.com.br> Hi, sometimes, mouse simply stops working with X. Everything else (eg. keyboard) keeps working. I have no choice (AFAIK) but shutdown X with CTRL+ALT+BACKSPACE, which sometimes makes me lose stuff I was doing. I use latest 4.3.0-55 packages for Fedora, with NVidia driver 5336. My mouse-related settings on XF86Config are: Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" # InputDevice "DevInputMice" "AlwaysCore" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/psaux" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" EndSection # Section "InputDevice" # If the normal CorePointer mouse is not a USB mouse then # this input device can be used in AlwaysCore mode to let you # also use USB mice at the same time. # Identifier "DevInputMice" # Driver "mouse" # Option "Protocol" "IMPS/2" # Option "Device" "/dev/input/mice" # Option "ZAxisMapping" "4 5" # Option "Emulate3Buttons" "no" # EndSection My mouse is an optical MS Intellimouse, attached do PS/2 port. The reported behavior happens either if I keep gpm running or not while on X./var/log/XFree86.0.log says: (II) XINPUT: Adding extended input device "DevInputMice" (type: MOUSE) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)(II) Mouse0: ps2EnableDataReporting: succeeded Any hints on what to do to narrow down the cause of the problem? Should I post this to NVIDIA ML? TIA Andre -- Andre Oliveira da Costa From mharris at redhat.com Tue Mar 9 02:01:43 2004 From: mharris at redhat.com (Mike A. Harris) Date: Mon, 8 Mar 2004 21:01:43 -0500 (EST) Subject: Freeglut 2.2.0 is now in Fedora devel tree - Request For Testers Message-ID: I have updated freeglut to version 2.2.0 in fedora-devel. The new version should be API and ABI compatible with glut 3.7 to the best of my knowledge, as that is one of the main goals of the freeglut project. When upgrading to these new freeglut packages, they will automatically obsolete and uninstall any "glut" and "glut-devel" package present on the system. The new packages have a virtual provides set for "glut = 3.7" and "glut-devel = 3.7" for rpm dependancy compatibility with rpms which may be installed already which require either of the two. I have done some preliminary testing already, however there are 3 levels of testing that need to be done. Please test as many of the following scenarios as you can: - Install binary software that is already linked dynamically to Mark Kilgard's GLUT (or install GLUT and build some GLUT applications). Then upgrade to freeglut, and run the existing GLUT applications. This tests ABI compatibility from glut->freeglut. - With freeglut and freeglut installed (which will remove glut and glut-devel automatically), rebuild some applications that use GLUT, so that they've linked against freeglut instead. Test them, and note any problems or incompatibilities. This tests API compatibility. Note that no modification to the application's source is necessary. - With applications linked to freeglut as per above, now remove freeglut with "rpm -e freeglut freeglut-devel --nodeps" and reinstall the original glut from RHL 9. Now run-test the GLUT apps. This tests freeglut->glut ABI compatibility. Some software which you may find useful for testing include Mesa-demos, and Really Slick Screensavers (rss). There are many other GLUT using apps out there as well, however Fedora Core itself has no dependancies on GLUT currently, so 3rd party software is required to do this testing. If possible, please perform the above testing if possible by using the Red Hat supplied Mesa OpenGL implementation which is included with XFree86, so that we can get adequate test coverage with Mesa libGL, and DRI drivers. If you are using proprietary drivers from Nvidia, ATI or another 3rd party, you would have to uninstall these drivers temporarily and reinstall the Fedora provided libGL, etc. so that we know what is being tested is what comes with the OS. It is also important however for people to test with proprietary libGL from Nvidia, ATI, etc. as well however, as that will give additional compatibility test coverage with alternative libGL implementations. Interestingly enough, one of the problems with Mark Kilgard's original GLUT, is that it has a bug in it which causes it to not work properly with Nvidia and other libGL implementations if it has been compiled with Mesa, because mesa implements some extensions which are not widely used, and are not present in all vendor's libGLs out there. Freeglut should not suffer from this limitation, and so it should work equally well with both Mesa libGL and with Nvidia/ATI/etc. libGL - at least in theory. If you encounter any API or ABI incompatibilities in the above testing, or any bugs/problems with the library itself, please report them to the upstream freeglut bug tracker on sourceforge, which is located at: http://sourceforge.net/tracker/?atid=101032&group_id=1032&func=browse If you report a bug there, feel free to also file a tracker bug in Red Hat bugzilla as well, with a URL pointing to the upstream bug report for me to track. I'll monitor the upstream report also. If you discover any problems with the RPM packaging of freeglut itself, please report the bug in Red Hat bugzilla instead of upstream. Thanks in advance for any testing. -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat From mharris at www.linux.org.uk Tue Mar 9 04:28:03 2004 From: mharris at www.linux.org.uk (Mike A. Harris) Date: Mon, 8 Mar 2004 23:28:03 -0500 (EST) Subject: Dual DVI success In-Reply-To: References: Message-ID: On Mon, 8 Mar 2004, William D. Hamblen wrote: >I promised I would write back with the results of my attempt to assemble a >RHEL3 system with two flat panels, both using DVI connections. So here it >is. > >The short version: two Radeon 7000s (one AGP, one PCI), two Dell 1703FP >1280x1024 flat panels. Works great out of the box if you disable DRI in >XF86Config. No artifacts, stable image, uniform color across both >displays. Very nice. > >I ended up ordering a prebuilt system from a vendor we've used fairly >often. It came with two 64MB Powercolor Radeon 7000 Multi-Display Edition >video cards (Evil Wizard): one AGP and one PCI. The vendor picked the >specific card - all I cared about is that they were Radeon 7000s with DVI >(because they are cheap and have a PCI version). These cards also have a >VGA connector and TV Out. lspci calls them > >01:07.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY >[Radeon 7000/VE] >02:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY >[Radeon 7000/VE] > >I added two Dell 1703FP flat panels. These have DVI connectors and a >native resolution of 1280x1024. > >I did the Redhat Enterprise Linux WS 3.0 installation myself. There was >only one problem. After the installation finished, the system rebooted >and the primary screen (only one is setup by the installer) went blank as >X started. The system appeared to be completely hung. Nothing on any of >the four video connectors (2 DVI, 2 VGA) and I couldn't switch to a >virtual console (even once I bypassed the firstboot script and started >"for real"). Yet, the monitor connected to the primary card's DVI output >was reporting a 1280x1024, 60Hz signal. > >I should interrupt myself here to mention that the system came with an >nForce2 based motherboard (ugh, my bad for not specifying) so I had no >ethernet support to login remotely and see if the system was really alive. >Unfortunately I did not think to save the XFree86 logs - but they looked >normal to me. > >I did the RHEL WS installation several times (out of curiousity - at this >point I knew what was wrong) to see if the installer would come up with >something that worked with DRI. The first install was with both cards in >place and the BIOS set to use the PCI card as primary. The second try was >with just the AGP card (BIOS still set to PCI since I hadn't seen the >option yet :-)). The third try was with just the AGP card and BIOS set to >AGP. > >Those all hung in the same way after the initial reboot. I did a fourth >installation with both cards installed and the BIOS still set to AGP. But >right after the installation, and before the reboot, I switched to a >virtual console and disabled DRI in XF86Config. It worked beautifully >from there. > >I added the usual stuff to XF86Config and both screens look great, with >DVI, but no DRI (which I do not care about in this application). I can >send the XF86Config file to anyone who cares. I merely turned on >Xinerama, added the second Device and Screen sections and inserted BusID >lines. > >I hope this is helpful to someone. Just as a point of reference, DRI is disabled if you are using multihead because DRI is not multihead compatible. So all multihead setups have DRI disabled wether or not Xinerama is being used, and also wether or not both heads are on one card or several. It is functionality that is just not implemented in XFree86 currently. Having said that, several drivers have had "merged framebuffer" support added to them in upstream development, and in a future OS release, mergedfb enabled drivers will support multihead+xinerama as well. Just thought I'd mention that so nobody wastes time trying to make DRI work with Xinerama. ;o) From mharris at www.linux.org.uk Tue Mar 9 05:02:54 2004 From: mharris at www.linux.org.uk (Mike A. Harris) Date: Tue, 9 Mar 2004 00:02:54 -0500 (EST) Subject: Mouse stops working In-Reply-To: <20040308135340.53859628.acosta@ar.microlink.com.br> References: <20040308135340.53859628.acosta@ar.microlink.com.br> Message-ID: On Mon, 8 Mar 2004, Andre Costa wrote: >sometimes, mouse simply stops working with X. Everything else (eg. >keyboard) keeps working. I have no choice (AFAIK) but shutdown X with >CTRL+ALT+BACKSPACE, which sometimes makes me lose stuff I was doing. > >I use latest 4.3.0-55 packages for Fedora, with NVidia driver 5336. My >mouse-related settings on XF86Config are: [SNIP] >My mouse is an optical MS Intellimouse, attached do PS/2 port. The >reported behavior happens either if I keep gpm running or not while on >X./var/log/XFree86.0.log says: > >(II) XINPUT: Adding extended input device "DevInputMice" (type: MOUSE) There are some faulty Microsoft Intellimice out there, which are just broken hardware. It is possible that you may have one of them, but I do not remember how to go about determining which ones are broken. Microsoft has some knowledgebase articles on this problem, and if I remember correctly, there is no easy way around the problem. However... you might not have the buggy M$ mouse either, it could be some other problem. I recommend disabling gpm entirely at boot time and rebooting without it running to see if that makes any difference. >(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: >Other)(II) Mouse0: ps2EnableDataReporting: succeeded Nvidia event handler? That's a new one to me. Perhaps Nvidia's video driver now has a built in mouse driver as well? ;o) >Any hints on what to do to narrow down the cause of the problem? Should >I post this to NVIDIA ML? I would recommend reinstalling XFree86 from the latest rpms available for the OS release you are using, and configure the "nv" driver, or "vesa" driver and try to reproduce the problem. If the problem is not reproduceable, then it may be possible that the nvidia driver is interfering with things, at which point you might want to try Nvidia's web forums in case someone is aware of problems like this caused by their driver. Hope this helps! Take care, TTYL From william.d.hamblen at dartmouth.edu Tue Mar 9 12:16:22 2004 From: william.d.hamblen at dartmouth.edu (William D. Hamblen) Date: Tue, 9 Mar 2004 07:16:22 -0500 (EST) Subject: Dual DVI success In-Reply-To: Message-ID: On Mon, 8 Mar 2004, Mike A. Harris wrote: > On Mon, 8 Mar 2004, William D. Hamblen wrote: > >The third try was with just the AGP card and BIOS set to AGP. > Just as a point of reference, DRI is disabled if you are using multihead > because DRI is not multihead compatible. So all multihead setups have > DRI disabled wether or not Xinerama is being used, and also wether or > not both heads are on one card or several. Yes, I knew that. That's actually why I looked to see if DRI was off when the first installation failed. But DRI still didn't work even when I had only the AGP card installed. I'd file something in Bugzilla but the system is now in use so I cannot play with it. Furthermore, I wonder if it had something to do with the nForce motherboard's AGP support. I never tried with only the PCI card - maybe that would have worked. - Bill Hamblen From acosta at ar.microlink.com.br Tue Mar 9 15:27:20 2004 From: acosta at ar.microlink.com.br (Andre Costa) Date: Tue, 9 Mar 2004 12:27:20 -0300 Subject: Mouse stops working In-Reply-To: References: <20040308135340.53859628.acosta@ar.microlink.com.br> Message-ID: <20040309122720.7cf4e3c4.acosta@ar.microlink.com.br> Hi Mike, On Tue, 9 Mar 2004 00:02:54 -0500 (EST) "Mike A. Harris" wrote: > On Mon, 8 Mar 2004, Andre Costa wrote: > > >sometimes, mouse simply stops working with X. Everything else (eg. > >keyboard) keeps working. I have no choice (AFAIK) but shutdown X with > >CTRL+ALT+BACKSPACE, which sometimes makes me lose stuff I was doing. > > > >I use latest 4.3.0-55 packages for Fedora, with NVidia driver 5336. > >My mouse-related settings on XF86Config are: > [SNIP] > >My mouse is an optical MS Intellimouse, attached do PS/2 port. The > >reported behavior happens either if I keep gpm running or not while > >on X./var/log/XFree86.0.log says: > > > >(II) XINPUT: Adding extended input device "DevInputMice" (type: > >MOUSE) > > There are some faulty Microsoft Intellimice out there, which are > just broken hardware. ... in this case, maybe they should be renamed to "M$ DumbMice" =) > It is possible that you may have one of > them, but I do not remember how to go about determining which > ones are broken. Microsoft has some knowledgebase articles on > this problem, and if I remember correctly, there is no easy way > around the problem. I will try to see if I can find some info on MS knowledge base about this. However, I really don't think it is a problem with my mouse, because windoze on the same box works just fine for hours (never experienced these locks there). > However... you might not have the buggy M$ mouse either, it > could be some other problem. I recommend disabling gpm entirely > at boot time and rebooting without it running to see if that > makes any difference. Mmh... I had already tried disabling gpm before starting X, and enabling right afterwards. Didn't help much, but I hadn't tried completely deactivating gpm (I mean, "chkconfig gpm off"). I am trying it right now (just rebooted), let's see if it improves stability... FYI, these locks are somewhat rare, it's not easy to reproduce them. One important info: with gpm enabled, I saw sometimes right after I exit X a "spurious interrupt 8257A" message on console (or something similar, can't remember exactly what it was, sorry...) > >(II) XINPUT: Adding extended input device "NVIDIA Event Handler" > >(type: Other)(II) Mouse0: ps2EnableDataReporting: succeeded > > Nvidia event handler? That's a new one to me. Perhaps Nvidia's > video driver now has a built in mouse driver as well? ;o) Who knows? ;) I will send a msg to Nvidia ML to try to gather some info. I will post back here any findings, just for the record. > >Any hints on what to do to narrow down the cause of the problem? > >Should I post this to NVIDIA ML? > > I would recommend reinstalling XFree86 from the latest rpms > available for the OS release you are using, and configure the > "nv" driver, or "vesa" driver and try to reproduce the problem. > If the problem is not reproduceable, then it may be possible that > the nvidia driver is interfering with things, at which point you > might want to try Nvidia's web forums in case someone is aware of > problems like this caused by their driver. > > Hope this helps! Sure did, Mike, thks a lot =) Let me see if I can gather any additional info, and I will post back here the results. Best, Andre -- Andre Oliveira da Costa From surak at casa.surak.eti.br Tue Mar 9 18:57:49 2004 From: surak at casa.surak.eti.br (Alexandre Strube) Date: Tue, 09 Mar 2004 15:57:49 -0300 Subject: Dual DVI success In-Reply-To: References: Message-ID: <1078858669.27631.3.camel@ahrak.surak.eti.br> Em Ter, 2004-03-09 ?s 01:28, Mike A. Harris escreveu: > Just as a point of reference, DRI is disabled if you are using > multihead because DRI is not multihead compatible. So all > multihead setups have DRI disabled wether or not Xinerama is I just realized that I have a onboard video on this machine, don't even know which board is. If I enable this board, I will loose 3d on my voodoo pci card, is that correct? -- Alexandre Strube From mharris at redhat.com Wed Mar 10 02:17:00 2004 From: mharris at redhat.com (Mike A. Harris) Date: Tue, 9 Mar 2004 21:17:00 -0500 (EST) Subject: New package added to Fedora devel: xrestop - GUI X Resource monitoring tool. Message-ID: The GUI xrestop utility has been added to Fedora Core development. xrestop presents a 'top' like view of X resources. This utility can be used to determine what applications might be leaking X resources, or may be using a lot of X resources, all of which are stored in the X server, and thus affect the memory footprint of the X server - even though the resources belong to the applications themselves. Often, people look at the output of "top" or "ps" and mistakenly believe that the X server is using a horrendous amount of memory. The output of both of those programs is very inaccurate for the X server process, as the X server mmap's video memory, and I/O regions of the video hardware, ROM BIOSes, etc. all of which add into the memory shown by top/ps for the process, but which are not physical system RAM. This results in the mistaken belief that the X server uses a lot of memory, when in reality, the X server itself uses very little memory at all. Aside from the above problem, the other more frequent cause of the X server appearing to use a lot of memory, is applications allocating X resources. Some applications such as Mozilla, can use a LOT of pixmaps when viewing certain web pages, etc. which all end up stored in the X server until mozilla releases them or exits. If you visit a large webpage with hundreds of images, you'll quickly see your X server increase in size. Quit the web browser and you'll see the X server shrink again. Applications which leak X resources, end up causing the X server to bloat over time, until the application is killed - at which time the resources are freed. xrestop is a useful utility for tracking down X resource leakage problems and for helping both developers and end users alike to determine what exactly is causing their X server memory usage to increase. The overwhelming majority of all "my X server is leaking memory" bugs that get reported, almost always end up /not/ being X server bugs, but instead are applications leaking X resources, some of which are hard to find because they are part of the desktop environment itself, such as gnome-panel or similar. Please use xrestop when experiencing problems of this nature, to help pinpoint the true cause of the problems at hand, so that bugs can be filed to the appropriate buggy components in bugzilla. Now that there is a useful tool for helping track these types of issues down, please do not gang up on the X server with X resource utilization bugs. It is memory leak free, or we'd have to change the name of it to XMalloc86. ;o) /me runs to dodge the tomatoes Seriously though, please play with xrestop, and report any application resource leakage bugs you find in bugzilla. Thanks for testing! -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat From acosta at ar.microlink.com.br Wed Mar 10 02:37:29 2004 From: acosta at ar.microlink.com.br (Andre Costa) Date: Tue, 9 Mar 2004 23:37:29 -0300 Subject: New package added to Fedora devel: xrestop - GUI X Resource monitoring tool. In-Reply-To: References: Message-ID: <20040309233729.6209872d.acosta@ar.microlink.com.br> Cool, Mike, well done! Kudos to all involved, seems like a very cool app... any ETA for it to appear among 'stable' Fedora packages? Best, Andre On Tue, 9 Mar 2004 21:17:00 -0500 (EST) "Mike A. Harris" wrote: > The GUI xrestop utility has been added to Fedora Core > development. > > xrestop presents a 'top' like view of X resources. This utility > can be used to determine what applications might be leaking X > resources, or may be using a lot of X resources, all of which > are stored in the X server, and thus affect the memory footprint > of the X server - even though the resources belong to the > applications themselves. > > Often, people look at the output of "top" or "ps" and mistakenly > believe that the X server is using a horrendous amount of memory. > The output of both of those programs is very inaccurate for the X > server process, as the X server mmap's video memory, and I/O > regions of the video hardware, ROM BIOSes, etc. all of which add > into the memory shown by top/ps for the process, but which are > not physical system RAM. This results in the mistaken belief > that the X server uses a lot of memory, when in reality, the X > server itself uses very little memory at all. > > Aside from the above problem, the other more frequent cause of > the X server appearing to use a lot of memory, is applications > allocating X resources. Some applications such as Mozilla, can > use a LOT of pixmaps when viewing certain web pages, etc. which > all end up stored in the X server until mozilla releases them or > exits. If you visit a large webpage with hundreds of images, > you'll quickly see your X server increase in size. Quit the web > browser and you'll see the X server shrink again. > > Applications which leak X resources, end up causing the X server > to bloat over time, until the application is killed - at which > time the resources are freed. > > xrestop is a useful utility for tracking down X resource leakage > problems and for helping both developers and end users alike to > determine what exactly is causing their X server memory usage to > increase. > > The overwhelming majority of all "my X server is leaking memory" > bugs that get reported, almost always end up /not/ being X server > bugs, but instead are applications leaking X resources, some of > which are hard to find because they are part of the desktop > environment itself, such as gnome-panel or similar. > > Please use xrestop when experiencing problems of this nature, to > help pinpoint the true cause of the problems at hand, so that > bugs can be filed to the appropriate buggy components in > bugzilla. > > Now that there is a useful tool for helping track these types of > issues down, please do not gang up on the X server with X > resource utilization bugs. It is memory leak free, or we'd have > to change the name of it to XMalloc86. ;o) > > /me runs to dodge the tomatoes > > Seriously though, please play with xrestop, and report any > application resource leakage bugs you find in bugzilla. > > Thanks for testing! > > > -- > Mike A. Harris ftp://people.redhat.com/mharris > OS Systems Engineer - XFree86 maintainer - Red Hat > > > _______________________________________________ > xfree86-list mailing list > xfree86-list at redhat.com > https://www.redhat.com/mailman/listinfo/xfree86-list > IRC: #xfree86 on irc.redhat.com -- Andre Oliveira da Costa From mharris at www.linux.org.uk Wed Mar 10 03:03:46 2004 From: mharris at www.linux.org.uk (Mike A. Harris) Date: Tue, 9 Mar 2004 22:03:46 -0500 (EST) Subject: New package added to Fedora devel: xrestop - GUI X Resource monitoring tool. In-Reply-To: <20040309233729.6209872d.acosta@ar.microlink.com.br> References: <20040309233729.6209872d.acosta@ar.microlink.com.br> Message-ID: On Tue, 9 Mar 2004, Andre Costa wrote: >Cool, Mike, well done! Kudos to all involved, seems like a very All the credit for xrestop should go to the author Matthew Allum, as I didn't really do anything other than download it and use his spec file as a basis for the Red Hat rpm. ;o) Took me about 10 minutes. ;o) In hindsight, I should have probably mentioned credit to Matt in my previous email, as well as a link to the upstream utility homepage: http://freedesktop.org/Software/xrestop >cool app... any ETA for it to appear among 'stable' Fedora >packages? It's now part of Fedora Core development, so once Fedora Core 2 is released, I guess we can consider it stable. ;o) It should be useable on Fedora Core 1 and FC2test releases in the mean time, or can be rebuilt with rpmbuild --rebuild for them. Enjoy! From anthony.seward at ieee.org Wed Mar 10 17:24:53 2004 From: anthony.seward at ieee.org (Anthony Joseph Seward) Date: Wed, 10 Mar 2004 10:24:53 -0700 Subject: Freeglut 2.2.0 is now in Fedora devel tree - Request For Testers In-Reply-To: References: Message-ID: <1078939492.4843.47.camel@sonylap1> There might be a dependency problem. I tried just 'up2date -i freglut- devel' and up2date crashed with ================================================================ [root at sonylap1 seward]# up2date -i freeglut-devel Fetching Obsoletes list for channel: fed-development... Fetching Obsoletes list for channel: katzj-evolution... Fetching rpm headers... ######################################## Name Version Rel ---------------------------------------------------------- freeglut-devel 2.2.0 10 i386 Testing package set / solving RPM inter-dependencies... Traceback (most recent call last): File "/usr/sbin/up2date", line 1267, in ? sys.exit(main() or 0) File "/usr/sbin/up2date", line 797, in main fullUpdate, dryRun=options.dry_run)) File "/usr/sbin/up2date", line 1141, in batchRun batch.run() File "up2dateBatch.py", line 74, in run File "up2dateBatch.py", line 159, in __dryRun File "up2date.py", line 387, in dryRun File "depSolver.py", line 716, in solvedep File "depSolver.py", line 683, in process_deps File "depSolver.py", line 475, in __dependencies File "depSolver.py", line 93, in solveDep File "/usr/share/rhn/up2date_client/repoBackends/genericSolveDep.py", line 40, in solveDep self.getSolutions(unknowns) File "/usr/share/rhn/up2date_client/repoBackends/genericSolveDep.py", line 235, in getSolutions hdr = self.getHeader(pkg) File "/usr/share/rhn/up2date_client/repoBackends/genericSolveDep.py", line 217, in getHeader progressCallback = progressCallback) File "rpcServer.py", line 112, in doCall File "repoDirector.py", line 31, in getHeader File "rpmSource.py", line 210, in getHeader File "/usr/share/rhn/up2date_client/repoBackends/yumRepo.py", line 87, in getHeader (fn, h) = urllib.urlretrieve(url) File "/usr/lib/python2.3/urllib.py", line 83, in urlretrieve return _urlopener.retrieve(url, filename, reporthook, data) File "/usr/lib/python2.3/urllib.py", line 213, in retrieve fp = self.open(url, data) File "/usr/lib/python2.3/urllib.py", line 181, in open return getattr(self, name)(url) File "/usr/lib/python2.3/urllib.py", line 306, in open_http return self.http_error(url, fp, errcode, errmsg, headers) File "/usr/lib/python2.3/urllib.py", line 323, in http_error return self.http_error_default(url, fp, errcode, errmsg, headers) File "/usr/lib/python2.3/urllib.py", line 551, in http_error_default return addinfourl(fp, headers, "http:" + url) File "/usr/lib/python2.3/urllib.py", line 837, in __init__ addbase.__init__(self, fp) File "/usr/lib/python2.3/urllib.py", line 787, in __init__ self.read = self.fp.read AttributeError: 'NoneType' object has no attribute 'read' ================================================================ I then did 'up2date -i freeglut' followed by 'up2date -i freeglut- devel'. This worked fine. Tony -- Anthony Joseph Seward From vpr_mam at lycos.com Mon Mar 15 15:20:17 2004 From: vpr_mam at lycos.com (Veera Partha) Date: Mon, 15 Mar 2004 10:20:17 -0500 Subject: Downloading the XFree86 4.3.0 binaries Message-ID: I downloaded the latest xfree86 binaries for AS 2.1 i.e. binaries under Linux-ix86-glibc22/ from the website. I installed these binaries into my existing AS 2.1 installtion using the Xinstall.sh script. It was successful. I tried to configure X with the following: xf86config utility- looks like it was not listing the video card i am using i.e. Intel D845GVSR mother board with intel extreme graphics.Hence the display was not proper. xf86cfg utility: tried the options, the same result. Thirdly, i tried XFree86 -configure: unable to configure since it complained that there is no glide 2.x installed. But my redhat installtion is a typical installation i.e. it contains gnome,kde & application development packages. I could also see glide 3.x. The binaries i am using is xfree86 4.4.0 Kindly let me know if the video card i am using is compatible with xfree 4.4.0. My system configuration is: Intel P 4, 512 mb RAM, intel D845 GVSR motherboard. Any help on this is greatly appreciated. Thanks. -- --------- Original Message --------- DATE: Thu, 26 Feb 2004 06:41:57 From: "Veera Partha" To: xfree86-list at redhat.com Cc: >Hi All, > >I have installed linux in my PC. version is Redhat advanced server 2.1. > >Can you please confirm which set of XFree86 4.3.0 binaries need to be downloaded from >http://ftp.xfree86.org/pub/XFree86/4.3.0/binaries/ > >I need to upgrade the current Xfre86 that comes with AS 2.1. > >From the above site, the binaries are organized by sub-directories which correspond to each of the OS/platforms for which binaries are provided. > >I need to download the binaries from one of the following directories corresponding to my os >version: >Linux-axp-glibc22/ > Linux-ix86-glibc21/ > Linux-ix86-glibc22/ > Linux-ix86-glibc23/ > >From which directory i need to download the binaries for my Redhat OS. >Request you to cinfirm. > >Thanks. > > >____________________________________________________________ >Find what you are looking for with the Lycos Yellow Pages >http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 > ____________________________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 From hardawayd at slu.edu Wed Mar 17 19:40:36 2004 From: hardawayd at slu.edu (don hardaway) Date: Wed, 17 Mar 2004 13:40:36 -0600 Subject: converting from XFree86 to xorg Message-ID: <4058A9B4.4010809@slu.edu> I am running the latest core2 beta and would like to convert from XFree86 to xorg. Can someone please instruct me how to do this considering the deps that exist between XFree86 and other packages. thank you From vpr_mam at lycos.com Mon Mar 22 10:26:27 2004 From: vpr_mam at lycos.com (Veera Partha) Date: Mon, 22 Mar 2004 05:26:27 -0500 Subject: Downloading the XFree86 4.4.0 binaries Message-ID: After the latest xfree86 binaries installation, i tried to configure using "xf86cfg". I could see the video card which i am using i.e. intel D845. AFter configuration, when i started X using startx, i get only the terminal window, not the Gnome or kde. Kindly let me know what needs to be done to get the gnome or kde desktop. I have a complete installation, with gnome & kde desktop. Any help is greatly appreciated. Thanks. -- --------- Original Message --------- DATE: Mon, 15 Mar 2004 10:20:17 From: "Veera Partha" To: xfree86-list at redhat.com Cc: >I downloaded the latest xfree86 binaries for AS 2.1 >i.e. binaries under Linux-ix86-glibc22/ from the website. > >I installed these binaries into my existing AS 2.1 installtion using the Xinstall.sh script. It was successful. I tried to >configure X with the following: > >xf86config utility- looks like it was not listing the video card i am using i.e. Intel D845GVSR mother board with intel extreme graphics.Hence the display was not proper. > >xf86cfg utility: tried the options, the same result. > >Thirdly, i tried XFree86 -configure: >unable to configure since it complained that there is no glide 2.x installed. But my redhat installtion is a typical installation i.e. it contains gnome,kde & application development packages. I could also see glide 3.x. > >The binaries i am using is xfree86 4.4.0 > >Kindly let me know if the video card i am using is compatible with xfree 4.4.0. > >My system configuration is: > >Intel P 4, 512 mb RAM, intel D845 GVSR motherboard. > >Any help on this is greatly appreciated. > >Thanks. > >-- > >--------- Original Message --------- > >DATE: Thu, 26 Feb 2004 06:41:57 >From: "Veera Partha" >To: xfree86-list at redhat.com >Cc: > >>Hi All, >> >>I have installed linux in my PC. version is Redhat advanced server 2.1. >> >>Can you please confirm which set of XFree86 4.3.0 binaries need to be downloaded from >>http://ftp.xfree86.org/pub/XFree86/4.3.0/binaries/ >> >>I need to upgrade the current Xfre86 that comes with AS 2.1. >> >>From the above site, the binaries are organized by sub-directories which correspond to each of the OS/platforms for which binaries are provided. >> >>I need to download the binaries from one of the following directories corresponding to my os >>version: >>Linux-axp-glibc22/ >> Linux-ix86-glibc21/ >> Linux-ix86-glibc22/ >> Linux-ix86-glibc23/ >> >>From which directory i need to download the binaries for my Redhat OS. >>Request you to cinfirm. >> >>Thanks. >> >> >>____________________________________________________________ >>Find what you are looking for with the Lycos Yellow Pages >>http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 >> > > > >____________________________________________________________ >Find what you are looking for with the Lycos Yellow Pages >http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 > ____________________________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 From vpr_mam at lycos.com Tue Mar 23 04:41:38 2004 From: vpr_mam at lycos.com (Veera Partha) Date: Mon, 22 Mar 2004 23:41:38 -0500 Subject: How to configure kde or gnome after latest xfree86 binaries installation? Message-ID: Hi All, I have installed latest xfree86 binaries ver 4.4.0, downloaded from xfree86.org. I have installed using Xinstall.sh script. This i installed on my existing redhat as 2.1 installation. After the binaries installation, i tried to configure X using: xfree86config xf86cfg Able to configure, but unable to get kde or gnome desktop. All that i get is terminal windows of xterm types. I tried to configure using XFree86 -configure, but it complained that glide is not available. Would like to know what needs to be carried out to get kde or gnome desktop. Any help is greatly appreciated. Thanks. ____________________________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 From beartooth at adelphia.net Sun Mar 28 15:42:43 2004 From: beartooth at adelphia.net (Bear Tooth) Date: Sun, 28 Mar 2004 10:42:43 -0500 Subject: Panel background goes black Message-ID: I recently got a new flat panel monitor, the BenQ FP767, and have made a lot of changes in /etc/X11/XF86Config -- but no others, except for tweaking a couple of apps (Konqueror 3.1.15-RedHat and Opera 7.23) I've also done a lot of logging out/in and rebooting. About the time I got the monitor more or less usable, I started noticing that the panels come up with a black background, making the launchers hard to see (especially since the monitor housing is deep black!), every time I reboot -- and, I think, every time I log out and back in. (If that matters, I'll gladly test it.) What could be causing this, and what should I do about it? -- Beartooth Autodidact, curmudgeonly codger learning linux id est karhunhammas (at) lserv dot com (adelphia = spamtrap) Keep in mind how little I know of what I'm talking about.