Fedora Core 5: # cat /dev/ttyS0 error - Hardware

This is a discussion on Fedora Core 5: # cat /dev/ttyS0 error - Hardware ; Hi. I'd like to use the smart-card reader/writer that I have, it connects to a RS-232 Serial port. the Applications for that device work fine on an old Laptop with such RS-232 port, but not on my desktop computer. when ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Fedora Core 5: # cat /dev/ttyS0 error

  1. Fedora Core 5: # cat /dev/ttyS0 error

    Hi.

    I'd like to use the smart-card reader/writer that I have, it connects to
    a RS-232 Serial port.

    the Applications for that device work fine on an old Laptop with such
    RS-232 port, but not on my desktop computer.

    when I try to read that port, I get an error message:

    # cat /dev/ttyS0
    cat: /dev/ttyS0: Input/output error

    I do it as root, and I do have read and write permission.

    how do I get rid of that error?

    please help,

    --polemon

    --
    -EOF-

  2. Re: Fedora Core 5: # cat /dev/ttyS0 error

    On Sun, 13 May 2007, in the Usenet newsgroup comp.os.linux.hardware, in article
    <5ap874F2pbgp4U1@mid.uni-berlin.de>, polemon wrote:

    >when I try to read that port, I get an error message:
    >
    ># cat /dev/ttyS0
    >cat: /dev/ttyS0: Input/output error
    >
    >I do it as root, and I do have read and write permission.


    Serial port isn't there. /dev/ttyS0 exists, but the kernel can't see
    the hardware. Start by looking at '/var/log/messages' to see if the
    kernel is using the serial driver. I'm NOT using Fedora, but on an
    older Red Hat system, this would look like this:

    Aug 21 16:23:27 Serial driver version 5.05c (2001-07-08) with MANY_PORTS
    SHARE_IRQ SERIAL_PCI ISAPNP enabled
    Aug 21 16:23:27 ttyS0 at 0x03f8 (irq = 4) is a 16550A
    Aug 21 16:23:27 ttyS1 at 0x02f8 (irq = 3) is a 16550A
    Aug 21 16:23:27 ttyS2 at 0x03e8 (irq = 4) is a 16550A

    My guess is you won't find any indication of the device in that file. If
    it's been a while since you booted, you may also find this but without
    the timestamps in the _FILE_ /var/log/dmesg (which is the output of the
    dmesg command that was run _at_ the last boot).

    >how do I get rid of that error?


    I dunno.

    Old guy

  3. Re: Fedora Core 5: # cat /dev/ttyS0 error

    After looking at /var/log/messages for signs of life form the serial
    driver, you might try a 'statserial /dev/ttyS0'. Also make sure
    that you're not running a agetty on /dev/ttyS0 (started from inittab).
    Seems like a longer shot, but it's possible that if you've rebuilt
    the kernel, you *removed* support for the serial driver. If so,
    rebuild the kernel with the support turned back on.

    My serial lines in messages look like:
    May 14 13:02:30 myhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    May 14 13:02:30 myhost kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 68 port
    s, IRQ sharing enabled
    May 14 13:02:30 myhost kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    May 14 13:02:30 myhost kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

    I have CONFIG_SERIAL_8250=y in my .config for kernel builds.

    -bc


    In article ,
    Moe Trin wrote:
    >
    >
    >On Sun, 13 May 2007, in the Usenet newsgroup comp.os.linux.hardware, in article
    ><5ap874F2pbgp4U1@mid.uni-berlin.de>, polemon wrote:
    >
    >>when I try to read that port, I get an error message:
    >>
    >># cat /dev/ttyS0
    >>cat: /dev/ttyS0: Input/output error
    >>
    >>I do it as root, and I do have read and write permission.

    >
    >Serial port isn't there. /dev/ttyS0 exists, but the kernel can't see
    >the hardware. Start by looking at '/var/log/messages' to see if the
    >kernel is using the serial driver. I'm NOT using Fedora, but on an
    >older Red Hat system, this would look like this:
    >
    > Aug 21 16:23:27 Serial driver version 5.05c (2001-07-08) with MANY_PORTS
    > SHARE_IRQ SERIAL_PCI ISAPNP enabled
    > Aug 21 16:23:27 ttyS0 at 0x03f8 (irq = 4) is a 16550A
    > Aug 21 16:23:27 ttyS1 at 0x02f8 (irq = 3) is a 16550A
    > Aug 21 16:23:27 ttyS2 at 0x03e8 (irq = 4) is a 16550A
    >
    >My guess is you won't find any indication of the device in that file. If
    >it's been a while since you booted, you may also find this but without
    >the timestamps in the _FILE_ /var/log/dmesg (which is the output of the
    >dmesg command that was run _at_ the last boot).
    >
    >>how do I get rid of that error?

    >
    >I dunno.
    >
    > Old guy




  4. Re: Fedora Core 5: # cat /dev/ttyS0 error

    On 05/14/2007 10:02 PM, Moe Trin wrote:

    > Serial port isn't there. /dev/ttyS0 exists, but the kernel can't see
    > the hardware. Start by looking at '/var/log/messages' to see if the
    > kernel is using the serial driver.


    > My guess is you won't find any indication of the device in that file. If
    > it's been a while since you booted, you may also find this but without
    > the timestamps in the _FILE_ /var/log/dmesg (which is the output of the
    > dmesg command that was run _at_ the last boot).


    You were right, the hardware was deactivated in BIOS.

    >>how do I get rid of that error?

    >
    > I dunno.


    lol?


    --polemon
    --
    -EOF-

  5. Re: Fedora Core 5: # cat /dev/ttyS0 error

    On 05/15/2007 01:50 AM, Time Waster wrote:
    > After looking at /var/log/messages for signs of life form the serial
    > driver, you might try a 'statserial /dev/ttyS0'. Also make sure
    > that you're not running a agetty on /dev/ttyS0 (started from inittab).


    Hmm, I actually considered having a terminal attached to RS-232 someday...

    Like I said in the reply to Moe Trin, my hardware was deactivated in
    BIOS... (pretty weird standard setting, eh?)


    Thanks for your help, though

    --polemon

    --
    -EOF-

+ Reply to Thread