linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: rivafb still broken in 2.5.59
Date: Tue, 14 Jan 2003 04:09:32 +0100	[thread overview]
Message-ID: <20030114030932.GA1417@fefe.de> (raw)

I am using a Geforce 4 Ti 4200, and with great joy I saw that recent 2.5
kernels actually recognize the PCI IDs of this card, so I tried the
module again.

And indeed, my screen went blank, and then started looking like a whole
lot of tiny moose droppings.  I can log in, I can run ls -l, and I can
see motion, but that's about it.  I write this because rivafb has been
broken for months now (also on my notebook with Geforce2 Go), and it is
now broken in a different way, so I thought I'd mention it, since
someone appears to be working on it.

You know, it would help a lot if that someone would publish his email
address somewhere.

Felix

             reply	other threads:[~2003-01-14 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  3:09 Felix von Leitner [this message]
2003-01-15  0:29 ` rivafb still broken in 2.5.59 James Simmons

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=20030114030932.GA1417@fefe.de \
    --to=felix-linuxkernel@fefe.de \
    --cc=linux-kernel@vger.kernel.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 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).