solved, but not fixed.
cu always sets hardware flow control, and there is no way of controlling this behaviour. this was already a known problem in 1995:...
Type: Posts; User: ummelum; Keyword(s):
solved, but not fixed.
cu always sets hardware flow control, and there is no way of controlling this behaviour. this was already a known problem in 1995:...
final bump & goodbye!
bump.
later this week, i'm going to boot old live cd's of ubuntu, to pinpoint when this problem exactly cropped up.
if that doesn't bring any enlightenment or solution, ubuntu goes out the door...
$ cu -l /dev/ttyS0 -s 115200 --debug all
cu: fconn_open: Opening port /dev/ttyS0 (speed 115200)
cu: fconn_set: Changing setting to 0, 0, 2
Connected.
~.cu: Exit status 0
cu: fconn_close:...
let's bump this thread by stating, in bold, that it has more than five hundred views, and not a single reaction :)
$ sudo ls -al /dev/ttyS?
crw-rw---- 1 root dialout 4, 64 Dec 8 10:05 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 Dec 8 10:05 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 Dec 8 10:05 /dev/ttyS2...
i just made user 'root' part of the groups tty, dialout and uucp. using sudo, or the root account, gives me the same behavior as using a normal user now...
let's try as a user with sufficient rights:
$ strace -f -ff -o STRACE_CU cu -l /dev/ttyS0 -s 115200
Connected.
but it doesn't relay the serial console. i can abort this with the usual "~." if i...
is this solved?
if not, please take a look at the following:
https://bugs.launchpad.net/ubuntu/+bug/1087519
http://ubuntuforums.org/showthread.php?t=2087953...
i think it's better to have it all in one single bugreport. i think developpers are swamped and trying to keep up by wading through a sea of bug reports.
apparently anyone with a launchpad account can confirm a bug, so i did.
i just hope someone will notice this now.
for the record: i'm currently running a more recent kernel (3.7.0-4-generic)...
silent bump, and link to the launchpad bug:
https://bugs.launchpad.net/ubuntu/+bug/1087519
silent bump, and link to the launchpad bug:
https://bugs.launchpad.net/ubuntu/+bug/1087519
silent bump, and link to the launchpad bug:
https://bugs.launchpad.net/ubuntu/+bug/1087519
silent bump, and link to the launchpad bug:
https://bugs.launchpad.net/ubuntu/+bug/1087519
can someone clue me in why this isn't working as it should? i find it hard to believe i'm the only ubuntu-user that needs a working serial port.
can someone clue me in why this isn't working as it should? i find it hard to believe i'm the only ubuntu-user that needs a working serial port.
i just tried with every possible combination, to rule this out. and it isn't making a difference...
can someone clue me in why this isn't working as it should? i find it hard to believe i'm the...
can someone clue me in why this isn't working as it should? i find it hard to believe i'm the only ubuntu-user that needs a working serial port.
and even more people with the same problem, all during the last weeks...
http://ubuntuforums.org/showthread.php?t=2087953
http://ubuntuforums.org/showthread.php?t=2082610
if this isn't solved yet:
http://ubuntuforums.org/showthread.php?p=12386577
http://ubuntuforums.org/showthread.php?t=2089911
http://ubuntuforums.org/showthread.php?p=12386595
other people...
if this isn't solved yet:
http://ubuntuforums.org/showthread.php?p=12386577
http://ubuntuforums.org/showthread.php?t=2089911
other people are experiencing problems with terminals on serial...
and apparently i'm not the only one with this problem:
http://ubuntuforums.org/showthread.php?p=12345518
i'm currently facing the same problem:
http://ubuntuforums.org/showthread.php?t=2089911
i suspect this is restricted by pam's capabilities...
so i added a line to /etc/security/group.conf
cu;*;ummelum;Al0000-2400;dialout
and created /etc/pam.d/cu
...