getty should be started automatically on serial port when serial console is set on kernel command line
Bug #702574 reported by
Clint Byrum
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Fix Committed
|
Wishlist
|
James Hunt |
Bug Description
Binary package hint: upstart
If a user passes console=ttySXXX on the kernel commandline to get a serial console, they will see the boot happen on the serial port, but not be given a chance to login on the serial port.
We should ship an upstart job that starts a getty on the serial console in this case.
Related branches
lp:~clint-fewbar/ubuntu/natty/upstart/add-serial-console
Ready for review
for merging
into
lp:ubuntu/natty/upstart
- James Hunt (community): Needs Fixing
- Scott James Remnant: Pending requested
-
Diff: 71 lines (+59/-0)2 files modifieddebian/changelog (+6/-0)
debian/conf/ttyS.conf (+53/-0)
Changed in upstart (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in upstart (Ubuntu): | |
assignee: | nobody → James Hunt (jamesodhunt) |
status: | Confirmed → In Progress |
Changed in upstart (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Due to the complexities of parsing the console= kernel param, as Clint suggested, we could just let the kernel+getty auto-detect speed.
We could therefore create a /etc/init/ ttyUSB0. conf (or similar) containing:
exec /sbin/getty -m -8 115200, 57600,38400, 19200,9600, 4800,2400, 1200 ttyUSB0
By specifying all possible/ reasonable( ?) baud rates as above, no complex param parsing is required for "console=": we only need to extract the device name itself.
Tested on natty booting with "console= ttyUSB0, 115200n8r console=tty" after removing "quiet" and "splash".
Getty was spawned and I could login, but my client end needs some "minicom lovin'" since I was getting control chars being echoed in minicom.