[LinuxBIOS] Call for help: superiotool

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at gmx.net
Tue Oct 2 17:50:40 CEST 2007


On 02.10.2007 17:44, Robinson Tryon wrote:
> On 10/2/07, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006 at gmx.net> wrote:
>> On 02.10.2007 05:37, Robinson Tryon wrote:
>>> On 9/27/07, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006 at gmx.net> wrote:
>>>> Not supported by superiotool, however if there was any output at all,
>>>> we'd like to know it. That alone would probably help us identify the
>>>> Super I/O, and from there, adding support is rather easy.
>>> System Information
>>>         Manufacturer: TOSHIBA
>>>         Product Name: Satellite 1415
>>>         Version: PS141U-1ZCF4V
>>>
>>> $ sudo ./superiotool -v
>>> superiotool r2815
>>> $ sudo ./superiotool -V
>>> Probing for ALi Super I/O at 0x3f0... failed
>>> Probing for ALi Super I/O at 0x370... failed
>>> Probing for NSC Super I/O at 0x2e... failed
>>> Probing for NSC Super I/O at 0x4e... failed
>>> Probing for Fintek Super I/O at 0x2e... failed
>>> Probing for Fintek Super I/O at 0x4e... failed
>>> Probing 0x2e, failed (0x22), data returns 0x04
>>> Probing 0x2e, failed (0x22), data returns 0x04
>>> Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... failed
>>> Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... failed
>>> Probing 0x2e, failed (0x21), data returns 0x00
>>> Probing 0x2e, failed (0x0e), data returns 0x00
>>> Probing for SMSC Super I/O at 0x4e... failed
>>> Probing for SMSC Super I/O at 0x4e... failed
>>> Probing for SMSC Super I/O at 0x3f0... failed
>>> Probing for SMSC Super I/O at 0x3f0... failed
>>> Probing for SMSC Super I/O at 0x370... failed
>>> Probing for SMSC Super I/O at 0x370... failed
>>> Probing for Winbond Super I/O (init=0x88) at 0x2e... failed
>>> Probing for Winbond Super I/O (init=0x89) at 0x2e... failed
>>> Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... failed
>>> Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... failed
>>> Probing for Winbond Super I/O (init=0x88) at 0x4e... failed
>>> Probing for Winbond Super I/O (init=0x89) at 0x4e... failed
>>> Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... failed
>>> Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... failed
>>> Probing for Winbond Super I/O (init=0x88) at 0x3f0... failed
>>> Probing for Winbond Super I/O (init=0x89) at 0x3f0... failed
>>> Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... failed
>>> Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... failed
>>> Probing for Winbond Super I/O (init=0x88) at 0x370... failed
>>> Probing for Winbond Super I/O (init=0x89) at 0x370... failed
>>> Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... failed
>>> Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... failed
>>> Probing for Winbond Super I/O (init=0x88) at 0x250... failed
>>> Probing for Winbond Super I/O (init=0x89) at 0x250... failed
>>> Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... failed
>>> Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... failed
>> Your superiotool version seems broken. Probably one of Uwe's "trivial"
>> patches.
> 
> Hmm... is it possible that the Satellite 1415 doesn't have a Super I/O ?

Probably the Super I/O is inside the embedded controller and responds to
a special probe sequence.

However, the probing sequence is incomplete (at least when judging it by
its output) and Uwe rewrote the probing sequence, so he can take a look
at it.

> (could verbose mode please print out the version # ?)

Good idea. Care to send a patch?

Carl-Daniel




More information about the coreboot mailing list