From: Mark Syms <mark@marksyms.demon.co.uk>
To: rl@hellgate.ch
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via-Rhine dirve in 2.4.21-pre7
Date: 17 Apr 2003 18:53:50 +0100 [thread overview]
Message-ID: <1050602030.988.4.camel@athlon> (raw)
In-Reply-To: <1049706637.963.6.camel@athlon>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Roger,
Just saw your response on the mailing list archive. Sorry I haven't
responded earlier but as I said below I'm not subscribed to the list.
The reason I was trying 2.4.21-pre7 is that I have been unable to get
the network card working on any kernel version if local IO-APIC is
enabled and I was hoping that the changes you had submitted for the
21pre series might help but they did not.
If you want me to try anything let me know or send me a patch (directly
please).
Sorry not to be more help.
Mark.
On Mon, 2003-04-07 at 10:10, Mark Syms wrote:
> Roger,
>
> Just tried the via-rhine driver in 2.4.21-pre7 and it appears to exhibit
> the problem Erik Hensema reported with the VT6103 onboard network card
> on my Chaintech 7VJL Athlon board whereby you get NETDEV Watchdog
> transmit timeout errors unless you turn local io-apic off in which case
> it all works fine.
>
> Please cc me directly as I'm not subscribed to the mailing list.
>
> Thank you,
>
> Mark Syms
--
Mark Syms <mark@marksyms.demon.co.uk>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-17 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 9:10 Via-Rhine dirve in 2.4.21-pre7 Mark Syms
2003-04-07 11:26 ` Roger Luethi
2003-04-17 17:53 ` Mark Syms [this message]
2003-04-17 17:59 ` Jeff Garzik
2003-04-18 2:47 ` Marc Wilson
2003-04-18 3:21 ` Jeff Garzik
2003-04-17 19:34 ` Roger Luethi
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=1050602030.988.4.camel@athlon \
--to=mark@marksyms.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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