Deployment Solution

Hi all,

We have just received the new HP Mini 5102 laptop. I am try to create an image of it after sysprepping and when I attempt to PXE boot it gets as far as the "initialsing TCP/IP via DHCP" and then fails, after it times out the following errors are displayed

NO DHCP server found: TCP/IP not loaded
Unloadable TCP 1.0 not loaded
NET0116: TCP access failed by Tiny RFC
Tiny RFC 1.0 not loaded
Error 7361: IPX or NetBIOS must be running in order to load the network services
Could not authenticate network connection
Unable to start network properly


Any ideas?  The installed NIC is a Marvell Yukon 88E8059 (gigabit ethernet controller) and we are running on DS 6.9 SP3
Other laptops & desktops are able to PXE no problem

Regards

Having an identical issue as Torrance. I've gone so far as to download the 'current' NDIS2 drivers from the Marvell site (which ironically doesn't even list this particular NIC). Trying to launch Ghost with the NDIS2 driver results in and 'Unable to bind' error during the initial boot and all options outside of Local being grayed out in Ghost itself. This error persists across multiple identical systems.

A couple of weeks ago I received the new HP 5102 mini to build an image and got the Marvell Yukon 88E8059 ndis2 driver to boot into Ghost - no such luck.  When Ghost is "Initializing packet driver and IP address..." here is what I get:

     Application Error 19913
     Unable to start TCP/IP
     Can't find DHCP server
     Possible network setup problem

     If this problem persists, ... blah, blah.

I have tried both cd-rom (external, of course) and USB (thumbdrive) to no avail.  I figure it's the correct driver since I got it from Marvell's support site.  Have any ideas or solutions?  Thanks.

Same issue as Torrence and NClark. we have ~500 of these to image and a solution would be nice.
Error log attached. tried with -FNI and without (or standard does not have FNI)

found
>> Found Mass storage & network controller hard wire-ord together !!
>> Found Mass storage & network controller hard wire-ord together !!
>> Found Mass storage & network controller sharing IRQ
>> Reckon you should move the irq to 5
in the error log and looked that up. ref a dell gx270 image issues.
is there a BIOS setting to move the IRQ for the NIC??

I'll be looking...

In BIOS
System Configuration
Built In Device Options
Un-Check Audio Device (turn it off). this will also disable the microphone and internal speakers.

As soon as thats off PXE boot works and the image transfered

All other BIOS settings are set to Factory Default

well that got it running but ... now we're seeing intermittently imaging failures.
STACK FAULT in RMCB at eip=14c5;flags=3002 eax=00680001 ebx=00001246...

only on some and if we re-run the image it works so it doesnt look like a hardware issue. 
Im not getting much help on this from other forum posts either...

still looking

Fix (sort of) is posted at https://www-secure.symantec.com/connect/forums/problem-ghosting-hp-mini-5102

What type of PXE boot are you using?
WINPE 1.6 or 2.1.
If you use 2.1, then download the drivers for Vista.
Add the drivers to your WINPE image.

I added the drivers i use myself.

Same issue with 5103.

 

i have active case with HP to see if they have an answer for this model as well.

 

i tried the different versions of the marvell drivers, and disabled audio in the BIOS.

still get acquiring address from DHCP, and then after timing out, i get as Torrance.

 

NO DHCP server found: TCP/IP not loaded
Unloadable TCP 1.0 not loaded
NET0116: TCP access failed by Tiny RFC
Tiny RFC 1.0 not loaded
Error 7361: IPX or NetBIOS must be running in order to load the network services
Could not authenticate network connection
Unable to start network properly

we are running on DS 6.9 SP3 as well.

 

i have no issues with other machine using the winpe image.

so not server related, definitely driver.

had some breakthrough.

i can create a DOS boot image which works....

DOWNSIDE: its much slower than WINPE.

not sure yet if its something i have done, or driver related.

i used the NDIS2 DOS driver, and in altiris set the manufacturer as 11AB, and the device ID as 4381

Worked with Altiris, and found that the issue was the wireless was trying to boot first, instead of the NIC, and i didnt have the drivers for the wireless in the PXE image.

 

inserted them, and all working.

see new post for details

https://www-secure.symantec.com/connect/forums/how-pxe-boot-hp-mini-5103