Re: 56k USR problems

[Jeff Licquia <jeff@luci.org>]

[cc'ing to luci-discuss, to see what ideas others have]

On Sat, 4 Jul 1998, Bill Schoolcraft wrote:

> 	Well I haven't had to email anyone for a while but I'm
> REALLY stuck now. I just removed my old 1996 non-upgradeable
> 28.8 Sportster from my Linux Red Hat 5.0(b) box and put in a
> brand new USR 56k internal to upgrade it. Com 2 set exactly
> the same on the card, tied to fire it up and nothing, not
> even a squelch or dial tone etc. I suspect that I may need
> to edit the modem thread to adjust to the 56k?..... I'm 8
> months into Linux and can stumble around the ppp.conf file
> if needed. I set this Linux box up with netcfg (the GUI) so
> I'm really stuck. I put the old 28.8 back in to email for
> help. Thanks 

A few thoughts:

1.  It doesn't say "WinModem" on the box anywhere, does it?  If so, take
it back for a full refund and get one that doesn't.  The so-called
"WinModem" actually offloads most of its processing to an OS driver.
Besides taking up more CPU time, almost all manufacturers I've seen don't
provide Linux drivers.

2.  Is it Plug and Play?  If so, have you disabled that on the card?
Also, does your BIOS settings mention that you're running a "Plug-and-Play
OS"?  This can screw with the hardware settings.

3.  Make sure you don't have a COM2 port enabled in the BIOS, jumpered on
a card somewhere, etc., or that some other card isn't using IRQ 3.  If you
had a conflict like this, switching modems (even mostly-equivalent ones)
can tweak them.  You should check for any other hardware conflicts as
well; it's weird, but I've seen hardware conflicts affect hardware that
isn't even conflicting.

Try these and let me know what happens.  Good luck!



--
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.