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