Trouble getting modem to work in SUSE 9.1

adam_the_noob · 10-07-2004, 12:16 AM

ok after i configure the modem i get this in the error log"

SuSE Meta pppd (smpppd-ifcfg), Version 1.16 on linux.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: --> WvDial: Internet dialer version 1.54.0
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATM1
pppd[0]: --> Sending: ATQ0
pppd[0]: --> Re-Sending: ATM1
pppd[0]: --> Modem not responding.
pppd[0]: Connect script failed
Status is: disconnected
pppd[0] died: Connect script failed (exit code 8)

Plz help me

jk73 · 10-07-2004, 04:06 AM

I was in a similar situation just recently with a winmodem on SuSE 9.1: I got it to work by typing "slmodemd" from a root console, then trying to connect.

I'm new to Linux, so hopefully someone else could provide a better more detailed response to this issue. (Please!)

DaneM · 10-07-2004, 06:30 AM

Hello everybody.

I kind-of sounds like the dialer hasn't found the modem at all. I'm not familiar with Suse's modem dialing tool (I use KPPP), but I imagine that somewhere there's an option to "query modem." Try this and hopefully you'll get something like:

ATI: 5601
ATI 1: C084
ATI 2: OK
ATI 3: U.S. Robotics 56K FAX INT V5.22.70
ATI 4: U.S. Robotics 56K FAX INT Settings... B0 E0 F1 L0 M0 Q1 V1 X4 Y0
BAUD=115200 PARITY=N WORDLEN=8 DIAL=TONE ON HOOK CID=0
&A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1 &M4 &N0 &P1 &R2 &S0
&T5 &U0 &Y1 S00=000
ATI 5: U.S. Robotics 56K FAX INT NVRAM Settings... Template Y0 DIAL=TONE
B0 E1 F1 L1 M1 Q0 V1 X4 BAUD=115200 PARITY=N WORDLEN=8
&A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1 &M4 &N0 &P1 &R2 &S0
&T5 &U0 &Y1 S00=000 S02=
ATI 6: Template Y1 DIAL=TONE B0 E1 F1 L1 M1 Q0 V1 X4
BAUD=115200 PARITY=N WORDLEN=8 &A3 &B1 &C1 &D2 &G0
&H2 &I2 &K1 &M4 &N0 &P1 &R1 &S0 &T5 &U0 &Y1 S00=000
S02=043 S03=013 S04=010 S05=008 S06=004 S07=
ATI 7: Configuration Profile... Product type US/Canada Internal Product ID:
00561002 Options V32bis,V.80,V.34+,V.90,V.92 Fax Options
Class 1/Class 2.0 Line Options Caller ID, Distinctive Ring Clo

This is what KPPP displays for my modem. Suse's tool might just say "modem found" or "modem not found." Make sure that the program is pointing to the right COM port. /dev/modem usually works, but it's sometimes nonexistant or improperly linked. Try ttyS0, ttyS1, etc. until you get a good response from your modem. You also might want to try minicom to putz around and make sure that everything looks peachy. Type this in a console:

Code:

su
<password>
minicom

This should pop up a blue box that says "initializing modem" and then give you a command line of sorts. Try typing "ATZ" and then "ATDT 5555555". You might not see everything that you're typing. If my memory serves me well this should cause your modem to dial "555-5555" (an invalid number where I live). If all this goes smoothly then /dev/modem is linked to the right COM port and your modem drivers are working. If not then you can try linking /dev/modem to different serial port (like ttyS1, etc.). Before doing this, WRITE DOWN WHERE IT'S CURRENTLY LINKED TO! To find this out, type "ls -l /dev/modem". To change where it's linked to, type this from the command prompt:

Code:

su
<password>
rm /dev/modem
ln -s /dev/ttyS1 /dev/modem

This will link /dev/modem to /dev/ttyS1. Experiment with different ones if you want.

I hope this helps! I'm no expert, so if anybody else has some suggestions, please chime in!

--Dane

adam_the_noob · 10-07-2004, 08:11 PM

didn't work
the command slmodemd didn't work

jk73 · 10-08-2004, 05:43 AM

Go to the Suse web site & there is a winmodem driver package in the downloads/updates/9.1 section: I think its called: "31 Aug 2004 ltmodem: Driver for modems with lucent chipsets "

Get the rpm, and install it. Go to YaST/System/Run level editor/, probably best to stay in 'simple mode' find slmodem (SmartLink modem driver) in the list and enable it to run at boot time (this effectively loads the driver software you downloaded and installed), then your dialer should initialise the modem and connect to your ISP.

This was the situation for me. Hope this helps!

whit_wolf1 · 10-21-2004, 09:35 PM

i tryed the ltmodem and i didnt work or i didnt install right please help
what can i do

carrie · 10-22-2004, 03:48 AM

Hello,

PREFACE .

linux@user#newbie --help
connecting to linuxquestions.org
linux@user#THANKS!

>>I tryied 2 install the modem for 2.6 kernel; it is not enough with the driver, u need the kernel sources and a gcc compiler, but (the rpm denies to istall´em), it installs automatically with YAST, anyway I tough 2 install it the right way but it just don´t work, but I had a little advance at the buy of Suse pro and let YAST Install the driver itself, and YES it seems 2 use the slmodemd and in fact the device is /dev/ttySL0 -or-
/dev/slmr0 but I don´t know what 2 do now; Idid this:
-------------------------------------------------------------------------------------------------------------
1) wvdial can´t find the devices avobe

2) kppp tests the SL= and seems 2 work the ATI, but at the time 2 connect, justrare bin simbols apear in the log

3)when I try with Kinternet, it sayssomething like this:
>>
Suse Meta pppd (smpppd-ifcfg) version 1.16 on linux
statuss is disconnected
trying t connect 2 smpppd
connect 2 smpppd
status is disconected
status is connecting
status is dissconected
pppd (0) died pppd options error (exit code 2)

4)
linux@user# slmodemd
unable to create device /dev/slmr0
linux@user#

I don´t know what to do (who will save us?)

yours

tiox · 11-23-2004, 06:59 PM

i have the same problem,
k internet doesnt seem to detect the modem at all, in yast themodem appears to be configured,however nothing happens

ruan567 · 01-03-2005, 08:52 AM

I am also having the exact same problem with the new ltmodem driver running on Suse 9.1 personal [no other modifications made after installation from ISO image]

Could this be a bug in the ltmodem rpm?

Ruan

suranga · 01-15-2005, 01:33 AM

Hi adam_the_noob,
I too have the same problem when I have the Motorola PCI modem plugged in. SUSE Hardware database shows only 3 chip-sets to support SUSE.
1 SiS7013 56k Modem
2 SmartPCI562
3 VIA AC97 Modem Codec (VT82C686/686A/686B)
I had Aztech modem with SmartPCI562 Chip. When I replaced the Motorola with Aztech, I don't have this problem anymore, This is just my experience, I am totally a newbie to Linux.
But this suggest that it is a problem with driver. Why not try scanModem utility from http://linmodems.technion.ac.il

Carrie,
Now I got the same problem you have. He-he, I get "options error (exit code 2)" Hmmm, ....

K. Carl · 01-15-2005, 10:17 AM

I had no luck whatever in cofiguring a PCI winmodem, however others have had success. My solution was to obtain an old exernal modem connected via a serial cable. That was operational within 30 minutes of making my hardware connections.

Disclaimer: I'm also quite inexperienced, but this worked for me.

Regards,
K. Carl

suranga · 01-16-2005, 12:52 AM

Hi,
I could get my Aztech SmartPCI562 to work perfect.
Many thanks to jk73 for directing us to search for updates manually at Suse Downloads.
You all should try it too. http://www.novell.com/linux/download/updates/index.html
I only had to use the patch "29 Oct 2004 smartlink-softmodem" in Suse 9.2.
So, this will solve the problem of some of you but, not all. If you have one with Lucent chip there is an update posted in December. Hope that'll do ...
Oh, don't forget to reboot before you try to connect.

DoDo1523 · 02-10-2005, 02:02 PM

hi im DoDo1523 im a new user in linux and i have a problem
when i try to connect to the internet the modem cuts off and the log says :
pppd[0]died : pppd options error (exit code 2)

so plz if anyone one can propose somthing to fix this problem i will be very thankfull to him
PLz help

My e-mail is : ndodo15@hotmail.com

suranga · 02-10-2005, 09:50 PM

DoDo, The posts above seems to have number of suggestions. Follow them. Go to the suse web and find if your modem chip-set is supported. If yes, look for the patch rpm in downloads. This might work. Use the scanmodem utility to find your modem chip-set, if you don't know it yet.
Regards
Suranga