Dialup/Wireless Modem Upgrade Packages for Puppy 4.3+
Thanks very much to all of you for responding with useful info on this matter!
I must say that, apparently, my actions of configuring Wary 512 to use the internal modem of this notebook has had the effect of leaving me without audio & the capacity to connect via ethernet (up to yesterday) & today even Seamonkey was not responding well. In one 'wizard' there was a button for testing the audio syst. & below it was another for stoping the barks: it continued barking even after the Stop button was clicked many times. The only way I was able to connect was via wireless. After the barks, even Seamonkey stopped responding: my extreme reaction has been to delete both, the warysave & the SFS files. Let me see what's going to happen next time because now I'm again in PL511.
After I bootup Wary512 I'll try all the recommendations given in order & post the results below.
PS. To tempestuous --In your last post you mention another driver as well as a patch &, for me, it got a little too technical. I most say I didn't understand fully the info within this post; sorry.
I must say that, apparently, my actions of configuring Wary 512 to use the internal modem of this notebook has had the effect of leaving me without audio & the capacity to connect via ethernet (up to yesterday) & today even Seamonkey was not responding well. In one 'wizard' there was a button for testing the audio syst. & below it was another for stoping the barks: it continued barking even after the Stop button was clicked many times. The only way I was able to connect was via wireless. After the barks, even Seamonkey stopped responding: my extreme reaction has been to delete both, the warysave & the SFS files. Let me see what's going to happen next time because now I'm again in PL511.
After I bootup Wary512 I'll try all the recommendations given in order & post the results below.
PS. To tempestuous --In your last post you mention another driver as well as a patch &, for me, it got a little too technical. I most say I didn't understand fully the info within this post; sorry.
Dialup/Wireless 3G Modem
Hi rewin.
Thank you so much for all your work to make puppy such a great Linux distribution.
I am using Lupu 525 and have just bought a 3G modem. It’s being sold in Germany and comes from “klaremobil.de
Thank you so much for all your work to make puppy such a great Linux distribution.
I am using Lupu 525 and have just bought a 3G modem. It’s being sold in Germany and comes from “klaremobil.de
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Re: Dialup/Wireless 3G Modem
[quote="TIW"]I tried to connect with “Internet by wireless GPRS modem
I think you should verify your copy of 512. Check the md5sum of the .iso you downloaded against the value given on the site you downloaded from. Also verify the md5sum of the CD after you've burnt it. No point in spending a lot of time trying to get something to work when it's corrupt!benny7440 wrote:I must say that, apparently, my actions of configuring Wary 512 to use the internal modem of this notebook has had the effect of leaving me without audio & the capacity to connect via ethernet (up to yesterday) & today even Seamonkey was not responding well.
Today I spent about 90 mins trying to connect via ethernet or wireless (yesterday I did it using wlan) but it never gave up...
So, now I'm with PL525 (which for some reason refuses to remember that I'm installing a FF PET specifically for 525). It also insist in showing me at startup a configuration window that I've accepted many times already.
The requested info/files are included below as attachements.
The lsmod command's output can't be included as an attachement. By the way, in PL525, when I click on a text file it won't open anything. For I been able to paste the requested info below had to open first NicoEdit from the Menu, under the File tab click Open & search for the file + select all + copy. Does this has a quick fix? Have Geany in the open with menu options as well as the main Menu entry for it, but if I click on Geany nothing happens.
# lsmod
Module Size Used by
agrserial 7469 0
battery 7232 0
agrmodem 1232861 1
snd_hda_codec_idt 33542 1
arc4 954 2
ecb 1381 2
apm 9673 1
evdev 5525 1
iwl3945 58747 0
iwlcore 70103 1 iwl3945
mac80211 100092 2 iwl3945,iwlcore
led_class 1737 2 iwl3945,iwlcore
cfg80211 89366 3 iwl3945,iwlcore,mac80211
serio_raw 2864 0
rfkill 9872 1 cfg80211
pcspkr 1179 0
snd_hda_intel 15242 0
e100 21838 0
mii 2630 1 e100
snd_hda_codec 37509 3 agrmodem,snd_hda_codec_idt,snd_hda_intel
snd_pcm_oss 27859 0
snd_mixer_oss 10097 1 snd_pcm_oss
snd_pcm 46627 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
ohci1394 21365 0
ieee1394 51015 1 ohci1394
snd_seq_dummy 903 0
snd_seq_oss 18853 0
snd_seq_midi 3156 0
snd_rawmidi 11903 1 snd_seq_midi
snd_seq_midi_event 3592 2 snd_seq_oss,snd_seq_midi
snd_seq 33207 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
i2c_i801 6194 0
i2c_core 12215 1 i2c_i801
snd_timer 11802 2 snd_pcm,snd_seq
snd_seq_device 3613 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 31363 12 agrmodem,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
shpchp 21252 0
pci_hotplug 18214 1 shpchp
soundcore 3339 1 snd
snd_page_alloc 4673 2 snd_hda_intel,snd_pcm
intel_agp 19047 0
agpgart 19180 1 intel_agp
usb_storage 30317 0
usbhid 18389 0
fuse 43257 0
aufs 121731 571
nls_iso8859_1 2937 0
nls_cp437 4465 0
squashfs 16060 1
tifm_sd 6282 0
mmc_block 5972 0
mmc_core 35515 2 tifm_sd,mmc_block
tifm_7xx1 2966 0
tifm_core 3104 2 tifm_sd,tifm_7xx1
uhci_hcd 15691 0
ehci_hcd 27928 0
usbcore 91490 6 agrmodem,usb_storage,usbhid,uhci_hcd,ehci_hcd
yenta_socket 16259 1
rsrc_nonstatic 6869 1 yenta_socket
psmouse 47311 0
#
So, now I'm with PL525 (which for some reason refuses to remember that I'm installing a FF PET specifically for 525). It also insist in showing me at startup a configuration window that I've accepted many times already.
The requested info/files are included below as attachements.
The lsmod command's output can't be included as an attachement. By the way, in PL525, when I click on a text file it won't open anything. For I been able to paste the requested info below had to open first NicoEdit from the Menu, under the File tab click Open & search for the file + select all + copy. Does this has a quick fix? Have Geany in the open with menu options as well as the main Menu entry for it, but if I click on Geany nothing happens.
# lsmod
Module Size Used by
agrserial 7469 0
battery 7232 0
agrmodem 1232861 1
snd_hda_codec_idt 33542 1
arc4 954 2
ecb 1381 2
apm 9673 1
evdev 5525 1
iwl3945 58747 0
iwlcore 70103 1 iwl3945
mac80211 100092 2 iwl3945,iwlcore
led_class 1737 2 iwl3945,iwlcore
cfg80211 89366 3 iwl3945,iwlcore,mac80211
serio_raw 2864 0
rfkill 9872 1 cfg80211
pcspkr 1179 0
snd_hda_intel 15242 0
e100 21838 0
mii 2630 1 e100
snd_hda_codec 37509 3 agrmodem,snd_hda_codec_idt,snd_hda_intel
snd_pcm_oss 27859 0
snd_mixer_oss 10097 1 snd_pcm_oss
snd_pcm 46627 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
ohci1394 21365 0
ieee1394 51015 1 ohci1394
snd_seq_dummy 903 0
snd_seq_oss 18853 0
snd_seq_midi 3156 0
snd_rawmidi 11903 1 snd_seq_midi
snd_seq_midi_event 3592 2 snd_seq_oss,snd_seq_midi
snd_seq 33207 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
i2c_i801 6194 0
i2c_core 12215 1 i2c_i801
snd_timer 11802 2 snd_pcm,snd_seq
snd_seq_device 3613 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 31363 12 agrmodem,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
shpchp 21252 0
pci_hotplug 18214 1 shpchp
soundcore 3339 1 snd
snd_page_alloc 4673 2 snd_hda_intel,snd_pcm
intel_agp 19047 0
agpgart 19180 1 intel_agp
usb_storage 30317 0
usbhid 18389 0
fuse 43257 0
aufs 121731 571
nls_iso8859_1 2937 0
nls_cp437 4465 0
squashfs 16060 1
tifm_sd 6282 0
mmc_block 5972 0
mmc_core 35515 2 tifm_sd,mmc_block
tifm_7xx1 2966 0
tifm_core 3104 2 tifm_sd,tifm_7xx1
uhci_hcd 15691 0
ehci_hcd 27928 0
usbcore 91490 6 agrmodem,usb_storage,usbhid,uhci_hcd,ehci_hcd
yenta_socket 16259 1
rsrc_nonstatic 6869 1 yenta_socket
psmouse 47311 0
#
benny7440,
Sorry to be so long in responding to your posting. Lots of distractions. And, yesterday and today, some research time on this.
- The agrsm support comes in 3 flavors, only one of which supports your HDA-type modem. That variant is "11c11040", which so far is available only in wary and two upgrade packages for 4.3.1. (The variant in PL525 is not that one.)
- As far as I can tell from googling, the latest version (20091225) was coded for ALSA version 1.0.20, whereas wary has 1.0.21. That is not to say it will not work in wary; but the maintainer has apparently not determined that it would work with 1.0.21, either.
- Furthermore, the agrsm HDA driver has apparently been made to work with kernels up to 2.6.31 and with some patch also 2.6.32. I do not know whether wary's version is 2.6.32-capable, but let's assume it is.
So, your next experiments should be on wary 5.1.2. That also has a fix so that blacklisting of agrmodem should work, when you try that. I am attaching 2 experimental packages to try one at a time, at a point in your experiments. The first applies a change I found in my googling, which may not help, but would confirm that its problem-fix is not the issue. The other blacklists the 2 agrsm driver modules, in case that might work.
Now, on to the experiments, using only wary 5.1.2:
1. Boot with pfix=ram, to start afresh. If modem detected, try connecting with pupdial (not the GPRS connect option). If that fails, stop right there and run pmodemdiag. Then exit from the connection. While still in pupdial, click on CHOOSE and ERASE... and exit pupdial.
2. Then install package agrsm_fix-1 and reboot, creating a pupsave file and giving it a name extension when so prompted.
3. When booted up with the "1" package installed, try the connection, as before, and (after changing the name of the first diag file a bit) run pmodemdiag. Exit from the connection . While still in pupdial, click on CHOOSE and ERASE... and exit pupdial. Then install agrsm_fix-2 and reboot.
4. After bootup, if a modem is detected, use pupdial to try to connect. Either way, run pmodemdiag again. Then exit the connection and pupdial and somehow post or PM the diag files, named to reflect their significance.
If none of these attempts work (probably due to the ALSA version mismatch), we can try again with an upgraded 4.3.1, to determine whether success is even possible with the versions in sync. (4.3.1 has kernel 2.6.30 and ALSA 1.0.20, so the mismatches could be eliminated as the cause of the failure to connect.)
Thank you for your interest in making your HDA Agere-chip modem actually work.
Richard
Sorry to be so long in responding to your posting. Lots of distractions. And, yesterday and today, some research time on this.
First, the only puppy of those you mention that has a chance of supporting your modem is wary 5, preferably 5.1.2. Let me lay out the situation before making a recommendation.I've a VAIO VGN AR250G Notebook - 512 MB RAM - running any of the following linux oss: (1) PL 431 (Live CD, only), (2) PL 511 (installed at sda2), (3) PL 525 (frugal) & (4) Wary 5.* (frugal -I'm using it right now).
- The agrsm support comes in 3 flavors, only one of which supports your HDA-type modem. That variant is "11c11040", which so far is available only in wary and two upgrade packages for 4.3.1. (The variant in PL525 is not that one.)
- As far as I can tell from googling, the latest version (20091225) was coded for ALSA version 1.0.20, whereas wary has 1.0.21. That is not to say it will not work in wary; but the maintainer has apparently not determined that it would work with 1.0.21, either.
- Furthermore, the agrsm HDA driver has apparently been made to work with kernels up to 2.6.31 and with some patch also 2.6.32. I do not know whether wary's version is 2.6.32-capable, but let's assume it is.
So, your next experiments should be on wary 5.1.2. That also has a fix so that blacklisting of agrmodem should work, when you try that. I am attaching 2 experimental packages to try one at a time, at a point in your experiments. The first applies a change I found in my googling, which may not help, but would confirm that its problem-fix is not the issue. The other blacklists the 2 agrsm driver modules, in case that might work.
Now, on to the experiments, using only wary 5.1.2:
1. Boot with pfix=ram, to start afresh. If modem detected, try connecting with pupdial (not the GPRS connect option). If that fails, stop right there and run pmodemdiag. Then exit from the connection. While still in pupdial, click on CHOOSE and ERASE... and exit pupdial.
2. Then install package agrsm_fix-1 and reboot, creating a pupsave file and giving it a name extension when so prompted.
3. When booted up with the "1" package installed, try the connection, as before, and (after changing the name of the first diag file a bit) run pmodemdiag. Exit from the connection . While still in pupdial, click on CHOOSE and ERASE... and exit pupdial. Then install agrsm_fix-2 and reboot.
4. After bootup, if a modem is detected, use pupdial to try to connect. Either way, run pmodemdiag again. Then exit the connection and pupdial and somehow post or PM the diag files, named to reflect their significance.
If none of these attempts work (probably due to the ALSA version mismatch), we can try again with an upgraded 4.3.1, to determine whether success is even possible with the versions in sync. (4.3.1 has kernel 2.6.30 and ALSA 1.0.20, so the mismatches could be eliminated as the cause of the failure to connect.)
Thank you for your interest in making your HDA Agere-chip modem actually work.
Richard
- Attachments
-
- agrsm_fix-1.pet
- adds option for snd-hda-intel driver
- (540 Bytes) Downloaded 1309 times
-
- agrsm_fix-2.pet
- blacklists agrsm drivers
- (535 Bytes) Downloaded 1286 times
FIRST TRIAL - NO FIX YET
# pmodemdiag
cat: /etc/puppyversion: No such file or directory
/usr/sbin/pmodemdiag: line 20: [: -ge: unary operator expected
Running PupScan to get hardware IDs and drivers - please close its window manually.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20110802.tar.gz.
grep: /tmp/pup_event_backend/pup_event_alsa_cnt*: No such file or directory
grep: /tmp/rc_sysinit/*: No such file or directory
Diagnostic file collection complete.
Tarball pmodemdiag-20110802.tar.gz can be attached to a posting or personal
message (PM) in the Puppy forum, for analysis of dialup modem issues.
The content can be found in /tmp/pmodemdiag-20110802/.
#
==============
SECOND TRIAL - PET FIX #1
# pmodemdiag
cat: /etc/puppyversion: No such file or directory
/usr/sbin/pmodemdiag: line 20: [: -ge: unary operator expected
Running PupScan to get hardware IDs and drivers - please close its window manually.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20110802.tar.gz.
grep: /tmp/pup_event_backend/pup_event_alsa_cnt*: No such file or directory
grep: /tmp/rc_sysinit/*: No such file or directory
Diagnostic file collection complete.
Tarball pmodemdiag-20110802.tar.gz can be attached to a posting or personal
message (PM) in the Puppy forum, for analysis of dialup modem issues.
The content can be found in /tmp/pmodemdiag-20110802/.
#
==============
THIRD TRIAL - PET FIX #2
# pmodemdiag
cat: /etc/puppyversion: No such file or directory
/usr/sbin/pmodemdiag: line 20: [: -ge: unary operator expected
Running PupScan to get hardware IDs and drivers - please close its window manually.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20110802.tar.gz.
grep: /tmp/pup_event_backend/pup_event_alsa_cnt*: No such file or directory
grep: /tmp/rc_sysinit/*: No such file or directory
Diagnostic file collection complete.
Tarball pmodemdiag-20110802.tar.gz can be attached to a posting or personal
message (PM) in the Puppy forum, for analysis of dialup modem issues.
The content can be found in /tmp/pmodemdiag-20110802/.
#
# pmodemdiag
cat: /etc/puppyversion: No such file or directory
/usr/sbin/pmodemdiag: line 20: [: -ge: unary operator expected
Running PupScan to get hardware IDs and drivers - please close its window manually.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20110802.tar.gz.
grep: /tmp/pup_event_backend/pup_event_alsa_cnt*: No such file or directory
grep: /tmp/rc_sysinit/*: No such file or directory
Diagnostic file collection complete.
Tarball pmodemdiag-20110802.tar.gz can be attached to a posting or personal
message (PM) in the Puppy forum, for analysis of dialup modem issues.
The content can be found in /tmp/pmodemdiag-20110802/.
#
==============
SECOND TRIAL - PET FIX #1
# pmodemdiag
cat: /etc/puppyversion: No such file or directory
/usr/sbin/pmodemdiag: line 20: [: -ge: unary operator expected
Running PupScan to get hardware IDs and drivers - please close its window manually.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20110802.tar.gz.
grep: /tmp/pup_event_backend/pup_event_alsa_cnt*: No such file or directory
grep: /tmp/rc_sysinit/*: No such file or directory
Diagnostic file collection complete.
Tarball pmodemdiag-20110802.tar.gz can be attached to a posting or personal
message (PM) in the Puppy forum, for analysis of dialup modem issues.
The content can be found in /tmp/pmodemdiag-20110802/.
#
==============
THIRD TRIAL - PET FIX #2
# pmodemdiag
cat: /etc/puppyversion: No such file or directory
/usr/sbin/pmodemdiag: line 20: [: -ge: unary operator expected
Running PupScan to get hardware IDs and drivers - please close its window manually.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20110802.tar.gz.
grep: /tmp/pup_event_backend/pup_event_alsa_cnt*: No such file or directory
grep: /tmp/rc_sysinit/*: No such file or directory
Diagnostic file collection complete.
Tarball pmodemdiag-20110802.tar.gz can be attached to a posting or personal
message (PM) in the Puppy forum, for analysis of dialup modem issues.
The content can be found in /tmp/pmodemdiag-20110802/.
#
- tech_jnke2
- Posts: 10
- Joined: Sun 21 Mar 2010, 07:19
benny, it looks like that what rerwin got or setup for you to try didn't work at all?
their has to be something in either hardware or software that is blocking you from using that modem. thats the only thing i can come up with so far.
did you erase the previous driver after each test? that could've caused a problem loading the right kernel, but right now it could be almost anything.
i seen this very same problem on the freespire forums , when i was using it , and they had a heck of a time fixing it , and it seemed that agere wasn't cooperating with linux people at that time.
i'll keep an eye on this to see what happens, and maybe this will get fixed then it will help those with the agere card, but wait and see another card will have same problem. a vicious cycle of non cooperating hardware.
their has to be something in either hardware or software that is blocking you from using that modem. thats the only thing i can come up with so far.
did you erase the previous driver after each test? that could've caused a problem loading the right kernel, but right now it could be almost anything.
i seen this very same problem on the freespire forums , when i was using it , and they had a heck of a time fixing it , and it seemed that agere wasn't cooperating with linux people at that time.
i'll keep an eye on this to see what happens, and maybe this will get fixed then it will help those with the agere card, but wait and see another card will have same problem. a vicious cycle of non cooperating hardware.
Thanks, tech_jnke2, for responding!
I probably should've said that I'm not booting from a livecd, but instead from a frugal install by grub. The part of booting up as <pfix=ram> was left out because I don't have the opportunity of intervening at the correct moment. I thought that if I deleted the previous pupsave file then just the "fix # (1 or 1+2) would be there for making its thing.
I probably need more advise as to how to do it correctly, if at all possible.
I probably should've said that I'm not booting from a livecd, but instead from a frugal install by grub. The part of booting up as <pfix=ram> was left out because I don't have the opportunity of intervening at the correct moment. I thought that if I deleted the previous pupsave file then just the "fix # (1 or 1+2) would be there for making its thing.
I probably need more advise as to how to do it correctly, if at all possible.
ModeSwitcher update to usb-modeswitch-1.1.9-20110805
I have uploaded the latest update of the usb_modeswitch function. This might be useful to anyone still not getting a wireless modem to connect.
Release Notes for Version 1.1.9, 2011/08/05:
If your system would not benefit from this update, it can be skipped.
Richard
Release Notes for Version 1.1.9, 2011/08/05:
- Added CiscoMode for Valet device;
Additional checking for CDC ACM device to prevent erroneous driver loading after switching;
No more post-switch check for access to initial device if target parameters are given.
- 0af0:7a01 - Option HSO device
0af0:8600 - Option HSO device
0af0:8800 - Option HSO device
0af0:8900 - Option HSO device
0af0:9000 - Option HSO device
12d1:14b7 - Vodafone (Huawei) K4511
12d1:14c5 - Vodafone (Huawei) K4510
1307:1169 - Cisco AM10 "Valet Connector"
19d2:1171 - Vodafone (ZTE) K4510-Z
19d2:1175 - Vodafone (ZTE) K3770-Z
19d2:1179 - Vodafone (ZTE) K3772-Z
If your system would not benefit from this update, it can be skipped.
Richard
modem-modprobe package updated to 2011905
I have uploaded version 20110905 which has more bug fixes and usb_modeswitch 1.1.9 and its data base. It also might help with some sound issues. See the first message in this thread.
Its bugfix level is the same as for lucid pup 5.2.8, so it should not be applied to any lucid pup versions beyond 5.2.5. In fact, 5.2.8 is so good, that you might consider upgrading to it rather than updating the earlier lucid pups -- unless that just is not practical.
Richard
Its bugfix level is the same as for lucid pup 5.2.8, so it should not be applied to any lucid pup versions beyond 5.2.5. In fact, 5.2.8 is so good, that you might consider upgrading to it rather than updating the earlier lucid pups -- unless that just is not practical.
Richard
ModeSwitcher update to usb-modeswitch-1.2.0-20111023
I have uploaded the latest update of the usb_modeswitch function.
http://www.murga-linux.com/puppy/viewto ... 074#431074
This might be useful to anyone still not getting a wireless modem to connect.
Release Notes for Version 1.2.0, 10/23/2011:
Richard
http://www.murga-linux.com/puppy/viewto ... 074#431074
This might be useful to anyone still not getting a wireless modem to connect.
Release Notes for Version 1.2.0, 10/23/2011:
- Added QisdaMode for H21 ("Flying Beetle")
Improved boot reliability, particularly when config files are packed
Some timing adjustments for more robust behaviour
Workaround for quirky devices with bogus interface count
Fix for possible buffer overflow
Added some ZTE target IDs
Modded udev rules to include "change" as trigger event
- 16d8:6804 - C-motech CDU-685a
1da5:4512 - Qisda H21 "Flying Beetle"
05c6:6503 - AnyDATA APE-540H
19d2:1517 - ZTE MF192 (new variant)
1bbb:f052 - Alcatel OT X220L
0421:062d - Nokia CS-19
12d1:1d50 - Huawei ET302
1e89:f000 - 3GO 3GO11 HSUPA
1410:5059 - Novatel MC545
19d2:ffde - ZTE AC682
19d2:0166 - ZTE MF820 4G LTE
1de1:1101 - Philips PicoPix 1020 (LED projector)
Richard
Can't connect Modem ZTE MF628
Hello dear friends!
Thank you all for this big work.
I’m new in Puppy Linux. I’m trying to connect my 3g Modem ZTE 628 but till now no success. I Installed the latest update of the usb_modeswitch and the package 3G_pupdial-wireless-13.pet.
The result is:
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","internet.tmn.pt"
AT+CGDCONT=1,"IP","internet.tmn.pt"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Tue Nov 29 10:41:02 2011
--> pid of pppd: 10341
--> Disconnecting at Tue Nov 29 10:41:43 2011
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
I attached “pmodemdiag
Thank you all for this big work.
I’m new in Puppy Linux. I’m trying to connect my 3g Modem ZTE 628 but till now no success. I Installed the latest update of the usb_modeswitch and the package 3G_pupdial-wireless-13.pet.
The result is:
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","internet.tmn.pt"
AT+CGDCONT=1,"IP","internet.tmn.pt"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Tue Nov 29 10:41:02 2011
--> pid of pppd: 10341
--> Disconnecting at Tue Nov 29 10:41:43 2011
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
I attached “pmodemdiag
Hernâni,
Thank you for posting your problem here. I suspect you are using the wrong update dotpet package for the version of Puppy you have. But you have not told us which it is. Be aware that the 3G_pupdial-wireless-13.pet package is only for puppies 4.2 and older, and has not been maintained for a long time. Please do not use it.
The puppies I can help you with are 4.3.1 (plus an update package) and Lucid Pup 5.2.8. Lupu 5.2.8 should already support your 3G modem. You can get the very latest version of it here:
http://www.murga-linux.com/puppy/viewto ... 253#554253
If you are using "wary", the modem should also "just work" there. If you have trouble with the modem and lupu 5.2.8, please report that here, so I can work it.
Welcome to this thread.
Richard
Thank you for posting your problem here. I suspect you are using the wrong update dotpet package for the version of Puppy you have. But you have not told us which it is. Be aware that the 3G_pupdial-wireless-13.pet package is only for puppies 4.2 and older, and has not been maintained for a long time. Please do not use it.
The puppies I can help you with are 4.3.1 (plus an update package) and Lucid Pup 5.2.8. Lupu 5.2.8 should already support your 3G modem. You can get the very latest version of it here:
http://www.murga-linux.com/puppy/viewto ... 253#554253
If you are using "wary", the modem should also "just work" there. If you have trouble with the modem and lupu 5.2.8, please report that here, so I can work it.
Welcome to this thread.
Richard
Richard,
Thank you very much for trying to help me.
I really would like to be using this Puppy because it is incredible.
So, my Puppy is Lupu 5.2.8
I'm going to follow your advice. I'm using this O.S since tow weeks ago. Before I was using Debian Squeeze wich is also very good.
I really apreciate your work.
Thank you one more time.
Best wishes
Hernâni
Thank you very much for trying to help me.
I really would like to be using this Puppy because it is incredible.
So, my Puppy is Lupu 5.2.8
I'm going to follow your advice. I'm using this O.S since tow weeks ago. Before I was using Debian Squeeze wich is also very good.
I really apreciate your work.
Thank you one more time.
Best wishes
Hernâni
Modem 3g
Richard,
I did everything that you said for me to do, but with no success. Lupu 5.2.8.003 doesn't solve the problem. The modem is recognized but the connection hangs up allways.
The error message is this:
WvDial: Internet dialer version 1.53
Initializing modem.
Sending: ATZ
ATZ
OK
Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
Sending: AT+CGDCONT=1,"IP","internet.tmn.pt"
AT+CGDCONT=1,"IP","internet.tmn.pt"
OK
Modem initialized.
Sending: ATDT*99#
Waiting for carrier.
ATDT*99#
CONNECT
Carrier detected. Starting PPP immediately.
Starting pppd at Mon Dec 5 13:50:14 2011
pid of pppd: 2156
Disconnecting at Mon Dec 5 13:50:19 2011
The PPP daemon has died: A modem hung up the phone (exit code = 16)
man pppd explains pppd error codes in more detail.
Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
I would apreciate any help.
Thank you very much
Hernâni
I did everything that you said for me to do, but with no success. Lupu 5.2.8.003 doesn't solve the problem. The modem is recognized but the connection hangs up allways.
The error message is this:
WvDial: Internet dialer version 1.53
Initializing modem.
Sending: ATZ
ATZ
OK
Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
Sending: AT+CGDCONT=1,"IP","internet.tmn.pt"
AT+CGDCONT=1,"IP","internet.tmn.pt"
OK
Modem initialized.
Sending: ATDT*99#
Waiting for carrier.
ATDT*99#
CONNECT
Carrier detected. Starting PPP immediately.
Starting pppd at Mon Dec 5 13:50:14 2011
pid of pppd: 2156
Disconnecting at Mon Dec 5 13:50:19 2011
The PPP daemon has died: A modem hung up the phone (exit code = 16)
man pppd explains pppd error codes in more detail.
Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
I would apreciate any help.
Thank you very much
Hernâni
Question
Hi.
I've got ZTE USB modem too and using Wary Puppy 5.2.2
I have to say that after probing several times finnally I could access to internet on the first day I installed Puppy.
BUT two days after... and with no changes in the system at all, I'm getting a "bad init string" error.
Because of I considered myself a "lucky guy", I saved the "succesful" configuration of when I coud access to internet.
I attached that .png image.
But now...
Initializing modem.
Sending: ATZ
ATZ
OK
Sending: ATQ0 V1 E1 +FCLASS=0
ATQ0 V1 E1 +FCLASS=0
OK
Sending: AT+CGDCONT=1, "IP", "adslmovil"
AT+CGDCONT=1, "IP", "adslmovil"
ERROR
Bad init string.
How can it be?
How can i fix?
Thanks!
I've got ZTE USB modem too and using Wary Puppy 5.2.2
I have to say that after probing several times finnally I could access to internet on the first day I installed Puppy.
BUT two days after... and with no changes in the system at all, I'm getting a "bad init string" error.
Because of I considered myself a "lucky guy", I saved the "succesful" configuration of when I coud access to internet.
I attached that .png image.
But now...
Initializing modem.
Sending: ATZ
ATZ
OK
Sending: ATQ0 V1 E1 +FCLASS=0
ATQ0 V1 E1 +FCLASS=0
OK
Sending: AT+CGDCONT=1, "IP", "adslmovil"
AT+CGDCONT=1, "IP", "adslmovil"
ERROR
Bad init string.
How can it be?
How can i fix?
Thanks!