Re: Modem errors

[David Wright <d.wright@open.ac.uk>]

Quoting kmself@ix.netcom.com (kmself@ix.netcom.com):
> on Wed, Jan 10, 2001 at 11:17:15AM +0100, Joerg Johannes (liste_joerg@gmx.de) wrote:
> > Hi there
> > I cannot access my modem (Lasat safire 560). It is connected to
> > /dev/ttyS1(=com2).
> 
> How have you verified this?  Try the following command and post output:
> 
>     $ grep -i 'ttyS' /var/log/dmesg
> 
> In my case:
> 
>     ttyS00 at 0x03f8 (irq = 4) is a 16550A
>     ttyS01 at 0x02f8 (irq = 3) is a 16550A
>     ttyS02 at 0x03e8 (irq = 4) is a 16550A
> 
> ...of which ttyS01 is my modem.

I'm not sure what you're trying to say here. If you're trying to
verify where the modem is connected, then surely minicom is the
answer - try sending AT to it.

If you're talking about the names of devices, well, here's *my*
output from when I boot up:

 Setting kernel variables.
 Loading the saved-state of the serial devices...
 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
 /dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
 /dev/ttyS1 at 0x02f8 (irq = 3) is a 16550A
 Mounting local filesystems...

(/dev/ttyS1 is my modem, as for Joerg. Isn't that COM2?)

Cheers,

-- 
Email:  d.wright@open.ac.uk   Tel: +44 1908 653 739  Fax: +44 1908 655 151
Snail:  David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
Disclaimer:   These addresses are only for reaching me, and do not signify
official stationery. Views expressed here are either my own or plagiarised.