NDIS6 support for XP?

[Dietmar]

@Mov AX, 0xDEAD

@Damnation makes all ready so I think, that for the i219 only this function is missed.

I tested with these ndis6 files from Longhorn 5048 and this special ntoskrn8.sys some Intel lan drivers,

all work under XP SP3

Dietmar

[Dietmar]

@Mov AX, 0xDEAD

Here are all the for XP SP3 working files from Longhorn 5048 together with the Intel win7 bit32 driver,

thanks to @Damnation

Dietmar

https://ufile.io/22mh6zm7

 

[Mov AX, 0xDEAD]

15 hours ago, Dietmar said:

@Mov AX, 0xDEAD

@Damnation makes all ready so I think, that for the i219 only this function is missed.

I tested with these ndis6 files from Longhorn 5048 and this special ntoskrn8.sys some Intel lan drivers,

all work under XP SP3

Sorry, i don't play with "Binary BLOB" games, ntoskrn8.sys is 2 000 000 bytes, what is inside ? ntoskrnl from win7 ?

[Damnation]

@Mov AX, 0xDEAD @Dietmar

I was doing an experiment merging ntoskrn8.sys with the main kernel, since I wanted to add in extra Zw* functions that make use of internal KiSystemService function.

I don't think this approach worked though.

[Dietmar]

@Mov AX, 0xDEAD @Damnation

Any idea, what I can test for the longstanding problem with i219 for XP?

Now I have 2 days free

Dietmar

[Dietmar]

@Mov AX, 0xDEAD @Damnation

The Intel i211 can be installed as i217 or as i218 under XP SP3.

The same is true under ndis6, works there together with big ntoskrn8.sys

Dietmar

EDIT: Under win7 sp1 bit32, the real i211 network can be installed as i219.

And the real network i219 can be installed as i218.

Edited April 30 by Dietmar

[Dietmar]

@Mov AX, 0xDEAD @Damnation

May be the most easy way to understand what is going on with i219 is to look,

 

why i211, i217, i218 work with Windbg via Lan but i219 not under XP.

 

Because, that lan connection is driver independend

Dietmar

[Mov AX, 0xDEAD]

10 hours ago, Dietmar said:

@Mov AX, 0xDEAD @Damnation

May be the most easy way to understand what is going on with i219 is to look,

why i211, i217, i218 work with Windbg via Lan but i219 not under XP.

Because, that lan connection is driver independend

Try /PCI_ID option, intel driver parse PCI_ID before adapter detection. I was unable to test driver because i don't have MB with intel lan chips

[Dietmar]

@Mov AX, 0xDEAD

"Try /PCI_ID option, intel driver parse PCI_ID before adapter detection."

I want to try this, but I have no idea, how to do this.

So I need help

Dietmar

EDIT: Do you think, that it is something like this? That it is not just a bad joke from Intel, to exclude the i219 from XP,

but just a small hardware change in i219, so that it cant be used under XP because of a wrong setting via i218 for this?

"/PCI_ID - option required for Intel/Broadcom 10Gb/40Gb LAN Controllers (without this option, driver set too small size of memory buffer for 10Gb+ cards)"

Edited May 1 by Dietmar

[Dietmar]

@Mov AX, 0xDEAD

Can you compare the Source code of the

 

e1d5132.sys

driver with the

e1d6232.sys

 

The e1d6232.sys works for all the i211, i217,1218, i219,

but the e1d5132.sys works for all of them, only not for the i219.

So, a change in for example the Cache size would explain this behavior at once

Dietmar

[Dietmar]

@Mov AX, 0xDEAD

Both the i218 and i219 Ethernet controllers have integrated memory caches to improve network performance. However, the size of the cache differs between the two controllers.

The i218 has a 32 KB transmit buffer and a 32 KB receive buffer, which is used to temporarily store data as it is being transmitted or received over the network. This cache size is relatively small compared to other network controllers.

In contrast, the i219 features a larger memory cache with a 256 KB transmit buffer and a 256 KB receive buffer. This larger cache allows the i219 to store more data in memory, which can improve network performance in certain situations, such as when transferring large files or streaming high-bandwidth media.

In addition to the larger cache size, the i219 also features support for Adaptive Interrupt Coalescing (AIC), which is a feature that can help to reduce interrupt processing overhead and improve network performance. AIC works by grouping network traffic into larger packets, which reduces the number of interrupts that the CPU needs to handle.

In summary, while both the i218 and i219 have memory caches to improve network performance, the i219 has a larger cache size and additional features like AIC that can further enhance network performance.

[Dietmar]

@Mov AX, 0xDEAD

May be a look at the Linux Source code and a compare between the i218 and i219 and its differnces shows all,

what we need to do, for to make the i219 run under XP

Dietmar

[Dietmar]

@Mov AX, 0xDEAD

I found this for Linux, when the i218 works there but the i219 not:

The NVM Checksum Is Not Valid

I have found Intel's datasheet for I219, Section 10.3.2.2 Checksum Word Calculation says:

The Checksum word (Word 0x3F, NVM bytes 0x7E and 0x7F) is used to ensure that the base NVM image is a valid image. The value of this word should be calculated such that after adding all the words (0x00- 0x3F) / bytes (0x00-0x7F), including the Checksum word itself, the sum should be 0xBABA. The initial value in the 16 bit summing register should be 0x0000 and the carry bit should be ignored after each addition.

Dietmar

pdf datasheet for the i219

https://ufile.io/72w6bumg

Edited May 1 by Dietmar

[Dietmar]

@Mov AX, 0xDEAD

Now I have working Lan Debug for the i211 .

But until now no idea, how I can make Lan Debug work for the i219.

Can you send me the files which may help and a step by step instruction

Dietmar

EDIT: I get Lan debug on the i219 to work under XP SP3 on both compis with this boot.ini

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /DEBUG /DEBUGPORT=NET /HOST_IP=192.168.2.101 /HOST_PORT=50000 /ENCRYPTION_KEY=1.2.3.4 /CPUFREQ=3000 /TARGET_IP=192.168.2.103 /BREAK /PCI_ID=808615B8

 

But the most most crazy is, that I need all of this 3 files for Lan Windbg on XP SP3 on both compis and Intel i219

kdnet10.dll    from win10         10.0.19041.1 (WinBuild.160101.0800)

kdnet.dll        from win8.1        6.3.9600.17276 (winblue_r2.140808-0433)

kdstub.dll      (3.328 Bytes only)

I cant believe, so I check several times, always the same.

One file of those 3 not in Windows\system32 folder, no Lan Windbg via i219.

https://ufile.io/z7t4usd4

 

 

Edited May 1 by Dietmar

[Mov AX, 0xDEAD]

1 hour ago, Dietmar said:

@Mov AX, 0xDEAD

Can you send me the files which may help and a step by step instruction

I dont have any new files, kdnet is not updated since 2021 because i don't found bugs, just need take kdnet10.dll from last Windows 10 releases if need support for some new chipsets

1 hour ago, Dietmar said:

But the most most crazy is, that I need all of this 3 files for Lan Windbg on XP SP3 on both compis and Intel i219

kdnet10.dll    from win10         10.0.19041.1 (WinBuild.160101.0800)

kdnet.dll        from win8.1        6.3.9600.17276 (winblue_r2.140808-0433)

kdstub.dll      (3.328 Bytes only)

This is as should be, kdnet based on windows10 files requires 3 files, check with DepWalker, they linked together. kdstub.dll is little converter between Windows8.1 API <->Windows10 API

 

kdstub.c

Edited May 1 by Mov AX, 0xDEAD