network card not detected at boot

[Bill Campbell]

On Mon, Oct 16, 2006, Vu Pham wrote:
>On Mon, 2006-10-16 at 11:08 -0500, David Bandel wrote:
...
>> next time, do lsmod before then after you get eth1 working.  I'm
>> willing to bet the module doesn't load.  If that's the case, you may
>> have a file like /etc/modules that will allow you to tell the system
>> which modules to load prior to doing anything else.  That may be all
>> you need.  Note:  watch carefully to see if YAST passes any arguments
>> to the driver.  If so, you'll need to include those as part of the
>> automagic loading.
>> 
...
>Yes, I am trying to do it. In Suse, it seems they use modprobe.conf
>instead of modules.conf. I cannot find that file but I found
>out /etc/modprobe.conf is similar to it and working on this modproblem
>right now.

One thing I do to help figure out what's going on under the hood
on systems is to create a timestamp file, run the vendor's admin
tool to change something, the use ``find'' to see what's changed.

touch /tmp/timestamp
yast2 # do something
find /etc -type f -newer /tmp/timestamp > /tmp/changedfiles

The /tmp/changedfiles will contain a list of all files in the /etc
directory that have been changed since the /tmp/timestamp file was touched.

FWIW:  The system I'm typing this on is running SLES10 on an Asus A8N-SLI
Deluxe main board, AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ with dual
10/100/1000 NICs, one nVidea with the forcedeth.c driver, the other Marvell
with the skge.c driver.  I've had no problems booting this and having it
recognize both NICs.

Bill
--
INTERNET:   bill at Celestial.COM  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676

``If you make yourselves sheep, the wolves will eat you'' -- Benjamin Franklin