On Wed, 2006-12-13 at 22:49 +0000, Bruce M. Simpson wrote: > Yes. It looks like (from dmesg) that your card is a Yukon 1. I think I > managed to get the sk driver to attach to the PCI-e Yukon in my ASUS > machine and had similar problems, though this was many months ago. The > msk driver might work for you. Well .. i got around to trying the msk driver this morning and unfortunately (after adding the pci-id to the msk driver) the card probes, but doesn't attach because of the msk-driver rejecting device-id's that are't Yukon II chips. (the if-section below in if_msk.c) if (sc->msk_hw_id < CHIP_ID_YUKON_XL || sc->msk_hw_id > CHIP_ID_YUKON_FE) { device_printf(dev, "unknown device: id=0x%02x, rev=0x%02x\n", sc->msk_hw_id, sc->msk_hw_rev); error = ENXIO; goto fail; } My DGE-530T however has id=0xb1, rev=0x09 which seems to be what if_msk considers CHIP_ID_YUKON_LITE. So it looks that without further hacking on the msk driver trying to use if_msk instead of if_sk is an excercise in futility, though it was definitely worth a shot. I'll be watching the interrupts as soon as i can get a hold of my neighbour which should probably be sometime later today. If in the meanwhile people have other suggestions i might try, send them my way and i'll give it a shot :) -- Pascal HofsteeReceived on Thu Dec 14 2006 - 08:22:11 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:03 UTC