[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says use

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says use

[Curt Blank]

Ok, I answered my own question, yes I can backport the w83627ehf driver 
from 2.6.21 to 2.6.16.

If anyone is interested I put the patches here:

http://www.curtronics.com/patches/

Not bad for one nights work.

Below is the living proof. The chip ID reported by the W83627DHG on this 
MB was different then what the 2.6.21 w83627ehf code looked for so now 
it looks for both. There are 4 fans connected to this MB but only 3 are 
showing up, the 4th is a MSI installed fan on the Northbridge chip. 
Maybe I can't see that one, I don't know at this point. I have to 
validate the voltages also, they don't look quite right.

-Curt

w83627dhg-isa-0a10
Adapter: ISA adapter
in0:       +1.24 V  (min =  +0.00 V, max =  +1.74 V) 
in1:       +1.86 V  (min =  +1.06 V, max =  +0.79 V) 
in2:       +3.26 V  (min =  +2.34 V, max =  +3.36 V) 
in3:       +3.26 V  (min =  +0.90 V, max =  +2.77 V) 
in4:       +1.54 V  (min =  +1.23 V, max =  +0.02 V) 
in5:       +1.46 V  (min =  +0.24 V, max =  +0.78 V) 
in6:       +1.60 V  (min =  +0.17 V, max =  +0.53 V) 
in7:       +3.26 V  (min =  +2.18 V, max =  +2.26 V) 
in8:       +2.99 V  (min =  +2.08 V, max =  +0.86 V) 
fan1:     4326 RPM  (min =    0 RPM, div = 8)
fan2:     2812 RPM  (min = 9926 RPM, div = 8)
fan3:     6750 RPM  (min = 8881 RPM, div = 8)
fan4:        0 RPM  (min =  703 RPM, div = 128)
fan5:        0 RPM  (min = 10546 RPM, div = 128)
temp1:       +41?C  (high =   +53?C, hyst =   +16?C)  
temp2:     +28.5?C  (high = +80.0?C, hyst = +75.0?C)  
temp3:      +1.0?C  (high = +80.0?C, hyst = +75.0?C)  

Curt Blank wrote:

> Well that explains it. In kernel 2.6.21 and I have 2.6.16.
>
> If I'm reading things right that's not even a stable kernel yet. Any 
> chance of me being able to backport it to the 2.6.16 w83627ehf driver 
> for my use?
>
> Looks like I'm slightly on the bleeding edge.
>
> -Curt
>
> Curt Blank wrote:
>
>> In the meantime....
>>
>> Winbond W83627DHG
>>
>> http://www.curtronics.com/Pics/MSI_K9N4_SLI-F_Winbond.jpg
>>
>> How's that for Hi-Res. Couldn't use a flash and lighting was a bitch 
>> (running server).
>>
>> -Curt
>>
>> Jan van Tiggelen wrote:
>>
>>  
>>
>>> OK, the question is out to MSI. I expect it to take up to about a 
>>> day or 2
>>> before we have the full answer.
>>>
>>> Will post back to you in a personal message when I get the schematics.
>>>
>>> Kind regards,
>>>
>>> Jan van Tiggelen
>>>
>>>
>>> -----Original Message-----
>>> From: Curt Blank [mailto:curt at curtronics.com] Sent: Tuesday, March 
>>> 20, 2007 7:44 PM
>>> To: David Hubbard
>>> Cc: Jan van Tiggelen; lm-sensors at lm-sensors.org
>>> Subject: Re: [lm-sensors] MSI K9N4 SLI-F sensors-detect says use
>>> w83627ehfbut it won't load
>>>
>>> Jan/David
>>>
>>> Thanks! Man you guys are great.
>>>
>>> I built this server so I am familiar with the MB but it sounds like 
>>> Jan has the answer.
>>>
>>> I did try installing all the Winbond drivers one at a time but no luck.
>>>
>>> -Curt
>>>
>>> On Tue, 20 Mar 2007, David Hubbard wrote:
>>>
>>>
>>>
>>>   
>>>
>>>> Hi Jan,
>>>>
>>>> On 3/20/07, Jan van Tiggelen <den_tichel at zonnet.nl> wrote:
>>>>  
>>>>     
>>>>
>>>>> Curt / David,
>>>>>
>>>>> Would it be of any help if you get a full spec of the motherboard,
>>>>>    
>>>>>       
>>>>
>>> including
>>>
>>>
>>>   
>>>
>>>>> the schematics? I have access to that.
>>>>>
>>>>> That way you don't need to take the server apart, and you can be sure
>>>>>    
>>>>>       
>>>>
>>> that
>>>
>>>
>>>   
>>>
>>>>> the chip is used exactly for what purpose you would expect.
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Jan van Tiggelen
>>>>>    
>>>>>       
>>>>
>>>> Yes, that would be the best way.
>>>>
>>>> David
>>>>
>>>>
>>>>  
>>>>     
>>>
>>
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors at lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>  
>>

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says

[David Hubbard]

Hi Curt,

On 3/20/07, Curt Blank <Curt.Blank at curtronics.com> wrote:
> Ok, I answered my own question, yes I can backport the w83627ehf driver
> from 2.6.21 to 2.6.16.
>
> If anyone is interested I put the patches here:
>
> http://www.curtronics.com/patches/
>
> Not bad for one nights work.
>
> Below is the living proof. The chip ID reported by the W83627DHG on this
> MB was different then what the 2.6.21 w83627ehf code looked for so now
> it looks for both. There are 4 fans connected to this MB but only 3 are
> showing up, the 4th is a MSI installed fan on the Northbridge chip.
> Maybe I can't see that one, I don't know at this point. I have to
> validate the voltages also, they don't look quite right.
>
> -Curt

Good work. I am not surprised that the driver works in 2.6.16, since
it works in 2.6.17. If your voltages are slightly off, you'll just
need to edit /etc/sensors.conf and change the voltage formulas. (The
voltages are determined by resistors on the motherboard, so it's a
manufacturer and motherboard-specific decision how the voltages are
actually measured.)

David

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says

[Jean Delvare]

Hi Curt,

On Wed, 21 Mar 2007 01:27:48 -0500, Curt Blank wrote:
> Ok, I answered my own question, yes I can backport the w83627ehf driver 
> from 2.6.21 to 2.6.16.
> 
> If anyone is interested I put the patches here:
> 
> http://www.curtronics.com/patches/
> 
> Not bad for one nights work.
> 
> Below is the living proof. The chip ID reported by the W83627DHG on this 
> MB was different then what the 2.6.21 w83627ehf code looked for so now 
> it looks for both. There are 4 fans connected to this MB but only 3 are 
> showing up, the 4th is a MSI installed fan on the Northbridge chip. 
> Maybe I can't see that one, I don't know at this point. I have to 
> validate the voltages also, they don't look quite right.

Two comments about this patch:

1* You didn't have to convert the semaphores to mutexes. This is a
kernel-wide change that happened at one point in time, and is not
related with the W83627DHG support at all. Without that change, your
patch will be smaller.

2* You do not need to change the device ID. If you look at the code,
you'll see that we do explicitely mask out the lower bits, because they
are _known_ to change depending on the exact chip revision. So the
original code should work just fine for you too.

-- 
Jean Delvare

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says

[Curt Blank]

Thanks. It was more work then I expected. If I knew how much work it was 
before I started I probably would not have done it.

As for the kernel, due to using applications supplied on the distro I tend 
to like to stay with the kernel version supplied. I don't have the time to 
modify the applications if need be.

As for the voltages, yes I'm aware of the conf file, but my question has 
always been, how do I know which is what? I'd be guessing at best. When 
Jan gets the schematic he can tell me which input is what voltage but 
right now I don't have a clue.

-Curt

On Wed, 21 Mar 2007, David Hubbard wrote:

> Hi Curt,
> 
> On 3/20/07, Curt Blank <Curt.Blank at curtronics.com> wrote:
> > Ok, I answered my own question, yes I can backport the w83627ehf driver
> > from 2.6.21 to 2.6.16.
> >
> > If anyone is interested I put the patches here:
> >
> > http://www.curtronics.com/patches/
> >
> > Not bad for one nights work.
> >
> > Below is the living proof. The chip ID reported by the W83627DHG on this
> > MB was different then what the 2.6.21 w83627ehf code looked for so now
> > it looks for both. There are 4 fans connected to this MB but only 3 are
> > showing up, the 4th is a MSI installed fan on the Northbridge chip.
> > Maybe I can't see that one, I don't know at this point. I have to
> > validate the voltages also, they don't look quite right.
> >
> > -Curt
> 
> Good work. I am not surprised that the driver works in 2.6.16, since
> it works in 2.6.17. If your voltages are slightly off, you'll just
> need to edit /etc/sensors.conf and change the voltage formulas. (The
> voltages are determined by resistors on the motherboard, so it's a
> manufacturer and motherboard-specific decision how the voltages are
> actually measured.)
> 
> David
> 

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says

[Curt Blank]

Hi Jan,

Thanks for the information. I wasn't sure about the semaphores and I 
noticed they were no longer used in the 2.6.21 code at all so I thought 
just to be safe I'd switch them to mutexes. I wanted to match the code as 
close as possible to minimize any problems with doing the port and I'm not 
concerned about size.

As for the Device ID, I saw the masking, but I could not get it to work 
with just the 0xa020. I kept getting this:

Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xffff
Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xa023

Then when I added the 0xa023 definition and changed the mask to 0xFFF3 it 
worked.

Ah-ha-ha. I think I see the error in my ways. All I needed to do was 
change the mask to 0xFFE0. I'll give that a try. Always like to do things 
the same. It was late, I was getting tired and starting to wonder if I'd 
ever get it to work. Being refreshed and with your help it was now easy to 
spot this.

And, when you get the schematic for this MB, I would greatly appreciate it 
if you could tell me what input is what voltage. I will do it myself if 
it's possible for me to get a copy of the schematic. I'd also lik to see 
if the Northbridge fan is connected to the w83627dhg. Then I'd know for 
sure if I should be seeing its RPM.

-Curt

On Wed, 21 Mar 2007, Jean Delvare wrote:

> Hi Curt,
> 
> On Wed, 21 Mar 2007 01:27:48 -0500, Curt Blank wrote:
> > Ok, I answered my own question, yes I can backport the w83627ehf driver 
> > from 2.6.21 to 2.6.16.
> > 
> > If anyone is interested I put the patches here:
> > 
> > http://www.curtronics.com/patches/
> > 
> > Not bad for one nights work.
> > 
> > Below is the living proof. The chip ID reported by the W83627DHG on this 
> > MB was different then what the 2.6.21 w83627ehf code looked for so now 
> > it looks for both. There are 4 fans connected to this MB but only 3 are 
> > showing up, the 4th is a MSI installed fan on the Northbridge chip. 
> > Maybe I can't see that one, I don't know at this point. I have to 
> > validate the voltages also, they don't look quite right.
> 
> Two comments about this patch:
> 
> 1* You didn't have to convert the semaphores to mutexes. This is a
> kernel-wide change that happened at one point in time, and is not
> related with the W83627DHG support at all. Without that change, your
> patch will be smaller.
> 
> 2* You do not need to change the device ID. If you look at the code,
> you'll see that we do explicitely mask out the lower bits, because they
> are _known_ to change depending on the exact chip revision. So the
> original code should work just fine for you too.
> 
> -- 
> Jean Delvare
> 

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says

[David Hubbard]

Hi Curt,

On 3/21/07, Curt Blank <curt at curtronics.com> wrote:
> Hi Jan,
>
> Thanks for the information. I wasn't sure about the semaphores and I
> noticed they were no longer used in the 2.6.21 code at all so I thought
> just to be safe I'd switch them to mutexes. I wanted to match the code as
> close as possible to minimize any problems with doing the port and I'm not
> concerned about size.
>
> As for the Device ID, I saw the masking, but I could not get it to work
> with just the 0xa020. I kept getting this:
>
> Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xffff
> Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xa023
>
> Then when I added the 0xa023 definition and changed the mask to 0xFFF3 it
> worked.
>
> Ah-ha-ha. I think I see the error in my ways. All I needed to do was
> change the mask to 0xFFE0. I'll give that a try. Always like to do things
> the same. It was late, I was getting tired and starting to wonder if I'd
> ever get it to work. Being refreshed and with your help it was now easy to
> spot this.
>
> And, when you get the schematic for this MB, I would greatly appreciate it
> if you could tell me what input is what voltage. I will do it myself if
> it's possible for me to get a copy of the schematic. I'd also lik to see
> if the Northbridge fan is connected to the w83627dhg. Then I'd know for
> sure if I should be seeing its RPM.
>
> -Curt

You'll want to put your replies at the bottom of the email. If you
were getting unknown device ID, we should probably add another device
ID to the driver (0xa020 ?). I'll take a look at it when I get home
tonight.

David

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says

[Curt Blank]

On Wed, 21 Mar 2007, David Hubbard wrote:

> Hi Curt,
> 
> On 3/21/07, Curt Blank <curt at curtronics.com> wrote:
> > Hi Jan,
> >
> > Thanks for the information. I wasn't sure about the semaphores and I
> > noticed they were no longer used in the 2.6.21 code at all so I thought
> > just to be safe I'd switch them to mutexes. I wanted to match the code as
> > close as possible to minimize any problems with doing the port and I'm not
> > concerned about size.
> >
> > As for the Device ID, I saw the masking, but I could not get it to work
> > with just the 0xa020. I kept getting this:
> >
> > Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xffff
> > Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xa023
> >
> > Then when I added the 0xa023 definition and changed the mask to 0xFFF3 it
> > worked.
> >
> > Ah-ha-ha. I think I see the error in my ways. All I needed to do was
> > change the mask to 0xFFE0. I'll give that a try. Always like to do things
> > the same. It was late, I was getting tired and starting to wonder if I'd
> > ever get it to work. Being refreshed and with your help it was now easy to
> > spot this.
> >
> > And, when you get the schematic for this MB, I would greatly appreciate it
> > if you could tell me what input is what voltage. I will do it myself if
> > it's possible for me to get a copy of the schematic. I'd also lik to see
> > if the Northbridge fan is connected to the w83627dhg. Then I'd know for
> > sure if I should be seeing its RPM.
> >
> > -Curt
> 
> You'll want to put your replies at the bottom of the email. If you
> were getting unknown device ID, we should probably add another device
> ID to the driver (0xa020 ?). I'll take a look at it when I get home
> tonight.
> 
> David
> 
> 

Hi David, 

Ok, will do. pine puts me at the top so I just type.

No I think the Device ID issue is due to the mask needing to be 0xFFE0 as 
Jan pointed out. I'm going to change that and try it.

-Curt

[lm-sensors] SUCCESS! Re: MSI K9N4 SLI-F sensors-detect says

[Curt Blank]

On Wed, 21 Mar 2007, Curt Blank wrote:

> 
> 
> On Wed, 21 Mar 2007, David Hubbard wrote:
> 
> > Hi Curt,
> > 
> > On 3/21/07, Curt Blank <curt at curtronics.com> wrote:
> > > Hi Jan,
> > >
> > > Thanks for the information. I wasn't sure about the semaphores and I
> > > noticed they were no longer used in the 2.6.21 code at all so I thought
> > > just to be safe I'd switch them to mutexes. I wanted to match the code as
> > > close as possible to minimize any problems with doing the port and I'm not
> > > concerned about size.
> > >
> > > As for the Device ID, I saw the masking, but I could not get it to work
> > > with just the 0xa020. I kept getting this:
> > >
> > > Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xffff
> > > Mar 21 00:39:14 bnfsrvr kernel: w83627ehf: unsupported chip ID: 0xa023
> > >
> > > Then when I added the 0xa023 definition and changed the mask to 0xFFF3 it
> > > worked.
> > >
> > > Ah-ha-ha. I think I see the error in my ways. All I needed to do was
> > > change the mask to 0xFFE0. I'll give that a try. Always like to do things
> > > the same. It was late, I was getting tired and starting to wonder if I'd
> > > ever get it to work. Being refreshed and with your help it was now easy to
> > > spot this.
> > >
> > > And, when you get the schematic for this MB, I would greatly appreciate it
> > > if you could tell me what input is what voltage. I will do it myself if
> > > it's possible for me to get a copy of the schematic. I'd also lik to see
> > > if the Northbridge fan is connected to the w83627dhg. Then I'd know for
> > > sure if I should be seeing its RPM.
> > >
> > > -Curt
> > 
> > You'll want to put your replies at the bottom of the email. If you
> > were getting unknown device ID, we should probably add another device
> > ID to the driver (0xa020 ?). I'll take a look at it when I get home
> > tonight.
> > 
> > David
> > 
> > 
> 
> Hi David, 
> 
> Ok, will do. pine puts me at the top so I just type.
> 
> No I think the Device ID issue is due to the mask needing to be 0xFFE0 as 
> Jan pointed out. I'm going to change that and try it.
> 
> -Curt
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> 

Hi again David,

Test complete. By changing the mask to 0xFFE0 the W83627DHG is recognized 
by the w83627ehf driver using 0xa020 and works. You don't need to add 
another ID to look for.

-Curt