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

Bug#248256: installation report

Package: installation-reports

Debian-installer-version: sarge-i386-businesscard.iso, May 7, 2004
uname -a: Linux mercury 2.4.26-1-686 #3 Sun Apr 18 21:17:21 EST 2004
i686 GNU/Linux
Date: May 8, 2004
Method: installed from businesscard cd, booted from cd, just hit enter
at initial prompt
Machine: home built
Processor: intel pentium-III 733MHz
Memory: 448MB
Root Device: IDE, WD 40GB, 7200rpm, 8MB cache
Root Size/partition table: 
# /etc/fstab: static file system information.
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda5       none            swap    sw              0       0
/dev/hda1       /               reiserfs defaults        0       1
/dev/hda6       /home           reiserfs defaults        0       2
/dev/hdc        /media/cdrom    iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy   auto    rw,user,noauto  0       0
/dev/hdc        /cdrom          iso9660 ro,user,noauto  0       0

Output of lspci:
pcilib: Cannot open /sys/bus/pci/devices
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8605 [ProSavage
PM133] (rev 81)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8605 [PM133 AGP]
0000:00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super
South] (rev 22)
0000:00:04.1 IDE interface: VIA Technologies,
Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE
(rev 10)
0000:00:04.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0
controller] (rev 10)
0000:00:04.3 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0
controller] (rev 10)
0000:00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo
Super ACPI] (rev 30)
0000:00:0e.0 Multimedia audio controller: Creative Labs SB Live!
EMU10k1 (rev 08)
0000:00:0e.1 Input device controller: Creative Labs SB Live! MIDI/Game
Port (rev 08)
0000:00:0f.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
100] (rev 02)
0000:00:10.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo
3 (rev 01)

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


Overall great.  Problem with DHCP:

On a clean boot I don't have any DNS servers configured in
/etc/resolv.conf.  To my knowledge, there is nothing unusual about my

I installed "testing" when given the choice, and just stuck with
defaults as far as I can remember.  This means I have the package
dhcp-client installed, not dhcp3-client.

ifup -a gets run by /etc/init.d/networking, and this fails to properly
configure the dns servers.  It does however retrieve the dns server
information and store it in /var/run/dhclient.eth0.leases:

lease {
  interface "eth0";
  option subnet-mask;
  option routers;
  option domain-name-servers,,,;
  option domain-name "bc.hsia.telus.net";
  option dhcp-lease-time 345600;
  option dhcp-message-type 5;
  option dhcp-server-identifier;
  renew 3 2004/5/12 04:00:15;
  rebind 4 2004/5/13 16:00:15;
  expire 5 2004/5/14 04:00:15;

I think the script /etc/network/if-up.d/000resolvconf should set
things up here, but the $R environment variable contained within
remains unset (presumably this means that the $IF_DNS_DOMAIN,
not set).  I don't know why.  I guess ifup doesn't properly set those
when it runs dhclient?

"ps ax | grep dhclient" returns:
4294 ?        Ss     0:00 dhclient -e -pf /var/run/dhclient.eth0.pid
-lf /var/run/dhclient.eth0.leases eth0

I guess those are the options used by ifup.  Running dhclient after
boot (as root) with no options on the command line gets things running
(as would fixing it manually...).

Looked at the README for resolvconf and it does not mention
dhcp-client, only dhcp3-client, which I guess isn't used in d-i by
default yet.

Unsure why I haven't seen other reports of this...

Scott Webster

Reply to: