Well, I don't understand this; but I tried it again last night, and
it worked. There must have been some kind of environmental difference
between the first attempt and the second attempt (whether or not the
mwave kernel module was loaded, or whatever, who knows).
Here is what I got the first time:
--------------------
Selecting previously deselected package mwavem.
(Reading database ... 26960 files and directories currently installed.)
Unpacking mwavem (from .../archives/mwavem_2.0-3_i386.deb) ...
Processing triggers for man-db ...
Setting up mwavem (2.0-3) ...
MAKEDEV created device node /dev/or .
************************************************************************
*
* The update-modules command is deprecated and should not be used!
*
************************************************************************
Starting Mwave modem support: (aborted early) ^[[31mfailed!^{[39;49m
invoke-rc.d: initscript mwavem, action "start" failed.
dpkg: error processing mwavem (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
mwavem
--------------------
But when I tried it last night, it installed OK. I did find a bona-fide
bug in the /etc/init.d/mwavem script, however. There are a couple of places
where "log_progress_msg" is misspelled as "log_progess_msg". That should
be fixed.
Also, I have a suggestion for improvement:
When you create /etc/modprobe.d/mwave, in which the options to be passed
to the mwave kernel module when it loads are listed, you should add this
line also:
alias pnp:dIBM3760 mwave
This allows the hot-plug system to load the mwave driver automatically
during boot if it detects the presence of the Mwave chip. This avoids
having to list the driver in /etc/modules.
Many of the sound card drivers have "internal aliases" assigned to them
that allow them to be loaded in support of the chips they support.
Try "modinfo snd-cs4236" for example. In fact, I had to blacklist one of
them, snd-cs4232, to keep it from loading instead of snd-cs4236. But the
mwave driver does not have any such internal aliases; so we need to help
it out by defining the external alias above.
You can use "lspnp" to determine the alias name to use. On the ThinkPad
600, "IBM3760" was the only one whose description contained the word
"Mwave"; so I knew it was the right one. I have added this alias to
another file in /etc/modprobe.d on my system (/etc/modprobe.d/local),
and it works great. mwave now loads automatically, and I don't have to
list it in /etc/modules.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
