[Solved] Default NIC Module?

shoober420 · 2014-10-10 08:40:29

I'm trying to troubleshoot an issue I'm having with Steam downloads, and I'm thinking it may be my NIC drivers. I have a Intel Gigabit CT, with the latest 3.1.0.2 drivers. I was wondering what drivers or modules Arch was using before I installed the Intel drivers, so I can load them and see if it fixes my issue with Steam downloads.

Last edited by shoober420 (2014-10-11 02:41:20)

lucke · 2014-10-10 08:57:33

How did you install "the Intel drivers"?

tomk · 2014-10-10 09:03:27

Just remove whatever you installed - the kernel provides drivers for Intel devices, so I guess that's what you are referring to as the "Default NIC Module".

shoober420 · 2014-10-10 17:56:48

lucke wrote:

How did you install "the Intel drivers"?

I followed the Readme thats included. You do a "make install" in the src directory.

shoober420 · 2014-10-10 18:01:12

tomk wrote:

Just remove whatever you installed - the kernel provides drivers for Intel devices, so I guess that's what you are referring to as the "Default NIC Module".

Yes, that's what I'm referring to. The strange thing is, to uninstall them, I did multiple things, but they still come back. I did a "make uninstall" in the src directory, and I did a "modprobe -r ptp e1000e", but they are still there after reboot. It seems I can't remove them. Do you think if I blacklisted them that it would then use the drivers that the kernel provides?

EDIT: Sorry about double post, just woke up.

Last edited by shoober420 (2014-10-10 18:02:16)

Trilby · 2014-10-10 18:01:36

*headdesk*

This is why you should always use PKGBUILDs, makepkg, and pacman. As is, you are now at the mercy of the upstream source as to whether they included an uninstall directive. If they did, you can do a `make uninstall` in the same source directory. Otherwise you'll have to inspect any makefile(s) in order to see what was done and manually undo it.

EDIT: this was crossposted with the above post. Did the make uninstall command do anything? Where are these source files? If you show where you got them we can gather more information.

Last edited by Trilby (2014-10-10 18:02:20)

shoober420 · 2014-10-10 18:08:22

Trilby wrote:

*headdesk*
This is why you should always use PKGBUILDs, makepkg, and pacman. As is, you are now at the mercy of the upstream source as to whether they included an uninstall directive. If they did, you can do a `make uninstall` in the same source directory. Otherwise you'll have to inspect any makefile(s) in order to see what was done and manually undo it.
EDIT: this was crossposted with the above post. Did the make uninstall command do anything? Where are these source files? If you show where you got them we can gather more information.

It seems the "make uninstall" or "modprobe -r ptp e1000e" didn't do anything since they are back after reboot. I guess for not making a package, I will have too manually uninstall them. That will be my punishment lol.

Here is a link to the drivers from Intel.

https://downloadcenter.intel.com/Detail … ldID=15817

Trilby · 2014-10-10 18:09:13

This likely also overwrote managed files which you may have to reinstall. You might want to run `pacman -Qk`

shoober420 · 2014-10-10 18:11:14

Trilby wrote:

This likely also overwrote managed files which you may have to reinstall. You might want to run `pacman -Qk`

Okay, will do. What if I blacklisted the Intel drivers? Do you think that would switch over to the default kernel drivers?

Trilby · 2014-10-10 18:13:21

That sounds like a bad bandaid approach. If you successfully removed everything it installed, there would be nothing to blacklist. Figure out what *actually* broke, and fix that.

shoober420 · 2014-10-10 18:20:10

Trilby wrote:

That sounds like a bad bandaid approach. If you successfully removed everything it installed, there would be nothing to blacklist. Figure out what *actually* broke, and fix that.

Okay, thank you Trilby for the help.

shoober420 · 2014-10-10 18:59:55

Okay, I just did a derpy fail. I did a nano on the Makefile, and found where the install directory was. So, like an idiot, I deleted the whole directory, which contained the default NIC drivers I wanted. I was left with no internet on reboot. I had to reinstall the drivers I was trying to do away with just to have internet access. So I'm back to square one, well, maybe square zero since now even though I know which folder to remove (e1000e), I now have no default kernel drivers to fallback on, since I deleted the whole intel directory.

When a kernel update appears, will I get these drivers back?

Last edited by shoober420 (2014-10-10 19:01:13)

shoober420 · 2014-10-10 19:00:52

shoober420 wrote:

Okay, I just did a derpy fail. I did a nano on the Makefile, and found where the install directory was. So, like an idiot, I deleted the whole directory, which contained the default NIC drivers I wanted. I was left with no internet on reboot. I had to reinstall the drivers I was trying to do away with just to have internet access. So I'm back to square one, well, maybe square zero since now even though I know which folder to remove (e1000e), I now have no default kernel drivers to fallback on, since I deleted the whole intel directory.
When a kernel update appears, will I get these drivers back?

EDIT: I accidently did a quote instead of a edit. My bad, I just want to download some games and can't so I'm all stress out.

Last edited by shoober420 (2014-10-10 19:02:22)

bstaletic · 2014-10-10 19:55:48

Reinstall the kernel. If you have an internet connection from another computer you can download package and install it using pacman -U.

jasonwryan · 2014-10-10 19:58:02

Not a networking issue, moving to NC...

shoober420 · 2014-10-11 02:40:29

I think I'll just use the Intel NIC drivers for now until 3.18 gets released. I'm assuming once a new kernel version gets installed, it will reinstall those default kernel NIC drivers. I also found out that Steam might be writing to the disk too aggressively, and is stressing fsync, therefore making my downloads not work. So its a problem on Steams side. I'll just mark this as solved.

Last edited by shoober420 (2014-10-11 02:40:54)

Trilby · 2014-10-11 02:43:51

Why would you need to wait for 3.18 to reinstall the kernel? Just reinstall the linux package as you've already been advised to do.

tomk · 2014-10-11 12:00:28

shoober420 wrote:

I did a "modprobe -r ptp e1000e", but they are still there after reboot.

modprobe commands only affect the current running system, they are not persistent across reboots. The drivers provided by the kernel have the same names as the new versions that you installed, so you could have checked the versions with modinfo to determine which ones are "still there".

That's just FYI, no longer relevant because of your drastic actions since. Just reinstall the kernel.

shoober420 · 2014-10-11 17:26:14

Trilby wrote:

Why would you need to wait for 3.18 to reinstall the kernel? Just reinstall the linux package as you've already been advised to do.

I'm not in a rush to do so, since the Intel NIC drivers do work, except Steam can't download games. I only need the Intel NIC drivers, so I don't have any reason to use the default kernel ones, unless Steam isn't the problem.

tomk wrote:

modprobe commands only affect the current running system, they are not persistent across reboots. The drivers provided by the kernel have the same names as the new versions that you installed, so you could have checked the versions with modinfo to determine which ones are "still there".
That's just FYI, no longer relevant because of your drastic actions since. Just reinstall the kernel.

Oh I see, well that explains some things. I took some another drastic step last light, and upgraded my system from ext2 to ext4. Some people were saying that Steam was aggresively writing to the disk, and stressing out fsync, and that using barrier=0 would fix it. Well, it didn't. I upgraded for nothing.

Although with ext4, my system boots up faster, which I guess is a good thing. I heard ext2 is faster then ext4, even with the journal disabled, which is why I chose ext2. My fstab options for ext4 are in my Steam profile, and I still can't download games with Steam. I really don't know what the problem is.

Last edited by shoober420 (2014-10-11 17:28:48)

Arch Linux

#1 2014-10-10 08:40:29

[Solved] Default NIC Module?

#2 2014-10-10 08:57:33

Re: [Solved] Default NIC Module?

#3 2014-10-10 09:03:27

Re: [Solved] Default NIC Module?

#4 2014-10-10 17:56:48

Re: [Solved] Default NIC Module?

#5 2014-10-10 18:01:12

Re: [Solved] Default NIC Module?

#6 2014-10-10 18:01:36

Re: [Solved] Default NIC Module?

#7 2014-10-10 18:08:22

Re: [Solved] Default NIC Module?

#8 2014-10-10 18:09:13

Re: [Solved] Default NIC Module?

#9 2014-10-10 18:11:14

Re: [Solved] Default NIC Module?

#10 2014-10-10 18:13:21

Re: [Solved] Default NIC Module?

#11 2014-10-10 18:20:10

Re: [Solved] Default NIC Module?

#12 2014-10-10 18:59:55

Re: [Solved] Default NIC Module?

#13 2014-10-10 19:00:52

Re: [Solved] Default NIC Module?

#14 2014-10-10 19:55:48

Re: [Solved] Default NIC Module?

#15 2014-10-10 19:58:02

Re: [Solved] Default NIC Module?

#16 2014-10-11 02:40:29

Re: [Solved] Default NIC Module?

#17 2014-10-11 02:43:51

Re: [Solved] Default NIC Module?

#18 2014-10-11 12:00:28

Re: [Solved] Default NIC Module?

#19 2014-10-11 17:26:14

Re: [Solved] Default NIC Module?

Board footer