linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Paalanen <pq@iki.fi>
To: Pavel Machek <pavel@ucw.cz>
Cc: Stephane Marchesin <stephane.marchesin@gmail.com>,
	nouveau@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Nouveau] 2.6.33 vs. NVIDIA GForce GT 220
Date: Thu, 28 Jan 2010 16:38:01 +0000	[thread overview]
Message-ID: <20100128183801.2182c6f2@daedalus.pq.iki.fi> (raw)
In-Reply-To: <6a89f9d51001271828t54a28002k21ec96692af196b9@mail.gmail.com>

On Wed, 27 Jan 2010 18:28:06 -0800
Stephane Marchesin <stephane.marchesin@gmail.com> wrote:

> On Tue, Jan 26, 2010 at 01:47, Pavel Machek <pavel@ucw.cz> wrote:
> > Hi!
> >
> >> > > I tried enabling staging nvidia driver on GT220, but
> >> > > apparently driver does not know about it. Unfortunately, I
> >> > > have one of those cards here.
> >> > >
> >> > > (I wonder... is there better mailing list? MAINTAINERS
> >> > > only lists linux-fbdev....)
> >>
> >> The list is nouveau@lists.freedesktop.org. And driver knows
> >> about GT220 just fine, I've been using it for a month or two
> >> on GT220 already. Don't bother
> >
> > Perhaps nouveau@lists.freedesktop.org should be added to
> > MAINTAINERS?
> >
> >> about the "supported cards" lists in xf86-video-nouveau or
> >> wherever else, the driver will happily bind to any nvidia
> >> video card with known generation, even if nobody has seen that
> >> precise model before.
> >
> > Unfortunately, the driver does not seem happy:
> >
> > Jan 18 12:56:38 pma kernel: [    0.491073] nvidiafb
> > 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> > Jan 18 12:56:38 pma kernel: [    0.491507] nvidiafb: Device ID:
> > 10de0a20
> > Jan 18 12:56:38 pma kernel: [    0.491546] Chipset is 10de0a20
> > Jan 18 12:56:38 pma kernel: [    0.491584] nvidiafb: unknown
> > NV_ARCH Jan 18 12:56:38 pma kernel: [    0.492119] vga16fb:
> > initializing
> >
> 
> Hmm, but this is not nouveau, this is nvidiafb...

And both nvidiafb and vga16fb are known make Nouveau misbehave:
nvidiafb because it messes up the card state, and vga16fb because it
does not do the fb driver hand-over, AFAIK.

Relevant or not, I'd like to advertise our new troubleshooting page:
http://nouveau.freedesktop.org/wiki/TroubleShooting

I'm also adding the CCs that were dropped earlier.

Was the original question in this thread about nvidiafb or Nouveau?


Thanks.

-- 
Pekka Paalanen
http://www.iki.fi/pq/

      parent reply	other threads:[~2010-01-28 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 13:43 2.6.33 vs. NVIDIA GForce GT 220 Pavel Machek
2010-01-23 18:18 ` Marcin Slusarz
     [not found]   ` <201001231828.00557.koriakin@0x04.net>
     [not found]     ` <20100126094740.GC10858@atrey.karlin.mff.cuni.cz>
     [not found]       ` <6a89f9d51001271828t54a28002k21ec96692af196b9@mail.gmail.com>
2010-01-28 16:38         ` Pekka Paalanen [this message]

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=20100128183801.2182c6f2@daedalus.pq.iki.fi \
    --to=pq@iki.fi \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=pavel@ucw.cz \
    --cc=stephane.marchesin@gmail.com \
    /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).