Robert, have you tried modifying the script manually? Linuxconf modifies some scripts that enable NICs at boot time, and tell the system what kind of IP to get (DHCP or Static, etc). Here is what you can do:
1) Login as Root
2) cd /etc/sysconfig/network-scripts
3) make a backup of your current script (just in case) with:
cp ifcfg-eth0 eth0-backup
4) Then, check to see that your script contains the following lines
(it might contain more, but should mainly consist only of these):
DEVICE=eth05) Then, reboot your machine. If the DSL unit is providing full DHCP, then it will assign your NIC an IP, gateway, host/domain, and DNS.
BOOTPROTO=DHCP
If it does not, let me know, and I will provide more parameters to get your card the parameters to run.
Robert Krueger wrote:
Shawn Christian wrote:
>
> Robert,
>
> I would recommend you check with your DSL provider again...I checked today, it is DHCP.
Robert
>
> On Wed, 10 May 2000, Robert Krueger wrote:
>
> > Hi,
> > I'm a new Linux user, about 2 months. I have RH 6.1 installed as a
> > workstation on one HD, Win98 on the other HD of a new Gateway GP7-600
> > Mhz machine. My DSL internet provider installed a LinkSys LNE 100TX
> > ethernet card, which the designer of the tulip driver, Donald Becker,
> > helped me get working over a course of a week. ( in Linux ) It works
> > fine in Windows.
> > Here's what's going on. My DSL ISP told me that the IP address is
> > server assigned, and so I understand that this is the DHCP protocol. I
> > have installed the correct DNS Primary and Secondary addresses.
> > Using Gnome as root, I started the Network Configuration Utility.
> > Under the General tab, I put the Primary and Secondary DNS addresses.
> > Under the Hosts tab, only the loopback address is present. (127.0.0.1),
> > I did not add anything additional. In the Interface tab, I have:
> >
> > Interface: eth0
> > Proto: DHCP
> > Atboot: Yes
> > Active Inactive
> >
> > This is all I have done. When I select "Activate" for the eth0
> > interface, the dialog box locks up, and "inactive" does not change to
> > "active". However, if I log out, then log back in, the interface is
> > now "active" and my DSL works fine with Linux as expected. If I
> > select "Enabled" in Linuxconf, ( or Yes in atboot ) Linux will now try
> > to bring up eth0 at boot time. (My original intention) When the boot
> > process starts, it gets to the following two lines, and hangs. The
> > only way I can get out is Ctrl-Alt-Del.
> >
> > bringing up interface lo
> > bringing up interface eth0
> >
> > So, even as a beginner, I assume that whatever is locking up the Network
> > Configuration Dialog box when I try to go "active" is the same problem
> > that is causing intialization of eth0 to hang up during the boot
> > process.
> > It's checking for information somewhere that probably doesn't exist, or
> > is the wrong information, is my guess. But whatever it needs, is not
> > bad enough to keep the DSL from working, as I mentioned when activating
> > from Gnome. I really don't understand the process enough to guess
> > what's wrong. I've been through the Network HOWTO a couple of times,
> > but I have too many questions. I have also searched for any recent
> > documents on getting a DSL connection to work under Linux, but can't
> > locate any.
> > I'm very close to getting this to work correctly, if someone can help me
> > along a little.
> >
> > Thankyou,
> > Robert Krueger
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-net" in
> > the body of a message to [EMAIL PROTECTED]
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
