[NCLUG] ds: no socket drivers loaded!

[Christopher C.J. Keist]

Thank you for the reply. I hate to think this could just be a 
coincidence that my network card just went bad at same time I was trying 
to add support for my modem.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dev.txt
URL: <http://lists.nclug.org/pipermail/nclug/attachments/20021115/0f8a6645/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg.txt
URL: <http://lists.nclug.org/pipermail/nclug/attachments/20021115/0f8a6645/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: modules.txt
URL: <http://lists.nclug.org/pipermail/nclug/attachments/20021115/0f8a6645/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pci.txt
URL: <http://lists.nclug.org/pipermail/nclug/attachments/20021115/0f8a6645/attachment-0003.txt>
-------------- next part --------------

On Thursday, November 14, 2002, at 02:53  PM, John L. Bass wrote:

> Christopher "C.J." Keist <cjay at engr.colostate.edu> writes ...
>> No, I didn't touch the kernel at all.  Just installed the driver for 
>> the
>> modem (rpm package), instructions said nothing about building a new
>> kernel.  I don't have any PCMCIA support, correct me if I'm wrong, but
>> PCMCIA I thought was only needed for laptops.
>> The loading of that driver must of messed up something with startup
>> scripts or something.  Because the network driver is not being loaded
>> even if I boot with my backup kernel, which is suppose to be my safety
>> net when I screw up my default kernel.
>
> Hi,
>
> You didn't provide much help for a systems hack to help you debug. For a
> Redhat based system to initialize a network card on boot several things
> have to be correct.
>
> 	1)  /etc/modules.conf needs to alias the device(s), such as:
>
> 		alias eth0 airo
> 		alias eth1 tulip
> 		alias eth2 3c59x
>
Yes it has a line "alias eth0 3c59x

> 	2) in /etc/sysconfig/network-scripts/ifcfg-eth0 needs to be a
> 	   valid set of defines to be "sourced" by the "ifup" scripts:
>
> 		DEVICE=eth0
> 		BOOTPROTO=none
> 		IPADDR=192.168.0.1
> 		NETMASK=255.255.255.0
> 		BROADCAST=192.168.0.255
> 		NETWORK=192.168.0.0
> 		USERCTL=no
> 		ONBOOT=yes
>
> 	   with ONBOOT=yes necessary.
>
Yes the file is there and has all correct values.

> 	3) some network card drivers will not properly initialize unless
> 	   the media is plugged into an active/terminated subnet/hub.
>
Yes, it is plugged into an active network port.

> Debugging has several steps, first check /var/log/dmesg and 
> /var/log/messages
> for the startup sequence to check logging for the driver and network 
> scripts.
> You may find some useful chatter or nothing depending on the driver.
>
Yes, according to dmesg the Network driver is being seen, file is 
attached.

> Second check that the driver is loaded and bound to the network using 
> "lsmod"
> which besides all the other lines should show the network driver listed 
> in
> /etc/modules.conf:
>
> 	Module                  Size  Used by    Not tainted
> 	3c59x                  28552   1
>
I have the drive compiled into the kernel and not as a module.

> Third, if the driver loaded and Used is not zero, you should find the 
> driver
> bound to the network stack as eth0 in the kernel with:
>
> 	# cat /proc/net/dev
> 	Inter-|   
> Receive                                                |  Transmit
> 	 face |bytes    packets errs drop fifo frame compressed 
> multicast|bytes    packets errs drop fifo colls carrier compressed
> 	    lo:1474079184 1638417    0    0    0     0          0         
> 0 1474079184 1638417    0    0    0     0       0          0
> 	  eth0:669562079 6143865    0    0    0     0          0         0 
> 1905925603 3730999    0    0    0     0       0          0
>
The file is attached, and does show the eth0 line in it.

> Forth, if this failed, try:
>
> 	# ifdown eth0
> 	# ifup eth0
> or
> 	# sh /etc/init.d/network stop
> 	# sh /etc/init.d/network start
>
Tried both, very strange the card I can see turns itself on and off 
continuely.

> in some cases, you might have to load the kernel module manually with 
> modprobe
>
> Is this a PCI device? did it register in /proc/pci?
>
Yes, it is the file also is attached.

> have fun!
> John
>
> _______________________________________________
> NCLUG mailing list       NCLUG at nclug.org
>
> To unsubscribe, subscribe, or modify your settings, go to:
> http://www.nclug.org/mailman/listinfo/nclug
>
---------------------------------------------------------------------------------------------------
C.J. Keist                                                     Phone: 
970-491-0630
UNIX/Network Manager                           Fax: 970-491-5569
Colorado State University                        email: 
cjay at engr.colostate.edu
Dean of Engineering

I just want the chance to prove, "Money can't buy happiness"....