From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 35049] New: Cannot use higher resolutions of monitor
Date: Sat, 5 Mar 2011 18:53:21 -0800 (PST) [thread overview]
Message-ID: <bug-35049-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35049
Summary: Cannot use higher resolutions of monitor
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: sancaktar.1-ZbGKxL/pcrQ@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
I did a fresh Debian install to sid, upgraded to experimental to get xorg
1.9.99.903 (1.10.0 RC 3) then followed the instructions on the nouveau wiki
(http://nouveau.freedesktop.org/wiki/DebianInstall) to build a new kernel and
drivers. This was successful. The problem is that I have a monitor which
supports up to 2560x1600 (which the monitor reports by EDID) but the drivers
will only run at 1280x800. If I use xrandr to resize, I get a desktop that is
compressed to be equivalent to the larger size, but is actually 1280x800. I
have tried adding a virtual line to my monitor section and setting the
preferredmode. These did not help. The Xorg log shows that it detects the
higher resolutions. I tried booting the kernel with video=DVI-I-1:2560x1600.
The kernel FB driver does exactly the same thing, making the text very small
but still actually outputting the lower resolution. I originally thought that
this was a dual-link problem, but I don't think that 1280x800 is even the
maximum for a single DVI cable. The propriety driver works at the higher
resolutions.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-03-06 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 2:53 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-35049-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-03-06 2:58 ` [Bug 35049] Cannot use higher resolutions of monitor bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-06 2:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` 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-35049-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.