** Changed in: uucp (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage notifications
neat confirmation - it's 2015, and this bug is from 1995. Seemingly no-
one has had a need for a serial line in the last two decades :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
c
This used to work fine. I thought it was a bug in the pl2303 driver, but
it's definitly this issue. Look at stty output while cu running, shows
rtscts enabled. After adding /etc/uucp/port file, with tcp options, cu
works fine, rtscts disabled.
--
You received this bug notification because you are
There are two issues here:
cu randomly identifies the serial connection as dialin (nortscts) ot
dialout (rtscts). I don't care about that distinction being broken. I
fix that with the patch.
The other problem is 'line in use' which is caused by running cu as
root. The permission issues are discus
i have hard time of the issue.
i tried with many way including which figured out above.
after the patch but cu tells following,
./cu: mkdir (/usr/spool): Permission denied
./cu: /dev/ttyS0: Line in use
for the patch, i download uucp 1.07 source from http://airs.com/ian/uucp.html
and fixed sources
patch http://bugs.debian.org/cgi-
bin/bugreport.cgi?msg=15;filename=flow.patch;att=1;bug=336996
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect
i've glanced at the code: in case of TCP, hardware flow control is not
set explicitely (in other cases, it is set).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect pr
No, that's ok; I've added a comment to the debian bug, and I probably won't do
anything else with it; I've marked the bug
as triaged and added comemnts to the others - I suspect the right thing is to
add both fixes, although it probably needs someone with some time to grope
around the cu code an
me neither, but if i rename the /etc/uucp/port file, it doesn't work
anymore.
do you want an strace of a working example?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't con
Huh ok, I don't quite see the relation between 584787's fix and what
you're seeing; but hohum!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial co
https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/584787 : this
actually works...
$ ls /etc/uucp
total 28
drwxr-xr-x 2 root root 4096 Dec 31 23:27 .
drwxr-xr-x 147 root root 12288 Dec 31 22:19 ..
-rw-r--r-- 1 root uucp 461 Oct 9 01:24 config
-rw-r--r-- 1 root root86 Dec 31 23:27 po
thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
** Changed in: uucp (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage notifications about
Hi Koen,
Nicely found; I think the bug should stay open - I don't see a fix for it!
Can you try (the apparently unrelated) fix at:
https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/584787
it's just creating a config file, so it should be easy to try. Ah, and I've
found an
ancient debian bug
Triaged: Seems to be the same as the debian bug filed in '05, and looks
possible the patch linked to from NetBSD in '01 might fix it?!
** Changed in: uucp (Ubuntu)
Importance: Undecided => Medium
** Changed in: uucp (Ubuntu)
Status: New => Triaged
--
You received this bug notificatio
from the manual of cu:
"BUGS
This program does not work very well."
:)
i would love to know a workaround though; setting the flag manually with
stty, while cu has a connection, is apparently not possible...
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
as far as i am concerned, this bugreport can be closed; apparently this
was already a bug in 1995, and it has never been fixed
(http://web.archiveorange.com/archive/v/iBpRaJf4WODgPva7sywW)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
and this seems to be a very well known problem, that goes back a decade:
http://www.google.be/search?hl=en&as_q=%22cu%22+%22crtscts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu do
to be clear: my serial line works fine in minicom (i can access the
remote host, everything works as it should), but not with cu...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu do
so this works in minicom, if i disable hardware and software flow
control...
i put everything back as it should be: permissions are back to normal, target
host has a getty...
i try setting correct parameters (speed, no software flow control, no hardware
flow control):
$ stty -a -F /dev/ttyS0
sp
minicom sees the incoming hello...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage notifications about this bug go to:
https:/
Hmm.
Well we still don't know if the problem is cu or anything else. I doubt it's
anything complex with acpi etc.
For perms just do a simple chmod a+rw /dev/ttyS* (as long as you are
happy with that and to fix it later and it's a single user system of
course!).
OK, 1st question - are you sure y
for what it's worth: the cable is a standard 9-pin crossover serial
(DB-9)...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage
after reading Bug #577433, i booted with acpi=off and tried, but it
didn't make any difference...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial
spot the difference!
# while booted in openbsd, on the same hardware, this always works
speed 115200 baud; 0 rows; 0 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo
-extproc -xcase
iflags:
but it still won't connect...
$ cu -l /dev/ttyS0 -s 115200 --nostop
Connected.
~.
Disconnected.
$ cu -l /dev/ttyS0 -s 115200 --nostop -e
Connected.
~.
Disconnected.
$ cu -l /dev/ttyS0 -s 115200 --nostop -o
Connected.
~.
Disconnected.
$ cu -l /dev/ttyS0 -s 115200 --nostop -eo
Connected.
~.
Disconne
why aren't any settings actually set by stty?! ?
let's try this without sudo...
$ stty -F /dev/ttyS0 speed 115200
115200
$ stty -F /dev/ttyS0 icanon
$ stty -F /dev/ttyS0 isig
$ stty -F /dev/ttyS0 iexten
$ stty -F /dev/ttyS0 echo
$ stty -F /dev/ttyS0 echoe
$ stty -F /dev/ttyS0 -istrip
$ stty -F /de
so, i did...
$ sudo stty -F /dev/ttyS0 speed 115200
115200
$ sudo stty -F /dev/ttyS0 icanon
$ sudo stty -F /dev/ttyS0 isig
$ sudo stty -F /dev/ttyS0 iexten
$ sudo stty -F /dev/ttyS0 echo
$ sudo stty -F /dev/ttyS0 echoe
$ sudo stty -F /dev/ttyS0 -altwerase
stty: when specifying an output style, mode
so...
rts/cts flow control is different, and flow control is not based on a carrier
detect;
we're missing a dsusp control character.
we don't strip to 7 bits; we map carriage return to newline on input: we enable
start/stop output control; we allow any character to restart outut; we impose a
lim
the differences in terminal setting between a working configuration
(openbsd) and a non-working configuration (xubuntu) on the same
hardware; only the differences are shown, similar flags are left out:
# openbsd
cchars: discard = ^O; dsusp = ^Y; status = ; time = 0
cflags: -crtscts -mdmbuf
oflags:
to rule out anything related to permissions, i did:
$ sudo ls -al /dev/ttyS0
crw-rw 1 root dialout 4, 64 Dec 31 09:21 /dev/ttyS0
$ sudo chmod 0666 /dev/ttyS0
$ sudo chown koen:dialout /dev/ttyS0
$ sudo ls -al /dev/ttyS0
crw-rw-rw- 1 koen dialout 4, 64 Dec 31 10:15 /dev/ttyS0
which shouldn't m
the following might have been relevant: Bug #255200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage notifications about this b
on the target host (openbsd), i disabled the getty:
$ sudo cat /etc/ttys|grep tty00
tty00 noneunknown off
#tty00 "/usr/libexec/getty std.115200" vt220 on secure
on the xubuntu host, there was no getty on any ttyS:
$ sudo pstree -ac|grep getty
|-getty -8 38400 tty
Hi Koen,
It would probably be worth retrying the things without the getty (might be
worth checking there wasn't one on the xubuntu host as well!).
Hmm odd; the echo is about the simplest thing to try. if retrying without
the getty doesn't help; have you got a
serial breakout box, or a lead
note: while i tried the above, the target host still had a getty on that
port
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage
on the problematic xubuntu host, i tried...
$ echo TEST>/dev/ttyS0
and
$ sudo echo TEST>/dev/ttyS0
both gave me prompt again
while on the target host, i had...
$ sudo cat /dev/tty00
and
$ sudo hexdump /dev/tty00
and
$ sudo less -f /dev/tty00
and
$ sudo od /dev/tty00
didn't display anything...
o
thanks for the input!
i suspect it's the kernel; i don't see why cu would be at fault - it has been
working fine for decades.
my apologies for attaching a bug report to 'cu', but it's the only way to get
attention to this...
anyway, i tried minicom. didn't work as a normal user, didn't work wit
Hi Koen,
To try and nail down whether this is cu or a kernel serial problem, have you
tried:
1) Using a different serial program - e.g. minicom ?
2) use something simple like echo Hello > /dev/ttyS0
Dave
--
You received this bug notification because you are a member of Ubuntu
Bu
$ sudo setserial -av /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
from the target machine (openbsd):
$ sudo stty -a -f /dev/tty00
speed 115200 baud; 0 rows; 0 columns;
lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl
-echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin
-nokerninfo -extproc -xcase
iflags: -istrip -icrnl -in
for what it's worth:
$ ls /etc/uucp
config sys
$ cat /etc/uucp/config|grep -Ev '#'
(nothing)
$ cat sys|grep -Ev '#'
protocol gvG
protocol-parameter G packet-size 1024
protocol-parameter G short-packets
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
the following bug report might be relevant: Bug #1087519
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
cu doesn't connect properly to a serial console
To manage notifications about t
for what it's worth: i suspected this is restricted by pam's
capabilities.
so i added a line to /etc/security/group.conf:
cu;*;ummelum;Al-2400;dialout
and created /etc/pam.d/cu:
session optionalpam_permit.so
i used a login-shell and tried my serial console, but alas...
if i try with
for what it's worth: to make sure this wasn't a polkit thing, i made an
action definition for this, and dropped it in /etc/polkit-1/actions:
http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd";>
yes
/usr/bin/cu
-l /dev/ttyS0 -s
115200
unix-user:umme
$ cat STRACE_CU.3140
close(4)= 0
fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(3, F_SETFL, O_RDWR) = 0
rt_sigaction(SIGUSR1, {0x8051460, [], SA_INTERRUPT}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x8051460, [], SA_INTERRUPT}, NULL, 8) =
45 matches
Mail list logo
