| View previous topic :: View next topic |
| Author |
Message |
tabanus
l33t
Joined: 11 Jun 2004
Posts: 638
Location: UK
|
 Posted: Mon Apr 08, 2013 6:27 pm Post subject: Installing external kernel modules |
 |
|
I'm troubleshooting a networking problem, and want to try building my network card's kernel module separately.
The NIC is a Realtek RTL8111/8168. The kernel I'm using (3.7.10) doesn't list this in menuconfig. I've always used the driver for RTL8169 which until now has been OK, but I'm getting intermittent connectivity problems.
I've downloaded the driver from Realtek's website.
So, is it just a matter of untaring it, then 'make && make install' from a terminal in the directory that I untared it into, or do I have to do anything else to build and install it?
I know I have to deal with module loading as well, but I know what I'm doing with that.
Thanks
_________________
Things you might say if you never took Physics: "I'm overweight even though I don't overeat." - Neil deGrasse Tyson |
|
| Back to top |
|
 |
kurly
Apprentice
Joined: 02 Apr 2012
Posts: 260
|
| Posted: Mon Apr 08, 2013 6:56 pm Post subject: |
|
|
| Not really the answer to the question you were asking, but the r8168 driver is in portage as net-misc/r8168. |
|
| Back to top |
|
|
tabanus
l33t
Joined: 11 Jun 2004
Posts: 638
Location: UK
|
| Posted: Mon Apr 08, 2013 7:16 pm Post subject: |
|
|
| kurly wrote: | | Not really the answer to the question you were asking, but the r8168 driver is in portage as net-misc/r8168. |
OMG, thanks. I never even thought to look. 
_________________
Things you might say if you never took Physics: "I'm overweight even though I don't overeat." - Neil deGrasse Tyson |
|
| Back to top |
|
|
verchiel
n00b
Joined: 25 Nov 2012
Posts: 15
|
|
| Back to top |
|
|
tabanus
l33t
Joined: 11 Jun 2004
Posts: 638
Location: UK
|
| Posted: Mon Apr 08, 2013 8:40 pm Post subject: |
|
|
I think I've fixed the problem; it's hard to be sure though because I did have periods of relative normality before. Having fought for days with it, including (as asked about here) using the 'proper' kernel driver, what seems to have done the trick is using dhcp rather than a static ip address. It makes no sense to me why this would work, as there were definitely no ip address conflicts on my LAN, but at least for now, it's looking good.
_________________
Things you might say if you never took Physics: "I'm overweight even though I don't overeat." - Neil deGrasse Tyson |
|
| Back to top |
|
|
|
Kernel & Hardware
