On Sat, 08 Jul 2000, Charles E. Gelm wrote about, ? configuring NIC KNE110TX ?:
> Howdy, All:
I saw Rays explaination, but considering i use slackware i thought i could
help just a little more.
>
> I've just installed Slackware-7.0 - kernel 2.2.13.
> But I'm lost at where to find information about getting the
> kernel to recognize my NIC. It is a Kingston KNE110TX.
> I think that it may be a 'tulip'. I've browsed at Kingston
> and get refered to another web page and after some more browsing
> I found 'tulip.c' v0.92.
You have the correct driver, it is tulip.o tulip.c is the source file of
course .o is the object or module.
On a small note slackware 7.0 with kernel 2.2.13 has this module waiting
for you to use it, providing one installed kernel modules (which is pretty
much standard).
They reside in /lib/modules/2.2.13/* tulip.o in net.
In /boot there is a file called "config" its what is included in the
distribution kernel 2.2.13 installed via slackware.
To get the system running with the distribution kernel;
edit /etc/modules.conf and place the following.
alias eth0 tulip
edit /etc/rc.d/rc.inet1
An example would be;
#! /bin/sh
#
# rc.inet1 This shell script boots up the base INET system.
#
# Version: @(#)/etc/rc.d/rc.inet1 2.00 10/06/1999
#
HOSTNAME=`cat /etc/HOSTNAME`
# Attach the loopback device.
/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
# IF YOU HAVE AN ETHERNET CONNECTION, use these lines below to configure the
# eth0 interface.
# The modprobe is optional, slackware does not include kmod support in
# its supllied kernel and kerneld is not activated BEFORE this file gets
# read UNLESS you change /etc/rc.d/rc.S to start kerneld.
# If we do the above with our won compiled kernel with KMOD then we
# can skip the use of /etc/rc.d/rc.modules. Around line 160 you see;
# if [ -x /etc/rc.d/rc.modules ]; then
# Which means if rc.modules is executable read it, change permissions
# of /etc/rc.d/rc.modules
# chmod a-x /etc/rc.d/rc.modules
# Now it does not get read.
modprobe eth0 tulip
# Edit these values to set up a static IP address:
IPADDR="192.168.0.1" # REPLACE with YOUR IP address!
NETMASK="255.255.255.0" # REPLACE with YOUR netmask!
NETWORK="192.168.0.0" # REPLACE with YOUR network address!
BROADCAST="" # REPLACE with YOUR broadcast address, if you
# have one. If not, leave blank and edit below.
GATEWAY="" # REPLACE with YOUR gateway address!
Rest of the file snipped.
If you use DHCP to obtain an IP address from your provider leave the file
as is, it is default 127.0.0.1
Now without rebooting, try;
modprobe tulip
ifconfig eth0 192.168.0.1 up
route add -net 192.168.0.0 netmask 255.255.255.0 up
The above should intialise the card configure it and add a default route,
upon booting it should now be found automaticly and configured by rc.inet1
>
> Is this what I need?
> If yes, where do I put 'tulip.c'?
No need to put it anywhere IF you have installed the 2.2.13 kernel source.
> How do I generate 'tulip.o' and where should it reside?
It resides in /usr/src/linux/drivers/net
>
> I want to use this box as an IP Masquerade and Samba file server.
> I'd rather compile the NIC driver into the kernel instead of
> installing it as a module. I didn't see this NIC mentioned
> while doing a 'make config'.
The NIC is not mentioned however tulip support is.
To select it in make config select;
Ethernet (10 or 100Mbit) (CONFIG_NET_ETHERNET) [Y/n/?]
EISA, VLB, PCI and on board controllers (CONFIG_NET_EISA) [Y/n/?]
DECchip Tulip (dc21x4x) PCI support (CONFIG_DEC_ELCP) [N/y/m/?] ?
Answer the above as "y" for compile into the kernel "m" for module.
Of course if you select to have it in the kernel the comments about KMOD
and KERNELD are not needed.
>
> How do I include this NIC driver into my kernel?
As per above. But take note, like Ray said, there are many reasons for
compiling a kernel with modules, there are reasons not to, the for's are
more than the not's.
If there are more questions fire away.
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
