search for: ttys3

...330]: UPS myups at localhost is unavailable Oct 18 22:27:40 pane upsmon[13330]: UPS [myups at localhost]: connect failed: Connection failure: Connection refused i recognized upsd and the driver are not running... so i tried to start the driver manually... but it didn't have permissions on /dev/ttyS3, so i changed, and the driver works... then i could also start upsd manually... but upsmon or upsc can't connect to it: # upsc -l upsc.c:170: Error: Server disconnected i get the same if i trie manually to connect to port 3493, the connection is being closed at once.. what am i doing wrong, a...

...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-school on-board COM3 and COM4) and allocating ttyS4 through...

...550A 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 at helios ~]# setserial /dev/ttyS2 /dev/ttyS2, UART: 1655...

...of potential file name issues it is installed in c:\UPS\NUT and the .\etc files have been tweaked as follows: NUT.EXE Run as a system service, NUT user has read access to everything. Also put .\BIN and .\SBIN in path. _*nut.conf*_ MODE=1 _*ups.conf*_ [UPS2] driver = liebert-esp2 port = /dev/ttyS3 desc = "UPS No 2" NUT as a service starts and stops immediately so I thought I'd try, after much investigation, at lowest common denominator and see what the Driver is reporting. In an elevated CMD shell it says cannot find a /dev/ttyS3? so obviously reading the ups.conf file and...

...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 times and set the IrDA to *COM2* or *COM4* (which select *IRQ 3* with *I/O 0x2f8* or *0x2e8* on *ttyS1* or *ttyS3* - ra3 is the latter). Edit */etc/pcmcia/config.opts* to `*exclude irq 3*' (so that the IRQ is free) and */etc/sysconfig/irda* to set `*DEVICE=/dev/ttyS3*' (or *1*), and run `*chkconfig irda on*' so that it starts on reboot (or `*/etc/rc.d/init.d/irda start*' or `*irattach /dev/...

...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 setup hylafax previously on our existing CentOS-4.5 se...

tried to get the above program running (its a phone managment program for the siemens mobile phones) but it always brings up the error cannot open COM port.I can send AT commands to the phone via the terminal in KPPP. Martin Warby

...t: 0x8000, IRQ: 17 ??? Baud_base: 115200, close_delay: 50, divisor: 0 ??? closing_wait: none ??? Flags: spd_normal skip_test /dev/ttyS2, Line 2, UART: 16550A, Port: 0x8400, IRQ: 17 ??? Baud_base: 115200, close_delay: 50, divisor: 0 ??? closing_wait: none ??? Flags: spd_normal skip_test /dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3 ??? Baud_base: 115200, close_delay: 50, divisor: 0 ??? closing_wait: 3000 ??? Flags: spd_normal I changed the closing_wait: on ttyS1 to match ttyS0, but that didn't do anything, so there must be more to it. Pete -- Unencumbered by the thought...

Hi all! I want to assign a real serialport to my kvm virtual machine via virsh. When I add the following XML snippet to the domain xml, it gets successfully attached but not as I expected it to happen. <serial type='dev'> <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...

...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 crw-rw---- 1 root uucp 4, 66 Dec 6 2007 /dev/ttyS2 crw-rw-...

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 dialout 4, 67 Nov 10 12:18 /dev/ttyS3 By default s...

Hi,. I have some legacy applications for MSDOS / 95 and a new NT version of an application that i would like to use. I have un-commented the lines in wine.conf about serial access but i cant seem to get any MSDOS or win32 application to talk, is this currently supported in (the lateset) wine ? regards --- Matthew J Fletcher NPD Firmware When did ignorance become a point of view ? ---

...\windows" "System" = "c:\\windows\\system" "Temp" = "c:\\temp" "Path" = "c:\\windows;c:\\windows\\system" [serialports] "Com1" = "/dev/ttyS0" "Com2" = "/dev/ttyS1" "Com4" = "/dev/ttyS3" [parallelports] "Lpt1" = "/dev/lp0" [x11drv] "display" = ""

...able) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: serial setserial -g /dev/ttyS* shows this: /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 But, in virt-manage, when I try to add a serial device to the guest as the physical character device /dev/ttyS1 I get this error and the device is not added. XML error: unknown device type Traceback (most recent call last): File "/usr/share/virt-m...

...(irq = 4) is a 16550A ttyS4 at I/O 0x5020 (irq = 177) is a 16C950/954 ttyS5 at I/O 0x5028 (irq = 177) is a 16C950/954 ttyS6 at I/O 0x5030 (irq = 177) is a 16C950/954 ttyS7 at I/O 0x5038 (irq = 177) is a 16C950/954 ttyS1 at I/O 0x5060 (irq = 193) is a 16450 ttyS2 at I/O 0x5068 (irq = 193) is a 16450 ttyS3 at I/O 0x5070 (irq = 193) is a 16450 I have no idea what ttyS1-3 are, but I've tested ttyS4-7 and they work fine. If I only install one card (in either PCI slot 1 or 2) I get the same 4 ports. If I install both cards, ttyS4-7 work on the card that is in PCI slot 2. Any ideas how to ge...

Thanks for the response. No /dev/ttyUSB0. /dev/tty and /dev/tty1 ... /dev/tty63 /dev/ttyS0 ... /dev/ttyS3 but no /dev/ttyUSB0 How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 What ought the major number be? On 2016-10-20 07:33, Charles Lepple wrote: > [please use reply-all to include the list - the headers are not > mangled] > >> On Oct 18, 2016, at 9:02 PM,...

...of bug fixes, improved testsuite coverage, and minor documentation and portability improvements. The wiki has the usual summary of the most notable changes: https://trac.xapian.org/wiki/ReleaseOverview/1.4.23 A big thanks to Robert Stepanek, Germ?n M. Bravo, stark3y, Vivek Pal, Alexei Kharchev, ttyS3, mgautier, xpbxf4, Vaibhav Kansagara, uhuntu, John G. Heim, and James Aylett for helping to make this release a reality. If I've missed anyone out, you can claim an extra big thankyou. As always, if you encounter problems, please report them here, or to the bug-tracker: https://xapian.org/bug...

...e serial port and to pass it to the guest. On the host, ls -l /dev | grep ttyS, returns: crw-rw---- 1 root uucp 4, 64 Jul 6 10:17 ttyS0 crw-rw---- 1 root uucp 4, 65 Jul 6 10:17 ttyS1 crw-rw---- 1 root uucp 4, 66 Jul 6 10:17 ttyS2 crw-rw---- 1 root uucp 4, 67 Jul 6 10:17 ttyS3 It only has 1 serial port so I don't know why ttyS1-S3 are listed. On the guest it says that Com1 is configured and working properly. On the Virtual Machine Hardware tab of the guest it lists a Serial 0. Details: Serial Device (Priamary Console) Device Type: pty Target Port: 0 Source Path: /d...

...ib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) then ok. lpinfo -v gives: network socket network http network ipp network lpd direct parallel:/dev/lp0 direct scsi serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS1?baud=115200 serial serial:/dev/ttyS2?baud=115200 serial serial:/dev/ttyS3?baud=115200 serial serial:/dev/ttyS4?baud=115200 serial serial:/dev/ttyS5?baud=115200 serial serial:/dev/ttyS6?baud=115200 ----------------------------------------------- serial serial:/dev/ttyS29?baud=115200 serial serial:/dev/ttyS30?baud=115200 serial serial:/dev/ttyS31?baud=115200 direct usb:/de...

...0, close_delay: 50, divisor: 0 > ??? closing_wait: none > ??? Flags: spd_normal skip_test > > /dev/ttyS2, Line 2, UART: 16550A, Port: 0x8400, IRQ: 17 > ??? Baud_base: 115200, close_delay: 50, divisor: 0 > ??? closing_wait: none > ??? Flags: spd_normal skip_test > > /dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3 > ??? Baud_base: 115200, close_delay: 50, divisor: 0 > ??? closing_wait: 3000 > ??? Flags: spd_normal > > I changed the closing_wait: on ttyS1 to match ttyS0, but that didn't > do anything, so there must be more to it. > > P...