Lenovo M73 and RM CC4 - Network Driver issue - Anyone have these working?

[tj2419]

Hi

 

We have just had some Lenovo M73 tiny computers delivered. We are getting a build error saying missing driver so we have downloaded the driver from the lenovo site and extracted the INF and created a new build disk etc but it still fails with the same error.

 

Does anyone have the Lenovo M73's on CC4 Windows 7 SP1? Do you have the exact driver you are using?

 

Or any other things we can try.

 

The missing driver is PCI\VEN_8086&DEV_153B&SUBSYS_309E17AA&REV_04

 

Thanks

[foofighterjim]

Just to cover the basics. You say you have downloaded the driver and recreated the build disk.

 

Did you add the driver to the build image and if deploying with WDS did you replace the wim in WDS?

 

The other thing I would try if you are still struggling is use something like Driver Grabber on a fully functional device. It should pull (amongst other things) the LAN driver that is on the device, you will have direct access to the INF without extracting and can test with the new driver.

[tj2419]

Hi yes we added the driver and then replaced the WIM file in WDS.

 

We have tried that. Just installed windows 7 professional and extracted the network driver and that has still not worked.

 

Our LEA said we will need to find a Vista driver for it but they do not seem to be available from Lenovo or Intel.

[foofighterjim]

You should be using WinPE 3.1 as a minimum now (based on Windows 7 not Vista). It should only include Windows 7 build templates, if you have XP & Vista listed as well as Win 7 you are still using WinPE 2.0 wim which is Vista based and may be causing the issue.

[tj2419]

You should be using WinPE 3.1 as a minimum now (based on Windows 7 not Vista). It should only include Windows 7 build templates, if you have XP & Vista listed as well as Win 7 you are still using WinPE 2.0 wim which is Vista based and may be causing the issue.

 

OK, how do i check the version we currently have? How do we upgrade that?

 

Thanks

[foofighterjim]

You should have the following in the build disks node: (possibly without the Windows 8 images) each disk creates a separate wim and needs to be added into WDS this gives you the option of selecting what wim to load on PXE. As I said the WinPE 2.0 wim contains images for XP, Vista and 7. WinPE 3.1 only has Windows 7 images.

[tj2419]

Thanks @foofighterjim. I have successfully updated our build disks so we now have PE3.1 available.

 

We are getting closer as it now allows the computer to start the build process and get an IP, download and install the OS. But when it restarts it doesn't get the IP address back and eventually crashes out saying missing driver again.

 

We seem to have imported all the drivers we can find :S

 

Any advice?

 

Cheers

[foofighterjim]

Always good to make sure you are up to date on the RM Driver packs (TEC1299560) as even though the actual device may not be relevant the chipset drivers and the like usually do the trick.

 

It sounds like it knows to use the LAN driver in the PE Environment but not in Windows build. In the drivers list on the RMMC is the driver listed? If so does it have the OS you are building to listed? If not it may be rejecting the driver because of the OS version. As a test on the build screen where you specify the name of the device you can click on the drivers tab and instruct the build to use a specific driver. If this works then there may be a newer version of the driver getting in the way.

[tj2419]

Always good to make sure you are up to date on the RM Driver packs (TEC1299560) as even though the actual device may not be relevant the chipset drivers and the like usually do the trick.

 

It sounds like it knows to use the LAN driver in the PE Environment but not in Windows build. In the drivers list on the RMMC is the driver listed? If so does it have the OS you are building to listed? If not it may be rejecting the driver because of the OS version. As a test on the build screen where you specify the name of the device you can click on the drivers tab and instruct the build to use a specific driver. If this works then there may be a newer version of the driver getting in the way.

 

You legend looks like selecting the specific driver to use has worked. Build has got further and now assigning packages. Wonder why it wouldn't find it automatically :S

[foofighterjim]

The only reason is if the inf file info doesn't match either with OS or it isn't an exact match for the card. If CC4 thinks it has a newer driver than your imported one for that card it will try to use that instead. Ensure you are up to date with your CC4 driver packs!