Re: 2.6.5 Sensors & USB problems

[Ian Morgan]

Yeah, bad form to reply to one's self, but someone may appreciate this info:

Seems that the w83781d driver no longer detects whatever the sensor chip on
the P4PE is, but I see there is now a new driver called asb100 which does
work. An old conflicting lm_sensors install was breaking the sensors-detect
script, but once resolved it nicely detected the asb100.

Can anyone explain, however, why my i2c bus showed up as number 0 under
linux <= 2.6.4, and now always as number 1 under linux 2.6.5? The is no
number 0 any more.

Regards,
Ian Morgan

-- 
-------------------------------------------------------------------
 Ian E. Morgan          Vice President & C.O.O.       Webcon, Inc.
 imorgan at webcon dot ca        PGP: #2DA40D07      www.webcon.ca
    *  Customized Linux network solutions for your business  *
-------------------------------------------------------------------


On Sat, 17 Apr 2004, Ian Morgan wrote:

> On Wed, 7 Apr 2004, Jean Delvare wrote:
> 
> > Hi Ben,
> > 
> > > 2.6.5-rc1 -> sensors broke (ERROR: Can't get <sensor> data!)
> > 
> > Your sensors problem will be resolved as soon as you switch to the just
> > released lm_sensors 2.8.6.
> 
> I use the same w83781d and i2c_i801 drivers on my Asus P4PE box, and they
> too went belly up with 2.6.5. However, I HAVE tried lm_sensors 2.8.6 and
> that made no difference. They're just user-space tools that don't touch the
> kernel any more in 2.6.x (right?).
> 
> The problem I am seeing now in 2.6.5 is that after loading the w83781d
> module, nothing shows up in /sys or /proc, as though the module had not
> loaded but lsmod says it is loaded.
> 
> In 2.6.4, my sensors showed up hare:
> /sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002d/* (w83781d)
> /sys/devices/pci0000:00/0000:00:1f.3/i2c-0/1-0050/* (eeprom)
> 
> Now in 2.6.5, with both eeprom and w83781d modules loaded, I only get the
> eeprom, and the w83781d is nowhere to be found:
> /sys/devices/pci0000:00/0000:00:1f.3/i2c-1/1-0050/* (eeprom)
> 
> # find /sys/bus/i2c/drivers/
> /sys/bus/i2c/drivers/
> /sys/bus/i2c/drivers/w83781d
> /sys/bus/i2c/drivers/eeprom
> /sys/bus/i2c/drivers/eeprom/1-0050
> /sys/bus/i2c/drivers/dev_driver
> /sys/bus/i2c/drivers/i2c_adapter
> 
> This certainly shows that the driver is loaded, but has not found/registered
> any devices?
> 
> Regards,
> Ian Morgan
> 
> -- 
> -------------------------------------------------------------------
>  Ian E. Morgan          Vice President & C.O.O.       Webcon, Inc.
>  imorgan at webcon dot ca        PGP: #2DA40D07      www.webcon.ca
>     *  Customized Linux network solutions for your business  *
> -------------------------------------------------------------------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


Regards,
Ian Morgan

-- 
-------------------------------------------------------------------
 Ian E. Morgan          Vice President & C.O.O.       Webcon, Inc.
 imorgan at webcon dot ca        PGP: #2DA40D07      www.webcon.ca
    *  Customized Linux network solutions for your business  *
-------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/