public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, jgarzik@pobox.com
Subject: Re: Issues with uli526x networking module
Date: Thu, 6 Apr 2006 13:24:20 +1000	[thread overview]
Message-ID: <200604061324.24499.ncunningham@cyclades.com> (raw)
In-Reply-To: <200604041615.10749.prakash@punnoor.de>

[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]

Hi.

On Wednesday 05 April 2006 00:15, Prakash Punnoor wrote:
> Am Dienstag März 28 2006 23:47 schrieb Nigel Cunningham:
> > Hi.
> >
> > On Wednesday 29 March 2006 03:30, Prakash Punnoor wrote:
> > > Hi, I am just wondering whether you found out what the issue is with
> > > the link problem. If you have some patch ready (even if it is hackish)
> > > I would be happy to use it.
> > >
> > > Anyways, I know you are busy with swsusp2. ;-)
> > >
> > > Cheers,
> >
> > Yes, I do have a patch. It is hackish at the moment because as you've
> > rightly guessed, I haven't gotten around to finishing it. It also doesn't
> > work perfectly - I sometimes need to rmmod and insmod after booting a new
> > kernel to get the link to come up. But, apart from that, it works fine.
>
> Thx for sharing it. Unfortunately it doesn't help me. (I am not using
> suspend or anything on that machine as it is supposed to be running 24/7.)
> After pulling out the LAN cable and putting it back in. network is dead.
> The driver (even unpatched) sees the cable is back in, but obviously
> wrongly
> reinitializes(?) the nic: Ie, kernel says after pluggin cable back in:
>
> uli526x: eth0 NIC Link is Up 100 Mbps Full duplex
>
> but network is dead.
>
> I have to do:
>
> ifconfig eth0 down
> modprobe -r uli526x
> modprobe uli526x
> ifconfig eth0 up
> dhclient
>
> And then it works again.

Yes, this is what I was describing too. I need to learn more about how the 
link control works.

Regards,

Nigel

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-04-06  3:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26  8:00 Issues with uli526x networking module Prakash Punnoor
2006-01-26 11:10 ` Nigel Cunningham
2006-03-28 17:30   ` Prakash Punnoor
2006-03-28 21:47     ` Nigel Cunningham
2006-04-04 14:15       ` Prakash Punnoor
2006-04-06  3:24         ` Nigel Cunningham [this message]

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=200604061324.24499.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakash@punnoor.de \
    /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