<snip>
> 8. Finally I tried this:
>
> root@ibmtop:pts/0 ~ # chmod 777 /dev/ttyS[01]
> root@ibmtop:pts/0 ~ # setserial -av -z /dev/ttyS0 port 0x03f8 auto_irq autoconfig
> /dev/ttyS0, Line 0, UART: unknown, Port: 0x03f8, IRQ: 4
> Baud_base: 115200, close_delay: 50, divisor: 0
> closing_wait: 3000, closing_wait2: infinite
> Flags: spd_normal auto_irq
>
> root@ibmtop:pts/0 ~ # cu -l /dev/ttyS0
> Connected.
> cu: Got hangup signal
>
> Disconnected.
The problem is not in the serial driver, neither with your notebook, but
with the cu application (AFAIK). If you tried minicom, it would have
probably work with the previous permissions. cu requires the device to be
accessible by the uucp group. A permission set that works with everything
I tried (as I found out from Red Hat 6.0), including cu, is:
[ivan@kelly ivan]$ ls -l /dev/ttyC0
crw-rw---- 1 uucp uucp 19, 0 jun 28 17:15 /dev/ttyC0
I'm showing a Cyclades serial port device, but if you change the
permissions on the standard serial port to those (actually, this is how it
is on Red Hat 6.0), then cu will work fine.
Hope it helps.
Regards,
Ivan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/