Hi everyone,

I have a Fujitsu P5020D with SUSE 10 installed and mostly everything is working great. I like how madwifi and wpa are supported right out of the box for this newbie.

The only problem that's taking away from general usability is when I resume from suspend to disk. My problem is the modem times out when I try to reconnect. I have to reboot from scratch to reset the modem.

This is what I see in the KInternet log:

SuSE Meta pppd (smpppd-ifcfg), Version 1.59 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]: ATM1
pppd[0]: OK
pppd[0]: --> Modem initialized.
pppd[0]: --> Sending: ATDT14638
pppd[0]: --> Waiting for carrier.
pppd[0]: ATDT14638
pppd[0]: --> Timed out while dialing. Trying again.
pppd[0]: --> Sending: ATDT14638
pppd[0]: --> Waiting for carrier.
pppd[0]: --> Timed out while dialing. Trying again.
pppd[0]: --> Sending: ATDT14638
pppd[0]: --> Waiting for carrier.....etc


....or.....

SuSE Meta pppd (smpppd-ifcfg), Version 1.59 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)

Any ideas?
Nathan

Don't you want ATZ in your initialisation script? You know, to reset the modem?

I'll give it a try! I've never had to do this kinda thing in windows before.

Thanks,
Nathan

I added ATZ to the initialization script in yast and after resuming from S2D the log displayed my first example.

I've googled for this problem for about a week now. I don't know what is different coming out of suspend vs.rebooting the machine.

I'll read up on modem init commands and see if I can figure something out.

Nathan

I found the solution.

I edited the /etc/sysconfig/powersave/sleep and unloaded slmodemd before S2D, and then to restart that service.I didn't know there was the slmodemd daemon as well as the slamr driver.

Turns out initialization commands for the modem was unnecesary.

Just in case someone else needs this info....

Nathan

I'm sorry - which action fixed the issue?

You edited: /etc/sysconfig/powersave/sleep to read what? What was it before?
You unloaded slmodemd then S2D ... then "to restart that service"... ? what did you do? Anything special or did you just restart the ppp0 service normally (which would probably reload the slmodemd driver with the snd-AC97 driver)?

You didn't know there was the slamr driver as well? What is the significance of this? Had you inadvertently loaded both drivers at once? Were you using slamr when you should have been using slmodemd - or was it the other way around?

If the "It's fixed" post is to be of any use to anyone else, they need this information... it also helps to include how you discovered to do these things: did you guess? What was your reasoning? (This last is, in fact, the most useful. It helps others, with not quite the same trouble as you, research their own problem.)

Apart from that ... well done.

The following entries were added to "/etc/sysconfig/powersave/sleep":

UNLOAD_MODULES_BEFORE_SUSPEND2DISK="slmodemd"

SUSPEND2DISK_RESTART_SERVICES="855resolution slmodemd"

Prior to this, SUSPEND2DISK_RESTART_SERVICES="855resolution" was the only modification I had made so that my laptop display would use the 1280x768 mode that is not reported by the video BIOS.

"You unloaded slmodemd then S2D ... then "to restart that service"... ? what did you do? Anything special or did you just restart the ppp0 service normally (which would probably reload the slmodemd driver with the snd-AC97 driver)?"

The answers to these questions is simply that I didn't do anything special but add slmodemd to the sleep config file as annotated above. I don't really know how to restart the ppp0 service manually, or any service for that matter.

You didn't know there was the slamr driver as well? What is the significance of this? Had you inadvertently loaded both drivers at once? Were you using slamr when you should have been using slmodemd - or was it the other way around?

I knew of the slamr driver (module) and after much reading tried using the modprobe command to see what it does. What I didn't realize was there was the slmodemd daemon (or service for ex-windows people) that the slamr driver communicates with. When I resumed from S2D, I'm guessing that the slmodemd got hung up and prevented the modem from functioning.


My reasoning when I was working through this was the simple fact that the modem worked fine after a reboot/cold boot. It wasn't necessary to have any initialization strings. Only after a S2D would it do what I posted in my original post.

I then went to linmodems.org and download the scanmodem utility and read all the documentation that was created from running the tool. That was when I learned about the existence of slmodemd and basically what it does. And after thinking about that for a minute, thought that maybe slmodemd needed to be unloaded before S2D and restarted after resume.

To be honest, entering slmodemd in both of the entries I made may not be entirely necessary. The next thing I should do is remove it from UNLOAD_MODULES_BEFORE_SUSPEND2DISK and see what happens, and then put it back and remove it from SUSPEND2DISK_RESTART_SERVICES.

Bottom line was the fact that it worked when I didn't suspend to disk, and it didn't work after I did. I hope this is clear.

Nathan