Running usb_modeswitch with the ZTE636 (by uncommentning the second instance of ZTE636 in the udev rule) only detaches it from usb_storage. This makes it impossible to run the eject trick (ejecting the CD that shows up if you jut plug in and waits) since no CD will show up.
This means, so far, that the ZTE636 can be made usable only by:
either
1) disabling the CD autorun via hyperterminal in windows
or
2) ejecting the CD that turns up if you just plug in the modem
to dejan555: if the 626 is like the 636,maybe it could be useful to try to not uncomment anything( not run usb_modeswitch, and then try the eject method, and then try different ports (ttyUSB2? ttyUSB3?)
Integration of 3G Wireless Modem Detection - 4.1.2 & 4.2.1
Kark,
When you run usb_modeswitch from a console, does it report an "error -110"? That is what Wilky sees with his MF626, along with a bunch of other messages, I assume error messages.
I am stumped at that point. You could also use the "-W" argument to get feedback on the device IDs in play.
Richard
When you run usb_modeswitch from a console, does it report an "error -110"? That is what Wilky sees with his MF626, along with a bunch of other messages, I assume error messages.
I am stumped at that point. You could also use the "-W" argument to get feedback on the device IDs in play.
Richard
Last edited by rerwin on Sat 02 May 2009, 18:50, edited 1 time in total.
-
BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Well Ubuntu Jaunty Puppy alpha6 is available, with rerwin's '-9' patches.
http://puppylinux.com/blog/?viewDetailed=00702
As this uses the 2.6.29.1 kernel, it may need some changes. Note alpha7 will have the 2.6.29.2 kernel, then hopefully we will stay with that for sometime.
Note, the 'pctel' module may load when it shouldn't and on certain hardware you may have to blacklist it. will fix for alpha7.
http://puppylinux.com/blog/?viewDetailed=00702
As this uses the 2.6.29.1 kernel, it may need some changes. Note alpha7 will have the 2.6.29.2 kernel, then hopefully we will stay with that for sometime.
Note, the 'pctel' module may load when it shouldn't and on certain hardware you may have to blacklist it. will fix for alpha7.
[url]https://bkhome.org/news/[/url]
OK, like I said I installed those pets rerwin said patched usb-storage, option, usb_switch etc. and since ZTE626 doesn't show up as storage drive anymore so I can't do that eject tip. When I run usb_modeswitch it doesn't show that error, it says it found default device and when I look into /proc/bus/usb/devices it shows the right vendor and id.
So then I do modprobe usbserial vendor=0x19d2 product=0x0031
Then I enter /dev/usb/ttyUSB1 manually in wvdial.conf 'cause pupdial doesn't recognize it and then I start wvdial from CLI. It shows that modem is initialized, all init lines show OK, and when it comes to ATDT dial command it disconnects. After that modem is not longer recognized as /dev/usb/ttyUSB1, little LED indicator on it switches off and I have to unplug it then plug it back in and do modeswitch again for it to be recognized.
So then I do modprobe usbserial vendor=0x19d2 product=0x0031
Then I enter /dev/usb/ttyUSB1 manually in wvdial.conf 'cause pupdial doesn't recognize it and then I start wvdial from CLI. It shows that modem is initialized, all init lines show OK, and when it comes to ATDT dial command it disconnects. After that modem is not longer recognized as /dev/usb/ttyUSB1, little LED indicator on it switches off and I have to unplug it then plug it back in and do modeswitch again for it to be recognized.
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
I'm not an expert, rather fresh actually, but since we seem to have approximately the same modem...
I couldn't get my one to work with wvdial before I'd run the pgprs-connect once, and I also had the problem of the modem being made unusable by wvdial and I had to unplug and replug, so now I only use pgprs.
So: 1) does the same thing happen with pgprs as well?
2) Have you tried the option module? At the stage where you are, the modem actually being recognized as modem, my puppy automatically loads option.
I couldn't get my one to work with wvdial before I'd run the pgprs-connect once, and I also had the problem of the modem being made unusable by wvdial and I had to unplug and replug, so now I only use pgprs.
So: 1) does the same thing happen with pgprs as well?
2) Have you tried the option module? At the stage where you are, the modem actually being recognized as modem, my puppy automatically loads option.
dejan555 wrote:OK, like I said I installed those pets rerwin said patched usb-storage, option, usb_switch etc. and since ZTE626 doesn't show up as storage drive anymore so I can't do that eject tip. When I run usb_modeswitch it doesn't show that error, it says it found default device and when I look into /proc/bus/usb/devices it shows the right vendor and id.
So then I do modprobe usbserial vendor=0x19d2 product=0x0031
Then I enter /dev/usb/ttyUSB1 manually in wvdial.conf 'cause pupdial doesn't recognize it and then I start wvdial from CLI. It shows that modem is initialized, all init lines show OK, and when it comes to ATDT dial command it disconnects. After that modem is not longer recognized as /dev/usb/ttyUSB1, little LED indicator on it switches off and I have to unplug it then plug it back in and do modeswitch again for it to be recognized.
1) Yes, same thing happens with pgprs-connect, it disconnects on same spot
2) I installed that option package, I thought it does something automatically at bootup or something like that, didn't try to load it manually, but when I try to remove usbserial module with rmmod usbserial it says "usbserial is in use by option" so I thought it's automatically loaded? How do I use that?
Thanks for your tips.
2) I installed that option package, I thought it does something automatically at bootup or something like that, didn't try to load it manually, but when I try to remove usbserial module with rmmod usbserial it says "usbserial is in use by option" so I thought it's automatically loaded? How do I use that?
Thanks for your tips.
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
Well, if your modem is the same as my one (it's got the same vendor and product id) then I guess the modprobe usb_serial should not be necessary. Once the switching actually has taken place, the option driver should be loaded, I think. That's what happens with my modem, What does pupscan say? It should say "VendorID=19d2 ProductID=0031 KERNEL-MODULE=option"
option depends on usb_serial, I think, so both are needed.
And IF we have the same modem, why not try /dev/ttyUSB3? where my one always comes up.
What do the expert say?
Kark
option depends on usb_serial, I think, so both are needed.
And IF we have the same modem, why not try /dev/ttyUSB3? where my one always comes up.
What do the expert say?
Kark
dejan555 wrote:1) Yes, same thing happens with pgprs-connect, it disconnects on same spot
2) I installed that option package, I thought it does something automatically at bootup or something like that, didn't try to load it manually, but when I try to remove usbserial module with rmmod usbserial it says "usbserial is in use by option" so I thought it's automatically loaded? How do I use that?
Thanks for your tips.
dejan555, Kark,
I'd like to clarify things about the drivers. This project supports the new drivers, which include option. I have not addressed usbserial except to provide an initialization script to set ttyUSB0. I support Kark's advice to use the option driver and not usbserial. Note, however, that option is dependent on usbserial, so your modprobing of it could be confusing things. Option should start automatically after a mode switch, but try modprobing it (no arguments) if it doesn't (or even forcing its loading in BootManager).
For now, i suggest commenting out the udev rule for the MF626/MF636, so that the modeswitch is not done at all. Then you should be able to "eject" the storage device to trigger the switching (as I understand what you or someone else did).
Regarding ttyUSB1, I have the impression that the modem is on ttyUSB2, according to some postings somewhere. I have not yet figured out a clean way to handle that in the initialization script (because most use ttyUSB0), but I need to.
Re dejan555's earlier post: This modem requires the patched versions of the option and usb_storage drivers, because they are they only versions that recognize its hardware IDs. (In addition to the 3G_pupdial and usb_modeswitch dotpets.)
Richard
I'd like to clarify things about the drivers. This project supports the new drivers, which include option. I have not addressed usbserial except to provide an initialization script to set ttyUSB0. I support Kark's advice to use the option driver and not usbserial. Note, however, that option is dependent on usbserial, so your modprobing of it could be confusing things. Option should start automatically after a mode switch, but try modprobing it (no arguments) if it doesn't (or even forcing its loading in BootManager).
For now, i suggest commenting out the udev rule for the MF626/MF636, so that the modeswitch is not done at all. Then you should be able to "eject" the storage device to trigger the switching (as I understand what you or someone else did).
Regarding ttyUSB1, I have the impression that the modem is on ttyUSB2, according to some postings somewhere. I have not yet figured out a clean way to handle that in the initialization script (because most use ttyUSB0), but I need to.
Re dejan555's earlier post: This modem requires the patched versions of the option and usb_storage drivers, because they are they only versions that recognize its hardware IDs. (In addition to the 3G_pupdial and usb_modeswitch dotpets.)
Richard
Thanks for clarifying things rerwin, regarding ttyUSB2, I don't have that device in /dev or /dev/usb/ , and it would be there if it was on that position right? I'll try with eject thing now.
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
rerwin
a link, which may give some insight
HTH
Aitch
a link, which may give some insight
http://www.murga-linux.com/puppy/viewto ... 4&start=15kayan wrote:@big_bass
Finally i can browse internet using my 3G Wireless Data Terminal ZTE MG478/AC8700 usb modem,in puppy using your Slaxer_Pup, by just editing WvDial Config.
but in all other puplets including Deep Though 4.2 ,modem not found was the standered error reported (even after editing WvDial Config)
Thanks !!!
HTH
Aitch
Aitch,
Thanks for directing me to information about the 3G Wireless Data Terminal ZTE MG478/AC8700 usb modem. I have looked into whether puppy supports it. No and yes.
Only the new 2.6.29 kernel in Puppy 5 will recognize it. But currently there is no usb_modeswitch item to effect the switch between its being a storage device and becoming seen as a modem. If you have such a modem and want to create the usb_modeswitch code for it, there is a way. So you could be ready for Puppy 5.
Richard
Thanks for directing me to information about the 3G Wireless Data Terminal ZTE MG478/AC8700 usb modem. I have looked into whether puppy supports it. No and yes.
Only the new 2.6.29 kernel in Puppy 5 will recognize it. But currently there is no usb_modeswitch item to effect the switch between its being a storage device and becoming seen as a modem. If you have such a modem and want to create the usb_modeswitch code for it, there is a way. So you could be ready for Puppy 5.
Richard
rerwin great you started this thread
lets offer another option
http://www.murga-linux.com/puppy/viewto ... 4&start=22
big_bass
lets offer another option
http://www.murga-linux.com/puppy/viewto ... 4&start=22
big_bass
New version of 3G project dotpets!
Testers and other users,
I have updated the download dotpets in the first posting of this project thread.
http://www.murga-linux.com/puppy/viewto ... 979#266979
and give details there as "UPDATE 5/11/09". It now logs the mode switching, to aid in troubleshooting uncooperative modems. It also should support some more modems: high-speed and Motorola modems as well as modems using device drivers ipw and ipwireless.
I have upgraded the hso driver and usb_modeswitch package to the latest. I created a separate hso-udev dotpet for high-speed-modem switching, to correspond to the tarball it is based on. I obtained it as udev.tar.gz from http://www.pharscape.org/forum/index.php?topic=545.0
but modified the udev rule file heavily for efficiency and addition of new devices. Usb_modeswitch came from the Download section of page http://www.draisberghof.de/usb_modeswitch/
The addition of mode-switch logging and insertion of a delay before making the switch are results of my (unsuccessful) work with Wilky and his ZTE MF626 modem, which gets a "-110" error code in usb_modeswitch that prevents it from working. Now that he can no longer test for me, I will need muggins' help to see whether that is a larger problem.
I am concerned that so few people have complained about this implementation even though I have found large parts that do not work as intended. If something does not work, please tell me before giving up in disgust. Also, I would like a few people to assure me that it works for them, particularly the mode switching. I think I am as far as I can go until I get some feedback on this new version.
Thank you, all, for your help in moving this project forward.
Richard
I have updated the download dotpets in the first posting of this project thread.
http://www.murga-linux.com/puppy/viewto ... 979#266979
and give details there as "UPDATE 5/11/09". It now logs the mode switching, to aid in troubleshooting uncooperative modems. It also should support some more modems: high-speed and Motorola modems as well as modems using device drivers ipw and ipwireless.
I have upgraded the hso driver and usb_modeswitch package to the latest. I created a separate hso-udev dotpet for high-speed-modem switching, to correspond to the tarball it is based on. I obtained it as udev.tar.gz from http://www.pharscape.org/forum/index.php?topic=545.0
but modified the udev rule file heavily for efficiency and addition of new devices. Usb_modeswitch came from the Download section of page http://www.draisberghof.de/usb_modeswitch/
The addition of mode-switch logging and insertion of a delay before making the switch are results of my (unsuccessful) work with Wilky and his ZTE MF626 modem, which gets a "-110" error code in usb_modeswitch that prevents it from working. Now that he can no longer test for me, I will need muggins' help to see whether that is a larger problem.
I am concerned that so few people have complained about this implementation even though I have found large parts that do not work as intended. If something does not work, please tell me before giving up in disgust. Also, I would like a few people to assure me that it works for them, particularly the mode switching. I think I am as far as I can go until I get some feedback on this new version.
Thank you, all, for your help in moving this project forward.
Richard
big_bass,
The apparent simplicity is appealing and makes a good workaround until full automatic detection is achieved.
That ZTE device is one of the hybrids that appear to require switching the mode from storage to modem. He did not say how he did that, but perhaps "ejecting" the storage device (mentioned above somewhere) might suffice. He also did not say how he got to the point where wvdial.conf contained "modem = /dev/ttys0". That suggests a serial modem was already attached so that puppy would set up wvdial.conf appropriately. Also omitted was anything about the driver for it; since option does not see it in P4, usbserial with vendor & product IDs must have been started somehow -- in Puppy that should be through BootManager.
My understanding is that the baud value is essentilly ignored. Others have posted that their modem worked fine even if the value were, like, 56K. I would like to know what in the deleted initialization string prompted him to delete it. Also, why "Dial Command = ATX1DT" instead of just ATDT. The "X1" controls the set of modem responses to be handled -- why is that necessary? I need justification for each divergence from what puppy provides, so I might improve puppy to take them into account.
Almost all of the mods were through the PupDial window, which is appropriate. So my question is about the need for "X1". Regarding the other edit, I wonder if the probe-PROBE function would find ttyUSB0 and set it in wvdial.conf. I would prefer that kind of instruction over editing, which exposes files to accidental corruption. We could work up a set of workaround instructions that avoids editing. Maybe a minor tweak to PupDial would be needed to make that work. Interested?
Richard
The apparent simplicity is appealing and makes a good workaround until full automatic detection is achieved.
But I think he left out a few things.i edited modem= from /dev/ttys0 to /dev/ttyUSB0
i removed the activation string from init2=
set carrier check to no
Baud = from 460800 to 980800
just that is it
That ZTE device is one of the hybrids that appear to require switching the mode from storage to modem. He did not say how he did that, but perhaps "ejecting" the storage device (mentioned above somewhere) might suffice. He also did not say how he got to the point where wvdial.conf contained "modem = /dev/ttys0". That suggests a serial modem was already attached so that puppy would set up wvdial.conf appropriately. Also omitted was anything about the driver for it; since option does not see it in P4, usbserial with vendor & product IDs must have been started somehow -- in Puppy that should be through BootManager.
My understanding is that the baud value is essentilly ignored. Others have posted that their modem worked fine even if the value were, like, 56K. I would like to know what in the deleted initialization string prompted him to delete it. Also, why "Dial Command = ATX1DT" instead of just ATDT. The "X1" controls the set of modem responses to be handled -- why is that necessary? I need justification for each divergence from what puppy provides, so I might improve puppy to take them into account.
Almost all of the mods were through the PupDial window, which is appropriate. So my question is about the need for "X1". Regarding the other edit, I wonder if the probe-PROBE function would find ttyUSB0 and set it in wvdial.conf. I would prefer that kind of instruction over editing, which exposes files to accidental corruption. We could work up a set of workaround instructions that avoids editing. Maybe a minor tweak to PupDial would be needed to make that work. Interested?
Richard
dejan555,
That's good! Don't forget to include the special versions of the option and usb-storage drivers by tempestuous: http://www.murga-linux.com/puppy/viewto ... 448#254448
And please do not improvise. I need to know where the automated scheme fails, if it does. But my fear is that you will encounter the "error -110" that Wilky and Kark get. Fingers crossed.
Richard
That's good! Don't forget to include the special versions of the option and usb-storage drivers by tempestuous: http://www.murga-linux.com/puppy/viewto ... 448#254448
And please do not improvise. I need to know where the automated scheme fails, if it does. But my fear is that you will encounter the "error -110" that Wilky and Kark get. Fingers crossed.
Richard
Minor corrections to 3G-pupdial-wireless-10 dotpet
I made some minor changes to four scripts in the /usr/sbin directory of the 3G... dotpet. Modemprobe and pupdial have corrections; modemprobe_erase and modemtest are the others. All have the "v41?" annotations changed to "v413". The bugs affect only the first 12 downloads of the dotpet. Details on the download page.
UPDATE 5/13/09: I posted this update in the puppy 5 Alpha 7 Bugs thread along with correcting the firmware omission in Alpha 7. For anyone testing 3G on Alpha 7, the update dotpet is here:
http://www.murga-linux.com/puppy/viewto ... 153#305153
Richard
UPDATE 5/13/09: I posted this update in the puppy 5 Alpha 7 Bugs thread along with correcting the firmware omission in Alpha 7. For anyone testing 3G on Alpha 7, the update dotpet is here:
http://www.murga-linux.com/puppy/viewto ... 153#305153
Richard
@rerwin
I am a noob, i just like to tinker with linux, i have SLAX (frugal)installed in my laptop,i was able to connect using kppp dial, i saw the settings and edited the WvDial conf in slaxer_pup .
i tried again from a fresh (frugal) install of slaxer_pup.. i just edited the WvDial.conf
and i am writing this from the slaxer_pup..
Hope this helps
My 3g usb modem does not have any flash drive ,hence i think
there was no need for me to use any swiching..
I have a integrated dialup modem in my laptop ,hence i think the /dev/ttys0 entry in wvdial.conf
May be because of better hardware detection by slax - ware in slaxer_pup , it was autodetected
With Regards
kayan
The apparent simplicity is appealing and makes a good workaround until full automatic detection is achieved.
i edited modem= from /dev/ttys0 to /dev/ttyUSB0
i removed the activation string from init2=
set carrier check to no
Baud = from 460800 to 980800
just that is it
But I think he left out a few things.
That ZTE device is one of the hybrids that appear to require switching the mode from storage to modem. He did not say how he did that, but perhaps "ejecting" the storage device (mentioned above somewhere) might suffice. He also did not say how he got to the point where wvdial.conf contained "modem = /dev/ttys0". That suggests a serial modem was already attached so that puppy would set up wvdial.conf appropriately. Also omitted was anything about the driver for it; since option does not see it in P4, usbserial with vendor & product IDs must have been started somehow -- in Puppy that should be through BootManager.
I am a noob, i just like to tinker with linux, i have SLAX (frugal)installed in my laptop,i was able to connect using kppp dial, i saw the settings and edited the WvDial conf in slaxer_pup .
i tried again from a fresh (frugal) install of slaxer_pup.. i just edited the WvDial.conf
and i am writing this from the slaxer_pup..
Hope this helps
My 3g usb modem does not have any flash drive ,hence i think
there was no need for me to use any swiching..
I have a integrated dialup modem in my laptop ,hence i think the /dev/ttys0 entry in wvdial.conf
May be because of better hardware detection by slax - ware in slaxer_pup , it was autodetected
With Regards
kayan
[color=blue]SAHARA laptop intel celeron M 1.4 GHz/ 768Mb Ram /40GB ,SIS 661 chipset,[/color]
Richard,
Here are the steps I had to do to get my Sierra (Sprint) 598U wireless broadband modem to work in Puppy 4.20.
1. Went to sierrawireless.com support and downloaded their pdf file on how to set up the modem in Ubuntu using kppp. This also has instructions to set up modem manually using wvdial.config.
2.Ran "modinfo sierra" to see if my unit was supported by the driver that came with 4.20. It was not.
3.Went back to Sierra website and downloaded latest driver for 4.20 kernel. Unpacked it and created dotpet using dir2pet. Installed my dotpet (now I noticed that you have a dotpet with the new drivers for Sierra in it to download) and rebooted.
4.Ran "modinfo sierra" again. My unit was now listed. Vendor Id=0x1199, Product id=0x0025.
5.Following instructions from Sierra I ran "modprobe -r usbserial" and got "Fatal usbserial in use by sierra." So I next ran "modprobe usbserial vendor=0x1199 product=0x0025" Didn't get an error.
6.Ran "dmesg|grep -i ttyUSB" which told me "Sierra now attached to ttyUSB0 etc."
7.Navigated to /root/ect/wvdial.conf and opened it up in Geany and deleted all the text in it, then copied and pasted the text from the Sierra pdf instructions and saved it.
8.Closed that, went to Connect icon on desktop, clicked and ticked pupdial to open when clicking Connect.
9.Clicked on Connect, opened pupdial and clicked on probe for modem. That gave me "modem detected" report at top. Hit connect to internet and viola here I am.
I must tell you tho I got it boiled down to these steps which I have also used to set up the modem in Puppy4.13NOP, after many hours of reading and fruitless tinkering because I didn't have the proper driver installed. So the very most important step for these modems, which work quite well once set up, is to check to make sure the driver in your system is the right one for your device. I'm not a programmer so I don't know if these steps will help you with you're quest to automate the process, but I hope so.
Here are the steps I had to do to get my Sierra (Sprint) 598U wireless broadband modem to work in Puppy 4.20.
1. Went to sierrawireless.com support and downloaded their pdf file on how to set up the modem in Ubuntu using kppp. This also has instructions to set up modem manually using wvdial.config.
2.Ran "modinfo sierra" to see if my unit was supported by the driver that came with 4.20. It was not.
3.Went back to Sierra website and downloaded latest driver for 4.20 kernel. Unpacked it and created dotpet using dir2pet. Installed my dotpet (now I noticed that you have a dotpet with the new drivers for Sierra in it to download) and rebooted.
4.Ran "modinfo sierra" again. My unit was now listed. Vendor Id=0x1199, Product id=0x0025.
5.Following instructions from Sierra I ran "modprobe -r usbserial" and got "Fatal usbserial in use by sierra." So I next ran "modprobe usbserial vendor=0x1199 product=0x0025" Didn't get an error.
6.Ran "dmesg|grep -i ttyUSB" which told me "Sierra now attached to ttyUSB0 etc."
7.Navigated to /root/ect/wvdial.conf and opened it up in Geany and deleted all the text in it, then copied and pasted the text from the Sierra pdf instructions and saved it.
8.Closed that, went to Connect icon on desktop, clicked and ticked pupdial to open when clicking Connect.
9.Clicked on Connect, opened pupdial and clicked on probe for modem. That gave me "modem detected" report at top. Hit connect to internet and viola here I am.
I must tell you tho I got it boiled down to these steps which I have also used to set up the modem in Puppy4.13NOP, after many hours of reading and fruitless tinkering because I didn't have the proper driver installed. So the very most important step for these modems, which work quite well once set up, is to check to make sure the driver in your system is the right one for your device. I'm not a programmer so I don't know if these steps will help you with you're quest to automate the process, but I hope so.