Dialup/Wireless Modem Upgrade Packages for Puppy 4.3+

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

#31 Post by rerwin »

Toy4,
Sorry for the delay in responding. I am afraid I have bad news. The phone number you are using looks like what you would use when dialing from a land-line phone to get to an ISP. From what I have seen, the wireless modems use the cell phone systems, which apparently have their own way of providing data services. So, I don't think you can do what you are trying. As I mentioned before, the number most people use is some variant of #99*. I have also seen a number like 777, but certainly not a 10-digit number as used for voice calls.

I guess your options are to:
- Augment your cellular account to add data services.
- Use your analog modem (built-in, PCI card, PCcard) if you have one.
- Obtain a USB analog modem (SmartLink- or Conexant DGC-based)
Richard

User avatar
Toy4
Posts: 50
Joined: Sun 27 Jun 2010, 16:14
Location: Pedley, CA USA

modem_fix_pack_delta-7-to-7.2.pet& modem_7.1_debug installed

#32 Post by Toy4 »

It is back to having attitude problems. It looked like it was going to work then a bunch of new ugly messages showed near where it paused last time then worked. This time it paused and then buckled. I have attached the most current diag file.
Asus EeePc 900A w/Puppeee1.0 with 3G modem (Sierra 598U)
AMD Duron 797Mhz w/Puppy4.31 & Puppy2.14& Puppy4.20
Dell Dimension 2350 w/Quirky1.20Retro & Lucid Puppy5.10& Wolfe020

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

modem_fix_pack_delta-6-to-7.2.pet connect wizard fixed

#33 Post by rerwin »

I have fixed the problem reported in Barry's blog
Posted on 8 Aug 2010, 16:20 by BarryK
script broken
Please do not apply modem_fix_pack_delta-6-to-7.2.pet in any Puppy greater than 4.x, as it breaks network setup.

The script /usr/sbin/connectwizard is overwritten with a very old version.

I will contact rerwin about this and he will post an upgrade for the PET.
That package has been re-uploaded with better implementation of the modem message changes. More details are given in the update in the first message of this thread.

In addition, I have upgraded the usb-modeswitch data base (to 7/7), to add 6 wireless devices:

Code: Select all

0421:060c - Nokia CS-10
0cf3:20ff  -  Atheros Wireless / Netgear WNDA3200
12d1:1031 - for Android SDK
12d1:14c1 - Vodafone (Huawei) K4605
12d1:1523 - Huawei R201
1ee8:0013 - Onda MW833UP
There is no need to replace your data base unless your wireless device has one of the listed hardware IDs.
Richard

User avatar
Toy4
Posts: 50
Joined: Sun 27 Jun 2010, 16:14
Location: Pedley, CA USA

Modem not working

#34 Post by Toy4 »

When I last installed those 2 files you requested the modem stopped working. I saw that you said the modem_fix_pack_delta-6-to-7.2.pet that I installed was screwed up and should be removed. I removed and downloaded the newer one. Now my modem isn't detected at all. I am sending you a diag file to see anything sticks out. Please advise.
Asus EeePc 900A w/Puppeee1.0 with 3G modem (Sierra 598U)
AMD Duron 797Mhz w/Puppy4.31 & Puppy2.14& Puppy4.20
Dell Dimension 2350 w/Quirky1.20Retro & Lucid Puppy5.10& Wolfe020

User avatar
Toy4
Posts: 50
Joined: Sun 27 Jun 2010, 16:14
Location: Pedley, CA USA

Still having troubles with Puppeee Version 1.0

#35 Post by Toy4 »

After I installed version 1.0 of Puppeee and with a new save file. Now, I got nothing. I don't have Wlan so I am attaching this file from a Windows(sic) computer. This maybe that same as the one you got the other day. I can't get the 3G modem to show up. Boot with it in and probed it and nothing. It doesn't even show up.
Asus EeePc 900A w/Puppeee1.0 with 3G modem (Sierra 598U)
AMD Duron 797Mhz w/Puppy4.31 & Puppy2.14& Puppy4.20
Dell Dimension 2350 w/Quirky1.20Retro & Lucid Puppy5.10& Wolfe020

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

Code correction for wireless modem support

#36 Post by rerwin »

I have discovered a coding error in the magic logic that ensures that wireless modem drivers get loaded. Although the error may not affect all such modems, I cannot let it stand. The fix is in the attached package.

The package also addresses an issue uncovered by puppeee 1.0. The file that relates drivers to firmware is named to match the kernel name. However, puppeee uses two such names, but has the file named without the kernel part. Although there may be cases where different versions of the file are needed, much of the time the file is the same for all kernels used in a puplet or derivative. For cases like puppeee, I have added logic to create a link to the "generic" (non-kernel identified) file name, so developers need not attend to the naming unless a special version of the file is needed. The logic is in the package as an edit of rc.sysinit, so should apply to any version of rc.sysinit.

The package also includes a debug statement that I intend to remove (and re-upload the package) when I am convinced all is well. (I cannot completely test the magic myself, so need the debug info from actual wireless-modem users.)

UPDATE: Re-uploaded the package (after download number 10) with a different way of ensuring the correct firmware.dep file, by renaming it instead of creating a link. This is to avoid complicating the version-update process. There is no need to re-download it for testing, though, as the effect is the same as before.

UPDATE 8/28/2010: Uploaded "5.4" which improves the waiting for all firmware to load, particularly where a module substitution is made.
Richard
Attachments
pup_event_backend_modprobe_fix_to_p43x-delta_5.2_to_5.4.pet
Fixes wireless modem error. Ensures correct firmware.dep file.
(7.84 KiB) Downloaded 1451 times
Last edited by rerwin on Sat 28 Aug 2010, 03:47, edited 2 times in total.

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#37 Post by BarryK »

Richard,
The latest Woof supports logging of monthly tx/rx totals. Reported here:

http://bkhome.org/blog/?viewDetailed=01758

I posted a comment to that blog thread outlining how support for monthly logging could be built into pupdial.
[url]https://bkhome.org/news/[/url]

User avatar
Toy4
Posts: 50
Joined: Sun 27 Jun 2010, 16:14
Location: Pedley, CA USA

Verizon USB760 Modem now works

#38 Post by Toy4 »

I was instructed to install pup_event_backend_modprobe_fix_to_p43x-delta_5.2_to_5.3.pet that rerwin just created that would fix the recent modem and network issues. Well, I created another copy of Puppeee1.0 on my Netbook and added the pet package and rebooted numerous times. The only browser on 1.0 is chrome and while the 3G and the networks appeared to be working i wasn't able to properly test them.
I tried again later and now I can get chrome to load web pages and have verified that the modem works with the update on a clean install of Puppeee1.0... Many thanks to Rerwin for this.
Asus EeePc 900A w/Puppeee1.0 with 3G modem (Sierra 598U)
AMD Duron 797Mhz w/Puppy4.31 & Puppy2.14& Puppy4.20
Dell Dimension 2350 w/Quirky1.20Retro & Lucid Puppy5.10& Wolfe020

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

pupdial support of tx/rx accumulated monthly

#39 Post by rerwin »

Barry,
Attached is my implementation of tx/rx accumulation by pupdial. I collect separately for each of the two possible accounts, but provide a link for the reporting tool to access the active account values.

The files for rc.sysinit to initialize are:
- /var/local/pupdial/isp1/rx_bytes_month
- /var/local/pupdial/isp1/tx_bytes_month
- /var/local/pupdial/isp2/rx_bytes_month
- /var/local/pupdial/isp2/tx_bytes_month

The link for reporting the current ISP values is:
- /var/local/pupdial/isp

The package sets these up for testing, but there is no report program, yet. This provides a test case for whomever codes the reporter. A difference file is also attached.

Toy4,
This also has an updated modem script for you to try with puppeee 1.0. Your diag file indicates the detection logic is not adequate, so I added debug logging. Also, the diag file did not show your actually connecting with the modem. Could you wait until you are connected before you run pmodemdiag, so I can be sure all the pieces are playing right? Just install it on top of what you have, "CHOOSE > ERASE" in pupdial, then reboot. Thanks.

UPDATE 8/22/2010: Uploaded delta to 7.4, which has an improved statistics collector and improvements and debug info for USB modem detection and some troubleshooting.

UPDATE 8/23/2010: Re-uploaded 7.4 with fixes and possible workaround for ttyUSB connect failure - after download number 3.

UPDATE 8/24/2010: Re-uploaded 7.4 with debugging of puppeee modem problem - after download number 6.
Richard
Attachments
modem_fix_pack_delta-7.2_to_7.4.pet
statistics-accumulating pupdial and usbserial debugging
(20.96 KiB) Downloaded 1294 times
diff-pupdial.tar.gz
pupdial difference listing - Shows the new code, but it is now moved to a new script,
modemdisconnect, because it is needed in 2 places in pupdial.
(1.14 KiB) Downloaded 1290 times
Last edited by rerwin on Wed 25 Aug 2010, 02:44, edited 4 times in total.

User avatar
Toy4
Posts: 50
Joined: Sun 27 Jun 2010, 16:14
Location: Pedley, CA USA

pet you requested was added

#40 Post by Toy4 »

I don't think I used pupdial yesterday and I don't think it went there. I clicked connect and then a window for gnome ppp showed up and i used that and it connected and showed a countdown of how long I was connected and it was 45:00. I just tried that again and it didn't work today. Went back and did Pupdial again but both of these will not show in the pmodemdiag file as it was taken right after I installed the fix and rebooted. Pupdial doesn't really show that I am connected but I am typing an entry in the forum and that can't be happening if the modem isn't connected. OK, here comes your file.
Asus EeePc 900A w/Puppeee1.0 with 3G modem (Sierra 598U)
AMD Duron 797Mhz w/Puppy4.31 & Puppy2.14& Puppy4.20
Dell Dimension 2350 w/Quirky1.20Retro & Lucid Puppy5.10& Wolfe020

User avatar
Toy4
Posts: 50
Joined: Sun 27 Jun 2010, 16:14
Location: Pedley, CA USA

modem touch up

#41 Post by Toy4 »

Didn't look like that found a device when it did the diagfile, but pupdial window is still open and modem is working fine.
I am attaching that file now. later, Off to work, thought i'd get you this before I left. Saw you on late last night then you left and when I came on to check this morning there was a PM waiting.
Asus EeePc 900A w/Puppeee1.0 with 3G modem (Sierra 598U)
AMD Duron 797Mhz w/Puppy4.31 & Puppy2.14& Puppy4.20
Dell Dimension 2350 w/Quirky1.20Retro & Lucid Puppy5.10& Wolfe020

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

#42 Post by rerwin »

This package improves modem detection and the support of alternative devices. If your wireless modem uses a device number other than ttyUSB0, you can try other ttyUSB devices by clicking on the ttyUSB1 (or 2 or 3, etc.) button to test that name. (It is only one button, but its name changes as you test the various names.) If successful, that device will become "selected", otherwise the selected device will be unchanged.

This also works with ttyACM and ttyHS devices. In addition, pupdial is shrunken a little to better fit small screens. The connect button changes are from jemimah.

UPDATE: Re-uploaded the package (after download number 7) with a rearranged pupdial selection/probe window to fit the most-used control buttons into a 480-pixel-tall display (after jemimah pointed out the problem to me). It has no functional changes.
Richard
Attachments
modem_fix_pack_delta-7.2_to_7.4.pet
Improvements to pupdial and its friends for modem detection and control of alternative ttyUSB devices.
(17.27 KiB) Downloaded 1418 times

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

Upgrades consolidated!

#43 Post by rerwin »

The above three pup_event and modem "delta" packages are now merged into the consolidated packages at the beginning of this thread. I have removed the "BETA" designation, as I have received no recent problem reports requiring fixes.

However, I am grateful to Toy4 for his assistance in testing my changes, as part of troubleshooting his installation of puppeee 1.0. Although he was eventually successful, our process involved verifying my changes and now gives me the confidence to publish what I hope is the final product, with respect to its functionality and "look and feel". Ongoing maintenance will be necessary to keep up with the usb_modeswitch utility as it evolves.

As a follow-on, I plan to post a "service pack 4.3.1.1" that includes these upgrades as well as some of the fixes posted in the 4.3.1 Bugs thread. That is intended for users starting out with 4.3.1, to make some improvements so they do not run into the same old problems that have long been solved (informally) . That will be in a new thread.

I hope that anyone still having difficulty with their modem will post here with the details, so I can assist.
Richard

Fabio T
Posts: 90
Joined: Fri 31 Aug 2007, 20:33
Location: Italy

Difficult in detecting HSDPA modem

#44 Post by Fabio T »

I have got a new brand Sony Vaio VGN-TT46XG with Sony EveryWair interface, that is in reality an OPTION Globetrotter module (it seems a GTM382W) vendor=0x0af0 product=0x7601.
With Puppy 4.3.1., specially with Quirky 1.20 retro (kernel 2.6.30.5) , modem is correctly responding and connecting, with advanced kerneks modem is invisible to Puppy (and not works).
In the other hand, same advanced kernel (2.6.33) can see an OPTION Globetrotter vendor=0x0af0 product=0x6901 on an ASUS notebook....
Any ideas?
Perhaps the upgrades posted in this thread can help, or need to wait a further kernel upgrade?
Thanks.

gortonc
Posts: 39
Joined: Tue 12 Jan 2010, 16:05
Location: Costa Rica

Success!

#45 Post by gortonc »

Richard,

Thanks so much for all the time you have devoted to this project. I have been thrilled with the performance of 5.1003 on my Compaq Presario V2000 with one minor annoyance. My Huawi usb 3g modem would only work after a minimum of 2, and sometimes 4 attempts at probing and or erasing modules. After adding the 4 new pets it connects flawlessly the first try. Congratulations, and thanks again ':D'

Chris

User avatar
Toy4
Posts: 50
Joined: Sun 27 Jun 2010, 16:14
Location: Pedley, CA USA

Failed to get online

#46 Post by Toy4 »

Hey, new failure to document. I was at my bank and tried to get online to access a website and it wouldn't work. OK, I am not sure what actually happened at that point. This modem never does tell you (in pupdial) that it is actually working so you have to guess it is and try it. OK, well I tried and it was working very well since that last issue. So, I don't know if it couldn't find a tower to connect to or if I tried too early before it was connected or what. When I tried it again in an area I know that I have success it told me that the daemon died (again). I booted up into my test system and mounted that save=file and went into etc/ppp/peers and removed those two files and rebooted and I am on without incident. I just checked the peers file and those 2 files are n there again so I have to assume they are OK in there and maybe they are removed on shutdown. It doesn't seem to connect when they are there. Like I mentioned before, I know how to clear the problem up I just don't understand what triggered it and what the story is with those two files and why they seem to cause it to not connect. I have attached the diag file.
Asus EeePc 900A w/Puppeee1.0 with 3G modem (Sierra 598U)
AMD Duron 797Mhz w/Puppy4.31 & Puppy2.14& Puppy4.20
Dell Dimension 2350 w/Quirky1.20Retro & Lucid Puppy5.10& Wolfe020

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

Modem Fix Pack 8 Available

#47 Post by rerwin »

Modem users,
I have uploaded a "cleaned up" version of the modem and modprobe improvement packages to the first page of this thread. If you have been keeping up with these updates for the puppy 4.3+ series, you can install the attached "7.2_to_8" package instead of the "6_to_8" package posted there. Be sure to also install the pup_event_backend_modprobe fix 5.5 package, preferably first.

If you use "6_to_8" on a newly installed frugal puppy that does not yet have a pupsave file, please wait until a reboot before installing it. This is necessary because the /var/local pieces do not get saved if a pupsave is not being used.

Some details of the internal changes: I have replaced some of my "improvised" logic with more "mainstream" coding.

1. I utilize the /etc/modprobe.d directory for any changes to the modprobe.conf file (for modems and sound cards). I have eliminated the /etc/modprobe_includes directory and have changed blacklist processing to include any blacklists in /etc/modprobe.d. This should facilitate changeover from the modprobe.conf file to moving its contents to modprobe.d files (although I did not actually do that).

2. I simplified maintenance of usb_modeswitch support by replacing the /etc/usb_modeswitch.d directory with a tarball of its contents. The tarball's name includes its version as the date of its release (-yyyymmdd). If multiple such files are present, the one with the latest date is used.

3. In response to a report by smokey01 that his wireless modem did not work in the latest fluppy, I noted that the modem was already switched to modem mode, so no modeswitching was done. With the earlier fluppy, the modem had to be switched, and then it worked. His case involves the "vodaphone workaround" for modems not recognized automatically. The script for that, pmodprobeoption, seemed to do the right things but the modem still was not "detected" appropriately. I have reviewed that script and have revised it to handle a flood of invocations that were not being serialized to prevent interference. Smokey01, please try this both with and without the modem having been switched.

4. As provided in the latest version of woof, I have added collection of traffic statistics similar to those for the "sns" networking connections. I expect someone else to add the values to the appropriate reporting scripts/programs.

5. In response to a continuing issue with Agere 8086:1040 PCI modems, I reviewed the "agrsm" driver package and made some changes. This modem is not "seen" by the linux driver, so requires that the drive be force-loaded. That revealed a bug with such a situation, as well as a missing part of agrsm support. Now, only "agrmodem" need be added to the list of modules to load at bootup (specified with the BootManager), since agrserial is an undeclared dependency that is now handled internally. This fix should also benefit any Agere modem that uses the "agrsm" driver -- without needing to force its loading (other than the 8086:1040).

UPDATE 9/23/2010: Re-uploaded package with patch to wireless modem detection, after download number 6.

UPDATE 10/3/2010: Re-uploaded package after download number 20, with verified corrections to wireless modem detection, incorporated from "patch-2" (so no need to install that patch).
Richard
Last edited by rerwin on Sun 03 Oct 2010, 19:49, edited 1 time in total.

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#48 Post by 01micko »

Hello Richard

I am having fatal issues with your latest packages with my hardware.

I have the Huawei e169 that is now approaching 2 years old trying on my X2 AMD dual core, 2GB RAM, nvidia chipset on motherboard. The issues are with Quirky-1.30 (Barry's latest) and lupu-511 and the latest dev branch of that luma-002, but the latter 2 don't include your latest packages so the packages are installed manually.

What happens is that the mode switching seems to occur just fine, though I have to load 'option' manually in lupu and luma, which is a system problem and beyond the help you provide here, so that's not the issue. I then probe the modem and it shows up as ttyUSB0, fine, then I try to connect with my usual settings and it initialises, and at the APN string it errors with 'bad init string'. Ok, so I tried changing the string manually same thing.

Now, if I try to test the modem by clicking on the 'ttyUSB0' button I get a complete system freeze, same behaviour in all three OS> qrky, lupu, luma. This is reproducable 100% of the time. It's possible that it's HW related at my end because this system is only a couple of months old and I have never used the modem with it.. the last time I used the modem was 3 months ago in lupu-500and Puppeee (by jemimah) on my eee 701SD and it worked fine OOTB.

If you want me to attach logs I can do so, but it might be a kernel issue, not sure.

I'll do some testing of the modem to make sure it still works, it is surely possible that it has failed.

Cheers
Puppy Linux Blog - contact me for access

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#49 Post by 01micko »

:oops: :oops: :oops:

Hello Richard..

I tested on another machine running widows xp and the modem worked, but, I got 'sim not inserted' error. This is probably because of corrosion ( I live on the coast in a warm moist climate) so I pulled the sim and cleaned it, booted to lupu-510 (which resides on this machine) and I was online in a matter of seconds.

That explains the 'bad init string' error. I'll test further on my main machine to see if I can reproduce the crash.

Perhaps when the sim card is not inserted you could append a line to the output that says, "check sim card insertion" or something to idiot proof the prog for dummies like me!

Cheers!

EDIT:
Results
luma-002 Opened pupdial on main machine, settings were already in place from previous experiments, clicked connect, online in 2 seconds, your packages uninstalled

qrky-130 Worse, now crashing as soon as I open pupdial

lupu-511 Not connecting, can still reproduce crash, your packages installed. NOTE: seem to experiencing network issues, this happens often, could be why it's not connecting, more on that one, and a log later.
Puppy Linux Blog - contact me for access

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

#50 Post by rerwin »

I am back, now, after a mini vacation away from computers. In response to Barry's report of an issue with his APN, I have discovered a recent bug in pupdial that skips processing of both the APN and PIN. I think I have that corrected in the attached patch package.

Anyone getting the "no carrier" problem might try this, in case the APN setting is the cause.

UPDATE 9/30/2010: Added patch-2 to fix the problematic modem detection for ttyUSB modems. Someone please try this and send me a pmodemdiag file, so I can verify the fix works. I cannot test with a real ttyUSB device, but have with a device that uses ttyACM. The logic is similar. You should see fewer alternatives, since only likely prospects are found, usually only one.
Richard
Attachments
modem_fix_pack_8-patch-2.pet
pupdial APN/PIN fix plus correction of modem detection accuracy
(39.08 KiB) Downloaded 852 times
modem_fix_pack_8-patch-1.pet
pupdial APN/PIN fix
(7.87 KiB) Downloaded 854 times

Post Reply