Greets; Have run ltmodem with all SuSe distro's to get softmodem working to send out faxes. However with 10.1 this is no longer supplied. Anyone have any idea's on how to get the modem up and running under 10.1 that would allow for incomming and out going faxes. Tried using yast to configure the modem and while it completes and identifies the modem as AMBIT Micro T23 (2647-4MG) the dev link from /dev/moden -> /dev/ttyLT0 does not exist. ideas?? /ch -- 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
On Wednesday 19 July 2006 10:56, Chris Herrnberger wrote:
Greets;
Have run ltmodem with all SuSe distro's to get softmodem working to send out faxes. However with 10.1 this is no longer supplied. Anyone have any idea's on how to get the modem up and running under 10.1 that would allow for incomming and out going faxes.
Tried using yast to configure the modem and while it completes and identifies the modem as AMBIT Micro T23 (2647-4MG) the dev link from /dev/moden -> /dev/ttyLT0 does not exist.
ideas??
/ch
Do you know what module was used on earlier SUSE versions? 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. -- 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
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 -- 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
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
On Wednesday 19 July 2006 11:39, Bruce Marshall wrote: OK will give this a try tomorrow as I am out of time for today. Thanks a lot for your help however. Regards /ch -- 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
On Wednesday 19 July 2006 12:16, Chris Herrnberger wrote:
On Wednesday 19 July 2006 11:39, Bruce Marshall wrote:
OK will give this a try tomorrow as I am out of time for today. Thanks a lot for your help however.
Tomorrow when I get some time this is the approach I will try; http://www.ubuntuforums.org/showthread.php?t=84805 as currently noting suse supplies seems as straight forward. Noticeably when in stalling the smart modem packages the needed models "slamr" are not to be found anywhere?? /ch -- 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
On Wednesday 19 July 2006 12:25, Chris Herrnberger wrote:
On Wednesday 19 July 2006 12:16, Chris Herrnberger wrote:
On Wednesday 19 July 2006 11:39, Bruce Marshall wrote:
OK will give this a try tomorrow as I am out of time for today. Thanks a lot for your help however.
Tomorrow when I get some time this is the approach I will try;
http://www.ubuntuforums.org/showthread.php?t=84805
as currently noting suse supplies seems as straight forward. Noticeably when in stalling the smart modem packages the needed models "slamr" are not to be found anywhere??
/ch
No. One thing that changed majorly with 10.1 was that Novell dropped all modules that are not a direct part (supported) by the kernel source. Check the archives for a discussion of the reasons. -- 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
On Wednesday 19 July 2006 12:57, Bruce Marshall wrote:
No. One thing that changed majorly with 10.1 was that Novell dropped all modules that are not a direct part (supported) by the kernel source. Check the archives for a discussion of the reasons.
If thats the case then there is no way that I know or can see that the winmodem in a T23 which is a http://www.thinkwiki.org/wiki/Mini-PCI_Modem_card can be support. Hope Im wrong as the solution offered previousely comes back negative..:) /ch -- 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
On Wednesday 19 July 2006 15:02, Chris Herrnberger wrote: You see the issue with smartlink is that the suse 10.1 install does not provide the needed modules even when you follow the instructions as provided by suse http://en.opensuse.org/SDB:Manual_Setup_of_the_SmartLink_Driver_(SUSE_LINUX_...) which should not deviate for 10.1 eg: suse10-1KDE:/home/chris123 # insserv -d slmodemd suse10-1KDE:/home/chris123 # /etc/init.d/slmodemd start Starting SmartLink Modem driver: FATAL: Module slamr not found. startproc: exit status of parent of /usr/sbin/slmodemd: 255 failed this is when ALSA is not used. When ALSA is used the following output is made available. suse10-1KDE:/home/chris123 # /etc/init.d/slmodemd start Starting SmartLink Modem driver: startproc: exit status of parent of /usr/sbin/slmodemd: 255 failed Remain clueless...:) /ch -- 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
On Wednesday 19 July 2006 15:53, Chris Herrnberger wrote:
On Wednesday 19 July 2006 15:02, Chris Herrnberger wrote:
You see the issue with smartlink is that the suse 10.1 install does not provide the needed modules even when you follow the instructions as provided by suse
I saw that and reported it long ago.
http://en.opensuse.org/SDB:Manual_Setup_of_the_SmartLink_Driver_(SUSE_LINUX _9.1) which should not deviate for 10.1
eg:
Why can't it? I *told* you that the modules are no longer supplied. slmodem is a high level driver providing modem function. But slmodemd needs a low level driver that will access the chipset.
suse10-1KDE:/home/chris123 # insserv -d slmodemd suse10-1KDE:/home/chris123 # /etc/init.d/slmodemd start Starting SmartLink Modem driver: FATAL: Module slamr not found. startproc: exit status of parent of /usr/sbin/slmodemd: 255 failed
this is when ALSA is not used.
When ALSA is used the following output is made available.
What alsa module did you load? modprobe ????
suse10-1KDE:/home/chris123 # /etc/init.d/slmodemd start Starting SmartLink Modem driver: startproc: exit status of parent of /usr/sbin/slmodemd: 255 failed
Remain clueless...:)
/ch
-- 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
participants (2)
-
Bruce Marshall
-
Chris Herrnberger