[lug] network issue/redhat linux 8.0

[Tony Dyson]

A dim memory says these 3Com cards like to default to IRQ5. Is something 
else trying to use that? It smells like some kind of hardware conflict. 
3Com used to supply a DOS utility to reconfigure the card. You might try 
  forcing a different interrupt that way.

The parameter on the modules.conf options line is evidently making 
something unhappy too.

I've seen adverse comments about these NIC's & Linux in the past. Do you 
have a different brand that you could try?

r ms wrote:
>> From: Andrew Gilmore <agilmore at uc.usbr.gov>
>> Reply-To: lug at lug.boulder.co.us
>> To: lug at lug.boulder.co.us
>> Subject: Re: [lug] network issue/redhat linux 8.0
>> Date: Thu, 05 Dec 2002 16:08:46 -0700
> 
> 
>> is there an alias for eth0 in modules.conf?
> 
> 
> alias parport_lowlevel parport_pc
> alias eth0 3c59x
> options 3c59x irq=5
> 
>> what does /var/log/messages contain about the module used?
> 
> The latest log entry:
> 
> Dec  4 21:06:31 localhost kernel: 00:0a.0: 3Com PCI 3c905B Cyclone 
> 100baseTx at 0xd800. Vers LK1.1.18-ac
> Dec  4 21:06:31 localhost kernel: PCI: Setting latency timer of device 
> 00:0a.0 to 64
> Dec  4 21:06:31 localhost insmod: Warning: ignoring irq=5, no such 
> parameter in this module
> Dec  4 21:06:31 localhost insmod: Module 3c59x loaded, with warnings
> 
> 
>> what does a modprobe <module_name> report?
> 
> when I do modprobe eth0 or 3c59x, nothing is reported....
> when modprobe -a, then the following:
> alias eth0 3c59x
> options 3c59x irq5
> 
> 
>> what does ifcfg-eth0 contain?
>>
> TYPE=Ethernet
> DEVICE=eth0:1
> HWADDR=00:xx:xx:xx:xx:xx
> BOOTPROTO=dhcp
> ONBOOT=yes
> USERCTL=no
> PEERDNS=yes