public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Problems with i2c-matroxfb and latest kernel
@ 2001-04-19 18:31 German Gomez Garcia
  0 siblings, 0 replies; 2+ messages in thread
From: German Gomez Garcia @ 2001-04-19 18:31 UTC (permalink / raw)
  To: Mailing List Linux Kernel

	Hello,

	After downloading latest 2.4.3-ac9 kernel and compiling it I found
that when I insert the i2c-matroxfb module, the modprobe utility
completely monopolize the system during about a minute everything gets
really slow and it seems that it do something on the virtual consoles
during this time, because if I change virtual console my monitor gets out
of sync for an instant, the same that happens when you have the consoles
set to different resolution/refresh rate. Everything gets fixed after it
load. 

	Any clue?

	- german

PS: Please CC'd to me as I'm not subscribed to the list.
-------------------------------------------------------------------------
German Gomez Garcia         | "This isn't right.  This isn't even wrong."
<german@piraos.com>         |                         -- Wolfgang Pauli


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Problems with i2c-matroxfb and latest kernel
@ 2001-04-20 18:01 Petr Vandrovec
  0 siblings, 0 replies; 2+ messages in thread
From: Petr Vandrovec @ 2001-04-20 18:01 UTC (permalink / raw)
  To: German Gomez Garcia; +Cc: linux-kernel

On 19 Apr 01 at 20:31, German Gomez Garcia wrote:
>     After downloading latest 2.4.3-ac9 kernel and compiling it I found
> that when I insert the i2c-matroxfb module, the modprobe utility
> completely monopolize the system during about a minute everything gets
> really slow and it seems that it do something on the virtual consoles

Hi German,
  try it without connected monitor. It looks to me like that
DDC's SDA and SCL pins are connected to ground in your monitor
and/or your monitor cable. If they are stuck, it takes very long
before i2c code gives up (1s timeout; BTW, there is a bug,
adap->timeout in i2c_bit_add_bus should be set to HZ and not to 100,
if it is doing what I think it does... besides that I thought that
it is caller responsibility to set timeout).

  You should compile i2c-algo-bit as module and use insmod it
with 'bit_test=1' parameter. It should do some tests on these pins
to find whether they are stuck in 0 or in 1. You can also try
'i2c_debug=3' ...

  And last question - which matrox hardware do you have?
                                                    Thanks,
                                                        Petr Vandrovec
                                                        vandrove@vc.cvut.cz
                                                        

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-04-20 16:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-04-20 18:01 Problems with i2c-matroxfb and latest kernel Petr Vandrovec
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19 18:31 German Gomez Garcia

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox