From: Paul Mundt <lethal@linux-sh.org>
To: Thomas Themel <themel-lkml@iwoars.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rivafb still broken in 2.6.0-test2?
Date: Mon, 28 Jul 2003 18:04:40 -0400 [thread overview]
Message-ID: <20030728220440.GB29466@linux-sh.org> (raw)
In-Reply-To: <20030728182822.GG391@iwoars.net>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On Mon, Jul 28, 2003 at 08:28:22PM +0200, Thomas Themel wrote:
> The original problem was encountered on a UP kernel running ACPI, local
> APIC and MTRR support, but removing these features didn't help.
>
> This is what rivafb has to say:
>
> rivafb: nVidia device/chipset 10DE0171
> rivafb: Detected CRTC controller 0 being used
> rivafb: PCI nVidia NV20 framebuffer ver 0.9.5b (nVidiaGeForce4-M, 64MB @ 0xD0000000)
> Console: switching to colour frame buffer device 80x30
>
> with MTRR enabled, it's:
>
> rivafb: nVidia device/chipset 10DE0171
> rivafb: Detected CRTC controller 0 being used
> rivafb: RIVA MTRR set to ON
> rivafb: PCI nVidia NV20 framebuffer ver 0.9.5b (nVidiaGeForce4-M, 64MB @ 0xD0000000)
> Console: switching to colour frame buffer device 80x30
>
> but gives the same result. Is this supposed to work?
>
Not sure about the GeForce4's, but I can attest that rivafb works fine under
-test1 and -test2 on my GeForce2:
rivafb: nVidia device/chipset 10DE0150
rivafb: RIVA MTRR set to ON
rivafb: PCI nVidia NV10 framebuffer ver 0.9.5b (nVidiaGeForce2-G, 32MB @ 0xE8000000)
Console: switching to colour frame buffer device 128x48
I'm running on SMP, and don't have ACPI enabled. MTRR support also works fine
for me.
The problem you have seems isolated to your board/chip.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-07-28 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 18:28 Thomas Themel
2003-07-28 22:04 ` Paul Mundt [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=20030728220440.GB29466@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=themel-lkml@iwoars.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
all inboxes | Powered by JetHome®