public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-rc2-mm3
Date: Thu, 25 Nov 2004 23:52:23 +0000	[thread overview]
Message-ID: <1101426743l.7616l.0l@werewolf.able.es> (raw)
In-Reply-To: <20041125183137.GA30975@kroah.com> (from greg@kroah.com on Thu Nov 25 19:31:37 2004)


On 2004.11.25, Greg KH wrote:
> > On 2004.11.22, Andrew Morton wrote:
> > > 
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm3/
> > > 
> > 
> > Problem with /sys/bus/i2c/devices empty.
> > 
> > I am running a 2.10-rc2-mm3 kernel with a couple pathes (unrelated to
> > i2c). It shows me an empty directory in /sys/bus/i2c/devices, even
> > if I have all suitable modules loaded:
> 
> Are you sure these are the proper modules for this system?
> 

The same /etc/sysconfig/lm_sensors has been working for many 2.6 kernels ;)

> > Module                  Size  Used by
> > w83627hf               24224  0 
> > i2c_dev                 8192  0 
> > i2c_sensor              3328  1 w83627hf
> > i2c_isa                 2304  0 
> > i2c_i801                7692  0 
> > i2c_core               18560  5 w83627hf,i2c_dev,i2c_sensor,i2c_isa,i2c_i801
> > 
> > On boxes running 2.6.9, the devices are present with the same module list
> > (different adapters)
> 
> Ah, but what about 2.6.9 on this same machine?  Are you sure that the

See below. I booted again on 2.6.9-jam1 (mm1 with fixes collected from LKML).

> i2c_i801 driver is the proper one for this box?  How about the w83627hf
> driver?  Are you sure that chip is on it?
> 

I updated my sensors userspace to latest cvs to check if some kind of
de-synchronisation was the cause:

werewolf:~> sensors -v
sensors version 2.9.0-CVS with libsensors version 2.9.0-CVS

sensors-detect on 2.6.9-mm1:

 Now follows a summary of the probes I have just done.
 Just press ENTER to continue: 

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x2f (and 0x48 0x49)
    Chip `Winbond W83792D' (confidence: 8)

Driver `smbus-arp' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x61
    Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

Driver `it87' (may not be inserted):
  Misdetects:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `ITE IT8705F / IT8712F / SiS 950' (confidence: 8)

Driver `w83627hf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-i801
modprobe i2c-isa
# I2C chip drivers
# no driver for Winbond W83792D yet
modprobe smbus-arp
modprobe w83627hf
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

With this modules (no smbus-arp):
w83627hf               25128  0 
eeprom                  7072  0 
i2c_sensor              3456  2 w83627hf,eeprom
i2c_isa                 2304  0 
i2c_i801                7820  0 
i2c_core               19712  5 w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801

I can see this:

werewolf:~> ls /sys/bus/i2c/devices
0-0050@ 0-0052@ 1-0290@

Now, 2.6.10-rc2-mm3:

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x2f (and 0x48 0x49)
    Chip `Winbond W83792D' (confidence: 8)

Driver `smbus-arp' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x61
    Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

Driver `it87' (may not be inserted):
  Misdetects:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `ITE IT8705F / IT8712F / SiS 950' (confidence: 8)

Driver `w83627hf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)

With same modules inserted:
w83627hf               24224  0 
eeprom                  6168  0 
i2c_sensor              3328  2 w83627hf,eeprom
i2c_isa                 2304  0 
i2c_i801                7692  0 
i2c_core               18560  6 i2c_dev,w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801

werewolf:~# ls /sys/bus/i2c/devices 
0-0050@  0-0052@

So i see the two DIMMS but not the 0x0290 bus.
I'm going to try with the other modules I am missing, smbus-arp and it87, but
this setup works in 2.6.9...

If you need any info, just ask for.

Hope this helps. Thanks.

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-rc2-jam3 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #1



  reply	other threads:[~2004-11-29 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041125022405.5fc37efa.akpm@osdl.org>
2004-11-25 18:31 ` 2.6.10-rc2-mm3 Greg KH
2004-11-25 23:52   ` J.A. Magallon [this message]
     [not found] <9dda34920411271434ef00874@mail.gmail.com>
     [not found] ` <20041127170635.6dbe75cd.akpm@osdl.org>
2004-11-28  2:34   ` 2.6.10-rc2-mm3 Paul Blazejowski
2004-11-22  6:39 2.6.10-rc2-mm3 Andrew Morton
2004-11-22 10:26 ` 2.6.10-rc2-mm3 Paul Mackerras
2004-11-22 13:45 ` 2.6.10-rc2-mm3 Adrian Bunk
2004-11-22 19:15 ` 2.6.10-rc2-mm3 Chris Ross
2004-11-22 23:56 ` 2.6.10-rc2-mm3 Fabio Coatti
2004-11-24 16:19 ` 2.6.10-rc2-mm3 William Lee Irwin III
2004-11-24 18:53 ` 2.6.10-rc2-mm3 Tom Rini
2004-11-25  2:31 ` 2.6.10-rc2-mm3 J.A. Magallon

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=1101426743l.7616l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.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