public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Gigabit Ethernet support for forcedeth
Date: Mon, 2 Aug 2004 12:51:46 +0100	[thread overview]
Message-ID: <20040802115146.GJ8175@redhat.com> (raw)
In-Reply-To: <410A8588.6020208@colorfullife.com>

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

On Fri, Jul 30, 2004 at 07:29:44PM +0200, Manfred Spraul wrote:

> Could you try modprobe forcedeth;sleep 5;ip link set dev eth0 up.

Link was detected.

> Then 
> pull out the network cable and check if the driver noticed that with 
> ethtool.

It didn't.  It still thought there was a link.

> Plug in back in and check again. With dprintk enabled. Then 
> send me the kernel log and the ethtool output.

Done: http://cyberelk.net/tim/tmp/debug.gz

> And add the lspci -vxx -s 00:05.0. Probably I'll make the timer 
> dependant on nForce 1-3 and exclude the nForce 3 Gb nics: they don't 
> need it.

# lspci -vxx -s 00:05.0
00:05.0 Ethernet controller: nVidia Corporation nForce3 Ethernet (rev a5)
        Subsystem: Asustek Computer, Inc.: Unknown device 80c5
        Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 10
        Memory at ff6fc000 (32-bit, non-prefetchable)
        I/O ports at eff0 [size=8]
        Capabilities: [44] Power Management version 2
00: de 10 d6 00 07 00 b0 00 a5 00 00 02 00 00 00 00
10: 00 c0 6f ff f1 ef 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 c5 80
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 01 14

Thanks,
Tim.
*/

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

  reply	other threads:[~2004-08-02 11:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 10:04 [PATCH] Gigabit Ethernet support for forcedeth Tim Waugh
     [not found] ` <410A4A1C.4040608@colorfullife.com>
2004-07-30 16:20   ` Tim Waugh
2004-07-30 16:52     ` Manfred Spraul
2004-07-30 17:16       ` Tim Waugh
2004-07-30 17:29         ` Manfred Spraul
2004-08-02 11:51           ` Tim Waugh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30  5:44 Manfred Spraul
2004-06-30  6:10 ` Jeff Garzik
2004-06-30 16:11   ` Manfred Spraul
2004-06-30 18:55     ` Manfred Spraul
2004-07-02 15:51       ` Jeff Garzik
2004-07-02 19:29         ` Manfred Spraul
2004-07-03  6:17           ` Jeff Garzik
2004-07-04 18:27 ` Pavel Machek

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=20040802115146.GJ8175@redhat.com \
    --to=twaugh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /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