Intel PRO/100 VE network adapter drivers loaded but disabled

Ask your support questions in here

Moderator: Moderator Team

Post Reply
middings
Posts: 1008
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Intel PRO/100 VE network adapter drivers loaded but disabled

Post by middings » Sat Jun 28, 2014 1:49 am

I have been experimenting with ReactOS on my P4-equipped HP Pavilion 7965 Desktop PC. I can now build ReactOS (thanks again, guys!), slipstream driver files into the build, and receive a serial debug stream* from the test PC with PuTTY running on another PC with Windows XP. The HP 7965 is listed on the PC ROS Rigs wiki page.

The HP 7965 has a network adapter on its motherboard. My current goal is to make that adapter work with ReactOS. With Windows XP, the adapter identifies itself as an Intel PRO/100 VE Network Connection. I saw the Intel PRO/100 VE listed as "works" (r42095) on the ReactOS Supported Hardware/Network cards wiki page. The PC ROS Rigs page mentions two other machines with an Intel PRO/100 VE network adapter. Unfortunately I cannot get mine to work.

Intel has a driver installer but it crashes. Instead, I used 7-Zip to open it up and unpack the individual driver files.
Slipstreaming the PRO/100 VE Network Connection drivers that work with Windows XP gets the driver files loaded but Device Manager reports "This device is not working properly because FIXME is not working properly (Code 31)", "Device usage: Do not use this device (disabled)", and causes a hang during Turn Off... (shut down). I slipstreamed Windows 2000 drivers using the method described in CORE-3452. The hang during shut down no longer occurs but the other problems remain.

I have run out of ideas to try. Revisions of ReactOS that have been reported to work with Intel PRO/100 VE network adapter hardware as old as r42095 won't build with RosBE 2.1 or, if a daily build is available, it does not run on my HP 7965 PC without crashing. So with my current abilities, I can not slipstream Intel PRO/100 VE drivers into them.

Any ideas?

If I should report this as a bug in JIRA, please let me know if there is debug information I should capture with the serial connection. I have no backtraces because the Windows 2000 drivers do not cause ReactOS to crash. I do not know how to set breakpoints, if doing that is necessary someone will have to explain how to do that.

Edit on 4 July 2014: Reported in JIRA as CORE-8340.
Edit: Debug log added 7 July to CORE-8340.


*I have been using a Laplink style serial RS-232 null-modem cable. It looks like this.

middings
Posts: 1008
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Intel PRO/100 VE network adapter drivers loaded but disa

Post by middings » Sat Oct 11, 2014 2:03 am

I haven't given up trying to get ReactOS to load the driver for my test machine's network adapter. I slipstream them into my builds of the ReactOS boot CD.

This is from a debug log made while installing r64577 on my test machine (HP Pavilion 7965 desktop PC, Pentium 4, 1.25 GiB, 1.67 MHz). I think this part of the debug log was made during ReactOS Setup / Registering Components. Notice the err: messages and the double backslashes in the file paths of the 5 driver files I slipstreamed into my ReactOS build. (Scroll down a bit to see them.)

Code: Select all

WDMAUD.DRV - Process attached
DRV_LOAD
Opening wdmaud device
Populating device lists
5 devices of type 2 found
5 devices of type 1 found
5 devices of type 4 found
5 devices of type 3 found
0 devices of type 5 found
5 devices of type 6 found
Initialisation complete
DRV_ENABLE / DRV_DISABLE
DRV_OPEN / DRV_CLOSE
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\vgamp.sys" -> 
L"C:\\ReactOS\\System32\\drivers\\vgamp.sys"
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\vbemp.sys" -> 
L"C:\\ReactOS\\System32\\drivers\\vbemp.sys"
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\vgaddi.dll" -> 
L"C:\\ReactOS\\System32\\vgaddi.dll"
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\framebuf.dll" -> 
L"C:\\ReactOS\\System32\\framebuf.dll"
WDMAUD.DRV - Process detached
DRV_OPEN / DRV_CLOSE
DRV_ENABLE / DRV_DISABLE
DRV_FREE
Unfreed memory blocks: 0
(ntoskrnl/mm/ARM3/pfnlist.c:1174) Marking PTE: E120FFB8 as transition (B00F44A0 - 8b98)
(ntoskrnl/mm/ARM3/section.c:679) Releasing page for transition PTE E120FFB8
(base/services/umpnpmgr/umpnpmgr.c:3109) Success? 0
(base/services/umpnpmgr/umpnpmgr.c:3000) Installing: 
PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&9090ae03&08
WDMAUD.DRV - Process attached
DRV_LOAD
Opening wdmaud device
Populating device lists
5 devices of type 2 found
5 devices of type 1 found
5 devices of type 4 found
5 devices of type 3 found
0 devices of type 5 found
5 devices of type 6 found
Initialisation complete
DRV_ENABLE / DRV_DISABLE
DRV_OPEN / DRV_CLOSE
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\e100b325.sys" -> 
L"C:\\ReactOS\\System32\\drivers\\e100b325.sys"
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\e100b325.din" -> 
L"C:\\ReactOS\\System32\\e100b325.din"
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\NicCo2.dll" -> 
L"C:\\ReactOS\\System32\\NicCo2.dll"
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\NicInst.dll" -> 
L"C:\\ReactOS\\System32\\NicInst.dll"
err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\e100bmsg.dll" -> 
L"C:\\ReactOS\\System32\\e100bmsg.dll"
WDMAUD.DRV - Thread attached
(dll/ntdll/ldr/ldrutils.c:1323) LDR: LdrpMapDll Relocating Image Name NicInst.dll (02000000 -> 00880000)
(dll/ntdll/ldr/ldrutils.c:1362) Overlapping DLL: C:\ReactOS\system32\NicCo2.dll
WDMAUD.DRV - Thread attached
(dll/ntdll/ldr/ldrutils.c:1323) LDR: LdrpMapDll Relocating Image Name NicInst.dll (02000000 -> 00880000)
(dll/ntdll/ldr/ldrutils.c:1362) Overlapping DLL: C:\ReactOS\system32\NicCo2.dll
(ntoskrnl/se/accesschk.c:271) HACK: Should deny access for caller: granted 0x0, desired 0x100000 (generic 
mapping B30380B0).
(ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\tcpip.sys at F7056000 with 35 pages
(K:/64577/reactos/drivers/network/ndis/ndis/protocol.c:988)(ndisBindMiniportsToProtocol) Performing standard 
bind for protocol 'TCPIP'
(K:/64577/reactos/drivers/network/ndis/ndis/miniport.c:696)(MiniLocateDevice) No registered miniports for 
protocol to bind to
Unhandled event type: 6
(ntoskrnl/se/accesschk.c:271) HACK: Should deny access for caller: granted 0x0, desired 0x100000 (generic 
mapping B30380B0).
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 
'PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&9090ae03&08' (no FDO above)
(ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\e100b325.sys at F7032000 with 24 pages
(K:/64577/reactos/drivers/network/ndis/ndis/miniport.c:2629)(NdisMRegisterMiniport) Initializing an NDIS 5.0 
miniport
(ntoskrnl/io/pnpmgr/pnpres.c:192) Satisfying interrupt requirement with IRQ 0x1
(drivers/bus/pci/pdo.c:1272) Assigning IRQ 1 to PCI device 0x8 on bus 0x2
(drivers/bus/pci/pdo.c:1289) Enabling command flags for PCI device 0x8 on bus 0x2: [Bus master] [Memory 
space enable] [I/O space enable]
(K:/64577/reactos/drivers/network/ndis/ndis/miniport.c:2848)(NdisMSetAttributesEx) Miniport attribute flags: 
0x2a
(K:/64577/reactos/drivers/network/ndis/ndis/io.c:1008)(NdisMRegisterInterrupt) Function failed. Status 
(0xC000000D).
(K:/64577/reactos/drivers/network/ndis/ndis/main.c:94)(NdisWriteErrorLogEntry) ERROR: ErrorCode 0xc000138c
(K:/64577/reactos/drivers/network/ndis/ndis/miniport.c:2063)(NdisIPnPStartDevice) MiniportInitialize() 
failed for an adapter.
(ntoskrnl/io/pnpmgr/pnpmgr.c:677) Warning: PnP Start failed 
(PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&9090ae03&08) [Status: 0xc0000001]
(dll/win32/kernel32/client/version.c:134) ReactOS returning version mismatch. Investigate!
(dll/win32/kernel32/client/version.c:134) ReactOS returning version mismatch. Investigate!
(base/services/umpnpmgr/umpnpmgr.c:3366) Removal pending: 
PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&9090ae03&08
(base/services/umpnpmgr/umpnpmgr.c:3354) Safe removal: 
PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&9090ae03&08
WDMAUD.DRV - Thread attached
(dll/ntdll/ldr/ldrutils.c:1323) LDR: LdrpMapDll Relocating Image Name NicInst.dll (02000000 -> 00880000)
(dll/ntdll/ldr/ldrutils.c:1362) Overlapping DLL: C:\ReactOS\system32\NicCo2.dll
WDMAUD.DRV - Process detached
DRV_OPEN / DRV_CLOSE
DRV_ENABLE / DRV_DISABLE
DRV_FREE
Here are the modifications I made to the boot\bootdata\packages\reactos.dff.in file in order to slipstream the network adapter driver files:

Code: Select all

; Optional/Intel NIC drivers for x86 HP Pavilion 7965
; PRO2K Windows 2000 WHQL approved files modified
; to appear as if they are for Windows XP & 2003 Server
; Append to end of reactos.dff.in
"modules/IntelNIC/e100b325.inf"                       6  optional
"modules/IntelNIC/e100b325.sys"                       2  optional
"modules/IntelNIC/e100bmsg.dll"                       1  optional
"modules/IntelNIC/NicCo2.dll"                         1  optional
"modules/IntelNIC/NicInst.dll"                        1  optional

Black_Fox
Posts: 1584
Joined: Fri Feb 15, 2008 9:44 pm
Location: Czechia

Re: Intel PRO/100 VE network adapter drivers loaded but disa

Post by Black_Fox » Sat Oct 11, 2014 1:35 pm

See above in the log that even the vga drivers say that copy error. Maybe the problem is a bit further in here:

Code: Select all

(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 
'PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&9090ae03&08' (no FDO above)
(ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\e100b325.sys at F7032000 with 24 pages

(...)

(K:/64577/reactos/drivers/network/ndis/ndis/io.c:1008)(NdisMRegisterInterrupt) Function failed. Status 
(0xC000000D).
(K:/64577/reactos/drivers/network/ndis/ndis/main.c:94)(NdisWriteErrorLogEntry) ERROR: ErrorCode 0xc000138c
(K:/64577/reactos/drivers/network/ndis/ndis/miniport.c:2063)(NdisIPnPStartDevice) MiniportInitialize() 
failed for an adapter.
(ntoskrnl/io/pnpmgr/pnpmgr.c:677) Warning: PnP Start failed 
(PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&9090ae03&08) [Status: 0xc0000001]
You might want to create a JIRA issue with your log if you didn't yet, devs probably won't see it here in the forums.

middings
Posts: 1008
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Intel PRO/100 VE network adapter drivers loaded but disa

Post by middings » Sat Oct 11, 2014 6:59 pm

Thanks. I was so excited that I might have discovered something about my network adapter drivers problem that I overlooked the similar vga driver file messages.

Now that I see the discrepancy is probably not due to my own mistake but may be a problem in the ReactOS code, I will take your advice and report the issue in JIRA.

ekohl
Developer
Posts: 16
Joined: Thu Sep 29, 2005 3:00 pm

Re: Intel PRO/100 VE network adapter drivers loaded but disa

Post by ekohl » Mon Oct 13, 2014 9:04 pm

A large part of the network setup code is not implemented yet. Your network adapter driver might fail because at least one part of the installer code is missing. This part should scan the ndi\params subkeys in the registry and copy the default values into the drivers software key.

middings
Posts: 1008
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Intel PRO/100 VE network adapter drivers loaded but disa

Post by middings » Thu Oct 16, 2014 10:45 am

The more I researched that 'copy error' message and the double backslashes, the more I think it is not really an error. I think it is a normal debugging message that only looks bad but really isn't. I suppose the double backslashes are an escape sequence used to write a single backslash.

Code: Select all

    err:(dll/win32/setupapi/queue.c:1664) copy error 2 L"C:\\ReactOS\\inf\\batt.dll" ->  
L"C:\\ReactOS\\System32\\batt.dll"
I see this message when I install bootcd-64750-dbg.iso unzipped from the Daily Builds page and burned onto a CD. I reviewed my logs of builds I made months ago and also see messages with the words 'copy error'. I searched the ReactOS.org site and found a partial log of an install of r24264 with those words. https://www.reactos.org/pipermail/ros-d ... 08847.html

So I'm not going to make new a JIRA issue out of messages like this after all. False alarm.

My existing JIRA report, CORE-8340, is still open. I continue bug hunting to solve my difficulty with the Intel network adapter and ReactOS on my test PC. Thank you, ekohl for your information about the network setup code. However, I believe someone in the past has been able to make ReactOS work with Intel network adapter hardware similar to what my test PC has. I found a few old comments in the ReactOS forums that suggest this is so. Unfortunately, those comments do not include enough information for someone like me to duplicate their result yet.

I am able to experiment a little bit with ReactOS's built-in kernel debugger. I can stop ReactOS and single-step through the code. Last month, I was working on how and where to set breakpoints so I could step through ReactOS's installation of the network adapter driver files. Then I ran out of time and that set me back. Now I just try to keep up with the fast tempo of revisions to the ReactOS code base and make time to build and install one or two revisions of ReactOS per week. Only now am I again reading the Debugging page in the ReactOS wiki and studying its Breaking into the built-in kernel debugger instructions.

As always, I appreciate whatever advice others here choose to offer.

Forever Winter
Posts: 131
Joined: Sun Oct 20, 2013 6:50 am

Re: Intel PRO/100 VE network adapter drivers loaded but disa

Post by Forever Winter » Thu Oct 16, 2014 1:58 pm

You are correct, the double backslashes are escape sequences for a single backslash. As for the copy error, it is indeed an error, since it can't copy the specified files. I guess it is caused because the inf file
in question (in your last case battery.inf) doesn't give a proper location where the files can be found nor does it define a layout file (with correct content) where the source locations for the files can be fetched from.
In this case, the system looks in the directory where the inf file is stored for the files, where they can't be found. Since the first stage setup has copied the files in question to their proper places already, it
works anyway and you can just ignore the copy errors. One may be able to get rid of this messages by giving layout.inf the needed content and modify the other inf files accordingly, but I don't know if this is
already supported.
I guess the file copy may fail for other reasons and then one should not ignore the messages.

middings
Posts: 1008
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Intel PRO/100 VE network adapter drivers loaded but disa

Post by middings » Fri Oct 17, 2014 12:51 am

Thank you Forever Winter for the explanation of the copy error messages that I saw. Last night I installed bootcd-64750-dbg.iso obtained from Daily Builds page. I captured a log of the installation with PuTTY on a host PC connected to my ReactOS test PC with a serial null-modem cable. ReactOS installed in the usual way and the desktop appeared. Yet when I reviewed the log I counted 40 copy error messages.

Those messages look alarming. I really thought I was on to something when I first noticed one of them in a debug log. Producing these unnecessary copy error messages should be avoided. I will file a JIRA report about this after all.

Edit on 17 October 2014: Reported in JIRA as CORE-8643, "bootcd-64750-dbg wrote 40 'copy error' messages to debug log during install".

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest