Re: [opensuse] USB Modem, wvdial not redialing
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2008-02-01 a las 00:56 +0530, umesh b escribió: (You forgot to email to the list)
On Jan 30, 2008 6:27 PM, Carlos E. R. <> wrote:
I never buy modems with propietary software. Now you know why. >:-)
actually the modem was provided by the local telco..and the driver CD was only for Win.. :-( However being a USB modem i tried to use it in Linux. Its actually a USB CDMA modem, ZTE make.. model AC8700
The fact is that, if the modem requires a driver, it is not a standard modem and you will have problems making it work under linux. I have no experience making such things work, because I don't want to use them: I'm fortunate to own a plain serial port external modem. But now and then people explain how they got their model working: search this list archive, the wiki pages, google... I'm sorry I can not give you more help. The needed info will be the output of the command "hwinfo --modem", as root. That will tell you how linux sees it, perhaps the chipset, and just maybe, somebody knows something. HTH. - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHoibVtTMYHG2NR9URAmQhAJ9RwRfwql7zCDvsQWeU60P5CNDVugCfe3Dr iV+NkanD9qI2WXnctrPxG9c= =SGcV -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 2008-02-01 a las 00:56 +0530, umesh b escribió:
(You forgot to email to the list)
On Jan 30, 2008 6:27 PM, Carlos E. R. <> wrote:
I never buy modems with propietary software. Now you know why. >:-)
actually the modem was provided by the local telco..and the driver CD was only for Win.. :-( However being a USB modem i tried to use it in Linux. Its actually a USB CDMA modem, ZTE make.. model AC8700
The fact is that, if the modem requires a driver, it is not a standard modem and you will have problems making it work under linux. I have no
Remember, Carlos, even plain-jane external modems that plug into a traditional serial port require a "driver" in Windows... if I were him, I would just try catting the /dev/whatever file that the modem shows up as, and see if it responds. Try some Hayes standard things, like: ATD telephone_number_here # AT = Attention D=dial If that works, then he should just try using it the same as if it were plugged into /dev/ttyS0.
experience making such things work, because I don't want to use them: I'm fortunate to own a plain serial port external modem. But now and then people explain how they got their model working: search this list archive, the wiki pages, google... I'm sorry I can not give you more help.
The needed info will be the output of the command "hwinfo --modem", as root. That will tell you how linux sees it, perhaps the chipset, and just maybe, somebody knows something.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-01-31 at 17:51 -0500, Aaron Kulkis wrote:
The fact is that, if the modem requires a driver, it is not a standard modem and you will have problems making it work under linux. I have no
Remember, Carlos, even plain-jane external modems that plug into a traditional serial port require a "driver" in Windows...
Not a "real" driver. Perhaps terminal software, configuration parameters and such. But not a driver for the modem. At least, I haven't seen it. I have, in the past, had problems several times with modems that required special software to work, and in all cases they were internal modems. Plain serial port external modems, no problems, ever. me, at least.
if I were him, I would just try catting the /dev/whatever file that the modem shows up as, and see if it responds.
I would try minicom. But I trust that if wvdial can not use it, there are serious problems. That's a very good program, I use it with preference to kinternet and such to really know what is happening with the connection. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHo2+btTMYHG2NR9URAqfLAKCXd95vEjBLSfsnQVb9qbegeScFdQCggyjA w9ex/qcMT7fOw505CtEqUX4= =w9Cl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2008-01-31 at 17:51 -0500, Aaron Kulkis wrote:
The fact is that, if the modem requires a driver, it is not a standard modem and you will have problems making it work under linux. I have no
Remember, Carlos, even plain-jane external modems that plug into a traditional serial port require a "driver" in Windows...
Not a "real" driver. Perhaps terminal software, configuration parameters and such. But not a driver for the modem. At least, I haven't seen it.
On windows, if you don't install an external modem on a serial port, you can't use it -- as stupid as that sounds. So, the fact that this USB modem has a Windows driver doesn't mean much of anything -- because Windows requires drivers for modems that don't need drivers.
I have, in the past, had problems several times with modems that required special software to work, and in all cases they were internal modems.
Those aren't actually modems...they're primitive sound cards combined with software which emulates a real modem. A real modem being defined as one which does the job with nothing more than analog circuits, A/D + D/A converters, and the only digital logic circuits being the the 4 registers (input, output, control, and status) plus associated "glue logic" Any "modem" with a DSP chip on it is NOT a real modem.
Plain serial port external modems, no problems, ever. me, at least.
if I were him, I would just try catting the /dev/whatever file that the modem shows up as, and see if it responds.
I would try minicom. But I trust that if wvdial can not use it, there are serious problems. That's a very good program, I use it with preference to kinternet and such to really know what is happening with the connection.
The reason I suggest catting to it directly is that the capabilities of the modem can be tested directly. My guess is that he probably didn't specify the correct /dev file. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-02-01 at 20:51 -0500, Aaron Kulkis wrote:
I have, in the past, had problems several times with modems that required special software to work, and in all cases they were internal modems.
Those aren't actually modems...they're primitive sound cards combined with software which emulates a real modem. A real modem being defined as one which does the job with nothing more than analog circuits, A/D + D/A converters, and the only digital logic circuits being the the 4 registers (input, output, control, and status) plus associated "glue logic"
Not always. Sometimes they are modems, but the error detection/correction logic is done by the driver and main cpu, instead of some kind of cpu in the modem.
Any "modem" with a DSP chip on it is NOT a real modem.
I wouldn't go as far as that.
I would try minicom. But I trust that if wvdial can not use it, there are serious problems. That's a very good program, I use it with preference to kinternet and such to really know what is happening with the connection.
The reason I suggest catting to it directly is that the capabilities of the modem can be tested directly.
My guess is that he probably didn't specify the correct /dev file.
Improbable. Wvdial connects the first time, and fails on the second one. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpMDLtTMYHG2NR9URAs+iAJ92omUQ82GcZoijyXXlbtMe2NN2IgCggwAp 6hyROgvvTx7HyUUTZtO1mtg= =AYkw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2008-02-01 at 20:51 -0500, Aaron Kulkis wrote:
I have, in the past, had problems several times with modems that required special software to work, and in all cases they were internal modems.
Those aren't actually modems...they're primitive sound cards combined with software which emulates a real modem. A real modem being defined as one which does the job with nothing more than analog circuits, A/D + D/A converters, and the only digital logic circuits being the the 4 registers (input, output, control, and status) plus associated "glue logic"
Not always.
Sometimes they are modems, but the error detection/correction logic is done by the driver and main cpu, instead of some kind of cpu in the modem.
A true modem doesn't have an on-board CPU. Not even 56k modems using frequency, amplitude, and phase shifting. There are hybrid digital/analog ICs (integrated circuits) which dothis right from the factory, needing only connectivity to power, a few external discreet elements (resistors, capacitors and/or crystals. They're generally more expensive than the DSP (Digital Signal Processor) + A/D + D/A solution, BUT they have the advantage of not needing any "driver" software, and so will be useable 50 years from now, as long as you can hook up to a serial port, or rig up the pin-outs to whatever a serial port will look like when that time comes.
Any "modem" with a DSP chip on it is NOT a real modem.
I wouldn't go as far as that.
I would try minicom. But I trust that if wvdial can not use it, there are serious problems. That's a very good program, I use it with preference to kinternet and such to really know what is happening with the connection.
The reason I suggest catting to it directly is that the capabilities of the modem can be tested directly.
My guess is that he probably didn't specify the correct /dev file.
Improbable.
Wvdial connects the first time, and fails on the second one.
- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFHpMDLtTMYHG2NR9URAs+iAJ92omUQ82GcZoijyXXlbtMe2NN2IgCggwAp 6hyROgvvTx7HyUUTZtO1mtg= =AYkw -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-02-02 at 14:20 -0500, Aaron Kulkis wrote:
Sometimes they are modems, but the error detection/correction logic is done by the driver and main cpu, instead of some kind of cpu in the modem.
A true modem doesn't have an on-board CPU. Not even 56k modems using frequency, amplitude, and phase shifting. There are hybrid digital/analog ICs (integrated circuits) which dothis right from the factory, needing only connectivity to power, a few external discreet elements (resistors, capacitors and/or crystals.
Some are flasheable, like mine. That usually implies a flash memory and cpu of some kind, even if part of a dedicated chip. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHptzntTMYHG2NR9URAjopAKCKY0uhr5qLbyvMPdv5/WhfgkGxGQCaA1aD e6WxQZYGnI7SDeE9X4MKuvU= =WO+Y -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis wrote:
A true modem doesn't have an on-board CPU. Not even 56k modems using frequency, amplitude, and phase shifting. There are hybrid digital/analog ICs (integrated circuits) which dothis right from the factory, needing only connectivity to power, a few external discreet elements (resistors, capacitors and/or
I think you'll find even those chips have an embedded CPU in 'em. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-04 at 13:18 -0500, James Knott wrote:
I think you'll find even those chips have an embedded CPU in 'em.
That's what I think. Otherwise... there is configuration, command management... difficult in hardware. Everything is possible, but :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHp2nxtTMYHG2NR9URAjn6AJ4/r9pbRofsM+ppvrYMyKTa/xdyLACghcxO A4TLB0PjkNvaJ5vq+rXiEng= =oeMU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Knott wrote:
Aaron Kulkis wrote:
A true modem doesn't have an on-board CPU. Not even 56k modems using frequency, amplitude, and phase shifting. There are hybrid digital/analog ICs (integrated circuits) which dothis right from the factory, needing only connectivity to power, a few external discreet elements (resistors, capacitors and/or
I think you'll find even those chips have an embedded CPU in 'em.
Those CPUs are only to implement the Hayes command set, and those don't need any external drivers, either, because the programming needed to run that is all self-contained in some sort of ROM (seperate, or on-chip if it's something like a Motorola 68HC11 microcontroller. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis wrote:
James Knott wrote:
Aaron Kulkis wrote:
A true modem doesn't have an on-board CPU. Not even 56k modems using frequency, amplitude, and phase shifting. There are hybrid digital/analog ICs (integrated circuits) which dothis right from the factory, needing only connectivity to power, a few external discreet elements (resistors, capacitors and/or
I think you'll find even those chips have an embedded CPU in 'em.
Those CPUs are only to implement the Hayes command set, and those don't need any external drivers, either, because the programming needed to run that is all self-contained in some sort of ROM (seperate, or on-chip if it's something like a Motorola 68HC11 microcontroller.
There's more than just the command set. Modems are also capable of data compression & error detection among other things, that while technically possible with custom logic are simply easier to implement in a CPU. BTW, what do you think is at the heart of a microcontroller? A microcontroller has a CPU, memory and I/O all built into one package. Take a look at this info on the 68HC11: http://bd.thrijswijk.nl/mcca1/68hc11_intro.htm A designer who needs a custom chip will take a microcontroller and program it to do what he wants, slap a new part number on it and ship it in a product. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2/3/08, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Wvdial connects the first time, and fails on the second one.
Thats right.. Modem connects the first time. i can connect to the internet. then i disconnect by issuing CTRL+C at the wvdial terminal. If i again try invoking wvdial, then the problem happens(see my traces in the original mail). I need this as mostly the telco is disconnecting connection randomly due to high traffic or maybe straight forward problems in their equipment. If the modem would connect the second time, then i could enable the autoreconnect option and let the downloads continue without human intervention. Othetwise modem wont connect the second time. -- umesh3034 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
umesh b wrote:
On 2/3/08, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Wvdial connects the first time, and fails on the second one.
Thats right.. Modem connects the first time. i can connect to the internet. then i disconnect by issuing CTRL+C at the wvdial terminal. If i again try invoking wvdial, then the problem happens(see my traces in the original mail). I need this as mostly the telco is disconnecting connection randomly due to high traffic or maybe straight forward problems in their equipment. If the modem would connect the second time, then i could enable the autoreconnect option and let the downloads continue without human intervention. Othetwise modem wont connect the second time.
You need to reset the modem. These commands can ALL be executed by simply running the cat command, such as is shown here: cat > /dev/ttyxx #Substitute the device name for ttyxx) ATZ # reset the modem to default state] ATH0 # go on hook (hang up)] ATH1 # o off hook] ATDT 1234567 # dial 123-4567 using touch-tone (DTMF)] ^D # Ctrl-D to end cat command Once you get everything worked out as to what you need to do before running wvdial again, you can put it into a script, like this You could save this script "redial" and then make it executable. You can call it as either: $ redial # use default tty device. or $ redial /dev/ttyS0 # overrides default tty device]] #!/bin/bash # Shell script to reset modem # and then run wvdial again MODEM=/dev/ttyxx # Modem's device here if [["$1" != "" ]] # test for cmd line argument then MODEM = $1 # set modem to cmd line arg. fi cat > $MODEM << end_of_commands ATZ ATH0 ATH1 end_of_commands wvdial # End of script. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
See http://www.linmodems.org/ Robert On Thursday 31 January 2008 19:51:46 Carlos E. R. wrote:
El 2008-02-01 a las 00:56 +0530, umesh b escribió:
(You forgot to email to the list)
On Jan 30, 2008 6:27 PM, Carlos E. R. <> wrote:
I never buy modems with propietary software. Now you know why.
:-)
actually the modem was provided by the local telco..and the driver CD was only for Win.. :-( However being a USB modem i tried to use it in Linux. Its actually a USB CDMA modem, ZTE make.. model AC8700
The fact is that, if the modem requires a driver, it is not a standard modem and you will have problems making it work under linux. I have no experience making such things work, because I don't want to use them: I'm fortunate to own a plain serial port external modem. But now and then people explain how they got their model working: search this list archive, the wiki pages, google... I'm sorry I can not give you more help.
The needed info will be the output of the command "hwinfo --modem", as root. That will tell you how linux sees it, perhaps the chipset, and just maybe, somebody knows something.
HTH.
-- http://rwbest.no.sapo.pt/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Aaron Kulkis -
Carlos E. R. -
James Knott -
Robert W Best -
umesh b