Mod for the Intel Lan driver i218-LM v3

[Dietmar]

Hi, I just notice, that some hacks for the i218 exist,

but no one for the Intel i218-LM v3, here with Ven_8086&Dev_15A2&Subsys_222617AA&REV_03

Tomorrow I make a try to do the hack by myself, via this idea from @Mov AX, 0xDEAD

msfn.org/board/topic/184522-lets-try-to-get-the-intel-lan-i219-v-running-with-xp/#comment-1241041

Maybe, that someone has done it already

Dietmar

Edited August 3 by Dietmar

[user57]

i dont make these 3 things firmware, ntoskrnl lan driver control(filter/in between/engine driver), lan driver 
into these 3 things the questions and answers certainly fall

coding wise i would be certainly enough, but i do not know how this chain actually is normed

that certainly needs operating system debugging to see where and how the problem apeared

the requied work needs presents like having the hardware and right toolset (like operating system debugger, the hardware, symbols, related code)

since the ntoskrnl is published we would see where in the code the problem relys
for the acpi.sys there is also full insight 
for the lan driver itself someone would have to know how it normally looks 
for the rather external firmware i would need knowlegue about this specific stuff, what i do not know about

if its a acpi.sys problem of power managment having the right tools and being present i certainly could tell why the problem apeared

sorry for not being more of help

[Dietmar]

Yessaa, on first try it works!!!

Now we have Intel Lan i218-LM v3 for XP

Dietmar

https://ufile.io/g6md5zge

 

PS: Mod is in

e1d5132oriori.sys  ==> e1d5132.sys  from PROEmbSw11 package:

2909:                      04 00 3D 5A 15 00 00 7F 20 3D ==> 04 00 3D A2 15 00 00 7F 20 3D

2137C:                    81 F9 5A 15 00 00 0F  ==> 81 F9 A2 15 00 00 0F

2835B:                   66 81 F9 5A 15 74 07 66  ==> 66 81 F9 A2 15 74 07 66

and correct Checksum

138:    A6 ==> EF 

139:    3D ==> CD

13A:    04 ==>  03

 

and mod its  e1d5132oriori.inf  ==> e1d5132.inf 

 

%E155ANC.DeviceDesc%            = E153A,       PCI\VEN_8086&DEV_155A

==>

%E155ANC.DeviceDesc%            = E153A,       PCI\VEN_8086&DEV_15A2

 

 

%E155ANC.DeviceDesc%            = E153A,       PCI\VEN_8086&DEV_155A

==>

%E155ANC.DeviceDesc%            = E153A,       PCI\VEN_8086&DEV_15A2

 

HKLM,Software\Intel\Prounstl\SupportedDevices\8086, 155A, 0, "155A"

==>

HKLM,Software\Intel\Prounstl\SupportedDevices\8086, 15A2, 0, "15A2"

 

And here is the Notebook Lenovo W550s with 5600U cpu and this Lan device

The only thing that will not work is the crazy graphik driver. Nvidia tells, it has driver for it, not works.

May be, that it is also a very easy hack for the Device ID in nv4_mini.sys..

 

Edited August 4 by Dietmar

[George King]

@Dietmar Looks great! Can you mod x64 aswell please?

[Dietmar]

@George King

I make try, but situation in XP bit64 for lan i218-LM v3 is much less clear than in bit 32 and I have not tested until now

     140:    D5    1D
     141:    0E    57
  2DD4:    5A    A2
335CB:    5A    A2

Dietmar

https://ufile.io/k6jekir2

Edited August 4 by Dietmar

[user57]

very quick

when that driver work on a different os, maybe there is a solution in acpi.sys, ntoskrnl ect.

[Saxon]

@Dietmar, you're super cool! Greetings from Belgium from Saxon!

[reboot12]

@Dietmar

Can you try to patch x64 the driver for the Intel I219-LM 8086 15BB ?

Edited August 18 by reboot12

[user57]

not being present at the place can also be a problem i cant see anything 
there must be a way the other operating system drivers are solving this 
when i cant see where and how the problem exits i actually cant make a conclusion where in ntoskrnl/or other system driver the connected problem might be

it give us a hint with not having the right Vendor number, that probaly the right place to look