Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 18 Nov 2017, 02:54
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
pgprs-2.0.2
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 3 [42 Posts]   Goto page: Previous 1, 2, 3
Author Message
Aung

Joined: 19 Jan 2007
Posts: 144
Location: Hervey Bay

PostPosted: Sun 01 May 2016, 23:21    Post subject:  

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.
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 2007
Location: Germany

PostPosted: Wed 04 May 2016, 09:43    Post subject:  

Pdiag file sent by PM.
_________________
RSH

"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) Laughing

No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! Wink
Back to top
View user's profile Send private message 
amn87

Joined: 28 Mar 2016
Posts: 13

PostPosted: Sun 08 May 2016, 13:42    Post subject:  

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
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1842
Location: Maine, USA

PostPosted: Wed 18 May 2016, 23:01    Post subject: pgprs-2.0 uploaded  

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
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1842
Location: Maine, USA

PostPosted: Thu 19 May 2016, 15:29    Post subject: Pgprs fatdog64 fix  

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.
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 2007
Location: Germany

PostPosted: Fri 20 May 2016, 17:12    Post subject:  

Quote:
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.

So, this would need one more testing for non-fatdog users?

_________________
RSH

"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) Laughing

No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! Wink
Back to top
View user's profile Send private message 
Aung

Joined: 19 Jan 2007
Posts: 144
Location: Hervey Bay

PostPosted: Sat 21 May 2016, 02:18    Post subject:  

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.
Back to top
View user's profile Send private message 
watchdog

Joined: 28 Sep 2012
Posts: 1490
Location: Italy

PostPosted: Sat 21 May 2016, 06:19    Post subject:  

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.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1842
Location: Maine, USA

PostPosted: Sat 21 May 2016, 20:04    Post subject:  

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:
Code:
Script chat -v -T *99# -f /etc/ppp/chatscripts/gprs-connect-chat finished (pid 1687), status = 0x9
The 0x9 just reflects that chat stopped because the ERROR abort trap occurred. I thought it might add the list of AT commands and responses. So, the chat seems to die even before an AT command starts!

While trying to work on this problem in fatdog64, I discovered that the setup window produces between 2 and 4 instances of the message: "broken pipe" on "line 12". I made changes to line 12 and another similar line of the dialog definition, but the number of messages changed seemingly randomly each time. Very strange!

I am afraid I will have to admit defeat with fatdog unless its developer can help out. But if fatdog already has a GPRS tool (which appears to be the case), there is no need to add a competing tool. If you can send me the file, /var/log/messages, I could check that for clues; but I don't expect that anything will "pop out".

Thanks for your help in identifying this problem.

Afterthought: Does the device dropdown list give you any other device possibilities? The usual device is /dev/ttyUSB0. Did you try any other devices?

More: My test PC also shows the "Selected interface 'wlan0' " line, as I have a wifi card but no available networks (out here in the country). But that seems to occur only on the first use in a no-savefile situation. The next connect attempt shows the AT commands before the ERROR (because I am using an analog modem, which doesn't understand the APN business). Do subsequent connect attempts get any further? Maybe there is a "timing" issue somewhere.
Back to top
View user's profile Send private message 
Aung

Joined: 19 Jan 2007
Posts: 144
Location: Hervey Bay

PostPosted: Wed 25 May 2016, 07:19    Post subject:  

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
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1842
Location: Maine, USA

PostPosted: Tue 14 Jun 2016, 20:39    Post subject: Uploaded pgprs-2.0.1 uploaded  

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!
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1842
Location: Maine, USA

PostPosted: Wed 17 May 2017, 19:54    Post subject:  

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.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 3 [42 Posts]   Goto page: Previous 1, 2, 3
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0518s ][ Queries: 13 (0.0061s) ][ GZIP on ]