As I remember, the de4x5 is an older chipset. The 21142 should use the tulip driver. The only boards I ever saw that actually used this chip were EISA boards for the DEC PCs.
On Tuesday 16 November 2004 10:30, Alex Williamson wrote: > Package: discover1-data > Version: 1.2004.11.09 > Severity: Normal > > Bug #267302 switched the default for "DECchip 21142/43" from tulip to > de4x5. Unfortunately, this breaks my system which only works with the > tulip. Device in question: > > # lspci -vvv -s 00:01.0 > 0001:00:01.0 Ethernet controller: Digital Equipment Corporation DECchip > 21142/43 (rev 41) Subsystem: Hewlett-Packard Company: Unknown device 104f > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- > DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 80 (5000ns > min, 10000ns max), Cache Line Size: 0x20 (128 bytes) Interrupt: pin A > routed to IRQ 49 > Region 0: I/O ports at 0d00 [size=128] > Region 1: Memory at 00000f0100041000 (32-bit, non-prefetchable) > [size=1K] Expansion ROM at 00000000c0000000 [disabled] [size=256K] > > # xxd /sys/devices/pci0001:00/0001:00:01.0/config > 0000000: 1110 1900 0700 8002 4100 0002 2050 0000 ........A... P.. > 0000010: 010d 0000 0010 04c0 0000 0000 0000 0000 ................ > 0000020: 0000 0000 0000 0000 0000 0000 3c10 4f10 ............<.O. > 0000030: 0000 00c0 0000 0000 0000 0000 cf01 1428 ...............( > 0000040: 00bc 0000 0000 0000 0000 0000 0000 0000 ................ > 0000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 0000060: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 0000070: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 0000080: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 0000090: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 00000a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 00000b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 00000c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 00000d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 00000e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 00000f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > > This occurs on an ia64 HP Superdome system. I also see that the > standard 4-port tulip card offering from HP has the same device/vendor: > > 0000:41:04.0 Ethernet controller: Digital Equipment Corporation DECchip > 21142/43 (rev 41) Subsystem: Hewlett-Packard Company: Unknown device 125a > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ > Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- > DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 128 (5000ns > min, 10000ns max), Cache Line Size: 0x20 (128 bytes) Interrupt: pin A > routed to IRQ 58 > Region 0: I/O ports at 3180 [size=128] > Region 1: Memory at 0000000098103000 (32-bit, non-prefetchable) > [size=1K] Expansion ROM at 00000000980c0000 [disabled] [size=256K] > > The de4x5 module loads, then promptly oopes when the installer tries to > ifconfig it. The tulip driver works just fine. Given the previous bug > #267302 there's obviously some disagreement on which module to use. I > know that nobody else (RH/SuSE) is using the de4x5 module on ia64. Is > there some way we can key on architecture? Can we add Subsystem > Device/Vendor ID checking? Thanks, > > Alex -- ************* Jim Lieb Wild Open Source Inc. [EMAIL PROTECTED] Cell: 831.295.9317 Office: 831.421.0883 Fax: 831.421.0885 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
