Re: simple network card setup (netgear 10/100 tulip) - solved

2000-11-25 Thread Jeff Davis
Thanks to all who replied! My network is working fine right now. appearenty 
none of
the drivers on the cd will work with a FA311 (I could be wrong, but i tried to 
find
one), so I compiled a new one from http://www.scyld.com/network/index.html, 
called
natsemi (National Semiconductor)

I was very happy after working at it for a long time. I set Debain up on 
another box
(pIII board w/ built in intel NIC, etherexpress pro 100) with no major 
problems. I
like the package management in Debian a lot (this is the first time I have used
Debian), but I will have to look into some more of its features.

This, of course, was a very short version of what I went through. I had to 
install
the kernel headers package and put its include directory as a -I parameter to 
the
gcc compile command for the driver module. I also had to do the same thing for
pci-scan module (at same website).

I hope someone else may find this useful as well.

Thanks again,
Jeff Davis

Jeff Davis wrote:

 I have been reading docs all day but I cannot figure this one out. Note
 that I am used to Redhat/Mandrake, and I don't know as much as I would
 like to about Debian.

 I have a Netgear 10/100 card. I am sure it works, and I have used the
 same type of card with other distros. In it's linux.txt it describes
 an object file called tulip.o, which I assume to be the same as in the
 Debian distro (I am using 2.2). I tried first to do modprobe tulip and
 I get an error from insmod (I think modprobe is just a higher-level
 version of insmod, but I am not sure of this. I tried both) like device
 or resource busy and then something about how I might try changing the
 parameters.

 I have no /dev/eth* devices at all in my system. When I try to load the
 tulip module during the initial install I get the same insmod error (but
 before it asks for parameters).

 I recorded the CDs, so I am not sure of their integrity. I tried copying
 files, etc, but it won't be easy to get the good CDs (I think the
 downloaded ISOs should be correct) until I have network access.

 I half expected Debian to see the card immediately and to work
 automatically. I was somewhat surprised to see no eth devices, and more
 surprised when I couldn't just load the module to use it.

 I added a few modules during the setup, including ip_masq modules and
 more notably traffic shaper. Could these be conflicting? I tried
 removing them and inserting the other, but no effect.

 Any help would be greatly appreciated. I like Debian so far, but
 I haven't seen much :)

 Regards,
 Jeff Davis

 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null



Re: simple network card setup (netgear 10/100 tulip)

2000-11-23 Thread Jeff Davis
J. Bruce Fields wrote:

 On Wed, 22 Nov 2000, Cliff Rice wrote:

  On Wed, Nov 22, 2000 at 07:43:34AM -0800, Jeff Davis wrote:
   I have a Netgear 10/100 card. I am sure it works, and I have used the
   same type of card with other distros. In it's linux.txt it describes
   an object file called tulip.o, which I assume to be the same as in the
   Debian distro (I am using 2.2). I tried first to do modprobe tulip and
   I get an error from insmod (I think modprobe is just a higher-level
   version of insmod, but I am not sure of this. I tried both) like device
   or resource busy and then something about how I might try changing the
   parameters.
 
  Hi Jeff, I also use netgear cards.  You may want to try old_tulip
  instead.  Here is the Ethernet section of my kernel config file:
  (This is a custom kernel from www.kernel.org so YMMV on some options...)
  I also chose to compile it in the kernal, btw.  Oh yeah, kernel is
  2.2.17.

 I'm using the newest tulip driver with a netgear (a FA310TX--the model
 number matters a lot, which is yours?), and it works fine.  See
 http://www.scyld.com/network/tulip.html, and note that you actually have
 to download 3 different files and compile them seperately from the
 kernel.---jbf

I go those files and comiled them seperately from the kernel. I got
kern_compat.h, pci-scan.c, tulip.c, pci-scan.h (actually that is four, I
assumed those were the right files).

I can't insmod tulip before I insmod pci-scan (unresolved symbols). After I
insmod pci-scan, I still get a device or resource busy and something about
changing my IRQ or IO parameters to the module (I don't know how to do this).

in /proc/pci it says little about my card.. that it is io 0xd400 and irq 11,
but it doesn't recognize the type. Is there a way I can send that io address
and irq to the module?
I tried:
~# insmod tulip irq=11
then I get error invalid parameter parm_irq

I am not getting my card to work at all and I have spent about 15 hours so far.
I tried a diagnostic tool called tulip-diag and I get:

~# ./tulip-diag
I get messages like:
Rx state stopped
Tx state stopped
and it says something about a 10mbps (it is an FA311 10/100)

I am using either a FA311 or FA310 in the computer I am writing this on, and it
works fine (Mandrake  Redhat). It shows much more details info in /proc/pci
like LiteOn LNE100TX (rev 32).

If /proc/pci isn't showing good information, how would I get it to work like my
other machines?

Thanks!
Jeff Davis



Re: simple network card setup (netgear 10/100 tulip)

2000-11-23 Thread J. Bruce Fields
On Thu, 23 Nov 2000, Jeff Davis wrote:
 J. Bruce Fields wrote:
  I'm using the newest tulip driver with a netgear (a FA310TX--the model
  number matters a lot, which is yours?), and it works fine.  See
  http://www.scyld.com/network/tulip.html, and note that you actually have
  to download 3 different files and compile them seperately from the
  kernel.---jbf
 
 I go those files and comiled them seperately from the kernel. I got
 kern_compat.h, pci-scan.c, tulip.c, pci-scan.h (actually that is four, I
 assumed those were the right files).
 .
 and it says something about a 10mbps (it is an FA311 10/100)

Yowza! Watch out for those model numbers, and don't assume two cards with
similar names are really related. Apparently the FA311 does not use the
tulip driver.  Try a google search on FA311 and linux.  It looks like some
people have complaints about it, but if you plow through the hits you'll
find some folks that say they've gotten it working.

Best of luck---jbf



Re: simple network card setup (netgear 10/100 tulip)

2000-11-23 Thread Cliff Rice
On Thu, Nov 23, 2000 at 09:10:09AM -0500, J. Bruce Fields wrote:
 
 Yowza! Watch out for those model numbers, and don't assume two cards with
 similar names are really related. Apparently the FA311 does not use the
 tulip driver.  Try a google search on FA311 and linux.  It looks like some
 people have complaints about it, but if you plow through the hits you'll
 find some folks that say they've gotten it working.
 
 Best of luck---jbf

Jeff, Bruce is correct here.  Just curious, do you have the box handy
which the card came in?.  You can get the model number off of that or
by looking at the card itself.  My cards also came with a floppy called
Drivers and Diagnostic Disk.  It has Micro~s??t DOS on it but if you
mount it up , you may find some Linux drivers.  All of mine did.  I have
the FA311 drivers on my floppy btw and can send them to you offlist if
these are the ones you need and for some reason you can't get them off
your floppy.  (I'd check your floppy first of course.) 

The exact model I have is Netgear FA311 REV-A1.  I also have the other
models as well.

Jeff, here is another gotcha you may want to watch for when compiling
your own drivers.  Go to /usr/doc/kernel-source-? and look at the
README.header.gz.  There is a big messy issue with kernel headers wrt to
/usr/include/asm and /usr/include/linux.  I do know form personal
experience that compiling with /usr/include/linux and the /usr/src/linux
headers makes nonfunctional drivers. Some vendors tend to make
assumptions which aren't valid at present. 


Good luck,  15 hours to get a device to work is a real pain. 
Been there, done that. (:
 
---
Cliff



Re: simple network card setup (netgear 10/100 tulip)

2000-11-23 Thread Andrew Dwight Dixon
HI Jeff,
I've got the same card and for me it worked right out of the box.  I guess that
doesn't help, but:

If you think the CD you have is bad look at the checksums (md5sum I think).

Try a clean install and don't do anything to the modules when prompted (I left 
them
alone and it worked).

There shouldn't be an eth0.  The pcmcia stuff (sorry I forget which stuff but 
read
the how-to) takes care of brining up an interface when needed.  There shouldn't 
be an
eth0 because this would confuse the system.

Hope at least some of this was helpful,
Andy


Jeff Davis wrote:

 I have been reading docs all day but I cannot figure this one out. Note
 that I am used to Redhat/Mandrake, and I don't know as much as I would
 like to about Debian.

 I have a Netgear 10/100 card. I am sure it works, and I have used the
 same type of card with other distros. In it's linux.txt it describes
 an object file called tulip.o, which I assume to be the same as in the
 Debian distro (I am using 2.2). I tried first to do modprobe tulip and
 I get an error from insmod (I think modprobe is just a higher-level
 version of insmod, but I am not sure of this. I tried both) like device
 or resource busy and then something about how I might try changing the
 parameters.

 I have no /dev/eth* devices at all in my system. When I try to load the
 tulip module during the initial install I get the same insmod error (but
 before it asks for parameters).

 I recorded the CDs, so I am not sure of their integrity. I tried copying
 files, etc, but it won't be easy to get the good CDs (I think the
 downloaded ISOs should be correct) until I have network access.

 I half expected Debian to see the card immediately and to work
 automatically. I was somewhat surprised to see no eth devices, and more
 surprised when I couldn't just load the module to use it.

 I added a few modules during the setup, including ip_masq modules and
 more notably traffic shaper. Could these be conflicting? I tried
 removing them and inserting the other, but no effect.

 Any help would be greatly appreciated. I like Debian so far, but
 I haven't seen much :)

 Regards,
 Jeff Davis

 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




simple network card setup (netgear 10/100 tulip)

2000-11-22 Thread Jeff Davis
I have been reading docs all day but I cannot figure this one out. Note
that I am used to Redhat/Mandrake, and I don't know as much as I would
like to about Debian.

I have a Netgear 10/100 card. I am sure it works, and I have used the
same type of card with other distros. In it's linux.txt it describes
an object file called tulip.o, which I assume to be the same as in the
Debian distro (I am using 2.2). I tried first to do modprobe tulip and
I get an error from insmod (I think modprobe is just a higher-level
version of insmod, but I am not sure of this. I tried both) like device
or resource busy and then something about how I might try changing the
parameters.

I have no /dev/eth* devices at all in my system. When I try to load the
tulip module during the initial install I get the same insmod error (but
before it asks for parameters).

I recorded the CDs, so I am not sure of their integrity. I tried copying
files, etc, but it won't be easy to get the good CDs (I think the
downloaded ISOs should be correct) until I have network access.

I half expected Debian to see the card immediately and to work
automatically. I was somewhat surprised to see no eth devices, and more
surprised when I couldn't just load the module to use it.

I added a few modules during the setup, including ip_masq modules and
more notably traffic shaper. Could these be conflicting? I tried
removing them and inserting the other, but no effect.

Any help would be greatly appreciated. I like Debian so far, but
I haven't seen much :)

Regards,
Jeff Davis



Re: simple network card setup (netgear 10/100 tulip)

2000-11-22 Thread Cliff Rice
On Wed, Nov 22, 2000 at 07:43:34AM -0800, Jeff Davis wrote:
 I have a Netgear 10/100 card. I am sure it works, and I have used the
 same type of card with other distros. In it's linux.txt it describes
 an object file called tulip.o, which I assume to be the same as in the
 Debian distro (I am using 2.2). I tried first to do modprobe tulip and
 I get an error from insmod (I think modprobe is just a higher-level
 version of insmod, but I am not sure of this. I tried both) like device
 or resource busy and then something about how I might try changing the
 parameters.

Hi Jeff, I also use netgear cards.  You may want to try old_tulip
instead.  Here is the Ethernet section of my kernel config file:
(This is a custom kernel from www.kernel.org so YMMV on some options...)
I also chose to compile it in the kernal, btw.  Oh yeah, kernel is
2.2.17.

CONFIG_NET_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_RTL8139 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_EISA=y
# CONFIG_PCNET32 is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
# CONFIG_DM9102 is not set
# CONFIG_DE4X5 is not set
# CONFIG_DEC_ELCP is not set
CONFIG_DEC_ELCP_OLD=y
# CONFIG_DGRS is not set
CONFIG_EEXPRESS_PRO100=y
# CONFIG_LNE390 is not set
# CONFIG_NE3210 is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SIS900 is not set
# CONFIG_ES3210 is not set
# CONFIG_EPIC100 is not set
# CONFIG_ZNET is not set
# CONFIG_NET_POCKET is not set

In dmesg , I get 
tulip.c:v0.89H 5/23/98 [EMAIL PROTECTED]
eth0: Lite-On 82c168 PNIC at 0xd000, 00 a0 cc 58 67 ea, IRQ 11.
eth0:  MII transceiver found at MDIO address 1, config 3000 status 7829.
eth0:  Advertising 01e1 on PHY 1, previously advertising 01e1.


 
 I have no /dev/eth* devices at all in my system. When I try to load the
 tulip module during the initial install I get the same insmod error (but
 before it asks for parameters).

This may seem strange, but that is normal .  Try looking in /proc/pci
instead. (:  You should see something like

Non-prefetchable 32 bit memory at 0xd800 [0xd800].
Bus  0, device  11, function  0:
Ethernet controller: LiteOn LNE100TX (rev 32).
Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  
Latency=32.  

Hope this helps and good luck

-- 
My inner child is cranky  www.hardradio.com
Cliff



Re: simple network card setup (netgear 10/100 tulip)

2000-11-22 Thread debuser
Probably not your problem, but make sure you have turned off plug and
play OS in your BIOS. This caused a major headache for me with another
card. Also, the ethernet howto may be helpful as well as looking at the
web sites for the driver of your card (probably listed in the source for
your driver or in the ethernet howto). 

On Wed, 22 Nov 2000, Jeff Davis wrote:

 I have been reading docs all day but I cannot figure this one out. Note
 that I am used to Redhat/Mandrake, and I don't know as much as I would
 like to about Debian.
 
 I have a Netgear 10/100 card. I am sure it works, and I have used the
 same type of card with other distros. In it's linux.txt it describes
 an object file called tulip.o, which I assume to be the same as in the
 Debian distro (I am using 2.2). I tried first to do modprobe tulip and
 I get an error from insmod (I think modprobe is just a higher-level
 version of insmod, but I am not sure of this. I tried both) like device
 or resource busy and then something about how I might try changing the
 parameters.
 
 I have no /dev/eth* devices at all in my system. When I try to load the
 tulip module during the initial install I get the same insmod error (but
 before it asks for parameters).
 
 I recorded the CDs, so I am not sure of their integrity. I tried copying
 files, etc, but it won't be easy to get the good CDs (I think the
 downloaded ISOs should be correct) until I have network access.
 
 I half expected Debian to see the card immediately and to work
 automatically. I was somewhat surprised to see no eth devices, and more
 surprised when I couldn't just load the module to use it.
 
 I added a few modules during the setup, including ip_masq modules and
 more notably traffic shaper. Could these be conflicting? I tried
 removing them and inserting the other, but no effect.
 
 Any help would be greatly appreciated. I like Debian so far, but
 I haven't seen much :)
 
 Regards,
 Jeff Davis
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
 



Re: simple network card setup (netgear 10/100 tulip)

2000-11-22 Thread J. Bruce Fields
On Wed, 22 Nov 2000, Cliff Rice wrote:

 On Wed, Nov 22, 2000 at 07:43:34AM -0800, Jeff Davis wrote:
  I have a Netgear 10/100 card. I am sure it works, and I have used the
  same type of card with other distros. In it's linux.txt it describes
  an object file called tulip.o, which I assume to be the same as in the
  Debian distro (I am using 2.2). I tried first to do modprobe tulip and
  I get an error from insmod (I think modprobe is just a higher-level
  version of insmod, but I am not sure of this. I tried both) like device
  or resource busy and then something about how I might try changing the
  parameters.
 
 Hi Jeff, I also use netgear cards.  You may want to try old_tulip
 instead.  Here is the Ethernet section of my kernel config file:
 (This is a custom kernel from www.kernel.org so YMMV on some options...)
 I also chose to compile it in the kernal, btw.  Oh yeah, kernel is
 2.2.17.

I'm using the newest tulip driver with a netgear (a FA310TX--the model
number matters a lot, which is yours?), and it works fine.  See
http://www.scyld.com/network/tulip.html, and note that you actually have
to download 3 different files and compile them seperately from the
kernel.---jbf



Re: simple network card setup (netgear 10/100 tulip)

2000-11-22 Thread William Cooper

Hi,
   which NIC do you have? I have a Netgear FA312 this does not use the 
tulip  drivers, it uses the natsemi driver. I have used both the drivers 
that came  with the card on the diskette and from http://www.scyld.com 
and both work.

HTH
Bill C

Jeff Davis wrote:


I have been reading docs all day but I cannot figure this one out. Note
that I am used to Redhat/Mandrake, and I don't know as much as I would
like to about Debian.

I have a Netgear 10/100 card. I am sure it works, and I have used the
same type of card with other distros. In it's linux.txt it describes
an object file called tulip.o, which I assume to be the same as in the
Debian distro (I am using 2.2). I tried first to do modprobe tulip and
I get an error from insmod (I think modprobe is just a higher-level
version of insmod, but I am not sure of this. I tried both) like device
or resource busy and then something about how I might try changing the
parameters.

I have no /dev/eth* devices at all in my system. When I try to load the
tulip module during the initial install I get the same insmod error (but
before it asks for parameters).

I recorded the CDs, so I am not sure of their integrity. I tried copying
files, etc, but it won't be easy to get the good CDs (I think the
downloaded ISOs should be correct) until I have network access.

I half expected Debian to see the card immediately and to work
automatically. I was somewhat surprised to see no eth devices, and more
surprised when I couldn't just load the module to use it.

I added a few modules during the setup, including ip_masq modules and
more notably traffic shaper. Could these be conflicting? I tried
removing them and inserting the other, but no effect.

Any help would be greatly appreciated. I like Debian so far, but
I haven't seen much :)

Regards,
Jeff Davis








Re: simple network card setup (netgear 10/100 tulip)

2000-11-22 Thread Cliff Rice
On Wed, Nov 22, 2000 at 12:58:29PM -0500, J. Bruce Fields wrote:
snip
 
 I'm using the newest tulip driver with a netgear (a FA310TX--the model
 number matters a lot, which is yours?), and it works fine.  See
 http://www.scyld.com/network/tulip.html, and note that you actually have
 to download 3 different files and compile them seperately from the
 kernel.---jbf

Strange,  That is what I have. 2  FA310TX's, REV-D2 which I bought last end of
last year.  To be fair, I did use the regular tulip driver which came
with the 2.2.12 kernel.  It was the 2.2.17 kernel where I had to use 
old_tulip.  As for model numbers, you are correct,  I just found a
FA311 in my closet, and I have a floppy with a fa311.c driver file
and then it goes on to say :

The FA311 driver is developed for use on Linux v2.0.36. It can be
configured either as a static driver into the kernel or as a loadable
module. The driver is capable of 10/100 Mbps Full/Half duplex mode
operation via an internal PHY. Detailed features are given below.
  and .

Unsupported Features
...
Newer MP kernels 2.2.xx

(All of my Netgear cards have come with floppies with M$ drivers and
Linux drivers.)

-- 
My inner child is cranky  www.hardradio.com
homepage : cliff.neosoft.com
Cliff