I want to bring bug #243448, which I've just reassigned to discover1-data, to your attention. I'm afraid it may represent a whole class of bugs. It seems that newer versions of discover fail to load modules for many ethernet cards. The reporter of this bug did an excellent isolation of the problem, though the discover-data version he upgraded to was a little old -- it would be nice if he could try again with unstable's discover1-data: > since i was able to work-around the problem with the > netinst daily build used, i went back to beta3 d-i and > installed from scratch on the same system, following > the walkthrough i logged earlier, except i skipped > over the automatic updating of base-system that occurs > after base-config reboot. > > i used aptitude to upgrade a single package at a time > in the base-system, in this order, and it didnt take > long to find the source of the problem (what causes > the 8139too module not to load automatically). i > tested the network using 'ping www.google.com', > rebooted and tested network again after each package > was upgraded.. > > sysvinit .. ok > > sysv-rc .. ok > > initscripts .. ok > > discover-data .. network lost > it's version 2.2004.02.24-5 and replaced > 1.2004.02-08-1 > > i double-checked by repeating the installation process > from the beginning with beta3, including skipping > base-system updates, and then upgraded only > discover-data. same results. network lost on reboot. A few other installation reports that mention a network that worked during d-i, but failed on reboot include #243895, #244744, #244744, #244665. They seem to cover most of the common network drivers. -- see shy jo
Attachment:
signature.asc
Description: Digital signature