Issue with sk/skc/msk/mskc based NIC - man sk(4) vs kernel config

[HORSTMANN, Jens]

Hi,

I have a possibly simple question. I am trying to make my Marvell Yukon
NIC work with a netbsd-6/amd64 installation. So far, I have not had any
success and I started to investigate.

I am confused with two version of the the same subject and wonder which
one is the right one. The one version will not let me to complete my
kernel configuration, the other one will produce a working kernel but
with obviously missing support for the NIC device (dmesg does not report
it, just a vendor/product ID + "not configured").


man sk(4) says:

skc* at pci? dev ? function ?
sk* at skc?
mskc* at pci? dev ? function ?
msk* at skc?


whereas the kernel config for GENERIC (i386/amd64) says:

skc* at pci? dev ? function ?
sk* at skc?
mskc* at pci? dev ? function ?
msk* at mskc?


When changing the kernel config from "msk* at mskc?" to "msk* at
skc?" I end up with when trying "config" for my kernel:

715: 'msk' cannot attach to 'skc'


I am not deep into OS development, but *could* imagine that there is a
mismatch among the above two version that is the root of the problem.
Has anyone a working msk(c) device?

Any hint to a possible solution is highly appreciated.

If you need further information or want me to test something on my
machine, just let me know.

Best regards

//Jens













--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[John Nemeth]

On Apr 4, 6:47pm, "HORSTMANN, Jens" wrote:
}
} I have a possibly simple question. I am trying to make my Marvell Yukon
} NIC work with a netbsd-6/amd64 installation. So far, I have not had any
} success and I started to investigate.
}
} I am confused with two version of the the same subject and wonder which
} one is the right one. The one version will not let me to complete my
} kernel configuration, the other one will produce a working kernel but
} with obviously missing support for the NIC device (dmesg does not report
} it, just a vendor/product ID + "not configured").
}
}
} man sk(4) says:
}
} skc* at pci? dev ? function ?
} sk* at skc?
} mskc* at pci? dev ? function ?
} msk* at skc?

This is a rather obvious typo in the manpage. Fixed.

}-- End of excerpt from "HORSTMANN, Jens"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Lloyd Parkes]

a working kernel but with obviously missing support for the NIC device (dmesg does not report it, just a vendor/product ID + "not configured").

This problem might just be caused by a new vendor/product ID for an old product, in which case a simple driver update will fix the problem. What model of NIC do you have and what is its vendor/product ID? You can check the vendor/product IDs yourself if you feel like diving in. The attachment source is in src/sys/dev/pci/if_{m,}sk.c and the master list of PCI devices is in src/sys/dev/pci/pcidevs.

Cheers,
Lloyd


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[HORSTMANN, Jens]

Thanks guys, for your answers.

The device is the following:

0x11ab:0x4381
Marvell Yukon 88E8059 PCI-E Gigabit Ethernet Controller

I have checked the files that you recommanded and it's not listed there.
Do you think it's worth adding it? As far as I can see the DragonFly
version of the driver has it included. At least it works fine and
out-of-the box with a DragonFly 3.x.x.

How is the procedure? Adding a line in src/sys/dev/pci/pcidevs? The if_*
files seem to be generated, aren't they?

Cheers

//Jens


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Lloyd Parkes]

Post by HORSTMANN, Jens
Thanks guys, for your answers.
0x11ab:0x4381
Marvell Yukon 88E8059 PCI-E Gigabit Ethernet Controller
I have checked the files that you recommanded and it's not listed there. Do you think it's worth adding it? As far as I can see the DragonFly version of the driver has it included. At least it works fine and out-of-the box with a DragonFly 3.x.x.
How is the procedure? Adding a line in src/sys/dev/pci/pcidevs? The if_* files seem to be generated, aren't they?

Files are generated from pcidevs, but not the if_* files. You have to update those by hand. The pattern should be fairly obvious though.

Cheers,
Lloyd
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de