On Wednesday 19 July 2006 11:21, Chris Herrnberger wrote:
On Wednesday 19 July 2006 11:07, Bruce Marshall wrote:
Do you know what module was used on earlier SUSE versions?
To long ago and partition no longer exists..:)
Chk to see if there exists an Alsa module to drive your modem. I found one to replace the slamr module that works with slmodemd.
Where and which one would be helpfull. slmodemd is installed but seems not to function.
/ch
Here's what I put on the list...... about a month ago Note that what I did will probably NOT work for you since you have a different chipset. I would suggest googling for your chipset which is what I did. ====================================================================== I've been complaining about not being able to find a copy of the slamr.ko module which is needed to drive the winmodem in my Thinkpad X30. Never did find one but I found a solution... much better too. Having spent two days on this project and googling at least 20 times for "slamr Suse" and such, I finally came across someone who tried a different approach, and although in what I read he still had a minor problem, I thought I would give it a go. The old solution was to: modprobe slamr slmodemd & where slamr was the module that access the hardware (low-level) and slmodemd is the piece that provides the high-level functions of the modem. The solution (at least for me?) modprobe snd-intel8x0m slmodemd -alsa -c USA hw:1 & which accomplishes the same thing and is used in the same fashion. Works like a charm. And I suspect it might work for winmodems from other vendors too if you first load the appropriate module for that vendors chipset and then run slmodemd. Can't prove that but it seems reasonable. In any event, this is a much better solution than the original. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com