Content Type
Profiles
Forums
Events
Everything posted by reboot12
-
@Dietmar I believe that no power-related fixes will help. Your driver has always work at speed of 1.0 Gbps and Auto Negotiation does not work, it cannot detect the correct speed of the network card on the other side of the cable. And that's the problem. Improve your driver so that it can detect the speed correctly, i.e. when I connect a Fast Ethernet device it should set a speed of 100 Mbps and when I connect a Gigabit Ethernet device it should set a connection of 1.0 Gbps Once it works properly, you can continue to look for the cause of 0/0 packets.
-
@Dietmar i219v1h - https://pastebin.com/WJUsiKYp i219v1k - https://pastebin.com/trbArAsY I have been testing a dozen or so drivers for several days and there is practically no progress - there are still 0 sent / 0 received packages. If it works for you on the identical i219 LM 15BB card, it should work for me too. Take a photo of the RJ45 plugs of your network cable on both sides. My cable is in standard EIA/TIA568B on both sides B-B. My cable came with the Draytek Vigor 2700G router and is 1.8 m long: Draytek included such a yellow network cable 1.8 m with its routers - as in this photo:
-
@Dietmar OK, I'll check tomorrow because I've had enough today P.S. If it doesn't want to work, that's too bad. I was just curious that it works for you, so I wanted to check the driver. But I don't use these i211 and i219 cards in my WinXP 64-bit on AIMB-786 anyway. I used i211 for a while, but it turned out that the driver extends the start of WinXP by 10 seconds. I disabled both cards in the BIOS and use an old PCI TP-Link Wifi card and the system starts very quickly and I have a network. These new Intel iXXX series network cards are highly advanced and problematic: https://forums.mydigitallife.net/threads/winxp-64-bit-on-a-modern-pc-iso-boot-wim-install-wim.88435/page-7#post-1869357
-
@Dietmar I noticed that WinDbg remembers the path to the symbols after starting, so there is no need to set it in the KD each time. I tested the commands without !sym noisy & .reload /f and the results are the same but the log is clearer without the DBGHELP messages so I think this commands are unnecessary. From now on I will start debugging with the commands: sxe ld:i219 sxe ud:i219 g .reload /f i219.sys lm m i219 and put your new commands there This is full WinDbg log if try from start WinDbg and from command sxe ld:i219 (after auto break from boot.ini switch) > https://pastebin.com/3HSAFxjG
-
So I can copy and paste all the code at once and you wrote earlier that I have to enter it line by line Now I can use WinDbg conveniently and pleasantly Typing line by line was very tiring https://www.upload.ee/files/19111494/i219LMbest_kd_diag_fixed_05d4_2026-02-26_07-14-11-281.txt.html i219LMv7 - 100 Mbps but 0/0
-
@Dietmar i219bind log - I do g few times: https://pastebin.com/EgHhp4h8 i219coll 100 Mbps but 0/0 and log: https://www.upload.ee/files/19108296/i219_rescue_windbg_0af0_2026-02-25_08-18-08-125.log.html i219CollFix - 100 Mbps 0/0. If tried connect i219 to GBE device e.g. my laptop then cable unplugged and mouse cursor gets stuck about every 3 seconds Does your i219 driver allDEV work with old 100 Mbps devices or only with GBE devices ?