[lug] network issue/redhat linux 8.0
Andrew Gilmore
agilmore at uc.usbr.gov
Fri Dec 6 08:30:42 MST 2002
what happens when you remove the :1 from the end of the DEVICE=eth0:1,
and ifup eth0 ?
I'd suggest removing the irq option from modules.conf as well.
Andrew
r ms wrote:
>
>
> The following is an excerpt of the log....the last line indicates that
> the dhcclient cannot bind socket to the interface.....I checked the
> /proc/interrupt file and the nic does nor interrupt 5 show up...so
> my question....is the NIC controller interrupt supposed to be in this file?
>
> Thx...Ron
>
> Excerpt:
> ______________
>
> Dec 4 21:06:31 localhost kernel: 3c59x: Donald Becker and others.
> www.scyld.com/network/vortex.html
> 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
> Dec 4 21:06:32 localhost /etc/hotplug/net.agent: invoke ifup eth0
> Dec 4 21:06:39 localhost dhclient: Bind socket to interface: No such
> device
> Dec 4 21:06:39 localhost dhclient:
> Dec 4 21:06:39 localhost dhclient: If you did not get this software
> from ftp.isc.org, please
> Dec 4 21:06:39 localhost dhclient: get the latest from ftp.isc.org and
> install that before
> Dec 4 21:06:39 localhost dhclient: requesting help.
>
>
>
>
>
>
>
>> From: John Karns <jkarns at csd.net>
>> 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, 5 Dec 2002 21:43:44 -0500 (COT)
>>
>> On Thu, 5 Dec 2002, Tony Dyson said:
>>
>> > 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?
>>
>> Are you confusing it with the 3c509? Those were 10mb ISA cards which had
>> a PnP feature which one was better off disabling. And a DOS utility to
>> set IRQ & PnP. The 3c59x however (aka cyclone) is a PCI card. I've had
>> little trouble with them, although I did have a problem with one recently
>> after upgrading to a faster mobo - the driver loaded ok, but all
>> throughput was garbled.
>>
>>
>> On Thu, 5 Dec 2002, r ms said:
>>
>> >
>> >> 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
>>
>> While it probably doesn't have much of an effect, the attempt to force
>> the
>> interrupt in the options line is superfluous, as the machine BIOS sets
>> the
>> IRQ before Linux boots, and the driver doesn't set the IRQ. Try
>> examining
>> /proc/interrupts to see if you have a conflict. Do you have dhclient or
>> dhcpcd running to set the IP@? If so, you should see a reference to dhcp
>> in the system logs.
>>
>> ----------------------------------------------------------------
>> John Karns jkarns at csd.net
>>
>>
>>
>>
>> _______________________________________________
>> Web Page: http://lug.boulder.co.us
>> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>
>
>
> _________________________________________________________________
> MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
> http://join.msn.com/?page=features/virus
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>
More information about the LUG
mailing list