[ale] modem set-up, love to hate it

[James Kinney]

It sounds like the modem is not activated by the bios. ISAPnp is a real
dog on any OS. Make sure the bios is set to have the modem on at irq 4
base 0x3e8 (I think, whatever ttyS00 is, change the F to an E) for ttyS02.
Then the isapntools stuff needs to berun. If the bios intialized the modem
properly, try it with minicom to see if it will fire up.

James P. Kinney III   \Changing the mobile computing world/
President and COO      \          one Linux user         /
Local Net Solutions,LLC \           at a time.          /
770-493-8244             \.___________________________./

On Thu, 8 Mar 2001, Joseph A. Knapka wrote:

> Two things:
> 
> (1) You almost certainly have two serial ports built into
> your motherboard (if this is not the case I'll eat... well,
> something unexpected). They will be configured as ttyS00 and
> ttyS01 unless you disable them in the BIOS settings (there's
> probably a "built-in peripherals" menu or something when you
> enter the BIOS setup screens at boot time).
> 
> (2) If you've got a Plug-n-Pray device, it *must* be configured
> properly before you can use it. If you don't let the kernel
> or isapnp assign the device an IRQ and IO ports, you lose.
> If your box has a PnP BIOS it will try to configure all the
> PnP devices it finds, I think, and in that case I expect the
> kernel would use the BIOS settings (so you shouldn't need
> to worry about it), but I'm not sure.
> 
> I don't even know if the 2.4 PnP stuff works; I know the
> earlier kernel PnP support was pretty twitchy, so I always
> just used isapnp. This is not very simple or well-documented,
> but it works, and I'm sure folks on the list can help you
> out if need be.
> 
> HTH,
> 
> -- Joe
> 
> Sage wrote:
> > 
> > And here again is another nasty.
> > 
> > Bought a new box last week. Installed Mandrake 7.2, which I will probably run over with Slackware. The GUI is MUCH too, well, fluffy.
> > 
> > ANYWAY, once installed, dmesg showed a ttyS00, a ttyS01, and a isapnp modem (Ack!). ttyS00 is on/at IRQ4 (I am thinking this is the mouse), and ttyS01 is at IRQ3 (which I had thought was supposed to be the modem).
> > 
> > Ditzed the pnp crap immediately. Tried every combo of tty's on the hardware, even tried changing the IRQ to 9 (when I did that, the system changed it back to three upon rebooting, anyone know why?). The system recognizes the new port setting, but will not put the IRQ where I set it on the hardware.
> > 
> > What on earth could ttyS01 be? It is causing a "Conflict I/O...2f8" error message from the BIOS, before LILO comes up. I assume here that is because two of the IRQ's are the same. I have checked, and my husband has checked again, and there is nothing else on a serial port, except the mouse. I keep getting "modem is busy" msg.
> > 
> > It is NOT a winmodem, had to pay extra for that, too. It is a TI, 56K V.90/X2.
> > 
> > Can anyone help me out here, or should I just take the stupid thing out to the back yard and shoot it?
> > 
> > Any help would be appreciated. I've called several friends who are Linux users, and they haven't a clue.
> > 
> > Thanks.
> > 
> > -Indira
> > 
> > 
> > --
> > To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
> 
> -- Joe Knapka
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
> 

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.