by John » Fri, 20 Aug 1999 04:00:00
------------------ Posted via CNET Linux Help ------------------
http://www.searchlinux.com
by Charles Sulliva » Fri, 20 Aug 1999 04:00:00
A couple of clues:
If the modem card has jumpers for COM port and IRQ it is most
likely NOT a winmodem.
If it's a PCI card, it most likely IS a winmodem.
(There are a few rare exceptions to the above.)
>------------------ Posted via CNET Linux Help ------------------
> http://www.searchlinux.com
by Chris Webst » Fri, 20 Aug 1999 04:00:00
"Can't set terminal input/output settings." Or some such message.
--Chris
by Timothy Dix » Fri, 20 Aug 1999 04:00:00
Anyway, if you know the manufacturer of the modem, you can do some
sluething online, but you probably already figured that out. Some
modems are good about this (they have "WinModem" printed on them, or
in the docs). These are easy. If they aren't clear, it becomes
largely a guessing game. Some of these clues might apply to
determining which box in Best Buy is WinModem.
A couple clues that might help;
1. If it's PCI, there's a good chance is WinModem; if it's not, it
likely isn't. PCI cards have quick enough access to the system to
send the raw data to the modem software, that actually decodes and
decompresses it (this is the part that doesn't work in Linux). ISA
cards generally do not.
2. If you can change the port settings (com1, etc) via jumpers, even
if the card is "Plug and Play," it likely is not a WinModem. If it's
set to Plug and Play, you may have trouble getting it to work in Linux
anyway; in that case, manually set com settings.
3. If there's software with it that says something like, "Requires
Pentium 133, 16MB RAM, Windows 95" it is likely (though not
necesarily) a WinModem. WinModems have that kind of system
requirement to run the modem software, but some manufacturers get
sloppy about what's needed to run the modem as opposed to what's
needed to run the software they bundle with the modem. If it says you
can use DOS, you're defnitely good to go (the WinModem software won't
run in DOS any more than Linux).
4. Similar to #3, if you can uninstall the modem software and
communicate with it from HyperTerminal, you're good to go: With the
modem driver completely uninstalled, a WinModem will be as dead in
Windows as it is in Linux, and HyperTerminal won't let you talk with
it. Similarly, if you can echo 'ath1' to the port in Linux and hear a
dial tone (or use a Linux terminal emulator to talk to the modem),
you're good to go.
5. If it supports "virtual com ports" up to numbers like 9 and 12, it
is likely a WinModem (though, again, not necessarily); WinModems
don't have to use a hardware com port, so it's easier to use
non-standard ports (1-4 are "standard").
6. Not much use for you, but helpful in the store, should you decide
this is a WinModem and need to buy a new one: if it's really cheap,
it's a WinModem (or junk, or a junky WinModem -- something to avoid in
any case). WinModems have less hardware (specifically, no
microcontrooler or on-board CPU) so they are cheaper to manufacture.
If it's $20, it's a WinModem. If it's $80, it likely is not.
Exceptions for specials, etc. naturally apply.
7. If it calls itself "controller based" it's not a WinModem (that's
the distinguishing factor -- Creative makes a big deal of this on one
of their modems, recognizing it as a selling factor).
8. Similar to 6 and 7, if you look at the card and it's tiny with
only a couple (3 or 4) IC's, it's probably a WinModem. If it's packed
with lots of stuff and is fairly large (nearly full size), it's
probably not a WinModem.
9. If it's external (again, not much use for you), it's not a
WinModem.
10. If it's "slow" it's probably not a WinModem. Software is what
makes 56K modems different than 33.6 modems, so it's silly to produce
a 33.6 WinModem.
11. If all else fails, but you can identify the modem, post info here
and see if anybody recognizes it.
by Bill Wei » Sun, 29 Aug 1999 04:00:00
I need to jump in on this, my modem simply won't work on Linux, no
matter what I do. I'll answer the questions, then comment at the
bottom.
>>I've purchased a secondhand pc without much documentation. I run
>>Win98 and
>>just installed Red Hat Linux 6.0. I understand that "winmodems"
>>will not
>>work with Linux and would like to know if there is a way to
>>identify
>>whether or not my modem is a "winmodem". Any help would be
>>appreciated.
>>--
>Sigh. Even if I *used* Windows, I'd think WinModems are a horrible
>thing. I don't want to use my CPU to do the work of my modem. Grr.
>Anyway, if you know the manufacturer of the modem, you can do some
>sluething online, but you probably already figured that out. Some
>modems are good about this (they have "WinModem" printed on them, or
>in the docs). These are easy. If they aren't clear, it becomes
>largely a guessing game. Some of these clues might apply to
>determining which box in Best Buy is WinModem.
>A couple clues that might help;
>1. If it's PCI, there's a good chance is WinModem; if it's not, it
>likely isn't. PCI cards have quick enough access to the system to
>send the raw data to the modem software, that actually decodes and
>decompresses it (this is the part that doesn't work in Linux). ISA
>cards generally do not.
Not good.Quote:>2. If you can change the port settings (com1, etc) via jumpers,
>even if the card is "Plug and Play," it likely is not a WinModem.
>If it's set to Plug and Play, you may have trouble getting it to
>work in Linux anyway; in that case, manually set com settings.
No documentation.Quote:>3. If there's software with it that says something like, "Requires
>Pentium 133, 16MB RAM, Windows 95" it is likely (though not
>necesarily) a WinModem. WinModems have that kind of system
>requirement to run the modem software, but some manufacturers get
>sloppy about what's needed to run the modem as opposed to what's
>needed to run the software they bundle with the modem. If it says
>you can use DOS, you're defnitely good to go (the WinModem software
>won't run in DOS any more than Linux).
No software. Uses Generic 33.6 on Win98.Quote:>4. Similar to #3, if you can uninstall the modem software and
>communicate with it from HyperTerminal, you're good to go: With the
>modem driver completely uninstalled, a WinModem will be as dead in
>Windows as it is in Linux, and HyperTerminal won't let you talk with
>it. Similarly, if you can echo 'ath1' to the port in Linux and hear
>a dial tone (or use a Linux terminal emulator to talk to the modem),
>you're good to go.
Standard ports.Quote:>5. If it supports "virtual com ports" up to numbers like 9 and 12,
>it is likely a WinModem (though, again, not necessarily); WinModems
>don't have to use a hardware com port, so it's easier to use
>non-standard ports (1-4 are "standard").
Great, I have $80 to spare ...Quote:>6. Not much use for you, but helpful in the store, should you
>decide this is a WinModem and need to buy a new one: if it's really
>cheap, it's a WinModem (or junk, or a junky WinModem -- something to
>avoid in any case). WinModems have less hardware (specifically, no
>microcontrooler or on-board CPU) so they are cheaper to manufacture.
>If it's $20, it's a WinModem. If it's $80, it likely is not.
>Exceptions for specials, etc. naturally apply.
No documentation.Quote:>7. If it calls itself "controller based" it's not a WinModem (that's
>the distinguishing factor -- Creative makes a big deal of this on
>one of their modems, recognizing it as a selling factor).
Almost the same size as my SB64 GOLD, if it helps.Quote:>8. Similar to 6 and 7, if you look at the card and it's tiny with
>only a couple (3 or 4) IC's, it's probably a WinModem. If it's
>packed with lots of stuff and is fairly large (nearly full size),
>it's probably not a WinModem.
Internal, natch.Quote:>9. If it's external (again, not much use for you), it's not a
>WinModem.
33.6Quote:>10. If it's "slow" it's probably not a WinModem. Software is what
>makes 56K modems different than 33.6 modems, so it's silly to
>produce a 33.6 WinModem.
Well, here you go.Quote:>11. If all else fails, but you can identify the modem, post info
>here and see if anybody recognizes it.
The card was identified for me, by the FCC number. The company, in
Taiwan, has no web page, or any way to reach them.
I've used a few dialer packages in Linux, as well as the RH dialer,
no luck.
It dials, handshakes, connects, then disconnects. This loops.
/var/log/messages says something about "modem in use", "process
exiting", then it dials, and does the above.
Any ideas? I'm at the end of my rope here.
- --
Bill Weiss
PGP key: http://home.earthlink.net/~cultobill/bill_weiss.asc
ICQ#: 43270740
Intel Inside: The world's most commonly used warning label.
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com>
iQEVAwUBN8dszadYWMs+Z0hzAQFjTQf+PZd0c5vXcK8HG1N7XiIB6lDduIxw0Zpa
O0w8G+74Kh+nXZI4S6PpABRP2Mz7+TDQMNAwF0q7sNPGrTvAFu5JZfO7IPRtnLK4
iwyscegvL2GnqBEdQqWsoW0FS64/VaU1CqrMFdEx2BAmv7voHA564QFi3/De06SL
rtMBa+dj2a0ZMy4aVrKfHT7iUnLXYCuMqyaeV3kcOlM+n4mD/fu+dpCU6I7cM21G
8CuvzDnsCfKgf+iwNZDj1T3pbmd7R4koHY3FNllQi+akfUrPmhvKSs8AV1EO3zq2
rE+2Ib4xpBn3RfzB5kcJcrVv3gQ3OJcw4+oXz2IWtRjyyyMnAlqo/A==
=ZvBd
-----END PGP SIGNATURE-----
by Davis Eri » Mon, 30 Aug 1999 04:00:00
This modem stuff is really boring for Linux users. When will this kind
of stupid modem not be manufatured? sigh.
In my case, I used minicom in Linux to indentify my modem. The only
thing you need to do is fire up minicom in linux, then according to the
instruction it gives to talk to your modem. After using AT command, if
you get the message like "on-line" or "connected", then it is not a
winmodem. If you still get "off-line", then it is a winmodem.
I think winmode should be called losemodem instead.
Good luck to you,
Davis
> I need to jump in on this, my modem simply won't work on Linux, no
> matter what I do. I'll answer the questions, then comment at the
> bottom.
> >>I've purchased a secondhand pc without much documentation. I run
> >>Win98 and
> >>just installed Red Hat Linux 6.0. I understand that "winmodems"
> >>will not
> >>work with Linux and would like to know if there is a way to
> >>identify
> >>whether or not my modem is a "winmodem". Any help would be
> >>appreciated.
> >>--
> >Sigh. Even if I *used* Windows, I'd think WinModems are a horrible
> >thing. I don't want to use my CPU to do the work of my modem. Grr.
> >Anyway, if you know the manufacturer of the modem, you can do some
> >sluething online, but you probably already figured that out. Some
> >modems are good about this (they have "WinModem" printed on them, or
> >in the docs). These are easy. If they aren't clear, it becomes
> >largely a guessing game. Some of these clues might apply to
> >determining which box in Best Buy is WinModem.
> >A couple clues that might help;
> >1. If it's PCI, there's a good chance is WinModem; if it's not, it
> >likely isn't. PCI cards have quick enough access to the system to
> >send the raw data to the modem software, that actually decodes and
> >decompresses it (this is the part that doesn't work in Linux). ISA
> >cards generally do not.
> It's PCI.
> >2. If you can change the port settings (com1, etc) via jumpers,
> >even if the card is "Plug and Play," it likely is not a WinModem.
> >If it's set to Plug and Play, you may have trouble getting it to
> >work in Linux anyway; in that case, manually set com settings.
> Not good.
> >3. If there's software with it that says something like, "Requires
> >Pentium 133, 16MB RAM, Windows 95" it is likely (though not
> >necesarily) a WinModem. WinModems have that kind of system
> >requirement to run the modem software, but some manufacturers get
> >sloppy about what's needed to run the modem as opposed to what's
> >needed to run the software they bundle with the modem. If it says
> >you can use DOS, you're defnitely good to go (the WinModem software
> >won't run in DOS any more than Linux).
> No documentation.
> >4. Similar to #3, if you can uninstall the modem software and
> >communicate with it from HyperTerminal, you're good to go: With the
> >modem driver completely uninstalled, a WinModem will be as dead in
> >Windows as it is in Linux, and HyperTerminal won't let you talk with
> >it. Similarly, if you can echo 'ath1' to the port in Linux and hear
> >a dial tone (or use a Linux terminal emulator to talk to the modem),
> >you're good to go.
> No software. Uses Generic 33.6 on Win98.
> >5. If it supports "virtual com ports" up to numbers like 9 and 12,
> >it is likely a WinModem (though, again, not necessarily); WinModems
> >don't have to use a hardware com port, so it's easier to use
> >non-standard ports (1-4 are "standard").
> Standard ports.
> >6. Not much use for you, but helpful in the store, should you
> >decide this is a WinModem and need to buy a new one: if it's really
> >cheap, it's a WinModem (or junk, or a junky WinModem -- something to
> >avoid in any case). WinModems have less hardware (specifically, no
> >microcontrooler or on-board CPU) so they are cheaper to manufacture.
> >If it's $20, it's a WinModem. If it's $80, it likely is not.
> >Exceptions for specials, etc. naturally apply.
> Great, I have $80 to spare ...
> >7. If it calls itself "controller based" it's not a WinModem (that's
> >the distinguishing factor -- Creative makes a big deal of this on
> >one of their modems, recognizing it as a selling factor).
> No documentation.
> >8. Similar to 6 and 7, if you look at the card and it's tiny with
> >only a couple (3 or 4) IC's, it's probably a WinModem. If it's
> >packed with lots of stuff and is fairly large (nearly full size),
> >it's probably not a WinModem.
> Almost the same size as my SB64 GOLD, if it helps.
> >9. If it's external (again, not much use for you), it's not a
> >WinModem.
> Internal, natch.
> >10. If it's "slow" it's probably not a WinModem. Software is what
> >makes 56K modems different than 33.6 modems, so it's silly to
> >produce a 33.6 WinModem.
> 33.6
> >11. If all else fails, but you can identify the modem, post info
> >here and see if anybody recognizes it.
> Well, here you go.
> The card was identified for me, by the FCC number. The company, in
> Taiwan, has no web page, or any way to reach them.
> I've used a few dialer packages in Linux, as well as the RH dialer,
> no luck.
> It dials, handshakes, connects, then disconnects. This loops.
> /var/log/messages says something about "modem in use", "process
> exiting", then it dials, and does the above.
> Any ideas? I'm at the end of my rope here.
> - --
> Bill Weiss
> PGP key: http://home.earthlink.net/~cultobill/bill_weiss.asc
> ICQ#: 43270740
> Intel Inside: The world's most commonly used warning label.
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com>
> iQEVAwUBN8dszadYWMs+Z0hzAQFjTQf+PZd0c5vXcK8HG1N7XiIB6lDduIxw0Zpa
> O0w8G+74Kh+nXZI4S6PpABRP2Mz7+TDQMNAwF0q7sNPGrTvAFu5JZfO7IPRtnLK4
> iwyscegvL2GnqBEdQqWsoW0FS64/VaU1CqrMFdEx2BAmv7voHA564QFi3/De06SL
> rtMBa+dj2a0ZMy4aVrKfHT7iUnLXYCuMqyaeV3kcOlM+n4mD/fu+dpCU6I7cM21G
> 8CuvzDnsCfKgf+iwNZDj1T3pbmd7R4koHY3FNllQi+akfUrPmhvKSs8AV1EO3zq2
> rE+2Ib4xpBn3RfzB5kcJcrVv3gQ3OJcw4+oXz2IWtRjyyyMnAlqo/A==
> =ZvBd
> -----END PGP SIGNATURE-----
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
by Houdin » Mon, 30 Aug 1999 04:00:00
Lemme put a different approach to this, then I give up.Quote:>Hi, there,
>This modem stuff is really boring for Linux users. When will this
>kind of stupid modem not be manufatured? sigh.
>In my case, I used minicom in Linux to indentify my modem. The only
>thing you need to do is fire up minicom in linux, then according to
>the instruction it gives to talk to your modem. After using AT
>command, if you get the message like "on-line" or "connected", then
>it is not a winmodem. If you still get "off-line", then it is a
>winmodem.
>I think winmode should be called losemodem instead.
>Good luck to you,
>Davis
What is a 56k modem, preferably internal, that works with Linux? I
mean, I want one that someone can tell me works, from experience. No
strange tweaks, just works. Anyone?
- --
Bill "Houdini" Weiss
PGP key: http://home.earthlink.net/~cultobill/bill_weiss.asc
ICQ#: 43270740
6:66 - Wake-up time of the Beast
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com>
iQEVAwUBN8jIBKdYWMs+Z0hzAQH/SQf/RRIxoh2N7I9WnppXnhK8zO9OmcNue/IV
TduyhbH1FQmoPSIl2sKgicBGphtHV06HqvKtptbbH1eUtnsIqOLc0NS0nu7Uzvhj
7i61KeG4hWxqTmUtoAvKAfHRl18ELFNTxDsebSQ3wvWUdK6FhkXA7VSov/yQxg4J
2uro845O+yX93Kb+OyM6VEgXEphaOlVW2Fh78JI3daAvweRHINNhCnu2mdVa9VrF
s6ZMSqOUdIOJ/XhV1nfU7Y6Ve3mKFGzK+N89+SyML8VU/45aY/jTs/oi79/X0rbX
Gs++/VRuaRhUs8m53fsF/bc3hdMENMJSqyHgS/khQwy5ZEnE7oMx0Q==
=DtRg
-----END PGP SIGNATURE-----
by Timothy Dix » Tue, 31 Aug 1999 04:00:00
>>Hi, there,
>>This modem stuff is really boring for Linux users. When will this
>>kind of stupid modem not be manufatured? sigh.
>>In my case, I used minicom in Linux to indentify my modem. The only
>>thing you need to do is fire up minicom in linux, then according to
>>the instruction it gives to talk to your modem. After using AT
>>command, if you get the message like "on-line" or "connected", then
>>it is not a winmodem. If you still get "off-line", then it is a
>>winmodem.
>>I think winmode should be called losemodem instead.
>>Good luck to you,
>>Davis
>Lemme put a different approach to this, then I give up.
>What is a 56k modem, preferably internal, that works with Linux? I
>mean, I want one that someone can tell me works, from experience. No
>strange tweaks, just works. Anyone?
Curiously, I've not been able to make it connect to my ISP from
Windows. Nor have I tried hard.
by Spike » Tue, 31 Aug 1999 04:00:00
Surely 06:06:06...Quote:> 6:66 - Wake-up time of the Beast
:)
--
___________________________________________________________________________
| Andrew Halliwell BSc | |
| in | "I think so brain, but this time, you control |
| Computer Science | the Encounter suit, and I'll do the voice..." |
---------------------------------------------------------------------------
|GCv3.12 GCS>$ d-(dpu) s+/- a C++ US++ P L/L+ E-- W+ N++ o+ K PS+ w-- M+/++ |
|PS+++ PE- Y t+ 5++ X+/X++ R+ tv+ b+ DI+ D+ G e++ h/h+ !r!| Space for hire |
---------------------------------------------------------------------------
by Mike Marti » Wed, 01 Sep 1999 04:00:00
Very simply put.
ZOOM model 2919 56k dule mode kflex/V.90 modem ISA
Features: PnP disable jumper
IRQ and COM jumpers.
Any questions?
Running on Linux Redhat 6.0 2.2.5
Shadow's Web Creations & Computer Consultants
"A day's not complete without getting into a little trouble."
Greetings all:
I have a modem which was not represented as being a winmodem. It is a PCI
v.90 modem which uses a 2 chip set from Rockwell (One is P/N RLVDL56DPF/SP).
When I cat /proc/pci after boot, here is what I get for the modem:
Bus 0, device 11, function 0:
Serial controller: Unknown vendor Unknown device (rev 1).
Vendor id=127a. Device id=1005.
Medium devsel. Fast back-to-back capable. IRQ 10. Master
Capable. Latency=32.
Non-prefetchable 32 bit memory at 0xf7ff0000.
Question: can I get this thing to work under Linux or is it a winmodem?
Any help appreicated!
Keith
--
Keith Outwater
6. Tulip driver fails with recent boards
7. I am getting a few error lines on boot up that I can't identify.
9. Identifying actual kernel in use?
10. How do I identify a squash file?
11. how to identify what process has a given socket open ?
12. Identify file status (completely-transfered or transfer-in-progress) ??
13. Identifying Apache SSL Connections