retitle 518694 slamr module doesnt behave correctly if loaded too early fixed 518694 2.9.11~20080817-1 thanks
Il 10/03/2009 04:32, The Eclectic One ha scritto: > [...] > This might have been the problem. > > That was the work-around. Thanks! Stopping sl-modem-daemon unloaded > the slamr driver. Actually, I did manually modprobe slamr (which worked > fine) and then restarted the sl-modem-daemon, but after that I get RING > messages. > > Ah yes, but I was already running sl-modem-source. It must be the order > of loading or some contention with the intel-8x0m driver. But that's > strange, as that driver doesn't appear to be loaded. AFAIK this issue happens because sometimes ACPI disables modem's interrupt at boot: as a workaround you can prevent automatic module loading at boot by blacklisting the slamr module; if no other suitable module has been loaded, sl-modem-daemon will load the slamr module. I tried to document this behaviour in README.Debian since 2.9.11~20080817-1. > Now that I have a work-around, I think I'll wait until the changes from > unstable propagate the normal way. This kernel is working wonderfully > with the source drivers I have installed (and that was easy, thanks to > module assistant). I'd rather not open another can of worms with a > driver from another kernel version. > > Thanks a bunch for the tip! > > And a huge thank you to the kernel/drivers group. It's quite amazing that > something that supports all the modules/devices below works as well as > it does. Thank you for reporting this bug! Maurizio Avogadro -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
