network-admin lets poor 9600 tty baud rate stand.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-system-tools (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt |
Bug Description
/dev/ttyS[01] on this Elite K7S5A motherboard are set to 9600 baud
after boot. Using network-admin to activate the ppp0 interface results
in pppd being run as
/usr/sbin/pppd /dev/ttyS0 noauth nopersist nocrtscts defaultroute \
usepeerdns user inputplus.
Since no baud rate has been specified on the pppd command-line
communication between the motherboard and the modem over /dev/ttyS0
happens at 9600 resulting in a very slow Internet experience.
The tty's current baud rate can be examined with
# stty -a </dev/ttyS0 | grep baud
speed 9600 baud; rows 0; columns 0; line = 3;
Although stty can be used to alter it too, I find that sometimes hangs
so prefer
# getty -i -l /bin/true -n -L ttyS0 115200 vt100
Note, unlike some other similar bug-reports I don't need to do this
twice to make it work. Nor do I think it's a kernel bug since
network-admin can't assume that nothing's been diddling with the tty,
e.g. minicom, since boot-up so should explicitly give pppd a baud rate.
What baud rate I don't know -- bring back /etc/ttys! :-) Perhaps the
kernel is also at fault?
# sed /unknown/q /proc/tty/
serinfo:1.0 driver revision:
0: uart:16550A port:000003F8 irq:4 tx:3092388 rx:11957721 RTS|CTS|DTR|DSR|CD
1: uart:16550A port:000002F8 irq:3 tx:2 rx:0
2: uart:unknown port:000003E8 irq:4
#
The alternative would be to place the baud rate in one of the config
files pppd reads, e.g. /etc/ppp/
I think this is quite an important bug because the users it affects are
using a modem for Internet access so it's likely they've one machine
and one means of Internet access, e.g. me. With access being so slow
it's hard to Google, etc., at 800B/s, looking for solutions.
$ lsb_release -sri
Ubuntu 5.04
$ uname -a
Linux blake 2.6.10-5-386 #1 Tue Apr 5 12:12:40 UTC 2005 i686 GNU/Linux
Thanks for your bugreport.
I think it's just a matter of adding
"115200"
at the end of the /etc/ppp/peers/ppp0 file
Can you please check if that helps?