Hi,
as you may have noticed, we have a relatively new tool called 'superiotool' (http://linuxbios.org/index.php/Superiotool) in the repository:
$ svn co svn://linuxbios.org/repos/trunk/util/superiotool
It is able to detect which Super I/O is located on your mainboard, and (if the respective code support was added), it can also dump the contents of all registers on the Super I/O:
$ superiotool -d
This will hopefully be helpful in debugging Super I/O related problems, e.g. with keyboards, systems sensors and fans, etc.
To make the tool more useful we need
- As many supported Super I/Os as possible.
Supporting new ones is relatively easy, but a bit time-consuming. You have to grab the datasheet, find out the ID/version of the Super I/O and add it in the respective file (ite.c for ITE Super I/Os, for example). For the dump functionality you have to add a (large) table with all registers and their defaults.
- One or two outputs of 'superiotool -d' for each supported Super I/O for reference, so we can compare values for different boards.
If you have one of the supported Super I/Os (see table in http://linuxbios.org/Superiotool) please run 'superiotool -d' as root, reply to this email and submit the output. We'll then link to your email (in the list archive) in the wiki page.
Thanks, Uwe.
./superiotool -d Found ITE IT8708F (id=0x8708, rev=0x0) at port=0x2e Register dump: idx 07 20 21 22 23 24 25 26 27 28 29 2a 2e 2f val 02 87 08 00 00 00 00 00 03 01 01 00 00 00 def NA 87 08 00 00 NA 3f 00 ff ff ff ff 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 val 01 03 f0 06 02 00 80 def 00 03 f0 06 02 00 00 LDN 0x01 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 00 03 f8 04 00 LDN 0x02 (COM2) idx 30 60 61 70 f0 f1 f2 f3 val 01 02 f8 03 00 50 01 7f def 00 02 f8 03 00 50 00 7f LDN 0x03 (Parallel port) idx 30 60 61 62 63 64 65 70 74 f0 val 01 03 78 07 78 00 80 07 03 0b def 00 03 78 07 78 00 80 07 03 03 LDN 0x04 (SWC) idx e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f2 f3 f4 f5 f6 val 00 61 00 00 00 00 00 00 80 00 30 00 80 00 de def NA NA 00 00 00 00 00 00 00 00 00 00 00 NA NA LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 71 f0 val 01 00 60 00 64 01 02 0c def 01 00 60 00 64 01 02 00 LDN 0x06 (Mouse) idx 30 70 71 f0 val 01 0c 02 00 def 00 0c 02 00 LDN 0x07 (GPIO) idx 70 b0 b1 b2 b3 b4 b5 b8 b9 ba bb bc bd c0 c1 c2 c3 c4 c5 c8 c9 ca cb cc cd d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc val 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 01 01 00 00 00 03 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff 7f 20 51 00 0e 00 00 00 00 00 18 00 def 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA NA NA NA NA NA 00 00 00 00 00 00 00 00 00 00 00 NA 00 LDN 0x08 (Game port) idx 30 60 61 val 00 02 01 def 00 02 01 LDN 0x09 (Consumer IR) idx 30 60 61 70 f0 val 00 03 10 0b 06 def 00 03 10 0b 00 LDN 0x0a (MIDI port) idx 30 60 61 70 f0 val 00 03 00 0a 40 def 00 03 00 0a 00
Uwe.
On Sun, Sep 23, 2007 at 01:13:15PM +0200, Uwe Hermann wrote:
Hi,
as you may have noticed, we have a relatively new tool called 'superiotool' (http://linuxbios.org/index.php/Superiotool) in the repository:
$ svn co svn://linuxbios.org/repos/trunk/util/superiotool
It is able to detect which Super I/O is located on your mainboard, and (if the respective code support was added), it can also dump the contents of all registers on the Super I/O:
$ superiotool -d
This will hopefully be helpful in debugging Super I/O related problems, e.g. with keyboards, systems sensors and fans, etc.
To make the tool more useful we need
As many supported Super I/Os as possible.
Supporting new ones is relatively easy, but a bit time-consuming. You have to grab the datasheet, find out the ID/version of the Super I/O and add it in the respective file (ite.c for ITE Super I/Os, for example). For the dump functionality you have to add a (large) table with all registers and their defaults.
One or two outputs of 'superiotool -d' for each supported Super I/O for reference, so we can compare values for different boards.
If you have one of the supported Super I/Os (see table in http://linuxbios.org/Superiotool) please run 'superiotool -d' as root, reply to this email and submit the output. We'll then link to your email (in the list archive) in the wiki page.
Oh, and some open questions remain:
Do we want to logs more information in addition to the pure 'superiotool -d' output? The same Super I/O on different boards can be configured differently, can be at another port (0x2e / 0x4e) etc. etc.
How about mainboard vendor/name/PCB-revision and lspci -nn? Other information?
Suggestions welcome!
Uwe.
This is a Fujitsu-Siemens Lifebook S4572 notebook.
./superiotool -d Found SMSC FDC37N769 (id=0x28, rev=0x01) at port=0x3f0 Register dump: idx 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f val 20 90 80 f4 00 00 ff 00 00 00 40 00 0e 28 01 00 00 00 00 00 02 00 01 03 00 00 00 00 00 00 80 00 00 00 00 00 00 ba 00 00 03 00 00 23 03 03 00 00 def 28 9c 88 70 00 00 ff 00 00 00 00 00 02 28 NA 00 00 80 RR RR NA NA NA 03 RR RR RR RR RR RR 80 00 3c RR RR 00 00 00 00 00 00 00 RR 00 00 03 00 00
Uwe.
Some Intel board, don't remember details and I don't have access to it right now.
$ superiotool -d: Found ITE IT8718F (id=0x8718, rev=0x1) at port=0x2e Register dump: idx 07 20 21 22 23 24 2b val 0a 87 18 01 10 00 00 def NA 87 18 01 00 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 val 01 03 f0 06 02 00 80 def 00 03 f0 06 02 00 00 LDN 0x01 (COM1) idx 30 60 61 70 f0 f1 f2 f3 val 01 03 f8 04 00 50 00 7f def 00 03 f8 04 00 50 00 7f LDN 0x02 (COM2) idx 30 60 61 70 f0 f1 f2 f3 val 01 02 f8 03 00 50 00 7f def 00 02 f8 03 00 50 00 7f LDN 0x03 (Parallel port) idx 30 60 61 62 63 70 74 f0 val 01 03 78 00 00 07 04 08 def 00 03 78 07 78 07 03 03 LDN 0x04 (Environment controller) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 val 01 02 90 00 00 00 80 00 0a 00 c0 00 ff def 00 02 90 02 30 09 00 00 00 00 00 NA NA LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 71 f0 val 01 00 60 00 64 01 02 68 def 01 00 60 00 64 01 02 00 LDN 0x06 (Mouse) idx 30 70 71 f0 val 01 0c 02 00 def 00 0c 02 00 LDN 0x07 (GPIO) idx 25 26 27 28 29 2a 2c 60 61 62 63 64 65 70 71 72 73 74 b0 b1 b2 b3 b4 b5 b8 b9 ba bb bc bd c0 c1 c2 c3 c4 c8 c9 ca cb cc e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff val 00 02 00 40 00 00 1c 00 00 08 00 00 00 00 01 00 38 00 00 00 00 00 00 00 00 02 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 26 00 00 00 00 00 53 00 00 00 def 01 00 00 40 00 00 00 00 00 00 00 00 00 00 00 20 38 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 40 00 01 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA 00 00 00 LDN 0x0a (Consumer IR) idx 30 60 61 70 f0 val 00 03 10 0b 06 def 00 03 10 0b 00
Uwe.
MSI MS-7260 (K9N Neo), rev. 1.0.
./superiotool -d Found Winbond W83627EHF/EF/EHG/EG (id=0x88, rev=0x68) at 0x4e Register dump: idx 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f val 88 68 ff 00 04 00 40 ff 50 01 9c 00 01 21 00 ff def 88 MM ff 00 MM 00 MM RR 50 04 00 RR 00 21 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 01 03 f0 06 02 8e 00 ff 00 00 def 01 03 f0 06 02 8e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 00 00 00 00 04 3f def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 01 02 f8 03 00 54 def 01 02 f8 03 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 72 f0 val 01 00 60 00 64 01 0c 82 def 01 00 60 00 64 01 0c 83 LDN 0x06 (Serial flash interface) idx 30 62 63 val 00 ff ff def 00 00 00 LDN 0x07 (GPIO 1, GPIO 6, game port, MIDI port) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 f7 val 09 00 00 00 00 00 c3 ff 00 00 ff 00 00 00 def 00 02 01 03 30 09 ff 00 00 00 ff 00 00 00 LDN 0x08 (WDTO#, PLED) idx 30 f5 f6 f7 val 00 ff 00 ff def 00 00 00 00 LDN 0x09 (GPIO 2, GPIO 3, GPIO 4, GPIO 5, SUSLED) idx 30 e0 e1 e2 e3 e4 e5 f0 f1 f2 f3 f4 f5 f6 f7 val 00 ff ff ff ff ff ff ff ff ff 09 ff ff ff ff def 00 ff 00 00 ff 00 00 ff 00 00 00 ff 00 00 00 LDN 0x0a (ACPI) idx 30 70 e0 e1 e2 e3 e4 e5 e6 e7 e8 f2 f3 f4 f6 f7 val 01 00 01 00 44 00 00 00 1c 00 09 7c 00 00 00 00 def 00 00 01 00 ff 08 00 RR 00 00 RR 7c 00 00 00 00 LDN 0x0b (Hardware monitor) idx 30 60 61 70 f0 f1 val 01 0a 10 00 c1 3f def 00 00 00 00 c1 00
Uwe.
This is the ASUS A8NE-FM/S board, rev. 1.01A.
./superiotool -d Found ASUS A8000 (id=0x77, rev=0x01) at port=0x2e Register dump: idx 03 07 20 21 22 23 24 26 27 28 2a 2b 2c 2d 2e 2f val 00 0a 77 01 18 00 44 2e 00 00 00 00 00 00 00 00 def RR 00 77 NA 00 RR 44 MM MM RR NA NA NA NA NA NA LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 00 00 00 00 04 0e 00 ff 00 00 def 00 03 f0 06 02 0e 00 ff 00 00 LDN 0x03 (Parallel port) idx 30 60 61 70 74 f0 f1 val 01 03 78 07 04 38 00 def 00 00 00 00 04 3c 00 LDN 0x04 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 00 00 00 00 00 LDN 0x05 (COM2) idx 30 60 61 70 f0 f1 f2 val 00 00 00 00 00 02 03 def 00 00 00 00 00 02 03 LDN 0x07 (Keyboard) idx 30 70 72 f0 val 01 01 0c 00 def 00 00 00 00 LDN 0x0a (Runtime registers) idx 30 60 61 62 63 f0 f1 f2 val 01 08 00 00 00 00 00 04 def 00 00 00 00 00 NA RR 04
Uwe.
On 9/23/07, Uwe Hermann uwe@hermann-uwe.de wrote:
To make the tool more useful we need
As many supported Super I/Os as possible.
Supporting new ones is relatively easy, but a bit time-consuming. You have to grab the datasheet, find out the ID/version of the Super I/O and add it in the respective file (ite.c for ITE Super I/Os, for example). For the dump functionality you have to add a (large) table with all registers and their defaults.
Okay -- I grabbed the code from SVN, compiled it and ran it on a few computers, but I didn't get any useful output (verbose mode was also pretty sparse). I assume that this means that my Super I/O chips are not supported, correct?
I did some digging online, but I wasn't very successful in finding datasheets for Super I/Os. If someone could point me in the right direction, I could take a few datasheets and covert them into the appropriate tables. Although it would be nifty to add support for whatever chips are on my motherboards, I'm happy to work on whatever Super I/Os datasheets are available right now.
On 27.09.2007 18:21, Robinson Tryon wrote:
On 9/23/07, Uwe Hermann uwe@hermann-uwe.de wrote:
To make the tool more useful we need
As many supported Super I/Os as possible.
Supporting new ones is relatively easy, but a bit time-consuming. You have to grab the datasheet, find out the ID/version of the Super I/O and add it in the respective file (ite.c for ITE Super I/Os, for example). For the dump functionality you have to add a (large) table with all registers and their defaults.
Okay -- I grabbed the code from SVN, compiled it and ran it on a few computers, but I didn't get any useful output (verbose mode was also pretty sparse). I assume that this means that my Super I/O chips are not supported, correct?
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.
I did some digging online, but I wasn't very successful in finding datasheets for Super I/Os. If someone could point me in the right direction, I could take a few datasheets and covert them into the appropriate tables. Although it would be nifty to add support for whatever chips are on my motherboards, I'm happy to work on whatever Super I/Os datasheets are available right now.
I can send dozens of ITE data sheets (even for now unavailable chips) your way.
What's the vendor of your Super I/O?
Carl-Daniel
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 27.09.2007 18:21, Robinson Tryon wrote:
On 9/23/07, Uwe Hermann uwe@hermann-uwe.de wrote:
To make the tool more useful we need
As many supported Super I/Os as possible.
Supporting new ones is relatively easy, but a bit time-consuming. You have to grab the datasheet, find out the ID/version of the Super I/O and add it in the respective file (ite.c for ITE Super I/Os, for example). For the dump functionality you have to add a (large) table with all registers and their defaults.
Okay -- I grabbed the code from SVN, compiled it and ran it on a few computers, but I didn't get any useful output (verbose mode was also pretty sparse). I assume that this means that my Super I/O chips are not supported, correct?
Not supported by superiotool, however if there was any output at all, we'd like to know it.
Ok. I'll re-run the tests when I get a chance and send in the output.
I can send dozens of ITE data sheets (even for now unavailable chips) your way.
Great. If you could just put those on a webserver someplace, that would be excellent. Any kind of preference on what chips get supported first?
What's the vendor of your Super I/O?
Well, as I said, I tested superiotool on multiple machines. I should be able to just crack the case on a machine and spot it on the motherboard, I assume?
On 27.09.2007 18:45, Robinson Tryon wrote:
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 27.09.2007 18:21, Robinson Tryon wrote:
On 9/23/07, Uwe Hermann uwe@hermann-uwe.de wrote:
To make the tool more useful we need
As many supported Super I/Os as possible.
Supporting new ones is relatively easy, but a bit time-consuming. You have to grab the datasheet, find out the ID/version of the Super I/O and add it in the respective file (ite.c for ITE Super I/Os, for example). For the dump functionality you have to add a (large) table with all registers and their defaults.
Okay -- I grabbed the code from SVN, compiled it and ran it on a few computers, but I didn't get any useful output (verbose mode was also pretty sparse). I assume that this means that my Super I/O chips are not supported, correct?
Not supported by superiotool, however if there was any output at all, we'd like to know it.
Ok. I'll re-run the tests when I get a chance and send in the output.
Thanks.
I can send dozens of ITE data sheets (even for now unavailable chips) your way.
Great. If you could just put those on a webserver someplace, that
I have some worries about copyright issues. Yes, they were freely downloadable, but...
would be excellent. Any kind of preference on what chips get supported first?
Winbond and ITE are the ones where Uwe and I are specialized.
What's the vendor of your Super I/O?
Well, as I said, I tested superiotool on multiple machines. I should be able to just crack the case on a machine and spot it on the motherboard, I assume?
Yes, but we'll probably be able to tell it from the short output without opening any machine.
Carl-Daniel
On Thu, Sep 27, 2007 at 06:54:28PM +0200, Carl-Daniel Hailfinger wrote:
Well, as I said, I tested superiotool on multiple machines. I should be able to just crack the case on a machine and spot it on the motherboard, I assume?
Yes, but we'll probably be able to tell it from the short output without opening any machine.
Looking at the actual chip would still be useful sometimes, for instance to spot datasheet ID/rev errors (e.g. when the chip says it's a different chip than what the IDs tell you).
As for datasheets:
http://www.ite.com.tw/product_info/PC/pc_product_info_2.asp http://www.winbond.com/hq/enu/ProductAndSales/ProductLines/ComputerLogicIC/ http://www.winbond.com/hq/enu/ProductAndSales/ProductReference/EOLProducts/ http://www.smsc.com/main/datasheet.html ftp://ftp.smsc.com/pub/datasheets/ ftp://ftp.smsc.com/pub/discontinued/ http://www.fintek.com.tw/eng/products.asp?BID=1&SID=17&layer=0
Probably lots more which I missed right now (just google for the Super I/O name, that should find you datasheets for almost all of them). Hm, maybe we should add a "Datasheets" wiki page with links?
Uwe.
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 27.09.2007 18:21, Robinson Tryon wrote:
Okay -- I grabbed the code from SVN, compiled it and ran it on a few computers, but I didn't get any useful output (verbose mode was also pretty sparse). I assume that this means that my Super I/O chips are not supported, correct?
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.
What kinds of machines would you like output from? Any hardware I can get to run 'superiotool' ? :-)
What other information should I include? Motherboard model? Output from lspci?
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@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.
Dell XPS Inspiron PP09L
ubuntu@ubuntu:~$ sudo ./superiotool -v superiotool 0.1 ubuntu@ubuntu:~$ sudo ./superiotool -V No Super I/O chip found at 0x002e No Super I/O chip found at 0x004e No Super I/O chip found at 0x002e No Super I/O chip found at 0x004e Probing 0x002e, failed (0x22), data returns 0x00 Probing 0x002e, failed (0x22), data returns 0x00 No Super I/O chip found at 0x004e No Super I/O chip found at 0x004e Probing 0x002e, failed (0x0e), data returns 0x00 Probing 0x002e, failed (0x21), data returns 0x11 No Super I/O chip found at 0x004e No Super I/O chip found at 0x004e No Super I/O chip found at 0x03f0 No Super I/O chip found at 0x03f0 No Super I/O chip found at 0x0370 No Super I/O chip found at 0x0370 No Super I/O chip found at 0x002e No Super I/O chip found at 0x002e No Super I/O chip found at 0x002e No Super I/O chip found at 0x002e No Super I/O chip found at 0x004e No Super I/O chip found at 0x004e No Super I/O chip found at 0x004e No Super I/O chip found at 0x004e No Super I/O chip found at 0x03f0 No Super I/O chip found at 0x03f0 No Super I/O chip found at 0x03f0 No Super I/O chip found at 0x03f0 No Super I/O chip found at 0x0370 No Super I/O chip found at 0x0370 No Super I/O chip found at 0x0370 No Super I/O chip found at 0x0370 No Super I/O chip found at 0x0250 No Super I/O chip found at 0x0250 No Super I/O chip found at 0x0250 No Super I/O chip found at 0x0250
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@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: Dell Computer Corporation Product Name: OptiPlex GX1 400MTbr+
# ./superiotool -v superiotool r2815þ2@ # ./superiotool -V Probing for ALi Super I/O at 0x3f0... failed Probing for ALi Super I/O at 0x370... failed Super I/O found at 0x2e: id = 0xe0 <unknown> No dump for 0xe0 Probing for NSC Super I/O at 0x4e... failed Probing 0x2e, failed (0x24), data returns 0x00 Probing for Fintek Super I/O at 0x4e... failed Probing 0x2e, failed (0x22), data returns 0x70 Probing 0x2e, failed (0x22), data returns 0x70 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 0x0f 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 0x2e, failed (0x09), data returns 0x00 Probing 0x2e, failed (0x09), data returns 0x00 Probing 0x2e, failed (0x09), data returns 0x00 Probing 0x2e, failed (0x09), data returns 0x00 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
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@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
Uwe Hermann uwe@hermann-uwe.de wrote:
$ superiotool -d
Here comes a few: Mainboard: Asus N4L-VM DH (945GM board with socket 479)
Found Winbond W83627EHF/EF/EHG/EG (id=0x88, rev=0x63) at 0x2e Register dump: idx 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f val 88 63 ff 00 44 00 00 ff 50 04 00 00 9a 21 00 ff def 88 MM ff 00 MM 00 MM RR 50 04 00 RR 00 21 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 00 03 f0 06 02 0e 00 ff 00 00 def 01 03 f0 06 02 8e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 00 03 78 00 04 3c def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 00 03 f8 04 00 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 00 02 f8 03 00 00 def 01 02 f8 03 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 72 f0 val 01 00 60 00 64 01 0c 83 def 01 00 60 00 64 01 0c 83 LDN 0x06 (Serial flash interface) idx 30 62 63 val 00 ff ff def 00 00 00 LDN 0x07 (GPIO 1, GPIO 6, game port, MIDI port) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 f7 val 00 02 01 03 30 00 ff ff ff ff ff ff ff 00 def 00 02 01 03 30 09 ff 00 00 00 ff 00 00 00 LDN 0x08 (WDTO#, PLED) idx 30 f5 f6 f7 val 00 ff 00 ff def 00 00 00 00 LDN 0x09 (GPIO 2, GPIO 3, GPIO 4, GPIO 5, SUSLED) idx 30 e0 e1 e2 e3 e4 e5 f0 f1 f2 f3 f4 f5 f6 f7 val 0f ff 21 00 ff 08 00 ff 0c 00 09 9f ff 00 00 def 00 ff 00 00 ff 00 00 ff 00 00 00 ff 00 00 00 LDN 0x0a (ACPI) idx 30 70 e0 e1 e2 e3 e4 e5 e6 e7 e8 f2 f3 f4 f6 f7 val 01 00 00 00 ff 00 40 02 0c 10 09 7d 00 00 00 00 def 00 00 01 00 ff 08 00 RR 00 00 RR 7c 00 00 00 00 LDN 0x0b (Hardware monitor) idx 30 60 61 70 f0 f1 val 01 02 90 00 c1 3f def 00 00 00 00 c1 00
Mainboard: MSI K7T266 PRO2 (MS-6380 v2.0) Found Winbond W83627HF/F/HG/G (id=0x52, rev=0x17) at 0x2e No dump available for this Super I/O
I also ran superiotool on an Asus L8400 laptop and a HP compaq d530 sff desktop, but it did not detect any super I/O. Opening up the HP revealed an SMSC LPC47B387-NC, I feel a bit reluctant to take the laptop apart.
/Rasmus Wiman
On 02.10.2007 05:37, Robinson Tryon wrote:
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@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.
Carl-Daniel
On 02.10.2007 00:33, Robinson Tryon wrote:
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 27.09.2007 18:21, Robinson Tryon wrote:
Okay -- I grabbed the code from SVN, compiled it and ran it on a few computers, but I didn't get any useful output (verbose mode was also pretty sparse). I assume that this means that my Super I/O chips are not supported, correct?
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.
What kinds of machines would you like output from? Any hardware I can get to run 'superiotool' ? :-)
Basically, if the chipset (north-/southbridge) is supported, the first step in trying to port LB to the mainboard is running superiotool so you can find out the correct settings for early serial output.
What other information should I include? Motherboard model? Output from lspci?
Motherboard model and if possible the numbers printed on top of the Super I/O chip.
We can then locate the right data sheet and give it either to you or add support for the part to superiotool ourselves.
Carl-Daniel
On 10/2/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 02.10.2007 05:37, Robinson Tryon wrote:
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@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 ?
(could verbose mode please print out the version # ?)
On 02.10.2007 17:44, Robinson Tryon wrote:
On 10/2/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 02.10.2007 05:37, Robinson Tryon wrote:
On 9/27/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@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
On 10/2/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 02.10.2007 17:44, Robinson Tryon wrote:
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.
Ah, interesting.
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?
Sure -- see attachment.
Hi Robinson,
On Tue, Oct 02, 2007 at 02:34:37PM -0400, Robinson Tryon wrote:
(could verbose mode please print out the version # ?)
Good idea. Care to send a patch?
Sure -- see attachment.
Could you resend with a signed-off-by?
Thanks, Ward.
On 10/2/07, Robinson Tryon bishop.robinson@gmail.com wrote:
(could verbose mode please print out the version # ?)
Good idea. Care to send a patch?
Sure -- see attachment.
Sorry about that. Here's my signed-off by:
Signed-off-by: Robinson P. Tryon bishop.robinson@gmail.com
On Tue, Oct 02, 2007 at 03:26:20PM -0400, Robinson Tryon wrote:
Signed-off-by: Robinson P. Tryon bishop.robinson@gmail.com
Thanks, committed in r2818 with some minor changes (no need to add the prototype in superiotool.h as we only use the function in superiotool.c).
Uwe.
On Mon, Oct 01, 2007 at 11:34:05PM -0400, Robinson Tryon wrote:
System Information Manufacturer: Dell Computer Corporation Product Name: OptiPlex GX1 400MTbr+
# ./superiotool -v superiotool r2815þ2@ # ./superiotool -V Probing for ALi Super I/O at 0x3f0... failed Probing for ALi Super I/O at 0x370... failed Super I/O found at 0x2e: id = 0xe0
<unknown> No dump for 0xe0
This _might_ be the NSC PC87309 chip. No support yet, but the NSC code needs a rewrite to make it more generic anyway.
Can you look at the mainboard and find out which chip it actually is?
Uwe.
On Tue, Oct 02, 2007 at 05:50:40PM +0200, Carl-Daniel Hailfinger wrote:
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.
Will do. What do you mean with incomplete? The --verbose output needs some more fixing to make it more informative, IMO.
Uwe.
[Please always reply to the list]
On Fri, Sep 28, 2007 at 12:01:09PM -0400, Robinson Tryon wrote:
On 9/23/07, Uwe Hermann uwe@hermann-uwe.de wrote:
Supporting new ones is relatively easy, but a bit time-consuming. You have to grab the datasheet, find out the ID/version of the Super I/O and add it in the respective file (ite.c for ITE Super I/Os, for example). For the dump functionality you have to add a (large) table with all registers and their defaults.
I went through with the 8726F and saw how the register table in ite.c matched up with the datasheet, but I couldn't find the ID/Version number mentioned anywhere in the datasheet. For ITE chips it looks like the ID generally matches up with the name of the chip, but I figure that it would be best if I could actually look up that information in the datasheet -- especially if other chips don't follow this convention.
Yes, you should definately look up the ID. Many other chips/vendors use various different IDs of various sizes and in various locations.
What's the best way for me to search through a datasheet to find the ID/Version?
There's no general rule, but look for something like "chip id" or "chip revision" or similar. Usually this information (together with the required init sequence and ports) is somewhere near the "Global Configuration Registers" or "PNP configuration" or similar chapter.
HTH, Uwe.
On 10/2/07, Uwe Hermann uwe@hermann-uwe.de wrote:
On Mon, Oct 01, 2007 at 11:34:05PM -0400, Robinson Tryon wrote:
System Information Manufacturer: Dell Computer Corporation Product Name: OptiPlex GX1 400MTbr+
# ./superiotool -v superiotool r2815þ2@ # ./superiotool -V Probing for ALi Super I/O at 0x3f0... failed Probing for ALi Super I/O at 0x370... failed Super I/O found at 0x2e: id = 0xe0
<unknown> No dump for 0xe0
This _might_ be the NSC PC87309 chip. No support yet, but the NSC code needs a rewrite to make it more generic anyway.
Can you look at the mainboard and find out which chip it actually is?
sure -- it'll be a couple days until I can get to it and crack it open, though.
On Tue, Oct 02, 2007 at 03:29:38PM +0200, Rasmus Wiman wrote:
Here comes a few: Mainboard: Asus N4L-VM DH (945GM board with socket 479)
Found Winbond W83627EHF/EF/EHG/EG (id=0x88, rev=0x63) at 0x2e Register dump: idx 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f val 88 63 ff 00 44 00 00 ff 50 04 00 00 9a 21 00 ff def 88 MM ff 00 MM 00 MM RR 50 04 00 RR 00 21 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 00 03 f0 06 02 0e 00 ff 00 00 def 01 03 f0 06 02 8e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 00 03 78 00 04 3c def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 00 03 f8 04 00 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 00 02 f8 03 00 00 def 01 02 f8 03 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 72 f0 val 01 00 60 00 64 01 0c 83 def 01 00 60 00 64 01 0c 83 LDN 0x06 (Serial flash interface) idx 30 62 63 val 00 ff ff def 00 00 00 LDN 0x07 (GPIO 1, GPIO 6, game port, MIDI port) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 f7 val 00 02 01 03 30 00 ff ff ff ff ff ff ff 00 def 00 02 01 03 30 09 ff 00 00 00 ff 00 00 00 LDN 0x08 (WDTO#, PLED) idx 30 f5 f6 f7 val 00 ff 00 ff def 00 00 00 00 LDN 0x09 (GPIO 2, GPIO 3, GPIO 4, GPIO 5, SUSLED) idx 30 e0 e1 e2 e3 e4 e5 f0 f1 f2 f3 f4 f5 f6 f7 val 0f ff 21 00 ff 08 00 ff 0c 00 09 9f ff 00 00 def 00 ff 00 00 ff 00 00 ff 00 00 00 ff 00 00 00 LDN 0x0a (ACPI) idx 30 70 e0 e1 e2 e3 e4 e5 e6 e7 e8 f2 f3 f4 f6 f7 val 01 00 00 00 ff 00 40 02 0c 10 09 7d 00 00 00 00 def 00 00 01 00 ff 08 00 RR 00 00 RR 7c 00 00 00 00 LDN 0x0b (Hardware monitor) idx 30 60 61 70 f0 f1 val 01 02 90 00 c1 3f def 00 00 00 00 c1 00
Thanks, added a link to the wiki.
Mainboard: MSI K7T266 PRO2 (MS-6380 v2.0) Found Winbond W83627HF/F/HG/G (id=0x52, rev=0x17) at 0x2e No dump available for this Super I/O
If you want to, feel free to grab the datasheet and add dump support. Nothing complex, just a bit time-consuming...
I also ran superiotool on an Asus L8400 laptop and a HP compaq d530 sff desktop, but it did not detect any super I/O. Opening up the HP revealed an SMSC LPC47B387-NC, I feel a bit reluctant to take the laptop apart.
Interesting. I can't find a datasheet for the LPC47B387, so dump support won't happen anytime soon. But it would be nice if you could re-run 'superiotool -V' on that box with my latest patch applied ([PATCH] superiotool: Various improvements). That should tell us the Super I/O ID, I hope, so we can at least detect the chip.
Uwe.
Uwe Hermann uwe@hermann-uwe.de wrote:
Interesting. I can't find a datasheet for the LPC47B387, so dump support won't happen anytime soon. But it would be nice if you could re-run 'superiotool -V' on that box with my latest patch applied ([PATCH] superiotool: Various improvements). That should tell us the Super I/O ID, I hope, so we can at least detect the chip.
Ok, here is the result: ./superiotool -V superiotool r2815 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0x0000, rev=0x00 Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0x6e00, rev=0x9 Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0x6e00, rev=0x9 Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0x6e, rev=0x00 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
By the way, svn said I checked out r2820, but superiotool says r2815.
/Rasmus
On Thu, Oct 04, 2007 at 04:19:56PM +0200, Rasmus Wiman wrote:
Interesting. I can't find a datasheet for the LPC47B387, so dump support won't happen anytime soon. But it would be nice if you could re-run 'superiotool -V' on that box with my latest patch applied ([PATCH] superiotool: Various improvements). That should tell us the Super I/O ID, I hope, so we can at least detect the chip.
Ok, here is the result:
Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0x6e, rev=0x00
OK, good. Looks like 0x6e is the ID for the LPC47B387.
Please retry with r2823, just to make sure detection really works (just run 'superiotool').
By the way, svn said I checked out r2820, but superiotool says r2815.
Yes, unfortunately. I think I was wrong, the version-from-svn thing won't work for us. More on that in another mail.
Uwe.
On Thu, Oct 04, 2007 at 04:22:02AM +0200, Uwe Hermann wrote:
I also ran superiotool on an Asus L8400 laptop and a HP compaq d530 sff desktop, but it did not detect any super I/O. Opening up the HP
Oh, I almost forgot: what does the latest version say on the laptop when run with --verbose?
Uwe.
On 03.10.2007 04:42, Uwe Hermann wrote:
On Tue, Oct 02, 2007 at 05:50:40PM +0200, Carl-Daniel Hailfinger wrote:
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.
Will do. What do you mean with incomplete? The --verbose output needs some more fixing to make it more informative, IMO.
ITE superio probing at 0x2e does not appear in the log above.
Carl-Daniel
Uwe Hermann uwe@hermann-uwe.de skrev:
On Thu, Oct 04, 2007 at 04:22:02AM +0200, Uwe Hermann wrote:
I also ran superiotool on an Asus L8400 laptop and a HP compaq d530 sff desktop, but it did not detect any super I/O. Opening up the HP
Oh, I almost forgot: what does the latest version say on the laptop when run with --verbose?
Horribly little, I'm afraid. Seems like every probe attempt returns the same.
./superiotool -V superiotool r2815 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0xffff, rev=0xff Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
/Rasmus
Uwe Hermann uwe@hermann-uwe.de wrote:
Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0x6e, rev=0x00
OK, good. Looks like 0x6e is the ID for the LPC47B387.
Please retry with r2823, just to make sure detection really works (just run 'superiotool').
It worked!
./superiotool Found SMSC LPC47B387 (id=0x6e, rev=0x00) at 0x2e
./superiotool --verbose superiotool r2815 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0x0000, rev=0x00 Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0x6e00, rev=0x9 Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0x6e00, rev=0x9 Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Found SMSC LPC47B387 (id=0x6e, rev=0x00) at 0x2e Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
/Rasmus
Uwe Hermann uwe@hermann-uwe.de wrote:
If you want to, feel free to grab the datasheet and add dump support. Nothing complex, just a bit time-consuming...
Not so time-consuming for an unemployed guy like me. A few questions, though. I am not sure how I am supposed to use the constants NANA, RSVD and MISC, as defined in superiotool.h. I marked the default for global CR 07 and 21 as NANA, but 07 is logical device number and msd of 21 is supposedly always 1 and lsd is chip revision id, on my HF it is 7. For 24 the datasheet says "Default 0b1s000s0s", a notation I'm unfamiliar with, so I set the default to MISC. This is very likely the wrong way to do it. Also, a few registers are specified as "reserved" or "Test:Reserver for winbond", but they provide a default, so I entered that default.
Also, I only grabbed the W83627HF/F datasheet, I think there was a HG/G sheet available too.
Rasmus Wiman rasmus@wiman.org wrote:
Also, I only grabbed the W83627HF/F datasheet, I think there was a HG/G sheet available too.
Rediffed against r2825, my patch was against r2823.
This is an IBM NetVista A30p box.
$ superiotool -d Found SMSC LPC47M10x (id=0x59, rev=0x01) at 0x2e Register dump: idx 03 07 20 21 22 23 24 26 27 28 2a 2b 2c 2d 2e 2f val 00 0b 59 01 39 00 44 2e 00 00 00 00 00 00 00 00 def RR 00 59 NA 00 00 44 MM MM RR NA NA NA NA NA NA LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 01 03 f0 06 02 0e 00 ff 00 00 def 00 03 f0 06 02 0e 00 ff 00 00 LDN 0x03 (Parallel port) idx 30 60 61 70 74 f0 f1 val 01 03 78 07 03 ba 00 def 00 00 00 00 04 3c 00 LDN 0x04 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 00 00 00 00 00 LDN 0x05 (COM2) idx 30 60 61 62 63 70 74 f0 f1 f2 val 01 02 f8 00 00 03 04 00 06 03 def NA 00 00 RR RR 00 RR 00 02 03 LDN 0x07 (Keyboard) idx 30 70 72 f0 val 01 01 0c 04 def 00 00 00 00 LDN 0x09 (Game port) idx 30 60 61 val 00 00 00 def 00 00 00 LDN 0x0a (Power Management Events (PME)) idx 30 60 61 f0 f1 val 01 08 00 00 00 def 00 00 00 NA RR LDN 0x0b (MPU-401) idx 30 60 61 70 val 00 03 30 05 def 00 03 30 05
Uwe.
On Thu, Oct 04, 2007 at 06:43:40PM +0200, Carl-Daniel Hailfinger wrote:
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
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.
Will do. What do you mean with incomplete? The --verbose output needs some more fixing to make it more informative, IMO.
ITE superio probing at 0x2e does not appear in the log above.
Ah, yes, indeed. I think it _was_ being probed but not correctly shown in the output. I guess the two 'Probing 0x2e, failed...' lines belong to the ITE 0x2e probing.
Anyway, the output should be much better in the latest revision. Can you please repost the --verbose output?
Uwe.
Rasmus Wiman rasmus@wiman.org wrote:
Rediffed against r2825, my patch was against r2823.
Oh, I forgot, you might want this too. Mainboard is still the MSI K7T266 PRO2 (MS-6380 v2.0)
su -c './superiotool -d' Password: Found Winbond W83627HF/F/HG/G (id=0x52, rev=0x17) at 0x2e Register dump: idx 02 07 20 21 22 23 24 25 26 28 29 2a 2b 2c 2e 2f val ff 0b 52 17 ff fe c4 00 00 00 70 7c 10 ff 00 ff def 00 NA 52 NA ff 00 MM 00 00 00 00 7c c0 00 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 01 03 f0 06 02 0e 00 ff 00 00 def 01 03 f0 06 02 0e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 01 03 78 07 03 3a def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 01 02 f8 03 00 44 def 01 02 f8 03 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 72 f0 val 01 00 60 00 64 01 0c 80 def 01 00 60 00 64 01 0c 80 LDN 0x06 (Consumer IR) idx 30 60 61 70 val 00 00 00 00 def 00 00 00 00 LDN 0x07 (Game port, MIDI port, GPIO 1) idx 30 60 61 62 63 70 f0 f1 f2 val 03 02 00 00 00 00 ff 00 00 def 00 02 01 03 30 09 ff 00 00 LDN 0x08 (GPIO 2) idx 30 f0 f1 f2 f3 f5 f6 f6 f7 val 01 ef 00 10 00 00 00 00 00 def 00 ff 00 00 00 00 00 00 00 LDN 0x09 (GPIO 3) idx 30 f0 f1 f2 f3 val 01 e3 00 00 00 def 00 ff 00 00 00 LDN 0x0a (ACPI) idx 30 70 e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f3 f4 f6 f7 f9 fe ff val 01 00 00 00 00 00 00 00 00 00 00 af 3c 04 00 00 05 00 00 def 00 00 00 00 NA NA 00 00 00 00 00 00 00 00 00 00 00 00 00 LDN 0x0b (Hardware monitor) idx 30 60 61 70 f0 val 01 02 90 00 01 def 00 00 00 00 00
On Fri, Oct 05, 2007 at 03:32:43PM +0200, Rasmus Wiman wrote:
Uwe Hermann uwe@hermann-uwe.de wrote:
If you want to, feel free to grab the datasheet and add dump support. Nothing complex, just a bit time-consuming...
Not so time-consuming for an unemployed guy like me. A few questions, though. I am not sure how I am supposed to use the constants NANA, RSVD and MISC, as defined in superiotool.h. I marked the default for global
This is up for discussion, more or less. Here's how I handled it until now:
RSVD -- registers marked as reverved in the datasheet
NANA -- do default available / mentioned in the datasheet
MISC -- random other values which cannot be expressed in numbers (e.g. "Bits 0 and 1 depend on the state of xyz, rest is 0"; in this case the default could be 0x03 or 0x00, we don't know. Thus MISC.)
CR 07 and 21 as NANA, but 07 is logical device number and msd of 21 is
CR 07 is debatable anyway. There's no real value in listing it at all, IMO. Maybe we should just drop it from all listings? Comments?
Revision IDs (which can change from chip to chip) should be NANA, at least that's how I handle them usually.
supposedly always 1 and lsd is chip revision id, on my HF it is 7. For 24 the datasheet says "Default 0b1s000s0s", a notation I'm unfamiliar
Good candidate for MISC, yes.
with, so I set the default to MISC. This is very likely the wrong way to do it. Also, a few registers are specified as "reserved" or "Test:Reserver for winbond", but they provide a default, so I entered that default.
Hm, neither solution is good for this case, IMO. But we have to choose one of them. I don't care which. Opinions?
Also, I only grabbed the W83627HF/F datasheet, I think there was a HG/G sheet available too.
Yes. But its unlikely that they're (very) different if they're documented in the same datasheet. I'll check later.
I was about to commit, but noticed that you forgot to add a Signed-off-by line, see http://linuxbios.org/index.php/Development_Guidelines#Sign-off_Procedure Please repost with a Signed-off-by.
No need to rediff btw, we can adapt the patch to (smaller) changes right before committing.
Uwe.
Uwe Hermann uwe@hermann-uwe.de wrote:
I was about to commit, but noticed that you forgot to add a Signed-off-by line, see http://linuxbios.org/index.php/Development_Guidelines#Sign-off_Procedure Please repost with a Signed-off-by.
No need to rediff btw, we can adapt the patch to (smaller) changes right before committing.
Ok, here comes the line. It's my first contribution to a free software project, so it feels great anyway.
Signed-off-by: Rasmus Wiman rasmus@wiman.org
On 05.10.2007 15:32, Rasmus Wiman wrote:
[...] the datasheet says "Default 0b1s000s0s", a notation I'm unfamiliar with, so I set the default to MISC.
AFAIK that is (at least partially) Verilog syntax.
Regards, Carl-Daniel
On Fri, Oct 05, 2007 at 07:15:02PM +0200, Rasmus Wiman wrote:
Signed-off-by: Rasmus Wiman rasmus@wiman.org
Thanks, committed in r2828 with some very small cosmetic changes. I also added you to the Copyright owner list at the top of the file.
Uwe.
On 10/5/07, Uwe Hermann uwe@hermann-uwe.de wrote:
On Fri, Oct 05, 2007 at 07:15:02PM +0200, Rasmus Wiman wrote:
Signed-off-by: Rasmus Wiman rasmus@wiman.org
Thanks, committed in r2828 with some very small cosmetic changes. I also added you to the Copyright owner list at the top of the file.
Should I be adding myself to the copyright owner list at the top of the files when I add dump support for chips? I assumed that copying the tables from the datasheets wouldn't be "creative" enough for me to assert a copyright on the commit...
On Fri, Oct 05, 2007 at 06:10:36PM -0400, Robinson Tryon wrote:
On 10/5/07, Uwe Hermann uwe@hermann-uwe.de wrote:
On Fri, Oct 05, 2007 at 07:15:02PM +0200, Rasmus Wiman wrote:
Signed-off-by: Rasmus Wiman rasmus@wiman.org
Thanks, committed in r2828 with some very small cosmetic changes. I also added you to the Copyright owner list at the top of the file.
Should I be adding myself to the copyright owner list at the top of the files when I add dump support for chips? I assumed that copying the tables from the datasheets wouldn't be "creative" enough for me to assert a copyright on the commit...
Hm, I think you're right. I acted a bit too fast by adding you to the Copyright header, sorry. However, we should still give proper credit to all contributors, so maybe we add a THANKS or AUTHORS file (or a section in the README file)?
Opinions?
Uwe.
Question about registers:
In the datasheet for the FDC37M81x, registers 0x62,0x63 of COM2 have values marked for their hard reset (0x00,0x00). In the 'Configuration Register' column, there is a note that these two registers are 'Reserved'.
So, in this type of case should I mark the two registers with their given value, 0x00, or should I use RSVD?
What if the registers were marked with a dash (-) ? Usually I would mark that as NANA, but if it's marked as reserved I assume I should use RSVD instead.
Oh -- and what about the chip rev? Usually there's no given value (because it would change with each chip), so I would mark it MISC, but I believe I saw that other people had marked the chip rev register as NANA. Which is preferable, and why?
Thanks! --Robinson
On Sat, Oct 06, 2007 at 06:50:31PM +0200, Uwe Hermann wrote:
However, we should still give proper credit to all contributors, so maybe we add a THANKS or AUTHORS file (or a section in the README file)?
Opinions?
AUTHORS is good, section in README is fine too.
//Peter
On Sat, Oct 06, 2007 at 10:46:44PM -0400, Robinson Tryon wrote:
Question about registers:
In the datasheet for the FDC37M81x, registers 0x62,0x63 of COM2 have values marked for their hard reset (0x00,0x00). In the 'Configuration Register' column, there is a note that these two registers are 'Reserved'.
So, in this type of case should I mark the two registers with their given value, 0x00, or should I use RSVD?
Either is fine, I guess. So far I let RSVD "override" everything else, i.e. as soon as I see a "Reserved" register, I make it RSVD, even if there's a default value in the datasheet.
What if the registers were marked with a dash (-) ? Usually I would mark that as NANA, but if it's marked as reserved I assume I should use RSVD instead.
Yeah.
Oh -- and what about the chip rev? Usually there's no given value (because it would change with each chip), so I would mark it MISC, but I believe I saw that other people had marked the chip rev register as NANA. Which is preferable, and why?
NANA, because there's no default. MISC would also be possible, but I think NANA is more specific. It's a minor issue, though.
Uwe.
On 06.10.2007 18:50, Uwe Hermann wrote:
On Fri, Oct 05, 2007 at 06:10:36PM -0400, Robinson Tryon wrote:
On 10/5/07, Uwe Hermann uwe@hermann-uwe.de wrote:
On Fri, Oct 05, 2007 at 07:15:02PM +0200, Rasmus Wiman wrote:
Signed-off-by: Rasmus Wiman rasmus@wiman.org
Thanks, committed in r2828 with some very small cosmetic changes. I also added you to the Copyright owner list at the top of the file.
Should I be adding myself to the copyright owner list at the top of the files when I add dump support for chips? I assumed that copying the tables from the datasheets wouldn't be "creative" enough for me to assert a copyright on the commit...
Hm, I think you're right. I acted a bit too fast by adding you to the Copyright header, sorry. However, we should still give proper credit to all contributors, so maybe we add a THANKS or AUTHORS file (or a section in the README file)?
Opinions?
Can we split code/tables to different files? That way, we can make it clear what was copied from data sheets and what was original work.
Besides that, some time in the future part vendors may decide that they don't like parts of their data sheets copied under licenses we decide. The current situation is pretty much a grey area and I'd like to make sure we don't get any cease-and-desist letters for superiotool.
Carl-Daniel
-
Carl-Daniel Hailfinger -
Peter Stuge -
Rasmus Wiman -
Robinson Tryon -
Uwe Hermann -
Ward Vandewege