-------- Forwarded Message -------- From: wes schreiner <[EMAIL PROTECTED]> To: Thomas Hood <[EMAIL PROTECTED]> Subject: Re: [ltp] Volunteers to test mwavem 2.0 .deb? Date: Sun, 22 May 2005 23:44:54 -0500 I installed the mwavem_2.0-1 package for the following tests, though I first ran "dpkg -r mwavem" to remove the alpha package. I see you made changes to the /etc/init.d/mwavem file. The value for SERDEV at the top of that file is set to /dev/ttyS1, but I'm one of probably very few users that have the modem on the first serial port. Anyway, it works just fine. I tested both data and fax connections.
Thomas Hood wrote: >Possibly the mwave module does not have time to initialise itself before >mwavemd is started. ... > >Can you find out at what point in the boot sequence the mwave module is >loaded and what (e.g., hotplug or discover) is loading it? > > Sorry for the delay in replying. As far as I can tell the mwave module isn't loaded by either discover or hotplug. I seems to get loaded only when /etc/init.d/mwave is run. Yes, I just tested by putting an "exit 0" at the top of that file and after a reboot I see that mwave is not loaded. When I remove the "exit 0" and run "/etc/init.d/mwavem start" then the module is loaded, so I'm guessing that kmod is responsible for that. I still get a line in syslog of: mwavemd: mwmipc1::mwmIPC1InterruptHandler, WARNING usControlStat was 0 (setting to 4) but everything is working fine. And it continues to work correctly after multiple invocations "/etc/init.d/mwavem restart" >Please tell me what kernel you are using. > > 2.4.28 with the LCK patchset (see <http://www.plumlocosoft.com/kernel/>) >Do you have the sometimes-failing-to-start-on-boot problem with mwavem >version 1.0.4-1 also? > > I can't say that I would notice most of the time, I rarely use the modem. With 1.0.4-1 once in a while I would see a hang on boot, at the point where the mwavem init script runs. It would not happen on two consecutive boots. >Do you have the sometimes-failing-to-start-on-boot problem with both >Linux 2.4 and Linux 2.6? > > There is no 2.6 kernel on my 600E, so I have no information there. I use this 600E for audio work, and thus I need the low-latency and kernel preemption patches included in the LCK patchset. 2.6 kernels are only now approaching the performance of 2.4.x kernels when patched for low latency, so while I haven't been able to use 2.6 kernels before I might put a 2.6 kernel on my 600E before long. I tried several reboots and managed to get one where the modem is non-responsive until I run "/etc/init.d/mwavem restart". It does look like some sort of timing problem, but it maybe it comes about because of the patched kernel I use. I did get the same warning in syslog, but I seem to get that once every boot. This isn't much of a problem for me since I have an easy workaround and I don't use the modem much anyway. The warning I get has nothing to do with a race between the mwave module loading and mwaved starting up. To prove this, I first disabled /etc/init.d/mwavem again with an "exit 0" and rebooted. After reboot I confirmed that nothing had loaded mwave. I then manually loaded mwave with "modprobe mwave" and confirmed that it was loaded. Then I removed the "exit 0" from /etc/init.d/mwavem and ran it with the "start" parameter. I got the same warning in syslog as above. Yet the modem worked fine. If I am the only one that reports this non-responsive modem problem then don't worry about it, it might just be something in my system. In my tesing today I rebooted about eight times and restarted mwavemd about 20 times, and in all of that only once had a non-responsive modem. Thanks for maintaining this package. wes -- Thomas Hood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
