From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Johan <johan@ccs.neu.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: status of via velocity in 2.6.9
Date: Tue, 07 Dec 2004 13:28:39 +0000 [thread overview]
Message-ID: <1102426117.18043.26.camel@localhost.localdomain> (raw)
In-Reply-To: <41B4F447.2060808@ccs.neu.edu>
On Maw, 2004-12-07 at 00:07, Johan wrote:
> How 'working' are the via velocity drivers in 2.6.9?
They should be pretty solid. The original VIA code worked pretty well,
the kernel merge had a few glitches but in 2.6.9* it seems rock solid
with the bits Francois applied.
> Unfortunately, while they (the driver and card, that is) seem at first
> to work fine, auto negotiating a gigabit connection with my hub, the
> network stops working after 5 ish minutes (could be function of bytes
> tx'ed as well, I guess). restarting the network (appart from a kernel
> upgrade, the box is redhat fc2) fixes the problem... for another 5 minutes.
>
> Is this known behavior?
I've seen this with an Edimax el cheapo gigabit switch, but it was also
doing it with some other cards so I assumed it was random cheap junk.
Since I swapped that for a slightly better one it's behaved reliably.
> (*) The card's box advertizes linux compatibility with RH 7.3 (2.4.18-3
> or later), which makes me wonder whether another driver may work better.
> 2.4.18-3 would seem to predate the via-velocity driver.
There is a vendor provided driver for older systems (and in fact VIA
networking wrote and contributed the code that was cleaned up to go into
the kernel too)
Alan
prev parent reply other threads:[~2004-12-07 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 0:07 status of via velocity in 2.6.9 Johan
2004-12-07 0:44 ` Francois Romieu
2004-12-07 1:23 ` Johan
2004-12-07 8:26 ` Francois Romieu
2004-12-07 8:08 ` Lenar Lõhmus
2004-12-07 8:21 ` Francois Romieu
2004-12-07 13:28 ` Alan Cox [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=1102426117.18043.26.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=johan@ccs.neu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox