linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: bugzilla-daemon@bugzilla.kernel.org, ericitaquera@gmail.com,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 13566] New: nvidiafb doesn't get my oooold monitor working
Date: Mon, 29 Jun 2009 16:04:42 -0700	[thread overview]
Message-ID: <20090629160442.0cbd68b8.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-13566-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Thu, 18 Jun 2009 13:04:12 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=13566
> 
>            Summary: nvidiafb doesn't get my oooold monitor working
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.30
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Video(Other)
>         AssignedTo: drivers_video-other@kernel-bugs.osdl.org
>         ReportedBy: ericitaquera@gmail.com
>         Regression: No

There's more info at the above link

> 
> Nvidiafb doesn't get my ooooooold black & white 7" CRT VGA monitor working. I
> have an GeForce 6200 one:
> 
> root@slackade:~# lspci  | grep -i vga
> 01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200
> TurboCache(TM)] (rev a1)
> 
> 
> This is the dmesg output with this old monitor ( or without any ) plugged to
> the VGA output:
> 
> root@slackade:~# dmesg | grep nvidia
> nvidiafb 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> nvidiafb: Device ID: 10de0161 
> nvidiafb: CRTC0 analog not found
> nvidiafb: CRTC1 analog not found
> nvidiafb: CRTC 1 is currently programmed for TV
> nvidiafb: Using TV on CRTC 1
> nvidiafb: Panel is TMDS
> nvidiafb: MTRR set to ON
> nvidiafb: Flat panel dithering disabled
> nvidiafb: PCI nVidia NV16 framebuffer (64MB @ 0xD0000000)
> root@slackade:~# 
> 
> After that, even if I switch to a brand new 1080p lcd the screen just blinks
> with weird vertical stripes.
> 
> If I reboot with a newer monitor plugged to VGA output all works fine:
> 
> root@slackade:~# dmesg | grep nvidia
> nvidiafb 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> nvidiafb: Device ID: 10de0161 
> nvidiafb: CRTC0 analog found
> nvidiafb: CRTC1 analog not found
> nvidiafb: CRTC 0 appears to have a CRT attached
> nvidiafb: Using CRT on CRTC 0
> nvidiafb: MTRR set to ON
> nvidiafb: PCI nVidia NV16 framebuffer (64MB @ 0xD0000000)
> root@slackade:~# 
> 
> Tnx in advance!
> 

hm.  drivers/video/nvidia/ isn't exactly a hive of development activity
but let's switch this over to the mailing list and see if there's any
help.


------------------------------------------------------------------------------

       reply	other threads:[~2009-06-29 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-13566-10286@http.bugzilla.kernel.org/>
2009-06-29 23:04 ` Andrew Morton [this message]
2009-06-30  3:11   ` [Bugme-new] [Bug 13566] New: nvidiafb doesn't get my oooold monitor working eric miranda

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=20090629160442.0cbd68b8.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=ericitaquera@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).