From: Anders Rune Jensen <anders@gnulinux.dk>
To: linux-kernel@vger.kernel.org
Cc: "jos.huisken" <jos.huisken@kpnplanet.nl>
Subject: Re: Forcedeth: Nvidia NIC goes up and down
Date: Fri, 24 Aug 2007 03:40:21 +0200 [thread overview]
Message-ID: <1187919621.8533.3.camel@localhost> (raw)
In-Reply-To: <181B3AA5E931BA4AB8ED25976193DDC30137416B@CPEXBE-VOIP03.bbp.local>
On Wed, 2007-08-22 at 22:43 +0200, jos.huisken@kpnplanet.nl wrote:
> Hi,
>
>
> I have a similar issue. The network drops away randomly for short periods (several to ten(s) seconds).
> Strange enough nothing is reported is syslog, and indeed from the machine itself pinging works perfectly to another machine.
> From that other machine however the connections looks dead in those periods...
>
> I'm running kernel 2.6.18.8-0.5-default on a SUSE 10.2 machine with a ASUS M2NPV-VM board.
> Have tried both the default "0.59" and "0.62-Driver Package V1.23" version of forcedeth
> Tried 2 BIOSes: 0901 and 1001.
>
> Also have tried several kernel options independently: noapic, pci=routeirq, acpi=off, pci=nomsi
> All did not help.
>
>
> Any suggestions?
I got it working by connecting the network card my old 100mbit hub. It
seems that the problem is only when it runs a 1gbit. So my setup is now
1gbit switch <> computers, 1mbit hub <> machine with broken netcard.
This is good enough for now, since I don't really transfer that much
data to and from the machine, but of course I would like to have 1gbit
working for when I actually do need it ;-)
> BTW I'm not subscribed, please CC me personally.
>
>
> Thanks in advance,
> -- Jos
--
Anders Rune Jensen
http://people.iola.dk/anders/
next prev parent reply other threads:[~2007-08-23 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 20:43 Forcedeth: Nvidia NIC goes up and down jos.huisken
2007-08-24 1:40 ` Anders Rune Jensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-02 19:08 Anders Rune Jensen
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=1187919621.8533.3.camel@localhost \
--to=anders@gnulinux.dk \
--cc=jos.huisken@kpnplanet.nl \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.