> Hazel Russman wrote: > > My LFS system boots successfully but so far I have no ethernet. The > > driver (built into the kernel) is e1000e and dmesg shows that this > > driver has registered itself. Some time later I can see: > > > > Bringing up the eth0 interface....stty: standard input: > > inappropriate ioctl for device. > > > > Then, when systemd tries to assign the address to the interface in > > [email protected], it reports that eth0 does not exist. > > > > At first I thought it might have been given one of those new names > > that have caused so much annoyance, but in that case the name should > > show up in ifconfig and in sys/class/net. In fact both show lo only. > > Also I cannot get an eth0 interface by masking the udev net-naming > > rules file with a link of the same name to /dev/null > > in /etc/udev/rules.d. > > > > This is the first time I have used systemd on this particular > > computer. > > If nothing shows up in /sys/class/net it's almost certainly a driver > or firmware problem. > > I do have a card that uses the e1000e driver. It does not need any > firmware. Do you have lines in dmesg similar to: > > From lspci: > 00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit > Network Connection (rev 02) > > From dmesg: > [ 1.288693] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. > [ 1.480406] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network > Connection
Yes, this is what I meant when I said I had seen the driver registering itself. > > If udev is renaming it, then *something* should show up > in /sys/class/net. > > -- Bruce That's what I thought! The card doesn't need firmware. I have built kernels before on this machine and all that is normally required is the e1000e driver. It worked flawlessly in LFS7.4 with sysvinit. I don't have pciutils in lfs but here is the relevant line from one of my other distros: 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) And here are the relevant lines from the systemd journal: -- Reboot -- May 11 18:54:15 compaq kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI May 11 18:54:15 compaq kernel: e100: Copyright(c) 1999-2006 Intel Corporation May 11 18:54:15 compaq kernel: e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI May 11 18:54:15 compaq kernel: e1000: Copyright (c) 1999-2006 Intel Corporation. -............................................ May 11 18:54:15 compaq kernel: Netfilter messages via NETLINK v0.30. May 11 18:54:15 compaq kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max) May 11 18:54:15 compaq kernel: ctnetlink v0.93: registering with nfnetlink. May 11 18:54:15 compaq kernel: ip_tables: (C) 2000-2006 Netfilter Core Team May 11 18:54:15 compaq kernel: TCP: cubic registered May 11 18:54:15 compaq kernel: Initializing XFRM netlink socket May 11 18:54:15 compaq kernel: NET: Registered protocol family 17 May 11 18:54:15 compaq kernel: Key type dns_resolver registered .............................................. May 11 18:54:15 compaq kernel: console [netcon0] enabled May 11 18:54:15 compaq kernel: netconsole: network logging started .............................................. May 11 18:54:15 compaq kernel: NET: Registered protocol family 10 ............................................. May 11 18:54:15 compaq systemd[1]: Inserted module 'ipv6' May 11 18:54:15 compaq systemd[1]: Set hostname to <compaq>. ........................................................... May 11 18:54:15 compaq systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device... ..................................................... May 11 18:54:15 compaq systemd[1]: Starting system-ifupdown.slice. May 11 18:54:15 compaq systemd[1]: Created slice system-ifupdown.slice. ................................................................. May 11 18:54:18 compaq systemd[1]: Starting Start ifupdown for eth0... May 11 18:54:18 compaq systemd[1]: Started Start ifupdown for eth0. ....................................................... May 11 18:54:18 compaq ifup[140]: stty: standard input: Inappropriate ioctl for device May 11 18:54:18 compaq ifup[140]: Bringing up the eth0 interface... stty: standard input: Inappropriate ioctl for device May 11 18:54:18 compaq ifup[140]: Adding IPv4 address 192.168.2.100 to the eth0 interface...Cannot find device "eth0" May 11 18:54:18 compaq ifup[140]: [22B blob data] May 11 18:54:18 compaq ifup[140]: [51B blob data] May 11 18:54:18 compaq systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE May 11 18:55:44 compaq systemd[1]: Job sys-subsystem-net-devices-eth0.device/start timed out. May 11 18:55:44 compaq systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device. It looks very much as if the operation that is supposed to bring up eth0 failed because of an extraneous error. If I set the option for IPV6 tunnelling, I get a device called sit0, which I can bring up by hand using ifup (systemd's ifup service ignores it). Unfortunately, I can't actually use it; it won't talk to my router. I am thinking of creating another partition and building a 7.5 LFS with sysvinit but with the same kernel configuration. If this works, the problem must be with udev or systemd; if not, then I've misconfigured my kernel. -- -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
