From: Rudolf Marek <r.marek@assembler.cz>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] hwmon/w83627ehf
Date: Mon, 14 May 2007 05:13:02 +0000 [thread overview]
Message-ID: <4647EFDE.5090405@assembler.cz> (raw)
In-Reply-To: <4dfa50520705132035l219dfd4bibaaab442fa3992f4@mail.gmail.com>
Hi
Please provide the output of
isadump -y 0x0A05 0xA06
isadump -y -k 0x87,0x87 0x2e 0x2f 0xb 0x7
And cat /proc/ioports
Thanks!
Rudolf
David Hubbard wrote:
> Hi Lambert,
>
> On 5/13/07, Lambert Carsten <reply01@lhcarsten.org> wrote:
>> Hello David,
>>
>> Just starting out with lm sensors I found a sensor chip that is recognized by
>> the 'sensors-detect' script as :
>>
>> Found `Winbond W83627DHG Super IO Sensors' Success!
>> (address 0xa00, driver `w83627ehf')
>>
>> Driver `w83627ehf' (should be inserted):
>> Detects correctly:
>> * ISA bus address 0x0a00 (Busdriver `i2c-isa')
>> Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)
>>
>> I saw you had added support for this chip in the 2.6.21 kernel. However when
>> loading the module I get:
>>
>> w83627ehf: unsupported chip ID: 0xffff
>>
>> I am not contacting you for support, but I figured I might be of help,
>> testing, gathering information, whatever is usefull.
>> I do know my way around the command line but I am not a programmer so you
>> might have to tell me how to gather any information you need.
>>
>> Don't waste your time replying unless I can be of help to you. :)
>>
>> Kind regards,
>>
>> Lambert Carsten
>
> You've got the right person here. I'm CCing the lm-sensors list so
> that this information will be publicly available. So it would be easy
> to just add 0xffff as a chip ID and forget about it -- but somehow,
> that doesn't seem like a valid chip ID to me. So I'm going to treat it
> as some kind of bug and try to get your motherboard to report a
> different chip ID. That's just my initial guess...
>
> Would you mind providing the following information?
>
> Kernel version
>
> Motherboard manufacturer and model number
>
> sensors version
>
> Full output of sensors-detect.pl
>
> Any additional clues -- what caused the failure? Did you upgrade to
> linux 2.6.21, or is this new hardware ... ?
>
> Thanks for the report!
> David
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-05-14 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 3:35 [lm-sensors] hwmon/w83627ehf David Hubbard
2007-05-14 5:13 ` Rudolf Marek [this message]
2007-05-14 19:54 ` Rudolf Marek
2007-05-15 8:19 ` Lambert Carsten
2007-05-15 18:16 ` Jean Delvare
2007-05-15 18:53 ` David Hubbard
2007-05-15 23:51 ` Rudolf Marek
2007-05-16 22:59 ` David Hubbard
2007-06-08 14:46 ` Jean Delvare
2007-06-08 19:13 ` David Hubbard
2007-06-16 12:43 ` Jean Delvare
2007-06-21 19:24 ` David Hubbard
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=4647EFDE.5090405@assembler.cz \
--to=r.marek@assembler.cz \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.