Ok, a little progress but not what you would expect. Updated the BIOS and made changes to the protocol.ini with no success. On a hunch, I plugged the system onto our Windows Network (we have two separate networks, one Windows and one *nix). The Windows Network run DHCP on an NT system, and it worked fine. Which led me back to this obscure gem from Microsoft posted in 2001.
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com: 80/support/kb/articles/Q179/2/38.ASP&NoWebContent=1 Since we are using a "third-party (ie. non-microsoft) DHCP server" we put in the two options mentioned into dhcpd.conf and restarted. However it still hangs on getting an address. However, since it worked with the e100b.img on the Windows network, i'm confident that the problem lays somewhere in my linux dhcp configuration. has anyone been successful using linux dhcp on redhat7.2 to perform an unattended install? If so, could you share your dhcpd.conf file for comparison. Here's our current setup: shared-network eth1 { subnet 172.30.1.0 netmask 255.255.255.0 { #eth1 dynamic_start# range 172.30.1.162 172.30.1.180; filename "/tftpboot/pxelinux.0"; next-server 172.30.1.161; option dhcp-server-identifier 172.30.1.161; option option-128 E4:45:74:68:00:00; option option-160 "timeout=5:default=195"; option option-193 "eepro100:::/tftpboot/xcat/stage.nbi:::console =ttyS1,9600 stage2 eepro100"; option option-194 "pcnet32:::/tftpboot/xcat/stage.nbi:::console= ttyS1,9600 stage2 pcnet32"; option option-195 "autodetect:::/tftpboot/xcat/stage.nbi:::conso le=ttyS1,9600 stage2 eb"; #eth1 dynamic_end# default-lease-time -1; option routers 172.30.1.161; option subnet-mask 255.255.255.0; option nis-domain "NA"; option domain-name "[actualdomainname.com]"; (removed for maillist posting) option domain-name-servers 172.30.1.161; option time-offset -5; option dhcp-rebinding-time 300; option dhcp-renewal-time 300; host feydpv07 { hardware ethernet 00:09:6B:58:2C:DC; fixed-address 172.30.1.177; filename "/tftpboot/pxelinux.0"; option dhcp-server-identifier 172.30.1.161; next-server 172.30.1.161; } } #172.30.1.0/255.255.255.0 subnet_end# } #eth1 network_end# -----Original Message----- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 10:51 AM To: Delgado, Ed Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] RE: TCPTSR.EXE doesn't obtain address It definitely sounds like the IRQ is wrong. OK, from the top :-). I see Intel released a new e100b driver in March. I have updated Unattended for the next release, and uploaded the new e100b.img to <http://unattended.sourceforge.net/testing/>. It is probably the same as what you already have, but please try it out just in case. Next, I suggest making sure your Compaq's BIOS is flashed to the most recent release. The IRQ auto-detection is supposed to "just work", but it depends on some interaction between the driver and the BIOS. If you look at the message printed during "net initialize /dynamic", it should show the I/O address and IRQ which was probed. If you can set the card's IRQ in the BIOS, you could force it to use that value. Some BIOSes allow this; some do not. If none of that works, or if you are loathe to muck with your hardware in this way, try editing net\protocol.ini on the boot disk. Add a line like this to the [GEN_NDIS] section: IRQ = 9 Try 9, 0xA, 0xB, and 0xC first. Then try 10, 11, and 12 :-). (I am not 100% sure of this syntax. I am not even sure that the e100b driver supports forcing the IRQ. But it is probably worth a try.) - Pat "Delgado, Ed" <[EMAIL PROTECTED]> writes: > Patrick, > > Thanks for the reply, so to answer your questions: > > - So "net initialize /dynamic" loads the e100b driver and correctly > identifies the network card? > > Yes, it loads the e100b driver successfully and proceeds to netbind > and tcptsr. I also tried using the e100b drivers downloaded directly from > IBM and Intel. Neither has worked. > > - Does this system have multiple NICs? If so, you might try disabling > one of them in the BIOS. > > Yes, the system has two NICs. I have tried disabling them in the > BIOS, doing one then the other but still no luck. I will try it again to > make sure I didn't mess something up. But i'm pretty sure that failed too. > > - Do things hang permanently, or do they eventually time out with an > error message? (If so, what message?) > > Yes, they just hang. The line reads "Initializing TCP/IP via > DHCP..." ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
