[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Weird Network Card problems - 2



On Thu, Jan 02, 2003 at 06:05:37AM -0800, Ajit Warrier wrote:
> Hi list,
> 
> Looks like I posted my email at a bad time (31st Dec
> when the world does not want to think of problems!).
> So I am posting it again. Hopefully I will get some
> help this time around. Sorry for the re-posting.
> 
> I am facing a weird problem with my Network Card
> (Xircom CBE-10/100). I have installed RH80 on an IBM
> Thinkpad 600 laptop. During bootup, the card is not
> detected - only lo is started. However, after booting,
> when I do dmesg, I get to see this message as part of
> the output -
> 
> eth0: Digital DS21143 Tulip rev 48 at 0xc4865000,
> EEPROM not present, 00:4c:69:6e:75:79, IRQ 11.
> 
> Does this mean that the card has now been detected
> after some other component has been loaded as part of
> the boot process?
> 
> However, if I now do ifconfig I only get to see lo.
> ifconfig -a shows eth0 too. So I then did - ifup eth0
> and the system came back with the message 
> 
> /sbin/ifup: configuration for eth0 not found.
> 
> Usage: ifup <device name>
> 
> Assuming that I need to configure the card, I opened
> System Settings > Network from the Gnome menu. eth0
> does NOT show up in the list. SO I added it manually
> as an Ethernet connection "DEC 21*40 and clones" type.
> I set the IP address statically (one complication at a
> time, right?).
> 
> The status of eth0 in the Network tool now shows eth0
> as inactive. When I press activate, it gets activated.
> Now ifconfig shows eth0 as well with the statically
> assigned IP configuration.
> 
> This is where the problem starts (all the rest was
> just a background so that you all know how I got
> here). I can ping the IP address on eth0 but I cannot
> ping any other IP on the network. The card is working
> fine when I boot into the Windows 98 partition so the
> cable and card are fine. The net mask is correct for
> my network.
> 
> Where can the problem be? Why can I not ping the
> internal network?

Perhaps your firewalling is set to "high".  Run your firewall
configuration tool and, if your network is isolated from the Internet
by a firewall, turn firewalling off.  Note: the config tool does NOT
read your current configuration.  It always comes up ready to set it
to "high".

> So anyway, being an MS junkie, I rebooted my system.
> In the start up messages (BTW, is there a way I can
> see the startup messages in a file? they scroll by too
> fast),

Both "dmesg" and /var/log/messages contain the boot information.  To
view the latter, bring it up with "less", go to the end of file, and
search backward for "restart", to wit:

 less /var/log/messages
 # and use these keystrokes: G?restart<Enter_key>

> I see something like this when it tries to
> bring eth0 up (lo comes up fine) - 
> 
> tulip device does not seem to be present, delaying...

Strange as it may seem, that's normal.  Networking is started before
pcmcia.

> Still, when I do ifconfig, eth0 shows up and the same
> problem remains - can ping itself but not other
> internal IPs.
> 
> Please help!
> 
> Ajit

Cheers,
-- 
Bob McClure, Jr.             Bobcat Open Systems, Inc.
robertmcclure earthlink net  http://www.cumbytel.com/~bobcatos/
Linux: because I want to get there today.  Without rebooting.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]