>>>>> "Steve" == Steve Langasek <[EMAIL PROTECTED]> writes:
Steve> Ok, thanks. FWIW, this same chip works fine for me in an LX164
Steve> system; but you're the second to report problems with it on
Steve> other alphas -- unfortunately, though, the first to confirm
Steve> that it's a problem with current 2.6 kernels.
Another example of de2104x misbehaviour on Alpha (this time with an
AlphaStation 500/333):
00:06.0 0200: 1011:0002 (rev 24)
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: 255
Interrupt: pin A routed to IRQ 29
Region 0: I/O ports at 9800 [size=128]
Region 1: Memory at 0225b000 (32-bit, non-prefetchable) [size=128]
With de2104x:
de2104x PCI Ethernet driver v0.7 (Mar 17, 2004)
eth0: 21040 at 0xfffffc860225b000, 00:f8:22:fb:cd:ec, IRQ 29
With de4x5:
0000:00:06.0: DE434/5 at 0x9800, h/w address 00:00:f8:22:fb:cd,
and requires IRQ29 (provided by PCI BIOS).
Notice how the ethernet address is shifted by 8 bits to the left. Of
course, the real ether address is the one reported by de4x5 (checked
from SRM).
This is not as bad as with the Multia, since the driver actually
works, and I managed to install etch over the network. This is
extremly confusing though.
Regards,
M.
--
And if you don't know where you're going, any road will take you there...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
