Hidden and disabled SMBus SiS0016, please enable

Hidden and disabled SMBus SiS0016, please enable

[Xuan Baldauf]

Hello Alex and Mark,

I'm referring to your discussions at 
http://archives.andrew.net.au/lm-sensors/msg01299.html

I have got a new notebook "Mitac 8640m". (The same as in 
http://archives.andrew.net.au/lm-sensors/msg03881.html ) It is based on 
a SiS645DX ("SiS646") northbridge and a SiS962 southbridge. There is a 
SMBus device 1039:0016 from SiS, but the BIOS (which does not seem very 
usable) seems to hide that device. (See 
http://archives.andrew.net.au/lm-sensors/msg01872.html ).

    * When using Linux 2.6, the device is unhidden at boot (
      http://archives.andrew.net.au/lm-sensors/msg02573.html ).
    * Under Linux 2.4, i2c-sis645 seems to unhide it (but not for the
      kernel, "lspci" won't show it, but "lspci -H1" will show it).
    * Under Windows, MBM seems to unhide it.

Unfortunately, the I/O-ports will not be enabled,

    * neither under Windows using MBM 5.3.5.0
    * nor under Linux 2.6 using i2c-sis96x (Linux 2.6.0)
    * nor under Linux 2.4 using i2c-sis645 (lm-sensors 2.8.2).

I can verify this by looking at the PCI config space word at byte offset 
0x04 ("PCI_COMMAND", see 
http://lxr.linux.no/source/include/linux/pci.h?v=2.6.0#L28 ).  For I/O 
ports being enabled bit 0 (PCI_COMMAND_IO) has to be set. This is not 
the case:

<MBM PCI Dump>
Bus :00 Device :02 Func :01 Vendor :1039 Device ID :0016

  $0000:  39 10 16 00 00 00 80 02 00 00 05 0C 00 00 00 00
</MBM PCI Dump>

Under Linux 2.4 and Linux 2.6, I can try to manually set 
PCI_COMMAND=0x01. This works, so that then modules "i2c-sis96x" and 
"i2c-sis645" respectively can be loaded.

    * But under Linux 2.6, "i2cdetect 0" returns only "XX" results and
      is pretty slow. I enabled the "#define DEBUG" in the sourcecode if
      "i2c-sis96x" and saw that every request to the SMBus times out.
    * Under Linux 2.4, "i2cdetect 0" or "sensors" crashes with a
      (recoverable) kernel oops

Under Windows, the pci device actually cannot be enabled manually (after 
running MBM 5, device manager will recognize an "SM-Bus-Controller", but 
I cannot find a driver for that device). When running "SMB Dump" in MBM, 
I get this:


------MBM SMB DUMP-------

SMB SiS0016 via SiS0008 @ $0000

SMBus Register :$10
  $0000:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  $0010:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  $0020:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[...only zeros...]


So it seems that I'm missing something when manually enabling the 
device. MBM 5.3.5.0 also seems to misidentify the device (SiS5595 
instead of SiS962) and base I/O port address (the I/O-port-space of the 
SMBus device is at 0x1080).

So I'm asking you (Alex and Mark) wether it is possible to enable the 
device not just by unhiding it, but also by enabling I/O-ports and other 
stuff I'm not familiar with so that the SMBus device will get usable.

I'd like to get rid of the CPU fan noise by manually controlling the CPU 
fan based on CPU temperature (or by even unplugging the CPU fan and 
verifying success by reading the CPU temperature).

I'm willing to run tests, alpha versions and the like.

Thank you,
Xu?n.



----MBM SYSTEM INFO-----
 
MBM 5.3.5.0
MBM 5 Core EXE                : 5.3.5.0
MBM 5 Core DLL                : 5.3.5.1
MBM 5 Settings DLL            : 5.3.5.0
MBM 5 Dashboard DLL           : 5.3.5.0
MBM 5 Hibernation DLL         : 5.0.0.0
MBM 5 Ras DLL                 : 5.0.0.0
MBM 5 Logger DLL              : 5.3.4.0
MBM 5 Mail, FTP and UDP DLL   : 5.3.4.0
MBM 5 OSD DLL                 : 5.0.0.3
MBM 5 ASPI DLL                : 5.2.1.0
MBM 5 Heat Up EXE             : 5.0.0.0
MBM 5 Wizard                  : 5.3.5.0
MBMIO DLL                     : 1.0.0.2
MBMIO Driver                  : 1.1
 
DLL Folder Location           : C:\Programme\Motherboard Monitor 5\DLL\
Data Folder Location          : C:\Programme\Motherboard Monitor 5\Data\
Language Folder Location      : C:\Programme\Motherboard Monitor 5\Language\
Log Folder Location (Alarm)   : c:\programme\motherboard monitor 5\log\
Log Folder Location (High Low): c:\programme\motherboard monitor 5\log\
Log Folder Location (Interval): c:\programme\motherboard monitor 5\log\
 
Selected Language             : English
 
Info ChipInfo.ini             : 16576 bytes  24.10.2003 13:37:26
Info shdn.ini                 : 388 bytes    12.10.2000 18:47:06
Info Voltage.ini              : 31808 bytes  24.10.2003 13:09:22
Info Language file            : 22920 bytes  17.10.2003 08:33:40
 
Up Time MBM session           : 00:00:11:23
Up Time MBM total             : 00:00:32:02
 
------Sensor Chip-------
 
Main Sensor Chip              : Sis SiS5595
SMB Address                   : $0000
Used Bus                      : ISA
ISA Address                   : $8008
 
-Sensor Chip Selections-
 
Possible Temp Sensors[2]      : SiS5595
 
Selected Temp Sensors[1]      : SiS5595  (115)
Selected Temp Sensors[2]      : Custom  (185)
Selected Temp Sensors[3]      : Custom  (185)
 
Possible Voltage Sensors[2]   : MBM Fixed
 
Selected Voltage Sensors[1]   : MBM Fixed  (2)
Selected Voltage Sensors[2]   : MBM Fixed  (2)
Selected Voltage Sensors[3]   : MBM Fixed  (2)
Selected Voltage Sensors[4]   : MBM Fixed  (2)
Selected Voltage Sensors[5]   : MBM Fixed  (2)
Selected Voltage Sensors[6]   : MBM Fixed  (2)
Selected Voltage Sensors[7]   : MBM Fixed  (2)
 
Possible Fan Sensors[1]       : SiS5595-1
Possible Fan Sensors[2]       : SiS5595-2
 
Selected Fan Sensors[1]       : SiS5595-1  T1  D4  (32)
Selected Fan Sensors[2]       : SiS5595-2  T1  D4  (33)
Selected Fan Sensors[3]       : Asus-3  T1  D4  (31)
 
Possible Voltage Sub Types[0] : Sis 5595 Standard
Selected Voltage Sub Type     : Sis 5595 Standard  (0)
 
--Sensor Chip Readings--
 
Temperature Readout[1]        : 51
Temperature Readout[2]        : 51
Voltage Readout[1]            : 4,08
Voltage Readout[3]            : 4,08
Voltage Readout[4]            : 6,8544
Voltage Readout[5]            : 15,504
 
---------System---------
 
Operating System              : Microsoft Windows XP (NT 5.1) (Build 
2600) Service Pack 1
User                          : Administrator
Memory in use                 : 89%
Total Physical Memory         : 261616 KB
Available Physical Memory     : 28716 KB
 
----------CPU-----------
 
CPU Speed                     : 1792 MHz
Nr of CPU's                   : 1
 
-------3rd Party--------
 
ShutDownNow                   :
 
----Advanced Settings---
 
Fan Temp                      : 0
Custom Temp Table             : 0
Startup Delay                 : 0
2E 4E Enabled                 : 0
2E Forced                     : 0
4E Forced                     : 0
Do Not Reset                  : 1
SMB Scan Range                : $10 - $7F

Hidden and disabled SMBus SiS0016, please enable

[Mark M. Hoffman]

* Xuan Baldauf <xuan--sensors--2003.12.20@baldauf.org> [2003-12-21 00:29:00 +0100]:
> Hello Alex and Mark,
> 
> I'm referring to your discussions at 
> http://archives.andrew.net.au/lm-sensors/msg01299.html
> 
> I have got a new notebook "Mitac 8640m". (The same as in 
> http://archives.andrew.net.au/lm-sensors/msg03881.html ) It is based on 

I re-read that thread and laughed: is your machine really labelled
"Packard Bell"?  I can't remember the last time I saw that name on
a computer in the US - at least not since 1995.  They had an *awful*
reputation.

> Unfortunately, the I/O-ports will not be enabled,
> 
>    * neither under Windows using MBM 5.3.5.0
>    * nor under Linux 2.6 using i2c-sis96x (Linux 2.6.0)
>    * nor under Linux 2.4 using i2c-sis645 (lm-sensors 2.8.2).
> 
> I can verify this by looking at the PCI config space word at byte offset 
> 0x04 ("PCI_COMMAND", see 
> http://lxr.linux.no/source/include/linux/pci.h?v=2.6.0#L28 ).  For I/O 
> ports being enabled bit 0 (PCI_COMMAND_IO) has to be set. This is not 
> the case:
> 
> <MBM PCI Dump>
> Bus :00 Device :02 Func :01 Vendor :1039 Device ID :0016
> 
>  $0000:  39 10 16 00 00 00 80 02 00 00 05 0C 00 00 00 00
> </MBM PCI Dump>
> 
> Under Linux 2.4 and Linux 2.6, I can try to manually set 
> PCI_COMMAND=0x01. This works, so that then modules "i2c-sis96x" and 
> "i2c-sis645" respectively can be loaded.

When you say "manually", where and how did you do this?  If you put it
in the driver(s), would you like to send a patch? ;)  I suspect it
wouldn't help in your case though...

>    * But under Linux 2.6, "i2cdetect 0" returns only "XX" results and
>      is pretty slow. I enabled the "#define DEBUG" in the sourcecode if
>      "i2c-sis96x" and saw that every request to the SMBus times out.
>    * Under Linux 2.4, "i2cdetect 0" or "sensors" crashes with a
>      (recoverable) kernel oops

The result under 2.6 says that your SMBus is not connected to anything
at all - sorry.  I don't think it's unusual for a notebook to just
leave it disconnected.

But, what about this kernel oops under 2.4?  Whatever the state of the
hardware, this shouldn't happen.  Could you give more details about that?
I2C and lm_sensors versions, how you built them, anything else special...
And of course a copy of the oops message itself.

> So I'm asking you (Alex and Mark) wether it is possible to enable the 
> device not just by unhiding it, but also by enabling I/O-ports and other 
> stuff I'm not familiar with so that the SMBus device will get usable.

You've really searched through the mailing lists, and I appreciate that.
Unfortunately, it also means I have nothing more to add... as you've
already tried what I would have recommended.  Without sensors on the
SMBus or ISA bus, the only other possibility is ACPI - and for that
you'll need to ask elsewhere.

> I'm willing to run tests, alpha versions and the like.

Sure, I would appreciate if you could help me to debug that 2.4 kernel
oops.

Thanks and regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

Hidden and disabled SMBus SiS0016, please enable

[Mark Studebaker]

Mark M. Hoffman wrote:
> * Xuan Baldauf <xuan--sensors--2003.12.20@baldauf.org> [2003-12-21 00:29:00 +0100]:
> 
>>Hello Alex and Mark,
>>
>>I'm referring to your discussions at 
>>http://archives.andrew.net.au/lm-sensors/msg01299.html
>>
>>I have got a new notebook "Mitac 8640m". (The same as in 
>>http://archives.andrew.net.au/lm-sensors/msg03881.html ) It is based on 
> 
> 
> I re-read that thread and laughed: is your machine really labelled
> "Packard Bell"?  I can't remember the last time I saw that name on
> a computer in the US - at least not since 1995.  They had an *awful*
> reputation.
> 
>

Looks like NEC owns Packard Bell and has been investing in them since 1995.

http://www.businessweek.com/1998/02/b3560256.htm

Hidden and disabled SMBus SiS0016, please enable

[Xuan Baldauf]

Mark M. Hoffman wrote:

>But, what about this kernel oops under 2.4?  Whatever the state of the
>hardware, this shouldn't happen.  Could you give more details about that?
>I2C and lm_sensors versions, how you built them, anything else special...
>And of course a copy of the oops message itself.
>  
>
Sorry, it was my fault. I digged into this and found that lm-sensors 
modules had different assumptions about some "struct"s than i2c-core. 
The reason was that I did not use i2c-2.8.0 but i2c provided from kernel 
2.4. After using the correct i2c version, the oops disappeared.

Xu?n.

Hidden and disabled SMBus SiS0016, please enable

[Xuan Baldauf]

Mark Studebaker wrote:

>
>
> Mark M. Hoffman wrote:
>
>> * Xuan Baldauf <xuan--sensors--2003.12.20@baldauf.org> [2003-12-21 
>> 00:29:00 +0100]:
>>
>>> Hello Alex and Mark,
>>>
>>> I'm referring to your discussions at 
>>> http://archives.andrew.net.au/lm-sensors/msg01299.html
>>>
>>> I have got a new notebook "Mitac 8640m". (The same as in 
>>> http://archives.andrew.net.au/lm-sensors/msg03881.html ) It is based on 
>>
>>
>>
>> I re-read that thread and laughed: is your machine really labelled
>> "Packard Bell"?  I can't remember the last time I saw that name on
>> a computer in the US - at least not since 1995.  They had an *awful*
>> reputation.
>>
>>
>
> Looks like NEC owns Packard Bell and has been investing in them since 
> 1995.
>
> http://www.businessweek.com/1998/02/b3560256.htm
>
Just in case somebody is interested, I want to mention:

I now can read out the temperatures (actually, there are two sensors in 
this notebook), not by SMBus, but by using the ACPI embedded controller. 
However, by reading the ACPI DSDT table, I found out that there is also 
a way to access the ACPI embedded controller address space using the 
SIS0016 controller. I did not investigate further into it, because I did 
not need (because reading by ACPI EC was sufficient).

I then changed the ACPI DSDT table to define three new thermal zones, 
one for the CPU temperature, one for the chipset ("mainboard") 
temperature and one for the maximum CPU temperature since the last real 
poweroff (which is also reported in the ACPI address space). I 
discovered that the CPU temperature oscillated between 44 ?C and 54 ?C, 
which is pretty cool. Additionally, I can (under Linux) read these 
temperatures. Under Windows, I'm missing such a tool (hint to Alexander 
van Kaam ;-)).

Then I hacked the firmware of the ACPI embedded controller (which 
actually is software for the Hitachi H8/300, which is the core of the 
microcontroller which provides the ACPI EC functionality) so that the 
fan speed is only 15% of the former value. The fan at this low speed 
blows the heat nearly as equal as the fan at high speed. Even with full 
CPU usage, the temperature will not rise above 56 ?C. But now, the fan 
is *much more* quiet, there is just some regular ticking. I do not know 
wether these ticks are due to snapping in of the motor or wether they 
are due to microcontroller which may set the fan speed by providing 
duty-cycles, i.e. on-off-alternations where the "on" time is higher when 
the fan should run faster. Nevertheless, it served the purpose of 
calming down the 8640 notebook.

Unfortunately, the notebook has a too high thermal resistance to the 
environment if the fan is completely off. That means, that the 
temperature will be too high (63 ?C) if the fan is shut off for longer 
time. If the temperature is kept too high, the heat will flow to other 
parts of the notebook (i.e. the chipset), which will make a secondary 
fan start. Because this fan is normally off, I consider the safety limit 
for slowing down the CPU fan to be that low speed of the CPU fan. where 
the secondary fan would start due to heat flow.

So, that's the story.

If someone needs somebody for hacking ACPI tables or ACPI embedded 
controller firmware in order to read temperatures and control fans, 
maybe I can help.

Xu?n Baldauf.

[lm-sensors] Hidden and disabled SMBus SiS0016, please enable

[Bailly Jérôme]

Hello ,
I have the same notebooks : Mitac 8640 and i want to monitoring it. I 
can't find the sensors in the dsdt table. If you can send me your DSDT 
table or explain the processus.

Thank

jerome_bailly at club-internet.fr