8 Replies Latest reply on Nov 27, 2009 7:50 AM by olucas

    NIC Driver issue nightmare!!

    Rookie

      Guys, really struggling with a driver issue for the vboot image. I have identified the Hardware on the OS with the following ID (PCI\VEN_8086&DEV_10F5&subsys_024d1028) I have injected what I think is the drivers and all associated files into the image..

       

      When I boot up the image all i get is the network driver not found blah blah blah - I have been trying to look to see what "landesk" picks up the driver ID as, this is the only thing I can think of, maybe landesk is identifiying the nic as a differnet device ID.

       

      I have had a look in WINPEOEM.SIF when its booted into VBOOT and all I see is errors for a NIC card with the same "Manufacturer" but different model of device, Im not sure if this is the error log or not?

       

      Any tips on getting the failed hardware ID from VBOOT itself? or any kind of logging?

       

      Oh and yes the Image has been pushed to the PXE Rep and the drivers are in the image incase anyone asks.

       

      If I cant get this resolved today, I will need to think of a workaround - If anyone has guide on doing this mucho apreciated.

       

      Ollie

        • 1. Re: NIC Driver issue nightmare!!
          rcronje Apprentice

          Is this a Dell with an Intel NIC?

          • 2. Re: NIC Driver issue nightmare!!
            Rookie

            Why yes, yes it is =( - How did you know?

             

            It is infact the Dell 4300 model with the Intel 82567LM driver - It feels like im just going round in circles!!

            • 3. Re: NIC Driver issue nightmare!!
              rcronje Apprentice

              Well I did a good old google for the device and I came up with some hits.

               

              The problem I think you are having is that the .inf file in the driver provided by Dell doesn't have all the information listed in it. Now you would think that downloading the Intel driver from Intel directly would then be the solution. This works in some cases but not in all (I don't really know why but I suspect it has something to do with the PC manufacturer customizing the driver that they receive from Intel). So what I suggest doing is editing the inf file for the driver and putting in the missing Intel manufacturer section then re-adding the driver and files to your WinPE etc. Now this process can be quite a challenge to figure out but google comes to the rescue again. Have a look at your inf file and see if it matches below:

               

              [Manufacturer]
              %Intel%     = Intel, NTx86.6.0, NTx86.6.0.1

               

              [ControlFlags]


              [Intel]

               

              [Intel.NTx86.6.0.1]


              ; DisplayName                   Section         DeviceID
              ; -----------                   -------         --------

               

              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_10F58086

               

              ;Dell
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02331028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02341028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024D1028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024F1028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02501028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02771028

               

              %E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF
              %E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF&SUBSYS_10BF8086
              %E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB
              %E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB&SUBSYS_10CB8086

               

              [Intel.NTx86.6.0]

               

              ;=============================================================================
              ;
              ;                              WINDOWS Vista PLATFORMS
              ;
              ;==========================================================================

               

              If this looks like the inf file you have (E1y6032.inf) then edit it to look like this:

               

              [Manufacturer]
              %Intel%     = Intel, NTx86.6.0, NTx86.6.0.1

               

              [ControlFlags]


              [Intel]

               

              [Intel.NTx86.6.0.1]
              ; DisplayName                   Section         DeviceID
              ; -----------                   -------         --------

               

              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_10F58086

               

              ;Dell
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02331028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02341028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024D1028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024F1028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02501028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02771028

               

              %E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF
              %E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF&SUBSYS_10BF8086
              %E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB
              %E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB&SUBSYS_10CB8086

               

              [Intel.NTx86.6.0]

               

              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_10F58086

               

              ;Dell
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02331028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02341028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024D1028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024F1028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02501028
              %E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02771028

               

              %E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF
              %E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF&SUBSYS_10BF8086
              %E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB
              %E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB&SUBSYS_10CB8086

               

              ;=============================================================================
              ;
              ;                              WINDOWS Vista PLATFORMS
              ;
              ;=============================================================================

               

              Try this and see if you come right

               

              Message was edited by: Ryan Cronje

              • 4. Re: NIC Driver issue nightmare!!
                Employee

                Why don't you try this: http://community.landesk.com/support/people/jan.buelens/blog/2009/06/18/winpe-driverpack-tool--bring-your-winpe-image-up-to-date-with-all-the-latest-drivers. This imports the latest intel drivers (as well as broadcom drivers).

                 

                I'm afraid I can't agree with Ryan. The x86.6.x sections are for Vista / W2K8. LDMS 8.8 has a Win2003 based WinPE (x86.5 or x86.5.x).

                • 5. Re: NIC Driver issue nightmare!!
                  rcronje Apprentice

                  Thanks for clarifying what the sections are Jan. I like to know these things

                   

                  Would I be correct though if there was an empty x86.5 or x86.5.x section in the inf file? In other words copying the info under that section would then fix the issue (or maybe obtaining the 2003 driver would be best)?

                  • 6. Re: NIC Driver issue nightmare!!
                    Employee

                    No you still wouldn't be correct...You still wouldn't want to hand-add "missing" stuff to inf files in the way you describe. If you think stuff is missing, you're almost certainly looking at the wrong inf file.

                     

                    When you find an inf file with an empty x86.5.x section, that's usually to stop the wrong driver being used with the wrong OS. The file that you are showing (e1y6032.inf) is part of the vista/W2K8 drivers. Intel puts it in a folder called provista32. The corresponding file for WinXP/W2K3 is e1y5132.inf.

                     

                    Perhaps you found some gossip in google about the PC manufacturer messing with the intel NIC drivers? I remember comparing the intel original with a PC OEM manufacturer's version. The only diffrence was that the PC manufacturer had added some empty sections, like an empty x86.5.x section in the Vista/W2K8 inf file, or X86.6.x in the WXP/W2K3 inf file. The only reason I can think of is to make things slight more robust against human error.

                    1 of 1 people found this helpful
                    • 7. Re: NIC Driver issue nightmare!!
                      zman Master

                      Why don't you try this: http://community.landesk.com/support/people/jan.buelens/blog/2009/06/18/winpe-driverpack-tool--bring-your-winpe-image-up-to-date-with-all-the-latest-drivers. This imports the latest intel drivers (as well as broadcom drivers).

                       

                      I second this recomendation. I have tested this script out and 1. it works, and 2. it works very well! Sooooooo much easier.

                      • 8. Re: NIC Driver issue nightmare!!
                        Rookie

                        Thanks guys, the driver inject wizard worked - I used it when we first rolled out LANDesk 8.8 but never came back to it.

                         

                        The worst part is I actually had the proxp driver pack from intel downloaded, and I manually injected the INF file for the hardware ID - Unfortunatly it looks like I injected the inccorect one or .. the inject did not work!!

                         

                        Well thanks for the link, I shall be keeping that for next time!

                         

                        Ollie