VOGONS


Reply 681 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie

I noticed SIV did not have support for S3 Savage3D (86C390+86C391) GPUs so I added it for SIV 5.53 Beta-02.

If you have an S3 Savage3D please post Menu->Machine->GPU Info so I can check the correct clock speeds are reported.

Reply 682 of 806, by grey_beard

User metadata
Rank Newbie
Rank
Newbie

Just a quick question from my side:

Is there a section for IrDA somewhere in SIV as it's quite common on old machines?

I would have expected to find it somewhere in the Network section but couldn't find anything. Would be interested in what speeds etc. are supported on my hardware.

Reply 683 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
grey_beard wrote on 2020-11-20, 20:58:

Is there a section for IrDA somewhere in SIV

Thank you for your post. SIV checks for GUID_DEVINTERFACE_IRPORT devices and it it finds any then there should be Menu->System->ACPI + PnP->IR Ports, is it there please?

For 5.54 Beta-02 I will change the name to ->IRDA Ports and will add Menu->Network->IRDA Ports.

Have you found Menu->Help->View Menus?

Reply 684 of 806, by grey_beard

User metadata
Rank Newbie
Rank
Newbie
red-ray wrote on 2020-11-20, 21:33:

Thank you for your post. SIV checks for GUID_DEVINTERFACE_IRPORT devices and it it finds any then there should be Menu->System->ACPI + PnP->IR Ports, is it there please?

Unfortunately "IR Ports" doesn't show up in that menu, although the port itself is working fine and shows up in the windows device manager. Just used it a few weeks ago to sync an old Palm device.

I'm running SIV on Windows 10 N (32-Bits) on an old Thinkpad X60s.

Reply 685 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
grey_beard wrote on 2020-11-21, 12:57:

Unfortunately "IR Ports" doesn't show up in that menu, although the port itself is working fine and shows up in the windows device manager. Just used it a few weeks ago to sync an old Palm device.

I'm running SIV on Windows 10 N (32-Bits) on an old Thinkpad X60s.

I would expect it to show up on W10 and should be on Menu->System->Interfaces as below.

To really know why it's not I would need you to do Menu->File->Save Local and post the two files that are generated.

Attachments

  • Winbond CIR Transceiver.png
    Filename
    Winbond CIR Transceiver.png
    File size
    93.73 KiB
    Views
    525 views
    File comment
    Winbond CIR Transceiver
    File license
    Public domain

Reply 686 of 806, by grey_beard

User metadata
Rank Newbie
Rank
Newbie

Nope, the port doesn't show up in the interfaces menu, instead it shows up in the list of "ACPI Devices" as to be seen in the screenshot attached. It's the "IBM ThinkPad Fast Infrared Port" right at the bottom.

The report you were asking for is also attached.

Attachments

  • Filename
    SIVReports.zip
    File size
    317.37 KiB
    Downloads
    15 downloads
    File license
    Fair use/fair dealing exception
  • ACPI Devices.png
    Filename
    ACPI Devices.png
    File size
    19.67 KiB
    Views
    520 views
    File license
    Public domain

Reply 687 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
grey_beard wrote on 2020-11-21, 14:00:

Nope, the port doesn't show up in the interfaces menu

I know why and don't think there is much I can do about this. It's using the National 6.0.6001.18000 driver which looks like it fails to expose the GUID_DEVINTERFACE_IRPORT interface. Looking at Menu->System->DOS Devices I found:

ACPI#IBM0071#4&224b442a&0#{ad498944-762f-11d0-8dcb-00c04fc3358c} \Device\00000028
ACPI#IBM0071#4&224b442a&0#{cac88484-7515-4c03-82e6-71a87abac361} \Device\00000028

{cac88484-7515-4c03-82e6-71a87abac361} is GUID_DEVINTERFACE_NET and {ad498944-762f-11d0-8dcb-00c04fc3358c} is GUID_NDIS_LAN_CLASS neither of which identify the device as IRDA 🙁 On systems where SIV finds IRDA devices there is such as:

ACPI#WEC1022#1#{064f8c82-77b2-445e-b85d-c4e20f942fe1} \Device\00000022

{064f8c82-77b2-445e-b85d-c4e20f942fe1} is GUID_DEVINTERFACE_IRPORT .

On the plus side I was pleased to see SIV automatically detected five ACPI motherboard temperature sensors 😀

I have now released SIV 5.54 Beta-02 which should list your IRDA device as a Net device on Menu->System->Interfaces, does it please?

Last edited by red-ray on 2020-11-22, 16:18. Edited 1 time in total.

Reply 688 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie

From SIV 5.54 Beta-02 SIV should report all three fans on EVGA RTX 3080 + 3090 + all FTW3 GPUs, but I have only tested this on my EVGA RTX 3080 XC3 Ultra. If you have an EVGA RTX 3080, 3090 or FTW3 GPU please will you check if SIV reports all three fans and post the Menu->Machine->GPU Info panel. If only two fans are reported also post Menu->Machine->GPU I2C which should enable to to add the third fan.

file.php?id=96777

Note that currently SIV is only able to report all three fans for EVGA GPUs.

Attachments

  • EVGA [GPU I2C] panel.png
    Filename
    EVGA [GPU I2C] panel.png
    File size
    43.34 KiB
    Views
    508 views
    File comment
    EVGA [GPU I2C] panel
    File license
    Public domain
  • EVGA Fan 3 reporting.png
    Filename
    EVGA Fan 3 reporting.png
    File size
    95 KiB
    Views
    508 views
    File comment
    SIV reporting 3 fans on an EVGA RTX 3080 XC3 Ultra
    File license
    Public domain

Reply 689 of 806, by grey_beard

User metadata
Rank Newbie
Rank
Newbie
red-ray wrote on 2020-11-21, 14:53:

I have now released SIV 5.54 Beta-02 which should list your IRDA device as a Net device on Menu->System->Interfaces, does it please?

Yes it shows up between the "Net" devices as "Infrared-5".

Attachments

  • Infrared-5.png
    Filename
    Infrared-5.png
    File size
    58 KiB
    Views
    490 views
    File license
    Public domain

Reply 690 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
grey_beard wrote on 2020-11-22, 20:34:

Yes it shows up between the "Net" devices as "Infrared-5".

Ah, I had not spotted the class was Infrared. I could use that to detect it, but given it's not GUID_DEVINTERFACE_IRPORT I expect it won't support IOCTL_IR_GET_DEV_CAPS so even if I used the class being Infrared then the IOCTL_IR_GET_DEV_CAPS would probably fail anyway.

I have built the attached SIV322X 5.54 IRDA-03 test SIV, would you like to try it and report what gets reported?

IOCTL_IR_GET_DEV_CAPS definition
// Module Name:
//
// irclass_ioctl.h
//
// Abstract:
//
// This module contains the IOCTL definitions for the WDF IRCLASS class driver
//
#define FILE_DEVICE_IRCLASS 0x0F60


#define IOCTL_IR_GET_DEV_CAPS CTL_CODE(FILE_DEVICE_IRCLASS, \
1, \
METHOD_BUFFERED, \
FILE_READ_ACCESS)
Last edited by red-ray on 2020-11-23, 16:01. Edited 1 time in total.

Reply 691 of 806, by grey_beard

User metadata
Rank Newbie
Rank
Newbie
red-ray wrote on 2020-11-22, 20:56:

I have built the attached SIV322X 5.54 IRDA-03 test SIV, would you like to try it and report what gets reported?

It reports "Unzulässige Funktion" which I would translate into "illegal operation".

Attachments

  • Filename
    IRDA.PNG
    File size
    8.82 KiB
    Downloads
    No downloads
    File license
    Public domain

Reply 692 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
grey_beard wrote on 2020-11-23, 15:47:

It reports "Unzulässige Funktion" which I would translate into "illegal operation".

file.php?id=96867

Thank you for checking it out, this is what I was expecting and in the header file Status 1 is as below.

I feel I should leave the code there so the IRDA port is at least listed on Menu->Network->IRDA Ports, what do you think please?

// MessageId: ERROR_INVALID_FUNCTION
//
// MessageText:
//
// Incorrect function.
//
#define ERROR_INVALID_FUNCTION 1L // dderror

Reply 694 of 806, by RichardG867

User metadata
Rank Newbie
Rank
Newbie

SIV (and just about any other tool) doesn't read SPD and other SMBus data from the SMSC SLC90E66, a rare southbridge that mostly mimics the PIIX4 (apparently with Intel's blessing). It has the same function layout as the PIIX4, and according to the datasheet (p. 149-154) and the Linux kernel (l. 785), the same SMBus controller located in the power management function, which has a PCI ID of 1055:9463.

Attachments

  • 20201211-201204-237.png
    Filename
    20201211-201204-237.png
    File size
    43.01 KiB
    Views
    398 views
    File license
    Fair use/fair dealing exception

Reply 695 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
RichardG867 wrote on 2020-12-11, 20:13:

PCI ID of 1055:9463.

Thank you for the report and links to the datasheet. Please try SIV 5.54 Beta-08 or later, check if SIV finds the SMBus and it works, if not post [PCI Bus].

Can you also post the two Menu->File->Save Local files as I suspect I will need to made some changes to the PCI device reporting for the SLC90E66.

Reply 696 of 806, by RichardG867

User metadata
Rank Newbie
Rank
Newbie
red-ray wrote on 2020-12-13, 09:47:

Thank you for the report and links to the datasheet. Please try SIV 5.54 Beta-08 or later, check if SIV finds the SMBus and it works, if not post [PCI Bus].

Can you also post the two Menu->File->Save Local files as I suspect I will need to made some changes to the PCI device reporting for the SLC90E66.

The new build now detects SMBus and SPD. A report is attached, with a few caveats:

1) I went with the "Public" set because I wasn't keen on including IP and geolocation information.
2) I've unchecked the "msrs" section, because this is running in an emulator which doesn't like the way SIV probes MSRs (BSOD caused by a RDMSR GPF once it gets to MSR 8C). I'm investigating the matter.
3) SIV only detects SPD for 1 of the 4 RAM sticks (even though SMBus probing detects all 4 SPD devices) but this could be another emulation issue. Other anomalies like CPU cache latency and AGP Voodoo3 on PCI can be attributed to emulation as well.

Attachments

  • Filename
    SIV_86BOX-D3C3B359D.zip
    File size
    167.76 KiB
    Downloads
    13 downloads
    File license
    Fair use/fair dealing exception

Reply 697 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
RichardG867 wrote on 2020-12-14, 20:12:
[…]
Show full quote
  1. I went with the "Public" set because I wasn't keen on including IP and geolocation information.
  2. I've unchecked the "msrs" section, because this is running in an emulator which doesn't like the way SIV probes MSRs (BSOD caused by a RDMSR GPF once it gets to MSR 8C). I'm investigating the matter.
  3. SIV only detects SPD for 1 of the 4 RAM sticks (even though SMBus probing detects all 4 SPD devices) but this could be another emulation issue. Other anomalies like CPU cache latency can be attributed to emulation as well.

Thank you for the report and SIV worked much as I expected. After a quick check all the issues are down to the emulation. SIV is designed to work on real hardware and in general makes emulators work hard.

  1. OK
  2. I expect the root cause of this is down to bugs in your emulator as SIV always reads MSRs within a _try{}_except(){} block. Do you need to know anything more for you to fix this?
  3. This is down to there being no SMBIOS. As SIV reads the SPD after the main screen popup it reads the number on DIMMs from the SMBIOS to know how to layout the panel, but as none were reported forced the minimum of one. Do SIV32X -DIMMS=4 and SIV should report all four sets of SPD.
  4. The CPUID data returned is less than it should be for a Pentium II, for openers there needs to be the cache information.
  5. Most of the MSRs that should be returned are absent, SIV would have tried to read quite a lot of MSRs so your emulation can't be that wonky.
  6. Below is what a real Pentium II (Deschutes) would return.
Menu->Hardware->CPUID->CPU-0 for a real Pentium II (Deschutes)
[CPUID CPU-0] <- SIV32X - System Information Viewer V5.55 Beta-00 RETRONATER::GiSWiG

CPU-0 Intel Pentium II (Deschutes) 401MHz [dA1] STK 400.779MHz CPU 400.779MHz FSB 100.195MHz L2 200.389MHz WIN 400.000MHz

[Y]CPUID EAX EBX ECX EDX
00000000 00000002 756E6547 6C65746E 49656E69 [Y]"GenuineIntel"
00000001 00000651 00000000 00000000 0183F9FF [_]09 APIC 0x00 [_]16 Count 0 [Y]15 CMOV [Y]08 CX8 [Y]04 TSC [Y]03 PSE
00000002 03020101 00000000 00000000 0C040843 [Y]43 L2U 4-way 32-byte 512KB [Y]08 L1C 4-way 32-byte 16KB
[Y]0C L1D 4-way 32-byte 16KB

40000000 03020101

80000000 03020101

80860000 03020101

C0000000 03020101

00005A4E 03020101 00000000 00000000 0C040843 [Y]"____C___________"

8FFFFFFF 03020101 00000000 00000000 0C040843 [Y]"____________C___"

POIS 00000001 0000E410 6. 00000000 PROCESSOR_OBJECT_INFO [CPU0] \Device\00000033 ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_5\_0

[Y]MSR EDX EAX Thermal 00000000 [_]16 TSCIV [_]17 SLAT [Y]00 Flags 0000000000208002
00000017 2000A0A3 E06531E3 PLATFORM_ID [Y]59 Multiplier 04 [_]57 [ES] 0 50 Socket 0 [_]56 TDP 0.0 Watt [_]27 [ES] [_]08 Ratio x0
0000001B 00000000 FEE00100 APIC_BASE [_]11 APIC Disabled [_]10 x2APIC Disabled [_]09 Reserved [Y]08 Boot CPU
0000002A 00000000 C4880000 EBL_CR_POWERON [_]20 Arbitration 00 [_]16 APIC ID 00 [Y]Cur 02 (x4) [Y]Max 00 (x5) FSB 02 (100MHz)
0000008B 00000040 00000000 BIOS_SIGN_ID [Y]32 Revision 0040 (Intel+VIA) [_]00 Revision 0000 (AMD)
000000C1 00000000 00000000 IA32_PMC0
000000C2 00000000 00000000 IA32_PMC1
0000011E 00000000 0134450F BBL_CR_CTL3 [Y]23 L2 Present [Y]08 Initialised 4GB [Y]01 Latency 7 [Y]00 L2 Enabled
00000179 00000000 00000005 MCG_CAP [_]24 SERP [_]16 EXT_CNT 0 [Y]00 MCG_CNT 5 [_]11 TESP [_]10 CMCP [_]09 EXTP [_]08 CTLP
00000186 00000000 00000000 PERFEVTSEL0
00000187 00000000 00000000 PERFEVTSEL1
00000150 00000000 00000000 IA32_OC_MAILBOX [_]Core Rank 0 x0 [_]CPU 400.78 MHz + 400.78 MHz + 100.19 MHz

[ OK ] [ Copy] [Windows] [Processors][Features] [Groups] [ NUMA] [ CPU-0] [Cache-0]

Reply 698 of 806, by RichardG867

User metadata
Rank Newbie
Rank
Newbie

Thanks for the attention.

red-ray wrote on 2020-12-14, 21:17:

I expect the root cause of this is down to bugs in your emulator as SIV always reads MSRs within a _try{}_except(){} block. Do you need to know anything more for you to fix this?

Don't really need any more information, this is being investigated, reading MSRs like this should definitely not BSOD.

red-ray wrote on 2020-12-14, 21:17:

This is down to there being no SMBIOS. As SIV reads the SPD after the main screen popup it reads the number on DIMMs from the SMBIOS to know how to layout the panel, but as none were reported forced the minimum of one. Do SIV32X -DIMMS=4 and SIV should report all four sets of SPD.

That parameter worked. I'm aware SMBIOS is quite dodgy on older machines.

red-ray wrote on 2020-12-14, 21:17:

The CPUID data returned is less than it should be for a Pentium II, for openers there needs to be the cache information.
Most of the MSRs that should be returned are absent, SIV would have tried to read quite a lot of MSRs so your emulation can't be that wonky.

This is meant to be a Mendocino Celeron, so there is indeed a lot of information missing.

red-ray wrote on 2020-12-14, 21:17:

Below is what a real Pentium II (Deschutes) would return.

Thanks for the report. I also have a real Deschutes CPU to test with.

Reply 699 of 806, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
RichardG867 wrote on 2020-12-14, 22:38:

This is meant to be a Mendocino Celeron, so there is indeed a lot of information missing.

When I looked some more at the save file I noticed that MSR 0000001B is returned as zero and as this is the APIC base it should never be zero. As a result of this SIV did not even try to read any of the other MSRs as it deduced the CPU was not a real CPU and therefore unlikely to return anything useful in the MSRs. Which MSRs are implemented?

Your Intel 82443BX 440BX Chipset PCI to AGP Bridge - Vendor ID 8086-7191 is incorrect as 0F to 17 are reserved and should be zero. The values present result in impossible BAR 0 settings.

[0 - 01 - 0] <- [PCI Bus] <- SIV32X - System Information Viewer V5.55 MSRs-00 86BOX-D3C3B359D::Administrator

Intel 82443BX 440BX Chipset PCI to AGP Bridge - Vendor ID 8086-7191-00000000-02 size 0100

Device Class 0x060400 PCI Bridge
Command 0x0107 I/O Access Memory Access Bus Master System Errors
Status 0x0220 Medium Timing Supports 66MHz Speed

[Y]Cache Line Size 8 2 ULONGs Latency Timer 8 PCI clocks
[_]Header Type 0x01 Prof IF 0x00 Built-in Self Test 0x00

BAR 0 (255.97TB) [0xFFF80000FFF0] Alignment 0x00000010 16 ( Anywhere in 64-bit space, Prefetchable )

Primary Bus # 0 Control 0x00 Controls Enabled
Secondary Bus # 1 Status 0x02A0 Supports 66MHz Speed Fast Back-to-Back
Subordinate Bus # 1 Latency 32 Address Ranges beyond Bridge

0 4 8 C 0 2 4 6 8 A C E
000: 71918086 02200107 06040002 00014008 :00C 000: 8086 7191 0107 0220 0002 0604 4008 0001 :00E
010: 0000FFFC 0000FFF8 20010100 02A000F0 :01C 010: FFFC .... FFF8 .... 0100 2001 00F0 02A0 :01E
020: 0000FFF0 0000FFF0 00000000 00000000 :02C 020: FFF0 .... FFF0 .... .... .... .... .... :02E
030: 00000000 00000000 00000000 00000000 :03C 030: .... .... .... .... .... .... .... .... :03E
040: 00000000 00000000 00000000 00000000 :04C 040: .... .... .... .... .... .... .... .... :04E
050: 00000000 00000000 00000000 00000000 :05C 050: .... .... .... .... .... .... .... .... :05E
060: 00000000 00000000 00000000 00000000 :06C 060: .... .... .... .... .... .... .... .... :06E
070: 00000000 00000000 00000000 00000000 :07C 070: .... .... .... .... .... .... .... .... :07E
080: 00000000 00000000 00000000 00000000 :08C 080: .... .... .... .... .... .... .... .... :08E
090: 00000000 00000000 00000000 00000000 :09C 090: .... .... .... .... .... .... .... .... :09E
0A0: 00000000 00000000 00000000 00000000 :0AC 0A0: .... .... .... .... .... .... .... .... :0AE
0B0: 00000000 00000000 00000000 00000000 :0BC 0B0: .... .... .... .... .... .... .... .... :0BE
0C0: 00000000 00000000 00000000 00000000 :0CC 0C0: .... .... .... .... .... .... .... .... :0CE
0D0: 00000000 00000000 00000000 00000000 :0DC 0D0: .... .... .... .... .... .... .... .... :0DE
0E0: 00000000 00000000 00000000 00000000 :0EC 0E0: .... .... .... .... .... .... .... .... :0EE
0F0: 00000000 00000000 00000000 00000000 :0FC 0F0: .... .... .... .... .... .... .... .... :0FE

[ OK ] [ Copy] [ First] [ Prev] [ This] [ Next] [ Last] [Dump PCI]