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. Sure, without the FB memory, video won't show up. And the 2 lines are directly related -- same error printed from 2 different places. >>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. Here's a tiny patch to get started. Hopefully it will show us why ioremap is failing... Another issue while looking at this code: there is some __initdata in nvidia.c that should be __devinitdata (deja vu) Miles, after using this patch, please also test by booting with "vmalloc=512M" (or "vmalloc=256M" if you don't have 512 MB to spare). -- ~Randy