Re: forcing a pci nic to use a different irq?
Matthew Garman muttered: According to the Ethernet HOWTO, the most common cause of this problem is an IRQ conflict. This seems believable, because... cat /proc/interrupts CPU0 0: 42726 XT-PIC timer 1: 2024 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 12012 XT-PIC 5: 3 XT-PIC soundblaster 11: 5986 XT-PIC sym53c8xx, eth0 12: 4799 XT-PIC PS/2 Mouse 14: 2 XT-PIC ide0 NMI: 0 ERR: 0 You can see that both my SCSI controller and my ethernet card live on IRQ 11. I'm not an expert on IRQs, but my (vague!) understanding is that it's actually the PCI controller that uses the IRQ, so if these devices are on the same bus, it doesn't necessarily indicate a conflict. Joost is absolutely on the right track: what changed between when it worked and when it quit working? This should be a clue. Also, before pinging it from another host, make sure that ifconfig returns good info for eth0 and that it can ping itself at eth0's TCP/IP address--if either of these fail then you already know it's not talking. One standard trouble-shooting technique for PCI devices is to swap the cards into different slots. HTH, Paul
Re: forcing a pci nic to use a different irq?
Sorry, I'm joining this conversation a little late so forgive me if this has already been said... Is your ethernet card an ISA one? If so there should be an configuration application that will let you move it to a different irq. Otherwise in your BIOS somewhere there should be a setting to assign irqs to individual PCI slots from which you can give each slot it's own irq. The card in that slot will use that irq of course. Irq sharing is possible though. My interrupt table looks like the following and I have no problems: CPU0 CPU1 0: 11296449 11304831IO-APIC-edge timer 1: 0 2IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 3:76823767694587IO-APIC-edge eth0 8: 2 0IO-APIC-edge rtc 9:47665034764709 IO-APIC-level advansys, aic7xxx, eth1 10: 5842 5890 IO-APIC-level advansys, aic7xxx 11: 18862 18793 IO-APIC-level advansys 12: 4 3 IO-APIC-level advansys 13: 1 0 XT-PIC fpu 14: 183701 180103IO-APIC-edge ide0 15:20034232014463IO-APIC-edge ide1 NMI: 0 ERR: 0 ttyl, james Paul Mackinney wrote: Matthew Garman muttered: According to the Ethernet HOWTO, the most common cause of this problem is an IRQ conflict. This seems believable, because... cat /proc/interrupts CPU0 0: 42726 XT-PIC timer 1: 2024 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 12012 XT-PIC 5: 3 XT-PIC soundblaster 11: 5986 XT-PIC sym53c8xx, eth0 12: 4799 XT-PIC PS/2 Mouse 14: 2 XT-PIC ide0 NMI: 0 ERR: 0 You can see that both my SCSI controller and my ethernet card live on IRQ 11. I'm not an expert on IRQs, but my (vague!) understanding is that it's actually the PCI controller that uses the IRQ, so if these devices are on the same bus, it doesn't necessarily indicate a conflict. Joost is absolutely on the right track: what changed between when it worked and when it quit working? This should be a clue. Also, before pinging it from another host, make sure that ifconfig returns good info for eth0 and that it can ping itself at eth0's TCP/IP address--if either of these fail then you already know it's not talking. One standard trouble-shooting technique for PCI devices is to swap the cards into different slots.
forcing a pci nic to use a different irq?
Hello: I have a two computer home LAN set up. I cannot get the machines to see each other (i.e., neither can ping the other). When I try to ping the other computer, it looks as though information is leaving, but not coming back, since the activity lights on my switch flash when I run ping. According to the Ethernet HOWTO, the most common cause of this problem is an IRQ conflict. This seems believable, because... cat /proc/interrupts CPU0 0: 42726 XT-PIC timer 1: 2024 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 12012 XT-PIC 5: 3 XT-PIC soundblaster 11: 5986 XT-PIC sym53c8xx, eth0 12: 4799 XT-PIC PS/2 Mouse 14: 2 XT-PIC ide0 NMI: 0 ERR: 0 You can see that both my SCSI controller and my ethernet card live on IRQ 11. How can I force this card not to use IRQ 11? My ethernet drivers are compiled into the kernel. So I tried doing this from the LILO prompt: Linux ether=9,0,0,0,eth0 It totally ignored the parameter, and loaded on IRQ 11 anyway. So then I tried adding the following line to /etc/lilo.conf append=ether=9,0,0,0,eth0 Then I *ran lilo*, rebooted, but the result was the same: the card still loads on IRQ 11. The card *used* to work fine. In fact it just started having this problem, and I can't figure out why. Thanks for any help, Matt -- Matt Garman, [EMAIL PROTECTED] I'll tip my hat to the new constitution, Take a bow for the new revolution Smile and grin at the change all around, Pick up my guitar and play Just like yesterday, Then I'll get on my knees and pray... -- Pete Townshend/The Who, Won't Get Fooled Again
Re: forcing a pci nic to use a different irq?
On Tue, Jul 24, 2001 at 06:25:19PM -0500, Matthew Garman wrote: cat /proc/interrupts 11: 5986 XT-PIC sym53c8xx, eth0 append=ether=9,0,0,0,eth0 Then I *ran lilo*, rebooted, but the result was the same: the card still loads on IRQ 11. The card *used* to work fine. In fact it just started having this problem, and I can't figure out why. Perhaps you upgraded your kernel? Or you moved cards around? You can manually set interrupts in most bios setup menus, I believe. Also look at the setpci(8) manpage in the pciutils package. Cheers, Joost
