Try setting your BIOS option from "PNP OS" to "non-PNP OS", from "Windows" to "Other OS", or the equivalent.
Conexant users: See the Conexant section, above.
Unresolved symbols are a true danger of version mismatching and are, in general, bad, but are also almost inevitable with binary modules. If the fixscript reports unresolved symbols, or the module does not work despite the unresolved symbols, you may be out of luck with that kernel/module combination; however, a few common cases involve symbols like:
slhc_xxxx: You probably need to insmod the slhc module before inserting the modem/ppp modules; using modprobe rather than insmod should also obviate this problem.
printk, jiffies: Your kernel may be compiled with SMP enabled. None of the binary modules are known to be SMP-safe, and will probably only work on a single-processor machine with a single-processor kernel, i.e. SMP disabled. You should try recompiling your kernel or otherwise obtaining a version with SMP disabled. (Thanks to Tom Reinertson (treinertson(at)uswest.net))
tty_xxxxwith esscom.o: Earlier fixscripts were not able to handle the version-specific symbols in this module. More recent versions are available at http://www.test.dclabs.com.au/linmodem/fixscript) which should be able to fix this module as well.
This is an often-reported problem that may have a few, or no, solutions:
kpppwill give this error, while an alternative like
wvdialdoes not, for the same modules and hardware. You may wish to try a different ppp dialer and see if that helps.
Most Linux distributions do deposit a kernel configuration file along with the kernel. For Debian related distributions, it is the file
/boot/config-versionThe positive choices can be quickly displayed with:
grep SOUND /boot/config-version |grep -v notFor the specific example of a 2.2.17 version:
# grep SOUND /boot/config-2.2.17 |grep -v not CONFIG_SOUND=m CONFIG_SOUND_OSS=m CONFIG_SOUND_SB=m CONFIG_SOUND_MPU401=m CONFIG_SOUND_YM3812=m CONFIG_SOUND_VMIDI=m CONFIG_SOUND_YMPCI=m CONFIG_LOWLEVEL_SOUND=y
Either CONFIG_SOUND=m or CONFIG_SOUND=yes would show that the kernel has sound support (as would simple sound output).
If none of these helps, you may wish to consider trying to use a kernel version which is closer to the module. Otherwise, try the mailing list at Linmodems.org for help.
There are a couple of possible solutions to this, neither of which may work:
If all seems lost, please see the section "Troubleshooting", below , and consider sending a message with the complete information described there to the mailing list at Linmodems.org.
If a contact address is not given above, you can in general assume that it was probably somebody on contract to the manufacturer, who probably does not have the authority the update/release/change the source code, and who probably doesn't have time to reply to your email in any case. See, for example, http://lwn.net/1999/1209/a/lucent.html