Re: Problem with AMD HD 5670 GPU
On 2019-07-05 5:28 p.m., Philippe Lefèvre wrote: > Sorry, error into the subject > please read Problem with AMD HD 5670 GPU > > Hi all, > > I am stuck with my graphic card since I upgraded my Linux box from > Jessie to Stretch. > Before debian upgade, I had the fglrx proprietary driver which was > removed when upgrade. > > Now the issue is I can't get some structure rendering > For example, in a online game (Champions Of Regnum) my characters are > now nude and other players are not diplayed. > > Is there anyone who knows better than me the arcannes of graphics cards > parameters and who could help me to solve my problem? > (if possible using open source softwares) > > Regards, > Philippe > > > Here are some details of my installation: > > # lsb_release -a | grep Desc > Debian GNU/Linux 9.9 (stretch) > > My card is an AMD HD 5670, my distro is Debian Stretch up to date > # lspci -nn | grep VGA > 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] [1002:68d8] > > As there is no more proprietary drivers available for Debian, I tried to > compile AMD Catalyst(TM) Proprietary Driver-15.201.1151 > The compilation checks fails due to the X server version which is too > high on my box. > # error: Detected X Server version 'XServer 1.19.2_64a' is not supported. > Supported versions are X.Org 6.9 or later, up to XServer 1.10 > (default:v2:x86_64:lib:XServer 1.19.2_64a:none:4.9.0-9-amd64:) > Installation will not proceed. > > The non-free package firmware-amd-graphics (20161130-5) doesn't contain > any driver for HD5670 > > I then installed the recommended open source packages. > > I removed /etc/X11/xorg.conf > > # glxinfo | grep OpenGL > OpenGL vendor string: X.Org > OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.49.0 / > 4.9.0-9-amd64, LLVM 3.9.1) > OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 > OpenGL core profile shading language version string: 3.30 > OpenGL core profile context flags: (none) > OpenGL core profile profile mask: core profile > OpenGL core profile extensions: > OpenGL version string: 3.0 Mesa 13.0.6 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 > OpenGL ES profile extensions: > > What is installed : > [...] I'd try upgrading these and (at least) libgl1-mesa-dri to stretch-backports, and see if it works better then. -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer
Re: problem with radeon since mesa > 18.0.5-1
2018-07-17 11:21 GMT+02:00 Michel Dänzer : > On 2018-07-16 08:31 PM, Jérémy Lal wrote: > > After login on a x11 gnome gdm3 sesssion, > > display hangs, crash, becomes black, and occasionally freeze the > computer. > > Which is an imac 27" 2011. > > But > > - i'm not sure it's a mesa bug, maybe a linux kernel bug triggered by the > > mesa update > > - i think it's appearing only on large displays like 2560x1440. > > - i don't know how to get logs from previous boots with journalctl > > > > I remember something about "cs ring radeon", etc.. > > Sounds like https://bugs.freedesktop.org/105381 , fixed in > xf86-video-ati upstream Git master. > right ! Using master@499d2f9d (july 17th) and it works again. Thanks.
Re: problem with radeon since mesa > 18.0.5-1
On 2018-07-16 08:31 PM, Jérémy Lal wrote: > After login on a x11 gnome gdm3 sesssion, > display hangs, crash, becomes black, and occasionally freeze the computer. > Which is an imac 27" 2011. > But > - i'm not sure it's a mesa bug, maybe a linux kernel bug triggered by the > mesa update > - i think it's appearing only on large displays like 2560x1440. > - i don't know how to get logs from previous boots with journalctl > > I remember something about "cs ring radeon", etc.. Sounds like https://bugs.freedesktop.org/105381 , fixed in xf86-video-ati upstream Git master. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
Re: problem mounting a floppy disk
On Wed, Sep 07, 2005 at 11:45:57PM -0300, Roberto Fabbrin wrote: i just move to debian, like couple weeks ago, i just can't mount a simple floppy, because there is no /dev/fd0, i wish someone could help me. Thanks, Roberto. Hi roberto, ... Please try debian-user@lists.debian.org, as your question is highly off-topic here, debian-x is the X windows related mailing list. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem in new BTS feature.
El Martes, 19 de Julio de 2005 13:43, David Martínez Moreno escribió: Package: bugs.debian.org Severity: important Hello. In the XSF we have detected a problem with the new versioning feature. We have 4 merged bugs in the xserver-xorg package, namely #318218, #318231, #318271 and #318405. They were closed by the 6.8.2.dfsg.1-3 release, but users report failure in the fix, so I sent a mail to [EMAIL PROTECTED]: The bug associated to this issue is #319037. Ender. -- You idiots, you've captured their stunt doubles. -- Dark Helmet (Spaceballs). -- Debian developer pgp7y6qqWklxF.pgp Description: PGP signature
Re: Problem
On Sat, Jul 03, 2004 at 12:09:35PM +0200, Luigi Di Primio wrote: I tried the knoppix live-cd, but there are some problem with my graphic card. Can you help me?? XFree86 Version 4.3.0.1 (Debian 4.3.0-0pre1v5 20031207095205 [EMAIL PROTECTED]) This version of the XFree86 packages is pretty old by now. xfree86 (4.3.0-0pre1v5) experimental; urgency=low [...] -- Branden Robinson [EMAIL PROTECTED] Fri, 5 Dec 2003 21:18:07 -0500 (II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(1:0:0) nVidia Corporation NV28 [GeForce4 Ti 4800 SE] rev 161, Mem @ 0xd600/24, 0xd800/27, BIOS @ 0xd7fe/17 [...] (II) LoadModule: GLcore (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a Fatal server error: _LoaderFileToMem() read() failed: Input/output error 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] Gee, thanks, Knoppix, for shipping an experimental version of the XFree86 packages meant for Debian internal beta testing without even bothering to update the contact address. We'll probably be getting misguided bug reports from Knoppix users for years to come. At any rate, I've never seen this exact type of failure before. It's possible that either: 1) an incompatible version of the binary-only NVidia GLX modules is on the Knoppix CD or your system; 2) your chipset simply is not supported by this version of XFree86; try a more recent version, such as the one in Debian sid (unstable) -- G. Branden Robinson| There's something wrong if you're Debian GNU/Linux | always right. [EMAIL PROTECTED] | -- Glasow's Law http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Re: Problem during xserver-xfree86_4.3.0.dfsg.1-3 installation
On Sat, May 29, 2004 at 12:55:51AM +0200, jjluza wrote: It seems there is a problem with the preinst script of this package. I get it from incoming.debian.org When I try to install it, it freezes like that : # dpkg -i xserver-xfree86_4.3.0.dfsg.1-3_i386.deb (Lecture de la base de données... 151846 fichiers et répertoires déjà installés.) Préparation du remplacement de xserver-xfree86 4.3.0.dfsg.1-2 (en utilisant xserver-xfree86_4.3.0.dfsg.1-3_i386.deb) ... If I run ps aux, I get these lines : root 5464 30.0 7.1 38596 37044 pts/7 S+ 00:46 0:00 dpkg -i xserver-xfree86_4.3.0.dfsg.1-3_i386.deb root 5483 39.0 1.8 11288 9492 pts/7S+ 00:46 0:00 /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/tmp.ci/preinst u root 5489 0.0 0.2 2996 1544 pts/7S+ 00:46 0:00 /bin/sh /var/lib/dpkg/tmp.ci/config configure 4.3.0.dfsg.1-2 root 5518 0.0 0.1 2060 768 pts/7S+ 00:46 0:00 grep -q system type.*:.*SGI Indigo2 I can't tell more, but ask me if you need more information. This was fixed in 4.3.0.dfsg.1-4. xfree86 (4.3.0.dfsg.1-4) unstable; urgency=medium * The thanks for the 'testing' release. Changes by Branden Robinson: * Fix hang in xserver-xfree86 config script by telling grep what file to search. -- Branden Robinson [EMAIL PROTECTED] Fri, 28 May 2004 21:49:53 -0500 I apologize for the inconvenience. -- G. Branden Robinson| If you're handsome, it's flirting. Debian GNU/Linux | If you're a troll, it's sexual [EMAIL PROTECTED] | harassment. http://people.debian.org/~branden/ | -- George Carlin signature.asc Description: Digital signature
Re: problem with X-4.3 + flat panels using dvi cables and nvidia graphics card
On Thu, May 13, 2004 at 04:21:10PM -0400, James D. Freels wrote: I am having a nagging problem with my Nvidia-GeForce FX 5200 video card. I am hoping to get some help from this forum(s) on how to correct the problem(s). Please reply directly or through the forum with advise on this problem. [The following is a form letter.] Hello, You recently sent an off-charter message to the debian-x mailing list. First, I will offer an explanation of what this mailing list's purpose is; I will then suggest some alternative forums for your message or concern. The full charter of the mailing list follows. This list is for the discussion and support of the X Window System within Debian. Issues of maintenance and porting of Debian's XFree86 packages are germane here, as are discussions of possible Debian policy mechanisms for ensuring the smooth interoperation of packages that use the X Window System, particularly widget sets, desktop environments, window managers, display managers, and packages that provide fonts for the X Window System. In particular, individuals involved with building official Debian XFree86 packages for any architecture are invited to join, as are those with various graphics hardware who seek to reproduce and/or fix bugs in the X server. This is not a user support list; this list is intended for those who deal with the source code of any of the X Window System components mentioned above. If you are experiencing a problem, the first thing to check is the Debian X FAQ. This FAQ is available on the World Wide Web: http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ The FAQ is also available on any Debian system that has the xfree86-common package installed. You can use the command dpkg --status xfree86-common at a shell prompt to determine whether you have the xfree86-common package installed (this technique works with any other package name as well). For instance, when I run this command I see the following: $ dpkg --status xfree86-common Package: xfree86-common Status: install ok installed (followed by additional information about the package) If xfree86-common is installed, you can view the Debian X FAQ in a variety of ways, since it is a gzipped (compressed) text file. The path to the FAQ is /usr/share/doc/xfree86-common/FAQ.gz. Here's one method for viewing it: $ zmore /usr/share/doc/xfree86-common/FAQ.gz Debian X Window System Frequently Asked Questions (FAQ) List Copyright 1998-2002 Branden Robinson. This document is licensed under the GNU General Public License, version 2 (see /usr/share/common-licenses/GPL). By its nature, this document is not complete. If your question is not answered here, try /usr/share/doc/packagename/README.Debian (and other files in the package's doc directory), manual pages, and the debian-user mailing list. See http://www.debian.org/ for more information about the Debian mailing lists. (followed by the rest of the FAQ) If the FAQ does not satisfactorily answer your question, the primary Debian users' support forum is the debian-user mailing list. You can learn more about this list at: http://lists.debian.org/debian-user/ If you have already tried that mailing list, and/or your machine does *NOT* use an Intel-x86 compatible CPU (such as a Pentium or AMD Athlon chip), you may also want to peruse one of Debian's architecture-specific mailing lists: http://lists.debian.org/debian-alpha/ http://lists.debian.org/debian-arm/ http://lists.debian.org/debian-hppa/ http://lists.debian.org/debian-ia64/ http://lists.debian.org/debian-m68k/ http://lists.debian.org/debian-mips/ http://lists.debian.org/debian-powerpc/ http://lists.debian.org/debian-sparc/ http://lists.debian.org/debian-superh/ Before sending a message to one of the mailing lists, it's wise to try using the search interface; in many cases, your problem has been experienced before by other people, and a solution, workaround, or explanation may already be available! http://lists.debian.org/search.html If the search engine turns up nothing, you should know whether or not you're subscribed to a mailing list before sending a message to it. If you are not subscribed, make *certain* that you ask for private copies of replies to your message. Debian's standard practice is to reply only to mailing lists (this cuts down on Internet traffic and annoying bounce messages). If you want people to deviate from this standard practice you should ask them to do so. (Advanced mail users should set a Mail-Followup-To header that includes both the list address and their own address.) Finally, if you have found a problem in Debian's XFree86 packages (and especially if Debian experts on one or more of the above mailing lists agree), you should file a bug report with the Debian Bug Tracking System. One of the best ways to do this is with the reportbug package and command of the same name. One way to install reportbug
Re: problem with left-handed mouse on X - is GPM to blame or is it X?
On Mon, May 10, 2004 at 07:28:57PM -0400, Zephaniah E. Hull wrote: Please see the last message, where I covered just this. Raw mode repeats byte for byte, it does not attempt to do ANYTHING to them. In addition, he is repeating a PS2 protocol, with all the problems involved in that. I will say it once more, this is a case of user error. The proper configuration for this is having gpm not repeat, and both X and gpm reading from /dev/input/mice, with X doing some button remapping in whatever manner is now suggested. Okay. I checked the manpage for this information and did not find it. I also found that the gpm(8) manpage is ugly. So I did something about it. Please see two attached files; one is a diff which patches the manpage to simply document these two minor points. The other one overhauls the manpage completely. I looked into the source package, but the method used to generate both Texinfo and Roff document source from a single file is truly grody. If 'xmodmap -e pointer = 3 2 1' is no longer the suggested means, what is? That's a good question, and I don't have the answer at present. -- G. Branden Robinson| You are not angry with people when Debian GNU/Linux | you laugh at them. Humor teaches [EMAIL PROTECTED] | them tolerance. http://people.debian.org/~branden/ | -- W. Somerset Maugham --- gpm.8~ 2004-05-20 15:05:38.0 -0500 +++ gpm.8 2004-05-20 15:09:34.0 -0500 @@ -145,6 +145,10 @@ normal sequence, `321' can be used by left-handed people, and `132' can be useful with two-button mice (especially within Emacs). All the button permutations are allowable. +.IP +.B Note: +This option is ignored if the \(oq\-R\(cq option is used with the parameter +\(oqraw\(cq. .TP -d \fIdelta\fP Set the delta value. When a single motion event @@ -231,6 +235,9 @@ an easy way to manage those stupid dual-mode mice which force you to keep the middle button down while changing video mode. The option is forced on by the `-M' option. +.IP +.B Note: The only repeat type reliably supported by version 4.3 or later of +.B the XFree86 X server is \(oqms3\(cq. .TP -s \fInumber\fP Set the sample rate for the mouse device. .TH gpm 8 20 May 2004 GPM General Purpose Mouse 1.19.6 .SH NAME gpm \- cut\-and\-paste utility and mouse server for virtual consoles .SH SYNOPSIS .B gpm [ .I options ] .br .SH DESCRIPTION GPM (General Purpose Mouse) tries to be a useful mouse server for applications running on the Linux console. The information below is extracted from the Texinfo documentation, which is the preferred source of information. .PP GPM makes it easy to select and copy regions of text on the virtual console, much as is done in graphical programs such as word processors. Text regions are highlighted with the mouse in an area called the \(oqselection buffer\(cq, or just \(oqselection\(cq. The term \(oqcut\-and\-paste\(cq can be a little misleading, because GPM never deletes text from the console. GPM is actually more of a .RI \(oq copy \-and\-paste\(cq utility. .PP The .B gpm executable is meant to act like a daemon (thus, \(oqgpmd\(cq would be a better name for it). .SS Operation To select text press and hold the left mouse button and drag the mouse. .PP On three\-button mice, click the middle button to paste text in the same or another console. The right button is used to extend the selection, like in .BR xterm (1x). .PP Two\-button mice use the right button to paste text. .PP Double\- and triple\-clicks of the left button select whole words and whole lines. Use of the .B \-p option is recommended for best visual feedback. Which characters constitute part of a \(oqword\(cq can be changed with the .B \-l option. .PP If a trailing space after the visible content of a line is highlighted, and if there is no other text on the remainder of the line, the rest of the line will be selected automatically. If a number of lines are selected, highlighted trailing spaces on each line will be removed from the selection buffer. .PP Any output on the virtual console holding the selection will clear the highlighted selection from the screen, to maintain integrity of the display, although the contents of the selection buffer will be unaffected. .PP The selection mechanism is disabled if the controlling virtual console is placed in graphics mode (for example when running an X server), and is re\-enabled when text mode is resumed \(em but see the \(oqBUGS\(cq section below. .SS Special Commands GPM has the ability to execute special commands via mouse actions under certain circumstances. The special commands default to rebooting and halting the system, but the user can specify his or her personal choice. The ability to invoke commands using only the mouse can be a handy one, because it allows you to shut the system down cleanly when the keyboard is locked and no network is available to restore the system to a sane
Re: Problem with MGA driver in X
On Wednesday 19 May 2004 01:43, Xavier LaRue wrote: Hi, I was just playing with OpenGL using my Matrox G400 when I came over a problem that apear with the update of X to 4.3.0 Using this program http://nehe.gamedev.net/data/lessons/linuxsdl/lesson02.tar.gz which is suposed to display a white triangle and a white quad. The quad don't appear. If I move the code place to draw the Quad first, the triangle doesn't appear. I would like to know if somone have experimented the problem and if somone have a solution. Thank you in advence Xavier LaRue Have you tried to call glFlush() before swapping the buffers ? I bet this will solve the problem. Damien
Re: problem with left-handed mouse on X - is GPM to blame or is it X?
On Fri, Apr 30, 2004 at 10:14:32AM +0300, Martin-Éric Racine wrote: 1) The information about using GPM's -B option is incorrect. As you can see from the enclosed configs, I already use -B 321, but this is ignored by X. Zeph, can you comment on this? Is -B 321 really broken, or only broken for the raw repeat type? I think I can imagine why it might not work for the raw repeat type. 2) xmodmap has been broken since XFree 4.3.0. Any xmodmap receipe I had left from 4.2.1 either results in broken keyboard maps or in is simply ignored. This is because the XKB configuration data has been overhauled. xmodmap has been deprecated for years. Honnestly, the correct action would be for X to follow the button order configured for GPM. I really wonder why that fails. If you use the raw repeat type, there may be no way it *can* work. Zeph, can you help clear up this issue? -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy [EMAIL PROTECTED] |spot on the pavement, where used to http://people.debian.org/~branden/ |lie the carcass of a dead horse. signature.asc Description: Digital signature
Re: problem with left-handed mouse on X - is GPM to blame or is it X?
On Mon, May 10, 2004 at 04:10:18PM -0500, Branden Robinson wrote: On Fri, Apr 30, 2004 at 10:14:32AM +0300, Martin-?ric Racine wrote: 1) The information about using GPM's -B option is incorrect. As you can see from the enclosed configs, I already use -B 321, but this is ignored by X. Zeph, can you comment on this? Is -B 321 really broken, or only broken for the raw repeat type? I think I can imagine why it might not work for the raw repeat type. Honnestly, the correct action would be for X to follow the button order configured for GPM. I really wonder why that fails. If you use the raw repeat type, there may be no way it *can* work. Zeph, can you help clear up this issue? Please see the last message, where I covered just this. Raw mode repeats byte for byte, it does not attempt to do ANYTHING to them. In addition, he is repeating a PS2 protocol, with all the problems involved in that. I will say it once more, this is a case of user error. The proper configuration for this is having gpm not repeat, and both X and gpm reading from /dev/input/mice, with X doing some button remapping in whatever manner is now suggested. If 'xmodmap -e pointer = 3 2 1' is no longer the suggested means, what is? -- 1024D/E65A7801 Zephaniah E. Hull [EMAIL PROTECTED] 92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801 CCs of replies from mailing lists are requested. Mercury Knghtbrd: Eww, find a better name, the movie sucked.. G Knghtbrd Mercury: The engine is better than the movie
Re: problem with left-handed mouse on X - is GPM to blame or is it X?
[Zeph Hull dropped from Cc.] On Thu, Apr 29, 2004 at 12:29:35PM +0300, Martin-Éric Racine wrote: Greetings, Given how everyone in this family is left-handed, I recently got around inverting the order of the mouse buttons in GPM; works great in console. Since GPM is setup as a repeater for X, I thought that X would also end up defaulting to inverted button order, but it doesn't. I haven't found any option in X to configure the button order and Googling didn't tell me anything relevant about perhaps selecting a different protocol in GPM to get everything working in X the same way it does on console. Would anybody happen to have a cure for this? There is information in the Debian X FAQ about this. /usr/share/doc/xfree86-common/FAQ.gz http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ Please let us know if it is insufficient. -- G. Branden Robinson|Religion consists in a set of Debian GNU/Linux |things which the average man thinks [EMAIL PROTECTED] |he believes and wishes he was http://people.debian.org/~branden/ |certain of. -- Mark Twain signature.asc Description: Digital signature
Re: problem with left-handed mouse on X - is GPM to blame or is it X?
On Thu, Apr 29, 2004 at 12:29:35PM +0300, Martin-?ric Racine wrote: Greetings, Given how everyone in this family is left-handed, I recently got around inverting the order of the mouse buttons in GPM; works great in console. Since GPM is setup as a repeater for X, I thought that X would also end up defaulting to inverted button order, but it doesn't. repeat_type=raw type=imps2 Section InputDevice Option Device/dev/gpmdata Option Protocol ImPS/2 EndSection impolite rant removed This is user error. The raw repeat type is something that I am beginning to think is more of a bug then a feature, it does a byte for byte repeat, making no changes to the byte stream. Further more, it seems to be most commonly used with the PS/2 protocols, which, is another rant about two-way communications on a FIFO. Kill the repeat type, have X read from /dev/input/mice as well, and use xmodmap in your ~/.xsession. -- 1024D/E65A7801 Zephaniah E. Hull [EMAIL PROTECTED] 92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801 CCs of replies from mailing lists are requested. VOICE MODE=Pitr So, you are thinking am Communist ? Deal, Comerade ! /VOICE -- Chris on ASR. signature.asc Description: Digital signature
Re: problem with dpkg-reconfigure and noninteractive frontend
On Sat, Apr 24, 2004 at 02:43:25PM -0700, Don Armstrong wrote:
On Sat, 24 Apr 2004, Denis Barbier wrote:
When a package is reconfigured, the new debconf settings and current
configuration files are available, but previous debconf settings are
not and you cannot determine that there have been no local changes.
While the former is true[1], the latter is not. See, for example, how
xserver-xfree86 deals (perhaps suboptimally) with this situation.
It's going to be dealing with it a little less suboptimally in the near
future.
See attachment (you may want to scroll to the bottom).
--
G. Branden Robinson|It's like I have a shotgun in my
Debian GNU/Linux |mouth, I've got my finger on the
[EMAIL PROTECTED] |trigger, and I like the taste of
http://people.debian.org/~branden/ |the gunmetal. -- Robert Downey, Jr.
#!/bin/sh
# Debian xserver-xfree86 package configuration script
# Copyright 2000--2004 Branden Robinson.
# Licensed under the GNU General Public License, version 2. See the file
# /usr/share/common-licenses/GPL or http://www.gnu.org/copyleft/gpl.txt.
# $Id: xserver-xfree86.config.in 1188 2004-03-25 23:06:35Z branden $
set -e
# source debconf library
. /usr/share/debconf/confmodule
THIS_PACKAGE=xserver-xfree86
THIS_SCRIPT=config
#INCLUDE_SHELL_LIB#
CONFIG_DIR=/etc/X11
SERVER_SYMLINK=$CONFIG_DIR/X
XF86CONFIG=$CONFIG_DIR/XF86Config-4
CONFIG_AUX_DIR=/var/lib/xfree86
SERVER_SYMLINK_CHECKSUM=$CONFIG_AUX_DIR/${SERVER_SYMLINK##*/}.md5sum
XF86CONFIG_CHECKSUM=$CONFIG_AUX_DIR/${XF86CONFIG##*/}.md5sum
THIS_SERVER=/usr/bin/X11/XFree86
NCARDS=0
NSERVERS=0
NDRIVERS=0
MULTIHEAD=
# get machine architecture
ARCH=$(dpkg --print-installation-architecture)
discover_video () {
# wrapper for discover command that can distinguish Discover 1.x and 2.x
# Ugh, Discover 1.x didn't exit with nonzero status if given an unrecongized
# option!
DISCOVER_TEST=$(discover --version 2/dev/null)
if expr $DISCOVER_TEST : 'discover 2.*' /dev/null 21; then
# Discover 2.x
# XXX: this is sort of nasty
VENDOR_MODEL_FILE=$(tempfile)
SERVER_FILE=$(tempfile)
DRIVER_FILE=$(tempfile)
CMD=discover --type-summary display
run $CMD $VENDOR_MODEL_FILE
CMD=discover --data-path=xfree86/server/name \
--data-version=${SOURCE_VERSION%-*} display
run $CMD $SERVER_FILE
CMD=discover --data-path=xfree86/server/device/driver \
--data-version=${SOURCE_VERSION%-*} display
run $CMD $DRIVER_FILE
DISCOVERED_VIDEO=$(paste $VENDOR_MODEL_FILE $SERVER_FILE $DRIVER_FILE)
rm -f $VENDOR_MODEL_FILE $SERVER_FILE $DRIVER_FILE
else
# must be Discover 1.x
DISCOVERED_VIDEO=$(run discover --disable=serial,parallel \
--format=%V %M\t%S\t%D\n video 2/dev/null)
fi
echo $DISCOVERED_VIDEO
}
validate_string_db_input () {
# Syntax: validate_string_db_input priority template
#
# validate string input; can't have doublequotes
# If $MAY_BE_NULL is a non-null value (e.g., yes), the string may be null.
if [ $# -ne 2 ]; then
internal_error validate_string_db_input() called with wrong number of \
arguments: $*
fi
PRIORITY=$1
TEMPLATE=$2
db_get $TEMPLATE
SAFE=$RET
set +e
while :; do
db_input $PRIORITY $TEMPLATE
# is the question going to be asked?
if [ $? -eq 30 ]; then
break # no; bail out of validation loop
fi
db_go
db_get $TEMPLATE
if [ -n $RET ]; then
if ! expr $RET : '.*.*' /dev/null 21; then
break # valid input
else
ERROR=xserver-xfree86/config/doublequote_in_string_error
fi
else
if [ -n $MAY_BE_NULL ]; then
break # valid (null) input
else
ERROR=xserver-xfree86/config/null_string_error
fi
fi
# we only get to this point if the input was invalid; restore the known
# good value in case we are interrupted before the user provides a valid
# one
db_set $TEMPLATE $SAFE
db_fset $TEMPLATE seen false
# now show the user the error message
db_fset $ERROR seen false
db_input critical $ERROR
db_go
done
set -e
}
validate_numeric_db_input () {
# Syntax: validate_numeric_db_input priority template
#
# validate numeric input; must have only digits, can be null
if [ $# -ne 2 ]; then
internal_error validate_numeric_db_input() called with wrong number of \
arguments: $*
fi
PRIORITY=$1
TEMPLATE=$2
db_get $TEMPLATE
SAFE=$RET
set +e
while :; do
db_input $PRIORITY $TEMPLATE
# is the question going to be asked?
if [ $? -eq 30 ]; then
break # no; bail out of validation loop
fi
db_go
db_get $TEMPLATE
if [ -z $RET ] || expr $RET : [0-9]\+$ /dev/null 21; then
break # valid input
fi
# we only get to this point if the input was invalid; restore the known
# good value in case we are interrupted before the
Re: problem with
Hi, On Thu, 2004-03-25 at 13:22, Christian Stalp wrote: Hello together, I have a problem with the X-Server on my Notebook. A Asus 3500D with a synaptics-touchpad. I don't know if I have to subscribe to this list althought Im a normal X-User, however at the end of X-dump there was a announcement to send the full output to this list. I send you my XF86Config-4 too. What means loader failed 136233848? I hope anybody can help me what went wrong on my installation!? quoted from your attachments: XFree86 Version 4.2.1.1 (Debian 4.2.1-3.bunk.4 20030323114243 bunk@) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 2002 /Quote This version (Debian 4.2.1-3.bunk.4) has never been an official debian release. You won't get any help, unless you're installing official debian XFree86 packages... cheers. Christian
Processed: Re: Problem solved. Reassign?
Processing commands for [EMAIL PROTECTED]: reassign 239448 capplets-data Bug#239448: libxft2: Fails to render fonts, making GTK+ 2 and related system unusable. Bug reassigned from package `libxft2' to `capplets-data'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Problem with new libc, locales and X
On Tue, Aug 26, 2003 at 11:27:34AM +0200, Jean-Christophe Dubacq wrote: Hi! I run XFree 4.3.0. I tested the new libc (2.3.2-3) and accordingly new locale package (and new gdm package). For european countries, LANG is now set to something like [EMAIL PROTECTED] (instead of the former [EMAIL PROTECTED]). Xlib does not recognize this kind of locale. More important, fonts are not found any more (probably no matching charset) because of this. This leads to really poor experience. Any thoughts on this ? I will continue my soliloque: it works perfectly when adding the correct stuff to /usr/X11R6/lib/X11/locale/locale.alias (see attached file) Current versions: libc6: Installed: 2.3.2-3 Candidate: 2.3.2-3 Version Table: *** 2.3.2-3 0 500 ftp://ftp.fr.debian.org unstable/main Packages 100 /var/lib/dpkg/status xlibs: Installed: 4.3.0-0pre1v1 Candidate: 4.3.0-0pre1v1 Version Table: *** 4.3.0-0pre1v1 0 1 ftp://ftp.debian.org ../project/experimental/main Packages 100 /var/lib/dpkg/status 4.2.1-10 0 500 ftp://ftp.fr.debian.org unstable/main Packages Result of locale: [EMAIL PROTECTED] LC_CTYPE=[EMAIL PROTECTED] LC_NUMERIC=[EMAIL PROTECTED] LC_TIME=[EMAIL PROTECTED] LC_COLLATE=[EMAIL PROTECTED] LC_MONETARY=[EMAIL PROTECTED] LC_MESSAGES=[EMAIL PROTECTED] LC_PAPER=[EMAIL PROTECTED] LC_NAME=[EMAIL PROTECTED] LC_ADDRESS=[EMAIL PROTECTED] LC_TELEPHONE=[EMAIL PROTECTED] LC_MEASUREMENT=[EMAIL PROTECTED] LC_IDENTIFICATION=[EMAIL PROTECTED] LC_ALL= Patch to /usr/X11R6/lib/X11/locale/locale.alias: append [EMAIL PROTECTED]: br_FR.ISO8859-15 [EMAIL PROTECTED]: ca_ES.ISO8859-15 [EMAIL PROTECTED]: de_AT.ISO8859-15 [EMAIL PROTECTED]: de_BE.ISO8859-15 [EMAIL PROTECTED]: de_DE.ISO8859-15 [EMAIL PROTECTED]: de_LU.ISO8859-15 [EMAIL PROTECTED]: el_GR.ISO8859-15 [EMAIL PROTECTED]: en_IE.ISO8859-15 [EMAIL PROTECTED]: es_ES.ISO8859-15 [EMAIL PROTECTED]: eu_ES.ISO8859-15 [EMAIL PROTECTED]: fi_FI.ISO8859-15 [EMAIL PROTECTED]: fr_BE.ISO8859-15 [EMAIL PROTECTED]: fr_FR.ISO8859-15 [EMAIL PROTECTED]: fr_LU.ISO8859-15 [EMAIL PROTECTED]: ga_IE.ISO8859-15 [EMAIL PROTECTED]: gl_ES.ISO8859-15 [EMAIL PROTECTED]: it_IT.ISO8859-15 [EMAIL PROTECTED]: nl_BE.ISO8859-15 [EMAIL PROTECTED]: nl_NL.ISO8859-15 [EMAIL PROTECTED]: oc_FR.ISO8859-15 [EMAIL PROTECTED]: pt_PT.ISO8859-15 [EMAIL PROTECTED]: sv_FI.ISO8859-15 [EMAIL PROTECTED]: sv_SE.ISO8859-15 [EMAIL PROTECTED]: wa_BE.ISO8859-15 [EMAIL PROTECTED]: br_FR.ISO8859-15 [EMAIL PROTECTED]: ca_ES.ISO8859-15 [EMAIL PROTECTED]: de_AT.ISO8859-15 [EMAIL PROTECTED]: de_BE.ISO8859-15 [EMAIL PROTECTED]: de_DE.ISO8859-15 [EMAIL PROTECTED]: de_LU.ISO8859-15 [EMAIL PROTECTED]: el_GR.ISO8859-15 [EMAIL PROTECTED]: en_IE.ISO8859-15 [EMAIL PROTECTED]: es_ES.ISO8859-15 [EMAIL PROTECTED]: eu_ES.ISO8859-15 [EMAIL PROTECTED]: fi_FI.ISO8859-15 [EMAIL PROTECTED]: fr_BE.ISO8859-15 [EMAIL PROTECTED]: fr_FR.ISO8859-15 [EMAIL PROTECTED]: fr_LU.ISO8859-15 [EMAIL PROTECTED]: ga_IE.ISO8859-15 [EMAIL PROTECTED]: gl_ES.ISO8859-15 [EMAIL PROTECTED]: it_IT.ISO8859-15 [EMAIL PROTECTED]: nl_BE.ISO8859-15 [EMAIL PROTECTED]: nl_NL.ISO8859-15 [EMAIL PROTECTED]: oc_FR.ISO8859-15 [EMAIL PROTECTED]: pt_PT.ISO8859-15 [EMAIL PROTECTED]: sv_FI.ISO8859-15 [EMAIL PROTECTED]:
Re: Problem with new libc, locales and X
On Tue, Aug 26, 2003 at 11:27:34AM +0200, Jean-Christophe Dubacq wrote: Hi! I run XFree 4.3.0. I tested the new libc (2.3.2-3) and accordingly new locale package (and new gdm package). For european countries, LANG is now set to something like [EMAIL PROTECTED] (instead of the former [EMAIL PROTECTED]). Xlib does not recognize this kind of locale. More important, fonts are not found any more (probably no matching charset) because of this. This leads to really poor experience. Any thoughts on this ? Strangely enough, this is a rehash of a former major libc upgrade. http://lists.debian.org/debian-x/2000/debian-x-200012/msg00152.html The solution is probably to append a few lines to /usr/X11R6/lib/X11/locale/locale.alias I can provide a patch, if necessary. But shouldn't X11 try to read the locale correctly at first view? I think I already worked on this once. -- JCD
Re: Problem with Sony Vaio PCG-R505GL
I wrote: X doesn't work on this laptop. I've tried the Debian 4.2.1-6 packages, Daniel Stone's 4.3.0-0ds4 packages and 4.2.1-6 plus the patch found at http://www.cse.unsw.edu.au/~chak/linux/c400.html#xfree86 This problem is now solved. I upgraded the kernel from the 2.4.18-bf2.4 that was installed by Debian to a homegrown 2.4.21-rc2 kernel. Then my 4.2.1-6.1 X packages work fine. Probably worth noting for the next time someone has this problem. Rumour has it X 4.3 should work out of the box, but I haven't tested that yet. -- It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject? -- Robert Fisk
Re: Problem with setxkb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Branden, all, thank's for your quick reply last time. (In January archives.) (I reported that I had problems with setxkbmap.) Now I have more detail: I don't know what causes this, it might be just that I'm doing something wrong. When I have Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys in my XF86Config-4's keyboard section, I try 'setxkbmap -v -layout de' to get kill my keys (disable the nodeadkeys). This does not work. When I have disabled the nodeadkeys in the config file, however, I can use above call to setxkbmap to undo the changes of 'setxkbmap -v -layout -variant nodeadkeys'. Is there any way to use setxkbmap or similar to disable nodeadkeys when it's in the config? It's rather important to have nodeadkeys as a default because a dead tilda (~) is sort of dangerous when clumsily removing backup files. ;) Cheers Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: GnuPG key at http://www.beamnet.de/tv/ iD8DBQE+P4qtriZpaaIa1PkRAiHZAKCyRqd9JtGX7bRCu9iOS+GfpMNJHgCghrGN qVMuC6EFn0nemkkArVOboJ8= =jTwc -END PGP SIGNATURE-
Re: Problem with setxkb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi again. Thomas Viehmann wrote: This doesn't work anymore and I do get the impression that setxkbmap is not doing terribly much at all (setxkbmap -v layout us) doesn't give me a us keyboard either. That said, XF86Config-4's settings are respected. After downgrading xbase-clients to 4.2.1-3 (thanks to snapshot.d.n), reupgrading, and restarting with deadkeys, it setxkbmap seems to work as before... So please don't bother until I've found out how to reproduce this. Regards Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: GnuPG key at http://www.beamnet.de/tv/ iD8DBQE+NWzNriZpaaIa1PkRAlnfAKC46v9uN3EuTUwFdVudvAr9aIYMxwCcCVFv 9niSb8S5klTjdO9LEOlkmXI= =PoVv -END PGP SIGNATURE-
Re: Problem with setxkb
On Mon, Jan 27, 2003 at 05:06:35PM +0100, Thomas Viehmann wrote: First thank you for the X -5 packages and the rather smooth upgrade (modulo me forgetting to turn off debconfiguration of XF86Config-4 - BTW: is it hopeful to file wishlist bugs for new config options, such as Device options for Roation, or would that just be wasting your and my time?). If the option is not essential to setting up a usable single-head system, I do not as a matter of policy provide a debconf template for it. Otherwise the debconfage for XFree86 would explode with complexity. However, I have a minor problem, unsure whether it's a bug: Formerly setxkbmap -v -layout de would give me dead keys (~ and accents), and setxkbmap -v -layout -variant nodeadkeys would turn them off. This doesn't work anymore and I do get the impression that setxkbmap is not doing terribly much at all (setxkbmap -v layout us) doesn't give me a us keyboard either. That said, XF86Config-4's settings are respected. Any hints? (I will provide more data as needed, but I'm not sure whether just pasting the XFree86.0.log would really help.) I am not sure what is causing this. Is anyone else experiencing this problem? -- G. Branden Robinson| I had thought very carefully about Debian GNU/Linux | comitting hara-kiri over this, but [EMAIL PROTECTED] | I overslept this morning. http://people.debian.org/~branden/ | -- Toshio Yamaguchi pgptP8fRHJiL3.pgp Description: PGP signature
Re: Problem with Debian
#include hallo.h * Skip Queen [Sun, Jan 19 2003, 07:14:35AM]: Have been trying to install Debian Woody 3.0 at least 10 times but unsuccessful. Cannot get either xwindows (have an i810 video card) or sound to work. It recognizes the cards but video/sound will not work. Have tried every way of installing possible, but no luck. Odd part is: I have installed Lindows and Knoppix - both of which are Debian and They do not ship with an old piece of shit as X (Version 4.1, not supporting any modern video card) while our X maintainer prefered to do so. Gruss/Regards, Eduard. -- Anwender1: Mein WIN95 ist in 6 Monaten noch NIE abgestürzt... Anwender2: Ein halbes Jahr ohne Strom - das ist hart! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with Debian
#include hallo.h * Daniel Stone [Mon, Jan 20 2003, 07:42:02AM]: They do not ship with an old piece of shit as X (Version 4.1, not supporting any modern video card) while our X maintainer prefered to do so. I didn't see *YOU* volunteering to fix PCI domains on SPARC, or even doing any packaging at all, let alone hacking. I suggest you refrain from such preppy, pithy, moronic snipes in future before you do your homework, unless you truly believe that i386 is the most important It is. architecture in Debian and that nothing else matters. If you support X refusing to work at all on SPARC in a release, speak up! Otherwise (and this is the most preferable option), shut up. If you cannot provide XFree for a certain architecture, but an ancient version, find a way to detach the development trees. For boot-floppies, we choose the kernel version that works best for certain architecture. For most people, X is as important as the kernel, so I fail to see how I you can really think that a KEEP-ALL-VERSIONS-EQUAL dogma is better for our users than working productive environment. Oh, I see you calling me a damn moron again, but it's easier than accepting the truth. Synchronisation problems inside of Debian will became worse, the number of supported hardware will grow too, so you won't be able to keep your eyes closed. Gruss/Regards, Eduard. -- Hi! Ich bin der beruechtigte .signature-Virus. Mach mit und kopier mich in deine .signature! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with Debian
On Sun, Jan 19, 2003 at 10:16:32PM +0100, Eduard Bloch scrawled: * Daniel Stone [Mon, Jan 20 2003, 07:42:02AM]: They do not ship with an old piece of shit as X (Version 4.1, not supporting any modern video card) while our X maintainer prefered to do so. I didn't see *YOU* volunteering to fix PCI domains on SPARC, or even doing any packaging at all, let alone hacking. I suggest you refrain from such preppy, pithy, moronic snipes in future before you do your homework, unless you truly believe that i386 is the most important It is. So we should do things that advantage i386 users, but severely break users of other architectures? Have a look at www.debian.org: i386 is now officially a port. The only distinctive feature is that it was the first port. architecture in Debian and that nothing else matters. If you support X refusing to work at all on SPARC in a release, speak up! Otherwise (and this is the most preferable option), shut up. If you cannot provide XFree for a certain architecture, but an ancient version, find a way to detach the development trees. For boot-floppies, we choose the kernel version that works best for certain architecture. That's because the kernel is relatively small. The kernel image debs come out to a few meg at most. X comes out to a couple of hundred meg. My apple is better than your orange! For most people, X is as important as the kernel, so I fail to see how I you can really think that a KEEP-ALL-VERSIONS-EQUAL dogma is better for our users than working productive environment. Yes, but X is far too big to carry on with all this crap. Branden has a hard enough slog maintaining just maintaining one version, let alone two. I don't think there are many people out there who can produce packages like X to the same quality as Branden, and know X well enough. None of them would volunteer to actually do it, I'm sure. Oh, I see you calling me a damn moron again, but it's easier than accepting the truth. Synchronisation problems inside of Debian will became worse, the number of supported hardware will grow too, so you won't be able to keep your eyes closed. I'm not trying to keep my eyes closed; au contrare, it seems that you are the one valiantly attempting to do so. Maybe you should come down here to Australia some time. The reason I'm mirror-whoring for my XFree86 4.3 debs at the moment is because we're charged $93/gb for international traffic, and that's *cheap*, because we're a college at a uni. If we weren't a uni, it would be a hell of a lot more for a decent connection. The reality is this: a) it's a pain in the arse for absolutely *NO* gain; b) it's stupid, and will kill mirrors (try thinking outside of Europe/America sometime); c) it's very short-sighted, and only demonstrates that you haven't actually thought about it; d) i386 is just another port. Before you go mentioning the kernel again, and how X is just as important to core operations as the kernel, you probably should take a look at their relative sizes. X: huge, kernel: not quite that big. Maybe you also want to have a look at the XFree86 debian/patches directory. Massive. Daniel, someone who knows what it's like to package XFree86 -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne msg05384/pgp0.pgp Description: PGP signature
Re: Problem with Debian
#include hallo.h * Skip Queen [Sun, Jan 19 2003, 07:14:35AM]: Have been trying to install Debian Woody 3.0 at least 10 times but unsuccessful. Cannot get either xwindows (have an i810 video card) or sound to work. It recognizes the cards but video/sound will not work. Have tried every way of installing possible, but no luck. Odd part is: I have installed Lindows and Knoppix - both of which are Debian and They do not ship with an old piece of shit as X (Version 4.1, not supporting any modern video card) while our X maintainer prefered to do so. Gruss/Regards, Eduard. -- Anwender1: Mein WIN95 ist in 6 Monaten noch NIE abgestürzt... Anwender2: Ein halbes Jahr ohne Strom - das ist hart!
Re: Problem with Debian
On Sun, Jan 19, 2003 at 01:30:15PM +0100, Eduard Bloch scrawled: #include hallo.h * Skip Queen [Sun, Jan 19 2003, 07:14:35AM]: Have been trying to install Debian Woody 3.0 at least 10 times but unsuccessful. Cannot get either xwindows (have an i810 video card) or sound to work. It recognizes the cards but video/sound will not work. Have tried every way of installing possible, but no luck. Odd part is: I have installed Lindows and Knoppix - both of which are Debian and They do not ship with an old piece of shit as X (Version 4.1, not supporting any modern video card) while our X maintainer prefered to do so. I didn't see *YOU* volunteering to fix PCI domains on SPARC, or even doing any packaging at all, let alone hacking. I suggest you refrain from such preppy, pithy, moronic snipes in future before you do your homework, unless you truly believe that i386 is the most important architecture in Debian and that nothing else matters. If you support X refusing to work at all on SPARC in a release, speak up! Otherwise (and this is the most preferable option), shut up. Scant regards, Daniel -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne pgp2BB2YknO4l.pgp Description: PGP signature
Re: Problem with Debian
On Sun, Jan 19, 2003 at 10:16:32PM +0100, Eduard Bloch scrawled: * Daniel Stone [Mon, Jan 20 2003, 07:42:02AM]: They do not ship with an old piece of shit as X (Version 4.1, not supporting any modern video card) while our X maintainer prefered to do so. I didn't see *YOU* volunteering to fix PCI domains on SPARC, or even doing any packaging at all, let alone hacking. I suggest you refrain from such preppy, pithy, moronic snipes in future before you do your homework, unless you truly believe that i386 is the most important It is. So we should do things that advantage i386 users, but severely break users of other architectures? Have a look at www.debian.org: i386 is now officially a port. The only distinctive feature is that it was the first port. architecture in Debian and that nothing else matters. If you support X refusing to work at all on SPARC in a release, speak up! Otherwise (and this is the most preferable option), shut up. If you cannot provide XFree for a certain architecture, but an ancient version, find a way to detach the development trees. For boot-floppies, we choose the kernel version that works best for certain architecture. That's because the kernel is relatively small. The kernel image debs come out to a few meg at most. X comes out to a couple of hundred meg. My apple is better than your orange! For most people, X is as important as the kernel, so I fail to see how I you can really think that a KEEP-ALL-VERSIONS-EQUAL dogma is better for our users than working productive environment. Yes, but X is far too big to carry on with all this crap. Branden has a hard enough slog maintaining just maintaining one version, let alone two. I don't think there are many people out there who can produce packages like X to the same quality as Branden, and know X well enough. None of them would volunteer to actually do it, I'm sure. Oh, I see you calling me a damn moron again, but it's easier than accepting the truth. Synchronisation problems inside of Debian will became worse, the number of supported hardware will grow too, so you won't be able to keep your eyes closed. I'm not trying to keep my eyes closed; au contrare, it seems that you are the one valiantly attempting to do so. Maybe you should come down here to Australia some time. The reason I'm mirror-whoring for my XFree86 4.3 debs at the moment is because we're charged $93/gb for international traffic, and that's *cheap*, because we're a college at a uni. If we weren't a uni, it would be a hell of a lot more for a decent connection. The reality is this: a) it's a pain in the arse for absolutely *NO* gain; b) it's stupid, and will kill mirrors (try thinking outside of Europe/America sometime); c) it's very short-sighted, and only demonstrates that you haven't actually thought about it; d) i386 is just another port. Before you go mentioning the kernel again, and how X is just as important to core operations as the kernel, you probably should take a look at their relative sizes. X: huge, kernel: not quite that big. Maybe you also want to have a look at the XFree86 debian/patches directory. Massive. Daniel, someone who knows what it's like to package XFree86 -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne pgpvJiw8lVHXI.pgp Description: PGP signature
Re: Problem with xserver and framebuffer
El sáb, 30-11-2002 a las 16:39, Michel Dänzer escribió: On Sam, 2002-11-30 at 12:38, José Salavert Torres wrote: El vie, 29-11-2002 a las 12:50, Michel Dänzer escribió: On Fre, 2002-11-29 at 12:20, José Salavert Torres wrote: El vie, 29-11-2002 a las 10:50, Michel Dänzer escribió: On Fre, 2002-11-29 at 01:25, José Salavert Torres wrote: The screen doesn't fill the whole monitor. It moves around when the pointer is near to the edge. I don't know why this happens, because server is set to 1024x768 in all modes, here is my XF86config. I don't see any obvious problems, please also provide a logfile. How can I provide that file? It should be /var/log/XFree86.0.log, or look at the X server output. Here it is. Hmm, no mention of 1024x768 at all. (==) Using config file: /etc/X11/XF86Config-4 Are you looking at this config file? I deleted 1024x768 in XF86config-4 because the desktop had 1024x768 size, but the screen not here is the new log file and XF86config-4. I use Nvidia fame buffer, I made it work beforewith xf86config and answering no to the question: Do you want a screen larger than the physical screen? no. or adding Virtual 1024 768 to the modes in XF86config. Other progrrams like mol can use full screen framebuffer (but has a configuration tool for that). I can't see any file in /etc refering to framebuffer modes. DRI for Nvidia still not supported can anyone talk with Nvidia corp??? 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.1.1 (Debian 4.2.1-4 20021123054041 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 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.19-powerpc-smp ppc [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 Dec 1 11:29:02 2002 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device NVIDIA GeForce (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout es (**) XKB: layout: es (==) Keyboard: CustomKeycode disabled (**) 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 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (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.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.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:0b:0: chip 106b,002d card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:10:0: chip 10de,0110 card 0208,a5b8 rev a1 class 03,00,00 hdr 00 (II) PCI: 10:0b:0: chip 106b,002e card , rev 00 class 06,00,00 hdr 00 (II) PCI: 10:13:0: chip 9004,5078 card 9004,7850 rev 03 class 01,00,00 hdr 00 (II) PCI: 10:17:0: chip 106b,0022 card , rev 03 class ff,00,00 hdr 00 (II) PCI: 10:18:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 10:19:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 20:0b:0: chip 106b,002f card , rev 00 class 06,00,00 hdr 00 (II) PCI: 20:0f:0: chip 106b,0021 card , rev 01 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading
Re: Problem with xserver and framebuffer
El sáb, 30-11-2002 a las 16:39, Michel Dänzer escribió: On Sam, 2002-11-30 at 12:38, José Salavert Torres wrote: El vie, 29-11-2002 a las 12:50, Michel Dänzer escribió: On Fre, 2002-11-29 at 12:20, José Salavert Torres wrote: El vie, 29-11-2002 a las 10:50, Michel Dänzer escribió: On Fre, 2002-11-29 at 01:25, José Salavert Torres wrote: The screen doesn't fill the whole monitor. It moves around when the pointer is near to the edge. I don't know why this happens, because server is set to 1024x768 in all modes, here is my XF86config. I don't see any obvious problems, please also provide a logfile. How can I provide that file? It should be /var/log/XFree86.0.log, or look at the X server output. Here it is. Hmm, no mention of 1024x768 at all. (==) Using config file: /etc/X11/XF86Config-4 Are you looking at this config file? I deleted 1024x768 in XF86config-4 because the desktop had 1024x768 size, but the screen not here is the new log file and XF86config-4. I use Nvidia fame buffer, I made it work beforewith xf86config and answering no to the question: Do you want a screen larger than the physical screen? no. or adding Virtual 1024 768 to the modes in XF86config. Other progrrams like mol can use full screen framebuffer (but has a configuration tool for that). I can't see any file in /etc refering to framebuffer modes. DRI for Nvidia still not supported can anyone talk with Nvidia corp??? This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org 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.1.1 (Debian 4.2.1-4 20021123054041 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 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.19-powerpc-smp ppc [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 Dec 1 11:29:02 2002 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device NVIDIA GeForce (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout es (**) XKB: layout: es (==) Keyboard: CustomKeycode disabled (**) 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 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (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.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.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:0b:0: chip 106b,002d card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:10:0: chip 10de,0110 card 0208,a5b8 rev a1 class 03,00,00 hdr 00 (II) PCI: 10:0b:0: chip 106b,002e card , rev 00 class 06,00,00 hdr 00 (II) PCI: 10:13:0: chip 9004,5078 card 9004,7850 rev 03 class 01,00,00 hdr 00 (II) PCI: 10:17:0: chip 106b,0022 card , rev 03 class ff,00,00 hdr 00 (II) PCI: 10:18:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 10:19:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 20:0b:0: chip 106b,002f card , rev 00 class 06,00,00 hdr 00 (II) PCI: 20:0f:0: chip 106b,0021 card , rev 01 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II)
Re: problem about SID/xserver
On Sun, Oct 27, 2002 at 07:06:42PM +0100, Clemens Wohld wrote: I have some big problem after an dist-upgrade on unstable. My system was runin before also unstalble. Some must be chance, but I cant find some in debian-databases/google etc. Log is attached. I will ask you if you can give me any hints to fix my problem. [...] # XF86Config (XFree86 server configuration file) generated by Dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-v3 manual page. # (Type man XF86Config-v3 at the shell prompt.) Well, at least one problem is pretty obvious. You've put an XFree86 3.x config file in /etc/X11/XF86Config-4. -- G. Branden Robinson| The last Christian died on the Debian GNU/Linux | cross. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | msg04401/pgp0.pgp Description: PGP signature
Re: problem about SID/xserver
On Sun, Oct 27, 2002 at 07:06:42PM +0100, Clemens Wohld wrote: I have some big problem after an dist-upgrade on unstable. My system was runin before also unstalble. Some must be chance, but I cant find some in debian-databases/google etc. Log is attached. I will ask you if you can give me any hints to fix my problem. [...] # XF86Config (XFree86 server configuration file) generated by Dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-v3 manual page. # (Type man XF86Config-v3 at the shell prompt.) Well, at least one problem is pretty obvious. You've put an XFree86 3.x config file in /etc/X11/XF86Config-4. -- G. Branden Robinson| The last Christian died on the Debian GNU/Linux | cross. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | pgpKWtgbQf5gd.pgp Description: PGP signature
Re: problem with type6 keyboard on sparc
On Wed, Sep 25, 2002 at 09:01:26AM +0100, John P. Looney wrote: I had a lot of trouble getting this working at all. First off, I blindly assumed that my keyboard was a type5, and this caused kernel panics on debian/woody, on boot, when loadkeys was run! Once I fixed that, X was a problem. By default, the X configurator on Erm, how did you fix that? Cheers -- Paul
Re: problem with type6 keyboard on sparc
On Wed, Sep 25, 2002 at 09:01:26AM +0100, John P. Looney wrote: I had a lot of trouble getting this working at all. First off, I blindly assumed that my keyboard was a type5, and this caused kernel panics on debian/woody, on boot, when loadkeys was run! Once I fixed that, X was a problem. By default, the X configurator on Erm, how did you fix that? Cheers -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with xfree86-common_4.2.1-0pre1v1_all
On Wed, Sep 11, 2002 at 04:23:46PM -0500, Branden Robinson wrote: On Wed, Sep 11, 2002 at 10:45:01PM +0200, Alexander Opitz wrote: Ok, here it comes. shell dpkg-preconfigure xfree86-common_4.2.1-0pre1v1_all.deb debconf (developer): starting /tmp/config.8571 configure 4.2.1-0pre1v1 debconf (developer): -- REGISTER xfree86-common/experimental_packages xfree86-common/nag debconf (developer): -- 10 No such template, xfree86-common/experimental_packages xfree86-common failed to preconfigure, with exit status 10 Hope it helps to help me :-) Hmm, not really. It looks like dpkg-preconfigure is failing to call apt-extracttemplates. It looks like a corrupt debconf database to me, especially if man-db runs into it too. Try taking a copy of everything in /var/cache/debconf (for the purposes of later bug reports :-)), and then running /usr/share/debconf/fix_db.pl. -- Colin Watson [EMAIL PROTECTED]
Re: problem with xfree86-common_4.2.1-0pre1v1_all
On Wed, Sep 11, 2002 at 10:45:01PM +0200, Alexander Opitz wrote: Ok, here it comes. shell dpkg-preconfigure xfree86-common_4.2.1-0pre1v1_all.deb debconf (developer): starting /tmp/config.8571 configure 4.2.1-0pre1v1 debconf (developer): -- REGISTER xfree86-common/experimental_packages xfree86-common/nag debconf (developer): -- 10 No such template, xfree86-common/experimental_packages xfree86-common failed to preconfigure, with exit status 10 Hope it helps to help me :-) Hmm, not really. It looks like dpkg-preconfigure is failing to call apt-extracttemplates. -- G. Branden Robinson| Measure with micrometer, Debian GNU/Linux | mark with chalk, [EMAIL PROTECTED] | cut with axe, http://people.debian.org/~branden/ | hope like hell. pgpxFrPC6PCNf.pgp Description: PGP signature
Re: problem in xterm 4.2.0 pre1v4
On Sat, Sep 07, 2002 at 08:22:49PM +0200, Giuseppe Sacco wrote: [Please CC to me.] Hi, I found a problem in xterm (I think) that shows incorrectly a line as shown in this image: http://eppesuigoccas.homedns.org/~giuseppe/xfree420bug/xterm-4.2.0-pre1v3.png On my system it looks a lot stranger sometimes since it does not look like a line or something like this. I have even seen strange color errors like red dots somewhere in plain ascii text and so on. The problem shows up *often* on my system. I think I can reproduce the problem on my system with vim: - enter one line of text - press enter to get new line - then press backspace to return to previous line A refresh cleares the display corruption. Is this a problem of the backing store? [...] P.S. the problem was already present in pre1v3 but not in 4.1.0.1 (woody). The XFconfig driver is sis and the chipset SiS 630. I am using an Nvidia Geforce 4200 card and with the NV driver the problem does not show up (not very helpful info I guess). If you need further infos about my system just let me know. I am currently running ii xserver-xfree8 4.2.1-0pre1v1 the XFree86 X server (static version since it is not that big a download (only 3.5 MB compared to the 16 MB of the regular version -- I think that's a build error, shouldn't the static debug version be the large one?) -- Well, yeah ... I suppose there's no point in getting greedy, is there? Calvin Hobbes
Re: Problem building X4.2
Hello, The problem was mine. My ext2 filesystem was corrupt. I'm sorry. God bye. El Mié 14 Ago 2002 11:02, Iñigo Lekanda escribió: Hello, I have testing the X4.2 ok in my laptop (the 4.1 hang it). When I atempt to build from source I have these errors: --- c++ -c -O2 -fno-strength-reduce -g -I../internals -I../../include -I../../../../include -I../../../../include/GL -I../../../.. -I../../../../exports/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DLIBRARYBUILD -DNDEBUG -fPIC monoPolyPart.cc rm -f DONE touch DONE make[6]: Leaving directory `/tmp/xfree86-4.2.0/build-tree/xc/lib/GLU/libnurbs/nurbtess' rm -f libGLU.a ar clq libGLU.a libutil/?*.o libtess/?*.o libnurbs/internals/?*.o libnurbs/interface/?*.o libnurbs/nurbtess/?*.o ar: libnurbs/internals/?*.o: No such file or directory make[5]: *** [libGLU.a] Error 1 make[5]: Leaving directory `/tmp/xfree86-4.2.0/build-tree/xc/lib/GLU' make[4]: *** [all] Error 2 make[4]: Leaving directory `/tmp/xfree86-4.2.0/build-tree/xc/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/tmp/xfree86-4.2.0/build-tree/xc' make[2]: *** [World] Error 2 make[2]: Leaving directory `/tmp/xfree86-4.2.0/build-tree/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/tmp/xfree86-4.2.0/build-tree/xc' make: *** [debian/stampdir/build] Error 2 Build command 'cd xfree86-4.2.0 dpkg-buildpackage -b -uc' failed. E: Child process failed mv: cannot stat `*.deb': No such file or directory [chroot]ilekandap:/# --- This in the laptop with Sarge and in K6-2 with Sarge. I use pentium-builder package to optimize for the corresponding CPU. I'm not probe with Woody or Sid. If I can help you in any question for debug this tell me. Good bye.
Re: Problem switching back to X from console in 4.1.0
On Thu, Sep 13, 2001 at 03:48:15PM -, Geoffrey Hausheer wrote: I am having difficulties with XFree 4.1.0-5 (also -3) in Woody. Specifically, if I switch to a virtual terminal and then switch back to X, I get a black screen. The only way I seem to be able to resolve this is to manually kill and restart X from the console. I have the same problems with nvidias closed-source-drivers if I use the rivafb for console. If i dont use rivafb there are no problems. Martin -- [this line is intentionally left blank] pgpMLBCvZIcCA.pgp Description: PGP signature
Re: problem w voodoo3/XF86-4
I have just spent several hours last night getting my new V3 card to work with 4.0.2. Here are my thoughts (And I did get it to work) 1. compile kernel with agp, DRI support (I didnt build DRI module like they suggested, I used DRI that came with the kernel source), and your chipset support. In X, put in Load glx Load dri into the Xconfig file. Verify that you are in fact using correct libs (in my case, I had to remove my old glut3g and mesa3g libs and install xlibmesa3 and xlibosmesa3. The best document you can read on this issue is the DRi user guide on X's page (http://www.xfree86.org/4.0.3/DRI.html), it explains how to vefiry you have everything setup. Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354 -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem w voodoo3/XF86-4
Andrei Ivanov wrote: I have just spent several hours last night getting my new V3 card to work with 4.0.2. Here are my thoughts (And I did get it to work) 1. compile kernel with agp, DRI support AGP support isn't needed for 3dfx chips as the chips themselves don't support any AGP functions. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem w voodoo3/XF86-4
I have just spent several hours last night getting my new V3 card to work with 4.0.2. Here are my thoughts (And I did get it to work) 1. compile kernel with agp, DRI support (I didnt build DRI module like they suggested, I used DRI that came with the kernel source), and your chipset support. In X, put in Load glx Load dri into the Xconfig file. Verify that you are in fact using correct libs (in my case, I had to remove my old glut3g and mesa3g libs and install xlibmesa3 and xlibosmesa3. The best document you can read on this issue is the DRi user guide on X's page (http://www.xfree86.org/4.0.3/DRI.html), it explains how to vefiry you have everything setup. Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354 --
Re: problem w voodoo3/XF86-4
Andrei Ivanov wrote: I have just spent several hours last night getting my new V3 card to work with 4.0.2. Here are my thoughts (And I did get it to work) 1. compile kernel with agp, DRI support AGP support isn't needed for 3dfx chips as the chips themselves don't support any AGP functions. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member
Re: Problem with your Debian packages
Hallo, I guess you have followed the warnings during an previous install of the XF4.01-deb's. Don't, i repeat, don't make a symbolic link (ignore the warnings during an install) from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. In this trap i got in, short time ago (The trap snaps if you update, after you make this symlink) big bummer delete this link and it should go fine I've learned this the hard-way (removing all the X depending stuff; inclusive X itself; don't do this) Hi Branden and all, A solution for this? Greetings Reiner Stallknecht -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with your Debian packages
On Sat, Dec 16, 2000 at 12:18:01AM +0100, reiner wrote: Don't, i repeat, don't make a symbolic link (ignore the warnings during an install) from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. You have to be more specific. On my systems, both current woody and potato with the potato versions of Branden's packages, I did this (have a real /etc/X11/app-defaults and create a symbolic link to it from /etc/X11R6/lib/X11 for backwards compatibility) and these systems are as happy and healthy as can be. -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with your Debian packages
Hallo, I guess you have followed the warnings during an previous install of the XF4.01-deb's. Don't, i repeat, don't make a symbolic link (ignore the warnings during an install) from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. In this trap i got in, short time ago (The trap snaps if you update, after you make this symlink) big bummer delete this link and it should go fine I've learned this the hard-way (removing all the X depending stuff; inclusive X itself; don't do this) Hi Branden and all, A solution for this? Greetings Reiner Stallknecht
Re: Problem with your Debian packages
On Sat, Dec 16, 2000 at 12:18:01AM +0100, reiner wrote: Don't, i repeat, don't make a symbolic link (ignore the warnings during an install) from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. You have to be more specific. On my systems, both current woody and potato with the potato versions of Branden's packages, I did this (have a real /etc/X11/app-defaults and create a symbolic link to it from /etc/X11R6/lib/X11 for backwards compatibility) and these systems are as happy and healthy as can be. -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
Re: Problem getting XF 4.0.1(g) to work with Matrox G450
Sounds like you've got the exact same hardware that I do, Asus A7V, Duron 700, Matrox G200 (or some kind of MGA card), kernel 2.4.0test10 and rest assured that this hardware works extremely well with woody and the 2.4.0test10. I can honestly can say that, I've never seen my system work so well, including power management which never worked right for me before. Now, on to your problem, the solid crash. Here are few pointers. * Don't overclock bus speed in the bios unless you're ready to do some soldering on your Duron. - (Not recommended) * If you're using the font servers (xfs or xfstt), make sure they are running before you start X. XFree86 left my video card in unworkable state if any of font servers were not working. * Use the MGA driver that comes with the distribution. The driver from the Matrox site is unstable and only does DGA 1.0 * In your kernel setup, turn on the following M /dev/agpgart (AGP Support) [*] VIA chipset support [*] Direct Rendering Manager (XFree86 DRI support) M Matrox g200/g400 and for safety measure turn on [*] Magic SysRq key it will get you out of some nasty situations. Be careful with 3D apps. The gears and sprongies screen savers work find but lament will hang X and put your video card in a weird state and you'll have to reboot. Good luck. Rich Frederik Vanrenterghem wrote: Hi, I've been trying to get my comp running X, but with no success this far. I'm running the latest 2.2.18pre from Woody, and I've tried both mga_drv.o from Woody and from the Matrox website. Also, I've tried playing with some options in XF86Config-4, all with no luck. Every time I do startx, the computer locks hard and requires a manual reset (not very fun to do). Also, the Dell P790 monitor goes blank, saying something about the frequency (I've had this on my other box with the same monitor often while switching from VT7 with X to another VT. Switching back to VT7 and after that trying again to switch to the other VT solves that always) I've tried recompiling the kernel (a 2.4.0test10), but that didn't work out, probably due to my Asus A7V motherboard or Duron 700 CPU or something. Any help would be greatly appreciated, 'cause I've sold my other box already, and I would like to have some X functionality on my new one ;) Greetings, Frederik (in attachment: log file of latest attempt, and XF86Config-4) -- The seven year itch comes from fooling around during the fourth, fifth, and sixth years. --- Name: XF86Config-4 XF86Config-4Type: Plain Text (TEXT/PLAIN) Encoding: BASE64 Name: XFree86.0.log XFree86.0.logType: Plain Text (TEXT/PLAIN) Encoding: BASE64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem getting XF 4.0.1(g) to work with Matrox G450
On Sat, 2 Dec 2000, Richard Ayotte wrote: * Don't overclock bus speed in the bios unless you're ready to do some soldering on your Duron. - (Not recommended) Didn't do that. * If you're using the font servers (xfs or xfstt), make sure they are running before you start X. XFree86 left my video card in unworkable state if any of font servers were not working. Removed the line in the config, 'cause I haven't installed a font server (yet) * Use the MGA driver that comes with the distribution. The driver from the Matrox site is unstable and only does DGA 1.0 Tried both of them, no luck * In your kernel setup, turn on the following M /dev/agpgart (AGP Support) [*] VIA chipset support [*] Direct Rendering Manager (XFree86 DRI support) M Matrox g200/g400 I've done that (built-in, no modules) in the 2.2.18pre21 kernel supplied with Debian. I've been unable to build a 2.4.0test10 or 11 kernel (see some of my previous posts in debian-user) I've also tried to launch X without these things built in, disabling DRI in the config. No X either. Be careful with 3D apps. The gears and sprongies screen savers work find but lament will hang X and put your video card in a weird state and you'll have to reboot. I'll remember that advice, once I get X to work ;-) -- A sociologist, a psychologist, and a engineer were discussing the consequences and implications of a married man's having a mistress. The sociologist's opinion was that it is absolutely and categorically unforgivable for a married man to forfeit the bond of matrimony, and engage in such lowly and lustful pursuits. The psychologist's opinion was that although morally reprehensible, if a man MUST have a mistress to achieve his full potential as a human being, then -- well -- he may go ahead and choose to have a mistress, as long as he is considerate enough to keep this secret from his wife. The engineer then interjected: "I also believe that, if necessary, a married man is entitled to a mistress. However, I do not see why the affair should be concealed from the wife. On the contrary, if the affair is out in the open, then on Friday evenings he may tell his wife that he is going to see his mistress, tell his mistress that he is going to be with his wife, then go to his office and get some work done!" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem getting XF 4.0.1(g) to work with Matrox G450
* Frederik Vanrenterghem [EMAIL PROTECTED] [001202 08:46]: I've tried recompiling the kernel (a 2.4.0test10), but that didn't work out, probably due to my Asus A7V motherboard or Duron 700 CPU or something. uhhh... this should be investigated. Compiling an application is a fairly straightforward task and should work no matter your CPU or motherboard. (Do you have bin86 installed? Many people forget to install this package.. :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem getting XF 4.0.1(g) to work with Matrox G450
Sounds like you've got the exact same hardware that I do, Asus A7V, Duron 700, Matrox G200 (or some kind of MGA card), kernel 2.4.0test10 and rest assured that this hardware works extremely well with woody and the 2.4.0test10. I can honestly can say that, I've never seen my system work so well, including power management which never worked right for me before. Now, on to your problem, the solid crash. Here are few pointers. * Don't overclock bus speed in the bios unless you're ready to do some soldering on your Duron. - (Not recommended) * If you're using the font servers (xfs or xfstt), make sure they are running before you start X. XFree86 left my video card in unworkable state if any of font servers were not working. * Use the MGA driver that comes with the distribution. The driver from the Matrox site is unstable and only does DGA 1.0 * In your kernel setup, turn on the following M /dev/agpgart (AGP Support) [*] VIA chipset support [*] Direct Rendering Manager (XFree86 DRI support) M Matrox g200/g400 and for safety measure turn on [*] Magic SysRq key it will get you out of some nasty situations. Be careful with 3D apps. The gears and sprongies screen savers work find but lament will hang X and put your video card in a weird state and you'll have to reboot. Good luck. Rich Frederik Vanrenterghem wrote: Hi, I've been trying to get my comp running X, but with no success this far. I'm running the latest 2.2.18pre from Woody, and I've tried both mga_drv.o from Woody and from the Matrox website. Also, I've tried playing with some options in XF86Config-4, all with no luck. Every time I do startx, the computer locks hard and requires a manual reset (not very fun to do). Also, the Dell P790 monitor goes blank, saying something about the frequency (I've had this on my other box with the same monitor often while switching from VT7 with X to another VT. Switching back to VT7 and after that trying again to switch to the other VT solves that always) I've tried recompiling the kernel (a 2.4.0test10), but that didn't work out, probably due to my Asus A7V motherboard or Duron 700 CPU or something. Any help would be greatly appreciated, 'cause I've sold my other box already, and I would like to have some X functionality on my new one ;) Greetings, Frederik (in attachment: log file of latest attempt, and XF86Config-4) -- The seven year itch comes from fooling around during the fourth, fifth, and sixth years. --- Name: XF86Config-4 XF86Config-4Type: Plain Text (TEXT/PLAIN) Encoding: BASE64 Name: XFree86.0.log XFree86.0.logType: Plain Text (TEXT/PLAIN) Encoding: BASE64
Re: Problem getting XF 4.0.1(g) to work with Matrox G450
* Frederik Vanrenterghem [EMAIL PROTECTED] [001202 08:46]: I've tried recompiling the kernel (a 2.4.0test10), but that didn't work out, probably due to my Asus A7V motherboard or Duron 700 CPU or something. uhhh... this should be investigated. Compiling an application is a fairly straightforward task and should work no matter your CPU or motherboard. (Do you have bin86 installed? Many people forget to install this package.. :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: problem building 4.0.1d xf86cfg on SPARC
On Sun, 29 Oct 2000, Branden Robinson wrote:
Hi,
You can add these to xc/programs/Xserver/hw/xfree86/xf86cfg/loader.c.
I think one possible solution is to patch
xc/programs/Xserver/hw/xfree86/loader/xf86sym.c to use it in xf86cfg, so
that when that file is changed, there will be no need to updates to
xf86cfg/loader.c. But xf86cfg does not need everything, just enough
symbols to run the Setup from the module, and the AvailableOptions
functions.
gcc -o xf86cfg -O2 -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs
-L../../../../../exports/lib accessx.ocards.o config.ocard-cfg.o
help.o interface.o keyboard-cfg.o libc_wrapper.o loader.o monitor-cfg.o
mouse-cfg.o options.o screen-cfg.o screen.ostartx.o
stubs.o vidmode.o xf86config.o -lxkbui -lxkbfile -lxf86config -lXxf86misc
-lXxf86vm -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11 -lXt -lSM -lICE
-lXpm -L../loader -lxloader -L../dummylib -ldummy -rdynamic -ldl -lXext -lX11
-lm -Wl,-rpath-link,../../../../../exports/lib
../loader/libxloader.a(loader.o): In function `LoaderInit':
loader.o(.text+0x8c): undefined reference to `sparcUseHWMulDiv'
loader.o(.text+0x9c): undefined reference to `SparcLookupTab'
loader.o(.text+0xa0): undefined reference to `SparcV89LookupTab'
loader.o(.text+0xa4): undefined reference to `SparcV89LookupTab'
loader.o(.text+0xbc): undefined reference to `SparcLookupTab'
collect2: ld returned 1 exit status
These symbols appear to be defined in the following files:
xc/programs/Xserver/hw/xfree86/loader/xf86sym.c:LOOKUP SparcV89LookupTab[] = {
xc/programs/Xserver/hw/xfree86/loader/xf86sym.c:LOOKUP SparcLookupTab[] = {
xc/programs/Xserver/hw/xfree86/os-support/bus/sparcPci.c:int sparcUseHWMulDiv(void);
--
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
Paulo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem building 4.0.1d xf86cfg on SPARC
On Sun, 29 Oct 2000, Branden Robinson wrote:
Hi,
You can add these to xc/programs/Xserver/hw/xfree86/xf86cfg/loader.c.
I think one possible solution is to patch
xc/programs/Xserver/hw/xfree86/loader/xf86sym.c to use it in xf86cfg, so
that when that file is changed, there will be no need to updates to
xf86cfg/loader.c. But xf86cfg does not need everything, just enough
symbols to run the Setup from the module, and the AvailableOptions
functions.
gcc -o xf86cfg -O2 -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wredundant-decls
-Wnested-externs -L../../../../../exports/lib accessx.ocards.o
config.ocard-cfg.o help.o interface.o keyboard-cfg.o
libc_wrapper.o loader.o monitor-cfg.o mouse-cfg.o options.o
screen-cfg.o screen.ostartx.ostubs.o vidmode.o
xf86config.o -lxkbui -lxkbfile -lxf86config -lXxf86misc
-lXxf86vm -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11 -lXt -lSM -lICE
-lXpm -L../loader -lxloader -L../dummylib -ldummy -rdynamic -ldl -lXext
-lX11 -lm -Wl,-rpath-link,../../../../../exports/lib
../loader/libxloader.a(loader.o): In function `LoaderInit':
loader.o(.text+0x8c): undefined reference to `sparcUseHWMulDiv'
loader.o(.text+0x9c): undefined reference to `SparcLookupTab'
loader.o(.text+0xa0): undefined reference to `SparcV89LookupTab'
loader.o(.text+0xa4): undefined reference to `SparcV89LookupTab'
loader.o(.text+0xbc): undefined reference to `SparcLookupTab'
collect2: ld returned 1 exit status
These symbols appear to be defined in the following files:
xc/programs/Xserver/hw/xfree86/loader/xf86sym.c:LOOKUP SparcV89LookupTab[] = {
xc/programs/Xserver/hw/xfree86/loader/xf86sym.c:LOOKUP SparcLookupTab[] = {
xc/programs/Xserver/hw/xfree86/os-support/bus/sparcPci.c:int
sparcUseHWMulDiv(void);
--
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
Paulo
[david@kalifornia.com: Re: problem with 2.4.0-test9-pre6 seems to be SHM]
FYI, it seems the latest X CVS has the SHM problem fixed.
--
[EMAIL PROTECTED],havoc,gaeshido}.fi,{debian,wanderer}.org,stonesoft.com}
unix, linux, debian, networks, security, | The Web site you seek
kernel, TCP/IP, C, perl, free software, | cannot be located but
mail, www, sw devel, unix admin, hacks. | endless others exist
---BeginMessage---
Shaw Starr repored on xpert@xfree86.org that a fresh checkout of 4.01d and fresh
build of X resulted in a fixed/working shm w/ X.
-d
safemode wrote:
When in doubt. . Blame it on the biggest piece of crap around .. X.One
can
say using a cvs of X is the cause of this by somehow i doubt it would matter.
X
needs a sane make system and i'll bet 10:1 that it's the root of this shm
usage.
But it should not be crashing the OS ...which does occur since i just went
down a
couple minutes ago. Right now it's increasing 1 segment a second it seems.
it's
at 1200 now and i give it about 30 more minutes before i crash again. I'm
gonna
run this on the test8-vm3 patched kernel i had before that was VERY good
except
for that deadlock problem that caused me to crash after 7 days. If the shm
usage
is insane on that then i'll believe it is X's fault. be back with the
results
in a few minutes.
--
There is a natural aristocracy among men. The grounds of this are
virtue and talents, Thomas Jefferson [1742-1826], 3rd US President
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
org:img src=http://www.kalifornia.com/images/paradise.jpg;
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;28256
fn:David Ford
end:vcard
---End Message---
Re: Problem with xfree4 phase2 package
On Tue, Sep 12, 2000 at 12:37:50PM +0200, Christophe CALMEJANE wrote: Hello there, I'm wondering where the libGLU are gone ? They are not on xlibgl1 nor in xlibgl-dev They are not (yet) included in xfree. This will be changing soon, and i guess the mesa maintainer did/is doing a standalone libglu package. In the mean time and if the standalone libglu package is not yet done, just install mesa, and copy the libglu files by hand. This will work nicely, but lets hope a nicer solution will come soon. Friendly, Sven LUTHER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with xfree4 phase2 package
On Tue, Sep 12, 2000 at 12:37:50PM +0200, Christophe CALMEJANE wrote: Hello there, I'm wondering where the libGLU are gone ? They are not on xlibgl1 nor in xlibgl-dev They are not (yet) included in xfree. This will be changing soon, and i guess the mesa maintainer did/is doing a standalone libglu package. In the mean time and if the standalone libglu package is not yet done, just install mesa, and copy the libglu files by hand. This will work nicely, but lets hope a nicer solution will come soon. Friendly, Sven LUTHER
