Re: Preseeded installer uses avahi instead of waiting DHCP
- To: email@example.com
- Subject: Re: Preseeded installer uses avahi instead of waiting DHCP
- From: Дмитрий Огородников <firstname.lastname@example.org>
- Date: Sun, 1 Jan 2012 23:10:14 +1000
- Message-id: <[🔎] CACJDdd-HXkVYz+tsc_F+CThiwND2zkA-Z9V0swGRixWv6-f1cQ@mail.gmail.com>
- In-reply-to: <CAOdo=Sz_yZxD02RbMgmjaAY1ogq1Bz3C=X7ebbB-51mWZb_fZw@mail.gmail.com>
- References: <CACJDdd-1HhABH=aQGZ0ZOy9y17WQkFh4toy34ZSFwdqEmSVpmA@mail.gmail.com> <4EFA8741.email@example.com> <CAOdo=SyH3p90rHTKMEEJ7ofMR95NV3kDiRjyX397vy9rP2JZeQ@mail.gmail.com> <4EFAE5C0.firstname.lastname@example.org> <CAOdo=Sz_yZxD02RbMgmjaAY1ogq1Bz3C=X7ebbB-51mWZb_fZw@mail.gmail.com>
> I assumed that the "4" was a typo because the ipv4 link-local
> addresses are as you describe them above. :(
Yes, it was, sorry.
Problem solved, thanks you all.
Computer was IBM x3550 with two NetXreme2 cards. By default, Debian
doesn't have appropriate driver (it's non-free). Commonly, when
installer cannot find network card, he asks user for driver. BUT new
revision of x3550 (M3) has a management card ("USB Net"), and Debian
has a driver for this card. Installer finds this card and uses it as
the primary one (despite no link).
Inserting USB-flqash with bnx2 driver and forcing installer to read it
solves this problem.