Channel /dev/ttys0 Input/output Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss
Ttys0 Tcgetattr Input Output Error
the workings and policies of this site About Us Learn more linux serial port about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix &
Minicom
Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top cat /dev/ttyS0 Input/output error up vote 2 down vote favorite I created infrared receiver as in LIRC manual (http://www.lirc.org/receivers.html). And tested it on windows using program called Terminal. When I switched on RTS pin DCD pin was also switched on and when I used remote controll DCD was blinking. So everything works with hardware. Next I tried using the same hardware on Linux Mint 17 on same computer as in http://lifehacker.com/5527752/control-your-desktop-pc-with-a-remote-using-lirc but with no luck: piotrek-H87-HD3 piotrek # cat /dev/ttyS0 cat: /dev/ttyS0: Input/output error I also followed http://www.commandlinefu.com/commands/view/10218/ttys0-terminal-on-serial-connection. In this tutorial there was the same error I had so I tried looking in BIOS setup but serial ports were enabled. Why isin't it working? Some information data: piotrek-H87-HD3 piotrek # cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:16550A port:000003F8 irq:4 tx:0 rx:0 1: uart:unknown port:000002F8 irq:3 2: uart:unknown port:000003E8 irq:4 3: uart:unknown port:000002E8 irq:3 4: uart:16550A port:0000F080 irq:19 tx:34 rx:0 CTS|DSR|CD 5: uart:unknown port:00000000 irq:0 6: uart:unknown port:00000000 irq:0 7: uart:unknown port:00000000 irq:0 8: uart:unknown port:00000000 irq:0 ... //EDIT I was wondering lately if maybe linux somehow switched pin layout of my serial port? My motherboard COM port pins layout is : I have back panel extension cord which maps 1:1 pin layout from motherboard
port General support questions including new installations Post Reply Print view Search Advanced search 9 posts • Page 1 of 1 mahlenius Posts: 28 Joined: 2007/11/06 20:13:50 configuring /dev/ttyS0 port Quote Postby mahlenius » 2008/02/02 21:09:37 Hi,my /dev/ttyS0 port is not working - as far as I can tell. This is the only serial port on this machine (Dell tower)This is the first time I have tried to use it on this machine and I cannot get it working. I have used minicom and it won't communicate to my external device. On my laptop, which is also running Centos 5, the port works fine to my external device. I have the same http://unix.stackexchange.com/questions/192075/cat-dev-ttys0-input-output-error minicom port settings (speed, baud,,etc), but itstill will not work.Is there anything else I need to do to enusre the port is setup in the OS for usage?I did try to do a setserial cmd, but got:# setserial -a /dev/ttyS0Cannot get serial info: Invalid argumentnot sure if this helps, but something does not seem right....thanks'mark Top AlanBartlett Forum Moderator Posts: 9296 Joined: 2007/10/22 11:30:09 Location: ~/Earth/UK/England/Suffolk Contact: Contact AlanBartlett Website configuring /dev/ttyS0 port Quote http://www.centos.org/forums/viewtopic.php?t=10753 Postby AlanBartlett » 2008/02/02 22:28:01 Is the port enabled in the BIOS?On my system, with two physical RS-232 ports both enabled in the BIOS, this is what I see:# ls -l /dev/ | grep ttyScrw-rw-rw- 1 root tty 4, 64 Jan 31 10:13 ttyS0crw-rw-rw- 1 root tty 4, 65 Jan 31 10:13 ttyS1crw-rw---- 1 root uucp 4, 66 Jan 31 10:13 ttyS2crw-rw---- 1 root uucp 4, 67 Jan 31 10:13 ttyS3# stty < /dev/ttyS0speed 9600 baud; line = 0;-brkint -imaxbel# stty < /dev/ttyS1speed 9600 baud; line = 0;-brkint -imaxbel# stty < /dev/ttyS2stty: standard input: Input/output error# stty < /dev/ttyS3stty: standard input: Input/output error# This is entirely expected behaviour.HTH.Alan. Top mahlenius Posts: 28 Joined: 2007/11/06 20:13:50 Re: configuring /dev/ttyS0 port Quote Postby mahlenius » 2008/02/02 22:37:39 Hi,I have one follow up to the setserial command. I looked in the /var/log/messages file and found that it looks like it has something named a Xen virtual console installed on /dev/ttyS0also it looks like something isn't right in the serial port setup:Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabledFeb 1 14:02:04 daniel kernel: 8250_pnp: Unknown symbol serial8250_unregister_portFeb 1 14:02:04 daniel kernel: 8250_pnp: Unknown symbol serial8250_register_port# This is the default serial port on a Dell Dimension 2200 and I did not do anything specific during installation to enable it. Should I hav
fully installed and functional MythTV backend server. There were two things wrong with the Channel Changer program. I didn't know that the current directory is not in your path. SO-just because http://fourthlaw.com/mythtv-is-up-and-running-changing-channels-via-serial-cable/ you are in the same directory as a binary file, it can still be "unfound." When I typed in /usr/local/bin/channel to define the path explicitly it worked-I should have tried that. I probably http://www.crynwr.com/cgi-bin/ezmlm-cgi/2/5316 would have, but I was pressed for time that day. Once I could get the channel binary to work, then I faced a different issue. By using the -p switch on the channel output error changer program, the individual serial ports can be specified. Here's what I got: /dev/ttyS0 - Input / Output Error /dev/ttyS1 - No communciation /dev/ttyS2 - Input / Output Error /dev/ttyS3 - Input / Output Error Great. What now? I found several postings on the web talking about the dialout group-but I checked and my user account was already in that group. I was pretty sure that the channel /dev/ttys0 input/output serial cable to the Motorola box was hooked up to COM1 (/dev/ttyS0) so I thought I better do some more investigation. I found this tidbit: http://www.linuxquestions.org/questions/linux-hardware-18/cat-devttys0-inputoutput-error-397212/ Which instructed me more perfectly in the way of the SETSERIAL command. I ran SETSERIAL -a for each port and got the following info: /dev/ttyS0, Line 0, UART: , Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 500, divisor: 0
closing_wait: 30000
Flags: spd_normal /dev/ttyS1, Line 0, UART: 16550A, Port: 0x02f8, IRQ: 3
Baud_base: 115200, close_delay: 500, divisor: 0
closing_wait: 30000
Flags: spd_normal /dev/ttyS2, Line 0, UART: , Port: 0x03e8, IRQ: 4
Baud_base: 115200, close_delay: 500, divisor: 0
closing_wait: 30000
Flags: spd_normal /dev/ttyS3, Line 0, UART: , Port: 0x03e8, IRQ: 3
Baud_base: 115200, close_delay: 500, divisor: 0
closing_wait: 30000
Flags: spd_normal Wow. Do you see what I saw? Three out of four of my serial ports aren't detecting the UART. I can understand COM3 and COM4 not being there-they were not setup in the computer's BIOS, but COM1 and COM2 should be fine. A quick shutdown and boot to CMOS configuration proved my memory to be correct-but obviously there was something
+0100 Mon, 22 Mar 1999 23:16:48 +0100 Cornelius Creedon a écrit : > but later in the log it is corrected. > > at this point you are having a ppp problem. mgetty certainly seems to be > doing okay. Can you help me ? This is what my /var/log/messages looks like : Mar 22 20:09:17 server kernel: CSLIP: code copyright 1989 Regents of the University of California Mar 22 20:09:17 server kernel: PPP: version 2.2.0 (dynamic channel allocation) Mar 22 20:09:17 server kernel: PPP Dynamic channel allocation code copyright 1995 Caldera, Inc. Mar 22 20:09:17 server kernel: PPP line discipline registered. Mar 22 20:09:17 server kernel: registered device ppp0 Mar 22 20:09:17 server pppd[755]: pppd 2.3.5 started by root, uid 0 Mar 22 20:09:18 server pppd[755]: Connect script failed Mar 22 20:09:19 server pppd[755]: Exit. Mar 22 20:09:19 server mgetty[638]: tcgetattr failed: Input/output error Mar 22 20:09:19 server mgetty[638]: tcsetattr failed: Input/output error Mar 22 20:09:29 server mgetty[638]: tcsetattr failed: Input/output error Mar 22 20:09:45 server init: Re-reading inittab Mar 22 20:09:45 server mgetty[757]: failed dev=ttyS0, pid=757, got signal 15, exiting Mar 22 20:10:01 server pppd[764]: pppd 2.3.5 started by root, uid 0 Mar 22 20:10:02 server pppd[764]: Connect script failed Mar 22 20:10:03 server pppd[764]: Exit. Mar 22 20:10:18 server init: Re-reading inittab Mar 22 20:11:07 server mgetty[768]: data dev=ttyS0, pid=768, caller='none', conn='', name='', cmd='/etc/ppp/pppd', user='/AutoPPP/' Mar 22 20:11:07 server mgetty[768]: cannot execute '/etc/ppp/pppd': No such file or directory Mar 22 20:11:16 server kernel: PPP: ppp line discipline successfully unregistered Mar 22 20:12:58 server mgetty[773]: data dev=ttyS0, pid=773, caller='none', conn='', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/' Mar 22 20:12:58 server kernel: CSLIP: code copyright 1989 Regents of the Un