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 70972] New: Nouveau fails with broken screen on nv40 with kernel 3.12
Date: Mon, 28 Oct 2013 22:01:43 +0000	[thread overview]
Message-ID: <bug-70972-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1861 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=70972

          Priority: medium
            Bug ID: 70972
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: Nouveau fails with broken screen on nv40 with kernel
                    3.12
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: larry.finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 88259
  --> https://bugs.freedesktop.org/attachment.cgi?id=88259&action=edit
Output of dmesg

With nouveau on the graphics adapter on an HP dv2815nr laptop, both console and
X displays show an incorrect scan length with a resulting garbled screen.

The 'lspci -nnv' for this adapter is

00:12.0 VGA compatible controller [0300]: NVIDIA Corporation C67 [GeForce 7150M
/ nForce 630M] [10de:0531] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company Device [103c:30d6]
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
        Memory at f4000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at f0000000 (64-bit, non-prefetchable) [size=16M]
        [virtual] Expansion ROM at c0000000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel modules: nouveau

This device has never worked with nouveau on any kernel. I am trying to make it
work now as the nv driver is failing in certain cases, and fbdev cannot use the
optimum resolution (1600 x 800) for this laptop.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3270 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-10-28 22:01 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 22:01 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-70972-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-09 20:51   ` [Bug 70972] Nouveau fails with broken screen on nv40 with kernel 3.12 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-10  0:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-10  1:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-10 18:35   ` [Bug 70972] [NV67] Modesetting failure at 1280x800 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-13  5:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 20:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 21:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 21:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 22:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-23 15:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-23 16:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-25 20:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22  0:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22  0:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22  1:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 19:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 19:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 19:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 20:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-20 17:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-20 17:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-22 18:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-22 18:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-27 16:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 14:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 15:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-02 18:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 14:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 15:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 15:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 15:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 16:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 16:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:39   ` 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-70972-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.