Donald Becker <becker@scyld.com> writes: > On 29 Jul 2002, Patrick J. LoPresti wrote: > > 00:03.0 Class 0200: 10b7:6056 (rev 20) > > What is the subsystem ID? > (The "-5" version has a subsystem ID of 0x655610b7.) Hm, how would I determine that? Or is the subsystem ID just the concatenation of the device and vendor IDs? That is, did you mean "0x605610b7"? Because that is definitely the device; see the probe messages from the updated 3c59x driver below. > Both addresses are reasonable and potentially valid. > > There might be a difference based on if the machine is set to use > PXE boot or not. Perhaps. However, I instrumented pxegrub to see what I/O address *it* found for the card, and it was 0x1800. I have tried the new scyld.com driver. It's better! Or at least, it fails differently :-). It prints the banner with no warnings: eth0: 3c59x.c:v0.99X 6/21/2002 Donald Becker, becker@scyld.com eth0: 3Com 3c1556B mini-PCI at 0x1400, e0:00:e0:00:e0:00, IRQ 11 And it no longer complains about not finding any MII transceivers. But that MAC address still looks odd... Then when I try to use the interface, it fails with: eth0: Too much work in interrupt, status e011. Temporarily disabling functions (7fee). Ideas? (Thank you very much for looking at this, by the way. I really appreciate it!) - Pat - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
