I have been having problems with PC's with Asus A7N266-VN motherboards with Nforce onboard NIC's
This problem has been haunting me for weeks and I have spent alot of my spare time on this. Anyway I have found a solution today so I thought I would share it with everyone here just incase.
This was written by a MikeC on the nvidia forums but the links don't work anymore but don't worry I found this link ftp://dlsvr02.asus.com/pub/ASUS/misc/utils/nvidia/ and all the files I needed were there today.Quote:
nVidia motherboards installing Windows via RIS getting this strange error message:
"The operating system image you selected does not contain the necessary drivers for your network adapter"
as also described by MS in http://support.microsoft.com/?id=823658
*although* the network driver is correctly integrated into the image. Here's my point of view:
Motherboards with an nVidia chipset are somehow different, although the network adapter is available as a driver to the RIS setup it can't identifiy the device on the PCI bus therefore it fails to pick the correct driver inf file. nVidia chipsets don't view all devices on the PCI bus in a direct fashion meaning accessing the network controller there's a strange NVNRM driver necessary to make the network adapter appear as a common PCI Ethernet device on the bus.
I used a PCI scanner and was wondering why the network adapter appears as a unknown bridge device although it should be a common block device but then under a complete Windows installation the nVidia ethernet controller is available without any problem.
The nVidia network device is not enumerated until the nVidia bus driver is started, that one is used to control the bridge device. *Until* and this is where the angels meet the devil in freezing hell...
You must have a NVidia Boot Agent PXE BootRom Version higher than 201.xxxx
When installing the full nForce Driver Package under Windows a magic device called "nVidia Network Resource Manager" is installed to make the ethernet controller visible on the PCI bus. This is what was missing under a RIS setup and therefore lead to that strange error message.
Now where do i get that magic driver thing?
After searching the net up & down, i found those on an ASUS FTP server.
nForce < 5:
Integrate this driver *and* your nVidia network driver into the RIS image like described in http://support.microsoft.com/kb/314479/
The drivers available at ASUS can be used for *any* board with an nForce chipset and not only for ASUS boards since i have an MSI board running a RIS setup with those drivers. nVidia himself describes the problem here:
For the RIS setup it's important that this driver is installed in the ./i386 drawer of the RIS image. It makes the ethernet controller *visible* and RIS runs like a charm
There is also a PDF doc on the site relating to RIS
I hope this can be of some help to someone.Quote:
NVIDIA nForce2 MCP2S, NVIDIA
nForce3 250, and nForce4
Configuring NVIDIA Networking
Drivers with Microsoft RIS
Released Under NDA
11/17/04 NVIDIA CONFIDENTIAL
Install Networking Drivers
This application note describes how to configure NVIDIA® networking drivers
when using the Microsoft Remote Installation Services (RIS) to install OS images on
NVIDIA® nForce ™2 MCP2S, NVIDIA nForce3 250, and the nForce4 family of
products. (The NVIDIA nForce2 MCP2S family of products includes nForce2 RAID MCP
and nForce2 Gigabit MCP. The NVIDIA nForce3 250 family of products includes nForce3
250, nForce3 250Gb, nForce3 250 Pro, and nForce3 250 Ultra. The NVIDIA nForce4
family of products includes nForce4, nForce4 Ultra, nForce4 SLI, nForce Professional 2200, and
nForce Professional 2050).
For RIS installations, a network device attached to the PCI bus needs to be present.
For the NVIDIA nForce2 MCP2S, NVIDIA nForce3 250, and the NVIDIA
nForce4 families, the NVIDIA network device is not enumerated until the NVIDIA
bus driver is started. The NVIDIA bus driver is used to control the NVIDIA bridge
Detailed Installation Procedure
The following steps describe the sequence needed for NVIDIA nForce2 MCP2S,
NVIDIA nForce3 250, and NVIDIA nForce4 RIS clients on Windows XP,
Windows 2000, and Windows 2003 Server.
Ensure that the installed BIOS contains PXE version 201 or greater. PXE version
can be seen in the PXE startup banner. A sample PXE startup banner is provided
PXE Boot Agent 201.xxxx
1. Read Microsoft Knowledge Base Article #315279 for details on how to add
OEM Network Adapter Drivers to an RIS image.
2. This procedure is step 1 of article #315279:
If you are installing Windows XP onto your RIS client, copy the files contained
in nvriswxp.zip onto:
3. This procedure is step 1 of article #315279:
If you are installing Windows 2000 or 2003 Server onto your RIS client, copy
the files contained in nvrisw2k.zip onto:
Configuring NVIDIA Networking Drivers with Microsoft RIS
11/17/04 NVIDIA CONFIDENTIAL
4. This procedure is step 3 of article #315279:
You must copy the installation package for the NVIDIA NRM driver (that
is, netbus driver) to:
5. All other steps in article 315279 should be performed as specified.
6. After completing the above steps, you need to restart the boot information
negotiation layer, or restart the machine.
PXE may now be used to install the OS image onto the RIS client.