From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: graphics probing messages: questions
Date: Mon, 11 Feb 2008 18:02:41 -0800 [thread overview]
Message-ID: <47B0FE41.7090804@tlinx.org> (raw)
Maybe this should go to a more specific list, but I had
a question about a dmesg v. Kconfig item.
One option under graphics asks about enabling firmware EDID
and says should be safe. So it's 'yes'
Further down under nVidia FB Support, there is an option
"Enable DDC Support" which tries to use i2c for getting
EDID info and I should say 'Y'.
With those on, in dmesg, I get:
i2c-adapter i2c-0: unable to read EDID block.
i2c-adapter i2c-0: unable to read EDID block.
i2c-adapter i2c-0: unable to read EDID block.
i2c-adapter i2c-1: unable to read EDID block.
i2c-adapter i2c-1: unable to read EDID block.
i2c-adapter i2c-1: unable to read EDID block.
Followed by:
nvidiafb: CRTC 0 appears to have a CRT attached
nvidiafb: Using CRT on CRTC 0
mtrr: base(0xd0000000) is not aligned on a size(0x20000000) boundary
nvidiafb: unable to setup MTRR
Console: switching to colour frame buffer device 80x30
nvidiafb: PCI nVidia NV9 framebuffer (64MB @ 0xD0000000)
vesafb: cannot reserve video memory at 0xd0000000
vesafb: framebuffer at 0xd0000000, mapped to 0xffffc20015200000, using
3072k, total 262144k
vesafb: mode is 1024x768x16, linelength=2048, pages=1
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
fb1: VESA VGA frame buffer device
----
So this means turning "DCC Support" is useless on this machine?
Also, why can't the graphics drivers use a base that is
not aligned on a 0x20000000 boundary? Is this a machine design flaw,
or some limitation in the software?
Thanks muchly,
Linda
reply other threads:[~2008-02-12 2:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47B0FE41.7090804@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.