Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25970 - [initscripts] inittab: Raise agetty speed to 115200

Attached to Project: Arch Linux
Opened by Mark (voidzero) - Sunday, 11 September 2011, 23:05 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 20 September 2011, 11:18 GMT
Task Type Feature Request
Category Arch Projects
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Recently I had a bright moment, where I realised that my slow console display would probably be faster on screen updates if I would change agetty's "38400" argument to 115200. And voila.

So I suggest to make this default. Why is it set to 38400 anyway?
This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 20 September 2011, 11:18 GMT
Reason for closing:  Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 12 September 2011, 00:54 GMT
Such parameter does nothing on vt ;)
Comment by Mark (voidzero) - Monday, 12 September 2011, 10:50 GMT
I think this depends on the device, because for me my screen really updates faster. Maybe it has to do with framebuffer..
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 12 September 2011, 11:09 GMT
Interesting, what is your backing device? Is this value reflected/changed when see the speed in stty command?
Comment by Tom Gundersen (tomegun) - Monday, 12 September 2011, 22:25 GMT
Since we use the "-s" parameter we are supposed to be given the rate by the kernel. If this really makes a difference for you, maybe it would be worth trying to figure out if the kernel is setting the wrong baud, or if it is setting the correct one but it is just being ignored by atty...
Comment by Mark (voidzero) - Monday, 12 September 2011, 22:34 GMT
I have found this to occur on a server with the most recent (bleeding edge) Xen and an Archlinux dom0. As the server is running in a datacenter I am not able to test this any time soon... or at least I hope so, because that means that this server is still up :) But, to reiterate, I am indeed talking about the normal 'getties' rather than serial ports. I will try to reproduce this issue on a Xen testing server and then I'll report back.

Tom, how can I figure out what rate is set by the kernel?
Comment by Mark (voidzero) - Monday, 12 September 2011, 22:36 GMT
Also, it might be good to note that the production server is using the xgifb kernel module/fb device.
Comment by Tom Gundersen (tomegun) - Monday, 12 September 2011, 23:03 GMT
@voidzero: stty is your friend. I'm not abele to do anything interesting here, no matter what I do I get 38400 baud...
Comment by Mark (voidzero) - Tuesday, 20 September 2011, 00:33 GMT
I am not able to reproduce this bug. Please invalidise/close. :)

Loading...