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."
<[email protected]> | -- Wolfgang Pauli
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
[email protected]