Bug#226821:
tags 226821 d-i
clone 226821 -1 -2
severity -1 wishlist
retitle -1 ethdetect: give more information about network adapters found
reassign -1 ethdetect
tags -2 moreinfo
retitle -2 ethdetect: detects cards in different order as after install
reassign -2 ethdetect
close 226821
thanks
Hi.
I'm going through older installation reports to sort out things
that have not yet been fixed. I have split out some parts of
your report and reassigned them to the appropriate package
and am closing the bug now.
Thanks for your help.
On Thu, Jan 08, 2004 at 02:43:46PM -0500, Doug Larrick wrote:
> Base System Installation Checklist:
>
> Initial boot worked: [O]
> Configure network HW: [O]
> Config network: [E] *1
> 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: [E] *2
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Comments/Problems:
>
> *1: This system has two network adaptors, one wired and one wireless.
> Both were detected and had their drivers set up properly. In the
> installer screen, I chose the wrong device and had to start over to
> correct this mistake -- both adaptors were identified with the same text
> ("10/100 Ethernet" or something like that). Any one change out of the
> following list would have allowed me to continue the installation without
> that reboot:
> * in the list of network adaptors, further identify them (by MAC address
> and/or by which driver controls the adaptor)
I tested this with Beta 4 and my two cards are at least titled
"Wireless" and "Ethernet", so I could distinguish between them.
> * detect what network adatptor has a link (via the mechanisms used in
> package 'ifplugd' or something similar) and default to that one
> * Once DHCP has failed to negotiate a lease, present the user with an
> opportunity to re-select which network adaptor to use
> * If the chosen device is a wireless adaptor, present the user with an
> opportunity to enter a WEP key
this belongs to ethdetect, I guess. Can't test these issues, so
reassigning for now.
> *2: After the installation and reboot, the two network adaptors were
> detected in the opposite order, so that the wired card (that was eth0
> during install) was now eth1, and the wireless card (that was eth1 during
> install) was now eth0. This problem was easy to fix with appropriate
> entries in /etc/modules (so the drivers are forced to load in the proper
> order).
Hmm, don't know if this is still present. Reassigned, too. Can you test
this with Beta 4?
> One other problem -- not sure if this belongs here or as a bug for
> base-config: upon selecting a mirror for apt, it went off and did its
> apt-get update magic, then prompted me once again for a mirror. Thinking
> it did not like the mirror I had chosen, I chose another. And another.
> Only upon manually editing my sources.list file was I allowed to proceed.
This problem should be fixed in current versions of d-i.
Gruesse,
--
Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/
Reply to: