Bug#203283: marked as done (automatic xserver-xf86free configurator(s) broken?)
Your message dated Tue, 29 Jul 2003 11:41:19 -0500
with message-id <20030729164119.GP17560@deadbeast.net>
and subject line S3 Trio64V+ supported in Debian testing/unstable
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Jul 2003 05:52:13 +0000
>From gcf@panix.com Tue Jul 29 00:52:06 2003
Return-path: <gcf@panix.com>
Received: from mail1.panix.com [166.84.1.72]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19hNP3-0002Nl-00; Tue, 29 Jul 2003 00:52:05 -0500
Received: from panix1.panix.com (panix1.panix.com [166.84.1.1])
by mail1.panix.com (Postfix) with ESMTP id B1DDB48C95
for <submit@bugs.debian.org>; Tue, 29 Jul 2003 01:52:04 -0400 (EDT)
Received: (from gcf@localhost)
by panix1.panix.com (8.11.6p2/8.8.8/PanixN1.1) id h6T5q4x22399
for submit@bugs.debian.org; Tue, 29 Jul 2003 01:52:04 -0400 (EDT)
Date: Tue, 29 Jul 2003 01:52:04 -0400
From: Gordon Fitch <gcf@panix.com>
To: submit@bugs.debian.org
Subject: automatic xserver-xf86free configurator(s) broken?
Message-ID: <20030729055204.GA16776@panix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0
tests=BAYES_30,HAS_PACKAGE,PENISACCENT,USER_AGENT_MUTT
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)
Package: xserver-xf86free
Version: 4.1.0
I am not sure whether this is a bug or not or which package
it actually belongs to . I amm one of the many people (judging
by what I read in Google and Google News) who upgraded to
Woody and found that their X stuff didn't work any more. I
went through many hours and a number of iterations of fooling
with the configuration files, to no avail whatever. However,
after a considerable amount of searching, in which I came
across many complaints about very similar problems, but few
suggestions and fewer solutions, I found this -- in Spanish.
I'll translate here and send the original if you like. It
can also be seen as
http://groups.google.com/groups?selm=4g6o.3xd.11%40gated-at.bofh.it
Q:
>>... The problem is that it produces an error. I will
>>append the last lines of the [log] (not all, because it is
>>very long and I don't know how to take out [ just the
>>relevant information ]....
>>
>>
>> (EE) VESA(0): no matching modes
>> (II) Unloading /usr/X11R6/lib/modules/libvgahw.a
>> (EE) Screen(s) found, but none have a usable
>> configuration.
A:
>This error is relative to the file //etc/X11/XF86Config-4,
>which is the configuration of the X server.
>It is necessary to revise this file.
>This problem was discussed a few days ago on this list.
>XF86Config-4 ... has an error and that is what is causing
>the server to break. Do the following as root:
>#XFree86 -configure
>and then
>#XFree86 -xf86config XF86Config-4
>and notice what happens. Probably it will work.
This did work to the extent of bringing up a partially
usable, although somewhat defective X system. It failed to
configure the mouse properly (this is an old PS/2 with a
/dev/psaux mouse) but I was able to fix that by hand. Later
I was able to improve (?) the configuration file by adding
mode lines which the one produced as above didn't have.
There are still some problems, but in this message I am
trying to focus on the fact that the automatic configuration
programs started by the installation procedure did not work
correctly for my equipment (IBM PS/2 type, S3 Trio64V+ board,
NEC MultiSync 5FGE monitor.)
I have not found a reference to this problem on the debian
site. It is not easy to search for the bug because "no matching
modes" appears to be highly generic, the result of a number
of things going wrong with configuration.
(I might add that when the X server fails to come up at boot
time, a box comes up asking whether the user wants to run
a program to reconfigure. This turns out to be a graphical
program which, on my system, was seriously broken and
impossible to get out of short of a reboot. I would suggest
fixing it or getting rid of it.)
One problem may be that, according to
http://www.xfree86.org/4.1.0/Status28.html#28
support for my chipset (S3 Trio64V+) "has not yet been ported".
Meanwhile XFree86 has moved on to 4.3.0. However, I don't
know if I can revert to 3.3.6 without screwing up the
dependencies, or go forward to 4.3.0. What I have is what
apt-get got me in the last few days, after I loaded 3.0 from
CDs, so it's either on the CD or at debian.org.
I will send more material on request but as I say I think
this problem may already have been reported.
-- Gordon Fitch
gcf@panix.com
---------------------------------------
Received: (at 203283-done) by bugs.debian.org; 29 Jul 2003 17:10:59 +0000
>From branden@deadbeast.net Tue Jul 29 12:07:36 2003
Return-path: <branden@deadbeast.net>
Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net) [65.26.182.85]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19hXwm-0008P2-00; Tue, 29 Jul 2003 12:07:36 -0500
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id 935BE64118; Tue, 29 Jul 2003 12:07:35 -0500 (EST)
Resent-From: branden@deadbeast.net
Resent-Date: Tue, 29 Jul 2003 12:07:35 -0500
Resent-Message-ID: <20030729170735.GT17560@deadbeast.net>
Resent-To: 203283-done@bugs.debian.org
Date: Tue, 29 Jul 2003 11:41:19 -0500
From: Branden Robinson <branden@debian.org>
To: 203823-done@bugs.debian.org
Subject: S3 Trio64V+ supported in Debian testing/unstable
Message-ID: <20030729164119.GP17560@deadbeast.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="kOdvwer/5gjFgNo6"
Content-Disposition: inline
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
X-Manoj-Position-Advisory: Please note that Manoj Srivastava likely doubts any facts posited and opposes any conclusions reached in this message.
User-Agent: Mutt/1.5.4i
Delivered-To: 203283-done@bugs.debian.org
X-Spam-Status: No, hits=-9.3 required=4.0
tests=BAYES_30,PGP_SIGNATURE_2,USER_AGENT_MUTT
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)
--kOdvwer/5gjFgNo6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Debian testing/unstable has XFree86 4.2.1.
=46rom <URL: http://www.xfree86.org/4.2.1/Status28.html#28 >:
Support (accelerated) for the 964 (revisions 0 and 1), 968, Trio32,
Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX
is provided by the "s3" driver (however, only models using the IBM RGB
524, Texas Instruments 3025, or an internal TrioDAC RAMDAC chip are
supported).
Support in XFree86 4.3.0 appears to be identical[1].
If you find that XFree86 4.2.1/4.3.0 does not support your video card,
please file a new bug report.
[1] http://www.xfree86.org/4.3.0/Status29.html
--=20
G. Branden Robinson | The basic test of freedom is
Debian GNU/Linux | perhaps less in what we are free to
branden@debian.org | do than in what we are free not to
http://people.debian.org/~branden/ | do. -- Eric Hoffer
--kOdvwer/5gjFgNo6
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iEYEARECAAYFAj8mo68ACgkQ6kxmHytGonzBqQCfRNw4G9NfW2VFiB133SuBY2Ob
jfUAnju9aoITnK0asKEzfEWydunV3zU4
=SIqM
-----END PGP SIGNATURE-----
--kOdvwer/5gjFgNo6--
Reply to: