Thanks for the instructions on how to use svn-buildpackage. I have installed the updated package, and it resolves the modutils issue and the "progess" issue. It also includes the alias which allows the kernel mwave module to be automatically loaded by the hot plug system. In the process of my testing, I believe I have discovered the "environmental difference" that I referred to earlier.
I am using a stock Debian Lenny kernel, version 2.6.26-1-686. If I boot this kernel with the kernel boot parameter "acpi=off", then the mwavem user-space daemon runs fine. But if I use the kernel boot parameter "acpi=noirq", or if I do not use any ACPI-related boot parameter, then the user-space daemon fails to load. The message on the console is Starting Mwave modem support: (aborted early) failed! By using less /var/log/syslog I can see slightly more detailed messages. They are as follows: mwavemd: Started the Mwave manager ... mwavemd: Initializing mwave manager... mwavemd: MwaveAPIInit StartMwaveSubsystem failed mwavemd: mwavemd: ERROR initializing mwave manager... mwavemd: mwavemd: Cleaning up, unlinking /dev/Mwave-modem and exiting. It sure would be nice if the mwavem user-space daemon would peacefully coexist with ACPI. I'd hate to have to choose between the two. ACPI gives me a lot of other features that it would be nice to have. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
