From: Sean Middleditch <smiddle@twp.ypsilanti.mi.us>
To: Masoud Sharbiani <masouds@oeone.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 8139too on Proliant
Date: 07 Mar 2002 10:23:26 -0500 [thread overview]
Message-ID: <1015514607.25062.28.camel@smiddle> (raw)
In-Reply-To: <3C8784E8.78B2D878@oeone.com>
In-Reply-To: <1015510399.25062.1.camel@smiddle> <3C8784E8.78B2D878@oeone.com>
Doesn't look like it:
dns1:/home/smiddle# modprobe via-rhine
/lib/modules/2.4.9-686/kernel/drivers/net/via-rhine.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
/lib/modules/2.4.9-686/kernel/drivers/net/via-rhine.o: insmod
/lib/modules/2.4.9-686/kernel/drivers/net/via-rhine.o failed
/lib/modules/2.4.9-686/kernel/drivers/net/via-rhine.o: insmod via-rhine
failed
dns1:/home/smiddle#
Just to clarify, the exact model is a DFE530TX+. I use this exact same
card on most my machines at home, with the 8139too driver as well. They
work fine.
Also, from /proc/pci:
Bus 0, device 4, function 0:
Ethernet controller: PCI device 1186:1300 (D-Link System Inc) (rev
16).
IRQ 15.
Master Capable. Latency=66. Min Gnt=32.Max Lat=64.
I/O at 0x3000 [0x30ff].
Non-prefetchable 32 bit memory at 0xb0800000 [0xb08000ff].
On Thu, 2002-03-07 at 10:19, Masoud Sharbiani wrote:
> Hi,
> D-Link 530TX driver is actually via-rhine, not 8139too. Have you tried that
> one?
>
>
> Masoud
> --
> Masoud Sharabiani
> Software Developer, OEone Corporation
> #103 - 290 St-Joseph Blvd. Hull, Quebec J8Y 3Y3
>
>
>
prev parent reply other threads:[~2002-03-07 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 14:13 8139too on Proliant Sean Middleditch
2002-03-07 15:19 ` Masoud Sharbiani
2002-03-07 15:23 ` Sean Middleditch [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=1015514607.25062.28.camel@smiddle \
--to=smiddle@twp.ypsilanti.mi.us \
--cc=linux-kernel@vger.kernel.org \
--cc=masouds@oeone.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 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.