Bug#288522: debian-installer: details on stage 1 detection of firewire interfaces

[Michael Gilbert <zero79@cox.net>]

Package: debian-installer
Followup-For: Bug #288522

Ok, I booted the installer with "linux26."  After the "network hardware
detection" in stage 1, I am presented with the option to choose my main
network interface from only:

	eth0: 3com card
	eth1: wireless ethernet

Obviously, firewire is not included here.  Also, doing a dmesg yields no
indication that the firewire hardware had been started.  I didn't think about
doing an lsmod at the time, but I assume that the ieee1394, ohci1394, and 
eth1394 kernel modules were not loaded.  Perhaps all that is needed would be to
load these modules during the "network hardware detection" step?  Then
the stage 1 would be in the same state as stage 2 in terms of available
network interfaces.

In terms of robustness, it may be a good idea to think about any other 
potential network interfaces that will be available by default during
stage 2 that should also be enabled during network hardware detection in 
stage 1.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)