From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Walrond Subject: Re: Rivafb won't work with DVI connector Date: Wed, 24 Nov 2004 23:01:02 +0000 Message-ID: <200411242301.02046.andrew@walrond.org> References: <200411191137.14649.andrew@walrond.org> <200411231801.14328.andrew@walrond.org> <200411240226.03203.adaplas@hotpop.com> Reply-To: linux-fbdev-devel@lists.sourceforge.net Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1CX69S-0000Vu-Tj for linux-fbdev-devel@lists.sourceforge.net; Wed, 24 Nov 2004 15:02:18 -0800 Received: from [62.24.231.113] (helo=cenedra.walrond.org) by sc8-sf-mx2.sourceforge.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.41) id 1CX69Q-0007Lb-6e for linux-fbdev-devel@lists.sourceforge.net; Wed, 24 Nov 2004 15:02:18 -0800 In-Reply-To: <200411240226.03203.adaplas@hotpop.com> Content-Disposition: inline Sender: linux-fbdev-devel-admin@lists.sourceforge.net Errors-To: linux-fbdev-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: linux-fbdev-devel@lists.sourceforge.net Cc: "Antonino A. Daplas" On Tuesday 23 Nov 2004 18:26, Antonino A. Daplas wrote: > > Does vesafb work in x86_64? If it does you can add this in your > commandline: > > vga=0x307 > > 0x306 is the code for 1280x1024, see Documentation/fb/vesafb.txt. > > Then check your dmesg if the panel size also changed. If it did, then > you can do this: > > vga=0x307 video=nvidiafb:1280x1024@60. > If I did this right, it doesn't help. I built in the vesafb as well as your new nvidafb, then booted with the commandline vga=0x31b video=nvidiafb:1280x1024-32@60 It looks like the nvidafb got the first bite of the cherry: ... 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) vesafb: probe of vesafb0 failed with error -6 ... Do you know if the nvidia developers lurk on lkml? I seem to remember somebody saying that they do. If so, is it worth asking them for a bit of help with this? I know they're not about to open source their binary driver due to ip license problems, but the information we require to overcome this problem in the fb driver is probably quite trivial in nature. I assume they have been forthcoming in the past wrt the open source X driver. What do you think? Worth asking? 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/