no ethernet after cold boot

no ethernet after cold boot

Postby tjkupp » Jan 20th, '18, 00:29

First boot after power on has network center icon with "x" in system tray. Hovering over it produces balloon message, "Network is down on interface Wired (Ethernet) (eno1)." Left clicking it opens network center showing "Intel Corporation 82579X Gigabit Network Connection." Clicking on this and then clicking "Connect" does nothing. Clicking on "Configure" opens error message box which says "Unable to find network interface for selected device (using e1000e driver." I click "Leave" then "Restart" and network is up. This happens every time after a cold boot. I tried removing and adding the Ethernet card in MCC to no effect. Logging out and back in again has no effect. I compared the results from dmesg after cold boot to the results after warm boot. There were some differences, but nothing that meant anything to me. I edited ifcfg-eno1 changing LINK_DETECTION_DELAY value from 6 to 8, 10, 20 and 40. Network still down on cold boot. Does any body have any idea how to fix this?
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby tjkupp » Jan 20th, '18, 19:38

Oops! I forgot to say it's Mageia 5 KDE.
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby doktor5000 » Jan 21st, '18, 12:21

What you could try is compare the logs from a cold boot to the ones from the reboot afterwards and see where the difference is. As root run
Code: Select all
journalctl -ab > /tmp/bootlog_cold.txt
on the cold boot and then reboot and run
Code: Select all
journalctl -ab > /tmp/bootlog_reboot.txt
and then compare /tmp/bootlog_cold.txt to journalctl -ab > /tmp/bootlog_reboot.txt maybe in something like kdiff3 but you may need to ignore the first column, which is the timestamp which obviously differs between the two.

For omitting the timestamps, see e.g. https://stackoverflow.com/questions/440 ... ime-stamps
or https://unix.stackexchange.com/question ... -timestamp to get a general idea about this.
kdiff3 also has an option to run a preprocessor on the comparison files: http://kdiff3.sourceforge.net/doc/preprocessors.html
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14541
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: no ethernet after cold boot

Postby benmc » Jan 22nd, '18, 01:45

I too have had this issue intermittently on one system.

for me the fix is power cycle the modem.
(if I boot the system to desktop before powering up the modem, this issue (for me) never occurs.)
benmc
 
Posts: 683
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: no ethernet after cold boot

Postby wintpe » Jan 22nd, '18, 12:59

perhaps pick a static address for this instead of DHCP.

something thats likely to be out of the way of the routers dhcp daemon,

if possible to administer the router you can restrict the range it manages for DHCP so that theres a space for static addresses that are having this problem.

then it wont depend on the router for its settings.

with that static setting you will need to set your default route, dns, and subnetmask

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1177
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: no ethernet after cold boot

Postby tjkupp » Jan 22nd, '18, 20:29

Not quite sure how to set static address (I'm a bit new at this). When I hover over the network icon in system tray (when network is up) it shows IP address: 192.168.2.159, (another computer on same network is 192.168.2.160), Gateway: 192.168.2.1, and DNS 192.168.2.1. Would these be appropriate or should I pick something well away from 159?
Thanks!
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby wintpe » Jan 22nd, '18, 21:04

ok great feedback thats what we like

if you are using the netapplet you can double click on the wired lan and then i thing under wireless its quite obvious.

if not just pick network under mga control center and do it their its quite intuitive

you just need to change from dhcp on the nic to static.

once you do this the feilds to take the settings you want will be presented.

if you have only one thing on your network you could pick any address.

if you have more than one theres always a possibility that dhcp will give out the address you picked.

thats why i said if you can get into your router, there should be a way to restrict the range.

its probably set to 2-254 at the moment, but you could restrict that to 128-254 , that gives you 127 dhcp assignments and 127 static.

should be enough for most samll business or home use.

somethings just dont make sense being dhcp, ie an internal webserver, fileserver etc.

laptops, tablets phones, etc all need to be dhcp.

so back to the addresses you pick.

your network from what you have told me is

192.168.2.0

your netmask will be 255.255.255.0

your dns can be your ISP's dns , or your routers dns or 8.8.8.8 ie googles dns

your default gateway is 192.168.2.1

the address above depends on what you can achieve above, but for now and simplicity just pick anything 192.168.2.2 for example.

from the addresses you have shown me so far, your router may even have the range restricted as i suggested.

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1177
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: no ethernet after cold boot

Postby tjkupp » Jan 23rd, '18, 04:08

As wintpe suggested, I tried a few static ip addresses distant from 192.168.2.159, but there was no change in behavior. I'm also baffled by the facts that: 1) the system behaved perfectly since I installed Mageia 5 shortly after it was released, until the problem appeared suddenly a few weeks ago; 2) my wife's computer (different hardware, same OS, also on the network) behaves perfectly; 3) both are dual boot systems with Windows XP, and XP has no problems; 4) live DVD's of Mageia 5, Mageia 6, and PClinuxOS all work perfectly.

As doctor5000 suggested, I compared journalctl outputs. There were some differences, notably the cold boot version has "kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000, kernel: pci 0000:00:16.0: reg 0x10: [mem 0xfe428000-0xfe42800f 64bit], and kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold," and later mei-me references to failures on the same pci 0000:00:16.0. The reboot version has none of this.

Arg!
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby wintpe » Jan 23rd, '18, 11:44

did you update the kernel or are you still on the DVD install version.

if so try a few different kernels , maybe there is a genuine bug in one of the newer kernels with that NIC, which i also have in my syste,m, but dont see any issues with.

but nics also have firmware and variations in that can bring incompatibilities. Is your bios at the latest version.

Ive seen asrock am3+ boards have a nic issue with linux due to its bios being behind for example.

https://www.asrock.com/MB/NVIDIA/N68-GS ... x.asp#BIOS

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1177
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: no ethernet after cold boot

Postby tjkupp » Jan 24th, '18, 01:06

Well, Peter, my current kernel is 4.4.111-1.mga5. I also tried 4.4.105-1.mga5, 4.4.92-1.mga5, and 4.4.88-1.mga5. I'm pretty sure ...111... is the latest, since I always heed the notices that an update is available. They all behave the same. I happened to notice that after a bad (cold) boot and clicking "Leave" and then "Turn Off Computer" doesn't finish It stalls at the Mageia splash screen, and I have to push the machine's power button. Motherboard is Intel DH16CR. I'm a little leery of doing a BIOS update, since I read that Intel doesn't recommend it unless it's really needed. I'm starting to wonder if reinstalling Mageia makes sense. Cheers, Tom
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby wintpe » Jan 24th, '18, 12:41

im not sure this will magicaly be fixed by a reinstall, its not that sort of problem.

have you got any pcie nics lying around.

silly question, i have loads, so i assume anyone whose messing around with computers might,.

but its something you can try. you can get pice nics off of ebay for less than £20

mageia 6 is great except fro a few minor issues that you might see reported i still use it for all my systems and left mga5 behind.

I cant promise it will fix your problem.

ive checked your bios, nothing there for the onboard lan, what about the router, what make / model / firmware update?



regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1177
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: no ethernet after cold boot

Postby tjkupp » Feb 3rd, '18, 05:08

Since I had no nic's lying about, I bought one from Amazon. I disabled the onboard in the bios, plugged in the new one, and moved the cable. Booted and no connection. Rebooted but still no connection. I'm baffled.
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby jiml8 » Feb 3rd, '18, 20:32

I guess I no longer know how networks are started in a stock Mageia system. I just rooted around in my Mageia 6 workstation, and some things I expected to find in /etc/udev.d/rules.d are now gone, absorbed into that giant green blob that is consuming the system which is called systemd.

However, my network starts without issue. I have 3 NICs in this box, and all work. I do not use network manager; for my purposes it is beyond useless. I do use the Mageia network applet, though I am at least equally likely to just do things from the command line and (when needed) write a systemd service to invoke whatever scripting I have set up.

When I look into what is running, I see a lot of the historical stuff I am used to seeing, and when I grep my way around /etc, I find references to some of the ancient historical stuff that I have always used. But, given the age of this system (continuous history for 20 years now) I guess I'm not sure those things are still being used.

So, with that preface, it seems to me that you have two choices in how to proceed.

You can try to start it the "new" way, which you apparently don't understand, wintpe also apparently does not understand, and that I evidently do not understand either.

Or you can go with a more traditional way to start the network, which will certainly work although it might not be the "right way" in today's world.

To do it this latter way, I think the best approach is to begin by finding out what state your networking system is, on first boot.

To do this, upon startup (and before you do anything to start the network) as root please enter the following commands, and report the results here:
Code: Select all
ifconfig
route
ps ax | grep dhclient


Also, please report the contents of the directory /etc/sysconfig/network-scripts.

Working from this info, we'll get your network to start on boot, every time.
jiml8
 
Posts: 979
Joined: Jul 7th, '13, 18:09

Re: no ethernet after cold boot

Postby tjkupp » Feb 3rd, '18, 21:21

Here's what I got:
Code: Select all
[root@Daisy tom]# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 959  bytes 89281 (87.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 959  bytes 89281 (87.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Code: Select all
[root@Daisy tom]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface


Code: Select all
[root@Daisy tom]# ps ax | grep dhclient
 6236 pts/1    S+     0:00 grep --color dhclient


Code: Select all
[root@Daisy /]# cd /etc/sysconfig/network-scripts
[root@Daisy network-scripts]# ls
cellular.d/     ifdown@       ifdown-ipv6*    ifdown-tunnel*  ifup-eth*    ifup-post*    ifup-wireless*          wireless.d/
hostname.d/     ifdown-bnep*  ifdown-post*    ifup@           ifup-hso*    ifup-ppp*     init.ipv6-global*
ifcfg-eno1*     ifdown.d/     ifdown-ppp*     ifup-aliases*   ifup-ipv6*   ifup-routes*  network-functions
ifcfg-lo*       ifdown-eth*   ifdown-routes*  ifup-bnep*      ifup-plip*   ifup-sit*     network-functions-ipv6
ifcfg-vboxnet0  ifdown-hso*   ifdown-sit*     ifup.d/         ifup-plusb*  ifup-tunnel*  vpn.d/
Last edited by isadora on Feb 3rd, '18, 21:24, edited 1 time in total.
Reason: Placed command-output in between [CODE]-tags for better readability ;)
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby doktor5000 » Feb 4th, '18, 01:12

Well, no ethernet device was detected, so it seems.

Please also provide the output of the following commands:

Code: Select all
lspcidrake -v
ps -ef | grep -v grep | grep -iE "net|wpa"


and, as root:
Code: Select all
systemctl status network.service -al -n150
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14541
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: no ethernet after cold boot

Postby tjkupp » Feb 4th, '18, 05:33

Code: Select all
[tom@Daisy ~]$ lspcidrake -v
unknown         : Integrated Technology Express, Inc.|Device 8892 [BRIDGE_PCI] (vendor:1283 device:8892) (rev: 30)
ata_piix        : Intel Corporation|6 Series/C200 Series Chipset Family Desktop SATA Controller (IDE mode, ports 4-5) [STORAGE_IDE] (vendor:8086 device:1c08 subv:8086 subd:200d) (rev: 05)
i2c_i801        : Intel Corporation|6 Series/C200 Series Chipset Family SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:1c22 subv:8086 subd:200d) (rev: 05)
ata_piix        : Intel Corporation|6 Series/C200 Series Chipset Family Desktop SATA Controller (IDE mode, ports 0-3) [STORAGE_IDE] (vendor:8086 device:1c00 subv:8086 subd:200d) (rev: 05)
lpc_ich         : Intel Corporation|H61 Express Chipset Family LPC Controller [BRIDGE_ISA] (vendor:8086 device:1c5c subv:8086 subd:200d) (rev: 05)
ehci_pci        : Intel Corporation|6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [SERIAL_USB] (vendor:8086 device:1c26 subv:8086 subd:200d) (rev: 05)
shpchp          : Intel Corporation|6 Series/C200 Series Chipset Family PCI Express Root Port 1 [BRIDGE_PCI] (vendor:8086 device:1c10) (rev: b5)
snd_hda_intel   : Intel Corporation|6 Series/C200 Series Chipset Family High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:1c20 subv:8086 subd:200d) (rev: 05)
ehci_pci        : Intel Corporation|6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [SERIAL_USB] (vendor:8086 device:1c2d subv:8086 subd:200d) (rev: 05)
e1000e          : Intel Corporation|82579V Gigabit Network Connection [NETWORK_ETHERNET] (vendor:8086 device:1503 subv:8086 subd:200d) (rev: 05)
mei_me          : Intel Corporation|6 Series/C200 Series Chipset Family MEI Controller #1 [COMMUNICATION_OTHER] (vendor:8086 device:1c3a subv:8086 subd:200d) (rev: 04)
Card:Intel 810 and later: Intel Corporation|2nd Generation Core Processor Family Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:0102 subv:8086 subd:200d) (rev: 09)
unknown         : Intel Corporation|2nd Generation Core Processor Family DRAM Controller [BRIDGE_HOST] (vendor:8086 device:0100 subv:8086 subd:200d) (rev: 09)
hub             : Linux 4.4.111-desktop-1.mga5 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024)
usb_storage     : Generic|Mass Storage Device [Mass Storage|SCSI|Bulk-Only] (vendor:058f device:6364)
hub             : Terminus Technology Inc.|USB 2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:1a40 device:0101)
usbhid          : 2.4G KB|2.4G Mouse [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:1d57 device:0001)
usb_storage     : SanDisk|U3 Cruzer Micro [Mass Storage|SCSI|Bulk-Only] (vendor:0781 device:5406)
uvcvideo        : Logitech, Inc.|Webcam B500 [Video|Video Control] (vendor:046d device:0807)
Mouse:USB|Wheel : Microsoft|Microsoft 3-Button Mouse with IntelliEye(TM) [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:045e device:0040)
usbhid          : Logitech|USB Trackball [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:046d device:c408)
hub             : Linux 4.4.111-desktop-1.mga5 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024)
unknown         : HP|DeskJet 1110 series [Printer|Printer|Bidirectional] (vendor:03f0 device:df11)                             
hid_generic     : 2.4G KB 2.4G Mouse                                                                                           
hid_generic     : 2.4G KB 2.4G Mouse                                                                                           
hid_generic     : Generic Mass Storage Device
hid_generic     : Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)
hid_generic     : Logitech USB Trackball

[tom@Daisy ~]$ ps -ef | grep -v grep | grep -iE "net|wpa"
root        23     2  0 22:16 ?        00:00:00 [netns]
systemd+  3549     1  0 22:16 ?        00:00:00 /usr/lib/systemd/systemd-networkd
tom       5150  5041  0 22:18 ?        00:00:00 /usr/bin/perl /usr/bin/net_applet

[root@Daisy tom]# systemctl status network.service -al -n150
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: failed (Result: exit-code) since Sat 2018-02-03 22:17:00 EST; 6min ago
  Process: 3627 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Feb 03 22:16:57 Daisy systemd-sysctl[3655]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/51-alt-sysrq.conf'.
Feb 03 22:16:58 Daisy network[3627]: Bringing up loopback interface:  [  OK  ]
Feb 03 22:16:59 Daisy network[3627]: Bringing up interface eno1:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] e1000e device eno1 does not seem to be present, delaying initialization.
Feb 03 22:16:59 Daisy network[3627]: [FAILED]
Feb 03 22:17:00 Daisy network[3627]: Bringing up interface vboxnet0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device vboxnet0 does not seem to be present, delaying initialization.
Feb 03 22:17:00 Daisy systemd[1]: network.service: control process exited, code=exited status=1
Feb 03 22:17:00 Daisy systemd[1]: Failed to start LSB: Bring up/down networking.
Feb 03 22:17:00 Daisy systemd[1]: Unit network.service entered failed state.
Feb 03 22:17:00 Daisy systemd[1]: network.service failed.
Feb 03 22:17:00 Daisy network[3627]: [FAILED]
Last edited by Ken-Bergen on Feb 4th, '18, 05:49, edited 1 time in total.
Reason: Added code tags
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby jiml8 » Feb 5th, '18, 01:15

First thing, you need to get an ethernet device working.

Code: Select all
e1000e          : Intel Corporation|82579V Gigabit Network Connection [NETWORK_ETHERNET] (vendor:8086 device:1503 subv:8086 subd:200d) (rev: 05)


This is your ethernet controller. Since ifconfig does not show any ethernet device, most probably the driver is not being loaded at boot. You need either the e1000 or the e1000e driver (and based on the output, looks like it should be the e1000e.

Start by confirming the driver is not loaded. As root:
Code: Select all
lsmod | grep e1000


If the result of the command does not show one of those drives being present, then load it.

Now, I don't do this often enough, so I never remember the correct syntax and I usually have to try multiple variants to get it right.

As root, try these until you don't get an error message:
Code: Select all
insmod e1000e
or
insmod e1000e.ko
or
insmod e1000e.ko.xz
or
modprobe e1000e


One or more of these will work. Should you have any path problems, this driver is located in /lib/modules/(your kernel version ID)/kernel/drivers/net/ethernet/intel/e1000e.

if you look in /lib/modules you will see one or more directories that have the same name as the kernel you are running (you can find this with the command uname -r). That is the one you want.

In fact, you can directly reach that directory with this command:
Code: Select all
cd /lib/modules/`uname -r`/kernel/drivers/net/ethernet/intel/e1000e

Note that those are backticks surrounding the uname -r. On the US keyboard, the backtick is found to the left of the character 1 key.

Anyway, once you have the driver loaded, do an ifconfig and you should see your network adapter.

Now, you need to have this driver loaded on startup, and when it is then almost certainly your network will start automatically. Properly, this driver should go into the initrd and you would configure this using the dracut command. You are welcome to do a "man dracut" to learn about this command, but I will tell you that I don't know why that driver is not already in the initrd and I am not sure, off the top, how to configure dracut to add that driver. I would have to research it a bit. Wouldn't have to research it a lot, but I can't just tell you how to do it. I think there is a command line switch to tell it to "load this driver too".

But there is a quicker way, if you are willing to do it. Once again, this is very old-fashioned. I believe it is now deprecated but it still works.

There is a file called /etc/modules. In it, you place the name of any driver you want loaded that is not already being loaded. So all you do is edit that file (as root) using your favorite editor and add a line that says "e1000e" and nothing else (without the quotes...just the string e1000e).

You also can do it this way. As root:
Code: Select all
echo e1000e >>/etc/modules


Once you have told the system to load this driver at startup (using either method above), reboot the box and I will bet your network starts.
jiml8
 
Posts: 979
Joined: Jul 7th, '13, 18:09

Re: no ethernet after cold boot

Postby tjkupp » Feb 5th, '18, 01:36

Hmm... but why would it work fine after a warm boot?
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby tjkupp » Feb 5th, '18, 01:53

I get the same result after cold boot (not working) and after warm boot (working):

Code: Select all
[root@Daisy tom]# lsmod | grep e1000
e1000e                237568  0
ptp                    20480  1 e1000e
Last edited by isadora on Feb 5th, '18, 12:30, edited 1 time in total.
Reason: Placed command-output in between [CODE]-tags for better readability ;)
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby wintpe » Feb 5th, '18, 16:36

Hi tjcupp

well you did not pick a bad nic at all, you picked one of the most common , most well behaved nics there are.

I use these in all my systems as a preference, and neither mageia 5 or 6 has ever given me an issue with them.

I say this, as trying to get over your not seeing normal behavior of magia here.

I asked you a couple of weeks ago to test old kernels as ive been on mga6 for a while, i i considered that a newer one may have added
a problematic driver.

I also asked you to set it up statically as a static connection has no dependency on an external device except for its link, being established.

if it works after pushing it up, then maybe the router is not auto negotiating with the nic, but that would be really unusual as most routers and switches do, unless configured not to.

in mageia 5 i believe from memory /etc/udev/rules.d/70-network stores the mac address of the nic along with the name, to make it persistant across reboots.

if you added a new nic then that would become the next available device.

did that get populated on first boot with the new nics mac address.

all things to check.

while everything you are trying that people are suggesting to you to try, may help, its not normal to have to.

theres something we are all overlooking here.

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1177
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: no ethernet after cold boot

Postby jiml8 » Feb 5th, '18, 23:24

That situation is very odd. Very odd indeed.

Since the driver is loaded, you should have a network interface showing up in ifconfig.

I can speculate about what might be wrong, but that is all it would be...speculation. Things that come to mind right away include a flaky NIC that does not respond quickly enough when enumerated, and a flaky power supply. Possibly a bad cable, though I wouldn't expect that to cause this exact symptom...

When the network is not running try removing and reinstalling the driver. You would do this with:
Code: Select all
rmmod e1000e
insmod e1000e

as root, and with my previous caveats about syntax for insmod.

Does anyone here know offhand what the kernel tuneables are for that driver?
jiml8
 
Posts: 979
Joined: Jul 7th, '13, 18:09

Re: no ethernet after cold boot

Postby doktor5000 » Feb 5th, '18, 23:32

jiml8 wrote:Does anyone here know offhand what the kernel tuneables are for that driver?

modinfo <modulename> will show that in the options section for the module.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14541
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: no ethernet after cold boot

Postby jiml8 » Feb 5th, '18, 23:39

Just for fun, as root and while your network is not started, enter this command:
Code: Select all
sysctl -a


In the output, scroll to the section net.ipv4.conf, identify your ethernet adapter (you should see, for instance, net.ipv4.conf.l0 entries and there should be net.ipv4.conf.en0 - or something like that - entries that represent your NIC).

Copy and paste all that section here so we can look at it. There might be a clue to your problem in that data.

Then, get your network started, and do it again. Did any of the values change?
jiml8
 
Posts: 979
Joined: Jul 7th, '13, 18:09

Re: no ethernet after cold boot

Postby tjkupp » Feb 6th, '18, 06:41

Here's the section after cold boot:

Code: Select all
net.ipv4.conf.all.accept_local = 0
net.ipv4.conf.all.accept_redirects = 1
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.arp_accept = 0
net.ipv4.conf.all.arp_announce = 0
net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.arp_ignore = 0
net.ipv4.conf.all.arp_notify = 0
net.ipv4.conf.all.bootp_relay = 0
net.ipv4.conf.all.disable_policy = 0
net.ipv4.conf.all.disable_xfrm = 0
net.ipv4.conf.all.force_igmp_version = 0
net.ipv4.conf.all.forwarding = 0
net.ipv4.conf.all.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.all.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.all.ignore_routes_with_linkdown = 0
net.ipv4.conf.all.log_martians = 0
net.ipv4.conf.all.mc_forwarding = 0
net.ipv4.conf.all.medium_id = 0
net.ipv4.conf.all.promote_secondaries = 1
net.ipv4.conf.all.proxy_arp = 0
net.ipv4.conf.all.proxy_arp_pvlan = 0
net.ipv4.conf.all.route_localnet = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.send_redirects = 1
net.ipv4.conf.all.shared_media = 1
net.ipv4.conf.all.src_valid_mark = 0
net.ipv4.conf.all.tag = 0
net.ipv4.conf.default.accept_local = 0
net.ipv4.conf.default.accept_redirects = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.arp_accept = 0
net.ipv4.conf.default.arp_announce = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.arp_ignore = 0
net.ipv4.conf.default.arp_notify = 0
net.ipv4.conf.default.bootp_relay = 0
net.ipv4.conf.default.disable_policy = 0
net.ipv4.conf.default.disable_xfrm = 0
net.ipv4.conf.default.force_igmp_version = 0
net.ipv4.conf.default.forwarding = 0
net.ipv4.conf.default.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.default.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.default.ignore_routes_with_linkdown = 0
net.ipv4.conf.default.log_martians = 1
net.ipv4.conf.default.mc_forwarding = 0
net.ipv4.conf.default.medium_id = 0
net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.default.proxy_arp_pvlan = 0
net.ipv4.conf.default.route_localnet = 0
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.default.secure_redirects = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.default.shared_media = 1
net.ipv4.conf.default.src_valid_mark = 0
net.ipv4.conf.default.tag = 0
net.ipv4.conf.lo.accept_local = 0
net.ipv4.conf.lo.accept_redirects = 1
net.ipv4.conf.lo.accept_source_route = 1
net.ipv4.conf.lo.arp_accept = 0
net.ipv4.conf.lo.arp_announce = 0
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.arp_ignore = 0
net.ipv4.conf.lo.arp_notify = 0
net.ipv4.conf.lo.bootp_relay = 0
net.ipv4.conf.lo.disable_policy = 1
net.ipv4.conf.lo.disable_xfrm = 1
net.ipv4.conf.lo.force_igmp_version = 0
net.ipv4.conf.lo.forwarding = 0
net.ipv4.conf.lo.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.lo.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.lo.ignore_routes_with_linkdown = 0
net.ipv4.conf.lo.log_martians = 1
net.ipv4.conf.lo.mc_forwarding = 0
net.ipv4.conf.lo.medium_id = 0
net.ipv4.conf.lo.promote_secondaries = 0
net.ipv4.conf.lo.proxy_arp = 0
net.ipv4.conf.lo.proxy_arp_pvlan = 0
net.ipv4.conf.lo.route_localnet = 0
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.lo.secure_redirects = 1
net.ipv4.conf.lo.send_redirects = 1
net.ipv4.conf.lo.shared_media = 1
net.ipv4.conf.lo.src_valid_mark = 0
net.ipv4.conf.lo.tag = 0


Here's the section after warm boot:

Code: Select all
net.ipv4.conf.all.accept_local = 0
net.ipv4.conf.all.accept_redirects = 1
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.arp_accept = 0
net.ipv4.conf.all.arp_announce = 0
net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.arp_ignore = 0
net.ipv4.conf.all.arp_notify = 0
net.ipv4.conf.all.bootp_relay = 0
net.ipv4.conf.all.disable_policy = 0
net.ipv4.conf.all.disable_xfrm = 0
net.ipv4.conf.all.force_igmp_version = 0
net.ipv4.conf.all.forwarding = 0
net.ipv4.conf.all.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.all.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.all.ignore_routes_with_linkdown = 0
net.ipv4.conf.all.log_martians = 0
net.ipv4.conf.all.mc_forwarding = 0
net.ipv4.conf.all.medium_id = 0
net.ipv4.conf.all.promote_secondaries = 1
net.ipv4.conf.all.proxy_arp = 0
net.ipv4.conf.all.proxy_arp_pvlan = 0
net.ipv4.conf.all.route_localnet = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.send_redirects = 1
net.ipv4.conf.all.shared_media = 1
net.ipv4.conf.all.src_valid_mark = 0
net.ipv4.conf.all.tag = 0
net.ipv4.conf.default.accept_local = 0
net.ipv4.conf.default.accept_redirects = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.arp_accept = 0
net.ipv4.conf.default.arp_announce = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.arp_ignore = 0
net.ipv4.conf.default.arp_notify = 0
net.ipv4.conf.default.bootp_relay = 0
net.ipv4.conf.default.disable_policy = 0
net.ipv4.conf.default.disable_xfrm = 0
net.ipv4.conf.default.force_igmp_version = 0
net.ipv4.conf.default.forwarding = 0
net.ipv4.conf.default.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.default.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.default.ignore_routes_with_linkdown = 0
net.ipv4.conf.default.log_martians = 1
net.ipv4.conf.default.mc_forwarding = 0
net.ipv4.conf.default.medium_id = 0
net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.default.proxy_arp_pvlan = 0
net.ipv4.conf.default.route_localnet = 0
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.default.secure_redirects = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.default.shared_media = 1
net.ipv4.conf.default.src_valid_mark = 0
net.ipv4.conf.default.tag = 0
net.ipv4.conf.eno1.accept_local = 0
net.ipv4.conf.eno1.accept_redirects = 1
net.ipv4.conf.eno1.accept_source_route = 0
net.ipv4.conf.eno1.arp_accept = 0
net.ipv4.conf.eno1.arp_announce = 0
net.ipv4.conf.eno1.arp_filter = 0
net.ipv4.conf.eno1.arp_ignore = 0
net.ipv4.conf.eno1.arp_notify = 0
net.ipv4.conf.eno1.bootp_relay = 0
net.ipv4.conf.eno1.disable_policy = 0
net.ipv4.conf.eno1.disable_xfrm = 0
net.ipv4.conf.eno1.force_igmp_version = 0
net.ipv4.conf.eno1.forwarding = 0
net.ipv4.conf.eno1.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.eno1.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.eno1.ignore_routes_with_linkdown = 0
net.ipv4.conf.eno1.log_martians = 1
net.ipv4.conf.eno1.mc_forwarding = 0
net.ipv4.conf.eno1.medium_id = 0
net.ipv4.conf.eno1.promote_secondaries = 1
net.ipv4.conf.eno1.proxy_arp = 0
net.ipv4.conf.eno1.proxy_arp_pvlan = 0
net.ipv4.conf.eno1.route_localnet = 0
net.ipv4.conf.eno1.rp_filter = 0
net.ipv4.conf.eno1.secure_redirects = 1
net.ipv4.conf.eno1.send_redirects = 1
net.ipv4.conf.eno1.shared_media = 1
net.ipv4.conf.eno1.src_valid_mark = 0
net.ipv4.conf.eno1.tag = 0
net.ipv4.conf.lo.accept_local = 0
net.ipv4.conf.lo.accept_redirects = 1
net.ipv4.conf.lo.accept_source_route = 1
net.ipv4.conf.lo.arp_accept = 0
net.ipv4.conf.lo.arp_announce = 0
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.arp_ignore = 0
net.ipv4.conf.lo.arp_notify = 0
net.ipv4.conf.lo.bootp_relay = 0
net.ipv4.conf.lo.disable_policy = 1
net.ipv4.conf.lo.disable_xfrm = 1
net.ipv4.conf.lo.force_igmp_version = 0
net.ipv4.conf.lo.forwarding = 0
net.ipv4.conf.lo.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.lo.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.lo.ignore_routes_with_linkdown = 0
net.ipv4.conf.lo.log_martians = 1
net.ipv4.conf.lo.mc_forwarding = 0
net.ipv4.conf.lo.medium_id = 0
net.ipv4.conf.lo.promote_secondaries = 0
net.ipv4.conf.lo.proxy_arp = 0
net.ipv4.conf.lo.proxy_arp_pvlan = 0
net.ipv4.conf.lo.route_localnet = 0
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.lo.secure_redirects = 1
net.ipv4.conf.lo.send_redirects = 1
net.ipv4.conf.lo.shared_media = 1
net.ipv4.conf.lo.src_valid_mark = 0
net.ipv4.conf.lo.tag = 0


There is a section of 29 lines in the warm file referring to eno1 which do not appear in cold file.
tjkupp
 
Posts: 17
Joined: Jan 20th, '18, 00:26

Re: no ethernet after cold boot

Postby jiml8 » Feb 6th, '18, 09:42

OK, I believe I know what is happening.

But before I commit myself, please run rmmod e1000e followed by insmod e1000e after a cold boot with networking not working.

Then run ifconfig and see if the interface appears in the list. If it does, I am right, and I will tell you what is going on and what to do about it.
jiml8
 
Posts: 979
Joined: Jul 7th, '13, 18:09

Next

Return to Networking

Who is online

Users browsing this forum: No registered users and 1 guest

cron