Mageia forum

tjkupp, you would do me and all other visitors a great pleasure, when putting command-output between [CODE][/CODE]-tags.
Thanks ahead.

cold:

Code: Select all

[root@Daisy tom]# rmmod e1000e
[root@Daisy tom]# insmod e1000e
insmod: ERROR: could not load module e1000e: No such file or directory
[root@Daisy tom]# insmod e1000e.ko
insmod: ERROR: could not load module e1000e.ko: No such file or directory
[root@Daisy tom]# insmod e1000e.ko.xz
insmod: ERROR: could not load module e1000e.ko.xz: No such file or directory

warm:

Code: Select all

[root@Daisy tom]# rmmod e1000e
(message pops up in system tray that network is down)
[root@Daisy tom]# insmod e1000e
insmod: ERROR: could not load module e1000e: No such file or directory
[root@Daisy tom]# insmod e1000e.ko
insmod: ERROR: could not load module e1000e.ko: No such file or directory
[root@Daisy tom]# insmod e1000e.ko.xz
insmod: ERROR: could not load module e1000e.ko.xz: No such file or directory

Network still down. Possibly of interest: I then click icon in system tray. Network Center opens, showing
Wired (Ethernet)
Intel Corporation 82579V Gigabit Network Connection

I click Connect. No change. I click Configure. A second item appears, showing

Code: Select all

Wired (Ethernet)                                                eno1
Intel Corporation 82579V Gigabit Network Connection

I click Connect on this one, and network comes up.

Isadora,
Got your message just after last post. Will comply from now on.
Tom

Try again with

Code: Select all

modprobe e1000e

Code: Select all

[root@Daisy tom]# rmmod e1000e
[root@Daisy tom]# modprobe e1000e


No change in network.

I sincerely hope I haven't been wasting everybody's time here, but I just booted windows XP (which I rarely do), and I have exactly the same problem! I'm sure there was no problem in XP when I first noticed the problem in Mageia, but it sure is there now. Arg. In light of this, are we maybe looking at a hardware problem? Again, sincere apologies if I screwed up.

tjkupp wrote:

Code: Select all

[root@Daisy tom]# rmmod e1000e
[root@Daisy tom]# modprobe e1000e


No change in network.

And what does ifconfig say?

And, yes. It is either a hardware or a bios problem. Can be worked around, which is why I want to see what happens when you remove the driver, then reinstall it.

OK. My reply of Feb 6th, '18, 22:40 was intended to show there was no reply from either command. Sorry I did not make that clearer. Anyway, I just did this:

Code: Select all

[root@Daisy tom]# rmmod e1000e
[root@Daisy tom]# modprobe e1000e
[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 993  bytes 91093 (88.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 993  bytes 91093 (88.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



Still no network.

Another piece of (possibly) interesting info, which I found somewhere after a google search, is that pressing CTL+ALT+DEL when grub screen first appears then starting normally when it reappears is enough to get the network to start.

Well, yesterday was very interesting. My 6 year old motherboard is now unsupported. I did a bunch of googling about updating the BIOS and took the plunge. First one made no change. The next one caused a no-boot problem, so I used an old copy of Boot-Repair-Disk which, for some reason, replaced grub legacy with grub2. I cold booted Mageia and the network was up as enp0s25. However, browsers couldn't connect to the the web. I gave the interface a static address and voila, the problem was solved. Only thing now is Windows won't start. I get the first splash screen, and the machine reboots. That's probably something for another section of the forum, right?

tjkupp wrote:Only thing now is Windows won't start. I get the first splash screen, and the machine reboots. That's probably something for another section of the forum, right?

Yeah, probably for a windows forum
You should try to boot via safe mode, press f8 when windows boots and choose safe mode without network.
See e.g. https://support.microsoft.com/help/1741 ... -safe-mode

Sorry I am just getting back to this. I was off dealing with a wifi issue on the project that pays my bills.

Prior to my last posts, I had reached the conclusion you had either a hardware problem or a bios problem, in that at startup time your NIC was not properly responding when it was interrogated initially, or else your bios was losing the response. Consequently, when the linux kernel loaded the driver for that nic, no device was found.

I did fully expect that unloading and reloading the driver would cause the interface to appear, and I was flummoxed when that did not happen.

However, based upon your subsequent posts, it appears your bios did get corrupted, and reloading/upgrading it corrected the problem.

You might want to consider replacing the battery on the motherboard.