HowTo configure dial-up modem on 12.3?

English Hardware
#1

Hello, list, moderators!

I’m expecting to loose my DSL, so in the short time I still have it, I want to get a dial-up modem configured.

My system is 17-3770 on Asus P8Z77-M LK. I added a serial port today and enabled for com1 in the UEFI BIOS.

The serial port modem is a Best Data V.92. HW information seems to recognize it on /dev/ttyS0, but doesn’t mention Best Data. This is an excerpt from HWinfo.

>> braille.5.1: alva read done
>> braille.1.1: fhp_old
>> braille.2.1: fhp open
>> braille.3.1: fhp init ok
>> braille.4.1: fhp write ok
>> braille.5.1: fhp read done
fhp@/dev/ttyS0[1]: 00  "."
no fhp display: 0x00
>> braille.1.1: fhp_el
>> braille.2.1: fhp open
>> braille.3.1: fhp init ok
>> braille.4.1: fhp write ok
>> braille.5.1: fhp read done
fhp@/dev/ttyS0[1]: 00  "."
no fhp display: 0x00
>> braille.1.1: ht
>> braille.2.1: ht open
>> braille.3.1: ht init ok
>> braille.4.1: ht write ok
>> braille.5.1: ht read done
ht@/dev/ttyS0[1]: 00  "."
no ht display: 0x00
>> braille.1.1: baum
>> braille.2.1: baum open
>> braille.3.1: baum write ok
>> braille.4.1: baum read done
baum@/dev/ttyS0[1]: 00  "."
>> braille.1.1: fhp new
>> braille.2.1: fhp2 open
>> braille.3.1: fhp2 write ok
>> braille.4.1: fhp2 read done
fhp2@/dev/ttyS0[1]: 00  "."
******  stopped child process 1906 (8s)  ******
>> modem.1: serial
******  started child process 1907 (15s/120s)  ******
>> modem.2: init
>> modem.3.1: at test
>> modem.9.1: write at cmd
>> modem.9.1: read at resp
>> modem.9.1: read ok
/dev/ttyS0@115200: AT 
    ""
>> modem.3.2: at test
>> modem.9.2: write at cmd
>> modem.9.2: read at resp
>> modem.9.2: read ok
/dev/ttyS0@38400: AT 
    ""

To me this looks like the modem is detected at the com1 BIOS serial port setting.

I installed qinternet which pulled in wvdial and smpppd. With earlier versions, say 12.1, yast>network devices>network settings, I could choose ifup and add a modem.

With 12.3 add brings up a dropdown box that doesn’t have modem as a selection, even after changing the yast>network devices>network settings global tab to ifup and unchecking ipv6.

I was able to go to yast>network devices>modem and and a modem, but the best data had to be added manually. With the yast>network devices>modem setup qinternet fails as follows:

SuSE Meta pppd (smpppd-ifcfg), Version 1.60.56 on linux-uso4.(none)
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.60
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATZ
pppd[0]: --> Sending: ATQ0
pppd[0]: --> Re-Sending: ATZ
pppd[0]: --> Modem not responding.
pppd[0]: Script /usr/bin/wvdial --chat --no-syslog --config /var/run/smpppd/chat-modem0.conf smpppd finished (pid 17125), status = 0x1
pppd[0]: Connect script failed
Status is: disconnected
pppd[0] died: Connect script failed (exit code 8)

As soon as I shut off the network manager in deference to ifup, my DSL connection breaks. Back in 12.1 I could have both. Have I crossed the Rubicon moving up to 12.3? Heboland.

#2

I can only provide general advice, but as a start…

Just a guess - are you a member of the ‘dialout’ group? (This will only be applicable if dialling out as a user.)

I was able to go to yast>network devices>modem and and a modem, but the best data had to be added manually.

That is normal.

In an effort to assist, I ‘pretended’ to configure a modem, connected to /dev/ttyUSB3, and then dialout. I got the exact log output that you did, so it suggests no communication with the modem. (In my case none existed anyway).

Since you’re trying to connect to a serial modem, you need to set the baud rate just right first. Did you do that via YaST when configuring by hand? Maybe try communicating via minicom first. (Don’t forget to subscribe yourself to the dialout group first).

minicom -s

then ‘Serial Port Setup’

These old guides may be helpful with testing…
Modem-HOWTO: Trying Out Your Modem (Dialing Out)
Modem-HOWTO: Troubleshooting

#3

As soon as I shut off the network manager in deference to ifup, my DSL connection breaks. Back in 12.1 I could have both. Have I crossed the Rubicon moving up to 12.3? Heboland.

During the configuration with ‘qinternet’, which uses YaST, I did not have to relinquish the network manager. The dialling app can be launched separately, leaving my existing NM-managed wired, wireless, and broadband connections alone. I’m using openSUSE 12.2, but don’t expect 12.3 to be any different here.

#4

Thank you deano_ferrari!

Since I posted, I did a HwInfo with and without the serial modem cable plugged in. The diff file | grep modem looks like this:

< >> modem.9.1: write at cmd
< >> modem.9.1: read at resp
< >> modem.9.1: read ok
< >> modem.9.2: write at cmd
< >> modem.9.2: read at resp
< >> modem.9.2: read ok
< >> modem.9.3: write at cmd
< >> modem.9.3: read at resp
< >> modem.9.3: read ok
< >> modem.9.4: write at cmd
< >> modem.9.4: read at resp
< >> modem.9.4: read ok

The extra lines are from the file with the cable plugged in. That tells me HwInfo does see the modem.

If I poke around with wvdial, it sees no difference with cable in or out.

Apparently in 12.3 the yast>network devices>modem takes the place of earlier version’s yast>network devices>network setting>ifup.

I didn’t buy the serial port connector from Asus, but rather used the connector, pigtail and chassis mount from an older box. The connector plug fit well into the Asus keyed jack. I’m wondering if they rotated the pins in opposite directions to defeat someone from doing what I did? I’ll have to check that out next!

minicom is a great suggestion. I’m installing it now.

One other thought I’ve had, is going back to kppp. That had a nice low-level modem access application that would query the modem. Could that still be made to work, or is that too old?

I also tried using virtualbox running an xp-32 vm. I added /dev/ttyS0, but the modem didn’t respond to that either.

It helps to learn of the behavior of your system. I’ll keep fooling with this, especially trying to validate the serial connection.

Do you think I could gain anything my changing the serial port in the BIOS from Com1 to 2,3, or 4? Heboland.

#5

If I poke around with wvdial, it sees no difference with cable in or out.

Did you specifically mean the ‘wvdialconf’ utility? That should detect any working serial modem, assuming the cabling is correct.

I didn’t buy the serial port connector from Asus, but rather used the connector, pigtail and chassis mount from an older box. The connector plug fit well into the Asus keyed jack. I’m wondering if they rotated the pins in opposite directions to defeat someone from doing what I did? I’ll have to check that out next!

Yes, that’s the first thing to check. Ideally, a serial tester could be useful here.

minicom is a great suggestion. I’m installing it now.

Good. Let us know how this goes. You should be able to get a useful response, provided baud rate etc is configured correctly. Even without a modem, a serial loopback plug (pins 2 and 3 connected) can be used to establish basic validation of a working serial port.

[/QUOTE]One other thought I’ve had, is going back to kppp. That had a nice low-level modem access application that would query the modem. Could that still be made to work, or is that too old?

Well, I see that it is still available. I guess it wouldn’t hurt to try…

Do you think I could gain anything my changing the serial port in the BIOS from Com1 to 2,3, or 4? Heboland.

I don’t think so.

#6

On 2013-04-02 08:36, heboland wrote:

> I didn’t buy the serial port connector from Asus, but rather used the
> connector, pigtail and chassis mount from an older box. The connector
> plug fit well into the Asus keyed jack. I’m wondering if they rotated
> the pins in opposite directions to defeat someone from doing what I did?
> I’ll have to check that out next!

No. See the exchange:


>> modem.2: init
>> modem.3.1: at test
>> modem.9.1: write at cmd
>> modem.9.1: read at resp
>> modem.9.1: read ok
/dev/ttyS0@115200: AT

the modem is responding.

I do have a modem connected, but not for internet: for faxing. When I
used it for internet years ago I did not use any of the graphical
interfaces: I called wvdial directly in a terminal.

> Do you think I could gain anything my changing the serial port in the
> BIOS from Com1 to 2,3, or 4? Heboland.

No.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#7

Thanks robin_listas, deano_ferrari!

Your comments, suggestions, and advice are most appreciated!

Robin, let me start with your response. I agree with you that my serial modem is responding. Since my last post I have moved that Best Data serial modem to my Pentium3 system currently running 12.1-32bit. There it responds similarly, but there’s more.

On that box with a mobo riser serial port, 12.1 configures the modem on /dev/ttyS1. HwInfo recognizes it as a modem and does much more configuration. Leaving yast>network devices>network settings set to Network Manager, then configuring the modem with , the modem is recognized. It comes up in that gui as being /dev/ttyS1.

Continuing on with smpppd and qinternet, the modem dials and acts expectedly. 12.1 HwInfo does have the entry /dev/ttyS0 - not a modem.

For that reason I moved the 12.3 machine BIOS configuration to put the serial port on com2 (/dev/ttyS1) like the 12.1. Now the 12.3 has the entry /dev/ttyS1 - not a modem. Also HwInfo doesn’t show a modem.

As much as I want to believe you Robin, I think there’s still something wrong with the 12.3 Asus serial port. I don’t have access to a serial port tester, so I may need some suggestions to debug it. Your loopback suggestion may be a start. I do have an oscilloscope if I could get a test running pm on each machine.

Your mention of using a modem for fax would take me off topic, but for a quick comment I have a similar application for this modem if I’m able to restore my DSL. In the past I have used hylafax and efax, but my level of usage is between them. It’s my hope to use XP fax in my virtualBox.

I only installed wvdial, but I do have wvdialconf. What I was really after was something low level to be able to interrogate the modem with AT commands like in the old days. minicom hasn’t worked for that yet either, but I still think there’s still a serial port problem.

deano, I am a member of dialout, modem, and a few other groups I thought might be significant. I see now that the 12.x OSs will accept the network manager running simultaneously with qinternet. The difference is that the modem has to be set up with yast>network devices>modem.

On the baud rate the 12.1 where the modem is detected is around 115000. With the manual 12.3 add, the default baud rate is 57000. Either of those should work in my opinion.

I think I’ve answered your questions now, so I would like to describe my plan of attack. I think I have room to load the 12.3 on my P3 system. That will require overwriting the 12.1-32. I think the 12.3 is both a 32 and 64 bit OS combined on the same DVD. I would expect you guys would agree with me that the 32 Vs 64 should not affect the modem recognition.

If this all works, I’ll have an apples to apples comparison of 12.3-64 with a homemade serial port with a 12.3-32 with a mobo riser serial port. I will need to get both boxes to the same update level before I try this, to be fair.

Assuming the riser port works and homemade port doesn’t I’m thinking it’s more likely to find a Windows serial port test, but I may be wrong. Can I use my XP vm on 12.3-64 to run a serial port test if that’s all that exists? Heboand.

#8

On 2013-04-04 05:06, heboland wrote:
>
> Thanks robin_listas, deano_ferrari!
>
> Your comments, suggestions, and advice are most appreciated!
>
> Robin, let me start with your response. I agree with you that my serial
> modem is responding. Since my last post I have moved that Best Data
> serial modem to my Pentium3 system currently running 12.1-32bit. There
> it responds similarly, but there’s more.
>
> On that box with a mobo riser serial port, 12.1 configures the modem on
> /dev/ttyS1. HwInfo recognizes it as a modem and does much more
> configuration. Leaving yast>network devices>network settings set to
> Network Manager, then configuring the modem with , the modem is
> recognized. It comes up in that gui as being /dev/ttyS1.

I see, it behaves differently there.

You are right, I powered up my modem and tried - I’m using 12.1:


Telcontar:~ # hwinfo --modem
55: Serial 00.0: 10200 Modem
[Created at modem.447]
Unique ID: Fyby.ZhdTkiP6ZR9
Parent ID: S_Uw.3fyvFV+mbWD
Hardware Class: modem
Model: "U.S. Robotics 56K FAX EXT"
Vendor: USR "U.S. Robotics, Inc."
Device: eisa 0x006f "U.S. Robotics 56K FAX EXT"
Compatible to: PNP 0xc107
Device File: /dev/ttyS0
Speed: 115.2 kbps
Init1: ATZ
Init2: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #39 (Serial controller)
Telcontar:~ #

So that command would be enough to quickly identify a modem that is
responding correctly.

I intend to install 12.3 on a spare partition to test it, but that is
not something I’m going to do soon. I do have the xfce 12.3 rescue
system, which has hwinfo. I might try it sooner.

That will say if serial modem is supported in 12.3, basically.

I do have a symlink “modem” that points to “ttyS0”. I haven’t
noticed/remember if hwinfo polls all the ports or goes directly to the
one named “modem”. I think it does a poll.

> As much as I want to believe you Robin, I think there’s still something
> wrong with the 12.3 Asus serial port. I don’t have access to a serial
> port tester, so I may need some suggestions to debug it. Your loopback
> suggestion may be a start. I do have an oscilloscope if I could get a
> test running pm on each machine.

It is not that simple… of my head I can’t think of a way to do it… :-?

We would need access to the hardware level, to continuously output
patterns. Then you can identify the TX line and ground. But usually user
software stops transmitting if there is no ACK back, either software or
hardware…

> Your mention of using a modem for fax would take me off topic, but for
> a quick comment I have a similar application for this modem if I’m able
> to restore my DSL. In the past I have used hylafax and efax, but my
> level of usage is between them. It’s my hope to use XP fax in my
> virtualBox.

I still have hylafax configured, I believe it works. I have not used it
recently, my need to send a fax is a rare event. A year or two ago I
used it quite a bit.

I don’t know if a guest machine can handle the host serial port.

> I only installed wvdial, but I do have wvdialconf. What I was really
> after was something low level to be able to interrogate the modem with
> AT commands like in the old days. minicom hasn’t worked for that yet
> either, but I still think there’s still a serial port problem.

minicom does it. Provided the serial port responds… you have to do it
as root. Try different serial port configs.

> I think I’ve answered your questions now, so I would like to describe
> my plan of attack. I think I have room to load the 12.3 on my P3 system.
> That will require overwriting the 12.1-32. I think the 12.3 is both a 32
> and 64 bit OS combined on the same DVD. I would expect you guys would
> agree with me that the 32 Vs 64 should not affect the modem recognition.

You can download the 12.3 xfce rescue CD, either using a CD or an USB
stick. It has hwinfo and so you do not need to install it. Or the
gnome/kde lives should do… dunno if they have hwinfo.

If both machines have serial port, you can connect one to the other,
both running minicom. At least you should get garbage on the others
screen when typing. It does not matter what distro they run.

null modem cable was it named? One forgets these things, its long since
I do it…

I’m off to bed.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#9

minicom does it. Provided the serial port responds… you have to do it
as root. Try different serial port configs.

As long as you have the required R/W access (ie dialout group), then minicom will work as regular user. I frequently connect to various network equipment in my job using minicom to establish serial console sessions.

#10

I only installed wvdial, but I do have wvdialconf. What I was really after was something low level to be able to interrogate the modem with AT commands like in the old days. minicom hasn’t worked for that yet either, but I still think there’s still a serial port problem.

  1. wvdialconf is part of the wvdial package. If you had a working modem/serial port, wvdialconf will detect it as root, and as regular user if a member of the ‘dialout’ group.
  2. Yes, without being in front of your hardware, it does seem to be the case. (If I was in front of it, I almost certainly could determine the problem within a few minutes).
#11

On 2013-04-04 08:16, deano ferrari wrote:
>
>> minicom does it. Provided the serial port responds… you have to do it
>> as root. Try different serial port configs.
>>
> As long as you have the required R/W access (ie dialout group), then
> minicom will work as regular user. I frequently connect to various
> network equipment in my job using minicom to establish serial console
> sessions.

If I remember correctly, it does not allow you to change COM settings.

I am a member of dialout group. Lte’s try…

Interesting… it is allowing me to do changes, like changing from ttyS0
to ttyS1 - and the weird thing is that “ati3” is responding on both
ports, which is impossible. It does not apply the change.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#12

Thank you again guys! You both have been busy while I’ve been installing 12.3 on my P3.

FWIW, this install has been pretty brittle. The details of the install are off topic, but I’ll ask a question about them at the end of this post.

Let me describe the response of the 12.3-32 (P3). It configured the modem on /dev/ttyS0, recognizing it as a modem in HwInfo. I’m running the network manager but only able to connect to wired connections on both machines (another off topic problem)!

To configure the modem in the presence of the network manager, I used yast>network devices>modem. The gui that brings up, already recognized the modem on S0. It configures easily as modem0.

Next running qinternet simultaneous with NM, I took Settings>Configure with Yast2. That brings up the same gui as yast>network devices>modem. I choose the modem0 line and OKed it.

Invoking qinternet causes it to dial. I doesn’t connect as I don’t have a dial-up account yet.

Unless there’s something different between 12.3-32 and 12.3-64, I have a serial port problem with the 64-bit system.

So with this P3 I should be able to issue AT commands with minicom. I’m in dialout, so I should be able to do this as me. My last experience with direct modem commands was using Windows Hyperterm.

What I remember of that was a com port selection, then a connect button on the gui, then typing into a black terminal screen. Typically the modem would echo back the command. Sometimes it was necessary to change the duplex setting.

I don’t see any similar commands for minicom in the man page or in the ascii gui minicom displays. Are there more exhaustive descriptions for doing direct modem interrogation?

Robin, I don’t understand this! I this an excerpt from hwinfo --modem?

Telcontar:~ # hwinfo --modem 55: Serial 00.0: 10200 Modem [Created at modem.447] Unique ID: Fyby.ZhdTkiP6ZR9 Parent ID: S_Uw.3fyvFV+mbWD Hardware Class: modem

deano, I think if I can get minicom working for me at the AT level, I may be able
to find differences, but I don’t expect to be able to determine how things are messed up in the port on the 64-bit box.

I think my next step is to examine the 64-bit serial port connector and pigtail.

Do you guys have any other suggestions?

Let me drop the off topic install problem here FWIW. My Pentium 3 will only boot with the kernel parameter x11failsafe in the boot string.

Without that parameter the boot fails every time on this line:
[OK] Started /etc/init.d/boot.local Compatibility.

Is this a KMS video problem? With the failsafe parameter, I have to live with a low
resolution display. It would be great to get that fixed! Heboland.

#13

I think my next step is to examine the 64-bit serial port connector and pigtail.

Definitely. You need to know that the hardware and connections are okay before proceeding further.

#14

Let me drop the off topic install problem here FWIW. My Pentium 3 will only boot with the kernel parameter x11failsafe in the boot string.

Without that parameter the boot fails every time on this line:
[OK] Started /etc/init.d/boot.local Compatibility.

Is this a KMS video problem? With the failsafe parameter, I have to live with a low resolution display. It would be great to get that fixed! Heboland.

You really are best advised to start a separate thread in the appropriate forum for that. That way you’ll get the dedicated attention that it deserves.

#15

Thanks deano_ferrari!

I have my Asus modem port working! The problem was the different pinouts of the donor mobo and the Asus. Other serial ports I have are wired the same as the donor - linearly. The Asus is pinned odd then even. To make this work requires cross-wiring 8 of the 9 wires. Only pin 1 is correct!

One lingering problem is how to start smpppd “automatically”. The yast>systme>runtime services is different with 12.3. With previous versions, using “expert” allowed starting daemons at a choice of run levels. 12.3 only allows the choice of boot for smpppd. Saving that setting doesn’t leave a running smpppd at level 5. Any suggestions?

On the subject of running minicom as a user when the user is a member of the group dialout, I still had a problem. Originally minicom wanted to write a logfile into /var which it won’t allow as a user. I just tried it again as myself for this reply and it worked without complaining about the log file! I don’t know what happened!

My minicom has the environment variable MINICOM set to -C on. minicom -s brings up the ascii configuration menu. This is where the com port can be changed. Next I did Save setup as filename. Now minicom filename brings up a black terminal window that will accept modem AT commands. ^A z X exits minicom.

Robin, I found your wonderful command /sbin/hwinfo. That’s so much easier using the command line argument --modem than fishing the modem stuff out of the whole yast>hardware>hardware information file!

Finally, 12.3 does allows qinternet to run simultaneous with the network manager. Once the NM is selected, it’s necessary to configure the modem with yast>network devices>modem or qinternet>settings>Configure with yast. If qinternet comes up with an error, smpppd isn’t running and must be manually started.

Except for the smpppd issue, this thread is solved. The serial port was incorrectly connected to the dsub-9 connector. Heboland.

#16

That’s what was suspected, so good news. :slight_smile:

Finally, 12.3 does allows qinternet to run simultaneous with the network manager.

Yep, as I suggested was the case.

#17

One lingering problem is how to start smpppd “automatically”. The yast>systme>runtime services is different with 12.3. With previous versions, using “expert” allowed starting daemons at a choice of run levels. 12.3 only allows the choice of boot for smpppd. Saving that setting doesn’t leave a running smpppd at level 5. Any suggestions?

Now that systemd is in use, you need to do

systemctl enable smpppd.service

systemctl start smpppd.service

openSUSE 12.3: Chapter 8. The systemd daemon

#18

On 2013-04-08 02:46, heboland wrote:
>
> Thanks deano_ferrari!
>
> I have my Asus modem port working! The problem was the different
> pinouts of the donor mobo and the Asus. Other serial ports I have are
> wired the same as the donor - linearly. The Asus is pinned odd then
> even. To make this work requires cross-wiring 8 of the 9 wires. Only pin
> 1 is correct!

I was afraid this could be the case. Glad you could find the correct pins!

> One lingering problem is how to start smpppd “automatically”. The
> yast>systme>runtime services is different with 12.3. With previous
> versions, using “expert” allowed starting daemons at a choice of run
> levels. 12.3 only allows the choice of boot for smpppd. Saving that
> setting doesn’t leave a running smpppd at level 5. Any suggestions?

The yast module for controlling the starting of services in 12.3 is
broken, you have to do it manually. You might try “chkconfig”:


chkconfig smpppd
chkconfig smpppd on

> On the subject of running minicom as a user when the user is a member
> of the group dialout, I still had a problem. Originally minicom wanted
> to write a logfile into /var which it won’t allow as a user. I just
> tried it again as myself for this reply and it worked without
> complaining about the log file! I don’t know what happened!

Dunno.

> Robin, I found your wonderful command /sbin/hwinfo. That’s so much
> easier using the command line argument --modem than fishing the modem
> stuff out of the whole yast>hardware>hardware information file!

Heh, I didn’t even notice you were using yast for this. I thought you
were using hwinfo without options and thus getting the entire looooong
output :slight_smile:

> Finally, 12.3 does allows qinternet to run simultaneous with the
> network manager. Once the NM is selected, it’s necessary to configure
> the modem with yast>network devices>modem or
> qinternet>settings>Configure with yast. If qinternet comes up with an
> error, smpppd isn’t running and must be manually started.

Aha.

> Except for the smpppd issue, this thread is solved. The serial port was
> incorrectly connected to the dsub-9 connector. Heboland.

Wonderful!

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#19

Thanks guys for sticking with me on this one!

With the need to do manual start of daemons, it seems as if a script somewhere might be able to automate that fufnction in lieu of 12.3 services.

When I used to build linux drivers for win modems, there was a place to add options to a kernel config file to invoke some root level operations like starting daemons. I recall something like starting an instance of someting like slam!

Possibly something of interest to you Robin is that my XP vm now has the serial modem configured. I think I only need to make arrangements with a fax receiver person to test my XP fax. I still don’t have an address book for the XP fax, but that’s a minor point.

I’m encouraged about my chances now to retain DSL. A switch over may happen this week. That will make me go dark for while, but hopefully a short while. Heboland.

#20

With the need to do manual start of daemons, it seems as if a script somewhere might be able to automate that fufnction in lieu of 12.3 services.

No, the systemctl (or chkconfig) commands given previously should automate the starting of smpppd for subsequent boots. Are you still having issues?