On 171226-20:04+0100, J. Fahrner wrote:
> Am 2017-12-26 19:41, schrieb Miroslav Rovis:
> > What ethers you have? Try:
> >
> > # ip l show
>

> $ ip l show
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
> DEFAULT group default qlen 1
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state
> DOWN mode DEFAULT group default qlen 1000
>     link/ether 3c:97:0e:cb:ce:d7 brd ff:ff:ff:ff:ff:ff
> 3: wwan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
> group default qlen 1000
>     link/ether 26:77:58:61:50:ac brd ff:ff:ff:ff:ff:ff
> 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
> DORMANT group default qlen 1000
>     link/ether 6c:88:14:9d:7d:70 brd ff:ff:ff:ff:ff:ff

So the drivers are compiled fine and working.

> eth0 works normal in network-manager.
I don't use network-manager.
> The error is only during boot. I'm
> wondering why ifup tries to activate eth0, since this is not in
> /etc/network/interfaces. Where does this info come from, that it should
> enable eth0? Does it come from udevd?
Dunno. Look up:

/etc/init.d/networking
/etc/default/networking
/run/network/*

for clues...

Ah, I remember on Gentoo (long months ago now that I'm not running it), if you didn't want an interface, or wanted no interface, we could set it up in the conf file of our package which was/is called netifrc IIRC.

Maybe you shouldn't just leave /etc/network/interfaces completely unconfigured... But don't know.

BTW I'm running Ceres, which is probably certainly less comfortable than Ascii, a suspected bugs here and there (never yet time enough to study them and report them --it's also insfufficient knowledge--), or simply incompletenesses... I hoped otherwise, but Ceres almost looks to big to me to digest :-( . Will still be trying to sort it for a little while longer...

Regards!
--
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr