Debugging Guide

Wikis > MultiMac NIC Drivers > Debugging Guide

Debugging Guide

Known Issues

  • MultiMac drivers (except NVETH, E1000E, and R8169) are built from 2 major pieces:
    1. The FreeBSD driver which is simply compiled to run on OS/2
    2. The system library which is the interface between the FreeBSD driver and OS/2

    While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn’t work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn’t work properly on your hardware because we don’t have the hardware data that would be required.

    Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn’t work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver.

  • The interface speed shown by the “netstat -n” command always shows 100000000 regardless of the actual interface speed. This is because of an incompatibility between the way that the FreeBSD driver reports the interface status and the way (and when) OS/2 requires this information. This may get fixed eventually, but for now this is the way it is.

Before Opening a Ticket

Things to check before opening a ticket if you have problems

  • Make sure your issue is not listed in the Known Issues section above.
  • Make sure you are using the latest version of a supported driver. Only drivers distributed by Arca Noae are supported. The E1000E, R8169, and any other builds from other sources are not supported.
  • Make sure you are using an official supported kernel. Only the official IBM 14.104a debug, 14.105, 14.106, and the Arca Noae 14.104b, 14.200, and 14.201 kernels are supported.
  • Make sure you are using an official supported loader for the kernel you are using.
  • If you have ACPI.PSD installed, make sure it is the latest version and that you are not using any unnecessary switches. Recent versions of the MultiMac drivers will not work with ACPI.PSD older than 3.23.04 and may cause traps.
  • Make sure you don’t have any load order violations in your CONFIG.SYS. Specifically make sure that all IFS statements come before all MAC drivers.

If you open a ticket, please attach a TestLog log file when you open your ticket. Always make sure you capture the TestLog log file when the problem exists. If you cannot create a TestLog log, at a minimum you must include the bldlevel output for the driver you are using. Also, include the PCI Vendor ID and Device ID of your hardware in the ticket (ie. the section from PCI.EXE that relates to your NIC). If the driver traps, please, include the trap screen.

Capturing A TestLog log file

If you don’t already have the current version of the TestLog program, you can download it here: Get TestLog

Open a command window and execute the testlog command for your particular driver. For example:

testlog network

Attach the created log file to your ticket. Do not ZIP the log file. Always make sure you capture the TestLog log file when the problem exists.

Installing the Trace Version of the Driver

Only some older drivers have trace versions. Newer drivers do not have trace version so this section does not apply. To install the trace version, run the Warpin installation and select both packages.

To re-install the normal version, run the Warpin installation and uninstall the trace package and reinstall the retail package.

To enable tracing, add these two lines to your CONFIG.SYS:

  TRACEBUF=512 /M=NOWRAP,QUEUED,NODTI /D=ALL
  TRACE=ON 248

You must reboot to make the new driver active and enable tracing. This assumes that you have already setup this driver using NAPS (or mpts.exe). You do not need to setup the driver using NAPS (or mpts.exe) more than once, even if you install new versions of the driver. You just need to reboot to start using the new version.

Capturing the Trace

To capture the trace dump, open a command window and type:

TRACEFMT

From the file menu choose Save Formatted… and save the trace to a file of your choice.