Problem solved! (Was: Re: [SLUG] Driver for D-Link NIC)

2000-10-10 Thread Peter Hardy

On Tue, Oct 10, 2000 at 12:58:05PM +1100, Adrian van den Dries wrote:
> Wrote John:
> > 
> > The 100M versions of the card need the newer driver which only
> > ships with 2.4. It may ship with some distributions if the distro has
> > specifically compiled the right version in.
> > 
> 
> Perhaps that explains the 'poor' performance of that card. It's a 10/100 but
> I guess it's only being driven at 10Mbps. Is this correct, because as I
> said, I've never had 'trouble'? Peter, is it the standard kernel module that
> isn't recognizing your card? How's your modules.conf?

A standard Debian 2.2 install was failing to recognise the card,
modprobe'ing the driver failed with an error about specifying a base address
and irq.  As I've already said elsewhere, I think it may be a slightly
different revision of the card.

On Tue, Oct 10, 2000 at 10:40:12AM +1100, John Ferlito wrote:
> Had to do this a while ago. Now from memory do the following 
> Go back to the via-rhine web page and there should be a link to
> pci-scan.[ch] you need these as well then use the following to compile.
These are at http://www.scyld.com/network/updates.html, and you also need to
get the kern_compat.h file.  There's also instructions there to compile the
pci-scan and driver modules.

If anybody's interested I actually just put all the files in my
/usr/src/linux/drivers/net directory, and modified the Makefile there to
make sure pci-scan was being built as a module.  Tried building it into the
kernel following the instructions on the site, but linking failed because of
mismatched symbols in pci-scan.

Thankyou John and Adrian.
Peter
[EMAIL PROTECTED]


 PGP signature


Re: [SLUG] Driver for D-Link NIC

2000-10-09 Thread Peter Hardy

On Tue, Oct 10, 2000 at 10:53:11AM +1100, Adrian van den Dries wrote:
> I've never had any problem with the card, using the via-rhine module shipped
> in the standard kernel. I've never had to compile the module separately,
> even with early 2.2 kernels. I just have "alias eth0 via-rhine" in my
> modules.conf.

*shrug*  May be different revisions.  My card is fairly new, I bought it
about a month ago.  From the website (www.scyld.com): "You will need a
driver with version 1.07 or higher if you have a VT6102 Rhine-II chip with
PCI device ID 3065."  lspci on my machine reports that that is what I have,
and I know the card won't work with a standard debian 2.2 install.  The
module just doesn't detect the card..

Cheers,
Peter
[EMAIL PROTECTED]

 PGP signature


Re: [SLUG] Driver for D-Link NIC

2000-10-09 Thread Adrian van den Dries

Wrote John:
> 
>   The 100M versions of the card need the newer driver which only
> ships with 2.4. It may ship with some distributions if the distro has
> specifically compiled the right version in.
> 

Perhaps that explains the 'poor' performance of that card. It's a 10/100 but
I guess it's only being driven at 10Mbps. Is this correct, because as I
said, I've never had 'trouble'? Peter, is it the standard kernel module that
isn't recognizing your card? How's your modules.conf?

-- 
Cantanker /
-/
/ [EMAIL PROTECTED]


--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug



Re: [SLUG] Driver for D-Link NIC

2000-10-09 Thread John Ferlito

On Tue, Oct 10, 2000 at 10:53:11AM +1100, Adrian van den Dries wrote:
> I've never had any problem with the card, using the via-rhine module shipped
> in the standard kernel. I've never had to compile the module separately,
> even with early 2.2 kernels. I just have "alias eth0 via-rhine" in my
> modules.conf.

The 100M versions of the card need the newer driver which only
ships with 2.4. It may ship with some distributions if the distro has
specifically compiled the right version in.

> 
> HTH.
> 
> Wrote Peter:
> > 
> > This is where my meagre knowledge of C dries up.  Am I going to be able to
> > use this driver with 2.2?
> > 
> 
> -- 
> Cantanker /
> -/
> / [EMAIL PROTECTED]
> 
> 
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://slug.org.au/lists/listinfo/slug

-- 
John


--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug



Re: [SLUG] Driver for D-Link NIC

2000-10-09 Thread Adrian van den Dries

I've never had any problem with the card, using the via-rhine module shipped
in the standard kernel. I've never had to compile the module separately,
even with early 2.2 kernels. I just have "alias eth0 via-rhine" in my
modules.conf.

HTH.

Wrote Peter:
> 
> This is where my meagre knowledge of C dries up.  Am I going to be able to
> use this driver with 2.2?
> 

-- 
Cantanker /
-/
/ [EMAIL PROTECTED]


--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug



Re: [SLUG] Driver for D-Link NIC

2000-10-09 Thread John Ferlito

On Wed, Oct 04, 2000 at 07:18:43AM +1100, Peter Hardy wrote:
> I have a D-Link DFE-530TX NIC, which is supported by the newer versions of
> the via-rhine driver.  The driver included with the 2.2.17 kernel does not
> recognise the card.  Right now I'm running 2.4.0-pre9, but would prefer 2.2,
> at least until 2.4 becomes stable.  Looking at the webpage, I need version
> 1.07 or later.  The 2.2.17 kernel ships with 1.01.
> I've download the newest version (1.08) of via-rhine.c from
> www.scyld.com/pub/network/, but the compile fails with the
> following message:
> 
> peter@littlegeek:~/src$ gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c
> via-rhine.c
> via-rhine.c:91: linux/modversions.h: No such file or directory
> via-rhine.c:112: pci-scan.h: No such file or directory
> via-rhine.c:113: kern_compat.h: No such file or directory
> via-rhine.c:118: warning: #warning You are using an old kern_compat.h
> version.

Had to do this a while ago. Now from memory do the following 
Go back to the via-rhine web page and there should be a link to
pci-scan.[ch] you need these as well then use the following to compile.
You need a 2.2.17 souce tree somewhere or at least the header files and
use

gcc -D__KERNEL__ -I/usr/src/linux-2.2.17/include -Wall \
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing \
-pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 \
-malign-functions=2 -DCPU=586 -DMODULE -DMODVERSIONS -include \
/usr/src/linux-2.2.17/include/linux/modversions.h  -o via-rhine.o
via-rhine.c

the only real important bits above are
-D__KERNEL__ and -I/usr/src/linux-2.2.17/include

same as above with s/via-rhine/pci-scan/g

then insmod pci-scan.o
insmod via-rhine.o 
and hopefully you'll be away.

-- 
John

 PGP signature


[SLUG] Driver for D-Link NIC

2000-10-09 Thread Peter Hardy

I have a D-Link DFE-530TX NIC, which is supported by the newer versions of
the via-rhine driver.  The driver included with the 2.2.17 kernel does not
recognise the card.  Right now I'm running 2.4.0-pre9, but would prefer 2.2,
at least until 2.4 becomes stable.  Looking at the webpage, I need version
1.07 or later.  The 2.2.17 kernel ships with 1.01.
I've download the newest version (1.08) of via-rhine.c from
www.scyld.com/pub/network/, but the compile fails with the
following message:

peter@littlegeek:~/src$ gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c
via-rhine.c
via-rhine.c:91: linux/modversions.h: No such file or directory
via-rhine.c:112: pci-scan.h: No such file or directory
via-rhine.c:113: kern_compat.h: No such file or directory
via-rhine.c:118: warning: #warning You are using an old kern_compat.h
version.

This is where my meagre knowledge of C dries up.  Am I going to be able to
use this driver with 2.2?

Cheers,
Peter

 PGP signature