FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 06-24-2012, 11:04 PM
Valmor de Almeida
 
Default wicd setup on a virtualbox gentoo guest

Hello,

I am having a hard time getting wicd to work on gentoo guest. Thought
that it was a simple matter of emerge and run wicd-client -n to
configure. I have compiled the correct ethernet driver in the kernel (at
least I think so). Does anyone have some experience with this or could
point me to diagnostic approaches? The output of ifconfig -a follows
below. Don't know why eth1 and not eth0 is there. The HWaddr is
correctly obtained from the vbox.


Thanks,

--
Valmor

ifconfig -a

eth1 Link encap:Ethernet HWaddr 08:00:27:96:75:25
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
 
Old 06-24-2012, 11:24 PM
Alan McKinnon
 
Default wicd setup on a virtualbox gentoo guest

On Sun, 24 Jun 2012 19:04:25 -0400
Valmor de Almeida <val.gentoo@gmail.com> wrote:

>
> Hello,
>
> I am having a hard time getting wicd to work on gentoo guest. Thought
> that it was a simple matter of emerge and run wicd-client -n to
> configure. I have compiled the correct ethernet driver in the kernel
> (at least I think so).

What driver is that?

> Does anyone have some experience with this or
> could point me to diagnostic approaches?

What have you already tried (so we don't waste our time trying the same
thing)

> The output of ifconfig -a
> follows below.

dmesg? /var/log/messages?

> Don't know why eth1 and not eth0 is there.

udev persistent rules strike again

> The HWaddr
> is correctly obtained from the vbox.

Your information supplied is not enough to really help you solve this
problem.


>
> Thanks,
>
> --
> Valmor
>
> ifconfig -a
>
> eth1 Link encap:Ethernet HWaddr 08:00:27:96:75:25
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> sit0 Link encap:IPv6-in-IPv4
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
>



--
Alan McKinnnon
alan.mckinnon@gmail.com
 
Old 06-25-2012, 02:45 PM
Valmor de Almeida
 
Default wicd setup on a virtualbox gentoo guest

On 6/24/12 7:24 PM, Alan McKinnon wrote:
> On Sun, 24 Jun 2012 19:04:25 -0400
> Valmor de Almeida <val.gentoo@gmail.com> wrote:
>
>>
>> Hello,
>>
>> I am having a hard time getting wicd to work on gentoo guest. Thought
>> that it was a simple matter of emerge and run wicd-client -n to
>> configure. I have compiled the correct ethernet driver in the kernel
>> (at least I think so).
>
> What driver is that?

The vbox emulates this adapter
Intel PRO/1000 MT Desktop (8254OEM)

In the kernel 3.3.8-gentoo I compiled the

Intel(R) PRO/1000 Gigabit Ethernet Support

I compiled directly into the kernel. If I had used a module the module
name would have been e1000.

>
>> Does anyone have some experience with this or
>> could point me to diagnostic approaches?
>
> What have you already tried (so we don't waste our time trying the same
> thing)
>
>> The output of ifconfig -a
>> follows below.
>
> dmesg? /var/log/messages?

dmesg shows

[ 0.576506] e1000: Intel(R) PRO/1000 Network Driver - version
7.3.21-k8-NAPI
[ 0.577602] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 0.579200] e1000 0000:00:03.0: setting latency timer to 64

[ 1.071183] e1000 0000:00:03.0: eth0: (PCI:33MHz:32-bit)
08:00:27:96:75:25
[ 1.071949] e1000 0000:00:03.0: eth0: Intel(R) PRO/1000 Network
Connection

and there is nothing helpful in /var/log/messages

>
>> Don't know why eth1 and not eth0 is there.
>
> udev persistent rules strike again

The contents of /var/log/wicd/wicd.log below do indicate a mess up
with eth1 and eth0. Any idea on how to fix this?

Thanks,

--
Valmor

/var/log/wicd/wicd.log

2012/06/25 14:15:06 :: ---------------------------
2012/06/25 14:15:06 :: wicd initializing...
2012/06/25 14:15:06 :: ---------------------------
2012/06/25 14:15:06 :: wicd is version 1.7.2.1 755
2012/06/25 14:15:06 :: setting backend to external
2012/06/25 14:15:06 :: trying to load backend external
2012/06/25 14:15:06 :: successfully loaded backend external
2012/06/25 14:15:06 :: trying to load backend external
2012/06/25 14:15:06 :: successfully loaded backend external
2012/06/25 14:15:06 :: Couldn't detect a wireless interface.
2012/06/25 14:15:06 :: setting wireless interface wlan0
2012/06/25 14:15:06 :: automatically detected wired interface eth1
2012/06/25 14:15:06 :: setting wired interface eth0
2012/06/25 14:15:06 :: setting wpa driver wext
2012/06/25 14:15:06 :: setting use global dns to False
2012/06/25 14:15:06 :: setting global dns
2012/06/25 14:15:06 :: global dns servers are None None None
2012/06/25 14:15:06 :: domain is None
2012/06/25 14:15:06 :: search domain is None
2012/06/25 14:15:06 :: setting automatically reconnect when connection
drops True
2012/06/25 14:15:06 :: Setting dhcp client to 0
2012/06/25 14:15:06 :: Wireless configuration file found...
2012/06/25 14:15:06 :: Wired configuration file found...
2012/06/25 14:15:06 :: chmoding configuration files 0600...
2012/06/25 14:15:06 :: chowning configuration files root:root...
2012/06/25 14:15:06 :: Using wireless interface...wlan0
2012/06/25 14:15:06 :: Using wired interface...eth0
2012/06/25 10:15:13 :: Autoconnecting...
2012/06/25 10:15:13 :: No wired connection present, attempting to
autoconnect to wireless network
2012/06/25 10:15:13 :: Unable to autoconnect, you'll have to manually connect
2012/06/25 10:15:18 :: Autoconnecting...
[snip]


>
>> The HWaddr
>> is correctly obtained from the vbox.
>
> Your information supplied is not enough to really help you solve this
> problem.
>
>
>>
>> Thanks,
>>
>> --
>> Valmor
>>
>> ifconfig -a
>>
>> eth1 Link encap:Ethernet HWaddr 08:00:27:96:75:25
>> BROADCAST MULTICAST MTU:1500 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>
>> lo Link encap:Local Loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> inet6 addr: ::1/128 Scope:Host
>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>
>> sit0 Link encap:IPv6-in-IPv4
>> NOARP MTU:1480 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>
>>
>
>
>
 
Old 06-25-2012, 03:20 PM
Valmor de Almeida
 
Default wicd setup on a virtualbox gentoo guest

On Mon, Jun 25, 2012 at 10:45 AM, Valmor de Almeida
<val.gentoo@gmail.com> wrote:
> On 6/24/12 7:24 PM, Alan McKinnon wrote:
>> On Sun, 24 Jun 2012 19:04:25 -0400
>> Valmor de Almeida <val.gentoo@gmail.com> wrote:
>>
>>>
>>> Hello,
>>>
>>> I am having a hard time getting wicd to work on gentoo guest. Thought
>>> that it was a simple matter of emerge and run wicd-client -n to
>>> configure. I have compiled the correct ethernet driver in the kernel
>>> (at least I think so).
>>
>> What driver is that?
>
> The vbox emulates this adapter
> * *Intel PRO/1000 MT Desktop (8254OEM)
>
> In the kernel 3.3.8-gentoo I compiled the
>
> * Intel(R) PRO/1000 Gigabit Ethernet Support
>
> I compiled directly into the kernel. If I had used a module the module
> name would have been e1000.
>
>>
>>> Does anyone have some experience with this or
>>> could point me to diagnostic approaches?
>>
>> What have you already tried (so we don't waste our time trying the same
>> thing)
>>
>>> The output of ifconfig -a
>>> follows below.
>>
>> dmesg? /var/log/messages?
>
> dmesg shows
>
> [ * *0.576506] e1000: Intel(R) PRO/1000 Network Driver - version
> 7.3.21-k8-NAPI
> [ * *0.577602] e1000: Copyright (c) 1999-2006 Intel Corporation.
> [ * *0.579200] e1000 0000:00:03.0: setting latency timer to 64
>
> [ * *1.071183] e1000 0000:00:03.0: eth0: (PCI:33MHz:32-bit)
> 08:00:27:96:75:25
> [ * *1.071949] e1000 0000:00:03.0: eth0: Intel(R) PRO/1000 Network
> Connection
>
> and there is nothing helpful in /var/log/messages
>
>>
>>> Don't know why eth1 and not eth0 is there.
>>
>> udev persistent rules strike again
>
> The contents of /var/log/wicd/wicd.log below do indicate a mess up
> with eth1 and eth0. Any idea on how to fix this?

Yep. All I needed to do was to change the wired interface from eth0 to
eth1 in the preferences of wicd-client -n and it works. So the
question is, why do I have eth1 and not eth0 and how do I set up eth0
instead? Is dhcpcd involved in this?

Thanks,

--
Valmor

>
> Thanks,
>
> --
> Valmor
>
> /var/log/wicd/wicd.log
>
> 2012/06/25 14:15:06 :: ---------------------------
> 2012/06/25 14:15:06 :: wicd initializing...
> 2012/06/25 14:15:06 :: ---------------------------
> 2012/06/25 14:15:06 :: wicd is version 1.7.2.1 755
> 2012/06/25 14:15:06 :: setting backend to external
> 2012/06/25 14:15:06 :: trying to load backend external
> 2012/06/25 14:15:06 :: successfully loaded backend external
> 2012/06/25 14:15:06 :: trying to load backend external
> 2012/06/25 14:15:06 :: successfully loaded backend external
> 2012/06/25 14:15:06 :: Couldn't detect a wireless interface.
> 2012/06/25 14:15:06 :: setting wireless interface wlan0
> 2012/06/25 14:15:06 :: automatically detected wired interface eth1
> 2012/06/25 14:15:06 :: setting wired interface eth0
> 2012/06/25 14:15:06 :: setting wpa driver wext
> 2012/06/25 14:15:06 :: setting use global dns to False
> 2012/06/25 14:15:06 :: setting global dns
> 2012/06/25 14:15:06 :: global dns servers are None None None
> 2012/06/25 14:15:06 :: domain is None
> 2012/06/25 14:15:06 :: search domain is None
> 2012/06/25 14:15:06 :: setting automatically reconnect when connection
> drops True
> 2012/06/25 14:15:06 :: Setting dhcp client to 0
> 2012/06/25 14:15:06 :: Wireless configuration file found...
> 2012/06/25 14:15:06 :: Wired configuration file found...
> 2012/06/25 14:15:06 :: chmoding configuration files 0600...
> 2012/06/25 14:15:06 :: chowning configuration files root:root...
> 2012/06/25 14:15:06 :: Using wireless interface...wlan0
> 2012/06/25 14:15:06 :: Using wired interface...eth0
> 2012/06/25 10:15:13 :: Autoconnecting...
> 2012/06/25 10:15:13 :: No wired connection present, attempting to
> autoconnect to wireless network
> 2012/06/25 10:15:13 :: Unable to autoconnect, you'll have to manually connect
> 2012/06/25 10:15:18 :: Autoconnecting...
> [snip]
>
>
>>
>>> The HWaddr
>>> is correctly obtained from the vbox.
>>
>> Your information supplied is not enough to really help you solve this
>> problem.
>>
>>
>>>
>>> Thanks,
>>>
>>> --
>>> Valmor
>>>
>>> ifconfig -a
>>>
>>> eth1 * * *Link encap:Ethernet *HWaddr 08:00:27:96:75:25
>>> * * * * * * BROADCAST MULTICAST *MTU:1500 *Metric:1
>>> * * * * * * RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> * * * * * * TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> * * * * * * collisions:0 txqueuelen:1000
>>> * * * * * * RX bytes:0 (0.0 B) *TX bytes:0 (0.0 B)
>>>
>>> lo * * * *Link encap:Local Loopback
>>> * * * * * * inet addr:127.0.0.1 *Mask:255.0.0.0
>>> * * * * * * inet6 addr: ::1/128 Scope:Host
>>> * * * * * * UP LOOPBACK RUNNING *MTU:16436 *Metric:1
>>> * * * * * * RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> * * * * * * TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> * * * * * * collisions:0 txqueuelen:0
>>> * * * * * * RX bytes:0 (0.0 B) *TX bytes:0 (0.0 B)
>>>
>>> sit0 * * *Link encap:IPv6-in-IPv4
>>> * * * * * * NOARP *MTU:1480 *Metric:1
>>> * * * * * * RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> * * * * * * TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> * * * * * * collisions:0 txqueuelen:0
>>> * * * * * * RX bytes:0 (0.0 B) *TX bytes:0 (0.0 B)
>>>
>>>
>>
>>
>>
 
Old 06-25-2012, 10:01 PM
Neil Bothwick
 
Default wicd setup on a virtualbox gentoo guest

On Mon, 25 Jun 2012 11:20:42 -0400, Valmor de Almeida wrote:

> >> udev persistent rules strike again
> >
> > The contents of /var/log/wicd/wicd.log below do indicate a mess up
> > with eth1 and eth0. Any idea on how to fix this?
>
> Yep. All I needed to do was to change the wired interface from eth0 to
> eth1 in the preferences of wicd-client -n and it works. So the
> question is, why do I have eth1 and not eth0 and how do I set up eth0
> instead? Is dhcpcd involved in this?

No, it's udev persistent rules. eth0 has already been assigned to a
different MAC address, so this one gets eth1.

Delete /etc/udev/rules.d/70-persistent-net.rules to go back to eth0.


--
Neil Bothwick

Help a man when he is in trouble and he will remember you when he is in
trouble again
 

Thread Tools




All times are GMT. The time now is 02:47 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org