| Summary: | syslinux.bbclass needs some work to add serial support and a real menu | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Jason Wessel <jason.wessel> | ||||||
| Component: | deployment | Assignee: | Jason Wessel <jason.wessel> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | Medium | CC: | jason.wessel, Martin.Jansa, mihai.lindner, sgw | ||||||
| Version: | 1.4 | ||||||||
| Target Milestone: | 1.4 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | Don't know | |||||||
| Attachments: |
|
||||||||
Created attachment 1087 [details]
VGA syslinux menu example
Also it would be good to add the capability for a boot splash specified by SYSLINUX_SPLASH on the vga console. Attached is an example.
Implemented in OE with: 7032d559c04bae09e6b7c39ddeb1bf35acc0584c (syslinux.bbclass: Add a default serial console option and real boot menu support) Build Configuration: BB_VERSION = "1.18.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Unknown" TARGET_SYS = "i586-poky-linux" MACHINE = "atom-pc" DISTRO = "poky" DISTRO_VERSION = "1.3+snapshot-20130411" TUNE_FEATURES = "m32 core2" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "master:95b71d2b03a3a6dc5d32a7d6a84ec3420f39aa61" On both: bitbake core-image-basic & bitbake core-image-sato This doesn't allow to disable or change default tty0 as console: + btypes = [ [ "", "console=tty0" ] ] + if menu and syslinux_serial: + btypes = [ [ "Graphics console ", " console=tty0" ], + [ "Serial console ", " console=ttyS0,115200" ] ] It should respect syslinux_serial value even without menu enabled. Enabling menu doesn't work with boot-directdisk: meta/classes/boot-directdisk.bbclass because build_boot_dd reuses syslinux.cfg does not install vesamenu.c32 .. Changing from importance from improvement to major, because this improvement broke existing use-cases for boot-directdisk.bbclass (In reply to comment #6) > Changing from importance from improvement to major, because this improvement > broke existing use-cases for boot-directdisk.bbclass As far as I know this was fixed by: commit 63d164b755b984021f7e3cdba7280918ded6e821 Author: Jason Wessel <jason.wessel@windriver.com> Date: Tue Sep 17 13:32:17 2013 +0000 boot-directdisk.bbclass: Fix media generation problems with vmdk First part was fixed by: syslinux.bbclass: Fix hard coding of console=tty* The SYSLINUX_SERIAL variable was hard coded and occasionally needs to be different for the kernel argument vs the syslinux argument. http://git.openembedded.org/openembedded-core/commit/?id=cf2fba810a8a59cff71bf2c12e516e9080146604 2nd part by that other commit you mention, so yes I agree, it's fixed now. |
Created attachment 1086 [details] Serial Boot Menu Example Syslinux has the full ability for dual vga and serial support as well as a menu with command line editing. It is simply a matter of changing the class around in order to support it. The dual serial / vga support should be on by default, and a new option such as SYSLINUX_SERIAL can be used to disable it. See the example which is attached to this case.