Dialup/Wireless Modem Upgrade Packages for Puppy 4.3+

Message
Author
tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#161 Post by tempestuous »

Yes, I was about to suggest the same as rerwin did.
There's an overlapping range of drivers for Agere/Conexant/Lucent winmodems, and by blacklisting the "agrserial" driver, you will give Puppy a chance to auto-load another driver.
I still suspect that the correct driver will be "hsfhda".

benny7440, in the interests of diagnosis, I suggest that once you have blacklisted the agrserial module and have rebooted, you then run the "lsmod" command and take note of what winmodem driver Puppy has loaded.

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#162 Post by rerwin »

tempestuous wrote:There's an overlapping range of drivers for Agere/Conexant/Lucent winmodems, and by blacklisting the "agrserial" driver, you will give Puppy a chance to auto-load another driver.
I still suspect that the correct driver will be "hsfhda".
Good point. I just now checked the linuxant web site for AC97 devices supported by the HSF drivers and found that 8086 27d8 is not on the list. Even if it were, I am not convinced that Barry included the linuxant ALSA patch to the snd-hda-intel driver before compiling it, so the HSF HDA modems might not be supported.

benny7440,
To help us sort out ways of determining which of the three possible drivers to use, could you collect some diagnostic data for me? If you have the choice, please use wary 5.1.2, to be sure all the latest modem fixes are there.

1. First, after booting up and getting ttyS_AGS3 detected, then attempting to use it, please run in a console the command, pmodemdiag. That produces a so-named tar.gz file in your main/root directory. Please post that file as an attachment or PM it to me. You could rename it to append "-ttyS_AGS3" to the original name (before the ".tar.gz).

2. Then, after creating the blacklist conf file, rebooting and going as far as you can toward connecting, run pmodemdiag again and change the file name to add whatever device name was detected.

I hope to find something in the message log that might help identify which driver to use. I am seeking the best way to automatically handle the driver ambiguity. That begins by knowing what happens and when. Thanks for any help you can provide to that end.
Richard

User avatar
benny7440
Posts: 440
Joined: Mon 20 Apr 2009, 04:23

#163 Post by benny7440 »

Thanks for responding, tech_jnke2! Thanks also for the DSL comparison; even though I've a stick with it nearby, never have used it in this notebook: it simply won't finish booting up. Guess it's something related to the BIOS this machine uses.

To the other guys {rewin & tempestuous}: today I booted up with PL511 & was using FF 5.0. For some unknown reason the hdd led was lit every 5-10 mins for almost 3 mins, at a time. In addition to that, even a java script was stuck every now & then, consuming a lot of cpu capacity & making FF unresponsive. I resorted to restart the JWM once & it worked a little bit better but just for about 3-4 mins. I then resorted to restart the X server & this worked fine.

Now, I don't have any other choice for dealing with the next issue: a heavy thunderstorm is approaching & need to disconnect everything to protect the equipment. I'll give your commands & tricks a chance after I get online again maybe tonight or tomorrow. Thanks again for your help!

Shep
Posts: 878
Joined: Sat 08 Nov 2008, 07:55
Location: Australia

#164 Post by Shep »

benny7440 wrote: I booted up with PL511 & was using FF 5.0. For some unknown reason the hdd led was lit every 5-10 mins for almost 3 mins, at a time. In addition to that, even a java script was stuck every now & then, consuming a lot of cpu capacity & making FF unresponsive.
If you survive the thunderstorm, try clearing your browser cache. Just in case you have a lot of big files filling it.

And if you didn't survive the storm? Well, .... R.I.P. :twisted:

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#165 Post by tempestuous »

rerwin wrote:I am not convinced that Barry included the linuxant ALSA patch to the snd-hda-intel driver before compiling it, so the HSF HDA modems might not be supported.
Mmm, that's interesting. I have lost touch with Linux winmodem driver development, but I see that quite a few changes have happened since Dell made the HSF driver source available for free.
I just downloaded the HSF driver source from Barry's repository -
http://bkhome.org/sources/kernel-2.6.32 ... rid.tar.gz
and the README has this:
HDA (High Definition Audio) Modems
Only under 2.6.16 or newer kernels

HDA VENDOR ID 14F12BFA
HDA VENDOR ID 14F12C06

We recommend the installation of alsa-driver-linuxant available at http://www.linuxant.com/alsa-driver before installing this driver if you have a HDA modem.
So this means the snd-hda-intel patch is recommended, but not essential??

I have the Wary 5.1.1 CD on hand, so I just booted it to see that it contains ALSA 1.0.21 (which is the same ALSA version in Lucid 5.1/5.2). So the correct patch would be "alsa-driver-1.0.23-1.patch" from
http://www.linuxant.com/alsa-driver/

I don't have the kernel source for Wary, so I can't check to see if this patch has been applied.
But just for kicks, I checked the patch against the kernel source for Lucid 5.1/5.2 and I can definitely say that this patch has not been applied there.

Could someone with the Wary kernel source check to see if this patch has been applied? (# patch --dry-run ...)
It seems to me that if Wary contains the HSF driver, the ALSA patch would be an important inclusion ...
maybe we should check with Barry?

User avatar
benny7440
Posts: 440
Joined: Mon 20 Apr 2009, 04:23

#166 Post by benny7440 »

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.

TIW
Posts: 71
Joined: Thu 14 Apr 2011, 21:40

Dialup/Wireless 3G Modem

#167 Post by TIW »

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

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#168 Post by tempestuous »

benny7440,
the technical issues I raised are for the consideration of rerwin and other developers.

All you need to do is follow rerwin's suggestions regarding "pmodemdiag".

Shep
Posts: 878
Joined: Sat 08 Nov 2008, 07:55
Location: Australia

Re: Dialup/Wireless 3G Modem

#169 Post by Shep »

[quote="TIW"]I tried to connect with “Internet by wireless GPRS modem

Shep
Posts: 878
Joined: Sat 08 Nov 2008, 07:55
Location: Australia

#170 Post by Shep »

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.
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! :oops: :oops:

User avatar
benny7440
Posts: 440
Joined: Mon 20 Apr 2009, 04:23

#171 Post by benny7440 »

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
#

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#172 Post by rerwin »

benny7440,
Sorry to be so long in responding to your posting. Lots of distractions. And, yesterday and today, some research time on this.
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).
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.

- 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 1287 times
agrsm_fix-2.pet
blacklists agrsm drivers
(535 Bytes) Downloaded 1273 times

User avatar
benny7440
Posts: 440
Joined: Mon 20 Apr 2009, 04:23

#173 Post by benny7440 »

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/.
#

User avatar
tech_jnke2
Posts: 10
Joined: Sun 21 Mar 2010, 07:19

#174 Post by tech_jnke2 »

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.

User avatar
benny7440
Posts: 440
Joined: Mon 20 Apr 2009, 04:23

#175 Post by benny7440 »

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.

User avatar
benny7440
Posts: 440
Joined: Mon 20 Apr 2009, 04:23

#176 Post by benny7440 »

Addendum: Can that option of <pfix=ram> be included in the menu.lst file for the first boot? It occurred to me today that it might be an option but never have tried that.

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

ModeSwitcher update to usb-modeswitch-1.1.9-20110805

#177 Post by rerwin »

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:
  • 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.
New hardware IDs supported:
  • 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
A configuration file for ID 0471:1210 is deleted for the Vodafone MD950 (Wisue Technology). Apparently, its switching method was incorrect.

If your system would not benefit from this update, it can be skipped.
Richard

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

modem-modprobe package updated to 2011905

#178 Post by rerwin »

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

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

ModeSwitcher update to usb-modeswitch-1.2.0-20111023

#179 Post by rerwin »

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:
  • 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
New hardware IDs supported:
  • 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)
If your system would not benefit from this update, it can be skipped. Do not use this update on wary 5.2, because its service pack already contains it and should be used, instead.
Richard

Hernâni
Posts: 8
Joined: Tue 29 Nov 2011, 11:14

Can't connect Modem ZTE MF628

#180 Post by Hernâni »

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

Post Reply