pgprs-2.0.4-beta
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.
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
- Posts: 1934
- Joined: Fri 21 Nov 2014, 18:14
- Location: Germany
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
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
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.
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
- Posts: 1934
- Joined: Fri 21 Nov 2014, 18:14
- Location: Germany
So, this would need one more testing for non-fatdog users?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.
RSH
"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) :lol:
No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! :wink:
"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) :lol:
No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! :wink:
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.
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,
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: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.
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: Select all
Script chat -v -T *99# -f /etc/ppp/chatscripts/gprs-connect-chat finished (pid 1687), status = 0x9
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.
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
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
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!
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!
A new version is uploaded to the first message:
http://www.murga-linux.com/puppy/viewto ... 858#883858
It is compatible with both the connect_update and network_connect_update packages, and is required for the latter.
http://www.murga-linux.com/puppy/viewto ... 858#883858
It is compatible with both the connect_update and network_connect_update packages, and is required for the latter.
A new version is uploaded to the first message:
http://www.murga-linux.com/puppy/viewto ... 858#883858
Pgprs-2.03 was submitted to woofCE in July of 2018, but inadvertently did not get added to this thread at that time.
It simplifies the detection of modems by avoiding the use of the modem-stats tool.
http://www.murga-linux.com/puppy/viewto ... 858#883858
Pgprs-2.03 was submitted to woofCE in July of 2018, but inadvertently did not get added to this thread at that time.
It simplifies the detection of modems by avoiding the use of the modem-stats tool.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
WoofQ has version 2.0.2.
/usr/sbin has 'pgprs', and 'pgprs-connect' and 'pgprs-shell' symlinks to it. I see that the 2.0.3 PET doesn't have those symlinks. is that OK?
WoofQ doesn't have /usr/share/applications/pgprs-connect.desktop
I don't recall how it was invoked in that case.
EasyOS and EasyPup use NetworkManager by default, but are still supposed to be able to fallback to sns, pgprs, etc.
/usr/sbin has 'pgprs', and 'pgprs-connect' and 'pgprs-shell' symlinks to it. I see that the 2.0.3 PET doesn't have those symlinks. is that OK?
WoofQ doesn't have /usr/share/applications/pgprs-connect.desktop
I don't recall how it was invoked in that case.
EasyOS and EasyPup use NetworkManager by default, but are still supposed to be able to fallback to sns, pgprs, etc.
[url]https://bkhome.org/news/[/url]
Thanks, Barry, for your posting.
I am re-examining pgprs after several years of assuming it worked, but now am aware of some problems with it.
My difficulty with testing it is that I do not have a 3G modem that works in linux, and I do not have a data option for my minimalist cell phone account. So, I depend on others to work with me to resolve the problems.
The symlinks are for backward compatibility with your connectwizard, which interfaces with the pre-2.0 versions of pgprs. But I am not sure that actually works.
My intent, I think, was to have pgprs invoked from both connectwizard and a menu entry, because people were accustomed to the menu entry. It could be added to Easy to use the new interface, as a backup to the connectwizard option.
Maybe you should wait until I work out an issue with pgprs, where the connect log is not displayed as intended, at least when the connection fails due to an error. I am surprised that with so many downloads of pgprs, I am only now made aware of a problem. Maybe that means that it usually connects.
My intent with 2.0 was to mimic pupdial's option to quit the connection window but let the connection continue. I am not sure I completed that change. I need more feedback from users.
I am re-examining pgprs after several years of assuming it worked, but now am aware of some problems with it.
My difficulty with testing it is that I do not have a 3G modem that works in linux, and I do not have a data option for my minimalist cell phone account. So, I depend on others to work with me to resolve the problems.
The symlinks are for backward compatibility with your connectwizard, which interfaces with the pre-2.0 versions of pgprs. But I am not sure that actually works.
My intent, I think, was to have pgprs invoked from both connectwizard and a menu entry, because people were accustomed to the menu entry. It could be added to Easy to use the new interface, as a backup to the connectwizard option.
Maybe you should wait until I work out an issue with pgprs, where the connect log is not displayed as intended, at least when the connection fails due to an error. I am surprised that with so many downloads of pgprs, I am only now made aware of a problem. Maybe that means that it usually connects.
My intent with 2.0 was to mimic pupdial's option to quit the connection window but let the connection continue. I am not sure I completed that change. I need more feedback from users.
I know if I go to wiki I see all kind of info.
But to my knowledge pgprs was used in type 1G ( G ) Network. Just after Edge network. I now wiki will tell you good to 2.5 and even 3G. Now Ignoring what is right or wrong.
Do we have user TODAY using pgprs?
Here in America even 3G is phasing out and soon not even old 3G phones will work.
But to my knowledge pgprs was used in type 1G ( G ) Network. Just after Edge network. I now wiki will tell you good to 2.5 and even 3G. Now Ignoring what is right or wrong.
Do we have user TODAY using pgprs?
Here in America even 3G is phasing out and soon not even old 3G phones will work.
Neither do I. But it's my understanding that you can do this just with wvdial.rerwin wrote:My difficulty with testing it is that I do not have a 3G modem that works in linux, and I do not have a data option for my minimalist cell phone account.
1. Run: wvdialconf
2. Edit /etc/wvdial and enter your connection data.
3. Run: wvdial
Too bad that community members won't stay around long enough to resolve this.So, I depend on others to work with me to resolve the problems.
BarryK,BarryK wrote:WoofQ has version 2.0.2.
/usr/sbin has 'pgprs', and 'pgprs-connect' and 'pgprs-shell' symlinks to it. I see that the 2.0.3 PET doesn't have those symlinks. is that OK?
WoofQ doesn't have /usr/share/applications/pgprs-connect.desktop
I don't recall how it was invoked in that case.
EasyOS and EasyPup use NetworkManager by default, but are still supposed to be able to fallback to sns, pgprs, etc.
Regarding the symlinks, I have determined what needs to be changed in EasyOS (etc.) to use the interface provided by the 2.x versions of pgprs and attach them below. The tarball can be extracted to '/', or elsewhere if you just want to examine it (top directory: /usr). The difference listings summarize the changes, some of which are only for consistency and do not affect operation. With the updates installed, the two symlinks can be deleted from EasyOS.
I include the current version of get_modem_alternative_device because it is needed for pgprs, due to a bug in pgprs-setup that fails to detect the older version. The new version identifies the available serial devices (e.g., ttyACM0).
Regarding the .desktop file, I notice that /usr/local/sfsget/dir2pet generates /.control/easy.run-once-top that removes the desktop file for 'pgprs-connect'. That leaves pgprs-connect out of the menu.
A significant upgrade to networking in woofCE is management of switching among the various network managers without impacting each other. It adds the termination of the "current" manager windows in case the user switches while another manager is running. Otherwise, the user may see misleading indications of network status. The absence of that protection in EasyOS might influence whether you have pgprs in the menu.
- Attachments
-
- diff-pgprs_interfaces_easyos.txt.gz
- Summary of the changes
- (1.25 KiB) Downloaded 100 times
-
- diff-pgprs_interfaces_easyos_unified.txt.gz
- A basis for patching
- (3.34 KiB) Downloaded 107 times
-
- EasyOS_pgprs_updates.tar.gz
- Updated 2.3.1 scripts
- (13.69 KiB) Downloaded 98 times
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Thanks for taking the time to wend your way through all of that stuff!rerwin wrote:BarryK,BarryK wrote:WoofQ has version 2.0.2.
/usr/sbin has 'pgprs', and 'pgprs-connect' and 'pgprs-shell' symlinks to it. I see that the 2.0.3 PET doesn't have those symlinks. is that OK?
WoofQ doesn't have /usr/share/applications/pgprs-connect.desktop
I don't recall how it was invoked in that case.
EasyOS and EasyPup use NetworkManager by default, but are still supposed to be able to fallback to sns, pgprs, etc.
Regarding the symlinks, I have determined what needs to be changed in EasyOS (etc.) to use the interface provided by the 2.x versions of pgprs and attach them below. The tarball can be extracted to '/', or elsewhere if you just want to examine it (top directory: /usr). The difference listings summarize the changes, some of which are only for consistency and do not affect operation. With the updates installed, the two symlinks can be deleted from EasyOS.
I include the current version of get_modem_alternative_device because it is needed for pgprs, due to a bug in pgprs-setup that fails to detect the older version. The new version identifies the available serial devices (e.g., ttyACM0).
Regarding the .desktop file, I notice that /usr/local/sfsget/dir2pet generates /.control/easy.run-once-top that removes the desktop file for 'pgprs-connect'. That leaves pgprs-connect out of the menu.
A significant upgrade to networking in woofCE is management of switching among the various network managers without impacting each other. It adds the termination of the "current" manager windows in case the user switches while another manager is running. Otherwise, the user may see misleading indications of network status. The absence of that protection in EasyOS might influence whether you have pgprs in the menu.
I have applied the changes to woofQ, and bumped defaults-chooser PET:
http://murga-linux.com/puppy/viewtopic. ... 03#1060803
...that would be /usr/local/sfsget/dir2sfs script.Regarding the .desktop file, I notice that /usr/local/sfsget/dir2pet generates /.control/easy.run-once-top that removes the desktop file for 'pgprs-connect'. That leaves pgprs-connect out of the menu.
The scripts in .control inside the sfs only run when the sfs is in a container, not when on the main desktop. Also EasyPup will ignore .control folder.
In a container, whatever network setup is active on the main desktop, is inherited inside the container, so we don't want any network setup menu entries in, for example the containerised EasyOS.
[url]https://bkhome.org/news/[/url]
-
- Posts: 159
- Joined: Sun 01 Mar 2020, 16:17
Hi. It's me, RSH. I made testings for pgprs some time ago, around version 2.0 and before that to get it working in Puppy. I'm reporting the issues when using FossaPup by 666philb.
1. The version installed by default in FossaPup is 2.0.2. Can't connect to the web using pgprs. Modem is detected by /dev/ttyUSB0 as it should be. When I'm installing the attached older version I can connect to the web immediately.
2. FossaPup rebooted to start fresh. After installing version 2.0.3 still can't connect to the web. Modem is not detected anymore. The only device detected is /dev/ttyS0 which doesn't seem to be my modem. Connection not possible. After installing the attached older version connection still not possible.
Attached .pet is a modified version for my own ease of use, which came from Slacko 5.7. Works in all my Puppies.
1. The version installed by default in FossaPup is 2.0.2. Can't connect to the web using pgprs. Modem is detected by /dev/ttyUSB0 as it should be. When I'm installing the attached older version I can connect to the web immediately.
2. FossaPup rebooted to start fresh. After installing version 2.0.3 still can't connect to the web. Modem is not detected anymore. The only device detected is /dev/ttyS0 which doesn't seem to be my modem. Connection not possible. After installing the attached older version connection still not possible.
Attached .pet is a modified version for my own ease of use, which came from Slacko 5.7. Works in all my Puppies.
- Attachments
-
- pgprs-s57-6.pet
- (28.77 KiB) Downloaded 106 times
Our Future Is Not Set In Stone
[url]https://www.youtube.com/channel/UCyfyaxCNMduwyXlQFRQKhhQ[/url]
[url]https://soundcloud.com/user-633698367[/url]
[b]My own build of Bionic64[/b]
[url]https://www.youtube.com/channel/UCyfyaxCNMduwyXlQFRQKhhQ[/url]
[url]https://soundcloud.com/user-633698367[/url]
[b]My own build of Bionic64[/b]