Nolan -
No, you can not share serial ports without a little tweaking. But don't
sweat, it's easy.
You need to set the either the device on ttyS0 or ttyS2 to use a
non-standard interrupt (easiest on the modem on ttyS2 if it's jumper
configurable).
For instance - assuming int 5 is free, jumper the modem on ttyS2 to use
int 5. Then, create or modify /etc/rc.d/rc.serial (on RedHat) so that is
has the line:
/sbin/setserial ttyS2 irq 5
Then chmod 755 /etc/rc.d/rc.serial, and then run it. Every time you
reboot, your system will know that in order to access the modem, your
system needs to use the non-standard int 5.
Regards,
Thomas Cameron, RHCE, CNE, MCP, MCT
Three-Sixteen Technical Services, Inc.
A subsidiary of TeamLinux Corporation
--------------------------------------------------------------------------
In science it often happens that scientists say, 'You know that's a really
good argument; my position is mistaken,' and then they actually change
their minds and you never hear that old view from them again. They really
do it. It doesn't happen as often as it should, because scientists are
human and change is sometimes painful. But it happens every day. I
cannot recall the last time something like that happened in politics or
religion.
-- Carl Sagan, 1987 CSICOP keynote address
--------------------------------------------------------------------------
On Tue, 20 Jun 2000, Nolan Darilek wrote:
> Ok, guess it's time for my "problem of the month" post. :)
>
> I've recently been attempting to access /dev/ttyS0, but for some
> strange reason, Linux always reports that it's busy. Odd -- I have
> /dev/ttyS0-2, and ttyS1 and 2 are the only two ports being used.
>
> So I ran fuser/lsof to learn what might be grabbing the port. fuser
> shows that ttyS1-2 are being accessed, but not ttyS0.
>
> On a hunch, I killed my PPP connection (which uses ttyS2), and
> amazingly, ttyS0 became available. Anyhow, I can't quite figure out
> how my modem's use of ttyS2 could effect ttyS0. Here is what dmesg
> says about my serial ports:
>
> 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
> ttyS02 at 0x03e8 (irq = 4) is a 16550A
>
> So, it looks as if there shouldn't be any conflicts, except for the
> IRQs being shared by both, but doesn't the fact that they're using
> different addresses make that possible? If not, what should I do to
> fix this?
>
> ---------------------------------------------------------------------------
> Send administrative requests to [EMAIL PROTECTED]
>
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
