I have my modem configured under Yast and everything looks to be fine, but
now when I try to connect to the internet it doesn't do anything.
I tried reading the connection log to see what is going wrong and it says:
SuSE meta pppd (smpppd.ifcfg) version 1.16 on linux
Status is:disconnected
trying to connect to smpppd.ifcfg
Connect to smpppd.ifcfg
Status is:disconnected
Status is: connecting
Status is:disconnected
pppd(0) died: pppd options error(exit code 2)


By the way even my modem doesn't appears when trying to detect it by Yast,
Yast tells me to configure it anyways which I did (of course!).
What can I do now????

Are you looking at Yast-->Network Devices-->Modem or Yast-->Hardware-->Modem tab. If it isn't in the second, it wasn't detected, and therefore it probably isn't going to work. What kind of modem? BTW, the pppd error you are getting is ...

2 An error was detected in processing the options
given, such as two mutually exclusive options being
used.

so, if the modem is detected, you have a configuration problem.

RO

I'm not sure if this is the answer your looking for, but I had problems dialing out on Suse 9.1 too. I'm not sure what your using to dial out with, but if you look closely at your /etc/wvdial.conf file you'll see that it's set to stupid mode=1.

Turning the stupid mode feature off seemed to clear the problem up.

Also if your using a serial modem simple yast configuration should do the trick. Just point it in the direction of the connection.

I tried to edit the wvdial.conf but I can save it but I've got the message that I can't save the file,I'm not authorized to because it's a root file.
I even "su+password" it with no results.
It looks like if I can't solve this problem and be able to acces the internet I'll be quitting SuSE soon!!!

You will have no success until Suse detects your modem. See my post above, and let us know the modem type.

RO

I have exactly the same problem (pppd died, options error - exit code 2) with SuSE 8.2 (kernel 2.4.20), using an Intel 536ep. It detects and configures, but won't respond. Stupid mode is 0, btw. Its driver won't install because the system won't accept the "make clean" command, which is shown in the modem's manual for installation. All this happens even though I'm logged in on the console as "root," and should be authorized. Arrgh!

The above poster is correct, to configure your modem:

1. Go to yast (should be under the system tab, under the kde "start button"

2. Click on the "network devices" tab

3. Look for a configured modem, if none is configured click add

4. Go through configuration


If this is an internal modem, you need to check for Linux compatibility (may be a winmodem)

1. Go to linmodems.org

2. Download Scanmodem run it

3. Read the Scanmodem output and directions carefully


:If a modem is detected and configured try below. This is the problem I ran across in Suse 9.1 Professional (2.6 kernel), stupid mode was turned on by default.

Ok you have to sign in as root

1. Open a terminal

2. Type "su -l root"

3. Type your password when it asks for password

4. Type vi /etc/wvdial.conf

5. See if stupid mode is on if it is (indicated by a 1), turn it off.

Max it sounds like you have a driver issue, which wvdial has almost nothing to do with. Is make clean the only command you tried.

Eureka! Since I last posted, I've solved my problem. First, I went back to my OS installation (SuSE 2.4.20) and added the development package (which evidently includes the compiler) to the default installation. Then, using an Intel536ep PCI internal modem with a Linux-specific driver (intel536-4_68) from Intel by way of linmodems.org , I managed not only to get the modem detected and configured, but was actually able to install the driver, using the directions in the Readme file. This time, it not only executed "make clean" and "make install," it also told me what to do when the kernel didn't exactly match.

Kinternet (wvdial) now puts me right on line. So here I am, communicating with you on my new system, after a solid week of frustration. Tra la la!

@Sabicas

No need to edit wvdial.conf. Can be done from YAST in the configuration menu you referred to above (step 4).

@hlinux

In my setup stupid mode has to be set on so you'd better toggle that setting.

I just love to edit system files for some reason

I had the above problem with Suse 9.2. I could not understand why, because the package was loaded (but obviously not installed). I downloaded the driver from the Intel site & followed the instructions on the readme. I got some error messages, but it obviously filled in the gaps as the modem now works. (Ive yet to reboot & see if it loads next time!)

I too have the same problem as hilinux. I tried both stupid mode on and off. It didn work. I have Smartlink PCI.

SuSE Meta pppd (smpppd-ifcfg), Version 1.50 on linux.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
Status is: disconnected
pppd[0] died: pppd options error (exit code 2)

Class 0703: 163c:3052 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem (rev 04) (prog-if 00 [Generic])
SubSystem 122d:3052 Aztech System Ltd: Unknown device 3052
Flags: bus master, stepping, medium devsel, latency 32, IRQ 10
Memory at ed000000 (32-bit, non-prefetchable)
I/O ports at d800 [size=256]

==============================
grep ppp /etc/modprobe.conf
-------------------------------------
# ppp over ethernet
# the kernel 2.2 uses pppox
# the kernel 2.4 uses pppoe
alias char-major-108 ppp_generic
alias char-major-144 pppoe
alias net-pf-24 pppoe
# the kernel 2.2 uses ppp.o as ppp driver,
# the kernel 2.4 uses ppp_generic.o
alias ppp0 ppp_generic
alias ppp1 ppp_generic
alias tty-ldisc-3 ppp_async
alias ppp-compress-18 ppp_mppe
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
-------------------------------------

Hi, I got my modem working. Only had to use the update patch from Suse downloads for Smartlink PCI modem on my Suse 9.2 version. If you have the same configurations (see my first post above) this should work.
Don't forget to reboot before dial.
Hope this helps. Cheers. Suranga

It certainly looks like making sure the driver is actually loaded is vital. I've just bought another of these Intel PCI Modems for an old PII. Hove not installed yet, but the had them piled high in Maplins @ £9.99 so good value!

Yes, I agree with PeterKlancic. The patch was reaquired for my modem becasue "The slamr module does not get loaded automatically, so slmodemd
fails. This update gets the slamr module loaded on startup" - as it was given in Suse Updates. I am new to command line, but hope you know how to load the modem mannualy after reboot.