[linux-help] Re: netcfg errors out

[John Alexander <john.alexander@xxxxxxxx>]

You might want to hold off on doing anything with the IRQs, as PCI supports
IRQ sharing. I think it has something to do with the bus mastering
capabilities of the PCI/AGP bus. When I look on my box, the video, network,
and SCSI adapters all share the same IRQ.

ja

-----Original Message-----
From: linux-help-bounce@xxxxxxxxx [mailto:linux-help-bounce@xxxxxxxxx]On
Behalf Of Dale W Hodge
Sent: Wednesday, June 07, 2000 10:03 AM
To: linux-help@xxxxxxxxx
Subject: [linux-help] Re: netcfg errors out




> -----Original Message-----
> From: linux-help-bounce@xxxxxxxxx [mailto:linux-help-bounce@xxxxxxxxx]On
> Behalf Of Bruce Bales
>
> When I do Cat proc/interrupts, there is no listing for IRQ 12.
> When I do cat proc/pci, it
> shows both the VGA controller and the eth1 at IRQ 12.  How can I
> change the IRQ for the
> eth1 board.  It is a netgear FA310TX rev-D2 using the tulip
> driver - no jumpers, of course.
> The eth0 card (isa) is at IRQ 11.

/proc/interrupts will only show those interrupts that are actually in use.
To keep the vga and net card from sharing, you might look to see if you can
turn off the interrupt on the video card.  Many newer bioses have an option
that reads "Assign IRQ to VGA?" which can be toggled off. Other options
include turning off IRQ's for parallel ports and USB devices - which you can
safely do if you aren't dual booting Windows. Even running windows, you may
be able to get by without assigning an interrupt to the printer port. If you
are using a PS2 mouse, you may be able to turn off one of the com ports and
free up another interrupt there. Also, if possible, try changing the order
of the cards in the slots.  Interrupts are often assigned to cards based on
the slot they are in. Finally, unless you are dual booting, make sure that
you answer no to "Plug and Play Operating System?" in the bios setup.

> dmesg shows the following:
> eth1: Lite-On 82c168 PNIC at 0x6000, 00 a0 cc 5c ab 35, IRQ 12.
> eth1:  MII transceiver found at MDIO address 1, config 3000 status 7829.
> eth1:  Advertising 01e1 on PHY 1, previously advertising 01e1.
> cat uses obsolete /proc/pci interface

Now this looks like the driver has found the card.  What happens when you
run  /sbin/ifconfig?  Does eth1 show up?  If not, what happens when you run
/sbin/ifconfig eth1 up? Does the interface show up when you now re-run
/sbin/ifconfig?

--dwh

---
Dale W Hodge - dwh@xxxxxxxxxxxxxxxx
Secretary & Website Maintainer - info@xxxxxxxxx
Air Capital Linux User's Group  (ACLUG)
---




-- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi



-- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi