search for: ttys1

...Password: [SOL Session operational. Use ~? for help] ?????????? 10.0.0.14 is the DRAC IP address of the CentOS 6.3 box. It accepts the password and connects me to the console but then when I type I get those funny characters. Somehow an agetty is already being run: root 46110 1 0 16:13 ttyS1 00:00:00 /sbin/agetty /dev/ttyS1 19200 vt100-nav Is udev starting this up for me somehow? It says 19200 when everything I have read says it should be 115200. How do I change this? Some docs say I should create my own /etc/init/serial-ttyS1.conf containing: # For IPMI serial console # ttyS1 - a...

Hi, I need to add one line to /etc/securetty, say it needs to be ttyS1. Do not add it if ttyS1 already exists in file /etc/securetty. How to achieve this using puppet module in puppet 2.5? This file is different than the other examples using augeas, this one only has value per line, not name-val pair. Thanks, Hai -- You received this message because you are subscr...

...hine there are 76 device file for /dev/ttyS*. I tried running minicom on a Xen machine (domain 0) whose serial port is connected to a different machine (a machine with no VGA/Keyboard/Mouse). It gave the following error: minicom: WARNING: configuration file not found, using defaults Device /dev/ttyS1 access failed: No such file or directory. So I checked, and ls /dev/ttyS* -al gave only one device file: crw-rw---- 1 root uucp 4, 64 Apr 3 13:05 /dev/ttyS0 My question is : Is there a possibility to run minicom on domain 0 on Xen? I also tried adding that device,( which udev didn''t c...

...powermust 600usb (connected via com-port), I can't make it work. Got NUT installed via aptitude in ubuntu feisty and a basic setup, exactly the same as for the apc, except for the name of the ups and the corresponding section of ups.conf -- [mustek] driver = megatec port = /dev/ttyS1 desc = "Mustek PowerMust 600USB" -- # upsc mustek at localhost Error: Driver not connected Tried changing the port value to ttyS1, but this won't work either. Any suggestions? Thanks.

...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 ports, and I've already tried several >> different serial cards several of the slots on the motherboard all >> have yielded the same result.? I've even gone so far as to try to >> get this to work...

...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 ports, and I've already tried several different serial cards several of the slots on the motherboard all have yielded the same result.? I've even gone so far as to try to get this to work on another computer running C7 with the same res...

Hi List, I just got myself a new everpower-1000va. according to the compatibility list, the 'safenet' driver supposed to support it, however, when I try, I get this in syslog: Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000] (safenet-ttyS1): No such file or directory this is my ups.conf: [everpower1000] driver = safenet port = /dev/ttyS1 desc = "firefang.net" I am using nut installed via apt on debian-etch. any suggestions? Omry.

...sted 5 cables, but none works. whereas I'm not sure if it is a cable problem. this is what dmesg says when booting (with 2 onboard ports). OS is Centos 5.3: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing 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 Linux helios 2.6.18-128.2.1.el5 #1 SMP Tue Jul 14 06:39:56 EDT 2009 i686 i686 i386 GNU/Linux - the dealer says its not a cable problem and handed me a digitus pci car...

I've been playing with centos 6. Sometimes it gets into a mode when it "seems" like it hangs at boot. At reboot I hit ALT-D for details and the last thing printed is Starting atd. No I can press alt-f2 to get a login. Doing ps ax does not show a mingetty tty1, What might be going on here. What isn't completing to get a full boot. Thanks, Jerry

...iguration went smooth and the megatec driver recognized the ups and all was working fine. So i reconnected the server to the ups. And at start-up i started to receive some weird messages that warned me the connection to the ups was lost. The ups is connected to the server through a serial cable on ttyS1. Here's what's happening when i try to start the ups daemon: [root at corporate log]# [root at corporate all]# service ups start Starting megatec: Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c) 2003-2006 Megatec protocol UPS detected [ Pro 1400 4.01p]....

...iguration went smooth and the megatec driver recognized the ups and all was working fine. So i reconnected the server to the ups. And at start-up i started to receive some weird messages that warned me the connection to the ups was lost. The ups is connected to the server through a serial cable on ttyS1. Here's what's happening when i try to start the ups daemon: [root at corporate log]# [root at corporate all]# service ups start Starting megatec: Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c) 2003-2006 Megatec protocol UPS detected [ Pro 1400 4.01p]....

...9;ve found out that it's actually a CyberPower 1500 AVR LCD. I'm using it with the serial cable. I'm unable to get it working with any of the drivers provided with NUT. I've tried cpsups, cyberpower and powerpanel. here's the output of the different drivers ./cpsups -DDD /dev/ttyS1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. debug level is '3' ups_sync: send [\rP4\r] ups_sync: got ret -1 [] ups_sync: send [\rP4\r] ups_sync: got ret -1 [] ups_sync: send [\rP4\r]...

...ich 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 ports, and I've already tried several > >>different serial cards several of the slots on the motherboard all > >>have yielded the same result.? I've even gone so far as to try to >...

...in after mains returns. As this works with Personal Solution-Pac 2 on W2k I thought that there might be a way to achieve it with nut, too. However, after trying "everything", I don't know any further. My ups.conf: driverpath = /bin [Pulsar1000] driver = mge-shut port = /dev/ttyS1 offdelay = 120 # mge-shut: ondelay in s * 10 ondelay = 15 desc = tfp-3 Manually set cold start disabled automatic restart enabled energy savings disabled Any ideas? Thanks for your answers. Axel

...onnectivity to a BSD system only a few days ago. I have followed the instructions at http://opensource.mgeups.com/install/debian.htm The details... jason@ubuntu:~$ ls -la /dev/ttyS? crw-rw-rw- 1 root dialout 4, 64 2006-05-15 22:18 /dev/ttyS0 crw-rw-rw- 1 root dialout 4, 65 2006-05-14 22:12 /dev/ttyS1 jason@ubuntu:~$ grep -i nut /etc/group dialout:x:20:jason,nut nut:x:117: jason@ubuntu:~$ grep -i nut /etc/passwd nut:x:107:117::/var/lib/nut:/bin/false jason@ubuntu:~$ ls -la /etc/nut/ -rw-r----- 1 root nut 3769 2006-05-15 21:30 ups.conf -rw-r----- 1 root nut 1407 2006-05-15 20:26 upsd.conf...

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 dialou...

...resources on the web and from them uncovered the setserial 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 dev...

...s just a matter of following the (very good) INSTALL instructions provided in the tarball. Although I haven't got the hotplug scripts working yet (the samples provided are not a good fit on a FC3 system) I got around this by setting the perms (640) and ownership (nut:nut) manually for both /dev/ttyS1 and /proc/bus/usb/xxx/yyy (xxx/yyy obtained from lsusb). I suspect I will have to redo this last step after every reboot but that's not real prob as reboots happen very infrequently (even more so now I have this UPS hopefully). I will post the new hotplug scripts/instructions once I work it out...

Hi, I have a little problem with PowerCom BNT600AP after running driver I see: root@rask> powercom -D /dev/ttyS1 Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.2) debug level is '1' Values of arguments: manufacturer : 'PowerCom' model name : 'Unknown' serial number : 'Unknown' line voltage :...

...running NUT 2.6.3 on Debian wheezy [ with a 3.3.0 i686 kernel ] I've installed NUT via Debian APT [ package nut version 2.6.3-1 ] I have a REDi Blazer 600VA (BLAZER600c) UPS and I want to detect power failures. I have tried the following drivers: * gamatronic: Can't talk to UPS on port /dev/ttyS1! * bestups: Unable to detect a Best/SOLA or Phoenix protocol UPS * blazer_ser: No supported UPS detected I have also tried genericups with upstype=4, upstype=13, then I set OL to -DCD, then to -RNG, with no change when I cut the power Then I restored the power and ran statserial, which showed [*]...