The entry into /etc/conf.modules did the trick! I am networking happily...
-----Original Message-----
From: Richard Adams <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, October 20, 1998 3:46 PM
Subject: Re: can't network - delaying eth0 initialization
>According to John Kee: While burning my CPU.
>>
>> I have an old PC that I installed Linux (Red Hat 4.2) on - it's a 486
66MHz
>> with 20MB RAM. I put a standard 3COM network card in it - 3C509B. The
card
>> was configured while in DOS, then I rebooted and configured the network
>> settings using netcfg. I still get the error message "delaying eth0
>> initialization". Localhost can be seen. Are there some things I'm
missing?
>> What can I check to troubleshoot this?
>
>Bill Kocik made an excelant suggestion which could help you if you had a
PCI
>PC, considering you said "OLD" i would point my finger at No defined driver
>for your 3com card. You said also you configured the card under dos, which
>means you will know its IRQ and base address, (dont you!), and possably you
>tested the card right,??.
>
>Now if we know it works then it should work under linux, the first
>consideration is 'do i have support for a 3com card', the second if yes is
>it in the kernel or defined as a module, i would go for the module
>considering the error message.
>
>You mention "netcfg" so that should have said it found the card during the
>configuration. I dont know the name of the module for your particular card,
>but it would be something like 3c509, i will use this as the example.
>
>Check /lib/modules/$kernel_version/net for it, if you installed linux and
>took the install advice about installing a standard kernel with modules
then
>it should be there, make an entry into /etc/conf.modules;
>
>alias eth0 3c509
>
>That entry will tell kerneld what driver to use for eth0 and hopefully
>insert the module automaticly IF you start Kerneld in a bootup script.
>
>If not do;
>depmod -a
>modprobe 3c509
>
>Read the Module-HOWTO.gz in your /usr/doc dir, also
>/usr/src/linux/Documantation/networking/net-modules.txt
>
>Of course if you cant find the module in the /lib/modules dir, and you have
>a standard kernel installed by your distribution install, then you could
get
>the module off the distribution source, if all else fails compile a new
>kernel and define your needed driver either as a module or compile it into
>the kernel.
>
>I hope some of this helps.
>
>>
>> Thanks,
>> John Kee
>> [EMAIL PROTECTED]
>>
>>
>>
>
>
>--
>Regards Richard.
>[EMAIL PROTECTED]
