linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH] GeForce 5200 on rivafb
@ 2004-12-11 15:22 Antonino A. Daplas
  2004-12-11 18:21 ` Junio C Hamano
  0 siblings, 1 reply; 12+ messages in thread
From: Antonino A. Daplas @ 2004-12-11 15:22 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: linux-fbdev-devel

--- Junio C Hamano <junkio@cox.net> wrote:

> >>>>> "AAD" == Antonino A Daplas
> <adaplas@hotpop.com> writes:
> 
Dec 10 19:04:40 siamese kernel: nvidiafb: nVidia device/chipset 
10DE0110
Dec 10 19:04:40 siamese kernel: nvidiafb: nVidia Corporation NV11 
[GeForce2 MX/MX 400]
Dec 10 19:04:40 siamese kernel: nvidiafb: EDID found from BUS1

The EDID block is properly detected, so that's a good sign.

Dec 10 19:04:40 siamese kernel:       Display is GTF capable
Dec 10 19:04:40 siamese kernel: nvidiafb: Unable to detect which 
CRTCNumber...
Dec 10 19:04:40 siamese kernel: ...Defaulting to CRTCNumber 1
Dec 10 19:04:40 siamese kernel: nvidiafb: Using DFP on CRTC 1
Dec 10 19:04:40 siamese kernel: Panel size is 1 x 1

Panel size of 1x1 is a bad sign.  (Panel size is set by video BIOS).

Can you try the following:

1. Change this line in drivers/video/fbmon.c

#undef DEBUG

to 

#define DEBUG

2. Experiment with the following boot options:
forceCRTC (values are 0 or 1) and flatpanel. 

So you can try this, for a start:

video=nvidiafb:forceCRTC:1

3.  If you see the penguin, but no text, do an fbset -accel false.

Tony




-------------------------------------------------------
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/

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [PATCH] GeForce 5200 on rivafb
@ 2004-12-11 21:11 Antonino A. Daplas
  2004-12-12  2:25 ` Junio C Hamano
  0 siblings, 1 reply; 12+ messages in thread
From: Antonino A. Daplas @ 2004-12-11 21:11 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: linux-fbdev-devel


--- Junio C Hamano <junkio@cox.net> wrote:

> Thanks for a quick response.
> 
> >>>>> "AAD" == Antonino A Daplas
> <adaplas@hotpop.com> writes:
> 
> AAD> Dec 10 19:04:40 siamese kernel:       Display
> is GTF capable
> AAD> Dec 10 19:04:40 siamese kernel: nvidiafb:
> Unable to detect which 
> AAD> CRTCNumber...
> AAD> Dec 10 19:04:40 siamese kernel: ...Defaulting
> to CRTCNumber 1
> AAD> Dec 10 19:04:40 siamese kernel: nvidiafb: Using
> DFP on CRTC 1
> AAD> Dec 10 19:04:40 siamese kernel: Panel size is 1
> x 1
> 
> AAD> Panel size of 1x1 is a bad sign.  (Panel size
> is set by video BIOS).
> 
> What should it say normally?  The monitor is a CRT

It should tell you the pre-configured resolution of the display, if the
display is indeed a flatpanel...
> (ViewSonic
> PF775a) connected via a DSub connector.  I have

...which apparently isn't.

> rebuilt the
> kernel without I2C support and the boot log says
> "Defaulting to
> CRTCNumber 0".  With this, I get a working
> framebuffer console
> and fbdev X works on it.

Ah, ok.  The main problem is that the EDID block of your monitor is saying
that it is a flatpanel, not a CRT.

> 
> Dec 10 23:10:22 siamese kernel: nvidiafb: nVidia
> device/chipset 10DE0110
> Dec 10 23:10:22 siamese kernel: nvidiafb: nVidia
> Corporation NV11 [GeForce2 MX/MX 400]
> Dec 10 23:10:22 siamese kernel: nvidiafb: Unable to
> detect display type...
> Dec 10 23:10:22 siamese kernel: ...Using default of
> CRT
> Dec 10 23:10:22 siamese kernel: nvidiafb: Unable to
> detect which CRTCNumber...
> Dec 10 23:10:22 siamese kernel: ...Defaulting to
> CRTCNumber 0
> Dec 10 23:10:22 siamese kernel: nvidiafb: Using CRT
> on CRTC 0
> Dec 10 23:10:22 siamese kernel: nvidiafb: MTRR set
> to ON
> Dec 10 23:10:22 siamese kernel: Console: switching
> to colour frame buffer device 200x75
> Dec 10 23:10:22 siamese kernel: nvidiafb: PCI nVidia
> NV11 framebuffer (64MB @ 0xD8000000)
> 
> AAD> Can you try the following:
> AAD> 1. Change this line in drivers/video/fbmon.c
> 
> AAD> #undef DEBUG
> AAD> to 
> AAD> #define DEBUG
> 
> Will do, but I have one question.  The last time I
> tried
> turning debugging on on rivafb-i2c it was very
> unpleasant;

No :-), this is not for nvidiafb but for the EDID parser, and it will give
you a very descriptive parsing of the EDID block.

> eventually the driver ended up reporting scrolling
> events on the
> console which caused further scrolling which is
> reported on the
> console which caused further scrolling ... ;-).  I
> could not get
> the control back even with SysRQ.  Is there a trick
> to avoid
> this kind of trouble and still have debugging
> enabled?
> 
> AAD> 2. Experiment with the following boot options:
> 
> AAD> So you can try this, for a start:
> AAD> video=nvidiafb:forceCRTC:1
> 
> I presume I should use forceCRTC:0 to match the
> working "sans
> i2c" case.

Forget this part.

> 
> Is it possible that EDID is not being read correctly
> in my
> configuration?  Could it be a hardware problem
> (either the card,
> the monitor, or the connecting cable)?  If so, how

This is a problem in the EDID block.  Displays that support both digital and
analog (dsub) inputs should also have 2 EDID blocks, depending on the
connector attached.  In your case, if it has a dsub connector, then the
monitor should give out an EDID block that says it's analog, not digital.
 
So, with a broken EDID block, I guess your best workaround is to disable
i2c in your kernel config.

BTW:  Why can't you use the 'nv' driver with X? And does rivafb work with
your card?

Tony




-------------------------------------------------------
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/

^ permalink raw reply	[flat|nested] 12+ messages in thread
* [PATCH] GeForce 5200 on rivafb
@ 2004-12-08  1:47 Lucas Correia Villa Real
  2004-12-08 12:34 ` Antonino A. Daplas
  2004-12-23 20:48 ` Guido Guenther
  0 siblings, 2 replies; 12+ messages in thread
From: Lucas Correia Villa Real @ 2004-12-08  1:47 UTC (permalink / raw)
  To: linux-fbdev-devel

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

Hi,

I was trying to figure out why my GeForce FX 5200 wasn't being recognized by 
rivafb, when I saw that its ID was not being included by the driver.

The following patch (against 2.6.10-rc3) allows it to compile and switch to 
graphics mode successfully.

Just a note: the README file shipped with the NVIDIA driver has a complete 
list of device ID's. While it's easy to add them all into riva.c and 
pci_ids.h, I'm not very sure if it's okay to flood them with #defines and by 
increasing heavily the rivafb_pci_tbl table.

Is it ok to do that, or were you waiting to get a feedback from users from 
those cards first? I can provide a patch to include all the missing cards if 
there's no problem on doing that.

Thanks!
Lucas

[-- Attachment #2: rivafb-geforcefx.patch --]
[-- Type: text/x-diff, Size: 1793 bytes --]

diff -X dontdiff-2.6 -Nur 2.6.10-rc3-vanilla/drivers/video/riva/fbdev.c 2.6.10-rc3-lucasvr/drivers/video/riva/fbdev.c
--- 2.6.10-rc3-vanilla/drivers/video/riva/fbdev.c	2004-12-07 09:58:14.000000000 -0200
+++ 2.6.10-rc3-lucasvr/drivers/video/riva/fbdev.c	2004-12-07 22:45:52.000000000 -0200
@@ -192,6 +192,10 @@
 	  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
 	{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_QUADRO4_700XGL,
 	  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
+	{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_GEFORCE_FX_5200_ULTRA,
+	  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
+	{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_GEFORCE_FX_5200,
+	  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
 	{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_GEFORCE_FX_GO_5200,
 	  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
 	{ 0, } /* terminate list */
@@ -1876,6 +1880,8 @@
 		case 0x0300:   /* GeForceFX 5800 */
 		case 0x0310:   /* GeForceFX 5600 */
 		case 0x0320:   /* GeForceFX 5200 */
+		case 0x0321:   /* GeForceFX 5200 Ultra */
+		case 0x0322:   /* GeForceFX 5200 */
 		case 0x0330:   /* GeForceFX 5900 */
 		case 0x0340:   /* GeForceFX 5700 */
 		     arch =  NV_ARCH_30;
diff -X dontdiff-2.6 -Nur 2.6.10-rc3-vanilla/include/linux/pci_ids.h 2.6.10-rc3-lucasvr/include/linux/pci_ids.h
--- 2.6.10-rc3-vanilla/include/linux/pci_ids.h	2004-12-07 09:58:25.000000000 -0200
+++ 2.6.10-rc3-lucasvr/include/linux/pci_ids.h	2004-12-07 22:45:29.000000000 -0200
@@ -1144,6 +1144,8 @@
 #define PCI_DEVICE_ID_NVIDIA_QUADRO4_900XGL	0x0258
 #define PCI_DEVICE_ID_NVIDIA_QUADRO4_750XGL	0x0259
 #define PCI_DEVICE_ID_NVIDIA_QUADRO4_700XGL	0x025B
+#define PCI_DEVICE_ID_NVIDIA_GEFORCE_FX_5200_ULTRA 0x0321
+#define PCI_DEVICE_ID_NVIDIA_GEFORCE_FX_5200    0x0322
 #define PCI_DEVICE_ID_NVIDIA_GEFORCE_FX_GO_5200	0x0329
 
 #define PCI_VENDOR_ID_IMS		0x10e0

^ permalink raw reply	[flat|nested] 12+ messages in thread
end of thread, other threads:[~2004-12-24 19:43 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-11 15:22 [PATCH] GeForce 5200 on rivafb Antonino A. Daplas
2004-12-11 18:21 ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2004-12-11 21:11 Antonino A. Daplas
2004-12-12  2:25 ` Junio C Hamano
2004-12-12 10:00   ` Junio C Hamano
2004-12-13 20:52     ` Antonino A. Daplas
2004-12-13 21:47       ` Antonino A. Daplas
2004-12-14  7:51         ` Junio C Hamano
2004-12-08  1:47 Lucas Correia Villa Real
2004-12-08 12:34 ` Antonino A. Daplas
2004-12-10  1:46   ` Lucas Correia Villa Real
2004-12-10 20:43     ` Antonino A. Daplas
2004-12-11  3:34       ` Junio C Hamano
2004-12-23 20:48 ` Guido Guenther

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).