tag 225720 + moreinfo
retitle 225720 xserver-xfree86: [vga] driver doesn't support ATI Mach64 GB rev 92 in unknown configuration
thanks
On Wed, Dec 31, 2003 at 01:20:41PM -0800, Xeno Campanoli wrote:
> Package: xserver-xfree86
> Version: 4.1.0-16woody1
>
> I got this trying to start up the xserver on a machine with 128 mb mother
> board memory, and an ATI Tech card that says RagePro Turbo AGP AMC ver 2.0 on it.
> X does not come up.
You did not supply information critical to the further investigation of
this bug.
You did not supply a one-line summary of this bug, either.
Please read the XF86Config(7) manual page and supply the required
information. Until you do, we will be unable to act on this report.
Also, please do not file the same bug multiple times in the future.
Doing so will not hasten resolution of your problem.
[The following is a form letter.]
Hello,
You recently filed a bug report against Debian's XFree86
packages that had so little useful information in it that it could not
be meaningfully handled.
One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name. A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports. This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report. This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers. The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports. (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)
Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System, and try filing your report
again.
One way to install reportbug is with "apt-get"; for
example:
# apt-get install reportbug
The "reportbug" command has a few different modes that cater to different
levels of user expertise. If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.
$ reportbug --mode=novice
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.
$ reportbug
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
The reportbug command is extensively documented in its usage message and
manual page. Commands to view these pieces of documentation are:
$ reportbug --help | more
$ man reportbug
(The output of the above commands has been omitted from this message.)
If you don't want to use reportbug, then please see:
http://www.debian.org/Bugs/Reporting
for detailed instructions on how to file bug reports that are more
likely to be successfully resolved.
You can also view this document locally if you have the "doc-debian"
package installed:
# apt-get install doc-debian
$ pager /usr/share/doc/debian/bug-reporting.txt
Thanks for using the Debian system!
--
G. Branden Robinson |
Debian GNU/Linux | Extra territorium jus dicenti
branden@debian.org | impune non paretur.
http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature