From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 15729] New: nouveau fails to get ddc info from screen
Date: Sat, 26 Apr 2008 18:15:03 -0700 (PDT) [thread overview]
Message-ID: <bug-15729-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=15729
Summary: nouveau fails to get ddc info from screen
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: low
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: GatoLoko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=16203)
--> (http://bugs.freedesktop.org/attachment.cgi?id=16203)
Xorg log
Trying xrandr I got a weird maximun screen size.
Talking about this with somebody, he pointed that it may be because nouveau
can't access ddc info.
It's a mainboard integrated NV4E (gforce 6150LE / cuadro nvs 210s)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-04-27 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 1:15 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-15729-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-04-28 1:17 ` [Bug 15729] nouveau fails to get ddc info from screen bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-29 9:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-29 12:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-29 14:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-29 14:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-29 14:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-29 15:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-05-06 18: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-15729-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.