It could be a Winmodem in which case it's not the modem that's busy, but
rather it's just not finding anything that replies to (or is
available to reply to) modem commands (AT strings). Winmodems do not work with
Linux which would be why it's reported as busy.
Is the modem PCI? If yes, get an ISA or an external (not all boxes have
ISA slots anymore.. I looked for a long time before finding a motherboard
that met my specs when I was building this system.. It had to have at
least 3 ISA slots for all my stuff)
If it's not PCI, then tell us a lil more about the modem.. specs wise.
NOTE: If it's a sound card/modem, it'll be ISA since you can't have both
in a PCI (as it last was so). In this case, the modem could still be a
winmodem.
On Sun, 26 Nov 2000, Roadrunner wrote:
> Hi,
>
> I tried all afternoon to connect to the internet with an internal
> (Rockwell-chipset) modem and it kept failing.
>
> I tried to dailup to the ISP using Kppp.
> (I've installed as a KDE workstation, but I'm using Gnome)(Don't ask, I
> don't know how or why)
>
> anyway,
> I keep getting the message: "Looking for modem" and right after that:
> "Sorry, the modem is busy"
>
> What could be the problem?
>
> Am I using the wrong dailup-tool or am I missing something else?
>
> I hope someone out there can help me.
>
>
> Remon
>
> ps.
> What is keeping the modem so busy?
>
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
--
-Statux
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
