After I booted 2.2.19pre14 on a system with two via-rhine cards I see the
following:
via-rhine.c:v1.08b-LK1.0.0 12/14/2000 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
eth0: VIA VT3043 Rhine at 0x9400, 00:50:ba:c1:64:d9, IRQ 0.
eth0: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000.
eth1: VIA VT3043 Rhine at 0x8800, 00:50:ba:ab:60:64, IRQ 0.
eth1: MII PHY found at address 8, status 0x782d advertising 05e1 Link 0000.
and a network does not work due to these IRQ 0, I guess.
In contrast when I will boot on the same hardware 2.4.2-ac5 then I get,
among other things,
via-rhine.c:v1.08b-LK1.1.7 8/9/2000 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
PCI: Enabling device 00:09.0 (0094 -> 0097)
PCI: Found IRQ 9 for device 00:09.0
PCI: The same IRQ used for device 00:04.2
PCI: The same IRQ used for device 00:04.3
PCI: The same IRQ used for device 00:0d.0
eth0: VIA VT3043 Rhine at 0x9400, 00:50:ba:c1:64:d9, IRQ 9.
eth0: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000.
PCI: Enabling device 00:0c.0 (0094 -> 0097)
PCI: Found IRQ 11 for device 00:0c.0
eth1: VIA VT3043 Rhine at 0x8800, 00:50:ba:ab:60:64, IRQ 11.
eth1: MII PHY found at address 8, status 0x782d advertising 05e1 Link 0000.
Devices in question can be seen here:
-[00]-+-00.0 VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
+-01.0-[01]----00.0 ATI Technologies Inc Rage 128 RF
+-04.0 VIA Technologies, Inc. VT82C686 [Apollo Super South]
+-04.1 VIA Technologies, Inc. Bus Master IDE
+-04.2 VIA Technologies, Inc. UHCI USB
+-04.3 VIA Technologies, Inc. UHCI USB
+-04.4 VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
+-09.0 VIA Technologies, Inc. VT86C100A [Rhine 10/100]
+-0a.0 Symbios Logic Inc. (formerly NCR) 53c810
+-0c.0 VIA Technologies, Inc. VT86C100A [Rhine 10/100]
+-0d.0 Ensoniq CT5880 [AudioPCI]
\-11.0 Promise Technology, Inc. 20265
I do not have turned on a support for USB or audio in either of these
two kernels. They are actually configured pretty similar (within a
reason :-). But network is operational with 2.4.2-ac5. Hm...
Even with these IRQ conflicts for eth0 one would think that eth1 should
get its interrupt. It does not conflict with anything. Forgotten
'pci_enable()' somewhere?
Michal
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
