How to disable internal dialup modem? [SOLVED]

Message
Author
User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#21 Post by Sky Aisling »

Test to Determine if Machine is Healthy

I have done a further test with the machine in question:
Toshiba Satellite 1415-S115, 512 RAM.

I removed the lupu-520 save file from the HDD. (There is a backup on a flashdrive)
I removed the Puppy-520 Live CD.

I booted the machine with Puppy 4.3.1. Live CD.
The modem was detected.
I did a *probe*.
The modem Wintec-FileMate-56-k-ModemCX and Pupdial worked with no issues.

The environment is this:

Kernel 2.6.30.5 (i686)
SeaMonkey 1.1.18
Pupdial:
String 2 ATZ
String 3 ATQ0V1E1 S0=0&C1&D2+FCLASS=0
ttyACMO
auto connect

Dewbie

#22 Post by Dewbie »

I was just going to ask you to test the Toshiba Satellite 1415-S115 with 4.3.1 (k2.6.30.5).
Great, looks like nothing's fried. :)
That's strange, though...it worked OK before the surge with Lucid 5.2.0, and now it doesn't?

Anyway, if you're looking for something newer with kernel 2.6.30.5, try this or this.

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

#23 Post by Sky Aisling »

What are the drawbacks to using Puppy 4.3.1. with it's kernel?
I would update Seamonkey using Shinobar's .sfs solution.
http://www.murga-linux.com/puppy/viewtopic.php?t=78601

How come Puppy-520 kernel worked fine with Pupdial until ....?

Regarding this issue...
Does it matter that that he was receiving huge picture files from friends who don't understand that he is on dialup and what that means as far as transmission times?

Dewbie

#24 Post by Dewbie »

What are the drawbacks to using Puppy 4.3.1. with it's kernel?
4.x .pet packages have been discontinued in the main repository, http://distro.ibiblio.org.
However, shinobar and others still periodically release them.

Shinobar also maintains his own version of 4.3.1.
It's called 431JP.

The 5.x series (including kernel 2.6.30.5) versions still get new .pets.
How come Puppy-520 kernel worked fine with Pupdial until ....?
I forgot to ask:
Have you tried Lucid-520 modem setup with the puppy pfix=ram boot option, minus the save file?
Save files do get corrupted sometimes.
Does it matter that that he was receiving huge picture files from friends who don't understand that he is on dialup and what that means as far as transmission times?
That shouldn't matter in the context of this problem.
Do they know how to send him .zip files?
That should reduce the download times--maybe just a little bit, but with dial-up, everything helps.

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#25 Post by Sky Aisling »

Have you tried Lucid-520 modem setup with the puppy pfix=ram boot option, minus the save file?
At the time I was struggling with the *Inode* issue I did a pfix=RAM. The *inode* issue according to our local tech was probably caused by a power surge. He noted many power surge problems coming into his shop the week the machine went down. The wiring system is questionable where the machine is used. And, the machine had an inadequate surge protector. We've had lightening storms unusual for this area.

My memory is foggy as to what I did then as far as pfix=RAM with/without lupusave file. I'm pretty sure I did the pfix=RAM without the lupusave file being present.

I can do a pfix=RAM on the machine without the lupusave present, but...
if the lupusave file is corrupt then when I put it back after the pfix=RAM won't the bad lupusave (if it is bad) just be present again?

Also, can I somehow replace ttySL0 with ttyACMO in some control file somewhere?
I tried replacing it in etc/Wvdail.conf I *saved* etc/Wvdial.conf but that didn't appear to make any difference to Pupdial.

Dewbie

#26 Post by Dewbie »

I can do a pfix=RAM on the machine without the lupusave present, but...if the lupusave file is corrupt then when I put it back
If the lupusave file is corrupt, then you'll need to delete it and make a new one.

That's why pfix=ram is such a valuable boot option.
It's great for diagnosing problems.
Also, can I somehow replace ttySL0 with ttyACMO in some control file somewhere?
I tried replacing it in etc/Wvdail.conf I *saved* etc/Wvdial.conf but that didn't appear to make any difference to Pupdial.
Honestly, I don't know.
I never mess with that stuff.

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#27 Post by Sky Aisling »

If the lupusave file is corrupt, then you'll need to delete it and make a new one.

Oh groan!...

I've tried Wary before on several different machines but seems like it has issues.
I'll take a look at Lucid 525 Retro-2.6.30.5 again.

Not sure what to do...

Thank you Dewbie,
Thank you Karl Godt (I learned something from your post, Karl, helpful but didn't solve issue).

Dewbie

#28 Post by Dewbie »

Oh groan!...Not sure what to do...
If the testing is too much hassle, just stick with 4.3.1.
After all, you know it works. :)

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#29 Post by Sky Aisling »

Hi Dewbie,

That's exactly what I'm going to do.
I'll do a frugal install and add Shinobar's Seamonkey update .sfs.

So simple.

:D

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#30 Post by Karl Godt »

I tried replacing it in etc/Wvdail.conf I *saved* etc/Wvdial.conf but that didn't appear to make any difference to Pupdial.
I have reported this here : http://murga-linux.com/puppy/viewtopic.php?p=632972&search_id=505523010#632972
Pupdial owerwrites its /etc/wvdial.conf configuration file everytime, so
the suggestions written into it, to comment out lines

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#31 Post by Sky Aisling »

Dewbie writes:
If the testing is too much hassle, just stick with 4.3.1.
After all, you know it works. :D

Sky writes:
That's exactly what I'm going to do.
I'll do a frugal install and add Shinobar's Seamonkey update .sfs. :D
OK folks, I did set up 431 as a frugal install and upgraded SeaMonkey.

On the first try at Pupdial on the new setup, Pupdial connected with no issues.
But, then on the subsequence reboots and power ups, Pupdial failed with same error, modem not found on the tty port - "invalid argument".

It appears that WvDial.conf file works on the first time it is initialized by a system.
Then it appears that something gets over written and the original settings disappear.

If I load a Live CD with no save file then the Pupdial works.
If I create a save file then the next time I boot the OS and initiate Pupdial, Pupdial fails.

Unless, someone sees the answer to this, I have to stop working on the issue. I've done all I can to make it work.

Thank you everyone for your input.

Dewbie

#32 Post by Dewbie »

Sky Aisling wrote:
On the first try at Pupdial on the new setup, Pupdial connected with no issues.
But, then on the subsequence reboots and power ups, Pupdial failed with same error, modem not found on the tty port - "invalid argument".
When running from save file, can you get things working again by reprobing for modem in Menu / Network / Pupdial modem dialup?

I had to do this every time when booting from CD to save file with Wary 5.1.1-k2.6.30.5., using an external USRobotics serial modem.
(Note: Menu location is different in Wary, but that's beside the point.)

It was a real pain in the ass, but I just dealt with it.

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#33 Post by Sky Aisling »

Haven't tried that.
Will have a go at it tomorrow.
Thank you ...

Edit: The next morning;
When running from save file, can you get things working again by reprobing for modem in Menu / Network / Pupdial modem dialup?


Hi Dewbie,
There isn't anything called *Pupdial modem dialup* in Menu/Network/ in the Puppy-520 menu.

There is:
Firewallstate ...
Gpp&p pptp vpn client
Linux-firewall ...
MTR traceroute
Pcurl Ftp ...
Pnethood Samba ...
Pure FTP
Super Scan network Scanner

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#34 Post by Karl Godt »

forget about pupdial !

install pgprs-connect and pgprs-setup typing

Code: Select all

pgprs-shell
This installs /usr/bin/pgprs-setup to setup the modem and then run pgprs-connect . Both appear also in the Network menu .

Checkout that the driver always loads . Replug the modem to trigger it again .
"invalid argument" might be same as "unrecognized option /dev/tty*" in pgprs-connect when the driver is not loaded .

Dewbie

#35 Post by Dewbie »

Sky Aisling wrote:
There isn't anything called *Pupdial modem dialup* in Menu/Network/ in the Puppy-520 menu.
I thought we were dealing with 4.3.1. :?

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#36 Post by Sky Aisling »

Sorry Dewbie, my lack of attention. :oops:

I've tried so many combinations of OSes and how they are booted that I forgot we were talking about 4.3.1. in the previous post.

I cleaned off the 4.3.1. frugal install test and went back to his Puppy-520 via Live CD because I have 520 all tricked out for him.
My energy to customize another OS waned at about midnight last night.

I was going to give up and take the machine back today.
But, Karl is making one more suggestion that I want to try then I must stop.

Karl, is your suggestion
install pgprs-connect and pgprs-setup typing
Code:
pgprs-shell
applicable to Puppy-520?

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#37 Post by Karl Godt »

Puppy 520 is very special because I do not have it . After the puppy-511 and dpup-iguleder i stopped to test Puppy. Puppy boots and that is "so awfully normal" that it bored me off :P:

pgprs-setup is stock standard puppy inventory for the connect icon on the desktop, so should have it, except someone (playdays) forgot to implement it, cut down /lib/modules/all-modules where the pgprs.tar.gz is located that pgprs-shell installs or there was a woof problem that day as the iso had been created .

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#38 Post by Sky Aisling »

Karl writes:
forget about pupdial !

install pgprs-connect and pgprs-setup typing

Code:
pgprs-shell


This installs /usr/bin/pgprs-setup to setup the modem and then run pgprs-connect . Both appear also in the Network menu .

Checkout that the driver always loads . Replug the modem to trigger it again .
"invalid argument" might be same as "unrecognized option /dev/tty*" in pgprs-connect when the driver is not loaded .
Here is what I have so far.
Where do I set up the *connect script*?
Doesn't this program need provider's name, userid, userpassword?

BTW - Puppy-520 menu/network doesn't show *pgprs connect*.
I took both *setup* and *connect* from user/share/applications and put shortcut on desktop.
Edit: after I *rebooted* the *pgprs connect* and *pgprs setup* is listed in menu/network.
Attachments
pgprs2.png
(168.42 KiB) Downloaded 961 times

User avatar
Sky Aisling
Posts: 1368
Joined: Sat 27 Jun 2009, 23:02
Location: Port Townsend, WA. USA

How to disable internal dialup modem?

#39 Post by Sky Aisling »

Update to Dial-Up Issue on Toshiba Satellite 1415-S115 running Puppy Linux-520

Well, the issue is *solved* in that the local computer repair store gave me a 2000 Dell Latitude PP01L with a smashed hard drive. I peeled the disinigrated HDD out of the machine, shook out the remaining slivers of plastic and loaded up a Live CD with a Puppy 4.3.1 Kernel 2.6.30.5 (i686). I put Shino's Bar's updated version of SeaMonkey 2.10 on a flash drive along with the pup-save file. Puppy 4.3.1 took off running with the dial-up frisbee firmly clenched in it's teeth.

My friend can now enjoy the amazing technology of dial-up in the comfort of his home. :) Thank you one and all.

Sky

PS - The Dell also had an internal modem but Puppy 4.3.1 was able to handle both the internal and external modem conflict with no issue (so far).

Post Reply