On Mon, 10 Jul 2000, Chuck Gelm wrote about, Re: ? configuring NIC KNE110TX ?:
> Hi, Richard and Ray:
>
> Richard: I did what you mentioned:
Yes i see the problem later on in this reply, you have the driver compiled
into the kernel so forget about modules and modprobe.
There are more comments further down in this mail.
>
>
> Richard Adams wrote:
> >
> <snip>
> > edit /etc/modules.conf and place the following.
> > alias eth0 tulip
> > edit /etc/rc.d/rc.inet1
> > An example would be;
> >
> > #! /bin/sh
> <snip>
> modprobe eth0 tulip
> /* This is the only line that I added to /etc/rc.d/rc.inte1 */
> >
> > # 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
Ok DHCP then you should leave the stuff AS IS, dont toch any of it, just
make sure you have changed;
if [ "$DHCP" = "no" ]
if [ "$DHCP" = "yes" ]
Then it should work automaicly upon booting.
>
> I use DHCP. In windoze9x configuration my WINS(use DHCP) gateway is
> x.x.25.1
> Should I edit above to read
> GATEWAY="X.X.25.1"
No the dhcp server should do the rest for you.
> ?
>
> >
> > Now without rebooting, try;
> >
> > modprobe tulip
>
> This returned
> /lib/modules/2.2.13/net/tulip.o: init_module: Device or resource busy.
Yes that is understandable, you have the driver compiled into the kernel.
>
> > ifconfig eth0 192.168.0.1 up
> > route add -net 192.168.0.0 netmask 255.255.255.0 up
>
> I'm not sure which command the next two lines referenced, but I'm
> betting that y'all do. ;-)
>
> attempting to configure eth0 by contacting a DHCP server.
> modprobe: can't locate module net-pf-17
modprobe cannot find a module called af_packet.o make sure you have it
compiled into your kernel. If it is compiled into the kernel comment all
the aliases out of /etc/conf.modules for eth0, they are of course only
needed when one uses modules.
#
# Networking options
#
CONFIG_PACKET=y
make sure you have this one as well.
CONFIG_FILTER=y
The chances are you have otherwise DHCP would have barfed about it, or it
did not get that far because it could not find any af_packet support.
>
> <snip>
> > 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.
>
> I remember that I answered 'Y' at the above prompt
Yup, as i said the error message mean its compiled into the kernel.
> Thanks. I may get around to asking about to_kernel .vs. to_module,
> later.
> And, much later, why when I configure a kernel with seemingly little
> includes, is the kernel 'too big'.
> 'make bzImage' and 'make bzdisk' work fine.
Because so many things answered as "y" make a kernel above 512K, which i
belive is the limit, however i am not all to sure on just what the actual
limit is, bzImage can compile a larger image, BUT the larger the image the
larger the hunk of memory it will grab, just think of all the samll things
in a kernel which are only used "now and again" they will hog your memory.
I strongly advise the use of modules, but its what you want and its your
choise.
--
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
