3c905-tx installs with IRQ = 0

Jack Dodds <[email protected]> Sat, 24 May 2003 11:22:49 -0400
Newsgroups gmane.linux.drivers.3c509.devel
Message-ID <[email protected]>
I am attempting to do a net install of the current distribution of 
Debian Woody on a recent vintage 1.8 GHz Pentium 4 (ASUS P4B533 
motherboard) with a 3c905c-tx NIC. Specifically a 3c905cx-txnm, 
according to the sticker on the board.

I cannot get the 3c905c-tx to work at all. This is probably because it 
is being configured to use IRQ 0. During boot from CD, or after 
installing a minimal system, I get the message (approximately)

3c59x.c 18Feb01 Donald Becker etc etc etc
eth0: 3com 3c905c Toronado at 0xb400 00:04:75:c3:7c:8e IRQ 0
Warning: IRQ 0 is not likely to work

The warning is absolutely correct, of course.

The same computer/NIC/router works fine under Win98SE, either with DHCP 
or manually configured.

The BIOS identifies as an Award Medallion BIOS v. 6.0.
It also outputs the identification Award P&P BIOS V1.0A.

The driver which supports the 3c905c-tx apparently does not accept 
parameters to specify IO address or IRQ.

I downloaded and burned the latest version of the BIOS (1014) from the 
ASUS website. No change.

I tried disabling the on-board sound chip on the motherboard (I saw some 
newsgroup items re interrupt conflicts between the 3c905 and sound 
cards). No change.

I found an article on the 3com website describing a similar problem, 
"Award BIOS 4.50g sets IRQ to 0".  The solution described is to use the 
BIOS setup screen to force the PCI slot with the 3c905c-tx in it to IRQ 
10.  I have tried this and it makes no difference.

I have also tried moving the 3c905-tx to another slot.

Finally, I bought a Realtek RTL8139 NIC and tried installing it instead 
of the 3c905-tx.  I had similar problems, though I have not documented 
my efforts as carefully as with the 3c905-tx card.

It looks to me like the Award P & P BIOS on the ASUS motherboard has 
some major problem. Perhaps Windows does its own P & P allocation of 
IRQs and thereby overcomes the problem.

Can anyone suggest any way to get around this problem?