asked on

PCI Resource Conflict

Hi Folks --

I have a PowerMac 6500 that was running Debian with a 2.2.20 kernel. I recently upgraded to 2.4.20-ben5, which is the only 2.4 kernel I could get to compile and (mostly) work. I have two ethernet cards in this machine, an Apple card with the DEC 21041-PA chipset and a D-Link DFE-530TX+ based on the RealTek 8139 chipset. The first uses the Tulip driver and the second rtl8139. Both of these cards worked fine under 2.2.20, but under 2.4.20-ben5 neither one of them works. Calling ifup on either of them produces a SIOCSIFADDR: No such device error.

I checked out dmesg which had the following lines:

PCI:00:0d.0: Resource 0: 00000400-000004ff (f=101), vd: 1186, dev: 1300
... (other similar lines)
PCI:00:12.0: Resource 1: 00000400-000004ff (f=101) vd: 1002, dev: 4754
resource conflict with: 400..4ff (101), name: D-Link System Inc, RTL8139 Ethernet
PCI: Cannot allocate resource region 1 of device 00:12.0
PCI: parent is c0329030:00000000-007fffff (f=100)

It certainly seems like there's a PCI conflict here, but I'm new to the world of buses and other lower-level hardware stuff. Are the two ethernet cards trying to get the same resource region, and thus neither one of them works? If so, how do I fix this? If not, what then?

Thanks very much for the help.
--dlk

Debian_user

I've only ever done this in Debian on a PC, so I may be way off here, but hopefully this will help you head in the right direction.

Assuming the drivers for these network cards are compiled as modules for the kernel, you should be able to edit /etc/modules and solve the problem. Look for (or add if necessary) the line that says "tulip" and add "options io=0x240 irq=10" (or whatever io and irq you want it to use for that card). Next go to the line for rtl8139 and do the same, except change the io and irq options to be something different. You will also want to make sure that the io and irq you assign are not going to conflict with anything else on your computer. "less /proc/interrupts" and "less /proc/ioports" is a handy way of checking this.

If that doesn't work, be sure to report back and we'll try to help some more.

dlitter1

ASKER

Thanks for the comment, but I'm afraid the drivers are compiled directly into the kernel, not as modules. Can I pass the options you mentioned in as kernel arguments at boot time? Or is there some other config file that I can modify?

ASKER CERTIFIED SOLUTION

Debian_user

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Debian_user

<correction>

You probably won't need param_1 or param_2. You will need the name value to differentiate between the two cards.

</correction>

dlitter1

ASKER

Thanks for the quick reply! I'm using BootX instead of lilo (OldWord PowerMac), but I imagine it will still work. I'll try it when I get home from work today and let you know.

--dlk

CleanupPing

dlitter1:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.

paullamhkg

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is to:

Accept Debian_user's Comments as answer

Please leave any comments here within the next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

Paul
EE Cleanup Volunteer