search for: ttys0

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at kirkonmaki:/home/juuri# upsdrvctl -u root start Network UPS Tools - UPS driver controller 2...

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at kirkonmaki:/home/juuri# upsdrvctl -u root start Network UPS Tools - UPS driver controller 2...

A new kvm guest on a CentOS6.5 x84_64 host is set up to make use of the serial port (virt-install ... --serial dev,path=/dev/ttyS0) <serial type='dev'> <source path='/dev/ttyS0'/> <target port='0'/> </serial> <console type='dev'> <source path='/dev/ttyS0'/> <target type='serial' port='0'/>...

This change updates a guest which uses Xen's xvc0 to use ttyS0 instead. In a related change, it also makes a console a 'standard device' will always be configured. --- lib/Sys/VirtV2V/Converter.pm | 5 +++- lib/Sys/VirtV2V/Converter/Linux.pm | 46 ++++++++++++++++++++++++++++++++++++ 2 files changed, 50 insertions(+), 1 deletions(-) diff -...

Hi all, I hope this is possible. I have a server, with a network switch attached to the serial port, and I want to rescan the serial port (/dev/tty) to see if it picks it up? I'd prefer not to reboot the server if at all possible. dmesg reports ttyS0 as the active port: [root at zabackup01 ~]# dmesg |grep tty Bootdata ok (command line is ro root=/dev/System/root rhgb quiet xencons=tty6) Kernel command line: ro root=/dev/System/root rhgb quiet xencons=tty6 WARNING: Failed to register Xen virtual console driver as 'tty1' serial8250: ttyS...

Hello! I got my hands on a CyberPower 1500AVRT, and i'm trying to get it connected to my Gentoo machine. I've followed all the basic guides on setting up NUT and UPS' but have had no luck. My current ups.conf is: [cyberpower-gentoo] driver = cyberpower port = /dev/ttyS0 desc = Workstation Upon running /etc/init.d/upsd start or upsdrv start I get: * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.2.0 Network UPS Tools - CyberPower driver 1.00 (2.2.0) Giving up on hardware detection after 3 tries Unable to get initial hardware info s...

...d to try NUT. The smartups driver can't make contact through the serial port. Since this is rack-mounted, it comes with a 940-1524 serial cable. As far as I can tell, this is supposed to work with smart signaling. Here's my ups.conf: [myups] driver = apcsmart port = /dev/ttyS0 cable = 940-0095B sdtype = 0 Here's a session which illustrates the problem: [root]# ls -l /dev/ttyS0 crw------- 1 nut nut 4, 64 Jun 4 14:28 /dev/ttyS0 [root]# /usr/local/nut/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools (version 2.0....

I am having trouble installing nut-2.0.2-1.x86_64.rpm nut-client-2.0.2-1.x86_64.rpm the service run as nut:nut, but /dev/ttyS0 is owned by root:uucp I can chown nut:nut /dev/ttyS0, but the owner changes on reboot. /etc/security/console.perms looks like to me that it only applies to user logins I have searched the web & found several how-tos, but most are at least a year old and do not seem to address this issue. Q:...

H. Peter Anvin dixit: >But is that really a tty, then? I also understand that virtio console Hm. Both eglibc and dietlibc return true for isatty on it. >doesn't support termios, which makes this an ugly bifurcation. All of Let me test that? quick? hah not really (CONFIG_VIRTIO_CONSOLE=m)? ok luckily Ubuntu?s linux-image-3.15.0-5-generic is installable on Debian stable and has

...setup failure? stty tells me that the driver sets speed to 2400baud, but does that mean that the driver can establish a connection to the device? How to tell? If I interpreted other posts correctly, I should be able to use a terminal program to access the UPS device. So I started minicom -D /dev/ttyS0 (without and with " -b 2400" or " -b 9600") and tried to enter "Q1 \r" but I don't even get a local echo. So what does that mean and what else can I try? Thank you for your ideas and hints! Olav P.S.: Once it works, should I contribute my values to https://githu...

...therLink 5.7.1, I try to communicate via COM1 but the program can't find it and even not test with a loop plug in COM1. I have changed the mode to 0777 for the serial devices in /etc/udev/rules.d/50-udev-default.rules and rebooted. /home/sel/.wine/dosdevices reveal that com1 is linked to /dev/ttyS0 with total permission for all. Testing ttyS0 with a little test program with the dongle show the serial port is working. The same port with same WeatherLink 5.7.1 but booted in Windows 2000 on the same machine works fine. Any suggestions ? Thanks.

...might be desirable to have the klibc shell do some dancing (perhaps controlled by some flags, but on by default?) If getpid() == 1 then fork a child, continue in the child, have the parent wait for the child to terminate, then exit child should setsid() close(2) close(1) close(0) open("/dev/ttyS0", O_RDONLY) open("/dev/ttyS0", O_WRONLY|O_NOCTTY) open("/dev/ttyS0", O_WRONLY|O_NOCTTY) And /dev/ttyS0 should either be /dev/console or specified on commandline, or parsed out of kernel command line console= string. Just loose ideas.

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

Not the same as the other treath, but also an tty access problem. I have an old an cheap digital camera wich isn't supported by gphoto(2). I can get the program running under wine only it shows me: err:dosfs:DOSFS_CreateCommPort Couldn't open /dev/ttyS0,115200 ! (check permissions) err:file:CreateFileA Couldn't open device 'COM1'! FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock err:comm:OpenComm16 Couldn't open /dev/ttyS0 ! (Success) In my .wine/config file I have: [serialports] "Com1" = "/dev/ttyS0,115200&...

Hello, I've got RFID card reader plugged in serial port. cat /dev/ttyS0 ...gives me ID of the card I'm using => that's OK As soon as I open the port with win32 appication via wine... I get no data from reader. Even cat /dev/ttyS0 does not work anymore afterwards. I thinks it's because as soon as application opens it via wine some tty flags change: (PS...

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

...d through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen 4.1 and Linux kernel 3.2.0 the passthrough seems to work as well (/dev/ttyS0 appears in dmesg of DomU), but something is wrong. The GSM modem doesn't behave as expected. The smstools daemon errors out with 'Cannot open serial port /dev/ttyS0, error: Function not implemented'. It took me hours to find the difference, but it seems like the guest (domU) kernel is...

...d through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen 4.1 and Linux kernel 3.2.0 the passthrough seems to work as well (/dev/ttyS0 appears in dmesg of DomU), but something is wrong. The GSM modem doesn't behave as expected. The smstools daemon errors out with 'Cannot open serial port /dev/ttyS0, error: Function not implemented'. It took me hours to find the difference, but it seems like the guest (domU) kernel is...

Hello, ? I'm trying to configure my system such that I have a TCP port listening which will send all data it receives to a serial port. ie:?? tcp/2112? -->? /dev/ttyS0 My goal would be to be able to: Use netcat to create the listen and redirect to a serial port: ? $ nc -l 2112 > /dev/ttyS0 Then in another window, run minicom at /dev/ttyS0 Then in a 3rd window, ? $ telnet localhost 2112 ?"Type things, hello world" But, I can never get the text to...

The following patches add RHEL 6 guest support to virt-v2v. This was actually quite a lot easier than I expected. * [PATCH 1/4] Update virt-v2v.conf for RHEL 6 virtio support * [PATCH 2/4] Check kudzu exists before attempting to disable it * [PATCH 3/4] Use dracut rather than mkinitrd if it's available * [PATCH 4/4] Properly convert RHEL 6 guest console