All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 16120] New: White or black vertical stripes/ fencing on whole display with NV34M
Date: Tue, 27 May 2008 11:35:49 -0700 (PDT)	[thread overview]
Message-ID: <bug-16120-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=16120

           Summary: White or black vertical stripes/fencing on whole display
                    with NV34M
           Product: xorg
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau@lists.freedesktop.org
        ReportedBy: vincent@zerodeux.net
         QAContact: xorg-team@lists.x.org


Created an attachment (id=16772)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=16772)
my Xorg configuration

I just had a first shot at the "nouveau" Xorg driver, I'm a regular
"nv" user. It compiled and installed without a itch in a short time,
congrats (great instructions on
http://nouveau.freedesktop.org/wiki/InstallNouveau), ran fine... but
with a funny vertical fencing effect: one vertical line out of two was
black. After a few minutes, the effect would spontaneously switch (no
input from me, no app activity) to white vertical lines with the same
stripping setup (which gives a "dimming" or "enlightening" effect +
rather crunchy text).

  When reverting to the "nv" driver and simply restarting X, the fencing
effect persisted. So "nv" seems to rely on some BIOS stuff that
"nouveau" fiddles with. I (warm-)rebooted the whole system with the
"nouveau" driver on in order for it to benefit from the BIOS, same
problem. Same procedure while adding the "Option FlatPanel True", same
problem. Then (warm-)reboot with the "nv" driver on, everything working
fine again.

  I have a NV34M on a Dell Inspiron laptop, all details follow (and both
nouveau and nv logs attached):

  - Linux vanilla 2.6.23.1 on i386
  - Xorg 1.4.1~git20080131-4 from Debian 'testing' branch (not
'unstable')
  - nv 2.1.9
  - nouveau (drm + xf86-video-nouveau) from git as 2008-05-23

01:00.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX
Go5200 64M] (rev a1)
        Subsystem: Dell Device 019c
        Flags: bus master, VGA palette snoop, 66MHz, medium devsel,
latency 32, IRQ 11
        Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Expansion ROM at fd000000 [disabled] [size=128K]
        Capabilities: <access denied>

  The screen is a 1920x1200 LCD (physical: 332x207mm, ~150dpi). I can't
provide screenshots as X obviously saw perfectly sane (non-fenced)
display buffers.

  What could I do to help you fix this bug ? It looks like I'm very
close to be able to switch to "nouveau".


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2008-05-27 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 18:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-16120-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-05-27 18:36   ` [Bug 16120] White or black vertical stripes/ fencing on whole display with NV34M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-05-27 18:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-05-27 18:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-16 21:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-07-23 23:40   ` [Bug 16120] White or black vertical stripes/fencing " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-16120-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.