Ticket #2265 (new enhancement)

Opened 8 years ago

Last modified 6 years ago

Super I/O SMSC SCH5017 on Tyan Toledo i3100 (S5207)

Reported by: ticket Owned by: juergh
Priority: major Milestone:
Component: hardware Version: 2.10.1
Keywords: tyan superi/o SMSC SCH5017 Cc: ll20060607@…

Description (last modified by khali) (diff)

Hi Developers,

I am trying to get sensor information on this Tyan board, on which Tyan only supports M$ Windoze OS, therefore they are not providing a config file for lm-sensors and linux.

The sensors-detect detects the Super I/O chip but it is not recognized. This is the output from from sensors-detect:

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x7803
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0x7803
Trying family `VIA/Winbond/Fintek'...                       No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
root@tyan:~# sensors -v
sensors version 2.10.1 with libsensors version 2.10.1

root@tyan:~# uname -a
Linux tyan 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux

Change History

Changed 8 years ago by juergh

  • owner changed from somebody to juergh

Looks like you have something compatible to the dme1737. Get the latest version of the lm-sensors package (2.10.4) and the latest released kernel (2.6.23.xx) and use the dme1737 module.

Can you rerun sensors-detect 2.10.4? Are you sure this is a sch5017?

Changed 7 years ago by khali

  • description modified (diff)

Changed 6 years ago by khali

Hmm, same device ID as the DME1737, right? We had a report that the dme1737 driver recognizes it as such:

This ticket is getting old, I'd like to close it soon. Juerg, can you please clarify the status of SCH5017 support? Is it OK to just claim we support it, or are there actual differences between the SCH5017 and DME1737?

Note: See TracTickets for help on using tickets.