Severity = important
I have a problem that may affect both the setserial (serial line config)
and acpi (power management). My system is being prepared as a firewall
and serial-line communications controller.
Linux kernels are normally configured to support 4 serial lines. I have
not recompiled
1.771023] 00:0a: ttyS5 at I/O 0x2f8 (irq = 3) is a 16550A
>
> It posible resolve with setserial or minicom ???
>
> Sorry my english is not good
What's the problem? This is the standard way for Linux to name serial
ports. 3F8 gets /dev/ttyS0 and 2F8 gets /dev/ttyS1. That
is a 16550A
> [1.771023] 00:0a: ttyS5 at I/O 0x2f8 (irq = 3) is a 16550A
>
> It posible resolve with setserial or minicom ???
No. But you should be able to use a udev rule to rename the device node
(alternatively, if you use udev to add a symlink, then you can use the
ports as either ttyS[01] or ttyS[45].
signature.asc
Description: Digital signature
[1.771023] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
to
[1.770721] 00:09: ttyS4 at I/O 0x3f8 (irq = 4) is a 16550A
[1.771023] 00:0a: ttyS5 at I/O 0x2f8 (irq = 3) is a 16550A
It posible resolve with setserial or minicom ???
Sorry my english is not good
Regards
--
To UNSUBSCRIBE
On Sat, 20 Aug 2005 17:12:10 -0500, W. Paul Mills wrote:
> Perhaps you should read "/usr/share/doc/setserial/README.Debian.gz"
> See "/usr/share/doc/setserial/serial.conf" for a sample serial.conf file
> if you need one.
I don't need one if the serial.conf is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uwe Dippel wrote:
> setserial is broken, with respect to several aspects.
>
> Here is my story:
> Internal Modem on ttyS2 (COM3), IRQ5.
>
> Since the Linux kernel is too dumb to find out (the BSDs always find on
> their own
setserial is broken, with respect to several aspects.
Here is my story:
Internal Modem on ttyS2 (COM3), IRQ5.
Since the Linux kernel is too dumb to find out (the BSDs always find on
their own, but this is another topic), I install setserial.
Immediately it asks and suggests 'autosave once&#
hi all,
i inserted a two PCI serial port card into a debian machine
i used dpkg-reconfigure setserial and chose autoserial
when i check
#setserial -g /dev/ttyS?
i set tthe ttyS2&ttyS3 manually as
setserial /dev/ttyS3 uart 16550A port 0x02e8 irq 3
setserial /dev/ttyS2 uart 16550A port 0x03e8
hello,
i am having difficulties installing an pci modem with setserial and the
2.6 kernel.
it seems that the name(s) of the serial modules have changed from 2.2.x,
2.4.x to the 2.6.x series. what used to be "serial" is now "8250" and
"8250-pci", etc.
the (relev
he modem itself is in working order.
*
I want to use the modem on /dev/ttyS2. I therefore type the following
command (as root, of course), all in accordance with the modem's fine
manual:
# setserial /dev/ttyS2 uart 16550A port 0xb000 irq 4
This returns the error message:
"C
Pigeon wrote:
> Sebastia Altemir wrote:
> > I have fixed my winmodem problem by using
> >
> > setserial /dev/ttyS2 int 9
> >
> > When machine restarts, that seting is lost.
> >
> > What file must I edit to have this value forever ?
>
&
On Mon, Oct 27, 2003 at 07:05:31AM -0800, Sebastia Altemir wrote:
> Hi !
> I have fixed my winmodem problem by using
>
> setserial /dev/ttyS2 int 9
>
> When machine restarts, that seting is lost.
>
> What file must I edit to have this value forever ?
>
> I am
Hi !
I have fixed my winmodem problem by using
setserial /dev/ttyS2 int 9
When machine restarts, that seting is lost.
What file must I edit to have this value forever ?
I am using LINEX (this is a Debian distro, with kernel 2.4.20) 3.0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Hopefully somebody here can give me some ideas. I've tried eMailing the kernel
serial module maintainer (no response), and posting a bug report against
setserial (but he has no experience with kernel V2.6 and would appreciate any
advice too).
I've compiled kernel-image-2.6.0-tes
* Vineet Kumar ([EMAIL PROTECTED]) [020312 13:05]:
> one of the package-provided initscripts. For setserial, you should be
> able to 'dpkg-reconfigure setserial' (as root) and have it "autosave
> once". This means that any changes you make to /etc/serial.conf this
ppp0"
> 192.168.1.0 0.0.0.0 Ueth0
> 0.0.0.010.112.112.112 UG ppp0
>
> and I can now ping out of my lan to an ip on the net.
>
> Because I an using IRQ-5 on my modem I must also do a
> 'setserial /dev/ttyS3 IRQ 5" before dialing.
take a look at
2.112.112 0.0.0.0 UH ppp0"
> 192.168.1.0 0.0.0.0 Ueth0
> 0.0.0.010.112.112.112 UG ppp0
>
> and I can now ping out of my lan to an ip on the net.
>
> Because I an using IRQ-5 on my modem I must also do a
> 'setserial /dev/ttyS3 IRQ 5" before
out of my lan to an ip on the net.
Because I an using IRQ-5 on my modem I must also do a
'setserial /dev/ttyS3 IRQ 5" before dialing.
I am curious as to why the modem does not dial out
after setting 'demand' in 'ppp-config' ?
I set 'defaultroute' in ppp-conf
- Original Message -
From: "Jan Zegan" <[EMAIL PROTECTED]>
To:
Sent: Friday, October 13, 2000 2:01 PM
Subject: setserial
Not sure which kernel version, but if you have #AUTOSAVE at the top of your
serial.conf script, REMOVE it...Then reboot, it, your new settings should
Hello
When I issue
setserial /dev/ttyS0 irq 3 spd_hi
it goes back to the original settings after I reboot the system. How can I
make it stay?
Thanks in advance
Hello,
>
> err... have you installed the setserial package? it DOES run at every boot
> up. Place your configuration in /etc/serial.conf. If not, try "apt-get
> --purge remove setserial && apt-get install setserial" to do a complete (as
> in overwrite any
>From man setserial:
FILES
/etc/serial.conf /etc/init.d/setserial
Have a look at these files (especialy at the first one).
On Mon, 4 Sep 2000, David Bellows wrote:
> Hello everyone,
>
> I'm using a non-standard IRQ setting for my /dev/ttyS0. Currently every
> t
On Mon, 04 Sep 2000, David Bellows wrote:
> time I boot up I have to run the setserial command by hand. My question
> is where is the best Debian place to insert this command to have it
> execute on boot up?
err... have you installed the setserial package? it DOES run at every boot
Hello everyone,
I'm using a non-standard IRQ setting for my /dev/ttyS0. Currently every
time I boot up I have to run the setserial command by hand. My question
is where is the best Debian place to insert this command to have it
execute on boot up?
Thanks,
David Bellows
Quoting Johann Spies ([EMAIL PROTECTED]):
>
> Now I have a few questions about he setup and software. According to
> the documentation "The port must be set to run at 2400 baud,
> gety/login off, modem control enabled."
> [...]
> 1. Does that mean that I have to do a
modem control enabled."
The man page for setserial says
baud_base baud_base
This option sets the base baud rate, which is the
clock frequency divided by 16. Normally this value
is 115200, which is also the fastest baud rate
which th
> I couldn't change the setting of the port at all. stty -F /dev/ttyS0 -a shows
> the change, but cat /dev/ttyS0 shows nothing.
>
> The permissions are: crw-rw 1 root dialout4, 64 Dec 28 21:00
> /dev/ttyS0; I'm in the group dialout, but only minicom changes act
On 13.01.2000 08:38:00 AM matthschulz wrote:
>The permissions are: crw-rw 1 root dialout4, 64 Dec 28 21:00
>/dev/ttyS0; I'm in the group dialout, but only minicom changes actualy the
>settings - nothing else I found - stty and setserial.
>
So you tried with setserial, too ?
B.
tualy the
settings - nothing else I found - stty and setserial.
Any ideas?
Matth
Why does setserial depend on modutils? If I have serial support built into
my kernel I do not need modutils, do I?
Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz| Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU
ed for
> ttyS3.
> If I do a setserial -a ttyS3, I get the same reply..
Does the same thing happen on the other serial ports, ttyS0-2 ?
If it does, are you using a serial mouse and does it work?
If the same thing isnt happening on the other serial ports I would just
recreate this particular
Hi DebianUsers,
I have installed slink on my 486 last night..The kernel can't recognize
the modem. When I ran minicom, all it says is
Serial operation not supported by ttyS3. The modem is jumper configured
for ttyS3.
If I do a setserial -a ttyS3, I get the same reply..
Can some one figure
Hi Guys,
I am trying to get the not so important word out that the setserial that is
shipped with slink is not exactly right for kernel series 2.2.x. That isn't
to say it won't work with the newer kernels. It will. But it was compiled
with the 2.0.x version of serial.h and so will not
have problems getting /dev/ttyS3 to recognize the modem in
the first place. I use the following command to set up the port:
/bin/setserial /dev/ttyS3 port 0x03e8 irq 4
Seems simple enough, but a review of /proc/ioports shows nothing:
# more ioports
-001f : dma1
0020-003f : pic1
0040-005f : timer
Hi,
On Fri, 02 Apr, 1999 à 06:05:23AM -0500, [EMAIL PROTECTED] wrote:
> First: I could swear there was a script floating around
> to have your machine dial up your ISP & email the IP
> address to you. I thought it was in an early issue of
> Linux Gazette. Does anyone know if & where I might find
Judith E. Bush writes:
> I'd write it myself, except I'm frustrated with my ppp dial up script as
> it is.
Have you tried running pppconfig to set up ppp and then using pon and poff?
You are obviously using vanilla PAP authentication. With Debian there is
no need to write ornate ppp scripts.
--
I have written script like that, and it's on my homepage (URL below).
Basicly keeps pppd alive and emails you IPs.
Andrew
---
Andrei S. Ivanov
[EMAIL PROTECTED]
UIN 12402354
h
st, and do an "apt-get install dhis". (You could do it
manually, but I don't feel like checking how.)
> Last night I read some man pages (very large thankyou to
> those involved with setting up the HTML documentation
> structure) and thought I discovered the problem in
n the hylafax
probemodem script.
Last night I read some man pages (very large thankyou to
those involved with setting up the HTML documentation
structure) and thought I discovered the problem in the
closing_waits of setserial. closing_wait2seems 'stuck'
at infinte.
Anyhow, I&#
Anthony Campbell <[EMAIL PROTECTED]> writes:
> > > "Use of setserial/setrocket to get SPD_* flags is deprecated"
Are you sure that's "get SPD_"? The only string like that in the
kernel is in drivers/char/tty_io.c line 1903:
printk("Use
On 02 Feb 1999q, Carey Evans wrote:
> Anthony Campbell <[EMAIL PROTECTED]> writes:
>
> > "Use of setserial/setrocket to get SPD_* flags is deprecated"
> >
> > This seems to be said more in sorrow than in anger, since the process then
> > goes
Anthony Campbell <[EMAIL PROTECTED]> writes:
> "Use of setserial/setrocket to get SPD_* flags is deprecated"
>
> This seems to be said more in sorrow than in anger, since the process then
> goes off correctly. But what does it mean, and what can I do about
I use dip to connect to my ISP.
I've just installed kernel 2.2.1. When I connect, I get a message saying:
"Use of setserial/setrocket to get SPD_* flags is deprecated"
This seems to be said more in sorrow than in anger, since the process then
goes off correctly. But wh
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'
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
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, t
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 sc
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
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 revert
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 c
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 setserial in any of the other rc*.d directories, nor in init.d. I
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 L
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 = ttyS
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 setserial in any of the other rc*.d directories, nor in init.d. I tried
> editing 0setserial to manually assign irq 2 to
still saw setserial assign everything. When I moved 0setserial back in,
setserial was called >twicehttp://megadodo.com/~cleggp/
37 Briarwood Lane, Apt 4, Marlboro, MA 01752 (508) 481-2167
Visit the Project Galactic Guide Homepage! http://megadodo.com/
Check out Megadodo
I have edited /etc/rc.boot/0setserial removing the autodetect of
interupts for /dev/cua* and replacing it with a manual call for
/dev/cua2. This is intended to set the IRQ for /dev/cua2 to 5 instead
of 4.
However, after booting I find through setserial -v /dev/cua2 that the
IRQ is 4 (as if
>>>>> "chris" == Chris R Martin <[EMAIL PROTECTED]> writes:
> Is the setserial program contained in any of the Debian
> packages, or will I have to install it seperately?
I didn't do anything special, and it is here on my Debian 1.1
system. I do
On Wed, 11 Sep 1996, Chris R. Martin wrote:
>
> Is the setserial program contained in any of the Debian packages, or will
> I have to install it seperately?
>
Setserial is provided in the base packages (as it is used at boot time)
Chris R. Martin wrote:
>
> Is the setserial program contained in any of the Debian packages, or will
> I have to install it seperately?
Package: setserial
priority: required
section: base
maintainer: Gordon Russell <[EMAIL PROTECTED]>
version: 2.10-8
filename: unstable/b
Is the setserial program contained in any of the Debian packages, or will
I have to install it seperately?
Thanks, Chris.
===
Chris R. Martin email: [EMAIL PROTECTED]
> By the way, having 7 data bits and 2 stop bits should be equivalent to
> having 8 data bits without parity generation and 1 stop bit. This is
> because the data bits are sent least significant bit first, and a stop
> bit is the same as a zero data bit.
> ...
> Steve Preston ([EMAIL PROTECTED])
>>>>> Dale Scheetz <[EMAIL PROTECTED]> writes:
> I can point setserial at a particular port, but can't seem to tell it to
> set the stop bits to two.
By the way, having 7 data bits and 2 stop bits should be equivalent to
having 8 data bits without parity gen
Dale Scheetz <[EMAIL PROTECTED]> writes:
> I can point setserial at a particular port, but can't seem to tell it to
> set the stop bits to two.
> I can tell stty to set the stop bits, but can only seem to use it while on
> the tty in question. Is there any way to point
I can point setserial at a particular port, but can't seem to tell it to
set the stop bits to two.
I can tell stty to set the stop bits, but can only seem to use it while on
the tty in question. Is there any way to point stty at the port I want
changed?
TIA,
64 matches
Mail list logo
