Hi,
Thanks for your help. I tried all this stuff but "pump" doesn't work for me. It says
operation failed.
Also I checked up with the make menuconfig and under network device options, I wasn't
able to find my SMC ethernet driver in it. The only thing under eth0 was FDDI which I
don't think is for me but that too was configured inside the kernel and not as a
module.
Doing ifconfig gives me just "lo" information. But if I do "ifconfig eth0" I can see
the eth0 information including the mac address of my ethernet card but no ip
information.
Any more suggestions ???
Thanks in anticipation,
Aamir
---
Aamir Shaikh
11104, 61st STREET,
TEMPLE TERRACE,
FL - 33617, U.S.A
PH: (813) 988-0727.
EMAIL : [EMAIL PROTECTED]
[EMAIL PROTECTED]
On Tue, 23 May 2000 23:03:53 Jim Roland wrote:
>A couple of things come to mind. I probably run one of the most difficult
>configurations known to Linux (potentially incompatible hardware), which
>is a laptop. RedHat 6.1 is on my Dell laptop.
>
>When I dock in at work, the system has 2 network cards (one in the port
>replicator, and the other a PCMCIA card). When I'm at home, I only have
>the PCMCIA card. Although I only use the port replicator while at work,
>the PCMCIA card in both cases does exactly what you're discussing.
>Furthermore, when I'm not docked, the PCMCIA card changes it's identity
>from eth1 (card #2) to eth0 (card #1).
>
>Anyway, in both cases, the PCMCIA card comes up "Delaying eth(0 or 1)
>initialization" while the Interactive setup screens scroll after the
>kernel boots up.
>
>The reason mine does this is that I have to use the PCMCIA card as a
>module. I suspect your regular network card is configured to boot as a
>module also.
>
>When the kernel comes up, since there is not a driver compiled into the
>code of the kernel itself, the system loads the module later after it's
>already started the init scripts.
>
>-------------------
>Enough of my babbling.... <grin>
>
>First, let's rule out a driver problem altogether. When you're at the
>login prompt (from text mode), run a program called "pump". What you will
>want to run is "pump -i eth0" (assuming your network card is eth0, or card
>#1). If you boot into X, get a terminal prompt and run pump. Do all of
>this as the root user.
>
>That should assign you an IP address if the Roadrunner cable modem is
>functioning correctly for dhcp. You can confirm the IP address by running
>(as root, from a shell prompt) "ifconfig". The command alone without any
>parameters will display all cards that are "UP". If an "eth" device does
>not show up, your card is not initialized still. If all is well, you
>should see something simlar to (your MAC address and other things like IRQ
>will differ, that's okay):
>
># ifconfig
>lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:22 errors:0 dropped:0 overruns:0 frame:0
> TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:0
>
>eth0 Link encap:Ethernet HWaddr (your MAC address)
> inet addr: (IP from DHCP) Bcast: (some addr) Mask: (netmask)
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:531 errors:0 dropped:0 overruns:0 frame:0
> TX packets:561 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:0
> Interrupt:11 Base address:0x300
>
>Now, assuming this is what you see (an IP address in the "inet addr"
>field), it will probably be likely that your kernel is compiled for a
>module load of your network card (typical with RedHat's default kernel).
>
>Next, we will want to put your network card's driver in the kernel as a
>compiled-in driver, not as a module. This will allow the kernel to boot
>up already having detected and initialized the hardware-level of the
>network card. Then, pump will acquire a DHCP address while the init
>scripts (Interactive Setup) are running.
>
>You should have the kernel source installed already in /usr/src/linux. If
>so, go to that directory and type "make menuconfig". It will compile some
>items necessary for the menus and present you with a menu. Skip down to
>Network Devices, and find your network card in the menus. If it has a
>"<M>" selected, highlight it and hit "Y" or "y", changing it to a "<*>".
>This means that it's now not a module, but to be compiled into the kernel.
>
>Exit the kernel config (saving the changes). Then run the following
>commands:
> make dep
> make bzImage
> make install
>
>If you have compiled all and installed the new kernel correctly, You will
>see a set of "Added (something)" lines at the end. This indicates that
>the kernel has been compiled and installed. The "lilo" step has been run
>for you (the "Added" lines, which reflect bootable partitions you have
>setup on the system).
>
>Reboot and the card should work.
>
>Good luck.
>
>
>-------------------------------------------------------
>Jim Roland, President
>Roland Internet Services, "The host with the most"
>Offering premier web, email and CGI custom programming.
>Ask us about Frontpage98 Extensions!
>http://www.roland.net/ [EMAIL PROTECTED]
>-------------------------------------------------------
>
>
>On Tue, 23 May 2000, Aamir Shaikh wrote:
>
>> Date: Tue, 23 May 2000 08:19:19 -0700
>> From: Aamir Shaikh <[EMAIL PROTECTED]>
>> To: Jim Roland <[EMAIL PROTECTED]>
>> Cc: [EMAIL PROTECTED]
>> Subject: Re: Problem initializing eth0
>>
>> Hi,
>> Sorry to come into the middle of all this, but I too am facing a similar problem so
>thought you could help me out.
>> I'm running Roadrunner on a dualboot win98/linux RH6.1.
>> My ethernet card is an SMC Ultrachip and works fine with Win98. With Linux during
>bootup it gives a message "delaying eth0 initialization" and then says "failed".
>When I type "ifconfig eth0" I can see the mac address of the ethernet card but I'm
>unable to assign it an ip address dynamically. I used netconf and checked it out to
>use dhcp but it just doesn't initialize.
>>
>> Can you please help me with this.
>>
>> Thanks,
>> Aamir.
>>
>>
>>
>>
>> [EMAIL PROTECTED]
>>
>>
>> On Thu, 11 May 2000 16:08:31 Jim Roland wrote:
>> >Okay. I admit I'm coming in on this in the middle, so please bear with me.
>> >
>> >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=eth0
>> > BOOTPROTO=DHCP
>> >
>> >5) 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.
>> > 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]
>> >
>>
>>
>> Get your FREE Email at http://mailcity.lycos.com
>> Get your PERSONALIZED START PAGE at http://my.lycos.com
>>
>
>
Get your FREE Email at http://mailcity.lycos.com
Get your PERSONALIZED START PAGE at http://my.lycos.com
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
