Re: Bugreport Xfree 4.0.1c
On Fri, Oct 06, 2000 at 12:22:47AM +0200, Feczak Szabolcs wrote: XFree86 Version 4.0.1c / X Window System [...] When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to [EMAIL PROTECTED] I did :) You might consider mentioning what you were doing when the server crashed... -- G. Branden Robinson | Somewhere, there is a .sig so funny that Debian GNU/Linux| reading it will cause an aneurysm. This [EMAIL PROTECTED] | is not that .sig. http://www.debian.org/~branden/ | PGP signature
Re: xlibs 40.1-0phase2v13 break xawtv
On Thu, Oct 05, 2000 at 01:03:36AM -0400, Decklin Foster wrote: Robert Vollmert [EMAIL PROTECTED] writes: Error: XtMakeGeometryRequest - parent not composite Actually, this is not just happening with xawtv, but any xaw menu. It appears to be an upstream problem; send your report there. Are you using phase2v13? If not, please try it, because: 732. Fixed handling of XtMakeGeometryRequest() to test for parent belonging to subclass of composite class only if the widget itself is managed. This follows the specs more closely. (Keith Packard). If you already are using v13, then it is possible the client is coded wrongly. Or maybe Keith messed up (possible, but unusual). -- G. Branden Robinson |Kissing girls is a goodness. It is a Debian GNU/Linux|growing closer. It beats the hell out [EMAIL PROTECTED] |of card games. http://www.debian.org/~branden/ |-- Robert Heinlein PGP signature
Re: xlibs 4.0.1-0phase2v13 break xawtv
On Fri, Oct 06, 2000 at 01:56:02AM -0500, Branden Robinson wrote: Are you using phase2v13? If not, please try it, because: 732. Fixed handling of XtMakeGeometryRequest() to test for parent belonging to subclass of composite class only if the widget itself is managed. This follows the specs more closely. (Keith Packard). If you already are using v13, then it is possible the client is coded wrongly. Or maybe Keith messed up (possible, but unusual). I have these problems only when using v13, previous (at least v12) packages work fine. Apart from xawtv, xgammon and freeciv-xaw3d also fail, while xvile-xaw works. I also compiled xawtv without xaw3d support, but that doesn't seem to make a difference. With v12, all these programs work. -- Robert Vollmert [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: could not open default font
Sam, I had to do this to solve the problem:- apt-get remove xfonts-base dpkg --purge xfonts-base apt-get install xfonts-base The purging of the directory solved the problem for me as a new set of font information was installed alongside the fonts but it took a good 2 hours to work out what the problem was. Hope that helps, Ben Thompson sam th [EMAIL PROTECTED] wrote .. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When running the command `XFree86 -xf86config /root/XF86Config.new` as suggested by -configure, I get the following error at the end. Attached is the whole log, gzipped. There are no font paths in that config file, but according to the man page, it reads the defaults anyway, and they are correct. I have installed the 2v13 .debs for xfonts-base, -scalable, -75dpi and - -100dpi. I have tried this with and without xfs running. I can't think of anything else to try. (**) Option "Device" "/dev/mouse" (==) Mouse0: Buttons: 3 (II) Keyboard "Keyboard0" handled by legacy driver (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) Couldn't load XKB keymap, falling back to pre-XKB keymap (EE) Mouse0: cannot determine the mouse protocol Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Fatal server error: could not open default font 'fixed' sam th [EMAIL PROTECTED] http://www.abisource.com/~sam/ GnuPG Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=getsearch=0xCABD33FC -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE53bG/t+kM0Mq9M/wRAmf4AKDIeGTwzbhh35VFyPP+dq//p8tD6gCgp89O /weTvteUJgwPYh4NSCBdFTE= =3t9M -END PGP SIGNATURE-
Re: could not open default font 'fixed'
On Fri, Oct 06, 2000 at 06:04:29AM -0500, sam th wrote: There are no font paths in that config file, but according to the man page, it reads the defaults anyway, and they are correct. For me, the defaults work only so long as I make sure that neither the freefont package nor the sharefont package is installed. I have installed the 2v13 .debs for xfonts-base, -scalable, -75dpi and - -100dpi. I have tried this with and without xfs running. Even with the freefont package installed, my X server comes up properly if I list the font paths explicitly. In order to make use of all of the fonts, I also need to load the appropriate modules. Here is an excerpt from my /etc/X11/XF86Config. Note that the order of the lines in the "Files" section is important. By placing the 100dpi line before the 75dpi line, I get generally bigger fonts; I did this because some of the unadjustable fonts in netscape, etc. appear nicely larger. Note, too, the first three lines of the "Module" section. --begin excerpt from /etc/X11/XF86Config-- Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/PEX/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/TrueType/" EndSection Section "Module" Load "type1" Load "freetype" Load "speedo" Load "extmod" Load "xie" Load "pex5" Load "glx" Load "dri" Load "GLcore" Load "dbe" Load "record" EndSection --end excerpt from /etc/X11/XF86Config-- --some font packages installed on my system ii freefont 0.10-8Freeware font selection for X11 ii xfonts-100dpi 4.0.1-0phase2v13 100 dpi fonts for X ii xfonts-75dpi 4.0.1-0phase2v13 75 dpi fonts for X ii xfonts-base 4.0.1-0phase2v13 standard fonts for X ii xfonts-cyrillic 4.0.1-0phase2v13 Cyrillic fonts for X ii xfonts-intl-phonetic 1.1-9 International fonts for X -- Ph ii xfonts-jmk3.0-2 James M. Knoble's character-cel ii xfonts-pex4.0.1-0phase2v13 fonts for minimal PEX support i ii xfonts-scalable 4.0.1-0phase2v13 scalable fonts for X --- -- Thomas E. Vaughan [EMAIL PROTECTED] CIMMS/NSSL, Norman, OK, USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: could not open default font
On Fri, Oct 06, 2000 at 12:16:23PM +0100, [EMAIL PROTECTED] wrote: I had to do this to solve the problem:- apt-get remove xfonts-base dpkg --purge xfonts-base apt-get install xfonts-base The purging of the directory solved the problem for me as a new set of font information was installed alongside the fonts but it took a good 2 hours to work out what the problem was. In my reply to Sam's message, I mentioned a problem with sharefont and freefont. Because I had freefont installed, I was unable to start the X server even after doing what you recommend above. The only solution with freefont or sharefont installed seems to involve writing an explicit list of font paths into /etc/X11/XF86Config. -- Thomas E. Vaughan [EMAIL PROTECTED] CIMMS/NSSL, Norman, OK, USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: could not open default font 'fixed'
Actually, as well as having to re-install xfonts-base, I noticed that xf86config didn't put /usr/X11R6/lib/X11/fonts/misc in my font path. Since that's the location of the fixed font, it was unable to find it, and did the same thing to me. -- Justin Wheeler [EMAIL PROTECTED] On Fri, 6 Oct 2000, sam th wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When running the command `XFree86 -xf86config /root/XF86Config.new` as suggested by -configure, I get the following error at the end. Attached is the whole log, gzipped. There are no font paths in that config file, but according to the man page, it reads the defaults anyway, and they are correct. I have installed the 2v13 .debs for xfonts-base, -scalable, -75dpi and - -100dpi. I have tried this with and without xfs running. I can't think of anything else to try. (**) Option "Device" "/dev/mouse" (==) Mouse0: Buttons: 3 (II) Keyboard "Keyboard0" handled by legacy driver (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) Couldn't load XKB keymap, falling back to pre-XKB keymap (EE) Mouse0: cannot determine the mouse protocol Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Fatal server error: could not open default font 'fixed' sam th [EMAIL PROTECTED] http://www.abisource.com/~sam/ GnuPG Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=getsearch=0xCABD33FC -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE53bG/t+kM0Mq9M/wRAmf4AKDIeGTwzbhh35VFyPP+dq//p8tD6gCgp89O /weTvteUJgwPYh4NSCBdFTE= =3t9M -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bugreport Xfree 4.0.1c
On Fri, Oct 06, 2000 at 12:22:47AM +0200, Feczak Szabolcs wrote: XFree86 Version 4.0.1c / X Window System [...] When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] I did :) You might consider mentioning what you were doing when the server crashed... -- G. Branden Robinson | Somewhere, there is a .sig so funny that Debian GNU/Linux| reading it will cause an aneurysm. This [EMAIL PROTECTED] | is not that .sig. http://www.debian.org/~branden/ | pgpfuR9uMKKM5.pgp Description: PGP signature
Re: xlibs 40.1-0phase2v13 break xawtv
On Thu, Oct 05, 2000 at 01:03:36AM -0400, Decklin Foster wrote: Robert Vollmert [EMAIL PROTECTED] writes: Error: XtMakeGeometryRequest - parent not composite Actually, this is not just happening with xawtv, but any xaw menu. It appears to be an upstream problem; send your report there. Are you using phase2v13? If not, please try it, because: 732. Fixed handling of XtMakeGeometryRequest() to test for parent belonging to subclass of composite class only if the widget itself is managed. This follows the specs more closely. (Keith Packard). If you already are using v13, then it is possible the client is coded wrongly. Or maybe Keith messed up (possible, but unusual). -- G. Branden Robinson |Kissing girls is a goodness. It is a Debian GNU/Linux|growing closer. It beats the hell out [EMAIL PROTECTED] |of card games. http://www.debian.org/~branden/ |-- Robert Heinlein pgpxzsVAlyyD9.pgp Description: PGP signature
Re: xlibs 4.0.1-0phase2v13 break xawtv
On Fri, Oct 06, 2000 at 01:56:02AM -0500, Branden Robinson wrote: Are you using phase2v13? If not, please try it, because: 732. Fixed handling of XtMakeGeometryRequest() to test for parent belonging to subclass of composite class only if the widget itself is managed. This follows the specs more closely. (Keith Packard). If you already are using v13, then it is possible the client is coded wrongly. Or maybe Keith messed up (possible, but unusual). I have these problems only when using v13, previous (at least v12) packages work fine. Apart from xawtv, xgammon and freeciv-xaw3d also fail, while xvile-xaw works. I also compiled xawtv without xaw3d support, but that doesn't seem to make a difference. With v12, all these programs work. -- Robert Vollmert [EMAIL PROTECTED]
could not open default font 'fixed'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When running the command `XFree86 -xf86config /root/XF86Config.new` as suggested by -configure, I get the following error at the end. Attached is the whole log, gzipped. There are no font paths in that config file, but according to the man page, it reads the defaults anyway, and they are correct. I have installed the 2v13 .debs for xfonts-base, -scalable, -75dpi and - -100dpi. I have tried this with and without xfs running. I can't think of anything else to try. (**) Option Device /dev/mouse (==) Mouse0: Buttons: 3 (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) Couldn't load XKB keymap, falling back to pre-XKB keymap (EE) Mouse0: cannot determine the mouse protocol Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Fatal server error: could not open default font 'fixed' sam th [EMAIL PROTECTED] http://www.abisource.com/~sam/ GnuPG Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=getsearch=0xCABD33FC -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE53bG/t+kM0Mq9M/wRAmf4AKDIeGTwzbhh35VFyPP+dq//p8tD6gCgp89O /weTvteUJgwPYh4NSCBdFTE= =3t9M -END PGP SIGNATURE- XFree86.0.log.gz Description: Binary data
Re: could not open default font
Sam, I had to do this to solve the problem:- apt-get remove xfonts-base dpkg --purge xfonts-base apt-get install xfonts-base The purging of the directory solved the problem for me as a new set of font information was installed alongside the fonts but it took a good 2 hours to work out what the problem was. Hope that helps, Ben Thompson sam th [EMAIL PROTECTED] wrote .. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When running the command `XFree86 -xf86config /root/XF86Config.new` as suggested by -configure, I get the following error at the end. Attached is the whole log, gzipped. There are no font paths in that config file, but according to the man page, it reads the defaults anyway, and they are correct. I have installed the 2v13 .debs for xfonts-base, -scalable, -75dpi and - -100dpi. I have tried this with and without xfs running. I can't think of anything else to try. (**) Option Device /dev/mouse (==) Mouse0: Buttons: 3 (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) Couldn't load XKB keymap, falling back to pre-XKB keymap (EE) Mouse0: cannot determine the mouse protocol Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Fatal server error: could not open default font 'fixed' sam th [EMAIL PROTECTED] http://www.abisource.com/~sam/ GnuPG Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=getsearch=0xCABD33FC -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE53bG/t+kM0Mq9M/wRAmf4AKDIeGTwzbhh35VFyPP+dq//p8tD6gCgp89O /weTvteUJgwPYh4NSCBdFTE= =3t9M -END PGP SIGNATURE-
Re: could not open default font 'fixed'
On Fri, Oct 06, 2000 at 06:04:29AM -0500, sam th wrote: There are no font paths in that config file, but according to the man page, it reads the defaults anyway, and they are correct. For me, the defaults work only so long as I make sure that neither the freefont package nor the sharefont package is installed. I have installed the 2v13 .debs for xfonts-base, -scalable, -75dpi and - -100dpi. I have tried this with and without xfs running. Even with the freefont package installed, my X server comes up properly if I list the font paths explicitly. In order to make use of all of the fonts, I also need to load the appropriate modules. Here is an excerpt from my /etc/X11/XF86Config. Note that the order of the lines in the Files section is important. By placing the 100dpi line before the 75dpi line, I get generally bigger fonts; I did this because some of the unadjustable fonts in netscape, etc. appear nicely larger. Note, too, the first three lines of the Module section. --begin excerpt from /etc/X11/XF86Config-- Section Files FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath /usr/X11R6/lib/X11/fonts/freefont/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/PEX/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/TrueType/ EndSection Section Module Load type1 Load freetype Load speedo Load extmod Load xie Load pex5 Load glx Load dri Load GLcore Load dbe Load record EndSection --end excerpt from /etc/X11/XF86Config-- --some font packages installed on my system ii freefont 0.10-8Freeware font selection for X11 ii xfonts-100dpi 4.0.1-0phase2v13 100 dpi fonts for X ii xfonts-75dpi 4.0.1-0phase2v13 75 dpi fonts for X ii xfonts-base 4.0.1-0phase2v13 standard fonts for X ii xfonts-cyrillic 4.0.1-0phase2v13 Cyrillic fonts for X ii xfonts-intl-phonetic 1.1-9 International fonts for X -- Ph ii xfonts-jmk3.0-2 James M. Knoble's character-cel ii xfonts-pex4.0.1-0phase2v13 fonts for minimal PEX support i ii xfonts-scalable 4.0.1-0phase2v13 scalable fonts for X --- -- Thomas E. Vaughan [EMAIL PROTECTED] CIMMS/NSSL, Norman, OK, USA
Re: could not open default font
On Fri, Oct 06, 2000 at 12:16:23PM +0100, [EMAIL PROTECTED] wrote: I had to do this to solve the problem:- apt-get remove xfonts-base dpkg --purge xfonts-base apt-get install xfonts-base The purging of the directory solved the problem for me as a new set of font information was installed alongside the fonts but it took a good 2 hours to work out what the problem was. In my reply to Sam's message, I mentioned a problem with sharefont and freefont. Because I had freefont installed, I was unable to start the X server even after doing what you recommend above. The only solution with freefont or sharefont installed seems to involve writing an explicit list of font paths into /etc/X11/XF86Config. -- Thomas E. Vaughan [EMAIL PROTECTED] CIMMS/NSSL, Norman, OK, USA
Re: could not open default font 'fixed'
Actually, as well as having to re-install xfonts-base, I noticed that xf86config didn't put /usr/X11R6/lib/X11/fonts/misc in my font path. Since that's the location of the fixed font, it was unable to find it, and did the same thing to me. -- Justin Wheeler [EMAIL PROTECTED] On Fri, 6 Oct 2000, sam th wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When running the command `XFree86 -xf86config /root/XF86Config.new` as suggested by -configure, I get the following error at the end. Attached is the whole log, gzipped. There are no font paths in that config file, but according to the man page, it reads the defaults anyway, and they are correct. I have installed the 2v13 .debs for xfonts-base, -scalable, -75dpi and - -100dpi. I have tried this with and without xfs running. I can't think of anything else to try. (**) Option Device /dev/mouse (==) Mouse0: Buttons: 3 (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) Couldn't load XKB keymap, falling back to pre-XKB keymap (EE) Mouse0: cannot determine the mouse protocol Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Fatal server error: could not open default font 'fixed' sam th [EMAIL PROTECTED] http://www.abisource.com/~sam/ GnuPG Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=getsearch=0xCABD33FC -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE53bG/t+kM0Mq9M/wRAmf4AKDIeGTwzbhh35VFyPP+dq//p8tD6gCgp89O /weTvteUJgwPYh4NSCBdFTE= =3t9M -END PGP SIGNATURE-
Trouble with DRI on G200
Hi All, I'm trying to get DRI working on my Matrox G200 and not having much luck. Most of this is probably due to my ignorance of Linux 3d support, but since it involves Debian specific changes to X, I thought I'd ask here first. I first tried using the stock 4.0.1-0phase2v13 X packages with kernel 2.2.18pre15 and got the following message from the X server: (EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 1.0.0, expected 2.0.x). Disabling DRI. It seems the Debian diff for 4.0.1-0phase2v13 has patched the mga_drv X module to require a newer version of the mga kernel module, which AFAICT, is only available in the 2.4 kernel. I'd rather not switch to the 2.4 kernel yet. Does anyone know of a newer version of the mga kernel module for the 2.2 kernel? I then tried replacing the mga_drv X module with one from the Matrox ftp site that appeared to work with the 1.0.x mga kernel module and got the following messages: (0): [drm] installed DRM signal handler (0): [DRI] installation complete (II) MGA(0): direct rendering enabled However, glxinfo claimed direct rendering was not enabled, and sure enough, there was no improvement over software renedering when running 3d apps. FYI, another partly related problem I've run into is that the mesag3 package contains libGL and libGLU but the xlibmesa3 package only contains libGL. What package is supposed to provide libGLU when xlibmesa3 is used? David -- David Engel [EMAIL PROTECTED]
Re: Trouble with DRI on G200
* David Engel [EMAIL PROTECTED] [001006 08:08]: I'm trying to get DRI working on my Matrox G200 and not having much luck. Most of this is probably due to my ignorance of Linux 3d support, but since it involves Debian specific changes to X, I thought I'd ask here first. Well, I found it difficult to make work as well. It wasn't quite easy. I do not claim to know how it all works; I will give you my best understanding of the situation. DRI requires some help from the kernel that exists only in the 2.4 series. (And the 2.3, but who wants to run that now? :) To get my G400Max working, I had to load kernel modules agpgart and mga. At that point, using the Matrox driver seemed to make most things go. (q3a crashes after several minutes of play, UT doesn't even run, but the screensavers seemed accelerated.. :) FYI, another partly related problem I've run into is that the mesag3 package contains libGL and libGLU but the xlibmesa3 package only contains libGL. What package is supposed to provide libGLU when xlibmesa3 is used? As for libGLU, this has been hashed out many times in the past on this list. The short answer is, it isn't yet provided by the xf86 source, and until they provide it, branden has suggested a work around. It seemed like too much work to me, so I figured I would wait. :) Check the archives, they will have his suggestion. HTH
Re: Updated Debian XFree86 4.x mini-FAQ and status report
Hello Branden, Hello all, Here is a list of issues that are delaying official Debian XFree86 4.x packages: * The Mesa problem (specifically, the lack of libGLU.so) really has to be sorted out upstream if Debian is going to have a sensible handling of Mesa in our distribution. Alternatively, I can stop shipping the Mesa stuff altogether in the XFree86 packages until support is ready, but this will pretty much leave DRI out of the picture. I'd appreciate feedback on doing this. The XFree86 versions of the Mesa and OSMesa libraries can be added into woody at a later date without causing any real disruption. I'd appreciate feedback on the possibility of releasing 4.0.1-1 (or 4.0.2-1, or whatever) without the XFree86 version of Mesa. What little feedback I've had so far indicates that people would rather wait for upstream to resolve this, so that we ship XFree86 with its own version of libGLU. Please don't let DRI out of the picture. I´m waiting for XFree 4.0.x in Debian-Woody because of the DRI support for my brand new Voodoo 4 Card. I have installed phase2v12 debs and kernel 2.2.18pre11 and got working DRI rendering after some fiddeling (libs manually installed) with glide3 and libGLU.so . This installion is on a 540MB MO Disk on top of a fresh potato install. (Leaved my Woody box untouched). My suggestion so far: Besides the manual installation of some libs phase2v12 installs and work pretty good. My guess: Many Debian User want powerfull 3D support in the next XFree86 debs and therefore wants DRI support. If DRI is not supported most users can stick with XFree 3.3.6. Greetings R. Stallknecht
[feczo@koli.kando.hu: Re: Bugreport Xfree 4.0.1c]
- Forwarded message from Feczak Szabolcs [EMAIL PROTECTED] - From: Feczak Szabolcs [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: Re: Bugreport Xfree 4.0.1c Date: Fri, 6 Oct 2000 09:37:17 +0200 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i In-Reply-To: [EMAIL PROTECTED]; from [EMAIL PROTECTED] on Fri, Oct 06, 2000 at 01:52:22AM -0500 On Fri, Oct 06, 2000 at 01:52:22AM -0500, Branden Robinson wrote: On Fri, Oct 06, 2000 at 12:22:47AM +0200, Feczak Szabolcs wrote: XFree86 Version 4.0.1c / X Window System [...] When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] I did :) You might consider mentioning what you were doing when the server crashed... As I remember I played with gimp in woody. -- =-=-=-=-=-=-=-=-=-=- - F - 3 - C - Z - 0 - =-=-=-=-=-=-=-=-=-=- - End forwarded message - -- G. Branden Robinson| Debian GNU/Linux | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://deadbeast.net/~branden/ | pgp9a7VXrxSUC.pgp Description: PGP signature
Re: xlibs 40.1-0phase2v13 break xawtv
On Fri, Oct 06, 2000 at 01:56:02AM -0500, Branden Robinson wrote: On Thu, Oct 05, 2000 at 01:03:36AM -0400, Decklin Foster wrote: Robert Vollmert [EMAIL PROTECTED] writes: Error: XtMakeGeometryRequest - parent not composite Actually, this is not just happening with xawtv, but any xaw menu. It appears to be an upstream problem; send your report there. Are you using phase2v13? If not, please try it, because: 732. Fixed handling of XtMakeGeometryRequest() to test for parent belonging to subclass of composite class only if the widget itself is managed. This follows the specs more closely. (Keith Packard). If you already are using v13, then it is possible the client is coded wrongly. Or maybe Keith messed up (possible, but unusual). I am running kernel-2.4.0-test9 x phase2v13 xawtv 3.22 and I don't experience any problems watching tv. -ff -- Florian Friesdorf [EMAIL PROTECTED] OpenPGP key available on public key servers -- Save the future of Open Source -- - Online-Petition against Software Patents - -- http://petition.eurolinux.org --- pgpxXtx8KvGVM.pgp Description: PGP signature
Re: xlibs 4.0.1-0phase2v13 break xawtv
On Fri, Oct 06, 2000 at 11:50:27AM +0200, Robert Vollmert wrote: On Fri, Oct 06, 2000 at 01:56:02AM -0500, Branden Robinson wrote: Are you using phase2v13? If not, please try it, because: 732. Fixed handling of XtMakeGeometryRequest() to test for parent belonging to subclass of composite class only if the widget itself is managed. This follows the specs more closely. (Keith Packard). If you already are using v13, then it is possible the client is coded wrongly. Or maybe Keith messed up (possible, but unusual). I have these problems only when using v13, previous (at least v12) packages work fine. Apart from xawtv, xgammon and freeciv-xaw3d also fail, while xvile-xaw works. I also compiled xawtv without xaw3d support, but that doesn't seem to make a difference. With v12, all these programs work. Well, what I was trying to tell you is that the above mentioned fix appeared only in v13. So either Keith's patch is wrong, or xawtv, xgammon, and freeciv-xaw3d are coded wrongly. I suggest you contact the authors of these programs and see what they think. -- G. Branden Robinson |I must despise the world which does not Debian GNU/Linux|know that music is a higher revelation [EMAIL PROTECTED] |than all wisdom and philosophy. http://www.debian.org/~branden/ |-- Ludwig van Beethoven pgpHtUpXhEEPC.pgp Description: PGP signature
Re: xlibs 40.1-0phase2v13 break xawtv
[I didn't get the original for some reason] On Fri, Oct 06, 2000 at 01:56:02AM -0500, Branden Robinson wrote: On Thu, Oct 05, 2000 at 01:03:36AM -0400, Decklin Foster wrote: Robert Vollmert [EMAIL PROTECTED] writes: Error: XtMakeGeometryRequest - parent not composite Actually, this is not just happening with xawtv, but any xaw menu. It appears to be an upstream problem; send your report there. Are you using phase2v13? If not, please try it, because: Yes, I'm using v13. I've tried recompiling some trival menu code (same error); I don't have xvile-xaw handy. I will search out that patch and take a look. -- There is no TRUTH. There is no REALITY. There is no CONSISTENCY. There are no ABSOLUTE STATEMENTS. I'm very probably wrong. -- BSD fortune(6)
phase2v13 problems
I had been using phase2v3 in dual head mode on my G400 using the matrox supplied mga_drv.o released at the end of august. After upgrading to phase2v13 I get the following server output (still using the matrox supplied mga_drv.o): XFree86 Version 4.0.1c / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 28 August 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.17pre10 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Fri Oct 6 19:11:24 2000 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout dualhead (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor1 (**) | |--Device G400-1 (**) |--Screen Screen1 (1) (**) | |--Monitor Monitor2 (**) | |--Device G400-2 (**) |--Input Device Mouse (**) |--Input Device Keyboard (WW) The directory /usr/X11R6/lib/X11/fonts/local/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/CID/ does not exist. Entry deleted from font path. (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.0.1c, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.0.1c, module version = 0.1.0 (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (--) PCI: (0:8:0) BrookTree unknown chipset (0x036e) rev 2, Mem @ 0xea00/12 (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 4, Mem @ 0xe800/25, 0xe400/14, 0xe500/23 (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.1.7 (II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a (II) Module speedo: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Module pex5: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.13.0 (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/drivers/linux/v4l_drv.o (II) Module v4l: vendor=The XFree86 Project compiled for 4.0.1c, module version = 0.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/mga_drv.o (II) Module mga: vendor=The XFree86 Project compiled for 4.0.1, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.0.1c, module version = 1.0.0 (II) v4l driver for Video4Linux (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag100, mgag200, mgag200 PCI, mgag400 (**) Chipset override: mgag400 (**) Chipset mgag400 found (**) Chipset override: mgag400 (**)
Re: Trouble with DRI on G200
On Fri, Oct 06, 2000 at 11:59:28AM -0600, Joshua Shagam wrote: Did you later see 'DMA initialization failed?' That would be the No. Here are the DMA messages I got: (II) MGA(0): [drm] Registers = 0xe400 [drm] drmAgpEnabled succeeded (II) MGA(0): WARP Microcode Loaded (II) MGA(0): [drm] calced backoffset: 0x22f000 (II) MGA(0): [drm] added 31 65536 byte DMA buffers (II) MGA(0): [drm] Mga Dma Initialization start (II) MGA(0): [drm] Mga Dma Initialization done (II) MGA(0): [drm] Initialized Dma Engine (II) MGA(0): [drm] dma control initialized, using IRQ 11 (II) MGA(0): visual configs initialized (II) MGA(0): Using 128 lines for offscreen memory. (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) This issue is mostly moot anyway. My main point in trying XFree86 4.0.x with the G200 was to smooth the transition when I move my hard disks to my new system which has a GeForce2/MX. What I do is I use the libGL from xlibmesa3 and the libGLU compiled from Mesa's sources (which I already have on-hand because of formerly using Utah-GLX). I just copied libGLU from mesag3 to /usr/local/lib. On Fri, Oct 06, 2000 at 01:02:12PM -0500, Branden Robinson wrote: The patches you're talking about aren't really Debian-specific: Debian-specifici was probably a poor choice of words. My intent was that the change was not in the plain 4.0.1 upstream version. Please review my mini-FAQ, last posted to this list on Oct 1. Sorry about that. I read your mini-FAQ when it was sent, but I didn't understand the issue and I also didn't think I was using anything that needed libGLU either so I didn't worry about it. Anyway, have you considered using a dpkg-diversion? xlibmesa3 could divert any existing libGL out of the way but leave libGLU in place. David -- David Engel [EMAIL PROTECTED]
