D610 and D410 broadcom nic driver not loading during sysprep

Hello

We have excact the same problem with a D410 Laptop. We have a sysprep which runs trough from GX110/270/280 and all D400/D600/810. I have problems with the Boradcom B57 network driver in sysprep. I tryed about 5 difdrent version and releases (From dell Itself or direct from Broadcom). I can't join the Domain since at that point he does not have the NIC active. After that the NIC is fully initialized. One time i had to leave the test laptopo and came back 1 hour later and after the standby modus i could join the domain with the sysprep setup. Look like the card was found correct after the wake up.

- The sysprep.inf is as reccomende by Boradcom itself.

The same OemPnPDriversPath is used in our RIS setup and there the D410 is setup perfect.

My sysprep.inf (Parts of)

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    OemPnPDriversPath = pnp\Nic;pnp\wire;pnp\Modem;pnp\modem\ConGVC92;pnp\modem\conv90;pnp\modem\conv92;pnp\modem\pctel56k;pnp\modem\cond110;pnp\Video\e773c;pnp\video\intel915;pnp\video;pnp\sound\SIGMA975;pnp\sound\ADI1885;pnp\sound\ADI198X;pnp\sound\CRY4205;pnp\sound\CS4281;pnp\video\YMF724;pnp\Sound;pnp\Other;pnp\other\TI6515;pnp\other\o2micro;pnp\other\wire_IR;pnp\other\wire_ar;pnp\board;pnp\video\intel815;pnp\video\intel845;pnp\video\matro450;pnp\video\nvidia;pnp\video\915gm
    InstallFilesPath=C:\sysprep\i386
    TargetPath=\WINNT

**************************************************************************************************

I have the correct files:

b57win32.cat

b57win32.inf

b57w2k.sys

In path: \d610\sysprep\i386\$oem$\$1\pnp\nic

**************************************************************************************************

If anybody knows anything here it would be great if he could contact me directly at:

+41 61 565 62 24

M. Butsch / www.actelion.com

Hello

have the same problem with D410 and D610. The problem seems to come from the intel mobile chipset drivers. if you don't include it the RIS installation, the 2 network cards Broadcom and Wireless Intel 2200BG are well installed at the good time and but a PCI device is not installed 82801 FB/FBM SMBus controller 266A. This one come with the chipset drivers !!!

Have not got a fix yet,

rumor has it that Dell is aware of the issue and we are waiting on a potential fix.

-Rhino

Whst are you saying? To not load the chipset driver before the nic?

I am having an issue with mini setup hanging and needing a hard reset before mini setup will continue on D410 & D610 laptops. When it does come up I do see that it is installing and configuring the nic.

I have the nic specified in the drivers path and the chipset drive I have is not a .inf so it doesn't get installed until later by scripts I run after mini setup is finished, so it shouldn't be messing with the nic driver during mini setup. I just didn't understand in the one comment if you meant the chipset needed to be installed prior to nic install.

Have any of you resolved this issue satisfactorily? Any help is appreciated.

You can contact me at p3374c@gdds.com.

English Windows 2000, SP4, BIOS A03 (Switzerland shopping Bios for the D410).

RIS works fine

SYSPREP not

Thanks

Mike

What i mean is : with RIS installation if you include the intel mobile chipset the installation stops when you include the workstation into a domain. But you can continue and the Broadcom driver is installed at the first start of windows when all is installed and finished !!!

If you don't include the chipsets, All the network card are installed and the computer is added to the domain automatically. But the chipset are not installed .

I just saw this morning that dell have publised the chipset. I have tried them but it is the same thing.

still waiting a answer from Dell support. But if anybody have the solution i will be please to take it.

Pharma,

So, was it the braodcom drivers of the intel drivers that resolved the problem with sysprep.

I went out to broadcom's website and they still have the same driver out there from before (*same as dell's site as well._08/23/2004,7.86.0.0)...

Is that the one you used?

THanks

Rhino

No it's was just using the sysprep -pnp or not option. I have gotten some chat transscript from a user and it looks like they have problems with D410/D610 line and will soon release a new BIOS version.

DELL TRANSSCRIPT/CHAT  

{DELL_USER 12:03:26 PM} (4804410907) We are having an issue when imaging D410 & D610 laptops. When mini setup runs it hangs. After turning the power off and back on mimi-setup continues and I see networking components installing.

Do you know why mini setup would hang and how we can fix it? Having to hard boot the machine is unaccepatble due to the large number of machine simaged daily. 

{DELL_SUPPORT12:03:43 PM} Hi DELL_USER, I'll just need a moment to look over your request. Please be patient as I may be chatting with multiple users. Can I have your physical address where the machine is located at in case we need to send parts or a technician? 

{DELL_SUPPORT12:05:18 PM} For verification, what is the name of the organization that purchased the machine? 

{DELL_SUPPORT12:06:46 PM} this "mini setup" is that part of the imagine software that you are using? 

{DELL_USER  12:07:05 PM} and it isn't just this machine, they actually purchase many. I am creating an image for imaging them with the specifics General Dyanamics wants 

{DELL_USER  12:08:11 PM} no mini setup is what happens when you use sysprep to prepare a machine to imaging, it is part of Microsoft sysprep 

{DELL_SUPPORT12:08:22 PM} ah ok 

{DELL_USER  12:10:53 PM} you run sysprep on a machine then capture that image, then put it on another machine that machine runs mini setup, I think it is hanging during hardware detection. I think this is a problem with a driver, I have seen some comments in the customer forum on others having the same problem but no one with any resolution yet. 

{DELL_SUPPORT12:11:31 PM} i took a look at the forums and it looks like several people have this issue, but no fixes on it. 

{DELL_SUPPORT12:12:16 PM} let me check something else, ill be right back 

{DELL_USER  12:12:22 PM} ok 

{DELL_SUPPORT12:16:39 PM} i think i have an answer for you. 

{DELL_SUPPORT12:16:49 PM} are you installing xp? 

{DELL_USER  12:16:52 PM} yes 

{DELL_USER  12:17:24 PM} and the d410 has the latest bios A02 on it 

{DELL_SUPPORT12:19:07 PM} for the d610, the bios needs to be upgraded to the a03 bios 

{DELL_SUPPORT12:19:25 PM} on the d410s, the bios hasnt been updated yet. 

{DELL_USER  12:19:41 PM} haven't tried that yet since it also said to update the D410 to A02 and it didn't make any difference 

{DELL_SUPPORT12:19:44 PM} it should be released soon because the hardware is nearly identical to the d610 

{DELL_USER  12:20:00 PM} what should be released soon? 

{DELL_SUPPORT12:20:09 PM} the bios update for the d410 

{DELL_USER  12:21:37 PM} when? and is there another way to contact someone if I go update bios on D610 and try the install and it still doesn't work? e need these images built asap since we will start receiving them soon. 

{DELL_SUPPORT12:22:13 PM} i don't have any kinds of etas on that, but on the support site, you can set the "filewatch" to email you when the update is released. 

{DELL_SUPPORT12:23:09 PM} The issue rolls around the Programmable Interrupt Controller (APIC) based interrupt subsystem and the PIC based interrupt subsystem in the image 

{DELL_USER  12:23:37 PM} ok, I will go try the D610, but how soon will these be shipped with the correct bios? Is there anyway to contact you directly if the install still doesn't work? 

{DELL_SUPPORT12:23:40 PM} if the image is made with a PIC based interrupt, it will cause the image to not work on the machines. 

{DELL_SUPPORT12:23:56 PM} When you update the bios on the d610, it will allow the image to work on the machine. 

{DELL_SUPPORT12:24:16 PM} the older bios will only work on APIC images 

{DELL_USER  12:24:32 PM} I created these images on a GX280, I am not sure what a PIC based interrupt is, does the GX280 have it? 

{DELL_SUPPORT12:25:35 PM} that will cause the image to fail. 

{DELL_SUPPORT12:25:52 PM} you cant create an image on a gx280 and have it work on the portables 

{DELL_USER  12:26:17 PM} why not they have the same hal, and it works on the D400 & D600 

{DELL_USER  12:28:21 PM} actually the image we put on the D400 & D600 is built on a GX150 or GX260. 

{DELL_SUPPORT12:28:30 PM} D610 supports Advanced Programmable Interrupt Controller (APIC) based interrupt subsystem as well as PIC based interrupt subsystem. The D600 supports only PIC based interrupt subsystem.

If an operating system that supports APIC is installed on D610 it will enable APIC and the associated HAL. The same OS installed on D600 will run a PIC HAL. Microsoft operating systems such as Windows NT 3.1, Windows 2000, and Windows XP support APIC. Although some locations are using both Windows 2000 and Windows XP, their OS images are not configured to run in APIC mode. Since these locations use only one image to support ALL of their systems (PIC and APIC), they cannot simply force D610 image to run in APIC mode. 

{DELL_USER  12:31:58 PM} are meaing the ACPI Uniprocessor PC (HAL) or is this another piece of the hardware that we also now need to be aware of, I understood that if the machines had the same HAL you could use the images 

{DELL_USER  12:32:41 PM} I meant are you meaning 

{DELL_SUPPORT12:34:39 PM} the hal and the apic are separate entities 

{DELL_SUPPORT12:34:51 PM} the apic is a part of the motherboard/bios 

{CUSTOMER12:35:24 PM} ok, so now we have to create separate images not just for machines with different HALS but also for different apic's? 

{DELL_SUPPORT12:35:44 PM} there is a different hal for it 

{DELL_SUPPORT12:36:21 PM} you have to create separate images for separate machines 

{DELL_SUPPORT12:37:13 PM} for the most part, the desktops can use the same image. its the portables that really need separate images for different systems 

{DELL_SUPPORT12:37:33 PM} for the most part, the update on the d510 image fixes that problem 

{DELL_SUPPORT12:37:56 PM} and i suspect that the update for the d410 bios that will be released eventually will solve that problem 

{DELL_SUPPORT12:38:09 PM} the hardware is identical 

{CUSTOMER12:39:15 PM} But when I looked at the D410 prior to imaging it had the same hal as the GX280 the ACPI Uniprocessor PC, and we have never created separate images for different hardware until the GX280 because of hyperthreading, as I said the D400 & D600 use an image created on a GX150 or GX260. OK I am going to try to update the bios on the D610 and reapply the image, but you didn't answer if there is a way to contact you if this doesn't work 

Pharma, you say that the RIS works well

I have the same configuration W2K SP4 and for me it don't work. I have the latest drivers from intel and broadcom.

how did you make it to work and witch version of drivers did you take

Hi,

I have the same rpoblem when creating an unattended installation from CD. The problem occurs when I leave the ICH6core.inf in the $oem$ directory. If this one is removed the setup continues otherwise it blocks an reboots during the network configuration during GUI set-up.

I also have the latest chipset and network drivers from Broadcom and Intel.

Is there already a solution for this problem?

Lars