by P. T. Kornma » Wed, 10 Oct 2001 08:28:34
I am using a US Robotics 56K Performance Pro Modem (PCI) with RedHat 7.1
with all the upgrades, and I problems with my connection getting dropped. I
disabled the "drop the connection after x seconds" check box, but the
connection still can't be maintained. I was wondering if anyone has had a
similar problem & if/home they solved it.
thanks in advance
by James Richard Tyre » Thu, 11 Oct 2001 11:56:34
> Hi everyone-
> I am using a US Robotics 56K Performance Pro Modem (PCI) with RedHat 7.1
> with all the upgrades, and I problems with my connection getting dropped. I
> disabled the "drop the connection after x seconds" check box, but the
> connection still can't be maintained. I was wondering if anyone has had a
> similar problem & if/home they solved it.
What is the model number of your modem?
What software are you using to dial up?
JRT
1. Modem problem - External US Robotics Voice modem
I really need some help with this one.
I have a 3Com/USR External 56K X2 Voice Faxmodem. I upgraded it to V.90 the
day I bought it (why pay $50+ more for a V.90 modem when you can upgrade for
free anyway?). It's a model '00178400'. It's connected to serial port 2 on
my computer, and serial port 2 is manually set up as COM2 2F8 IRQ3 in the
BIOS. I have a Mouse Systems mouse on serial port 1, which is set up as
COM1 3F8 IRQ4 in the BIOS. I have no other COM ports in the system and no
IRQ conflicts.
The modem works perfectly within Windows 9x/NT. I have not had a single
problem in Windows. However, when I use Red Hat 5.0 on my system, the modem
doesn't quite work correctly. I have /dev/modem set up as a symbolic link
to /dev/cua1 (I've also tried ttyS1, and I get the same results). When I
open minicom, I get the initialization on the screen (e.g. ATZ, OK). All AT
commands I type in come up with an 'OK' as the result, so I know that the
modem is working at this point.
When I dial is a different story, however. When I dial using manual 'ATDT'
commands or from the dialer within minicom, it dials.. gives the 'CONNECT
50666/ARQ' or 'CONNECT 49333/ARQ'.. followed by a bunch of garbage. This
garbage has had three appearances:
1) 2) aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa 3) This is happening regardless of the number being connected to and the I've even tried turning off the power to the modem and turning it back on, The kicker is that it also does the same thing with Slackware 3.2 as well as What's going on? 2. Kernel version to include irqbalance patch??? 3. Problem with modem US Robotics 56k Win modem 4. KDE Install from .tar.gz files 5. US Robotics Performance Pro 56K PCI modem 6. Redhat 5.1 doesn't probe my network card 7. 3com/US robotics PCI modem with Redhat 6.0 8. HELP: ATI Mach64 flickers at 135 MHz dot clock! 9. Driver for US-Robotics PCI Modem ? 10. Help with US Robotics 56K PCI Modem 11. Will a US. Robotics modem (PCI) work? 12. PCI modem (56K US Robotics Condor) questions 13. ?Modem Dial In configuration for US robotics sportster modem
....x...Cf...c..d.f.a..sd.f...c.s..d..f....`....`.`.`.....df.a...x..x...x.c
....
(or something similar - I can't cut and paste to Windows and I have a
non-Linux printer)
```````````````````````````````````````````````````````````````````````````
`````
modulation used. I have tried disabling x2 via using "S32=34", but that has
not worked. It disabled the x2, connects at 28.8-33.6 and still gives the
same problem. I have tried using a "AT&F" to restore defaults. Same thing.
I've even connected to a 14.4 BBS here in town, and I got junk on the screen
again. There seems to be a few places that I have actually gotten the
proper ANSI/ASCII text on the screen.
but that doesn't give me any more luck. I've also tried not using a
symbolic link and using /dev/cua1 and /dev/ttyS1 directly. I just can't
seem to get it to work. The modem is a plug and play modem, but only as far
as the "recognition" of the modem. The COM settings and everything else are
already set up via the COM port.
my Red Hat 5.0.