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 29455] Nouveau TV-out incorrectly detecting load on NV18
Date: Wed, 11 Aug 2010 11:44:40 -0700 (PDT)	[thread overview]
Message-ID: <20100811184440.3AFEC130118@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29455-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

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

--- Comment #1 from Francisco Jerez <currojerez-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org> 2010-08-11 11:44:39 PDT ---
(In reply to comment #0)
> Nouveau is detecting and enabling TV-out, even though nothing is plugged in to
> it.
> 
> This causes the non-X terminals to only offer reduced resolution in the upper
> left corner of the display, and also has a few implications for X. Overall my
> problem seems very similar to bug #26800 .
> 
> I'm afraid I can't help much in solving this problem, for my knowledge of
> kernel internals is close to non-existent, and anyway PowerPC is not supported
> by the Nvidia binary driver.
> 
> I don't care much about the non-X terminals' resolution, but there is one
> annoying problem in X: Firefox (or Iceweasel in Debian) only expands its
> bookmarks menu within the small area in the upper left corner of the screen.
> Also the background in GDM and Gnome is show in reduced resolution in that
> corner, in addition to a full screen version.
> 
> I can get rid of the problems in X by calling "xrandr --output TV-1 --off". A
> permanent fix is the following simple /etc/X11/xorg.conf:
> 
> Section "Monitor" 
>        Identifier      "TV-1"
>        Option          "Ignore" "True" 
> EndSection 
> 
> The problem occurs with Ubuntu 10.04 (Kernel 2.6.33, nouveau
> 0.15+git20100219+9b4118d-0ubuntu5) and with Debian sid (Kernel 2.6.35, nouveau
> 0.16+git20100518+4b8f1a0-1).
> 
> I keep getting messages like this in the Kernel log:
> 
> [ 6399.294705] [drm] nouveau 0000:00:10.0: Output TV-1 is running on CRTC 1
> using output B
> [ 6399.498411] [drm] nouveau 0000:00:10.0: Load detected on output B
> [ 6399.730419] [drm] nouveau 0000:00:10.0: Load detected on output B
> [ 6399.934411] [drm] nouveau 0000:00:10.0: Load detected on output B
> [ 6400.126411] [drm] nouveau 0000:00:10.0: Load detected on output B
> 
> (from Debian)
> 
> [  124.508970] [drm] nouveau 0000:00:10.0: Load detected on output B
> [  150.448932] [drm] nouveau 0000:00:10.0: Load detected on output B
> [  232.721150] [drm] nouveau 0000:00:10.0: Load detected on output B
> [  232.727489] [drm] nouveau 0000:00:10.0: Setting dpms mode 3 on TV encoder
> (output 2)
> [  243.165175] [drm] nouveau 0000:00:10.0: Load detected on output B
> 
> (from Ubuntu)

Ideally you'd take an mmiotrace from the nvidia blob to fix this. I understand
that it's not an option in this case -- a video BIOS dump and a register dump
*might* be enough though: [1] has instructions on dumping video BIOSes, and you
can use [2] after a fresh boot, before loading nouveau.ko to get a register
dump.
Full kernel logs may be useful too.

[1] http://nouveau.freedesktop.org/wiki/DumpingVideoBios
[2] http://cgit.freedesktop.org/~currojerez/tvdump/

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

  parent reply	other threads:[~2010-08-11 18:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 10:12 [Bug 29455] New: Nouveau TV-out incorrectly detecting load on NV18 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-29455-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-08-11 18:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2010-08-12 11:21   ` [Bug 29455] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-12 11:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-12 11:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-12 11:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-12 12:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-12 15:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-12 21:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 11:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 12:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 14:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 15:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-14 20:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-14 21:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15  9:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15  9:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15  9:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15  9:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15  9:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15 13:36   ` 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=20100811184440.3AFEC130118@annarchy.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.