similar to: /dev/ttyS1 on Xen (domain 0)

I have been struggling with setting up two serial ports on an HP/Compaq D512S (Intel P4) under CentOS-5. I am not at all sure why these things were not auto-configured when I initially installed the CentOS system from CDs but they were not. I have found various 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

I am a 62 year old beginner in Ubuntu. Thanks for any help, guidance, suggestions on this problem! I have used commands like the following to be certain that I have an active com port: dmesg | grep ttyS rm com1 ln -s /dev/ttyS0 com1 So I suspect the solution lies somewhere in WINE. If all else fails I will get a USB to SERIAL converter cable and try that. My wife has an Abbott Labs Freestyle

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

Hi all, I have a question on /etc/inittab for DomU booted with xencons parameter. I saw the following error messages when I appended xencons=ttyS to DomU boot option. INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187. (Should be identical to this patch from last

Hi all I have a problem switch in our data centre, which is connected to a linux server via a serial cable. I know I can / could access the switch from my Windows PC back at the office, using hyperterm, but trying to access it using minicom just doesn't seem to work. I have changed the comms in minincom to use /dev/tty0 & the baud rate to 9600, yet I can't seem to connect with

I have installed two 4-port serial cards (http://www.startech.com/ Product/ItemDetail.aspx?productid=PCI4S550&c=US) on a CentOS 4.4 system. The hardware appears to be recognized correctly, as kudzu added 2 entries to /etc/sysconfig/hwconf and lscpi shows both cards (output of lspci -vv for both cards included at the end of this email): # lspci 00:00.0 Host bridge: Intel Corporation

CentOS-6.2 We have a dedicated CentOS-5.7 host used for fax reception and transmission that we wish to move to a CentOS-6.2 virtual guest instance. The CentOS-6.2 virtual host has a 4-port serial card installed. lspci -v tshows this this: 03:00.0 Serial controller: Oxford Semiconductor Ltd OX16PCI954 (Quad 16950 UART) function 0 (Uart) (prog-if 06 [16950]) Subsystem: Oxford

Hi people. I'm trying to config a: MGE ELISE PREMIUM 1200 NT 02 Serial Nr. 92HE04008 With its serial cable into /dev/ttyS0. I had configured ups.conf, with no luck. Here is my ups.conf: [upscura] driver = mge-shut port = /dev/ttyS0 desc = "UPS" The permissions into /dev/ttyS?: crw------- 1 nut nut 4, 64 mar 8 18:43 /dev/ttyS0 crw------- 1 nut nut 4, 65 mar 8 18:42

Hi there, I am using an old (really old) APC Smart-UPS 600. It worked fine under apcupsd but when I tried NUT it did not work. The error I was getting was: sudo /lib/nut/apcsmart -DDD /dev/ttyS1 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 debug level is '3' Attempting firmware lookup Firmware: [D4] Not found in

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

Hello xen-users ! I am coming for help concerning the just released 4.0 version. Install has worked rather well on my Debian Lenny. I have just had a few bugs for which I have found the answer looking around on this list. I have created a Debian Lenny domU which boots up just fine. The only problem is that I am unable to get a console prompt when using "xm console nameofdomU". I do see

I recently bought a new UPS, and I''m attempting to use nut to monitor it. Following setup instructions everything seemed to go well until it came to testing the connection, which failed. There is just one serial connector on the computer, so I set it to monitor /dev/ttyS0. Either that is wrong, or communication is failing. I''ve been told to try minicom to monitor it,

> > I can see how you could start a very simple VGA-only Xserver -- by > > default dom0 happens to have access to the bottom 1MB of > memory, which > > is enough to get a VGA Xserver working. > > OK, I wasn''t familiar with this. However I''ve checked > XFree86.0.log from domain 0 for memory reports, and these two > lines indicate more than

Hi all, When i do ''xm dmesg'' the last statement says "*** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen)" (i have no clue what''s that supposed to mean??) But when i press ctrl-a three times at the serial console, nothing happens. Iam using minicom to connect to the serial port of xen machine. Once xen

Hi, Is vfb working well lately? I thought I''d test it out on ia64 and it works great, but only once per boot. If I stop the domain and restart it, I get the following: Error: Device 0 (vkbd) is already connected. To make sure this isn''t an ia64 anomaly, I tried it on an x86_64 system. Same thing, works the first time, reboot the domain and it''s broken. I see

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: Of course I created

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

I am running Ubuntu 6.06 connected via serial port to an MGE Pulsar Ellipse 800VA. Have just installed NUT 2.0.3, and have problems with connectivity. This UPS was workign via serial connectivity 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,

Hello Can anyone share a known working config for xen which would transfer a serial interface ( add-on card preferably, mine uses e880-e887 : 0000:03:05.0 / ec00-ec07 : 0000:03:05.0 ) to a DomU ? I've been trying with the stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial