slmodem

[mcrandal]

After having upgraded my home laptop from RH9 to FC2 I decided I'd best get the modem working. Before upgrading I downloaded the latest modem driver (slmodem-2.9.7.tar.gz), who's README indicated that it works with the 2.6 kernel.

So it built fine and after a little hoop jumping the modem kinda works. Kppp cannot see the modem at all, however wvdial can (pointing at the same device /dev/modem). But after wvdial has been connected for a minute or so X hangs, no keyboard or mouse input is reflected on the screen. If anyone has this modem driver working on FC2 I'd appriciate knowing how you managed it :)

[blahrus]

I had it working very very easly . . . . .

un tared the file, cd'ed into it

make

make install

modprobe slamr

/usr/sbin/slmodemd --country=USA /dev/slamr0

and then it should tell you what device it sets it as

and change /dev/modem to that.

then so at boot it does a modprobe slamr and /usr/sbin/slmodemd --country=USA /dev/slamr0 runs the modem driver at boot. you need to add it to

vim /etc/rc.local


at this to the end of it.


modprobe slamr > /dev/null 2>&1
/usr/sbin/slmodemd --country=USA /dev/slamr0 > /dev/null 2>&1 &

[mcrandal]

I have already done all this and the modem works. However after about a minute of being connected X seems to hang, becoming unresponsive to either mouse or keyboard.

Any further ideas?

[andre@home]

Originally posted by blahrus
I had it working very very easly . . . . .
so far so good..... but i got a /dev/ttySL1 or something to connect with in KPP...
But that does not work as it is a softmodem and the link to /dev/modem does not work..
message something like: no such modem or file exist...

In the readme there is one remark about such a problem without a solution.... so i googled and found something like: try to install a hardware modem and after that make the link to that.... (i had a 28k8 serial modem lying around....)
(i forgot the internet link).
It works. I will have to put the code in some rc.local probalby else loosing it after every reboot.....

some of the commandlines:

[root@mobail root]# /usr/sbin/slmodemd --country=NETHERLANDS /dev/ttyS0 &

[root@mobail root]# SmartLink Soft Modem: version 2.9.7 May 31 2004 20:58:43
modem `ttyS0' created. TTY is `/dev/pts/3'
symbolic link `/dev/ttySL64' -> `/dev/pts/3' created.
Use `/dev/ttySL64' as modem device, Ctrl+C for termination.

after that in another term:
[root@mobail root]# ln -s /dev/ttySL64 /dev/ttyS0


and then configure KPP with /dev/ttyS0 and testing was ... OK.
See picture:
http://www.tomcomdesign.com/inet/slmmodemtest.jpg
PS:
Modffy the tttySL64 to your situation.
And download the real latest version as the same version with an older date did not work (confusing these dates as i was concentrating on the version not on the date first...):
[root@mobail root]# tar -xvzf slmodem-2.9.7.tar.gz

edit: if you get a message "/dev/ttyS0 exists allready" or something similar.. you must remove it on beforehand doing all this.
rm /dev/ttyS0
answer: y
After some reboots i saw this problem. This also means that if you want a script this must be done automatically


My system:
Asus L3800C with 40GB/512MB, winmodem, Realtek netcard, ect (standard running @ 1. 8 GHz)

some messages on the modem hardware:
dmesg
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 74227 usecs
intel8x0: clocking to 48000
slamr: module license 'Smart Link Ltd.' taints kernel.
slamr: SmartLink AMRMO modem.
slamr: probe 8086:2486 ICH card...
PCI: Setting latency timer of device 0000:00:1f.6 to 64
slamr: mc97 codec is SIL21
slamr: slamr0 is ICH card.

lspci -vv output
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02) (prog-if 00 [Generic])
Subsystem: Asustek Computer, Inc.: Unknown device 1496
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 11
Region 0: I/O ports at e200
Region 1: I/O ports at e300 [size=128]

[mcrandal]

This still isn't working for me. Using the 2.9.9 driver, still hangs X after a few moments of connectivity. I am using FC2. Haven't tried it with alsa.

Any ideas?

[merith]

Have you tried gnome-ppp, I currently have it working(though I have not fully tested the link as yet as I normally connect via the network) and it recognizes /dev/modem after you have created a symbolic link from it to your modem.

type in gnome-ppp into the web and to install it is the standard configure,make, make install process.

[andre@home]

generally you need ALSA as you need full duplex... does your driver has that fully working?

[mcrandal]

I've tried Kppp, wvdial and gnome-ppp all of which cause X to hang after a few moments of connectivity.

The drivers README says that it can be compiled with alsa, I haven't done so though. I will try this...

[andre@home]

This might be your answer.....
http://www.fedoraforum.org/forum/showthread.php?t=2021

Hello folks:

The modem is finally up and working.
If you ever encounter the situation, try changing to the KDE desktop environment.

Thanks

[mcrandal]

I already use KDE....

[andre@home]

he was propably jumping to conclusions... propably he has some processes NOT running under under KDE... Look whether you can contact him as the problem really looks quite similar....