dgerror.txt Driver File Contents (Lan.zip)

CONTENTS
========

1	Overview
2	Error Code Description

=============================================================================


(1) OVERVIEW
============


For each test the error messages are grouped. But it may be, that some
error codes may also occur while executing a different test, because
some tests are subsets of some other tests.

***

(2) ERROR CODE DESCRIPTION
==========================


'O': ASIC register check

100     - Error occurs while reading/writing PCI Configuration
          registers with PCI config cycles.
          The ASIC may be defective or not correctly soldered.
101     - Error occurs while reading/writing ASIC Registers with
          I/O cycles.
          The ASIC may be defective or not correctly soldered.
102     - MAC Address consistency check fails. The MAC addresses
          may not be programmed correctly.

103 ... 109	reserved

'X': MAC reg check

110     - Error occurs while reading/writing to the MAC registers.
111     - Error occurs while reading/writing to the PHY registers.
112     - Unexpected PHY type detected. The configuration data may be
          invalid or damaged.
113     - PHY ID does not comply with expected one.
114     - PHY IRQ check error. IRQ on external register is active
          although not enabled.
115     - PHY IRQ check error. IRQ on external register does not occur
          although it was forced.
116     - PHY IRQ check error. IRQ on external register still active
          although it was released.
117     - PHY IRQ check error. PCI Rev. 2.3 IRQ does not occur
          although enabled.
118	- Software IRQ check error. PCI Rev. 2.3 IRQ does not occur
          although enabled.

119	reserved

't': Timer & HW-IRQ

120 ... 129	reserved

'g': Counter Check

130 ... 139	reserved

'r': RAM check over RAM random access register

140     - Error occured when Reading the RAM Random register
          (RAM or ASIC defective)
141     - Error occured when checking RAM via Register
          (RAM defective)

142 ... 159	reserved

'f': DMA fragment check

160     - Fragment compare failure. Data has been corrupted
          while performing the DMA fragment check. This test is
          performed in ASIC loopback. The RAM and the ASIC
          may be defective or not correctly soldered.
161     - Timed out waiting for packet.
162     - Status burst does not burst all expected list elements.

163 ... 199	reserved

'M': Data transfer rate

200     - Transmit hungs during descriptor poll (timeout)
201     - Receive hungs during descriptor poll (timeout)
202     - Transmit hungs during descriptor poll in last loop (timeout)
203     - Receive hungs during descriptor poll in last loop (timeout)
204     - General timeout when trying to clear the last descriptors
205     - Memory compare failure.

206 ... 249	reserved

'F': Flash PROM check

250 ... 255	reserved
256     - Flash cannot be programmed with all zeros
257     - Flash cannot be erased before programming
258     - Flash cannot be programmed
259     - DATA verify error

260 ... 299	reserved

'y': Loopback tests AND 'j': Rx/Tx jumbo frames

300     - Receive Descriptor Check failed. These messages may
          appear along with this error code:
            "STF not set",
            "EOF not set",
            "RFSW not valid",
            "RFSW not looped",
            "Error in RFSW", and
            "wrong length"

301     - Data compare error after loopback test.
302     - Testpattern has been overridden after loopback test.
303     - No packets has been received during loopback test.
          The chips which may be defective or not corretly
          soldered depends from the loopback mode.
          ASIC Loopback:         RAM, ASIC
          MAC Loopback:          RAM, ASIC, XMAC
          PHY Loopback:          RAM, ASIC, XMAC, PHY
          Wrap Plug Loopback:    RAM, ASIC, XMAC, PHY, SERDES,
                                 ODL, Wrap Plug
          Port to Port Loopback: RAM, ASIC, XMAC, PHY, SERDES,
                                 ODL, Wrap Plug	

304     - Timestamp timer does not count properly.
305 ... 399	reserved

'R': Rate Control Test

400     - Frame Transmit Timeout occured
401     - Rate Control Parameter Config Error occured	
402     - Error occured while testing Rate Control       (Test Mode 1)
403     - Error occured while testing 'Enable Alloc' Bit (Test Mode 2)
404     - Error occured while testing 'Force Sync' Bit	 (Test Mode 3)

405 ... 409	reserved

'k': TCP checksum test

410     - RxD missing. Frame reception not complete.
411     - CheckSums are different. The TCP checksum provided
          by the ASIC does not match the calculated checksum.
412     - Data compare error.
413     - Status burst occurred but not all expected list elements were
          written.

414 ... 429	reserved

'n': Autonegotiation

430 ... 449	reserved

'I': I2C and VPD

     o VPD Tests
450     - General VPD Error: Before starting VPD test the
          VPD data will be read and save into a buffer
          to restore them later. This first read access fails.
          If this error occurs the VPD EEPROM may be
          defective or not present.
451     - VPD ROM Size check failed: This test checks if the
          size of the VPD EEPROM matches the VPD PROM size
          programmed in the FPROM. Either a wrong VPD EEPROM
          is manufactured or the Boot PROM data are not
          correct.
452     - Programming the Read/Write Area failed:
          The VPD EEPROM may be defective.
453     - Try to overwrite Read Only Area succeeds:
          The VPD EEPORM seems to be ok, but
          the Boot ROM data may be incorrect.
454     - Programming the Read Only Area in test mode failes.
          The VPD EEPORM may be defective.
455     - Unable to read VPD data.
          The VPD EEPORM may be defective.

456 ... 459	reserved

     o I2C HW Register Tests
460     - An error occured during the initialization of the I2C module.
          May be a started I2C transfer does never complete.
461     - The sensor value is outside the limits. May be the system
          is defective.
462     - The value read from the LM80 are all '0xff'. This means
          the sensor does not answer to the ASICs request.
          The sensor is disconnected or seems to be defective.
463     - The I2C ready IRQ does never occur or occurs to early.
464     - The IRQ on external register (IRQ from LM80) does
          not occur. The IRQ line between ASIC and LM80
          may be interrupted.
465     - An IRQ on external register does occur although the LM80
          does not generate it. Check that the IRQ line between
          ASIC and LM80 is not connected anywhere else.
466     reserved

     o I2C SW Register Tests
467     - No acknowledge from LM80. May be the LM80 is defective or
          not present.
461     - The sensor value is outside the limits. May be the system
          is defective.
462     - The value read from the LM80 are all '0xff'. This means
          the sensor does not answer to the ASICs request.
          The sensor is disconnected or seems to be defective.
468     reserved

'l': LED on/off (wait 1s)

470     - The user has decided that the LED test has been failed.

471 ... 499	reserved

'i': Special tests

     o PCI Parity Tests

500     - Force Dataperr on next master read failed.
501     - Force Dataperr on this target write failed.
502     - Force AddrPerr on next target access failed.
503     - Force Dataperr on next 64 bit master read failed.
504		reserved
505     - The PCI parity test which has been selected by the
          user failed.

506 ... 510	reserved

     o RAM Parity Tests

511     - Parity Error on RAM read does not occur (Not testable)
512     - Parity Error on RAM write does not occur (Not testable)

513 ... 514 reserved

     o DEV_0 test

515     - BMU DEV_0 test failed

     o DIS_CRC test

516     - Disable CRC test failed

517 ... 519 reserved

     o Time Stamp Test

520     - TimeStamp Sequence Error
521     - TimeStamp Timeout IRQ does not occur

522 ... 569 reserved

     o Power Management Tests
570     - Pattern RAM test failed
571     - Failed to reset WOL Ctrl register
572     - Unexpected behaviour of WOL Ctrl register
573     - Unexpected behaviour of WOL Ctrl register
574     - Detection of AMD Magic Packet failed
575     - The adapter is not connected to Vaux power
576     - Filed to reset PME function in PCI config space
577     - Failed to set PME function in PCI config space
578     - Failed to start adapter in power management test
579     - Failed to detect pattern match for WOL
580     - Failed to detect link change for WOL

581 ... 589	reserved

590     - Power Management Capability test failed
591     - Power Management Data test failed

592 ... 599	reserved

     o Echo Test 'e'

600     - corrupted packets received
601     - packets received out of order
602     - packets lost

603 ... 619 reserved

     o Multicast Test 'x'

620     - the adapter did not receive a frame the filter was
          configured for
621     - timeout during Loopback

622 ... 624	reserved

     o RSS Hash Test 'H'
625     - Hashes don't match

626 ... 629 reserved

     o Truncate test 't'
630     - Received packet not truncated
631     - No packet received

632 ... 635 reserved

     o LE opcodes and Sw IRQ generation '1'
635     - SW IRQ generation failed.
636     - No IRQ was generated for bad opcode.
637     - Unexpected IRQ generated

638 ... 699 reserved

     o Yukon 2 register test

700     - Register default value (after reset) is incorrect.
701     - Write a bit defined as writeable failed.
702     - A read only bit has been written successfuly.

703 ... 799 reserved

     o Link Test 'n'

800     - The link partner has signaled a port configuration
          although auto-negotiation is disabled at the
          local device. This is not possible.
801     - Duplex mismatch. The resolved duplex mode does not match
          the expected duplex mode.
802     - Frame transmission and link creation expected.
          But either the link was not coming up or no
          frames has been transmitted.
803     - The link has been coming up although a duplex mode
          combination has been configured where link generation
          is impossible.
804     reserved
805     - The Link Partner has sent pause frames although sending
          pause frames was not negotiated for the remote station.
806     reserved
807     - The Local Station has sent pause frames although sending
          pause frames was not negotiated for the local station.
808     - Sending pause frames has been negotiated for the
          local station and traffic has been generated on the
          receive side to force sending pause packets but
          the local station does not send any pause frames.
809     reserved
810     - The real master / slave resolution does not match the
          expected one.
811     reserved
812     - The link has been coming up although the configured
          master / slave resolution prevents link generation.
813 ... 814	reserved
815     - Remote fault mismatch. The remote fault bits signaled
          by the local port are not correctly received at
          the link partner.
816       Unexpected autonegotiation done event.
817       Next page capability not signaled.
818       Next page request missing.
819       Received next page was not the expected once.

     o ASF Test 'A'
820     - ASF packet not received. Time out occurred.
821     - Unexpected pattern matched the ASf packet.
822     - Wrong frame size of ASf packet
823     - Data comparison failed
824     - Timeout while running a ASF CPU Test.
825 ... 849 reserved

     o Repeater Mode 'Y'
850     - STF / EOF sequence error. Receive Frame too long.	

     o Flush Test 'u'
860     - No packet received with threshold below packet size.
861     - The packet was not flushed as expected.

862 ... 899 reserved

     o TCP Segmentation 'T'
900     - Time out waiting for segment
901     - Wrong segment/packet size
902     - ACK bit not properly handled by TCP segmentation engine
903     - URG bit not properly handled by TCP segmentation engine
904     - PSH bit not properly handled by TCP segmentation engine
905     - RST bit not properly handled by TCP segmentation engine
906     - FIN bit not properly handled by TCP segmentation engine
907     - IP header checksum wrong
908     - TCP header checksum wrong
909     - Ethernet headers differ
910     - Some IP header fields were changed
911     - Some TCP header fields were changed
912     - Segment payload corrupted/Packet data corrupted
913     - Wrong sequence number
914     - Wrong ID field

915 ... 949	reserved

Common Error Messages:
     This error messages may appear during several tests.

950     - Link Up Timeout: The diagnostics utility was unable
          to create a link and to finish the auto-negotiation
          process sucessfully. This message may appear during
          the tests 'y', 'k', 'n' and 'N'. The wrap plug may
          be missing, the ODL or SERDES by be defective.
951     - RAM Queue Size configuration error. The user has
          configured an invalid RAM queue configuration, using
          the 'QSizexxxx' parameters.
952     - Timeout during Fragment Transfer: may be returned
          during 'f' or 'k' test. The descriptors has not
          been returned by the adapter.
954     - Serious Hardware Error occured: this error code
          comes together with one of the follwing messages:
            "Error: Interrupt Status Exception"
            "Error: Unexpected IRQ Master error"
            "Error: Parity error on RAM (read)"
            "Error: Parity error on RAM (write)"
            "Error: Parity error MFF Port A"
            "Error: Parity error MFF Port B"
            "Error: Parity error RX 1"
            "Error: Parity error RX 2"
          The ASIC or the RAM may be defective or not
          correctly soldered.
955     - The PHY (copper only) does not support wrap plug loopback
          mode. This mode is supported by:
              Yukon Plus
              Yukon 2 (EC and XL)
956     - Descriptor/list element initialization ran out of memory.
957     - Open file failed. Please check if the file with the given
          name exists.
958     - Empty or invalid filename.
959 ... 999	reserved
***


*** End of File ***
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web3, load: 1.98