linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Lane <miles.lane@gmail.com>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Jean Delvare <khali@linux-fr.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen
Date: Thu, 21 Apr 2005 01:51:12 -0400	[thread overview]
Message-ID: <a44ae5cd05042022512e840cfa@mail.gmail.com> (raw)
In-Reply-To: <a44ae5cd05041601211c292316@mail.gmail.com>

Your patches seem to have fixed the Oops with I2C, but 
nvidiafb is not working unless I specify more than vmalloc=128M
in the append options.  That is, the default kernel options
do not provide for a working nvidiafb display.

Here's what I get when testing 2.6.12-rc2-mm3
(I verified that your two patches have been applied in my
tree):

Kernel command line: BOOT_IMAGE=Linux ro root=306
video=nvidiafb:1280x1024-16@85 vmalloc=
128M init=/etc/init lang=us apm=power-off nomce

nvidiafb: nVidia device/chipset 10DE0312
nvidiafb: nVidia Corporation NV31 [GeForce FX 5600]
i2c_adapter i2c-0: registered as adapter #0
i2c_adapter i2c-1: registered as adapter #1
i2c_adapter i2c-2: registered as adapter #2
nvidiafb: CRTC0 found
nvidiafb: CRTC1 not found
i2c_adapter i2c-0: master_xfer[0] W, addr=0x50, len=1
i2c_adapter i2c-0: master_xfer[1] R, addr=0x50, len=128
nvidiafb: EDID found from BUS1
i2c_adapter i2c-1: master_xfer[0] W, addr=0x50, len=1
i2c_adapter i2c-1: master_xfer[1] R, addr=0x50, len=128
i2c_adapter i2c-1: master_xfer[0] W, addr=0x50, len=1
i2c_adapter i2c-1: master_xfer[1] R, addr=0x50, len=128
i2c_adapter i2c-1: master_xfer[0] W, addr=0x50, len=1
i2c_adapter i2c-1: master_xfer[1] R, addr=0x50, len=128
nvidiafb: CRTC 0 appears to have a CRT attached
nvidiafb: Using CRT on CRTC 0
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
nvidiafb: cannot ioremap FB base

When I boot, the screen stays black until XFree86 starts up.


-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728

  reply	other threads:[~2005-04-21  5:52 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 ` 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Andrew Morton
2005-03-26  4:50   ` 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 [this message]
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=a44ae5cd05042022512e840cfa@mail.gmail.com \
    --to=miles.lane@gmail.com \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=khali@linux-fr.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).