1 |
On Saturday 16 June 2007 22:55, Xavier Parizet wrote: |
2 |
> Coud you provide us the output of dmesg according forcedeth module (dmesg |
3 |
> |grep forcedeth), route -n, ifconfig ethX and /etc/conf.d/net ... |
4 |
|
5 |
I could, but this is no more necessary |
6 |
|
7 |
On Saturday 16 June 2007 23:20, Uwe Thiem wrote: |
8 |
> |
9 |
> A guess from what I have read on another list: You have a conflict because |
10 |
> both drivers (modules) are loaded, the RLT one and forcedeth. If you remove |
11 |
> the RLT module, does is work? |
12 |
> |
13 |
> Uwe |
14 |
> |
15 |
|
16 |
Your guess was wrong, Uwe, but it did help me get on the right track. |
17 |
There is no RTL driver for that chip but... looking another time at the output |
18 |
of lsmod and getting the ansers to Xavier's demands I realized that I the |
19 |
system said that eth0 did not exists - but gave it an IP anyway. SO I |
20 |
wondered who could be stealing my eth0 and sure enough, it was eth1394! |
21 |
|
22 |
So although I did configure the ethernet card as eth0 during install, after |
23 |
reboot the firewire port took eth0 and the nforce card became eth1... |
24 |
|
25 |
So now I have put a (useless) config for eth0 in /etc/conf.d/net (perhaps I |
26 |
could remove it, but I don't know) and tranfered my settings on eth1, and I |
27 |
got my network back. |
28 |
|
29 |
Thanks you both for your help! Now is time to start emerge kde and go to bed! |
30 |
|
31 |
Thierry |
32 |
|
33 |
-- |
34 |
gentoo-user@g.o mailing list |