Monitor problems (was hi) + Question

[Jerry Feldman]

The kernel probes devices when it starts up. The dmesg command should show 
your kernel messages as below. Also, use your ifconfig command to see if 
the device is operational. This reports the IP address, mask and other 
properties of each interface.
--- kernel boot up message example (from 2.2.13 kernel).
ne2k-pci.c:vpre-1.00e 5/27/99 D. Becker/P. Gortmaker 
http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html
ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0x6600, IRQ 9.
eth0: RealTek RTL-8029 found at 0x6600, IRQ 9, 52:54:00:DA:02:4F.
ne2k-pci.c: PCI NE2000 clone 'Winbond 89C940' at I/O 0x6700, IRQ 10.
eth1: Winbond 89C940 found at 0x6700, IRQ 10, 00:20:78:13:4B:C2.   
--------------- ifconfig example: ----------------
       gaf at gaf:~ > sudo /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 52:54:00:DA:02:4F
          inet addr:XX.XX.XX.XX  Bcast::XX.XX.XX.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:123342 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13377 errors:0 dropped:0 overruns:0 carrier:0
          collisions:110 txqueuelen:100
          Interrupt:9 Base address:0x6600

eth1      Link encap:Ethernet  HWaddr 00:20:78:13:4B:C2
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2046 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2734 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1 txqueuelen:100
          Interrupt:10 Base address:0x6700

eth1:0    Link encap:Ethernet  HWaddr 00:20:78:13:4B:C2
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:10 Base address:0x6700

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:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0                     
--------------------------
Colin Principe wrote:

> On a unrelated topic, can anyone recommend some internal tests on Debian 
> 2.0.34 to see if a network card is active?  I'm trying to ping across a 
> 10-Base-T and the remote machine doesn't recognize the IP address.  I'm 
> trying to diagnose all problems along the chain, but I wanted to make sure 
> my system was seeing the card.  The IP address I'm using shows up at eth0 
> when I do ifconfig.
-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).