From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: Rivafb won't work with DVI connector
Date: Tue, 23 Nov 2004 15:09:24 +0000 [thread overview]
Message-ID: <200411231509.24489.andrew@walrond.org> (raw)
In-Reply-To: <200411232229.00311.adaplas@hotpop.com>
On Tuesday 23 Nov 2004 14:28, Antonino A. Daplas wrote:
>
> Okay, try the attached patch.
>
Ok, booting on dsub without params now results in a good 1024x768 (128x48)
console and boots cleanly. (Note this was a 1600x1200 (200xwhatever) before
the patch, which is the preferred, native resolution of the screen.)
nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
i2c_adapter i2c-0: registered as adapter #0
i2c_adapter i2c-1: registered as adapter #1
i2c_adapter i2c-2: registered as adapter #2
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 found
i2c_adapter i2c-0: master_xfer: with 2 msgs.
nvidiafb: EDID found from BUS1
i2c_adapter i2c-1: master_xfer: with 2 msgs.
nvidiafb: EDID found from BUS2
nvidiafb: CRTC 0appears to have a CRT attached
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 128x48
nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)
Booting on dvi with no kernel params results in a broken (right shifted) 80x30
display as before.
nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
i2c_adapter i2c-0: registered as adapter #0
i2c_adapter i2c-1: registered as adapter #1
i2c_adapter i2c-2: registered as adapter #2
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 not found
i2c_adapter i2c-0: master_xfer: with 2 msgs.
nvidiafb: EDID found from BUS1
i2c_adapter i2c-1: master_xfer: with 2 msgs.
i2c_adapter i2c-1: master_xfer: with 2 msgs.
i2c_adapter i2c-1: master_xfer: with 2 msgs.
nvidiafb: CRTC 1 is currently programmed for DFP
nvidiafb: Using DFP on CRTC 1
Panel size is 1024 x 768
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 80x30
nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)
Booting on dvi with video=nvidiafb:1600x1200-32@60 results in a fully working
console, but only at 80x25
nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
i2c_adapter i2c-0: registered as adapter #0
i2c_adapter i2c-1: registered as adapter #1
i2c_adapter i2c-2: registered as adapter #2
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 not found
i2c_adapter i2c-0: master_xfer: with 2 msgs.
nvidiafb: EDID found from BUS1
i2c_adapter i2c-1: master_xfer: with 2 msgs.
i2c_adapter i2c-1: master_xfer: with 2 msgs.
i2c_adapter i2c-1: master_xfer: with 2 msgs.
nvidiafb: CRTC 1 is currently programmed for DFP
nvidiafb: Using DFP on CRTC 1
Panel size is 1024 x 768
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 80x25
nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)
The Oops has gone though :)
Andrew
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-23 15:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 11:37 Rivafb won't work with DVI connector Andrew Walrond
2004-11-19 22:08 ` Antonino A. Daplas
2004-11-20 15:52 ` Andrew Walrond
2004-11-22 0:11 ` Antonino A. Daplas
2004-11-22 9:23 ` Andrew Walrond
2004-11-22 9:43 ` Andrew Walrond
2004-11-22 22:13 ` Antonino A. Daplas
2004-11-22 23:47 ` Andrew Walrond
2004-11-22 23:54 ` Andrew Walrond
2004-11-23 1:50 ` Antonino A. Daplas
2004-11-23 12:32 ` Andrew Walrond
2004-11-23 14:28 ` Antonino A. Daplas
2004-11-23 15:09 ` Andrew Walrond [this message]
2004-11-23 15:18 ` Antonino A. Daplas
2004-11-23 16:08 ` Andrew Walrond
2004-11-23 17:07 ` Antonino A. Daplas
2004-11-23 18:01 ` Andrew Walrond
2004-11-23 18:26 ` Antonino A. Daplas
2004-11-23 19:00 ` Andrew Walrond
2004-11-23 19:07 ` Andrew Walrond
2004-11-23 19:23 ` Andrew Walrond
2004-11-23 19:59 ` Geert Uytterhoeven
2004-11-23 20:53 ` Andrew Walrond
2004-11-23 22:44 ` Antonino A. Daplas
2004-11-23 23:59 ` Andrew Walrond
2004-11-24 22:38 ` Andrew Walrond
2004-11-23 20:21 ` Chad Daelhousen
2004-11-24 23:01 ` Andrew Walrond
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 0:07 Antonino A. Daplas
2004-11-25 15:27 ` Andrew Walrond
2004-11-25 21:16 ` Antonino A. Daplas
2004-11-26 14:09 ` Antonino A. Daplas
2004-11-27 12:40 ` Andrew Walrond
2004-11-27 18:29 ` Michel Dänzer
2004-11-27 22:35 ` Andrew Walrond
2004-11-27 22:43 ` Antonino A. Daplas
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=200411231509.24489.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=adaplas@hotpop.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 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.