lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 24 Feb 2007 16:31:51 -0800
From:	Petr Vandrovec <vandrove@...cvut.cz>
To:	Ondrej Zary <linux@...nbow-software.org>
CC:	Chris Rankin <rankincj@...oo.com>,
	linux-fbdev-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: Kernel warning from Matrox Framebuffer in 2.6.20.1

Ondrej Zary wrote:
> 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!

Can you try current git tree?  I believe that it is already fixed by 
Jean Delvare checkin from Feb 13th (thanks Jean!)
							Petr


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ