From: Ondrej Zary <linux@rainbow-software.org>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Kernel warning from Matrox Framebuffer in 2.6.20.1
Date: Sat, 24 Feb 2007 18:18:24 +0100 [thread overview]
Message-ID: <200702241818.24675.linux@rainbow-software.org> (raw)
In-Reply-To: <306590.53720.qm@web52912.mail.yahoo.com>
On Saturday 24 February 2007 14:08, Chris Rankin wrote:
> Hi,
>
> I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX
> graphics card. This machine uses the Matrox framebuffer and TV-OUT modules,
> and I have found these warnings in the kernel log:
>
> **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical
> device; fix it! **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to
> specify physical device; fix it! **WARNING** I2C adapter driver [MAVEN:fb0]
> forgot to specify physical device; fix it!
I'm seeing something like that since installing 2.6.20.1 yesterday:
matroxfb: Matrox Mystique (PCI) detected
PInS memtype = 0
matroxfb: MTRR's turned on
matroxfb: 1024x768x8bpp (virtual: 1024x4096)
matroxfb: framebuffer at 0xE1000000, mapped to 0xcc880000, size 4194304
Console: switching to colour frame buffer device 128x48
fb0: MATROX frame buffer device
**WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device;
fix it!
> The relevant kernel modules seem to be:
>
> matroxfb_maven 13228 0
> i2c_matroxfb 4064 0
> i2c_algo_bit 6312 1 i2c_matroxfb
>
> Cheers,
> Chris
--
Ondrej Zary
next prev parent reply other threads:[~2007-02-24 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 13:08 Kernel warning from Matrox Framebuffer in 2.6.20.1 Chris Rankin
2007-02-24 17:18 ` Ondrej Zary [this message]
2007-02-25 0:31 ` Petr Vandrovec
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=200702241818.24675.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@yahoo.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).