Hi, I know we can pass options to a module by using modeprobe.conf
I would like to know how can I pass options to a module that is statically compiled into kernel?
I want to compile my sound card(snd_hda_intel) into kernel but I have to pass "option model=lenovo" parameter to work correctly.

Any ideas?

I don't think that will work. It's a feature of modprobe that lets you pass options when loading a module. I could be wrong, but I think this is the case. Also, it used to be advised to build all sound drivers as modules to insure proper operation -I'm not sure if this advice still holds, but that's what they used to say -basic sound support hard-linked in the kernel, but individual drivers as modules.

OK,if there is no solution I have to compile my sound card as a module.

Um, it's possible, but you have to basically pass them to the kernel at boot time, which is unpleasant to say the least. Collect enough of these and what you type to lilo just to get the machine to boot could become a small novella.

The drivers for Intel HDA in particular are currently undergoing "heavy flux" (which is a nice way of saying "changing like mad") and compiling them statically is nowhere close to a useful thing to do. Don't bother.

If you're having trouble with Intel HDA sound, the only thing that's actually likely to work is to upgrade your kernel. The only worrisome part is that since kernel 2.6.23.x is using ALSA 1.0.15 as it's base, and not ALSA 1.0.14 (which is the version of the libraries and so forth that Slackware ships) you might wind up needing to upgrade all the ALSA userspace stuff--then again you might not. At the very least check the ALSA changelog for anything relating to the chipset variant you have or just try the latest 2.6.22.x kernel, since it still uses the same userspace stuff as what Slackware ships. If that sorts it you can stop there instead of having to try 2.6.23.x.

(FWIW, I am using 2.6.22.15 on my laptop for this very reason.)