1 |
On Sun, Feb 15, 2009 at 5:40 PM, Dirk Heinrichs |
2 |
<dirk.heinrichs@××××××.de> wrote: |
3 |
> Am Sonntag, 15. Februar 2009 22:31:40 schrieb Guillermo Garron: |
4 |
> |
5 |
>> Here you can find the config file for my current kernel. |
6 |
> |
7 |
> This has CONFIG_E1000=y |
8 |
> |
9 |
>> And the used to generate the new kernel (where NIC is not detected) |
10 |
> |
11 |
> This has both CONFIG_E1000=y and CONFIG_E1000E=y, maybe that's the problem. |
12 |
> |
13 |
> What does lspci -v tell about the used driver? Anything useful in the dmesg |
14 |
> output? |
15 |
|
16 |
Hi, |
17 |
Thanks for your prompt response. |
18 |
|
19 |
Here is the output of this command |
20 |
|
21 |
sudo lspci -v | grep Ether |
22 |
|
23 |
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network |
24 |
Connection (rev 02) |
25 |
|
26 |
> |
27 |
> BTW: There are also some other NICs enabled in both your configs. |
28 |
|
29 |
Yes, that is because I am not good a compiling kernels and did not |
30 |
know how to discover what NIC I have to enable only that driver or |
31 |
module. :( |
32 |
|
33 |
> |
34 |
> HTH... |
35 |
> |
36 |
> Dirk |
37 |
> |
38 |
|
39 |
|
40 |
|
41 |
-- |
42 |
Guillermo Garron |
43 |
"Linux IS user friendly... It's just selective about who its friends are." |
44 |
(Using Ubuntu, Debian, Gentoo) |
45 |
http://feeds.feedburner.com/go2linux |
46 |
http://www.go2linux.org |