search for: ttys2

I'm upgrading from CentOS6 to CentOS 7. I run 2 weather stations on C6 and have one of them attached to ttyS0 which is on the motherboard, and the other to ttyS2 which in on an add-on PCI serial card. I'm migrating the weather stations another host running C7 which has a similar hardware configuration.? When I connect the weather station to ttyS0 everything works fine, but when I try to use ttyS1 or ttyS2 nothing happens. The OS identifies all 3 p...

...01/28/18 20:15, Fred Smith wrote: > On Sun, Jan 28, 2018 at 12:10:29PM -0500, Pete Geenhuizen wrote: >> I'm upgrading from CentOS6 to CentOS 7. >> >> I run 2 weather stations on C6 and have one of them attached to >> ttyS0 which is on the motherboard, and the other to ttyS2 which in >> on an add-on PCI serial card. >> >> I'm migrating the weather stations another host running C7 which has >> a similar hardware configuration.? When I connect the weather >> station to ttyS0 everything works fine, but when I try to use ttyS1 >> or...

...enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 20 (level, low) -> IRQ 50 0000:05:00.0: ttyS2 at I/O 0xd000 (irq = 50) is a 16550A 0000:05:00.0: ttyS3 at I/O 0xd008 (irq = 50) is a 16550A ttyS2/3 at IRQ 50 ?! [root at helios ~]# setserial /dev/ttyS0 /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 [root at helios ~]# setserial /dev/ttyS1 /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3 [root...

...Googling for this, I find it is relatively common, and on different laptops. I thought it might be my internal SD reader causing the problems, but these other notebooks do not have such devices. Then I found: http://www.cl.cam.ac.uk/~pb22/I8600/ and: " IrDA - works except on COM3 / ttyS2 It appears that *ttyS2* (the FC2 default) does not work as the IrDA - on boot it reports `*ttyS2 at I/O 0x3e8 (irq = 0) is a 16550A*' and `*ide2: I/O resource 0x3EE-0x3EE not free.*', `*ide2: ports already in use, skipping probe*'. As such, during *POST* press *F2* and *Alt-P* 3 tim...

...Smith wrote: > >On Sun, Jan 28, 2018 at 12:10:29PM -0500, Pete Geenhuizen wrote: > >>I'm upgrading from CentOS6 to CentOS 7. > >> > >>I run 2 weather stations on C6 and have one of them attached to > >>ttyS0 which is on the motherboard, and the other to ttyS2 which in > >>on an add-on PCI serial card. > >> > >>I'm migrating the weather stations another host running C7 which has > >>a similar hardware configuration.? When I connect the weather > >>station to ttyS0 everything works fine, but when I try to u...

...tyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19 ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [LNKC] -> GSI 19 (level, low) -> IRQ 177 0000:01:0a.0: ttyS2 at I/O 0xd080 (irq = 177) is a 16550A 0000:01:0a.0: ttyS3 at I/O 0xd000 (irq = 177) is a 16550A ACPI: PCI Interrupt 0000:01:0a.1[A] -> Link [LNKC] -> GSI 19 (level, low) -> IRQ 177 Couldn't register serial port 0000:01:0a.1: -28 OK, instead of skipping ttyS2 and ttyS3 (normally old-s...

On Sun, Jan 28, 2018 at 12:10:29PM -0500, Pete Geenhuizen wrote: > I'm upgrading from CentOS6 to CentOS 7. > > I run 2 weather stations on C6 and have one of them attached to > ttyS0 which is on the motherboard, and the other to ttyS2 which in > on an add-on PCI serial card. > > I'm migrating the weather stations another host running C7 which has > a similar hardware configuration.? When I connect the weather > station to ttyS0 everything works fine, but when I try to use ttyS1 > or ttyS2 nothing happens....

The vm host shows this: # setserial -g /dev/ttyS* /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: 16950/954, Port: 0xd040, IRQ: 17 /dev/ttyS2, UART: 16950/954, Port: 0xd048, IRQ: 17 /dev/ttyS3, UART: 16950/954, Port: 0xd050, IRQ: 17 # # ll /dev/ttyS* crw-rw----. 1 root dialout 4, 64 Nov 10 12:18 /dev/ttyS0 crw-rw----. 1 root dialout 4, 65 Nov 10 12:18 /dev/ttyS1 crw-rw----. 1 root dialout 4, 66 Nov 10 12:18 /dev/ttyS2 crw-rw----. 1 root...

...erial utility. What I need from somebody is guidance on how to use this utility to properly configure the ports. Currently in /dev/ I have: crw------- 1 uucp uucp 4, 64 Dec 21 12:14 ttyS0 crw------- 1 root root 4, 65 Dec 20 17:36 ttyS1 crw------- 1 root root 4, 66 Dec 20 17:36 ttyS2 crw------- 1 root root 4, 67 Dec 20 17:36 ttyS3 When I run setserial -g ttyS* I get this: # setserial -g ttyS* Cannot get serial info: Invalid argument ttyS1: No such device or address ttyS2: No such device or address ttyS3: No such device or address Can someone walk me through this? I...

...l Bios Setup menu label ^Bios Setup kernel menu.c32 append pxelinux.cfg/biossetup.menu label Linux Installer menu label Linux ^Installer --- snip ------------ snip ------ Now, recently we bought different computers whose BMC(Baseboard Management Controller) redirect COM3(ttyS2) to SOL. We were able to see pxelinux menu with old machines but we can't see them with newer ones. We want to see pxelinux menu's outputs with both machines. Is it possible to have pxelinux output both COM2 and COM3 simultaneously ? Or, is it possible to have pxelinux behave like GRUB,...

...:DOSFS_CreateCommPort Couldn't open device '/dev/ttyS1' ! (check permissions) fixme:dosfs:DOSFS_OpenDevice device open L"COM2" not supported (yet) err:file:CreateFileW Couldn't open device L"COM2"! err:dosfs:DOSFS_CreateCommPort Couldn't open device '/dev/ttyS2' ! (check permissions) fixme:dosfs:DOSFS_OpenDevice device open L"COM3" not supported (yet) err:file:CreateFileW Couldn't open device L"COM3"! err:dosfs:DOSFS_CreateCommPort Couldn't open device '/dev/modem' ! (check permissions) fixme:dosfs:DOSFS_OpenDevice...

...t; <source path='/dev/ttyS3'/> <target type='isa-serial' port='2'> <model name='isa-serial'/> </target> <alias name='ua-Serial3'/> </serial> I expected, that given the target port 2 it will be connected to /dev/ttyS2 in the VM. But the target port gets totaly ignored and it will always be connected to ttyS0. Unless I define another serial before this, then it is connected to ttyS1, which is just the order of the serial devices in the xml then, still ignoring the target port. So, do I understand the target port...

After reading a retarded amount of docs I'm still unable to figure out how to get Asterisk to monitor my phone line and pick it up when the phone rings...Im using a voice/fax/data modem on ttyS2. Any tips/pointers to another stack of docs? Is this even doable without special hardware? TIA, Nick

...#39; I see this: ... Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 177 0000:04:00.0: ttyS0 at I/O 0xbf00 (irq = 177) is a 16550A 0000:04:00.0: ttyS1 at I/O 0xbf08 (irq = 177) is a 16550A 0000:04:00.0: ttyS2 at I/O 0xbe00 (irq = 177) is a 16550A 0000:04:00.0: ttyS3 at I/O 0xbe08 (irq = 177) is a 16550A Couldn't register serial port 0000:04:00.0: -28 ... [root at smse2e ~]# ls -la /dev/ttyS* crw-rw---- 1 root uucp 4, 64 Dec 6 2007 /dev/ttyS0 crw-rw---- 1 root uucp 4, 65 Dec 6 2007 /dev/ttyS1 cr...

Dear friends, I am trying NUT standalone on XP. My UPS is on serial port COM3 How can I include the serial port info in the ups.conf file. If it was like in Linux, I would put port=/dev/ttyS2 However, "something" tells me that this is not correct. Your input will be much appreciated. Regards Nick -- Nick P. Petropoulos, PhD NTUA, Mechanical Engineer NTUA, Lecturer, Nuclear Engineering Dept. School of Mechanical Engineering National Technical University of Athens Zografos...

..., setting to 0xdeadbeefF and then err:dosfs:DOSFS_CreateCommPort Couldn't open /dev/ttyS1 ! (check permissions) fixme:dosfs:DOSFS_OpenDevice device open COM2 not supported (yet) err:file:CreateFileA Couldn't open device 'COM2'! err:dosfs:DOSFS_CreateCommPort Couldn't open /dev/ttyS2 ! (check permissions) fixme:dosfs:DOSFS_OpenDevice device open COM3 not supported (yet) err:file:CreateFileA Couldn't open device 'COM3'! err:dosfs:DOSFS_CreateCommPort Couldn't open /dev/modem ! (check permissions) fixme:dosfs:DOSFS_OpenDevice device open COM4 not supported (yet) e...

...quot;). The client is gnophone (a Debian SID machine too, "client"). My modem is a GVC 56k voice modem connected to the server's serial port. I modified modem.conf by enabling "type=aopen", because modem can't be autodetected. I've also added "device => /dev/ttyS2". The modem seems to be initialised. I am not sure what to do with "stripmsd=1"... extension.conf: I've added "exten => 5957,Dial,Zap/1" to "[local]". iax.conf: I've added the following block: [kubi] type=user context=local secret=mysecret I'd l...

.../pci" below. The (very sparse) instructions for Linux support for this card state that you should look for the string "serial port x" in the contents of /proc/pci, and then use that information with the setserial command to configure the port as follows: # setserial /dev/ttyS2 port 0xc000 uart 16550 irq 11 baud_base 115200 The problem is that I can't find the equivalent of the "0xc000" and the IRQ on my system in the contents of /proc/pci. Here is what the built-in, working serial port looks like: # setserial -a /dev/ttyS0 /dev/ttyS0, Lin...

...in wine under Mandrake 8.0 (kernel 2.4.3). Installed wine without errors. Had a look at the ~/.wine/config and it looked ok for me. The part concerning the serial ports: [serialports] "Com1" = "/dev/ttyS0" "Com2" = "/dev/ttyS1" "Com3" = "/dev/ttyS2" "Com4" = "/dev/modem" Then I started the installer from the Toshiba-CD and installed the software for my Toshiba PDR-M5. It's not supported by gphoto (nor by gphoto2) so I am trying to get this windows-software running. The software installed ok. I start it and when...

Hello, Last night we had a power failure and my upsses worked. Strange thing was that the ups supporting the Windoze box lasted longer than the one supporting the (Epia based) Linux box (running nut). After exactly 5 minutes the Linux machine went down abruptly. Is this a configuration issue? What did I overlook? Please comment. Thanks, Udo