Meanie wrote:
>
> I'm having no end to my troubles getting my ISA PnP modem working. It's
> not a Winmodem; I had it working with Slackware a few months ago.. but I
> just can't get it working with Mandrake / KDE. I have tried every
> combination I could think of: setting the jumpers for PnP with PnP OS
> both enabled and disabled in BIOS, setting the jumpers for particular
> IRQ/COM with PnP OS both enabled and disabled in BIOS... nothing but
> trouble. I've mostly been using Kppp, and when everything seems to be
> set correctly (/dev/cua2 or /dev/ttys2), I usually get a "Modem is
> busy"... occasionally I get "Modem is not responding" though this is
> usually when I've gotten desperate and just go through the list of
> devices at random in kppp setup.
>
> I normally have PnP OS off in BIOS - this doesn't affect any of my
> hardware in Win95, but if it's turned on my sound card won't work in
> Linux... my modem refuses to work either way. Isapnp runs at startup,
> and is finding both of my PnP devices (modem / soundcard), but the modem
> refuses to work. If the jumpers aren't set to PnP, I can't get the
> modem to work in Windows so if it's possible to keep them there I'd like
> to.
>
> I've tried everything I could think of, including setserial...
> unfortunately, I have a feeling I'm using setserial incorrectly. As far
> as I can tell, I'm following the man pages correctly... but I guess I
> don't trust myself. Anyway, if it matters it's a Cheyenne(?) 56K/v.90.
> Looks like it has a Rockwell chipset. Any help (esp w/ setserial) would
> be appreciated.
I would turn PNP OS "off" in the BIOS (to get along with the soundcard),
then set the modem to be non-PNP. Set the modem jumpers to an unused
IRQ and COM port then boot Linux. During bootup, you should see
something like this:
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
that will let you know that the port was found. Check to make sure that
the IRQ matches what you set on the modem. If it doesn't, use setserial
to adjust it:
setserial /dev/ttyS<X> irq <Y>
where <X> is the port number from the line above (just remove the first
'0', so ttyS00 becomes ttyS0, etc) and <Y> is the IRQ number that you've
got the modem jumpered for.
Once that is fixed, change the /dev/modem link to point to the correct
device. If your modem is on COM1, you'll use:
cd /dev
rm modem
ln -s ttyS0 modem
Again, adjust those commands to the actual port you're using.
Next, check in /var/lock and see if there are any files named
LCK..<BLAH> there. If there are, remove them before trying to run KPPP.
Finally, run KPPP and adjust your setup to show /dev/modem as the modem
device. That _SHOULD_ be all that's necessary to getting it to work.
For the most part, PNP stuff CAN be a pain under Linux -- the conflicts
between the soundcard and modem when both are set for PNP is a good
example, and one I've fought here once or twice. I hope the information
above is helpful and gets you up and running with Linux!
Good luck!
--
Steve Philp
[EMAIL PROTECTED]
