[opensuse] setserial parameters
It is not clear from the <man setserial> page how to specify the port number. I would experiment, but the setserial command warns against entering invalid port numbers, but gives no example of a correct way to write a port number (an example would have been helpful). I might write: setserial --port 1 (with or without hyphen(s) in all these cases) setserial -port ttyS1 setserial port /dev/ttyS1 ...or something else. What does setserial want? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-25 at 20:11 +0200, Stan Goodman wrote:
It is not clear from the <man setserial> page how to specify the port number. I would experiment, but the setserial command warns against entering invalid port numbers, but gives no example of a correct way to write a port number (an example would have been helpful). I might write:
setserial --port 1 (with or without hyphen(s) in all these cases) setserial -port ttyS1 setserial port /dev/ttyS1
...or something else.
What does setserial want?
Something like "0x02f8". Look: nimrodel:~ # setserial /dev/modem /dev/modem, UART: 16550A, Port: 0x02f8, IRQ: 3 The precise number can be seen, usually, in the bios config page. But normally you don't set this. As to the format for input, the man says: -G Print out the configuration information of the serial port in a form which can be fed back to setserial as command-line arguments. Thus: nimrodel:~ # setserial -G /dev/modem /dev/modem uart 16550A port 0x02f8 irq 3 baud_base 115200 spd_normal skip_test - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHwx1HtTMYHG2NR9URAkDZAJ9rABqIqzrNI43Fe7u3NIVXLOlHhQCcDT8f CRzQkkNlbeT592uLR7p7sO0= =bYMD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 25 February 2008 21:55:50 Carlos E. R. wrote:
The Monday 2008-02-25 at 20:11 +0200, Stan Goodman wrote:
It is not clear from the <man setserial> page how to specify the port number. I would experiment, but the setserial command warns against entering invalid port numbers, but gives no example of a correct way to write a port number (an example would have been helpful). I might write:
setserial --port 1 (with or without hyphen(s) in all these cases) setserial -port ttyS1 setserial port /dev/ttyS1
...or something else.
What does setserial want?
Something like "0x02f8". Look:
nimrodel:~ # setserial /dev/modem /dev/modem, UART: 16550A, Port: 0x02f8, IRQ: 3
The precise number can be seen, usually, in the bios config page. But normally you don't set this.
As to the format for input, the man says:
-G Print out the configuration information of the serial port in a form which can be fed back to setserial as command-line arguments.
Thus:
nimrodel:~ # setserial -G /dev/modem /dev/modem uart 16550A port 0x02f8 irq 3 baud_base 115200 spd_normal skip_test
The machine has three serial ports, the one on the MB, and two on a PCI
card that has taken IRQ19:
# setserial -G /dev/modem
/dev/modem: No such file or directory
But the (external) modem IS attached to ttyS1, and this WAS visible to the
system when I had efax-gtk running after a fashion. I have done nothing
whatever since to the cable between the port and the modem.
Substituting the port name for "modem":
# setserial -G /dev/ttyS1
/dev/ttyS1 uart 16650V2 port 0xb800 irq 19 baud_base 921600 spd_normal
skip_test
Plugging this information into setserials:
# setserial /dev/ttyS1 uart 16650V2 port 0xb800 irq 19 baud_base 921600
spd_normal skip_test
And seeking the modem gives:
*****
# wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 --
ttyS1<*1>: failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- �
ttyS1<*1>: failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1
ttyS1<*1>: and failed too at 115200, giving up.
ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S3
ttyS4<Info>: No such device or address
Modem Port Scan<*1>: S4
ttyS5<Info>: No such device or address
Modem Port Scan<*1>: S5
ttyS6<Info>: No such device or address
Modem Port Scan<*1>: S6
ttyS7<Info>: No such device or address
Modem Port Scan<*1>: S7
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://open.nit.ca/wiki/?WvDial
If you still have problems, send mail to
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-25 at 23:41 +0200, Stan Goodman wrote:
The machine has three serial ports, the one on the MB, and two on a PCI card that has taken IRQ19:
# setserial -G /dev/modem /dev/modem: No such file or directory
Obviously: it is a symlink you have to create.
But the (external) modem IS attached to ttyS1, and this WAS visible to the system when I had efax-gtk running after a fashion. I have done nothing whatever since to the cable between the port and the modem.
Substituting the port name for "modem":
# setserial -G /dev/ttyS1 /dev/ttyS1 uart 16650V2 port 0xb800 irq 19 baud_base 921600 spd_normal skip_test
Plugging this information into setserials:
# setserial /dev/ttyS1 uart 16650V2 port 0xb800 irq 19 baud_base 921600 spd_normal skip_test
You do not need to feed that to setserial, because those are the same parameters you read from it.
And seeking the modem gives:
***** # wvdialconf /etc/wvdial.conf Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. ttyS1<*1>: ATQ0 V1 E1 -- ttyS1<*1>: failed with 2400 baud, next try: 9600 baud ttyS1<*1>: ATQ0 V1 E1 -- ??? ttyS1<*1>: failed with 9600 baud, next try: 115200 baud ttyS1<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 ttyS1<*1>: and failed too at 115200, giving up. ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S3 ttyS4<Info>: No such device or address Modem Port Scan<*1>: S4 ttyS5<Info>: No such device or address Modem Port Scan<*1>: S5 ttyS6<Info>: No such device or address Modem Port Scan<*1>: S6 ttyS7<Info>: No such device or address Modem Port Scan<*1>: S7
If I have understood you correctly, the simple conclusion seems to be that the (two-week-old) modem needs to be returned.
Well, I didn't say anything yet :-) I would try to access it manually, with minicom, as root. Usually, powering of/on the modem should at least produce garbage on the screen; and setting the correct speed would clear the garbage. Or type "AT[enter]", it should respond "OK". It should work at 115200, but some modems fail and want a lower speed. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHw0DjtTMYHG2NR9URAnNnAJ40Vwy8yPU4e6GN3KrZ9PkllbU0uQCgiwF/ bRk7hvU1gsDXnBX3JexXEdU= =sa7a -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Carlos E. R.
-
Stan Goodman