BTS

Issue853

Title regression: serial console baud rate settings misfeature
Priority bug Status resolved
Superseder Nosy List mika, zugschlus
Assigned To mika Topics

Created on 2010-05-21.12:38:44 by zugschlus, last changed 2010-06-02.10:13:06 by mika.

Messages
msg3206 (view) Author: mika Date: 2010-06-02.10:13:05
Successfully verified with grml-small_sid_20100602.iso and bootoption 
console=ttyS0,57600n8 - works as expected. Closing this bugreport.

regards,
-mika-
msg3202 (view) Author: mika Date: 2010-05-31.22:16:36
Michael Prokop <mika@grml.org> has uploaded a package that may fix your bug.
Please test the package and inform the maintainer whether
version 0.9.10 of grml-autoconfig works as intended or not.

Thank you

The changelog is attached below

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 01 Jun 2010 00:00:31 +0200
Source: grml-autoconfig
Binary: grml-autoconfig
Architecture: source all
Version: 0.9.10
Distribution: unstable
Urgency: low
Maintainer: Michael Prokop <mika@grml.org>
Changed-By: Michael Prokop <mika@grml.org>
Description: 
 grml-autoconfig - main bootup process of a Grml (based) system
Changes: 
 grml-autoconfig (0.9.10) unstable; urgency=low
 .
   * console/serial bootoption: allow manually specifying
     baude rate / speed settings. Thanks to Tonnerre Lombard
     and Marc Haber for reporting and special thanks to Marc
     for providing a system for debugging. [Testing: issue853]
Checksums-Sha1: 
 dc85247d72f455c6bf1c85d6a2c65deeea953d8e 945 grml-autoconfig_0.9.10.dsc
 4a92e014185b9e5e19fce93da8cf4ebbe2f0623f 70134 grml-autoconfig_0.9.10.tar.gz
 4f2e25091723ba2dfabaacdbdddafaa4701fad17 90148 grml-autoconfig_0.9.10_all.deb
Checksums-Sha256: 
 b93e92d97e35a5899a58323bb85af1f5b52c8ee765b7b4e08f53b06ecbecb588 945 grml-autoconfig_0.9.10.dsc
 acb9be7d010521a672b2f8ca15d99ce6f5a424120a39f341928cd2bce3484cba 70134 grml-autoconfig_0.9.10.tar.gz
 ef3e6b7a2d044703c93608629af22731a52ba758f8373c5f30361b6abacf4650 90148 grml-autoconfig_0.9.10_all.deb
Files: 
 3b78a9090f651a4543c6679199fac71b 945 grml optional grml-autoconfig_0.9.10.dsc
 8595c55e3317f7ddff1cabaa7d9d0c0b 70134 grml optional grml-autoconfig_0.9.10.tar.gz
 e7a3beb27298f1171b03476bc4024413 90148 grml optional grml-autoconfig_0.9.10_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFMBDKs2N9T+zficugRAqEHAJsGodBS5E2ONRq6KajhDePwpJwvkACdF4vE
Mc/c26GCxU3pEAorDeoPN4g=
=AwtA
-----END PGP SIGNATURE-----
msg3201 (view) Author: mika Date: 2010-05-31.22:07:58
Fixed in Git, thanks for reporting and providing a test environment, Marc!

I just uploaded the Debian packages grml-etc and grml-autoconfig which should 
provide the fix, the upload will automatically set this bugreport to status 
"testing" and I'll make sure it works as expected before finally closing this 
bugreport.

thanks && regards,
-mika-
msg3181 (view) Author: zugschlus Date: 2010-05-21.12:38:42
Hi,

in previous grml versions, grml tool the baud rate to configure the getty on
the serial console from the console= kernel command line item.

Recently, this has changed and tries to use some automatisms from getty, giving
it multiple baud rates on its command line. The getty man page says that a
Break could be used to change to the next baud rate.

This approach seems to be flawed in at least one of my settings, where the
target box has its serial console connected to a console server of unknown
manufacture which is in turn reachable via ssh, and which configuration I
cannot influence at all. grml serial console=ttyS0,57600n8 shows the boot
messages just fine up until the point when it says "Finished execution of main
grml startup" and the console turns to gibberish. This is the point where the
getty is started, and I guess that it comes up with a baud rate of 115200.

The getty man page suggests that a Break will cause the next baud rate to be
activated, but that doesn't seem to work through that Console server. Neither
Ctrl-@, nor Ctrl-C, nor ~B seem to have the desired effect.

I would suggest going back to the old setup, or at least to offer a possibility
to hard-specify the baud rate from the kernel command line in cases where the
new automatism misfires.

Greetings
Marc
History
Date User Action Args
2010-06-02 10:13:06mikasetstatus: testing -> resolved
nosy: mika, zugschlus
messages: + msg3206
2010-05-31 22:16:38mikasetstatus: fixed-in-git -> testing
nosy: mika, zugschlus
messages: + msg3202
2010-05-31 22:08:08mikasetassignedto: mika
nosy: + mika
2010-05-31 22:07:59mikasetstatus: unread -> fixed-in-git
messages: + msg3201
2010-05-21 12:38:44zugschluscreate