1 |
On Mon, Jun 25, 2012 at 10:45 AM, Valmor de Almeida |
2 |
<val.gentoo@×××××.com> wrote: |
3 |
> On 6/24/12 7:24 PM, Alan McKinnon wrote: |
4 |
>> On Sun, 24 Jun 2012 19:04:25 -0400 |
5 |
>> Valmor de Almeida <val.gentoo@×××××.com> wrote: |
6 |
>> |
7 |
>>> |
8 |
>>> Hello, |
9 |
>>> |
10 |
>>> I am having a hard time getting wicd to work on gentoo guest. Thought |
11 |
>>> that it was a simple matter of emerge and run wicd-client -n to |
12 |
>>> configure. I have compiled the correct ethernet driver in the kernel |
13 |
>>> (at least I think so). |
14 |
>> |
15 |
>> What driver is that? |
16 |
> |
17 |
> The vbox emulates this adapter |
18 |
> Intel PRO/1000 MT Desktop (8254OEM) |
19 |
> |
20 |
> In the kernel 3.3.8-gentoo I compiled the |
21 |
> |
22 |
> Intel(R) PRO/1000 Gigabit Ethernet Support |
23 |
> |
24 |
> I compiled directly into the kernel. If I had used a module the module |
25 |
> name would have been e1000. |
26 |
> |
27 |
>> |
28 |
>>> Does anyone have some experience with this or |
29 |
>>> could point me to diagnostic approaches? |
30 |
>> |
31 |
>> What have you already tried (so we don't waste our time trying the same |
32 |
>> thing) |
33 |
>> |
34 |
>>> The output of ifconfig -a |
35 |
>>> follows below. |
36 |
>> |
37 |
>> dmesg? /var/log/messages? |
38 |
> |
39 |
> dmesg shows |
40 |
> |
41 |
> [ 0.576506] e1000: Intel(R) PRO/1000 Network Driver - version |
42 |
> 7.3.21-k8-NAPI |
43 |
> [ 0.577602] e1000: Copyright (c) 1999-2006 Intel Corporation. |
44 |
> [ 0.579200] e1000 0000:00:03.0: setting latency timer to 64 |
45 |
> |
46 |
> [ 1.071183] e1000 0000:00:03.0: eth0: (PCI:33MHz:32-bit) |
47 |
> 08:00:27:96:75:25 |
48 |
> [ 1.071949] e1000 0000:00:03.0: eth0: Intel(R) PRO/1000 Network |
49 |
> Connection |
50 |
> |
51 |
> and there is nothing helpful in /var/log/messages |
52 |
> |
53 |
>> |
54 |
>>> Don't know why eth1 and not eth0 is there. |
55 |
>> |
56 |
>> udev persistent rules strike again |
57 |
> |
58 |
> The contents of /var/log/wicd/wicd.log below do indicate a mess up |
59 |
> with eth1 and eth0. Any idea on how to fix this? |
60 |
|
61 |
Yep. All I needed to do was to change the wired interface from eth0 to |
62 |
eth1 in the preferences of wicd-client -n and it works. So the |
63 |
question is, why do I have eth1 and not eth0 and how do I set up eth0 |
64 |
instead? Is dhcpcd involved in this? |
65 |
|
66 |
Thanks, |
67 |
|
68 |
-- |
69 |
Valmor |
70 |
|
71 |
> |
72 |
> Thanks, |
73 |
> |
74 |
> -- |
75 |
> Valmor |
76 |
> |
77 |
> /var/log/wicd/wicd.log |
78 |
> |
79 |
> 2012/06/25 14:15:06 :: --------------------------- |
80 |
> 2012/06/25 14:15:06 :: wicd initializing... |
81 |
> 2012/06/25 14:15:06 :: --------------------------- |
82 |
> 2012/06/25 14:15:06 :: wicd is version 1.7.2.1 755 |
83 |
> 2012/06/25 14:15:06 :: setting backend to external |
84 |
> 2012/06/25 14:15:06 :: trying to load backend external |
85 |
> 2012/06/25 14:15:06 :: successfully loaded backend external |
86 |
> 2012/06/25 14:15:06 :: trying to load backend external |
87 |
> 2012/06/25 14:15:06 :: successfully loaded backend external |
88 |
> 2012/06/25 14:15:06 :: Couldn't detect a wireless interface. |
89 |
> 2012/06/25 14:15:06 :: setting wireless interface wlan0 |
90 |
> 2012/06/25 14:15:06 :: automatically detected wired interface eth1 |
91 |
> 2012/06/25 14:15:06 :: setting wired interface eth0 |
92 |
> 2012/06/25 14:15:06 :: setting wpa driver wext |
93 |
> 2012/06/25 14:15:06 :: setting use global dns to False |
94 |
> 2012/06/25 14:15:06 :: setting global dns |
95 |
> 2012/06/25 14:15:06 :: global dns servers are None None None |
96 |
> 2012/06/25 14:15:06 :: domain is None |
97 |
> 2012/06/25 14:15:06 :: search domain is None |
98 |
> 2012/06/25 14:15:06 :: setting automatically reconnect when connection |
99 |
> drops True |
100 |
> 2012/06/25 14:15:06 :: Setting dhcp client to 0 |
101 |
> 2012/06/25 14:15:06 :: Wireless configuration file found... |
102 |
> 2012/06/25 14:15:06 :: Wired configuration file found... |
103 |
> 2012/06/25 14:15:06 :: chmoding configuration files 0600... |
104 |
> 2012/06/25 14:15:06 :: chowning configuration files root:root... |
105 |
> 2012/06/25 14:15:06 :: Using wireless interface...wlan0 |
106 |
> 2012/06/25 14:15:06 :: Using wired interface...eth0 |
107 |
> 2012/06/25 10:15:13 :: Autoconnecting... |
108 |
> 2012/06/25 10:15:13 :: No wired connection present, attempting to |
109 |
> autoconnect to wireless network |
110 |
> 2012/06/25 10:15:13 :: Unable to autoconnect, you'll have to manually connect |
111 |
> 2012/06/25 10:15:18 :: Autoconnecting... |
112 |
> [snip] |
113 |
> |
114 |
> |
115 |
>> |
116 |
>>> The HWaddr |
117 |
>>> is correctly obtained from the vbox. |
118 |
>> |
119 |
>> Your information supplied is not enough to really help you solve this |
120 |
>> problem. |
121 |
>> |
122 |
>> |
123 |
>>> |
124 |
>>> Thanks, |
125 |
>>> |
126 |
>>> -- |
127 |
>>> Valmor |
128 |
>>> |
129 |
>>> ifconfig -a |
130 |
>>> |
131 |
>>> eth1 Link encap:Ethernet HWaddr 08:00:27:96:75:25 |
132 |
>>> BROADCAST MULTICAST MTU:1500 Metric:1 |
133 |
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
134 |
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
135 |
>>> collisions:0 txqueuelen:1000 |
136 |
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) |
137 |
>>> |
138 |
>>> lo Link encap:Local Loopback |
139 |
>>> inet addr:127.0.0.1 Mask:255.0.0.0 |
140 |
>>> inet6 addr: ::1/128 Scope:Host |
141 |
>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 |
142 |
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
143 |
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
144 |
>>> collisions:0 txqueuelen:0 |
145 |
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) |
146 |
>>> |
147 |
>>> sit0 Link encap:IPv6-in-IPv4 |
148 |
>>> NOARP MTU:1480 Metric:1 |
149 |
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
150 |
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
151 |
>>> collisions:0 txqueuelen:0 |
152 |
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) |
153 |
>>> |
154 |
>>> |
155 |
>> |
156 |
>> |
157 |
>> |