From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Randy.Dunlap" Subject: Re: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Date: Mon, 28 Mar 2005 09:12:49 -0800 Message-ID: <42483B11.6010203@osdl.org> References: <20050324203118.345c6004.akpm@osdl.org> 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 1DFxrK-0000wX-7c for linux-fbdev-devel@lists.sourceforge.net; Mon, 28 Mar 2005 09:17:02 -0800 Received: from fire.osdl.org ([65.172.181.4] helo=smtp.osdl.org) by sc8-sf-mx2.sourceforge.net with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.41) id 1DFxrJ-00072u-Np for linux-fbdev-devel@lists.sourceforge.net; Mon, 28 Mar 2005 09:17:02 -0800 In-Reply-To: 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"; format="flowed" To: linux-fbdev-devel@lists.sourceforge.net Cc: Andrew Morton , khali@linux-fr.org, miles.lane@gmail.com Miles Lane wrote: > On Thu, 24 Mar 2005 20:31:18 -0800, Andrew Morton wrote: > >>(Added the mailing list - trust that's ok) >> >>Miles Lane wrote: >> >>>Kernel command line: BOOT_IMAGE=Linux ro root=306 video=nvidiafb >>>init=/etc/init lang=us apm=power-off nomce >>>nvidiafb: nVidia device/chipset 10DE0312 >>>nvidiafb: nVidia Corporation NV31 [GeForce FX 5600] >>>nvidiafb: CRTC0 found >>>nvidiafb: CRTC1 not found >>>nvidiafb: EDID found from BUS1 >>>nvidiafb: CRTC 0 appears to have a CRT attached >>>nvidiafb: Using CRT on CRTC 0 >>> >>> >>>>>I am wondering whether the following two lines point to the problem. >>> >>>allocation failed: out of vmalloc space - use vmalloc= to increase size. >>>nvidiafb: cannot ioremap FB base >> >>Quite possibly. >> >>I'll do rc2-mm3 tonight - please test that. It has fixes. > > > Hello Andrew, > > mm3 did not fix the problem. I still get a blank framebuffer console. > I still get these two errors: > allocation failed: out of vmalloc space - use vmalloc= to increase size. > nvidiafb: cannot ioremap FB base > Also, I still get the /sys listing Oops when listing the i2c entries > for the nvidiafb. > Lastly, I get the Oops that halts booting if I include certain other > i2c drivers in the build. > Removing nvidiafb from the build allows me to get a completely usable > build of 2.6.12-rc1-mm3. > > I haven't heard anything from the author of the nvidiafb driver about > the various issues I have reported. I guess that there is some chance that the io_remap_pfn* patches are involved with this. Is there some way to determine exactly which io remap kernel calls are involved in "nvidiafb: cannot ioremap FB base" ? Is that in the exposed source code? If so, where is that source code? If not, can we determine from the binary which calls are being made? Or should I just make a io_remap debug patch that prints out lots of debug info so that we can track this down? -- ~Randy ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click