[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#265651: (no subject)

Package: installation-reports

Debian-installer-version: rc1
uname -a: Linux acer 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004 i686 unknown 
Date: Aug 14 04:26:38
Method: Bootable sarge-i386-netinst.iso CD

Machine: Acer Travelmate 371TCi
Processor: Intel(R) Pentium(R) M processor 1400MHz
Memory: 512MB
Root Device: IDE /dev/hda5
Root Size/partition table:
/dev/hda1               1        1044     8385898+   c  W95 FAT32 (LBA)
/dev/hda2            1045        3132    16771860   a5  FreeBSD
/dev/hda3            3133        5628    20049120    5  Extended
/dev/hda5   *        3133        5078    15631213+  83  Linux
/dev/hda6            5079        5141      506016   82  Linux swap
/dev/hda7            5142        5628     3911796   83  Linux
Output of lspci:
0000:00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02)
0000:00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control Registers (rev 02) 0000:00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration Process Registers (rev 02) 0000:00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 0000:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03) 0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03) 0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03) 0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 03) 
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 83)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03) 0000:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 03) 0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03) 0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03) 0000:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03) 
0000:02:01.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05)
0000:02:09.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
0000:02:09.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
0000:02:09.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 04) 0000:02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 

Base System Installation Checklist:

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [E]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
The DHCP configuration got stuck in an endless loop. The installation screen on DHCP configuration would come up with 0%, proceed to 100%, claim success, then disappear only to reappear back at 0%, proceed to 100%, claim success, etc. There was no opportunity given to the user to break out of this endless loop.
My initial thought was to disable DHCP configuration as explained in one of the menus at the start of the CD boot, netcfg/disable_dhcp=true. This had absolutely no effect whatsoever, the installation system continued to use DHCP and be stuck in the endless loop.
My second thought was to remove the network cable. This resulted in two different behaviours, depending on when I removed the cable:
If the cable was removed before the DHCP configuration screen then it would fall into the static configuration screens from which I was able to proceed.
If the cable was removed the absolute instant after the 100%/success message the loop would be broken and the next screens would be set hostname, set domainname from which I could proceed. The hostname was automatically set correctly, ie, the installation system did indeed have success with DHCP. 

The subsequent installation and networking worked fine.
Attached is the syslog showing failure with cable in then success after cable is yanked. 

_________________________________________________________________
Play Love Hunt to win a $9000 holiday and find love! http://mobilecentral.ninemsn.com.au/mclovehunt/lovehunt.aspx

Attachment: syslog
Description: Binary data

Reply to: