headers
draco | 3 Jan 2010 11:15
Picon
Favicon

Re: Sensors-dectect , Ubuntu 9.04 intel p55 express chipset

Hello all,

I've purchased an ASUS P7P55D Deluxe motherboard, and I see in the 
mailing list archive that there is no support for it now.
The sensor is called "Nuvoton W83667HG-B Super IO Sensors".

How can I help you to develop the driver ?
Do you need some log, informations from dmidecode or other stuff ?

Please let me know if I can be usefull.

Best Regards,
draco

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Permalink | Reply | 0 comments |
headers
Marcus Vogt | 3 Jan 2010 23:53
Picon

SMSC SCH5147-NW not detected / supported

Hi guys,

I have a HP EX490 and it has a SMSC SCH5147-NW for monitoring (found
via visual inspection of the board).  The vendor URL for this chip is
http://www.smsc.com/index.php?tid=254&pid=161

This does not appear to be detected or supported via lm-sensors -
though it does identify that there is a Super I/O SMSC device - the
trimmed information from sensors-detect is as follows:

       Probing for Super-I/O at 0x2e/0x2f
       Trying family `SMSC'...                                     Yes
       Found unknown chip with ID 0xc101

Unfortunately, google does not appear to be able to find the data
sheet for this chip and the only other references are for some Lenovo
gear that use them.

Any ideas on how I'd progress with this?  I'm happy to do testing and
a bit of coding.

Cheers,

-I.

--------------------------------------------------------------------------------------

root <at> ythekshri:~# uname -a
Linux ythekshri 2.6.31-16-generic-pae #53-Ubuntu SMP Tue Dec 8
05:20:21 UTC 2009 i686 GNU/Linux
(Continue reading)

Permalink | Reply | 5 comments |
headers
Juerg Haefliger | 4 Jan 2010 00:45
Picon

Re: SMSC SCH5147-NW not detected / supported

> Hi guys,
>
> I have a HP EX490 and it has a SMSC SCH5147-NW for monitoring (found
> via visual inspection of the board).  The vendor URL for this chip is
> http://www.smsc.com/index.php?tid=254&pid=161
>
> This does not appear to be detected or supported via lm-sensors -
> though it does identify that there is a Super I/O SMSC device - the
> trimmed information from sensors-detect is as follows:
>
>       Probing for Super-I/O at 0x2e/0x2f
>       Trying family `SMSC'...                                     Yes
>       Found unknown chip with ID 0xc101
>
> Unfortunately, google does not appear to be able to find the data
> sheet for this chip and the only other references are for some Lenovo
> gear that use them.
>
> Any ideas on how I'd progress with this?  I'm happy to do testing and
> a bit of coding.

I'll ask my contact at SMSC if he can provide a datasheet.

...juerg

> Cheers,
>
> -I.
>
> --------------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 4 comments |
headers
Juerg Haefliger | 4 Jan 2010 17:51
Picon

Re: SMSC SCH5147-NW not detected / supported

Hi Marcus,

>> Hi guys,
>>
>> I have a HP EX490 and it has a SMSC SCH5147-NW for monitoring (found
>> via visual inspection of the board).  The vendor URL for this chip is
>> http://www.smsc.com/index.php?tid=254&pid=161
>>
>> This does not appear to be detected or supported via lm-sensors -
>> though it does identify that there is a Super I/O SMSC device - the
>> trimmed information from sensors-detect is as follows:
>>
>>       Probing for Super-I/O at 0x2e/0x2f
>>       Trying family `SMSC'...                                     Yes
>>       Found unknown chip with ID 0xc101
>>
>> Unfortunately, google does not appear to be able to find the data
>> sheet for this chip and the only other references are for some Lenovo
>> gear that use them.
>>
>> Any ideas on how I'd progress with this?  I'm happy to do testing and
>> a bit of coding.
>
> I'll ask my contact at SMSC if he can provide a datasheet.

The chip seems to be close to a SCH311x. Try loading the dme1737
module with 'force_id=0x7c' module load parameter and report your
results.

...juerg
(Continue reading)

Permalink | Reply | 3 comments |
headers
vajorie | 5 Jan 2010 01:51
Picon

sensors show hdd temp instead of cpu temp using coretemp in acer d250

Hi,

I guess this could be a follow up from my previous email trying to get
lm-sensors working in this laptop. Since kernel 2.6.32, coretemp seems
to support atom cpus, as I found out, but the temperature reported as
cpu temperature (I guess?) is hdd temperature, not cpu temperature.

The bug report in kernel.org indicated that I should report it here.
Here is that bug report:
http://bugzilla.kernel.org/show_bug.cgi?id=11161

Here's some info that I hope is useful:

Motherboard: I don't know (an Acer netbook using Atom N280 cpu)

lm-sensors v. 3.1.1

kernel 2.6.32 (arch linux)

sensors output:

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +45.0°C  (crit = +90.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +45.0°C  (crit = +90.0°C)

acpitz-virtual-0
(Continue reading)

Permalink | Reply | 6 comments |
headers
Marcus Vogt | 4 Jan 2010 23:25
Picon

Re: SMSC SCH5147-NW not detected / supported

Hi Juerg,

Unfortunately that didn't work:

root <at> ythekshri:~# modprobe  dme1737 force_id=0x7c
FATAL: Error inserting dme1737
(/lib/modules/2.6.31-16-generic-pae/kernel/drivers/hwmon/dme1737.ko):
Device or resource busy
root <at> ythekshri:~#

dmesg reports:

[ 1793.870444] ACPI: I/O resource dme1737 [0xa70-0xa71] conflicts with
ACPI region RNTR [0xa00-0xa7f]
[ 1793.870448] ACPI: If an ACPI driver is available for this device,
you should use it instead of the native driver

root <at> ythekshri:~# cat /proc/ioports | grep a7
0a00-0a7f : pnp 00:09
root <at> ythekshri:~#

Cheers,

Marcus.

On Tue, Jan 5, 2010 at 3:51 AM, Juerg Haefliger <juergh <at> gmail.com> wrote:
> Hi Marcus,
>
>
>>> Hi guys,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jean Delvare | 6 Jan 2010 11:12
Gravatar

Re: Troubleshooting SCH5127 / DME1737

Hi Juerg,

On Mon, 21 Dec 2009 10:18:26 -0800, Juerg Haefliger wrote:
> > Juerg, at this point I really need your help. I would like us to add
> > proper support for the SCH5127 to your dme1737 driver so that users
> > don't have to learn about the force_id trick. But I can't do that
> > safely without a datasheet. As only you have access to them, I need you
> > to tell us in which ways, if any, the SCH5127 differs from the SCH311x.
> 
> It's on my todo list for the christmas break :-) I started pulling up
> the datasheet and looking at the diffs. Give me a few days to come up
> with a patch.

Great. Anything new by now?

--

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Permalink | Reply | 3 comments |
headers
Jean Delvare | 6 Jan 2010 18:09
Gravatar

Re: Troubleshooting SCH5127 / DME1737

On Wed, 6 Jan 2010 08:50:30 -0800, Juerg Haefliger wrote:
> > Hi Juerg,
> >
> > On Mon, 21 Dec 2009 10:18:26 -0800, Juerg Haefliger wrote:
> >> > Juerg, at this point I really need your help. I would like us to add
> >> > proper support for the SCH5127 to your dme1737 driver so that users
> >> > don't have to learn about the force_id trick. But I can't do that
> >> > safely without a datasheet. As only you have access to them, I need you
> >> > to tell us in which ways, if any, the SCH5127 differs from the SCH311x.
> >>
> >> It's on my todo list for the christmas break :-) I started pulling up
> >> the datasheet and looking at the diffs. Give me a few days to come up
> >> with a patch.
> >
> > Great. Anything new by now?
> 
> Yes and no. I have a patch but it doesn't work on 2.6.33-rc2. In fact,
> even the vanilla dme1737 driver doesn't seem to work on 2.6.33-rc2 and
> sensors-detect is unable to find the I2C part of the chip. Haven't
> looked too closely yet but I must be missing something obvious. 2.6.28
> works just fine.

Could be that your machine is affected by the ACPI vs. native driver
resource conflict check that was added in kernel 2.6.32?

Try booting with acpi_enforce_resources=lax and see if it helps.

--

-- 
Jean Delvare
(Continue reading)

Permalink | Reply | 1 comment |
headers
Juerg Haefliger | 6 Jan 2010 17:50
Picon

Re: Troubleshooting SCH5127 / DME1737

> Hi Juerg,
>
> On Mon, 21 Dec 2009 10:18:26 -0800, Juerg Haefliger wrote:
>> > Juerg, at this point I really need your help. I would like us to add
>> > proper support for the SCH5127 to your dme1737 driver so that users
>> > don't have to learn about the force_id trick. But I can't do that
>> > safely without a datasheet. As only you have access to them, I need you
>> > to tell us in which ways, if any, the SCH5127 differs from the SCH311x.
>>
>> It's on my todo list for the christmas break :-) I started pulling up
>> the datasheet and looking at the diffs. Give me a few days to come up
>> with a patch.
>
> Great. Anything new by now?

Yes and no. I have a patch but it doesn't work on 2.6.33-rc2. In fact,
even the vanilla dme1737 driver doesn't seem to work on 2.6.33-rc2 and
sensors-detect is unable to find the I2C part of the chip. Haven't
looked too closely yet but I must be missing something obvious. 2.6.28
works just fine.

...juerg

> --
> Jean Delvare
>

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
(Continue reading)

Permalink | Reply | 2 comments |
headers
Huaxu Wan | 7 Jan 2010 02:59
Picon

Re: sensors show hdd temp instead of cpu temp using coretemp in acer d250

On 19:51 Mon 04 Jan, vajorie wrote:
> Hi,
> 
> I guess this could be a follow up from my previous email trying to get
> lm-sensors working in this laptop. Since kernel 2.6.32, coretemp seems
> to support atom cpus, as I found out, but the temperature reported as
> cpu temperature (I guess?) is hdd temperature, not cpu temperature.
> 
> The bug report in kernel.org indicated that I should report it here.
> Here is that bug report:
> http://bugzilla.kernel.org/show_bug.cgi?id=11161
> 
> Here's some info that I hope is useful:
> 
> Motherboard: I don't know (an Acer netbook using Atom N280 cpu)
> 
> lm-sensors v. 3.1.1
> 
> kernel 2.6.32 (arch linux)
> 
> sensors output:
> 
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +45.0°C  (crit = +90.0°C)
> 
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +45.0°C  (crit = +90.0°C)
>
(Continue reading)

Permalink | Reply | 5 comments |

Gmane