public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: German Gomez Garcia <german@piraos.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with i2c-matroxfb and latest kernel
Date: Fri, 20 Apr 2001 18:01:59 MET-1	[thread overview]
Message-ID: <A5B4671993@vcnet.vc.cvut.cz> (raw)

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
                                                        

             reply	other threads:[~2001-04-20 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 18:01 Petr Vandrovec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19 18:31 Problems with i2c-matroxfb and latest kernel German Gomez Garcia

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=A5B4671993@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=german@piraos.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox