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.

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.

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.

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.

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

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

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

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.

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.

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

modem_fix_pack_delta-7.2_to_7.4.pet

Description

Improvements to pupdial and its friends for modem detection and control of alternative ttyUSB devices.

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

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.

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 ''

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