From: Andrew Morton <akpm@osdl.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: khali@linux-fr.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen
Date: Thu, 24 Mar 2005 20:31:18 -0800 [thread overview]
Message-ID: <20050324203118.345c6004.akpm@osdl.org> (raw)
In-Reply-To: <a44ae5cd0503242023233dc23f@mail.gmail.com>
(Added the mailing list - trust that's ok)
Miles Lane <miles.lane@gmail.com> 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=<size> to increase size.
> nvidiafb: cannot ioremap FB base
Quite possibly.
I'll do rc2-mm3 tonight - please test that. It has fixes.
> CONFIG_AGP_NVIDIA=y
> CONFIG_I2C=y
> CONFIG_I2C_CHARDEV=m
> CONFIG_I2C_ALGOBIT=y
> CONFIG_I2C_ALGOPCF=m
> CONFIG_I2C_ALGOPCA=m
> CONFIG_I2C_ISA=m
> CONFIG_I2C_NFORCE2=m
>
> CONFIG_FB=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> CONFIG_FB_SOFT_CURSOR=y
> CONFIG_FB_MODE_HELPERS=y
> CONFIG_FB_TILEBLITTING=y
> CONFIG_VIDEO_SELECT=y
> CONFIG_FB_NVIDIA=y
> CONFIG_FB_NVIDIA_I2C=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
-------------------------------------------------------
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
next parent reply other threads:[~2005-03-25 4:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a44ae5cd0503242023233dc23f@mail.gmail.com>
2005-03-25 4:31 ` Andrew Morton [this message]
2005-03-26 4:50 ` 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Miles Lane
2005-03-28 17:12 ` Randy.Dunlap
2005-03-29 0:22 ` Miles Lane
2005-03-29 0:37 ` Randy.Dunlap
2005-03-29 0:56 ` Miles Lane
2005-03-29 1:02 ` Randy.Dunlap
2005-03-29 1:12 ` Miles Lane
2005-03-29 3:01 ` Randy.Dunlap
2005-03-29 9:16 ` Jean Delvare
2005-03-29 1:13 ` Andrew Morton
2005-03-29 3:56 ` Miles Lane
2005-03-29 4:34 ` Randy.Dunlap
2005-03-29 16:25 ` [PATCH] nvidiafb: fix section references Randy.Dunlap
2005-04-14 5:51 ` Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Antonino A. Daplas
2005-04-14 17:06 ` Jean Delvare
2005-04-15 3:07 ` Antonino A. Daplas
2005-04-14 5:51 ` Antonino A. Daplas
2005-04-14 17:13 ` Jean Delvare
2005-04-14 18:19 ` Miles Lane
2005-04-15 3:07 ` Antonino A. Daplas
2005-04-15 3:07 ` Antonino A. Daplas
2005-04-16 8:21 ` Miles Lane
2005-04-21 5:51 ` Miles Lane
2005-04-21 16:22 ` Randy.Dunlap
2005-04-21 18:36 ` Randy.Dunlap
2005-04-23 0:03 ` Miles Lane
2005-04-23 0:12 ` Miles Lane
2005-04-24 17:09 ` Miles Lane
2005-04-25 3:21 ` Antonino A. Daplas
2005-04-25 20:31 ` Miles Lane
2005-04-25 20:33 ` Miles Lane
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=20050324203118.345c6004.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=khali@linux-fr.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=miles.lane@gmail.com \
/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).