Please bear with me, I'm plodding through the installation of a linux
system...
I tried running setserial on ttys1 (my modem on com2), but I get a I/O Error
message all the time. I have checked permissions, but don't know what else
to do. Please help. (BTW: I have checked various faq's and
On Sun, Dec 28, 1997 at 12:14:54AM -0800, Dean Somji wrote:
I tried running setserial on ttys1 (my modem on com2), but I get a I/O Error
message all the time. I have checked permissions, but don't know what else
to do. Please help. (BTW: I have checked various faq's and how-to's with
little
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Will Lowe) writes:
I need to set ttyS3 to irq 10 to use my modem. I've been doing this as
setserial /dev/ttyS3 irq 10
Have you tried doing this in /etc/rc.boot/0setserial ?
someplace) or allow a normal user to setserial? I've gotten
On Tue, Dec 23, 1997 at 11:54:05AM -0500, Will Lowe wrote:
I need to set ttyS3 to irq 10 to use my modem. I've been doing this as
setserial /dev/ttyS3 irq 10
but this requires me to be root. Wouldn't be a problem to set it once on
boot with a root-owned script, but after ttyS3 is used for
On Tue, 23 Dec 1997, Adam Klein wrote:
On Tue, Dec 23, 1997 at 11:54:05AM -0500, Will Lowe wrote:
I need to set ttyS3 to irq 10 to use my modem. I've been doing this as
setserial /dev/ttyS3 irq 10
Have you compiled serial support as a module? If so, try having it loaded
from
I need to set ttyS3 to irq 10 to use my modem. I've been doing this as
setserial /dev/ttyS3 irq 10
but this requires me to be root. Wouldn't be a problem to set it once on
boot with a root-owned script, but after ttyS3 is used for a while (e.g.
by pppd or minicom) it reverts to irq 3,
On Sun, Apr 20, 1997 at 03:17:06PM -0400, Peter Iannarelli wrote:
No, it's irq2; I had to set the jumper myself. What you wrote is just the
defaults. I ran OS/2 previous to Linux, and you can't share irqs like
that under OS/2. :)
Well all I can tell you is I'm running 4 16450s cua0 to
I updated a bunch of stuff yesterday via dselect, and I rebooted this
morning to find problems with my modem.
I finally determined that somewhere, my modem (cua2) was being defined as
IRQ 4 (it's not, it's IRQ 2).
I tried to move the 0setserial file out of rc.boot, but during boot I
still saw
Paul J. Clegg wrote:
I updated a bunch of stuff yesterday via dselect, and I rebooted this
morning to find problems with my modem.
I finally determined that somewhere, my modem (cua2) was being defined as
IRQ 4 (it's not, it's IRQ 2).
I tried to move the 0setserial file out of rc.boot,
On Sun, 20 Apr 1997, Peter Iannarelli wrote:
Paul J. Clegg wrote:
I finally determined that somewhere, my modem (cua2) was being defined as
IRQ 4 (it's not, it's IRQ 2).
I think you are mistaken.
com1 = cua0 = ttyS0 irq4
com2 = cua1 = ttyS1 irq3
com3 = cua2 = ttyS2
Paul J. Clegg wrote:
No, it's irq2; I had to set the jumper myself. What you wrote is just the
defaults. I ran OS/2 previous to Linux, and you can't share irqs like
that under OS/2. :)
...Paul
...Paul, [EMAIL PROTECTED], http://megadodo.com/~cleggp/
37 Briarwood Lane, Apt
On Apr 20, Paul J. Clegg wrote
I tried to move the 0setserial file out of rc.boot, but during boot I
still saw setserial assign everything. When I moved 0setserial back in,
setserial was called twice! On top of that, I can't find a call to
setserial in any of the other rc*.d directories,
12 matches
Mail list logo
