On 31/08/16 at 13:15 +0800, Paul Wise wrote:
> On Wed, 2016-08-31 at 07:10 +0200, Lucas Nussbaum wrote:
>
> > Well, FTR it's exactly the kind of hardware I was using yesterday
> > (with the current jessie installer)
>
> Did you try with the cable plugged into only eth1?
Yes.
> If so, I guess t
On Wed, 2016-08-31 at 07:10 +0200, Lucas Nussbaum wrote:
> Well, FTR it's exactly the kind of hardware I was using yesterday
> (with the current jessie installer)
Did you try with the cable plugged into only eth1?
If so, I guess this is fixed.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On 31/08/16 at 11:26 +0800, Paul Wise wrote:
> On Tue, 2016-08-30 at 17:48 +0200, Lucas Nussbaum wrote:
>
> > What you put in the preseeding file has no effect for network
> > detection (at least in the case where this file is fetched over the
> > network).
>
> The preseeding I was talking about
On Tue, 2016-08-30 at 17:48 +0200, Lucas Nussbaum wrote:
> What you put in the preseeding file has no effect for network
> detection (at least in the case where this file is fetched over the
> network).
The preseeding I was talking about was added to the ISO IIRC.
> So it's possible that this bu
On 24/04/15 at 09:38 +0200, Lucas Nussbaum wrote:
> On 18/02/13 at 07:28 +0800, Paul Wise wrote:
> > On Sun, 2013-02-17 at 23:24 +0100, Philipp Kern wrote:
> >
> > > Now I'm not sure why we're checking for a link in netcfg_autoconfig
> > > again without error handling, but why does it try the wron
On 18/02/13 at 07:28 +0800, Paul Wise wrote:
> On Sun, 2013-02-17 at 23:24 +0100, Philipp Kern wrote:
>
> > Now I'm not sure why we're checking for a link in netcfg_autoconfig
> > again without error handling, but why does it try the wrong ifname in
> > the first place? In the auto selection proce
On Sun, 2013-02-17 at 23:24 +0100, Philipp Kern wrote:
> Now I'm not sure why we're checking for a link in netcfg_autoconfig
> again without error handling, but why does it try the wrong ifname in
> the first place? In the auto selection process we should've picked
> one earlier that had a link al
On Mon, Feb 11, 2013 at 04:44:50PM +0800, Paul Wise wrote:
> This is because the autoconfig code doesn't check the result of the link
> detection code and return that to upper layers (see below).
I think I'm missing something. Why is the autoconfig code at fault?
We'll start in GET_INTERFACE, ite
Package: netcfg
Severity: normal
Tags: d-i
netcfg/choose_interface=auto in preseeding or on the installer kernel
command-line fails to choose the right interface when the first
interface has no link. This is annoying for automated installs from CD.
For netboot installs, it is possible to use the p
9 matches
Mail list logo
