[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#243575: Still only DVI output for every 2nd run (xfree 4.3.0.dsfg.1-1)



unmerge 243575
reopen 243575
submitter 243575 Achim Bohnet <ach@mpe.mpg.de>
tag 243575 = moreinfo upstream
thanks

On Mon, May 03, 2004 at 08:47:45PM +0200, Achim Bohnet wrote:
> Hi,
> I'm using testing + xfree86 and kde from unstable. And noticed
> in the xfree86 changlog that DVI output on 9200 should work.
> After adding (again) my Sapphire Radeon 9200 Atlantis with
> 128MB RAM and VGA+DVI+TV and connecting only the DVI cable
> I can still reproduce this bug.
[...]
> Only every second time in 1280x1024 mode I get a DVI out put
> (ditto: once vt1 console stays blank and next time I see shell
> running in vt1 again.).  A diff
> of /var/log/XFree86.0.log{.old,}, first with DVI signal and second
> run without DVI signal, shows _no_ differences except for the startup
> time.
> 
> Adding "1600x1200" to Modes, I get no DVI output at all.
> (DVI output on this 1600x1200 TFT works fine here with the
> radeon driver and Radeon 7000 and 7500 cards).
[...]
> Looks like bug 243575 is not fixed.

Please run the following commands from a shell prompt to gather and
deliver some further information to us:

$ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1
$ mailx -s "Re: Bug#243575" 243575@bugs.debian.org < /tmp/output

If you do not have a "mailx" command on your system, you can get by
installing the "mailx" Debian package; for example, with the "aptitude
install mailx" or "apt-get install mailx" commands as root.  Alternatively,
you can also use a mail command that is compatible with mailx's
command-line syntax, such as "mutt".

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.  The reportbug
program 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 in the future.

"reportbug" will also include this information if you choose to followup
to an existing bug report, which is nice.

-- 
G. Branden Robinson                |
Debian GNU/Linux                   |     Music is the brandy of the damned.
branden@debian.org                 |     -- George Bernard Shaw
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature


Reply to: