From: "Lenar Lõhmus" <lenar@vision.ee>
To: Johan <johan@ccs.neu.edu>, linux-kernel@vger.kernel.org
Subject: Re: status of via velocity in 2.6.9
Date: Tue, 07 Dec 2004 10:08:56 +0200 [thread overview]
Message-ID: <41B56518.2070108@vision.ee> (raw)
In-Reply-To: <41B4F447.2060808@ccs.neu.edu>
Hi,
At least Abit AV8 onboard velocity doesn't work with 2.6.9. With earlier
kernels,
the machine just locked up after ifconfig up. With 2.6.9, it doesn't
lock up, but it doesn't
work either (data seems to go to black hole or sth). But there seem to
be some success reports
too with this kernel.
Lenar
Johan wrote:
> How 'working' are the via velocity drivers in 2.6.9?
>
> For better or worse, the cheapest gigabit card I could find has the
> vt6122 chip, which seems to want the velocity drivers. (*)
>
> 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?
>
> Thanks
>
> Johan
>
> (*) 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.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-12-07 8:08 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 [this message]
2004-12-07 8:21 ` Francois Romieu
2004-12-07 13:28 ` Alan Cox
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=41B56518.2070108@vision.ee \
--to=lenar@vision.ee \
--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