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 40747] New: The new nouveau kernel module fails to use my monitor's native resolution
Date: Fri,  9 Sep 2011 13:51:31 -0700 (PDT)	[thread overview]
Message-ID: <bug-40747-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: The new nouveau kernel module fails to use my
                    monitor's native resolution
           Product: xorg
           Version: unspecified
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: monnier-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=51019)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=51019)
Problematic boot with vanilla 3.0.4

Up until a while ago, the nouveau kernel module allowed me to move my 1600x1200
monitor from the VGA port to the DVI port of my card (before that I used the
`nv' X driver which wasn't able to setup the DVI output with the needed
resolution).  So all was well.
But starting a while ago (not sure when), the nouveau driver started to fail to
use my monitor's native resolution (it uses 1280x960 rather than 1600x1200). 
I'm using Debian built kernels usually and saw the difference somewhere between
Debian's 2.6.32-5 and 2.6.39-2.

To make sure the problem is not on Debian's side, I compiled my own vanilla
3.0.4 kernel (compiled with the same .config as Debian's), which showed the
same problem.

Debian maintainers told me (see debian bug#631582) to send you the dmesg log
with drm.debug=6, so here are three such boot logs: the successful one with
Debian's 2.6.32-5, the unsuccessful one with vanilla 3.0.4, and finally the
half-successful one with Debian's 3.0.0-1 combined with a "video=1600x1200"
argument, which gives me the right resolution (tho with a warning from my
monitor that I'm using a "non optimal" mode, and my monitor (samsung 214t)
seems to think I'm using a 1920x1200 mode for some odd reason).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-09-09 20:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09 20:51 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-40747-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-09-09 20:52   ` [Bug 40747] The new nouveau kernel module fails to use my monitor's native resolution bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-09 20:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-09 22:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10  0:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10  3:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 13:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 14:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 20:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 21:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-10 21:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-13 23:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-14 14:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-14 14:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-14 14:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-11-03 21:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 16:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 10:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 10:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05  4:18   ` [Bug 40747] [NV44] dual-link tmds no longer allowed bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05  4:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05  9:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 19:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-06 14:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-10  0:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:27   ` 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-40747-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.