public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recent networking problems
Date: Wed, 15 Feb 2012 09:21:08 -0600	[thread overview]
Message-ID: <CAEH5T2PHz72TWQQCzH9xWMS3cHVYbZaQB-LdWE8Bn9uCPu2zcA@mail.gmail.com> (raw)
In-Reply-To: <0629a23918d8cbddede4c1412da77fd1@weilbacher.org>

On Wed, Feb 15, 2012 at 3:32 AM, Peter Weilbacher
<newsspam@weilbacher.org> wrote:
> Hi all,
>
> since about two weeks I have been fighting with networking problems on a
> laptop. It all started with a big sync & world update that gave me new
> udev-171-r5, wicd-1.7.1_pre20120127, tuxonice-sources-3.0.17,
> openrc-0.9.8.2, among other things (I'm mostly running stable). Symptoms are
> that I cannot even get wired _listed_ in wicd, and when connecting to
> various different wireless routers, the connection died quickly. The e1000e
> driver (for wired) apparently never detects when a cable is connected, and
> when trying it through /etc/init.d/net.eth0, dhcpcd times out when waiting
> for a carrier... I tried alternating kernels (tuxonice- and gentoo-sources,
> both older and new ones between 2.3.38-r1 and 3.2.1) and kernel
> configurations as well as downgrades of several suspect packages, without
> success.
>
> Does that ring a bell with someone? Any advice how I can track down these
> problems?

There was a thread a while back about wicd quit working. The solution
then was to edit /etc/wicd/manager-settings.conf and change the
backend from "external" to "ioctl".



  reply	other threads:[~2012-02-15 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15  9:32 [gentoo-user] Recent networking problems Peter Weilbacher
2012-02-15 15:21 ` Paul Hartman [this message]
2012-02-22  8:59   ` [gentoo-user] " Peter Weilbacher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEH5T2PHz72TWQQCzH9xWMS3cHVYbZaQB-LdWE8Bn9uCPu2zcA@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox