Bug#239284: debian-installer: network started before pcmcia modules
Followup-For: Bug #239284
After successful first pass of debian installer, network is not
available after reboot.
Machine: Dell Latidude CP M200
200 MHz Pentium
PCMCIA ethernet card (3c575)
After first reboot, pcmcia modules are loaded
(yenta_socket, ds, pcmcia_core) and the appropriate driver
(3c59x) is also loaded, but only lo is up.
In particular, doing the initial package install via the network
fails. Issuing /etc/init.d/networking restart forcing the dhcp server
to be querried and eth0 to be brought up.
This is a common problem on many laptop installations. I find that I
often must make a local entry in /etc/init.d/ and a "late" link in rc2.d
to restart the networking.
The problem is that the networking tries to come up before pcmcia, and
so fails. I suppose you could automatically restart the network if
choosing a network option for installing packages, or alternatively,
you could add a screen upon failure of dselect to optionally restart
But in point of fact, this problem persists beyond the installation
of debian. The network must always be restarted manually, or done
automatically in an init.d script late in the boot process.
Would it be detrimental to restart the network late in the boot
process? It at least has the advantage of not requiring those without
previous experience to scratch their heads about how to get networking up.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.5-0
Locale: LANG=C, LC_CTYPE=C