Bug 20513 - Installation (over internet) does not work with DHCP; stops at "Scanning for DHCP servers"
Summary: Installation (over internet) does not work with DHCP; stops at "Scanning for ...
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: i386 (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: David E. O'Brien
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-08-10 01:40 UTC by kmuthu
Modified: 2000-11-10 18:02 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kmuthu 2000-08-10 01:40:00 UTC
I was trying to install FreeBSD 4.1 over the internet. As I don't have a fixed IP address, I started the installation
using DHCP. But the installation does not proceed after that. There is a message "Scanning for DHCP servers" and installion
is stalled there. 

It is NOT that there are no DHCP servers available. When I boot my system in win95, I do get the IP address and other information.
(I managed to install using a fixed IP address; Also there are no incompatibility issue between the server and the client
as the system is currently up with an IP address from the DHCP server)

How-To-Repeat: Start the installation of 4.1 through FTP method using DHCP.
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-10 11:18:37 UTC
State Changed
From-To: open->feedback

I'm pretty sure that you need to give us more info here. 
Could you send dmesg(8) output for the affected system so that 
the maintainer can see what network card you were using and 
can confirm that the network card was actually probed properly? 


Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-10 11:18:37 UTC
Responsible Changed
From-To: freebsd-bugs->obrien

Over to the maintainer.
Comment 3 muthu 2000-08-10 18:54:59 UTC
Hi,

	The network was indeed probed without any problems. I found
something strange yesterday. After I changed /etc/rc.conf to use DHCP &
rebooted it the first time, the system came up fine. When I rebooted it
yesterday evening (after I filed the PR), the system did not come up
(after displaying something related to 'hostname' while booting). I left
it and today morning, I found that the system is up.

Regards,
Muthu

dmesg output:
------------

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
       The Regents of the University of California. All rights reserved.
FreeBSD 4.1-RELEASE #0: Thu Jul 27 04:44:16 GMT 2000
    root@usw4.freebsd.org:/usr/src/sys/compile/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (398.27-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory  = 134217728 (131072K bytes)
config> di sn0
config> di lnc0
config> di le0
config> di ie0
config> di fe0
config> di ed0
config> di cs0
config> q
avail memory = 126398464 (123436K bytes)
Preloaded elf kernel "kernel" at 0xc040d000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc040d09c.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <ATI Mach64-GB graphics accelerator> at 0.0 irq 9
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x2000-0x207f mem 0x41100000-0x4110007f irq 11 at device 13.0 on pci0
xl0: Ethernet address: 00:50:04:87:44:3f
miibus0: <MII bus> on xl0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: <Intel 82371AB PCI to ISA bridge> at device 20.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0x20a0-0x20af at device 20.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> at device 20.2 on pci0
uhci0: Invalid irq 255
uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS
device_probe_and_attach: uhci0 attach returned 6
chip1: <Intel 82371AB Power management controller> port 0xfc00-0xfc0f at device 20.3 on pci0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppi0: <Parallel I/O> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
plip0: <PLIP network interface> on ppbus0
ad0: 6149MB <FUJITSU MPD3064AT> [13328/15/63] at ata0-master using UDMA33
acd0: CDROM <LTN323> at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s2a



> 
> Synopsis: Installation (over internet) does not work with DHCP; stops at "Scanning for DHCP servers"
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: sheldonh
> State-Changed-When: Thu Aug 10 03:18:37 PDT 2000
> State-Changed-Why: 
> I'm pretty sure that you need to give us more info here.
> Could you send dmesg(8) output for the affected system so that
> the maintainer can see what network card you were using and
> can confirm that the network card was actually probed properly?
> 
> 
> Responsible-Changed-From-To: freebsd-bugs->obrien
> Responsible-Changed-By: sheldonh
> Responsible-Changed-When: Thu Aug 10 03:18:37 PDT 2000
> Responsible-Changed-Why: 
> Over to the maintainer.
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=20513
>
Comment 4 David E. O'Brien freebsd_committer freebsd_triage 2000-11-10 18:01:40 UTC
State Changed
From-To: feedback->closed

It sounds like a sysinstall problem, not dhclient one.  Since 4.1 isn't the 
current release, I'm closing this unless someone sees the same problem 
with 4.2 {beta,RC,release}.