On Mon, 07 Feb 2000, AMH wrote:
> Thank you all for the reply. I am in Mississauga, Ontario, Canada. What actually
> I did was to configure network from GNOME control panel -> network
> configuration. There I opened interfaces and for eth0 I gave my ip address,
> proto - dhcp, atboot -yes, inactive. For routing I gave interface - eth0,
> netmask and gateway. There is one more field "Network" I don't know what to
> write there.
>
> While booting at "Bringing up interface eth0" the system fails. Does this mean I
> haven't configured my network card?
Normally speaking, most distibutions dont ask for network ,ipaddress,
braodcast address or whatever, dhcp is dhcp, even if the card has
the default address of 0.0.0.0 it should still work, with dhcp its
the braodcast address which counts and dhcp sets that itself.
So what i am saying is just say yes to dhcp and that should be enough.
The reason you are getting problems at startup is possably because
the driver for your card, (lord knows which card you have because you
dont say), is not getting loaded at bootime.
This can be caused by several things.
1) kmod or kerneld is not getting automaticly started at bootime.
2) You have not told modprobe what card to load in /etc/conf.modules
or /etc/modules.conf
I suspect it will be number 2 causing the problem.
All i can do is give an example.
I have a 3c509 card which i use for dhcp, i have in /etc/modules.conf.
alias eth0 3c59x
The alias tells modprobe to load the driver 3c59x, now thats a PCI
card so there is no need to tell modprobe where the card is, it will
find it automaticly. Kerneld or kmod as its called thesedays will
load the driver at bootime and contact your ISP with dhcp and connect
you to the net.
Now if your card is of the ISA type, say a ne2000(compatable) then
you might need to pass parameters to modprobe to tell it where to
find the card.
So an entry in /etc/modules.conf will look something like;
alias eth0 ne
options ne io=0x300
Note the options line, that is the address where the card is to be
found, your address may be different.
Now firstly, you dont need to reboot and start over, try something
like the following.
I am presuming you have edited /etc/modules.conf and entered the
details of your card.
modprobe 3c59x
After this command the prompt should return and there should be no
messages, if you see any messages then it possably failed.
Now you can see the driver with ;
lsmod
Module Size Used by
3c59x 19112 1
Now to start the link type;
/sbin/dhcpcd
With this daemon there is no text returned when doing it this way, no
text is good news, as soon as the prompt returns you are connected.
/sbin/route will show the routes, and /sbin/ifconfig shows the
configuration and IP address.
In extram cases it can take 10 seconds before you are linked.
When you first sent your message you said help me with;
configure linux @home, i did not have the slightest idea what you
meant, now this mail might be a little late in arriving, but i hope
it helps.
BTW, there are different dhcp deamons around, once again you have not
said what distro, you are using, i have on my home page a hwlp file
for dhcp, take a look, its example has another deamon name, i belive
that was when i was using redhat 6.1, i now use corel and slackware
on my own machines, and redhat on the remote machines that i am the
system operator of, so you now have the best of both worlds.
> Thanks for any help.
--
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
