Puppy Linux Discussion Forum

[Aung]

A little late, just checked in again to this thread.
In Fatdog I see it wanted to use wlan) so I killed it in 'manage services ect'

Attempting connection through /dev/ttyUSB2 to APN cellcard...

Selected interface 'wlan0'
OK

defining PDP context...

ERROR
Connect script failed
Exit status is 8
DISCONNECTED

But still same error message

defining PDP context...

ERROR
Connect script failed
Exit status is 8
DISCONNECTED


On micko slacko, which works for 3G modems, using it now. A bit more detail.
( I'm a bit disappointed that it needs PPP and what ever else, I was hoping it was a stand alone program which these modems need. I have a telstra and a virgin modem that have linux on them but when I tried to compile them I get the 'install: missing file operand ' message. End of experiment. Old sage is right, they really are made for the DEVIL.)

defining PDP context...

ERROR
Script chat -v -f /etc/ppp/chatscripts/gprs-connect-chat finished (pid 17491), status = 0x9
Connect script failed
Exit status is 8
DISCONNECTED


From micko in terminal
# pgprs
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.

Brings up the interface, click connect, same error repeated.

Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.

Fatdog from terminal, shows nothing.

[LazY Puppy]

Pdiag file sent by PM.

[amn87]

I was finally able to get internet working in Slacko 6.3 using my Nokia for USB Tethering after installing PGPRS2. Thanks a lot @rerwin

[rerwin]

The new pgprs seems to work well on standard puppies, but not on fatdog64 nor the debiandogs. In fatdog64, the PPP connection fails immediately, for reasons beyond what I can determine at this time. More work is needed to adapt pgprs for fatdog and the debiandogs. But I don;t want to delay release any further.

I am grateful to LazY Puppy for his persistence in testing this pgprs until I got it working, and now, too, the frisbee implementation based on pgprs.

amn87, Thanks for the praise. But it should go to 01micko, who developed "pgprs2". Mine is now designated as "pgprs-2.0. We started with the same original pgprs, but implemented our new versions in different ways.

Thank you, all who have been using the betas.
Richard

[rerwin]

To fix a noticeable problem in fatdog64, I have re-uploaded pgprs-2.0 after download number 1, with a minor change. I activated the "debug" option on line 30 of /etc/ppp/peers/gprs-editable.

Be aware, though, that installing the package does not replace an existing copy of that file. That is to preserve any changes already made to it. So, either edit the file yourself and ignore the replacement package, or remove that file before installing the replacement.

This is needed only in fatdog64, which does not have the usual 'options' file that contains the 'debug' line. This fix probably removes the dependency on the 'options' file.

Aung, This should help to get more information on your problem, but won't solve it. But it will help us work on it.

[LazY Puppy]

[Aung]

rerwin,
Fatdog without savefile dont have 'line 30 of /etc/ppp/peers/gprs-editable' so I just loaded the pets. Starting from terminal brings up the interface but not else.

Attempting connection through /dev/ttyUSB2 to APN cellcard...
defining PDP context...
ERROR
Script chat -v -T *99# -f /etc/ppp/chatscripts/gprs-connect-chat finished (pid 1687), status = 0x9
Connect script failed
Exit status is 8
DISCONNECTED

"This is needed only in fatdog64, which does not have the usual 'options' file that contains the 'debug' line. This fix probably removes the dependency on the 'options' file."

Does this mean etc/wvdial-options, FD has this with APN virginbroadband in it. It only has -chap in it.
If you want to give up on FD thats ok, as long as I can go online with micko slacko.

[watchdog]

I have forced to retirement my internet usb dongles. I now use the internal modem of a 3G android tablet: I have success to connect with both pupdial and pgprs-2.0 using puppy xenial 7.0.1. Thanks rerwin.

[rerwin]

watchdog,
Thanks for reporting your success with pgprs-2.0 on Xenial Pup.

LazY Puppy,
The re-upload does not need testing. It merely duplicates the 'debug' option selection already stated in another file that is also used as input -- just not in fatdog64. So, nothing has changed.

Aung,
Turning on debug logging added only the line:

[Aung]

Just checked in again. New pgprs, 2.0 bare fd702 no savefile.
Can confirm wlan 0 on first use only. Starting from terminal takes about 20 secs. to load. Nothing shows up in terminal. Drop down box only has ttyusb2, /dev has ttyusb0, 1 and 2, press refresh and pgprs freezes. The first 2 lines about 'dhcpcd', I dont know if they appeared before or after I loaded the pets.
Just curious, Why is there nothing showing up in the terminal

May 25 04:21:30 fatdog64-249 daemon.err dhcpcd[614]: timed out
May 25 04:21:30 fatdog64-249 daemon.info dhcpcd[614]: exited
May 25 04:25:17 fatdog64-249 user.notice logger: pgprs: Starting PPP daemon for /dev/ttyUSB2
May 25 04:25:17 fatdog64-249 daemon.notice pppd[2214]: pppd 2.4.7 started by root, uid 0
May 25 04:25:17 fatdog64-249 kern.info kernel: PPP generic driver version 2.4.2
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: timeout set to 10 seconds
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: abort on (\nBUSY\r)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: abort on (\nNO ANSWER\r)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: abort on (\nNO CARRIER\r)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: abort on (\nNO DIALTONE\r)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: abort on (\nRINGING\r\n\r\nRINGING\r)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: abort on (\nERROR\r)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: send (^MAT^M)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: timeout set to 12 seconds
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: expect (OK)
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: ^M^M
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: ERROR^M
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: -- failed
May 25 04:25:17 fatdog64-249 local2.info chat[2219]: Failed ( ERROR^M)
May 25 04:25:17 fatdog64-249 daemon.debug pppd[2214]: Script chat -v -T *99# -f /etc/ppp/chatscripts/gprs-connect-chat finished (pid 2219), status = 0x9
May 25 04:25:17 fatdog64-249 daemon.err pppd[2214]: Connect script failed
May 25 04:25:17 fatdog64-249 daemon.info pppd[2214]: Exit.
May 25 04:25:17 fatdog64-249 user.notice logger: pgprs: pppd exit status for /dev/ttyUSB2 is 8

[rerwin]

I have uploaded versions of pgprs and connect_updates that match what I submitted for inclusion in the woof-CE world, so that they can be included in builds of new puppies.

Most of the changes are to the installation process, with 2 minor noticeable differences. The icon in the menu and the upper left corner of each window now matches the icon in the Connect Wizard. The other change is that the Connect Wizard does not now recognize the original version of pgprs, which 2.0.1 replaces.

A lesson learned from my stepping up to woof-CE: In packages containing soft links, the target of those links will be uploaded to woof-CE instead of the link itself. Those links should be set in a pinstall.sh script at installation time. To have those links represented in the installed-files list (*.files), a dummy file of the same name could be included in the package, to be overwritten by the pinstall script.

UPDATE: After download number 4 of pgprs, I re-uploaded it with a change that affects only the woof-build environment. A second "lesson learned" is that pinstall scripts in submitted packages cannot contain the command, "exit", because it disrupts the build process.

I expect this to be the final version of pgprs, unless someone reports a problem. I think it's done!

[rerwin]

A new version is uploaded to the first message:
http://www.murga-linux.com/puppy/viewtopic.php?p=883858#883858

It is compatible with both the connect_update and network_connect_update packages, and is required for the latter.