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
i haven 't had time to look further into this; my apologies. still
haven't got time, but i know that an ubuntu installation requires group
'dialout' for users, and that the relevant character devices have that
too.
so try "sudo chown root:dialout /dev/ttyS4" ...
i hope this solves it.
--
You re
also check if you have an /etc/serial.conf or a modifief
/etc/init.d/setserial...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't work in 12.04
To manage noti
once again: are you sure nothing else is interfering on irq 17? check
with ' sudo lspci -vvvk|grep "IRQ 17" '
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't w
from the setserial output: "Flags: spd_normal skip_test"; skip_test is
usually set when there is a fake 16550 present; try without this flag,
and see if the uart gets tested ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
one more thing: setserial describes a 16550A uart and your lshw output
describes a 16550. i have no idea whether that makes a difference, but
setserial allow setting a 16550.
from your lspci output: "Kernel driver in use: serial"; this is not a
module, correct?
--
You received this bug notificat
you could dump the modem's diagnostics from windows, and see if that
looks in order...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't work in 12.04
To manage
it's normal you need sudo to delete the configuration file in /etc.
if the following is literal: "cannot write to etc./minicom/minird.xxx", there
is an odd problem with the path ("etc./").
if it's not literal, you probably need to start minicom with sudo to make sure
it can write a file in /etc
i think this is crucial: "All I can say is that Minicom flashes
"Initializing modem" at first, and that the Minicom cursor usually
disappears when I'm typing the commands."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
try booting in windows, and resetting the modem to factory default with
hardware flow control (ATZ4); then boot in ubuntu,
try deleting any minicom configuration you have (user and system-wide), and
start minicom with "-s" (this way, minicom will not initialise the modem); then
try to match min
also make sure the modem is in command modus, not in online modus. use
"+++" to switch...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't work in 12.04
To man
make sure the modem is set to display resulting codes (ATQ0)...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't work in 12.04
To manage notifications about th
ok, i missed the part where you stated it doesn't respond to a simple "AT"...
what if you try to put it back into a factory default mode
(http://www.usr.com/support/5610c/5610c-ug/tech-ref.html#f0) and match that in
minicom?
--
You received this bug notification because you are a member of Ubun
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
are you sure nothing else interferes on irq 17? shouldn't matter, but a
lot of bios' allow setting irq's manually for all things serial and
parallel...
> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
are you sure D0 is a normal status for this modem?
in minicom, do you get an "OK" back i
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
i had a problem with cu always resorting to hardware flow control on a
serial line (Bug #1094278), the fix above actually solves this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/584787
Title:
cu
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
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:/
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
Roger, you said: "Just to make sure it's clearly understood, this modem
is basically an internal sportster with it's own serial card / port at
ttyS4. "
it is a device on a pci-lane. it should identify itself with a vendor
id, which should show up in dmesg or probe by lspci...
--
You received thi
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
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
what is your output of "sudo setserial -av /dev/ttyS4"? if setserial
doesn't exist, you can "sudo apt-get install setserial" it.
what is your output of "sudo stty -a -F /dev/ttyS4"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
$ 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
are you sure the modem is awake (as in, no software magic or no bios
needs to wake it up)?
that modem has firmware that can be updated; do you have the latest?
what happens if you send a regular hayes command to the modem, for example:
escape, speaker always on, volume up and a pause (to hear a
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
Roger, have you verified whether the device is actually allocated (Kees'
question)?
I'd love to see a trace of your problem, to compare it with mine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087
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
i have no clue. i hid my own comments, to keep this bug report clean. i
made a separate bug report (for program 'cu', Bug #1094278 ) and hope
the maintainer takes a look at it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
$ 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) =
Public bug reported:
almost entirely default install of xubuntu 12.10; note that i'm running
a 3.7 kernel (because of Bug #1085115), but the problem is the same with
the default kernel. if i boot this box in openbsd or netbsd, cu will
connect just fine.
i need to access a terminal on another host
Thank you Kees! gives me something to bite into :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't work in 12.04
To manage notifications about this bug go to:
by the way, this might be related:
https://bugs.launchpad.net/qemu/+bug/1086745
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't work in 12.04
To manage notifi
$ sudo cat /proc/tty/driver/serial
serinfo:1.0 driver revision:
0: uart:16550A port:03F8 irq:4 tx:0 rx:0 DSR
1: uart:16550A port:02F8 irq:3 tx:0 rx:0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
$ sudo uname -a
Linux iugo 3.7.0-4-generic #12~lp1085115v1 SMP Fri Nov 30 20:57:19 UTC 2012
i686 i686 i686 GNU/Linux
(i have this kernel because of Bug #1085115, but the standard ubuntu kernel
behaves exactly similar)
$ sudo dmesg|grep tty
[0.00] console [tty0] enabled
[0.663436] 00:
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087519
Title:
Serial port ttyS4 doesn't work in 12.04
To manage notifications about this bug go
i have a very similar problem: trying to use a serial console (rs232c-
cable attached to serial port /dev/ttyS0) with 'cu'. this used to work
in older ubuntu-releases. this doesn't work anymore, and it is
apparently not related to permissions. on the exact same hardware, this
does work with with 'c
i forgot:
$ sudo uname -a
Linux iugo 3.7.0-4-generic #12~lp1085115v1 SMP Fri Nov 30 20:57:19 UTC 2012
i686 i686 i686 GNU/Linux
i did boot the new kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
thanks for the build! alas...
$ cat /var/log/dpkg.log|grep "status installed"
2012-12-01 11:16:21 status installed linux-image-3.7.0-4-generic:i386
3.7.0-4.12~lp1085115v1
2012-12-01 11:29:08 status installed linux-headers-3.7.0-4:all
3.7.0-4.12~lp1085115v1
2012-12-01 11:33:14 status installed li
Public bug reported:
kernel 3.5.0-19-generic #30-Ubuntu SMP
LSB Version:
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
Distributor ID: Ubuntu
Description:Ubuntu 12.10
Release:12
61 matches
Mail list logo
