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: Mon, 22 Nov 2004 23:47:17 +0000 [thread overview]
Message-ID: <200411222347.17562.andrew@walrond.org> (raw)
In-Reply-To: <200411230613.02227.adaplas@hotpop.com>
On Monday 22 Nov 2004 22:13, Antonino A. Daplas wrote:
>
> Try this patch (reverse the previous one first)
>
> - update code against the latest CVS version of Xorg
> - added VESA blanking support
> - added backlight support for powermacs
> - added hardware cursor support using option 'hwcur'.
> - clean-up of i2c code
>
> Let me know, again, of the results. Thanks.
>
Ok; getting closer. In all cases booting with DVI connection:
Booting with no module params gives an almost working 80x30 console, but
shifted/wrapped half a screen to the right as with the previous version.
nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 not found
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)
Note the erroneous panel detection; this is a 1600x1200 tft lcd. The panel is
detected as 1024x768 in every following case.
Now, with params. If I omit the @60 refresh rate, all I get is a screen of
dots; I can make out that there is are a couple of penguin smeared across the
top, but thats about all. So all the following have @60 which produces a
better display.
video=nvidia:1024x768-16@60
This produces a readable 128x48 display, but shifted about a quarter of a
display to the right. The penguins are a bit disjointed aswell.
nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 not found
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 128x48
nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)
video=nvidia:1024x768-32@60
Same results as -16, but my test programme confirms display is 32bpp.
Dmesg is identical
Interestingly, on all the shifted/wrapped displays, If I hit ctrl-L to clear
the screen, the prompt moves back to the correct position for just that one
top line. The next and subsequent lines are shifted right again.
video=nvidia:1280x1024-16@60
video=nvidia:1280x1024-32@60
video=nvidia:1600x1200-16@60
video=nvidia:1600x1200-32@60
All modes above 1024x768 produce the same result; a FULLY WORKING console, but
ONLY AT 80x25. No sign of the shifting/wrapping problem though.
nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 not found
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)
So, the main problems as I see them are:
- Panel is misdetected as 1024x768. Refresh rates are also likely misdetected
since I only get gibberish unless I add @60 (although monitor doesn't report
"out of range")
- Displays <= 1024x768 have this shifted/wrapped to the right problem.
Getting closer though!
I'll try the dsub connection next.
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-22 23:47 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 [this message]
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
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=200411222347.17562.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 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).